IMPORTANT: No additional bug fixes or documentation updates will be released for this version. For the latest information, see the current release documentation.

› ›

Source Fields

edit

Source Fields

edit

Source fields describe details about the source of a packet/event.

Source fields are usually populated in conjunction with destination fields.

Source Field Details

edit

Field	Description	Level
source.address	Some event source addresses are defined ambiguously. The event will sometimes list an IP, a domain or a unix socket. You should always store the raw address in the `.address` field. Then it should be duplicated to `.ip` or `.domain`, depending on which one it is. type: keyword	extended
source.bytes	Bytes sent from the source to the destination. type: long example: `184`	core
source.domain	Source domain. type: keyword	core
source.ip	IP address of the source. Can be one or multiple IPv4 or IPv6 addresses. type: ip	core
source.mac	MAC address of the source. type: keyword	core
source.nat.ip	Translated ip of source based NAT sessions (e.g. internal client to internet) Typically connections traversing load balancers, firewalls, or routers. type: ip	extended
source.nat.port	Translated port of source based NAT sessions. (e.g. internal client to internet) Typically used with load balancers, firewalls, or routers. type: long	extended
source.packets	Packets sent from the source to the destination. type: long example: `12`	core
source.port	Port of the source. type: long	core
source.registered_domain	The highest registered source 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: `example.com`	extended
source.top_level_domain	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: `co.uk`	extended

Field Reuse

edit

Field sets that can be nested under Source

edit

Nested fields	Description
source.as.*	Fields describing an Autonomous System (Internet routing prefix).
source.geo.*	Fields describing a location.
source.user.*	Fields to describe the user relevant to the event.

« Service Fields Threat Fields »