You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/fields/field-details.asciidoc
+18-18Lines changed: 18 additions & 18 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -496,7 +496,7 @@ a| The highest registered client domain, stripped of the subdomain.
496
496
497
497
For example, the registered domain for "foo.example.com" is "example.com".
498
498
499
-
This value can be determined precisely with a list like the public suffix list (http://publicsuffix.org). Trying to approximate this by simply taking the last two labels will not work well for TLDs such as "co.uk".
499
+
This value can be determined precisely with a list like the public suffix list (https://publicsuffix.org). Trying to approximate this by simply taking the last two labels will not work well for TLDs such as "co.uk".
500
500
501
501
type: keyword
502
502
@@ -532,7 +532,7 @@ example: `east`
532
532
533
533
a| The effective top level domain (eTLD), also known as the domain suffix, is the last part of the domain name. For example, the top level domain for example.com is "com".
534
534
535
-
This value can be determined precisely with a list like the public suffix list (http://publicsuffix.org). Trying to approximate this by simply taking the last label will not work well for effective TLDs such as "co.uk".
535
+
This value can be determined precisely with a list like the public suffix list (https://publicsuffix.org). Trying to approximate this by simply taking the last label will not work well for effective TLDs such as "co.uk".
536
536
537
537
type: keyword
538
538
@@ -1596,7 +1596,7 @@ a| The highest registered destination domain, stripped of the subdomain.
1596
1596
1597
1597
For example, the registered domain for "foo.example.com" is "example.com".
1598
1598
1599
-
This value can be determined precisely with a list like the public suffix list (http://publicsuffix.org). Trying to approximate this by simply taking the last two labels will not work well for TLDs such as "co.uk".
1599
+
This value can be determined precisely with a list like the public suffix list (https://publicsuffix.org). Trying to approximate this by simply taking the last two labels will not work well for TLDs such as "co.uk".
1600
1600
1601
1601
type: keyword
1602
1602
@@ -1632,7 +1632,7 @@ example: `east`
1632
1632
1633
1633
a| The effective top level domain (eTLD), also known as the domain suffix, is the last part of the domain name. For example, the top level domain for example.com is "com".
1634
1634
1635
-
This value can be determined precisely with a list like the public suffix list (http://publicsuffix.org). Trying to approximate this by simply taking the last label will not work well for effective TLDs such as "co.uk".
1635
+
This value can be determined precisely with a list like the public suffix list (https://publicsuffix.org). Trying to approximate this by simply taking the last label will not work well for effective TLDs such as "co.uk".
1636
1636
1637
1637
type: keyword
1638
1638
@@ -2125,7 +2125,7 @@ a| The highest registered domain, stripped of the subdomain.
2125
2125
2126
2126
For example, the registered domain for "foo.example.com" is "example.com".
2127
2127
2128
-
This value can be determined precisely with a list like the public suffix list (http://publicsuffix.org). Trying to approximate this by simply taking the last two labels will not work well for TLDs such as "co.uk".
2128
+
This value can be determined precisely with a list like the public suffix list (https://publicsuffix.org). Trying to approximate this by simply taking the last two labels will not work well for TLDs such as "co.uk".
2129
2129
2130
2130
type: keyword
2131
2131
@@ -2161,7 +2161,7 @@ example: `www`
2161
2161
2162
2162
a| The effective top level domain (eTLD), also known as the domain suffix, is the last part of the domain name. For example, the top level domain for example.com is "com".
2163
2163
2164
-
This value can be determined precisely with a list like the public suffix list (http://publicsuffix.org). Trying to approximate this by simply taking the last label will not work well for effective TLDs such as "co.uk".
2164
+
This value can be determined precisely with a list like the public suffix list (https://publicsuffix.org). Trying to approximate this by simply taking the last label will not work well for effective TLDs such as "co.uk".
2165
2165
2166
2166
type: keyword
2167
2167
@@ -2391,7 +2391,7 @@ Note: this field should contain an array of values.
2391
2391
2392
2392
a| A hash of the Go language imports in an ELF file excluding standard library imports. An import hash can be used to fingerprint binaries even after recompilation or other code-level transformations have occurred, which would change more traditional hash values.
2393
2393
2394
-
The algorithm used to calculate the Go symbol hash and a reference implementation are available [here](https://github.com/elastic/toutoumomoma).
2394
+
The algorithm used to calculate the Go symbol hash and a reference implementation are available here: https://github.com/elastic/toutoumomoma
2395
2395
2396
2396
type: keyword
2397
2397
@@ -6228,7 +6228,7 @@ beta::[ These fields are in beta and are subject to change.]
6228
6228
6229
6229
a| A hash of the Go language imports in a Mach-O file excluding standard library imports. An import hash can be used to fingerprint binaries even after recompilation or other code-level transformations have occurred, which would change more traditional hash values.
6230
6230
6231
-
The algorithm used to calculate the Go symbol hash and a reference implementation are available [here](https://github.com/elastic/toutoumomoma).
6231
+
The algorithm used to calculate the Go symbol hash and a reference implementation are available here: https://github.com/elastic/toutoumomoma
6232
6232
6233
6233
type: keyword
6234
6234
@@ -7897,7 +7897,7 @@ example: `6.3.9600.17415`
7897
7897
7898
7898
a| A hash of the Go language imports in a PE file excluding standard library imports. An import hash can be used to fingerprint binaries even after recompilation or other code-level transformations have occurred, which would change more traditional hash values.
7899
7899
7900
-
The algorithm used to calculate the Go symbol hash and a reference implementation are available [here](https://github.com/elastic/toutoumomoma).
7900
+
The algorithm used to calculate the Go symbol hash and a reference implementation are available here: https://github.com/elastic/toutoumomoma
7901
7901
7902
7902
type: keyword
7903
7903
@@ -9934,7 +9934,7 @@ a| The highest registered server domain, stripped of the subdomain.
9934
9934
9935
9935
For example, the registered domain for "foo.example.com" is "example.com".
9936
9936
9937
-
This value can be determined precisely with a list like the public suffix list (http://publicsuffix.org). Trying to approximate this by simply taking the last two labels will not work well for TLDs such as "co.uk".
9937
+
This value can be determined precisely with a list like the public suffix list (https://publicsuffix.org). Trying to approximate this by simply taking the last two labels will not work well for TLDs such as "co.uk".
9938
9938
9939
9939
type: keyword
9940
9940
@@ -9970,7 +9970,7 @@ example: `east`
9970
9970
9971
9971
a| The effective top level domain (eTLD), also known as the domain suffix, is the last part of the domain name. For example, the top level domain for example.com is "com".
9972
9972
9973
-
This value can be determined precisely with a list like the public suffix list (http://publicsuffix.org). Trying to approximate this by simply taking the last label will not work well for effective TLDs such as "co.uk".
9973
+
This value can be determined precisely with a list like the public suffix list (https://publicsuffix.org). Trying to approximate this by simply taking the last label will not work well for effective TLDs such as "co.uk".
9974
9974
9975
9975
type: keyword
9976
9976
@@ -10505,7 +10505,7 @@ a| The highest registered source domain, stripped of the subdomain.
10505
10505
10506
10506
For example, the registered domain for "foo.example.com" is "example.com".
10507
10507
10508
-
This value can be determined precisely with a list like the public suffix list (http://publicsuffix.org). Trying to approximate this by simply taking the last two labels will not work well for TLDs such as "co.uk".
10508
+
This value can be determined precisely with a list like the public suffix list (https://publicsuffix.org). Trying to approximate this by simply taking the last two labels will not work well for TLDs such as "co.uk".
10509
10509
10510
10510
type: keyword
10511
10511
@@ -10541,7 +10541,7 @@ example: `east`
10541
10541
10542
10542
a| The effective top level domain (eTLD), also known as the domain suffix, is the last part of the domain name. For example, the top level domain for example.com is "com".
10543
10543
10544
-
This value can be determined precisely with a list like the public suffix list (http://publicsuffix.org). Trying to approximate this by simply taking the last label will not work well for effective TLDs such as "co.uk".
10544
+
This value can be determined precisely with a list like the public suffix list (https://publicsuffix.org). Trying to approximate this by simply taking the last label will not work well for effective TLDs such as "co.uk".
10545
10545
10546
10546
type: keyword
10547
10547
@@ -12804,7 +12804,7 @@ a| The highest registered url domain, stripped of the subdomain.
12804
12804
12805
12805
For example, the registered domain for "foo.example.com" is "example.com".
12806
12806
12807
-
This value can be determined precisely with a list like the public suffix list (http://publicsuffix.org). Trying to approximate this by simply taking the last two labels will not work well for TLDs such as "co.uk".
12807
+
This value can be determined precisely with a list like the public suffix list (https://publicsuffix.org). Trying to approximate this by simply taking the last two labels will not work well for TLDs such as "co.uk".
a| The effective top level domain (eTLD), also known as the domain suffix, is the last part of the domain name. For example, the top level domain for example.com is "com".
12866
12866
12867
-
This value can be determined precisely with a list like the public suffix list (http://publicsuffix.org). Trying to approximate this by simply taking the last label will not work well for effective TLDs such as "co.uk".
12867
+
This value can be determined precisely with a list like the public suffix list (https://publicsuffix.org). Trying to approximate this by simply taking the last label will not work well for effective TLDs such as "co.uk".
12868
12868
12869
12869
type: keyword
12870
12870
@@ -13663,7 +13663,7 @@ The vulnerability fields describe information about a vulnerability that is rele
a| The type of system or architecture that the vulnerability affects. These may be platform-specific (for example, Debian or SUSE) or general (for example, Database or Firewall). For example (https://qualysguard.qualys.com/qwebhelp/fo_portal/knowledgebase/vulnerability_categories.htm[Qualys vulnerability categories])
13666
+
a| The type of system or architecture that the vulnerability affects. These may be platform-specific (for example, Debian or SUSE) or general (for example, Database or Firewall). For example (https://qualysguard.qualys.com/qwebhelp/fo_portal/knowledgebase/vulnerability_categories.htm)
a| The description of the vulnerability that provides additional context of the vulnerability. For example (https://cve.mitre.org/about/faqs.html#cve_entry_descriptions_created[Common Vulnerabilities and Exposure CVE description])
13703
+
a| The description of the vulnerability that provides additional context of the vulnerability. For example (https://cve.mitre.org/about/faqs.html#cve_entry_descriptions_created)
13704
13704
13705
13705
type: keyword
13706
13706
@@ -13738,7 +13738,7 @@ example: `CVE`
13738
13738
[[field-vulnerability-id]]
13739
13739
<<field-vulnerability-id, vulnerability.id>>
13740
13740
13741
-
a| The identification (ID) is the number portion of a vulnerability entry. It includes a unique identification number for the vulnerability. For example (https://cve.mitre.org/about/faqs.html#what_is_cve_id[Common Vulnerabilities and Exposure CVE ID])
13741
+
a| The identification (ID) is the number portion of a vulnerability entry. It includes a unique identification number for the vulnerability. For example (https://cve.mitre.org/about/faqs.html#what_is_cve_id)
0 commit comments