Date/time when the event originated. This is the date/time extracted from the event, typically representing when the event was generated by the source. If the event source has no original timestamp, this value is typically populated by the first time the event was received by the pipeline. Required field for all events.

type: date

example: 2016-05-23T08:05:34.853Z

required: True

Custom key/value pairs. Can be used to add meta information to events. Should not contain nested objects. All values are stored as keyword. Example: docker and k8s labels.

type: object

example: {application: foo-bar, env: production}

For log events the message field contains the log message, optimized for viewing in a log viewer. For structured logs without an original message field, other fields can be concatenated to form a human-readable summary of the event. If multiple messages exist, they can be combined into one message.

type: text

example: Hello World

List of keywords used to tag each event.

type: keyword

example: ["production", "env2"]

Ephemeral identifier of this agent (if one exists). This id normally changes across restarts, but agent.id does not.

type: keyword

example: 8a4f500f

Unique identifier of this agent (if one exists). Example: For Beats this would be beat.id.

type: keyword

example: 8a4f500d

Custom name of the agent. This is a name that can be given to an agent. This can be helpful if for example two Filebeat instances are running on the same host but a human readable separation is needed on which Filebeat instance data is coming from. If no name is given, the name is often left empty.

type: keyword

example: foo

Type of the agent. The agent type stays always the same and should be given by the agent used. In case of Filebeat the agent would always be Filebeat also if two Filebeat instances are run on the same machine.

type: keyword

example: filebeat

Version of the agent.

type: keyword

example: 6.0.0-rc2

Unique number allocated to the autonomous system. The autonomous system number (ASN) uniquely identifies each network on the Internet.

type: long

example: 15169

Organization name.

type: keyword

example: Google LLC

type: text

Some event client 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

Unique number allocated to the autonomous system. The autonomous system number (ASN) uniquely identifies each network on the Internet.

type: long

example: 15169

Organization name.

type: keyword

example: Google LLC

type: text

Bytes sent from the client to the server.

type: long

example: 184

format: bytes

Client domain.

type: keyword

City name.

type: keyword

example: Montreal

Name of the continent.

type: keyword

example: North America

Country ISO code.

type: keyword

example: CA

Country name.

type: keyword

example: Canada

Longitude and latitude.

type: geo_point

example: { "lon": -73.614830, "lat": 45.505918 }

User-defined description of a location, at the level of granularity they care about. Could be the name of their data centers, the floor number, if this describes a local physical entity, city names. Not typically used in automated geolocation.

type: keyword

example: boston-dc

Region ISO code.

type: keyword

example: CA-QC

Region name.

type: keyword

example: Quebec

IP address of the client. Can be one or multiple IPv4 or IPv6 addresses.

type: ip

MAC address of the client.

type: keyword

Translated IP of source based NAT sessions (e.g. internal client to internet). Typically connections traversing load balancers, firewalls, or routers.

type: ip

Translated port of source based NAT sessions (e.g. internal client to internet). Typically connections traversing load balancers, firewalls, or routers.

type: long

format: string

Packets sent from the client to the server.

type: long

example: 12

Port of the client.

type: long

format: string

The highest registered client domain, stripped of the subdomain. For example, the registered domain for "foo.google.com" is "google.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: google.com

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 google.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

Name of the directory the user is a member of. For example, an LDAP or Active Directory domain name.

type: keyword

User email address.

type: keyword

User’s full name, if available.

type: keyword

example: Albert Einstein

type: text

Name of the directory the group is a member of. For example, an LDAP or Active Directory domain name.

type: keyword

Unique identifier for the group on the system/platform.

type: keyword

Name of the group.

type: keyword

Unique user hash to correlate information for a user in anonymized form. Useful if user.id or user.name contain confidential information and cannot be used.

type: keyword

One or multiple unique identifiers of the user.

type: keyword

Short name or login of the user.

type: keyword

example: albert

type: text

The cloud account or organization id used to identify different entities in a multi-tenant environment. Examples: AWS account id, Google Cloud ORG Id, or other unique identifier.

type: keyword

example: 666777888999

Availability zone in which this host is running.

type: keyword

example: us-east-1c

Instance ID of the host machine.

type: keyword

example: i-1234567890abcdef0

Instance name of the host machine.

type: keyword

Machine type of the host machine.

type: keyword

example: t2.medium

Name of the cloud provider. Example values are aws, azure, gcp, or digitalocean.

type: keyword

example: aws

Region in which this host is running.

type: keyword

example: us-east-1

Unique container id.

type: keyword

Name of the image the container was built on.

type: keyword

Container image tag.

type: keyword

Image labels.

type: object

Container name.

type: keyword

Runtime managing this container.

type: keyword

example: docker

Some event destination 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

Unique number allocated to the autonomous system. The autonomous system number (ASN) uniquely identifies each network on the Internet.

type: long

example: 15169

Organization name.

type: keyword

example: Google LLC

type: text

Bytes sent from the destination to the source.

type: long

example: 184

format: bytes

Destination domain.

type: keyword

City name.

type: keyword

example: Montreal

Name of the continent.

type: keyword

example: North America

Country ISO code.

type: keyword

example: CA

Country name.

type: keyword

example: Canada

Longitude and latitude.

type: geo_point

example: { "lon": -73.614830, "lat": 45.505918 }

User-defined description of a location, at the level of granularity they care about. Could be the name of their data centers, the floor number, if this describes a local physical entity, city names. Not typically used in automated geolocation.

type: keyword

example: boston-dc

Region ISO code.

type: keyword

example: CA-QC

Region name.

type: keyword

example: Quebec

IP address of the destination. Can be one or multiple IPv4 or IPv6 addresses.

type: ip

MAC address of the destination.

type: keyword

Translated ip of destination based NAT sessions (e.g. internet to private DMZ) Typically used with load balancers, firewalls, or routers.

type: ip

Port the source session is translated to by NAT Device. Typically used with load balancers, firewalls, or routers.

type: long

format: string

Packets sent from the destination to the source.

type: long

example: 12

Port of the destination.

type: long

format: string

The highest registered destination domain, stripped of the subdomain. For example, the registered domain for "foo.google.com" is "google.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: google.com

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 google.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

Name of the directory the user is a member of. For example, an LDAP or Active Directory domain name.

type: keyword

User email address.

type: keyword

User’s full name, if available.

type: keyword

example: Albert Einstein

type: text

Name of the directory the group is a member of. For example, an LDAP or Active Directory domain name.

type: keyword

Unique identifier for the group on the system/platform.

type: keyword

Name of the group.

type: keyword

Unique user hash to correlate information for a user in anonymized form. Useful if user.id or user.name contain confidential information and cannot be used.

type: keyword

One or multiple unique identifiers of the user.

type: keyword

Short name or login of the user.

type: keyword

example: albert

type: text

An array containing an object for each answer section returned by the server. The main keys that should be present in these objects are defined by ECS. Records that have more information may contain more keys than what ECS defines. Not all DNS data sources give all details about DNS answers. At minimum, answer objects must contain the data key. If more information is available, map as much of it to ECS as possible, and add any additional fields to the answer objects as custom fields.

type: object

The class of DNS data contained in this resource record.

type: keyword

example: IN

The data describing the resource. The meaning of this data depends on the type and class of the resource record.

type: keyword

example: 10.10.10.10

The domain name to which this resource record pertains. If a chain of CNAME is being resolved, each answer’s name should be the one that corresponds with the answer’s data. It should not simply be the original question.name repeated.

type: keyword

example: www.google.com

The time interval in seconds that this resource record may be cached before it should be discarded. Zero values mean that the data should not be cached.

type: long

example: 180

The type of data contained in this resource record.

type: keyword

example: CNAME

Array of 2 letter DNS header flags. Expected values are: AA, TC, RD, RA, AD, CD, DO.

type: keyword

example: [RD, RA]

The DNS packet identifier assigned by the program that generated the query. The identifier is copied to the response.

type: keyword

example: 62111

The DNS operation code that specifies the kind of query in the message. This value is set by the originator of a query and copied into the response.

type: keyword

example: QUERY

The class of records being queried.

type: keyword

example: IN

The name being queried. If the name field contains non-printable characters (below 32 or above 126), those characters should be represented as escaped base 10 integers (\DDD). Back slashes and quotes should be escaped. Tabs, carriage returns, and line feeds should be converted to \t, \r, and \n respectively.

type: keyword

example: www.google.com

The highest registered domain, stripped of the subdomain. For example, the registered domain for "foo.google.com" is "google.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: google.com

The subdomain is all of the labels under the registered_domain. 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: www

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 google.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

The type of record being queried.

type: keyword

example: AAAA

Array containing all IPs seen in answers.data. The answers array can be difficult to use, because of the variety of data formats it can contain. Extracting all IP addresses seen in there to dns.resolved_ip makes it possible to index them as IP addresses, and makes them easier to visualize and query for.

type: ip

example: [10.10.10.10, 10.10.10.11]

The DNS response code.

type: keyword

example: NOERROR

The type of DNS event captured, query or answer. If your source of DNS events only gives you DNS queries, you should only create dns events of type dns.type:query. If your source of DNS events gives you answers as well, you should create one event per query (optionally as soon as the query is seen). And a second event containing all query details as well as an array of answers.

type: keyword

example: answer

ECS version this event conforms to. ecs.version is a required field and must exist in all events. When querying across multiple indices — which may conform to slightly different ECS versions — this field lets integrations adjust to the schema version of the events.

type: keyword

example: 1.0.0

required: True

Error code describing the error.

type: keyword

Unique identifier for the error.

type: keyword

Error message.

type: text

The stack trace of this error in plain text.

type: keyword

type: text

The type of the error, for example the class name of the exception.

type: keyword

example: java.lang.NullPointerException

The action captured by the event. This describes the information in the event. It is more specific than event.category. Examples are group-add, process-started, file-created. The value is normally defined by the implementer.

type: keyword

example: user-password-change

This is one of four ECS Categorization Fields, and indicates the second level in the ECS category hierarchy. event.category represents the "big buckets" of ECS categories. For example, filtering on event.category:process yields all events relating to process activity. This field is closely related to event.type, which is used as a subcategory. This field is an array. This will allow proper categorization of some events that fall in multiple categories.

type: keyword

example: authentication

Identification code for this event, if one exists. Some event sources use event codes to identify messages unambiguously, regardless of message language or wording adjustments over time. An example of this is the Windows Event ID.

type: keyword

example: 4648

event.created contains the date/time when the event was first read by an agent, or by your pipeline. This field is distinct from @timestamp in that @timestamp typically contain the time extracted from the original event. In most situations, these two timestamps will be slightly different. The difference can be used to calculate the delay between your source generating an event, and the time when your agent first processed it. This can be used to monitor your agent’s or pipeline’s ability to keep up with your event source. In case the two timestamps are identical, @timestamp should be used.

type: date

example: 2016-05-23 08:05:34.857000

Name of the dataset. If an event source publishes more than one type of log or events (e.g. access log, error log), the dataset is used to specify which one the event comes from. It’s recommended but not required to start the dataset name with the module name, followed by a dot, then the dataset name.

type: keyword

example: apache.access

Duration of the event in nanoseconds. If event.start and event.end are known this value should be the difference between the end and start time.

type: long

format: duration

event.end contains the date when the event ended or when the activity was last observed.

type: date

Hash (perhaps logstash fingerprint) of raw field to be able to demonstrate log integrity.

type: keyword

example: 123456789012345678901234567890ABCD

Unique ID to describe the event.

type: keyword

example: 8a4f500d

Timestamp when an event arrived in the central data store. This is different from @timestamp, which is when the event originally occurred. It’s also different from event.created, which is meant to capture the first time an agent saw the event. In normal conditions, assuming no tampering, the timestamps should chronologically look like this: @timestamp < event.created < event.ingested.

type: date

example: 2016-05-23 08:05:35.101000

This is one of four ECS Categorization Fields, and indicates the highest level in the ECS category hierarchy. event.kind gives high-level information about what type of information the event contains, without being specific to the contents of the event. For example, values of this field distinguish alert events from metric events. The value of this field can be used to inform how these kinds of events should be handled. They may warrant different retention, different access control, it may also help understand whether the data coming in at a regular interval or not.

type: keyword

example: alert

Name of the module this data is coming from. If your monitoring agent supports the concept of modules or plugins to process events of a given source (e.g. Apache logs), event.module should contain the name of this module.

type: keyword

example: apache

Raw text message of entire event. Used to demonstrate log integrity. This field is not indexed and doc_values are disabled. It cannot be searched, but it can be retrieved from _source.

type: keyword

example: Sep 19 08:26:10 host CEF:0|Security| threatmanager|1.0|100| worm successfully stopped|10|src=10.0.0.1 dst=2.1.2.2spt=1232

This is one of four ECS Categorization Fields, and indicates the lowest level in the ECS category hierarchy. event.outcome simply denotes whether the event represent a success or a failure. Note that not all events will have an associated outcome. For example, this field is generally not populated for metric events or events with event.type:info.

type: keyword

example: success

Source of the event. Event transports such as Syslog or the Windows Event Log typically mention the source of an event. It can be the name of the software that generated the event (e.g. Sysmon, httpd), or of a subsystem of the operating system (kernel, Microsoft-Windows-Security-Auditing).

type: keyword

example: kernel

Risk score or priority of the event (e.g. security solutions). Use your system’s original value here.

type: float

Normalized risk score or priority of the event, on a scale of 0 to 100. This is mainly useful if you use more than one system that assigns risk scores, and you want to see a normalized value across all systems.

type: float

Sequence number of the event. The sequence number is a value published by some event sources, to make the exact ordering of events unambiguous, regarless of the timestamp precision.

type: long

format: string

The numeric severity of the event according to your event source. What the different severity values mean can be different between sources and use cases. It’s up to the implementer to make sure severities are consistent across events from the same source. The Syslog severity belongs in log.syslog.severity.code. event.severity is meant to represent the severity according to the event source (e.g. firewall, IDS). If the event source does not publish its own severity, you may optionally copy the log.syslog.severity.code to event.severity.

type: long

example: 7

format: string

event.start contains the date when the event started or when the activity was first observed.

type: date

This field should be populated when the event’s timestamp does not include timezone information already (e.g. default Syslog timestamps). It’s optional otherwise. Acceptable timezone formats are: a canonical ID (e.g. "Europe/Amsterdam"), abbreviated (e.g. "EST") or an HH:mm differential (e.g. "-05:00").

type: keyword

This is one of four ECS Categorization Fields, and indicates the third level in the ECS category hierarchy. event.type represents a categorization "sub-bucket" that, when used along with the event.category field values, enables filtering events down to a level appropriate for single visualization. This field is an array. This will allow proper categorization of some events that fall in multiple event types.

type: keyword

Last time the file was accessed. Note that not all filesystems keep track of access time.

type: date

Array of file attributes. Attributes names will vary by platform. Here’s a non-exhaustive list of values that are expected in this field: archive, compressed, directory, encrypted, execute, hidden, read, readonly, system, write.

type: keyword

example: ["readonly", "system"]

File creation time. Note that not all filesystems store the creation time.

type: date

Last time the file attributes or metadata changed. Note that changes to the file content will update mtime. This implies ctime will be adjusted at the same time, since mtime is an attribute of the file.

type: date

Device that is the source of the file.

type: keyword

example: sda

Directory where the file is located. It should include the drive letter, when appropriate.

type: keyword

example: /home/alice

Drive letter where the file is located. This field is only relevant on Windows. The value should be uppercase, and not include the colon.

type: keyword

example: C

File extension.

type: keyword

example: png

Primary group ID (GID) of the file.

type: keyword

example: 1001

Primary group name of the file.

type: keyword

example: alice

MD5 hash.

type: keyword

SHA1 hash.

type: keyword

SHA256 hash.

type: keyword

SHA512 hash.

type: keyword

Inode representing the file in the filesystem.

type: keyword

example: 256383

Mode of the file in octal representation.

type: keyword

example: 0640

Last time the file content was modified.

type: date

Name of the file including the extension, without the directory.

type: keyword

example: example.png

File owner’s username.

type: keyword

example: alice

Full path to the file, including the file name. It should include the drive letter, when appropriate.

type: keyword

example: /home/alice/example.png

type: text

File size in bytes. Only relevant when file.type is "file".

type: long

example: 16384

Target path for symlinks.

type: keyword

type: text

File type (file, dir, or symlink).

type: keyword

example: file

The user ID (UID) or security identifier (SID) of the file owner.

type: keyword

example: 1001

City name.

type: keyword

example: Montreal

Name of the continent.

type: keyword

example: North America

Country ISO code.

type: keyword

example: CA

Country name.

type: keyword

example: Canada

Longitude and latitude.

type: geo_point

example: { "lon": -73.614830, "lat": 45.505918 }

User-defined description of a location, at the level of granularity they care about. Could be the name of their data centers, the floor number, if this describes a local physical entity, city names. Not typically used in automated geolocation.

type: keyword

example: boston-dc

Region ISO code.

type: keyword

example: CA-QC

Region name.

type: keyword

example: Quebec

Name of the directory the group is a member of. For example, an LDAP or Active Directory domain name.

type: keyword

Unique identifier for the group on the system/platform.

type: keyword

Name of the group.

type: keyword

MD5 hash.

type: keyword

SHA1 hash.

type: keyword

SHA256 hash.

type: keyword

SHA512 hash.

type: keyword

Operating system architecture.

type: keyword

example: x86_64

Name of the domain of which the host is a member. For example, on Windows this could be the host’s Active Directory domain or NetBIOS domain name. For Linux this could be the domain of the host’s LDAP provider.

type: keyword

example: CONTOSO

City name.

type: keyword

example: Montreal

Name of the continent.

type: keyword

example: North America

Country ISO code.

type: keyword

example: CA

Country name.

type: keyword

example: Canada

Longitude and latitude.

type: geo_point

example: { "lon": -73.614830, "lat": 45.505918 }

User-defined description of a location, at the level of granularity they care about. Could be the name of their data centers, the floor number, if this describes a local physical entity, city names. Not typically used in automated geolocation.

type: keyword

example: boston-dc

Region ISO code.

type: keyword

example: CA-QC

Region name.

type: keyword

example: Quebec

Hostname of the host. It normally contains what the hostname command returns on the host machine.

type: keyword

Unique host id. As hostname is not always unique, use values that are meaningful in your environment. Example: The current usage of beat.name.

type: keyword

Host ip address.

type: ip

Host mac address.

type: keyword

Name of the host. It can contain what hostname returns on Unix systems, the fully qualified domain name, or a name specified by the user. The sender decides which value to use.

type: keyword

OS family (such as redhat, debian, freebsd, windows).

type: keyword

example: debian

Operating system name, including the version or code name.

type: keyword

example: Mac OS Mojave

type: text

Operating system kernel version as a raw string.

type: keyword

example: 4.4.0-112-generic

Operating system name, without the version.

type: keyword

example: Mac OS X

type: text

Operating system platform (such centos, ubuntu, windows).

type: keyword

example: darwin

Operating system version as a raw string.

type: keyword

example: 10.14.1

Type of host. For Cloud providers this can be the machine type like t2.medium. If vm, this could be the container, for example, or other information meaningful in your environment.

type: keyword

Seconds the host has been up.

type: long

example: 1325

Name of the directory the user is a member of. For example, an LDAP or Active Directory domain name.

type: keyword

User email address.

type: keyword

User’s full name, if available.

type: keyword

example: Albert Einstein

type: text

Name of the directory the group is a member of. For example, an LDAP or Active Directory domain name.

type: keyword

Unique identifier for the group on the system/platform.

type: keyword

Name of the group.

type: keyword

Unique user hash to correlate information for a user in anonymized form. Useful if user.id or user.name contain confidential information and cannot be used.

type: keyword

One or multiple unique identifiers of the user.

type: keyword

Short name or login of the user.

type: keyword

example: albert

type: text

Size in bytes of the request body.

type: long

example: 887

format: bytes

The full HTTP request body.

type: keyword

example: Hello world

type: text

Total size in bytes of the request (body and headers).

type: long

example: 1437

format: bytes

HTTP request method. The field value must be normalized to lowercase for querying. See the documentation section "Implementing ECS".

type: keyword

example: get, post, put

Referrer for this HTTP request.

type: keyword

example: https://blog.example.com/

Size in bytes of the response body.

type: long

example: 887

format: bytes

The full HTTP response body.

type: keyword

example: Hello world

type: text

Total size in bytes of the response (body and headers).

type: long

example: 1437

format: bytes

HTTP response status code.

type: long

example: 404

format: string

HTTP version.

type: keyword

example: 1.1

Original log level of the log event. If the source of the event provides a log level or textual severity, this is the one that goes in log.level. If your source doesn’t specify one, you may put your event transport’s severity here (e.g. Syslog severity). Some examples are warn, err, i, informational.

type: keyword

example: error

The name of the logger inside an application. This is usually the name of the class which initialized the logger, or can be a custom name.

type: keyword

example: org.elasticsearch.bootstrap.Bootstrap

The line number of the file containing the source code which originated the log event.

type: integer

example: 42

The name of the file containing the source code which originated the log event. Note that this is not the name of the log file.

type: keyword

example: Bootstrap.java

The name of the function or method which originated the log event.

type: keyword

example: init

This is the original log message and contains the full log message before splitting it up in multiple parts. In contrast to the message field which can contain an extracted part of the log message, this field contains the original, full log message. It can have already some modifications applied like encoding or new lines removed to clean up the log message. This field is not indexed and doc_values are disabled so it can’t be queried but the value can be retrieved from _source.

type: keyword

example: Sep 19 08:26:10 localhost My log

The Syslog metadata of the event, if the event was transmitted via Syslog. Please see RFCs 5424 or 3164.

type: object

The Syslog numeric facility of the log event, if available. According to RFCs 5424 and 3164, this value should be an integer between 0 and 23.

type: long

example: 23

format: string

The Syslog text-based facility of the log event, if available.

type: keyword

example: local7

Syslog numeric priority of the event, if available. According to RFCs 5424 and 3164, the priority is 8 * facility + severity. This number is therefore expected to contain a value between 0 and 191.

type: long

example: 135

format: string

The Syslog numeric severity of the log event, if available. If the event source publishing via Syslog provides a different numeric severity value (e.g. firewall, IDS), your source’s numeric severity should go to event.severity. If the event source does not specify a distinct severity, you can optionally copy the Syslog severity to event.severity.

type: long

example: 3

The Syslog numeric severity of the log event, if available. If the event source publishing via Syslog provides a different severity value (e.g. firewall, IDS), your source’s text severity should go to log.level. If the event source does not specify a distinct severity, you can optionally copy the Syslog severity to log.level.

type: keyword

example: Error

A name given to an application level protocol. This can be arbitrarily assigned for things like microservices, but also apply to things like skype, icq, facebook, twitter. This would be used in situations where the vendor or service can be decoded such as from the source/dest IP owners, ports, or wire format. The field value must be normalized to lowercase for querying. See the documentation section "Implementing ECS".

type: keyword

example: aim

Total bytes transferred in both directions. If source.bytes and destination.bytes are known, network.bytes is their sum.

type: long

example: 368

format: bytes

A hash of source and destination IPs and ports, as well as the protocol used in a communication. This is a tool-agnostic standard to identify flows. Learn more at https://github.com/corelight/community-id-spec.

type: keyword

example: 1:hO+sN4H+MG5MY/8hIrXPqc4ZQz0=

Direction of the network traffic. Recommended values are: * inbound * outbound * internal * external * unknown

When mapping events from a host-based monitoring context, populate this field from the host’s point of view. When mapping events from a network or perimeter-based monitoring context, populate this field from the point of view of your network perimeter.

type: keyword

example: inbound

Host IP address when the source IP address is the proxy.

type: ip

example: 192.1.1.2

IANA Protocol Number (https://www.iana.org/assignments/protocol-numbers/protocol-numbers.xhtml). Standardized list of protocols. This aligns well with NetFlow and sFlow related logs which use the IANA Protocol Number.

type: keyword

example: 6

Name given by operators to sections of their network.

type: keyword

example: Guest Wifi

Total packets transferred in both directions. If source.packets and destination.packets are known, network.packets is their sum.

type: long

example: 24

L7 Network protocol name. ex. http, lumberjack, transport protocol. The field value must be normalized to lowercase for querying. See the documentation section "Implementing ECS".

type: keyword

example: http

Same as network.iana_number, but instead using the Keyword name of the transport layer (udp, tcp, ipv6-icmp, etc.) The field value must be normalized to lowercase for querying. See the documentation section "Implementing ECS".

type: keyword

example: tcp

In the OSI Model this would be the Network Layer. ipv4, ipv6, ipsec, pim, etc The field value must be normalized to lowercase for querying. See the documentation section "Implementing ECS".

type: keyword

example: ipv4

City name.

type: keyword

example: Montreal

Name of the continent.

type: keyword

example: North America

Country ISO code.

type: keyword

example: CA

Country name.

type: keyword

example: Canada

Longitude and latitude.

type: geo_point

example: { "lon": -73.614830, "lat": 45.505918 }

User-defined description of a location, at the level of granularity they care about. Could be the name of their data centers, the floor number, if this describes a local physical entity, city names. Not typically used in automated geolocation.

type: keyword

example: boston-dc

Region ISO code.

type: keyword

example: CA-QC

Region name.

type: keyword

example: Quebec

Hostname of the observer.

type: keyword

IP address of the observer.

type: ip

MAC address of the observer

type: keyword

Custom name of the observer. This is a name that can be given to an observer. This can be helpful for example if multiple firewalls of the same model are used in an organization. If no custom name is needed, the field can be left empty.

type: keyword

example: 1_proxySG

OS family (such as redhat, debian, freebsd, windows).

type: keyword

example: debian

Operating system name, including the version or code name.

type: keyword

example: Mac OS Mojave

type: text

Operating system kernel version as a raw string.

type: keyword

example: 4.4.0-112-generic

Operating system name, without the version.

type: keyword

example: Mac OS X

type: text

Operating system platform (such centos, ubuntu, windows).

type: keyword

example: darwin

Operating system version as a raw string.

type: keyword

example: 10.14.1

The product name of the observer.

type: keyword

example: s200

Observer serial number.

type: keyword

The type of the observer the data is coming from. There is no predefined list of observer types. Some examples are forwarder, firewall, ids, ips, proxy, poller, sensor, APM server.

type: keyword

example: firewall

Vendor name of the observer.

type: keyword

example: Symantec

Observer version.

type: keyword

Unique identifier for the organization.

type: keyword

Organization name.

type: keyword

type: text

OS family (such as redhat, debian, freebsd, windows).

type: keyword

example: debian

Operating system name, including the version or code name.

type: keyword

example: Mac OS Mojave

type: text

Operating system kernel version as a raw string.

type: keyword

example: 4.4.0-112-generic

Operating system name, without the version.

type: keyword

example: Mac OS X

type: text

Operating system platform (such centos, ubuntu, windows).

type: keyword

example: darwin

Operating system version as a raw string.

type: keyword

example: 10.14.1

Package architecture.

type: keyword

example: x86_64

Additional information about the build version of the installed package. For example use the commit SHA of a non-released package.

type: keyword

example: 36f4f7e89dd61b0988b12ee000b98966867710cd

Checksum of the installed package for verification.

type: keyword

example: 68b329da9893e34099c7d8ad5cb9c940

Description of the package.

type: keyword

example: Open source programming language to build simple/reliable/efficient software.

Indicating how the package was installed, e.g. user-local, global.

type: keyword

example: global

Time when package was installed.

type: date

License under which the package was released. Use a short name, e.g. the license identifier from SPDX License List where possible (https://spdx.org/licenses/).

type: keyword

example: Apache License 2.0

Package name

type: keyword

example: go

Path where the package is installed.

type: keyword

example: /usr/local/Cellar/go/1.12.9/

Home page or reference URL of the software in this package, if available.

type: keyword

example: https://golang.org

Package size in bytes.

type: long

example: 62231

format: string

Type of package. This should contain the package file type, rather than the package manager name. Examples: rpm, dpkg, brew, npm, gem, nupkg, jar.

type: keyword

example: rpm

Package version

type: keyword

example: 1.12.9

Array of process arguments, starting with the absolute path to the executable. May be filtered to protect sensitive information.

type: keyword

example: [/usr/bin/ssh, -l, user, 10.0.0.16]

Length of the process.args array. This field can be useful for querying or performing bucket analysis on how many arguments were provided to start a process. More arguments may be an indication of suspicious activity.

type: long

example: 4

Full command line that started the process, including the absolute path to the executable, and all arguments. Some arguments may be filtered to protect sensitive information.

type: keyword

example: /usr/bin/ssh -l user 10.0.0.16

type: text

Absolute path to the process executable.

type: keyword

example: /usr/bin/ssh

type: text

The exit code of the process, if this is a termination event. The field should be absent if there is no exit code for the event (e.g. process start).

type: long

example: 137

MD5 hash.

type: keyword

SHA1 hash.

type: keyword

SHA256 hash.

type: keyword

SHA512 hash.

type: keyword

Process name. Sometimes called program name or similar.

type: keyword

example: ssh

type: text

Array of process arguments. May be filtered to protect sensitive information.

type: keyword

example: [ssh, -l, user, 10.0.0.16]

Length of the process.args array. This field can be useful for querying or performing bucket analysis on how many arguments were provided to start a process. More arguments may be an indication of suspicious activity.

type: long

example: 4

Full command line that started the process, including the absolute path to the executable, and all arguments. Some arguments may be filtered to protect sensitive information.

type: keyword

example: /usr/bin/ssh -l user 10.0.0.16

type: text

Absolute path to the process executable.

type: keyword

example: /usr/bin/ssh

type: text

The exit code of the process, if this is a termination event. The field should be absent if there is no exit code for the event (e.g. process start).

type: long

example: 137

Process name. Sometimes called program name or similar.

type: keyword

example: ssh

type: text

Identifier of the group of processes the process belongs to.

type: long

format: string

Process id.

type: long

example: 4242

format: string

Parent process' pid.

type: long

example: 4241

format: string

The time the process started.

type: date

example: 2016-05-23T08:05:34.853Z

Thread ID.

type: long

example: 4242

format: string

Thread name.

type: keyword

example: thread-0

Process title. The proctitle, some times the same as process name. Can also be different: for example a browser setting its title to the web page currently opened.

type: keyword

type: text

Seconds the process has been up.

type: long

example: 1325

The working directory of the process.

type: keyword

example: /home/alice

type: text

Identifier of the group of processes the process belongs to.

type: long

format: string

Process id.

type: long

example: 4242

format: string

Parent process' pid.

type: long

example: 4241

format: string

The time the process started.

type: date

example: 2016-05-23T08:05:34.853Z

Thread ID.

type: long

example: 4242

format: string

Thread name.

type: keyword

example: thread-0

Process title. The proctitle, some times the same as process name. Can also be different: for example a browser setting its title to the web page currently opened.

type: keyword

type: text

Seconds the process has been up.

type: long

example: 1325

The working directory of the process.

type: keyword

example: /home/alice

type: text

Original bytes written with base64 encoding. For Windows registry operations, such as SetValueEx and RegQueryValueEx, this corresponds to the data pointed by lp_data. This is optional but provides better recoverability and should be populated for REG_BINARY encoded values.

type: keyword

example: ZQBuAC0AVQBTAAAAZQBuAAAAAAA=

Content when writing string types. Populated as an array when writing string data to the registry. For single string registry types (REG_SZ, REG_EXPAND_SZ), this should be an array with one string. For sequences of string with REG_MULTI_SZ, this array will be variable length. For numeric data, such as REG_DWORD and REG_QWORD, this should be populated with the decimal representation (e.g "1").

type: keyword

example: ["C:\rta\red_ttp\bin\myapp.exe"]

Standard registry type for encoding contents

type: keyword

example: REG_SZ

Abbreviated name for the hive.

type: keyword

example: HKLM

Hive-relative path of keys.

type: keyword

example: SOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File Execution Options\winword.exe

Full path, including hive, key and value

type: keyword

example: HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File Execution Options\winword.exe\Debugger

Name of the value written.

type: keyword

example: Debugger

All of the IPs seen on your event.

type: ip

All the user names seen on your event.

type: keyword

A categorization value keyword used by the entity using the rule for detection of this event.

type: keyword

example: Attempted Information Leak

The description of the rule generating the event.

type: keyword

example: Block requests to public DNS over HTTPS / TLS protocols

A rule ID that is unique within the scope of an agent, observer, or other entity using the rule for detection of this event.

type: keyword

example: 101

The name of the rule or signature generating the event.

type: keyword

example: BLOCK_DNS_over_TLS

Reference URL to additional information about the rule used to generate this event. The URL can point to the vendor’s documentation about the rule. If that’s not available, it can also be a link to a more general page describing this type of alert.

type: keyword

example: https://en.wikipedia.org/wiki/DNS_over_TLS

Name of the ruleset, policy, group, or parent category in which the rule used to generate this event is a member.

type: keyword

example: Standard_Protocol_Filters

A rule ID that is unique within the scope of a set or group of agents, observers, or other entities using the rule for detection of this event.

type: keyword

example: 1100110011

The version / revision of the rule being used for analysis.

type: keyword

example: 1.1

Some event server 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

Unique number allocated to the autonomous system. The autonomous system number (ASN) uniquely identifies each network on the Internet.

type: long

example: 15169

Organization name.

type: keyword

example: Google LLC

type: text

Bytes sent from the server to the client.

type: long

example: 184

format: bytes

Server domain.

type: keyword

City name.

type: keyword

example: Montreal

Name of the continent.

type: keyword

example: North America

Country ISO code.

type: keyword

example: CA

Country name.

type: keyword

example: Canada

Longitude and latitude.

type: geo_point

example: { "lon": -73.614830, "lat": 45.505918 }

User-defined description of a location, at the level of granularity they care about. Could be the name of their data centers, the floor number, if this describes a local physical entity, city names. Not typically used in automated geolocation.

type: keyword

example: boston-dc

Region ISO code.

type: keyword

example: CA-QC

Region name.

type: keyword

example: Quebec

IP address of the server. Can be one or multiple IPv4 or IPv6 addresses.

type: ip

MAC address of the server.

type: keyword

Translated ip of destination based NAT sessions (e.g. internet to private DMZ) Typically used with load balancers, firewalls, or routers.

type: ip

Translated port of destination based NAT sessions (e.g. internet to private DMZ) Typically used with load balancers, firewalls, or routers.

type: long

format: string

Packets sent from the server to the client.

type: long

example: 12

Port of the server.

type: long

format: string

The highest registered server domain, stripped of the subdomain. For example, the registered domain for "foo.google.com" is "google.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: google.com

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 google.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

Name of the directory the user is a member of. For example, an LDAP or Active Directory domain name.

type: keyword

User email address.

type: keyword

User’s full name, if available.

type: keyword

example: Albert Einstein

type: text

Name of the directory the group is a member of. For example, an LDAP or Active Directory domain name.

type: keyword

Unique identifier for the group on the system/platform.

type: keyword

Name of the group.

type: keyword

Unique user hash to correlate information for a user in anonymized form. Useful if user.id or user.name contain confidential information and cannot be used.

type: keyword

One or multiple unique identifiers of the user.

type: keyword

Short name or login of the user.

type: keyword

example: albert

type: text

Ephemeral identifier of this service (if one exists). This id normally changes across restarts, but service.id does not.

type: keyword

example: 8a4f500f

Unique identifier of the running service. If the service is comprised of many nodes, the service.id should be the same for all nodes. This id should uniquely identify the service. This makes it possible to correlate logs and metrics for one specific service, no matter which particular node emitted the event. Note that if you need to see the events from one specific host of the service, you should filter on that host.name or host.id instead.

type: keyword

example: d37e5ebfe0ae6c4972dbe9f0174a1637bb8247f6

Name of the service data is collected from. The name of the service is normally user given. This allows for distributed services that run on multiple hosts to correlate the related instances based on the name. In the case of Elasticsearch the service.name could contain the cluster name. For Beats the service.name is by default a copy of the service.type field if no name is specified.

type: keyword

example: elasticsearch-metrics

Name of a service node. This allows for two nodes of the same service running on the same host to be differentiated. Therefore, service.node.name should typically be unique across nodes of a given service. In the case of Elasticsearch, the service.node.name could contain the unique node name within the Elasticsearch cluster. In cases where the service doesn’t have the concept of a node name, the host name or container name can be used to distinguish running instances that make up this service. If those do not provide uniqueness (e.g. multiple instances of the service running on the same host) - the node name can be manually set.

type: keyword

example: instance-0000000016

Current state of the service.

type: keyword

The type of the service data is collected from. The type can be used to group and correlate logs and metrics from one service type. Example: If logs or metrics are collected from Elasticsearch, service.type would be elasticsearch.

type: keyword

example: elasticsearch

Version of the service the data was collected from. This allows to look at a data set only for a specific version of a service.

type: keyword

example: 3.2.4

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

Unique number allocated to the autonomous system. The autonomous system number (ASN) uniquely identifies each network on the Internet.

type: long

example: 15169

Organization name.

type: keyword

example: Google LLC

type: text

Bytes sent from the source to the destination.

type: long

example: 184

format: bytes

Source domain.

type: keyword

City name.

type: keyword

example: Montreal

Name of the continent.

type: keyword

example: North America

Country ISO code.

type: keyword

example: CA

Country name.

type: keyword

example: Canada

Longitude and latitude.

type: geo_point

example: { "lon": -73.614830, "lat": 45.505918 }

User-defined description of a location, at the level of granularity they care about. Could be the name of their data centers, the floor number, if this describes a local physical entity, city names. Not typically used in automated geolocation.

type: keyword

example: boston-dc

Region ISO code.

type: keyword

example: CA-QC

Region name.

type: keyword

example: Quebec

IP address of the source. Can be one or multiple IPv4 or IPv6 addresses.

type: ip

MAC address of the source.

type: keyword

Translated ip of source based NAT sessions (e.g. internal client to internet) Typically connections traversing load balancers, firewalls, or routers.

type: ip

Translated port of source based NAT sessions. (e.g. internal client to internet) Typically used with load balancers, firewalls, or routers.

type: long

format: string

Packets sent from the source to the destination.

type: long

example: 12

Port of the source.

type: long

format: string

The highest registered source domain, stripped of the subdomain. For example, the registered domain for "foo.google.com" is "google.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: google.com

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 google.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

Name of the directory the user is a member of. For example, an LDAP or Active Directory domain name.

type: keyword

User email address.

type: keyword

User’s full name, if available.

type: keyword

example: Albert Einstein

type: text

Name of the directory the group is a member of. For example, an LDAP or Active Directory domain name.

type: keyword

Unique identifier for the group on the system/platform.

type: keyword

Name of the group.

type: keyword

Unique user hash to correlate information for a user in anonymized form. Useful if user.id or user.name contain confidential information and cannot be used.

type: keyword

One or multiple unique identifiers of the user.

type: keyword

Short name or login of the user.

type: keyword

example: albert

type: text

Name of the threat framework used to further categorize and classify the tactic and technique of the reported threat. Framework classification can be provided by detecting systems, evaluated at ingest time, or retrospectively tagged to events.

type: keyword

example: MITRE ATT&CK

The id of tactic used by this threat. You can use the Mitre ATT&CK Matrix Tactic categorization, for example. (ex. https://attack.mitre.org/tactics/TA0040/ )

type: keyword

example: TA0040

Name of the type of tactic used by this threat. You can use the Mitre ATT&CK Matrix Tactic categorization, for example. (ex. https://attack.mitre.org/tactics/TA0040/ )

type: keyword

example: impact

The reference url of tactic used by this threat. You can use the Mitre ATT&CK Matrix Tactic categorization, for example. (ex. https://attack.mitre.org/tactics/TA0040/ )

type: keyword

example: https://attack.mitre.org/tactics/TA0040/

The id of technique used by this tactic. You can use the Mitre ATT&CK Matrix Tactic categorization, for example. (ex. https://attack.mitre.org/techniques/T1499/ )

type: keyword

example: T1499

The name of technique used by this tactic. You can use the Mitre ATT&CK Matrix Tactic categorization, for example. (ex. https://attack.mitre.org/techniques/T1499/ )

type: keyword

example: endpoint denial of service

type: text

The reference url of technique used by this tactic. You can use the Mitre ATT&CK Matrix Tactic categorization, for example. (ex. https://attack.mitre.org/techniques/T1499/ )

type: keyword

example: https://attack.mitre.org/techniques/T1499/

String indicating the cipher used during the current connection.

type: keyword

example: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256

PEM-encoded stand-alone certificate offered by the client. This is usually mutually-exclusive of client.certificate_chain since this value also exists in that list.

type: keyword

example: MII…​

Array of PEM-encoded certificates that make up the certificate chain offered by the client. This is usually mutually-exclusive of client.certificate since that value should be the first certificate in the chain.

type: keyword

example: [MII…​, MII…​]

Certificate fingerprint using the MD5 digest of DER-encoded version of certificate offered by the client. For consistency with other hash values, this value should be formatted as an uppercase hash.

type: keyword

example: 0F76C7F2C55BFD7D8E8B8F4BFBF0C9EC

Certificate fingerprint using the SHA1 digest of DER-encoded version of certificate offered by the client. For consistency with other hash values, this value should be formatted as an uppercase hash.

type: keyword

example: 9E393D93138888D288266C2D915214D1D1CCEB2A

Certificate fingerprint using the SHA256 digest of DER-encoded version of certificate offered by the client. For consistency with other hash values, this value should be formatted as an uppercase hash.

type: keyword

example: 0687F666A054EF17A08E2F2162EAB4CBC0D265E1D7875BE74BF3C712CA92DAF0

Distinguished name of subject of the issuer of the x.509 certificate presented by the client.

type: keyword

example: CN=MyDomain Root CA, OU=Infrastructure Team, DC=mydomain, DC=com

A hash that identifies clients based on how they perform an SSL/TLS handshake.

type: keyword

example: d4e5b18d6b55c71272893221c96ba240

Date/Time indicating when client certificate is no longer considered valid.

type: date

example: 2021-01-01T00:00:00.000Z

Date/Time indicating when client certificate is first considered valid.

type: date

example: 1970-01-01T00:00:00.000Z

Also called an SNI, this tells the server which hostname to which the client is attempting to connect. When this value is available, it should get copied to destination.domain.

type: keyword

example: www.elastic.co

Distinguished name of subject of the x.509 certificate presented by the client.

type: keyword

example: CN=myclient, OU=Documentation Team, DC=mydomain, DC=com

Array of ciphers offered by the client during the client hello.

type: keyword

example: [TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384, TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384, …​]

String indicating the curve used for the given cipher, when applicable.

type: keyword

example: secp256r1

Boolean flag indicating if the TLS negotiation was successful and transitioned to an encrypted tunnel.

type: boolean

String indicating the protocol being tunneled. Per the values in the IANA registry (https://www.iana.org/assignments/tls-extensiontype-values/tls-extensiontype-values.xhtml#alpn-protocol-ids), this string should be lower case.

type: keyword

example: http/1.1

Boolean flag indicating if this TLS connection was resumed from an existing TLS negotiation.

type: boolean

PEM-encoded stand-alone certificate offered by the server. This is usually mutually-exclusive of server.certificate_chain since this value also exists in that list.

type: keyword

example: MII…​

Array of PEM-encoded certificates that make up the certificate chain offered by the server. This is usually mutually-exclusive of server.certificate since that value should be the first certificate in the chain.

type: keyword

example: [MII…​, MII…​]

Certificate fingerprint using the MD5 digest of DER-encoded version of certificate offered by the server. For consistency with other hash values, this value should be formatted as an uppercase hash.

type: keyword

example: 0F76C7F2C55BFD7D8E8B8F4BFBF0C9EC

Certificate fingerprint using the SHA1 digest of DER-encoded version of certificate offered by the server. For consistency with other hash values, this value should be formatted as an uppercase hash.

type: keyword

example: 9E393D93138888D288266C2D915214D1D1CCEB2A

Certificate fingerprint using the SHA256 digest of DER-encoded version of certificate offered by the server. For consistency with other hash values, this value should be formatted as an uppercase hash.

type: keyword

example: 0687F666A054EF17A08E2F2162EAB4CBC0D265E1D7875BE74BF3C712CA92DAF0

Subject of the issuer of the x.509 certificate presented by the server.

type: keyword

example: CN=MyDomain Root CA, OU=Infrastructure Team, DC=mydomain, DC=com

A hash that identifies servers based on how they perform an SSL/TLS handshake.

type: keyword

example: 394441ab65754e2207b1e1b457b3641d

Timestamp indicating when server certificate is no longer considered valid.

type: date

example: 2021-01-01T00:00:00.000Z

Timestamp indicating when server certificate is first considered valid.

type: date

example: 1970-01-01T00:00:00.000Z

Subject of the x.509 certificate presented by the server.

type: keyword

example: CN=www.mydomain.com, OU=Infrastructure Team, DC=mydomain, DC=com

Numeric part of the version parsed from the original string.

type: keyword

example: 1.2

Normalized lowercase protocol name parsed from original string.

type: keyword

example: tls

Unique identifier of the trace. A trace groups multiple events like transactions that belong together. For example, a user request handled by multiple inter-connected services.

type: keyword

example: 4bf92f3577b34da6a3ce929d0e0e4736

Unique identifier of the transaction. A transaction is the highest level of work measured within a service, such as a request to a server.

type: keyword

example: 00f067aa0ba902b7

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 domain field.

type: keyword

example: www.elastic.co

The field contains the file extension from the original request url. 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".

type: keyword

example: png

Portion of the url after the #, such as "top". The # is not part of the fragment.

type: keyword

If full URLs are important to your use case, they should be stored in url.full, whether this field is reconstructed or present in the event source.

type: keyword

example: https://www.elastic.co:443/search?q=elasticsearch#top

type: text

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: keyword

example: https://www.elastic.co:443/search?q=elasticsearch#top or /search?q=elasticsearch

type: text

Password of the request.

type: keyword

Path of the request, such as "/search".

type: keyword

Port of the request, such as 443.

type: long

example: 443

format: string

The query field describes the query string of the request, such as "q=elasticsearch". The ? is excluded from the query string. If a URL contains no ?, there is no query field. If there is a ? but no query, the query field exists with an empty string. The exists query can be used to differentiate between the two cases.

type: keyword

The highest registered url domain, stripped of the subdomain. For example, the registered domain for "foo.google.com" is "google.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: google.com

Scheme of the request, such as "https". Note: The : is not part of the scheme.

type: keyword

example: https

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 google.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

Username of the request.

type: keyword

Name of the directory the user is a member of. For example, an LDAP or Active Directory domain name.

type: keyword

User email address.

type: keyword

User’s full name, if available.

type: keyword

example: Albert Einstein

type: text

Name of the directory the group is a member of. For example, an LDAP or Active Directory domain name.

type: keyword

Unique identifier for the group on the system/platform.

type: keyword

Name of the group.

type: keyword

Unique user hash to correlate information for a user in anonymized form. Useful if user.id or user.name contain confidential information and cannot be used.

type: keyword

One or multiple unique identifiers of the user.

type: keyword

Short name or login of the user.

type: keyword

example: albert

type: text

Name of the device.

type: keyword

example: iPhone

Name of the user agent.

type: keyword

example: Safari

Unparsed user_agent string.

type: keyword

example: Mozilla/5.0 (iPhone; CPU iPhone OS 12_1 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/12.0 Mobile/15E148 Safari/604.1

type: text

OS family (such as redhat, debian, freebsd, windows).

type: keyword

example: debian

Operating system name, including the version or code name.

type: keyword

example: Mac OS Mojave

type: text

Operating system kernel version as a raw string.

type: keyword

example: 4.4.0-112-generic

Operating system name, without the version.

type: keyword

example: Mac OS X

type: text

Operating system platform (such centos, ubuntu, windows).

type: keyword

example: darwin

Operating system version as a raw string.

type: keyword

example: 10.14.1

Version of the user agent.

type: keyword

example: 12.0

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 (Qualys vulnerability categories) This field must be an array.

type: keyword

example: ["Firewall"]

The classification of the vulnerability scoring system. For example (https://www.first.org/cvss/)

type: keyword

example: CVSS

The description of the vulnerability that provides additional context of the vulnerability. For example (Common Vulnerabilities and Exposure CVE description)

type: keyword

example: In macOS before 2.12.6, there is a vulnerability in the RPC…​

type: text

The type of identifier used for this vulnerability. For example (https://cve.mitre.org/about/)

type: keyword

example: CVE

The identification (ID) is the number portion of a vulnerability entry. It includes a unique identification number for the vulnerability. For example (Common Vulnerabilities and Exposure CVE ID

type: keyword

example: CVE-2019-00001

A resource that provides additional information, context, and mitigations for the identified vulnerability.

type: keyword

example: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-6111

The report or scan identification number.

type: keyword

example: 20191018.0001

The name of the vulnerability scanner vendor.

type: keyword

example: Tenable

Scores can range from 0.0 to 10.0, with 10.0 being the most severe. Base scores cover an assessment for exploitability metrics (attack vector, complexity, privileges, and user interaction), impact metrics (confidentiality, integrity, and availability), and scope. For example (https://www.first.org/cvss/specification-document)

type: float

example: 5.5

Scores can range from 0.0 to 10.0, with 10.0 being the most severe. Environmental scores cover an assessment for any modified Base metrics, confidentiality, integrity, and availability requirements. For example (https://www.first.org/cvss/specification-document)

type: float

example: 5.5

Scores can range from 0.0 to 10.0, with 10.0 being the most severe. Temporal scores cover an assessment for code maturity, remediation level, and confidence. For example (https://www.first.org/cvss/specification-document)

type: float

The National Vulnerability Database (NVD) provides qualitative severity rankings of "Low", "Medium", and "High" for CVSS v2.0 base score ranges in addition to the severity ratings for CVSS v3.0 as they are defined in the CVSS v3.0 specification. CVSS is owned and managed by FIRST.Org, Inc. (FIRST), a US-based non-profit organization, whose mission is to help computer security incident response teams across the world. For example (https://nvd.nist.gov/vuln-metrics/cvss)

type: keyword

example: 2.0

The severity of the vulnerability can help with metrics and internal prioritization regarding remediation. For example (https://nvd.nist.gov/vuln-metrics/cvss)

type: keyword

example: Critical