URL Fields
editURL Fields
editURL fields provide support for complete or partial URLs, and supports the breaking down into scheme, domain, path, and so on.
URL Field Details
editField | Description | Level |
---|---|---|
Domain of the url, such as "www.elastic.co". In some cases a URL may refer to an IP and/or port directly, without a domain name. In this case, the IP address would go to the If the URL contains a literal IPv6 address enclosed by type: keyword example: |
extended |
|
The field contains the file extension from the original request url, excluding the leading dot. The file extension is only set if it exists, as not every url has a file extension. The leading period must not be included. For example, the value must be "png", not ".png". Note that when the file name has multiple extensions (example.tar.gz), only the last one should be captured ("gz", not "tar.gz"). type: keyword example: |
extended |
|
Portion of the url after the The type: keyword |
extended |
|
If full URLs are important to your use case, they should be stored in type: wildcard Multi-fields:
example: |
extended |
|
Unmodified original url as seen in the event source. Note that in network monitoring, the observed URL may be a full URL, whereas in access logs, the URL is often just represented as a path. This field is meant to represent the URL as it was observed, complete or not. type: wildcard Multi-fields:
example: |
extended |
|
Password of the request. type: keyword |
extended |
|
Path of the request, such as "/search". type: wildcard |
extended |
|
Port of the request, such as 443. type: long example: |
extended |
|
The query field describes the query string of the request, such as "q=elasticsearch". The type: keyword |
extended |
|
The highest registered url domain, stripped of the subdomain. For example, the registered domain for "foo.example.com" is "example.com". 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". type: keyword example: |
extended |
|
Scheme of the request, such as "https". Note: The type: keyword example: |
extended |
|
The subdomain portion of a fully qualified domain name includes all of the names except the host name under the registered_domain. In a partially qualified domain, or if the the qualification level of the full name cannot be determined, subdomain contains all of the names below the registered domain. For example the subdomain portion of "www.east.mydomain.co.uk" is "east". If the domain has multiple levels of subdomain, such as "sub2.sub1.example.com", the subdomain field should contain "sub2.sub1", with no trailing period. type: keyword example: |
extended |
|
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". 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". type: keyword example: |
extended |
|
Username of the request. type: keyword |
extended |
Field Reuse
editThe url
fields are expected to be nested at:
-
threat.enrichments.indicator.url
-
threat.indicator.url
Note also that the url
fields may be used directly at the root of the events.