diff --git a/internal/version/index.go b/internal/version/index.go index fe8c93a..5a6471b 100644 --- a/internal/version/index.go +++ b/internal/version/index.go @@ -19,7 +19,7 @@ package version var ( - Latest = v8_10_0 + Latest = v8_11_0 Index = map[string]map[string]*Field{ "1.0": v1_0_1, "1.0.1": v1_0_1, @@ -77,8 +77,10 @@ var ( "8.8.0": v8_8_0, "8.9": v8_9_0, "8.9.0": v8_9_0, - "8": v8_10_0, "8.10": v8_10_0, "8.10.0": v8_10_0, + "8": v8_11_0, + "8.11": v8_11_0, + "8.11.0": v8_11_0, } ) diff --git a/internal/version/v8_11_0.go b/internal/version/v8_11_0.go new file mode 100644 index 0000000..e6edd30 --- /dev/null +++ b/internal/version/v8_11_0.go @@ -0,0 +1,1681 @@ +// Licensed to Elasticsearch B.V. under one or more contributor +// license agreements. See the NOTICE file distributed with +// this work for additional information regarding copyright +// ownership. Elasticsearch B.V. licenses this file to you under +// the Apache License, Version 2.0 (the "License"); you may +// not use this file except in compliance with the License. +// You may obtain a copy of the License at +// +// http://www.apache.org/licenses/LICENSE-2.0 +// +// Unless required by applicable law or agreed to in writing, +// software distributed under the License is distributed on an +// "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY +// KIND, either express or implied. See the License for the +// specific language governing permissions and limitations +// under the License. + +// Code generated by generator, DO NOT EDIT. +package version + +var v8_11_0 = map[string]*Field{ + "@timestamp": {Name: "@timestamp", DataType: "date", Description: "Date/time when the event originated.\nThis is the date/time extracted from the event, typically representing when the event was generated by the source.\nIf the event source has no original timestamp, this value is typically populated by the first time the event was received by the pipeline.\nRequired field for all events."}, + "agent.build.original": {Name: "agent.build.original", DataType: "keyword", Description: "Extended build information for the agent.\nThis field is intended to contain any build information that a data source may provide, no specific formatting is required."}, + "agent.ephemeral_id": {Name: "agent.ephemeral_id", DataType: "keyword", Description: "Ephemeral identifier of this agent (if one exists).\nThis id normally changes across restarts, but `agent.id` does not."}, + "agent.id": {Name: "agent.id", DataType: "keyword", Description: "Unique identifier of this agent (if one exists).\nExample: For Beats this would be beat.id."}, + "agent.name": {Name: "agent.name", DataType: "keyword", Description: "Custom name of the agent.\nThis 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."}, + "agent.type": {Name: "agent.type", DataType: "keyword", Description: "Type of the agent.\nThe agent type always stays 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."}, + "agent.version": {Name: "agent.version", DataType: "keyword", Description: "Version of the agent."}, + "client.address": {Name: "client.address", DataType: "keyword", Description: "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.\nThen it should be duplicated to `.ip` or `.domain`, depending on which one it is."}, + "client.as.number": {Name: "client.as.number", DataType: "long", Description: "Unique number allocated to the autonomous system. The autonomous system number (ASN) uniquely identifies each network on the Internet."}, + "client.as.organization.name": {Name: "client.as.organization.name", DataType: "keyword", Description: "Organization name."}, + "client.bytes": {Name: "client.bytes", DataType: "long", Description: "Bytes sent from the client to the server."}, + "client.domain": {Name: "client.domain", DataType: "keyword", Description: "The domain name of the client system.\nThis value may be a host name, a fully qualified domain name, or another host naming format. The value may derive from the original event or be added from enrichment."}, + "client.geo.city_name": {Name: "client.geo.city_name", DataType: "keyword", Description: "City name."}, + "client.geo.continent_code": {Name: "client.geo.continent_code", DataType: "keyword", Description: "Two-letter code representing continent's name."}, + "client.geo.continent_name": {Name: "client.geo.continent_name", DataType: "keyword", Description: "Name of the continent."}, + "client.geo.country_iso_code": {Name: "client.geo.country_iso_code", DataType: "keyword", Description: "Country ISO code."}, + "client.geo.country_name": {Name: "client.geo.country_name", DataType: "keyword", Description: "Country name."}, + "client.geo.location": {Name: "client.geo.location", DataType: "geo_point", Description: "Longitude and latitude."}, + "client.geo.name": {Name: "client.geo.name", DataType: "keyword", Description: "User-defined description of a location, at the level of granularity they care about.\nCould be the name of their data centers, the floor number, if this describes a local physical entity, city names.\nNot typically used in automated geolocation."}, + "client.geo.postal_code": {Name: "client.geo.postal_code", DataType: "keyword", Description: "Postal code associated with the location.\nValues appropriate for this field may also be known as a postcode or ZIP code and will vary widely from country to country."}, + "client.geo.region_iso_code": {Name: "client.geo.region_iso_code", DataType: "keyword", Description: "Region ISO code."}, + "client.geo.region_name": {Name: "client.geo.region_name", DataType: "keyword", Description: "Region name."}, + "client.geo.timezone": {Name: "client.geo.timezone", DataType: "keyword", Description: "The time zone of the location, such as IANA time zone name."}, + "client.ip": {Name: "client.ip", DataType: "ip", Description: "IP address of the client (IPv4 or IPv6)."}, + "client.mac": {Name: "client.mac", DataType: "keyword", Pattern: "^[A-F0-9]{2}(-[A-F0-9]{2}){5,}$", Description: "MAC address of the client.\nThe notation format from RFC 7042 is suggested: Each octet (that is, 8-bit byte) is represented by two [uppercase] hexadecimal digits giving the value of the octet as an unsigned integer. Successive octets are separated by a hyphen."}, + "client.nat.ip": {Name: "client.nat.ip", DataType: "ip", Description: "Translated IP of source based NAT sessions (e.g. internal client to internet).\nTypically connections traversing load balancers, firewalls, or routers."}, + "client.nat.port": {Name: "client.nat.port", DataType: "long", Description: "Translated port of source based NAT sessions (e.g. internal client to internet).\nTypically connections traversing load balancers, firewalls, or routers."}, + "client.packets": {Name: "client.packets", DataType: "long", Description: "Packets sent from the client to the server."}, + "client.port": {Name: "client.port", DataType: "long", Description: "Port of the client."}, + "client.registered_domain": {Name: "client.registered_domain", DataType: "keyword", Description: "The highest registered client domain, stripped of the subdomain.\nFor example, the registered domain for \"foo.example.com\" is \"example.com\".\nThis 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\"."}, + "client.subdomain": {Name: "client.subdomain", DataType: "keyword", Description: "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.\nFor 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."}, + "client.top_level_domain": {Name: "client.top_level_domain", DataType: "keyword", Description: "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\".\nThis 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\"."}, + "client.user.domain": {Name: "client.user.domain", DataType: "keyword", Description: "Name of the directory the user is a member of.\nFor example, an LDAP or Active Directory domain name."}, + "client.user.email": {Name: "client.user.email", DataType: "keyword", Description: "User email address."}, + "client.user.full_name": {Name: "client.user.full_name", DataType: "keyword", Description: "User's full name, if available."}, + "client.user.group.domain": {Name: "client.user.group.domain", DataType: "keyword", Description: "Name of the directory the group is a member of.\nFor example, an LDAP or Active Directory domain name."}, + "client.user.group.id": {Name: "client.user.group.id", DataType: "keyword", Description: "Unique identifier for the group on the system/platform."}, + "client.user.group.name": {Name: "client.user.group.name", DataType: "keyword", Description: "Name of the group."}, + "client.user.hash": {Name: "client.user.hash", DataType: "keyword", Description: "Unique user hash to correlate information for a user in anonymized form.\nUseful if `user.id` or `user.name` contain confidential information and cannot be used."}, + "client.user.id": {Name: "client.user.id", DataType: "keyword", Description: "Unique identifier of the user."}, + "client.user.name": {Name: "client.user.name", DataType: "keyword", Description: "Short name or login of the user."}, + "client.user.roles": {Name: "client.user.roles", DataType: "keyword", Array: true, Description: "Array of user roles at the time of the event."}, + "cloud.account.id": {Name: "cloud.account.id", DataType: "keyword", Description: "The cloud account or organization id used to identify different entities in a multi-tenant environment.\nExamples: AWS account id, Google Cloud ORG Id, or other unique identifier."}, + "cloud.account.name": {Name: "cloud.account.name", DataType: "keyword", Description: "The cloud account name or alias used to identify different entities in a multi-tenant environment.\nExamples: AWS account name, Google Cloud ORG display name."}, + "cloud.availability_zone": {Name: "cloud.availability_zone", DataType: "keyword", Description: "Availability zone in which this host, resource, or service is located."}, + "cloud.instance.id": {Name: "cloud.instance.id", DataType: "keyword", Description: "Instance ID of the host machine."}, + "cloud.instance.name": {Name: "cloud.instance.name", DataType: "keyword", Description: "Instance name of the host machine."}, + "cloud.machine.type": {Name: "cloud.machine.type", DataType: "keyword", Description: "Machine type of the host machine."}, + "cloud.origin.account.id": {Name: "cloud.origin.account.id", DataType: "keyword", Description: "The cloud account or organization id used to identify different entities in a multi-tenant environment.\nExamples: AWS account id, Google Cloud ORG Id, or other unique identifier."}, + "cloud.origin.account.name": {Name: "cloud.origin.account.name", DataType: "keyword", Description: "The cloud account name or alias used to identify different entities in a multi-tenant environment.\nExamples: AWS account name, Google Cloud ORG display name."}, + "cloud.origin.availability_zone": {Name: "cloud.origin.availability_zone", DataType: "keyword", Description: "Availability zone in which this host, resource, or service is located."}, + "cloud.origin.instance.id": {Name: "cloud.origin.instance.id", DataType: "keyword", Description: "Instance ID of the host machine."}, + "cloud.origin.instance.name": {Name: "cloud.origin.instance.name", DataType: "keyword", Description: "Instance name of the host machine."}, + "cloud.origin.machine.type": {Name: "cloud.origin.machine.type", DataType: "keyword", Description: "Machine type of the host machine."}, + "cloud.origin.project.id": {Name: "cloud.origin.project.id", DataType: "keyword", Description: "The cloud project identifier.\nExamples: Google Cloud Project id, Azure Project id."}, + "cloud.origin.project.name": {Name: "cloud.origin.project.name", DataType: "keyword", Description: "The cloud project name.\nExamples: Google Cloud Project name, Azure Project name."}, + "cloud.origin.provider": {Name: "cloud.origin.provider", DataType: "keyword", Description: "Name of the cloud provider. Example values are aws, azure, gcp, or digitalocean."}, + "cloud.origin.region": {Name: "cloud.origin.region", DataType: "keyword", Description: "Region in which this host, resource, or service is located."}, + "cloud.origin.service.name": {Name: "cloud.origin.service.name", DataType: "keyword", Description: "The cloud service name is intended to distinguish services running on different platforms within a provider, eg AWS EC2 vs Lambda, GCP GCE vs App Engine, Azure VM vs App Server.\nExamples: app engine, app service, cloud run, fargate, lambda."}, + "cloud.project.id": {Name: "cloud.project.id", DataType: "keyword", Description: "The cloud project identifier.\nExamples: Google Cloud Project id, Azure Project id."}, + "cloud.project.name": {Name: "cloud.project.name", DataType: "keyword", Description: "The cloud project name.\nExamples: Google Cloud Project name, Azure Project name."}, + "cloud.provider": {Name: "cloud.provider", DataType: "keyword", Description: "Name of the cloud provider. Example values are aws, azure, gcp, or digitalocean."}, + "cloud.region": {Name: "cloud.region", DataType: "keyword", Description: "Region in which this host, resource, or service is located."}, + "cloud.service.name": {Name: "cloud.service.name", DataType: "keyword", Description: "The cloud service name is intended to distinguish services running on different platforms within a provider, eg AWS EC2 vs Lambda, GCP GCE vs App Engine, Azure VM vs App Server.\nExamples: app engine, app service, cloud run, fargate, lambda."}, + "cloud.target.account.id": {Name: "cloud.target.account.id", DataType: "keyword", Description: "The cloud account or organization id used to identify different entities in a multi-tenant environment.\nExamples: AWS account id, Google Cloud ORG Id, or other unique identifier."}, + "cloud.target.account.name": {Name: "cloud.target.account.name", DataType: "keyword", Description: "The cloud account name or alias used to identify different entities in a multi-tenant environment.\nExamples: AWS account name, Google Cloud ORG display name."}, + "cloud.target.availability_zone": {Name: "cloud.target.availability_zone", DataType: "keyword", Description: "Availability zone in which this host, resource, or service is located."}, + "cloud.target.instance.id": {Name: "cloud.target.instance.id", DataType: "keyword", Description: "Instance ID of the host machine."}, + "cloud.target.instance.name": {Name: "cloud.target.instance.name", DataType: "keyword", Description: "Instance name of the host machine."}, + "cloud.target.machine.type": {Name: "cloud.target.machine.type", DataType: "keyword", Description: "Machine type of the host machine."}, + "cloud.target.project.id": {Name: "cloud.target.project.id", DataType: "keyword", Description: "The cloud project identifier.\nExamples: Google Cloud Project id, Azure Project id."}, + "cloud.target.project.name": {Name: "cloud.target.project.name", DataType: "keyword", Description: "The cloud project name.\nExamples: Google Cloud Project name, Azure Project name."}, + "cloud.target.provider": {Name: "cloud.target.provider", DataType: "keyword", Description: "Name of the cloud provider. Example values are aws, azure, gcp, or digitalocean."}, + "cloud.target.region": {Name: "cloud.target.region", DataType: "keyword", Description: "Region in which this host, resource, or service is located."}, + "cloud.target.service.name": {Name: "cloud.target.service.name", DataType: "keyword", Description: "The cloud service name is intended to distinguish services running on different platforms within a provider, eg AWS EC2 vs Lambda, GCP GCE vs App Engine, Azure VM vs App Server.\nExamples: app engine, app service, cloud run, fargate, lambda."}, + "container.cpu.usage": {Name: "container.cpu.usage", DataType: "scaled_float", Description: "Percent CPU used which is normalized by the number of CPU cores and it ranges from 0 to 1. Scaling factor: 1000."}, + "container.disk.read.bytes": {Name: "container.disk.read.bytes", DataType: "long", Description: "The total number of bytes (gauge) read successfully (aggregated from all disks) since the last metric collection."}, + "container.disk.write.bytes": {Name: "container.disk.write.bytes", DataType: "long", Description: "The total number of bytes (gauge) written successfully (aggregated from all disks) since the last metric collection."}, + "container.id": {Name: "container.id", DataType: "keyword", Description: "Unique container id."}, + "container.image.hash.all": {Name: "container.image.hash.all", DataType: "keyword", Array: true, Description: "An array of digests of the image the container was built on. Each digest consists of the hash algorithm and value in this format: `algorithm:value`. Algorithm names should align with the field names in the ECS hash field set."}, + "container.image.name": {Name: "container.image.name", DataType: "keyword", Description: "Name of the image the container was built on."}, + "container.image.tag": {Name: "container.image.tag", DataType: "keyword", Array: true, Description: "Container image tags."}, + "container.labels": {Name: "container.labels", DataType: "object", Description: "Image labels."}, + "container.memory.usage": {Name: "container.memory.usage", DataType: "scaled_float", Description: "Memory usage percentage and it ranges from 0 to 1. Scaling factor: 1000."}, + "container.name": {Name: "container.name", DataType: "keyword", Description: "Container name."}, + "container.network.egress.bytes": {Name: "container.network.egress.bytes", DataType: "long", Description: "The number of bytes (gauge) sent out on all network interfaces by the container since the last metric collection."}, + "container.network.ingress.bytes": {Name: "container.network.ingress.bytes", DataType: "long", Description: "The number of bytes received (gauge) on all network interfaces by the container since the last metric collection."}, + "container.runtime": {Name: "container.runtime", DataType: "keyword", Description: "Runtime managing this container."}, + "container.security_context.privileged": {Name: "container.security_context.privileged", DataType: "boolean", Description: "Indicates whether the container is running in privileged mode."}, + "data_stream.dataset": {Name: "data_stream.dataset", DataType: "constant_keyword", Description: "The field can contain anything that makes sense to signify the source of the data.\nExamples include `nginx.access`, `prometheus`, `endpoint` etc. For data streams that otherwise fit, but that do not have dataset set we use the value \"generic\" for the dataset value. `event.dataset` should have the same value as `data_stream.dataset`.\nBeyond the Elasticsearch data stream naming criteria noted above, the `dataset` value has additional restrictions:\n * Must not contain `-`\n * No longer than 100 characters"}, + "data_stream.namespace": {Name: "data_stream.namespace", DataType: "constant_keyword", Description: "A user defined namespace. Namespaces are useful to allow grouping of data.\nMany users already organize their indices this way, and the data stream naming scheme now provides this best practice as a default. Many users will populate this field with `default`. If no value is used, it falls back to `default`.\nBeyond the Elasticsearch index naming criteria noted above, `namespace` value has the additional restrictions:\n * Must not contain `-`\n * No longer than 100 characters"}, + "data_stream.type": {Name: "data_stream.type", DataType: "constant_keyword", Description: "An overarching type for the data stream.\nCurrently allowed values are \"logs\" and \"metrics\". We expect to also add \"traces\" and \"synthetics\" in the near future."}, + "destination.address": {Name: "destination.address", DataType: "keyword", Description: "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.\nThen it should be duplicated to `.ip` or `.domain`, depending on which one it is."}, + "destination.as.number": {Name: "destination.as.number", DataType: "long", Description: "Unique number allocated to the autonomous system. The autonomous system number (ASN) uniquely identifies each network on the Internet."}, + "destination.as.organization.name": {Name: "destination.as.organization.name", DataType: "keyword", Description: "Organization name."}, + "destination.bytes": {Name: "destination.bytes", DataType: "long", Description: "Bytes sent from the destination to the source."}, + "destination.domain": {Name: "destination.domain", DataType: "keyword", Description: "The domain name of the destination system.\nThis value may be a host name, a fully qualified domain name, or another host naming format. The value may derive from the original event or be added from enrichment."}, + "destination.geo.city_name": {Name: "destination.geo.city_name", DataType: "keyword", Description: "City name."}, + "destination.geo.continent_code": {Name: "destination.geo.continent_code", DataType: "keyword", Description: "Two-letter code representing continent's name."}, + "destination.geo.continent_name": {Name: "destination.geo.continent_name", DataType: "keyword", Description: "Name of the continent."}, + "destination.geo.country_iso_code": {Name: "destination.geo.country_iso_code", DataType: "keyword", Description: "Country ISO code."}, + "destination.geo.country_name": {Name: "destination.geo.country_name", DataType: "keyword", Description: "Country name."}, + "destination.geo.location": {Name: "destination.geo.location", DataType: "geo_point", Description: "Longitude and latitude."}, + "destination.geo.name": {Name: "destination.geo.name", DataType: "keyword", Description: "User-defined description of a location, at the level of granularity they care about.\nCould be the name of their data centers, the floor number, if this describes a local physical entity, city names.\nNot typically used in automated geolocation."}, + "destination.geo.postal_code": {Name: "destination.geo.postal_code", DataType: "keyword", Description: "Postal code associated with the location.\nValues appropriate for this field may also be known as a postcode or ZIP code and will vary widely from country to country."}, + "destination.geo.region_iso_code": {Name: "destination.geo.region_iso_code", DataType: "keyword", Description: "Region ISO code."}, + "destination.geo.region_name": {Name: "destination.geo.region_name", DataType: "keyword", Description: "Region name."}, + "destination.geo.timezone": {Name: "destination.geo.timezone", DataType: "keyword", Description: "The time zone of the location, such as IANA time zone name."}, + "destination.ip": {Name: "destination.ip", DataType: "ip", Description: "IP address of the destination (IPv4 or IPv6)."}, + "destination.mac": {Name: "destination.mac", DataType: "keyword", Pattern: "^[A-F0-9]{2}(-[A-F0-9]{2}){5,}$", Description: "MAC address of the destination.\nThe notation format from RFC 7042 is suggested: Each octet (that is, 8-bit byte) is represented by two [uppercase] hexadecimal digits giving the value of the octet as an unsigned integer. Successive octets are separated by a hyphen."}, + "destination.nat.ip": {Name: "destination.nat.ip", DataType: "ip", Description: "Translated ip of destination based NAT sessions (e.g. internet to private DMZ)\nTypically used with load balancers, firewalls, or routers."}, + "destination.nat.port": {Name: "destination.nat.port", DataType: "long", Description: "Port the source session is translated to by NAT Device.\nTypically used with load balancers, firewalls, or routers."}, + "destination.packets": {Name: "destination.packets", DataType: "long", Description: "Packets sent from the destination to the source."}, + "destination.port": {Name: "destination.port", DataType: "long", Description: "Port of the destination."}, + "destination.registered_domain": {Name: "destination.registered_domain", DataType: "keyword", Description: "The highest registered destination domain, stripped of the subdomain.\nFor example, the registered domain for \"foo.example.com\" is \"example.com\".\nThis 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\"."}, + "destination.subdomain": {Name: "destination.subdomain", DataType: "keyword", Description: "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.\nFor 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."}, + "destination.top_level_domain": {Name: "destination.top_level_domain", DataType: "keyword", Description: "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\".\nThis 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\"."}, + "destination.user.domain": {Name: "destination.user.domain", DataType: "keyword", Description: "Name of the directory the user is a member of.\nFor example, an LDAP or Active Directory domain name."}, + "destination.user.email": {Name: "destination.user.email", DataType: "keyword", Description: "User email address."}, + "destination.user.full_name": {Name: "destination.user.full_name", DataType: "keyword", Description: "User's full name, if available."}, + "destination.user.group.domain": {Name: "destination.user.group.domain", DataType: "keyword", Description: "Name of the directory the group is a member of.\nFor example, an LDAP or Active Directory domain name."}, + "destination.user.group.id": {Name: "destination.user.group.id", DataType: "keyword", Description: "Unique identifier for the group on the system/platform."}, + "destination.user.group.name": {Name: "destination.user.group.name", DataType: "keyword", Description: "Name of the group."}, + "destination.user.hash": {Name: "destination.user.hash", DataType: "keyword", Description: "Unique user hash to correlate information for a user in anonymized form.\nUseful if `user.id` or `user.name` contain confidential information and cannot be used."}, + "destination.user.id": {Name: "destination.user.id", DataType: "keyword", Description: "Unique identifier of the user."}, + "destination.user.name": {Name: "destination.user.name", DataType: "keyword", Description: "Short name or login of the user."}, + "destination.user.roles": {Name: "destination.user.roles", DataType: "keyword", Array: true, Description: "Array of user roles at the time of the event."}, + "device.id": {Name: "device.id", DataType: "keyword", Description: "The unique identifier of a device. The identifier must not change across application sessions but stay fixed for an instance of a (mobile) device. \nOn iOS, this value must be equal to the vendor identifier (https://developer.apple.com/documentation/uikit/uidevice/1620059-identifierforvendor). On Android, this value must be equal to the Firebase Installation ID or a globally unique UUID which is persisted across sessions in your application.\nFor GDPR and data protection law reasons this identifier should not carry information that would allow to identify a user."}, + "device.manufacturer": {Name: "device.manufacturer", DataType: "keyword", Description: "The vendor name of the device manufacturer."}, + "device.model.identifier": {Name: "device.model.identifier", DataType: "keyword", Description: "The machine readable identifier of the device model."}, + "device.model.name": {Name: "device.model.name", DataType: "keyword", Description: "The human readable marketing name of the device model."}, + "dll.code_signature.digest_algorithm": {Name: "dll.code_signature.digest_algorithm", DataType: "keyword", Description: "The hashing algorithm used to sign the process.\nThis value can distinguish signatures when a file is signed multiple times by the same signer but with a different digest algorithm."}, + "dll.code_signature.exists": {Name: "dll.code_signature.exists", DataType: "boolean", Description: "Boolean to capture if a signature is present."}, + "dll.code_signature.signing_id": {Name: "dll.code_signature.signing_id", DataType: "keyword", Description: "The identifier used to sign the process.\nThis is used to identify the application manufactured by a software vendor. The field is relevant to Apple *OS only."}, + "dll.code_signature.status": {Name: "dll.code_signature.status", DataType: "keyword", Description: "Additional information about the certificate status.\nThis is useful for logging cryptographic errors with the certificate validity or trust status. Leave unpopulated if the validity or trust of the certificate was unchecked."}, + "dll.code_signature.subject_name": {Name: "dll.code_signature.subject_name", DataType: "keyword", Description: "Subject name of the code signer"}, + "dll.code_signature.team_id": {Name: "dll.code_signature.team_id", DataType: "keyword", Description: "The team identifier used to sign the process.\nThis is used to identify the team or vendor of a software product. The field is relevant to Apple *OS only."}, + "dll.code_signature.timestamp": {Name: "dll.code_signature.timestamp", DataType: "date", Description: "Date and time when the code signature was generated and signed."}, + "dll.code_signature.trusted": {Name: "dll.code_signature.trusted", DataType: "boolean", Description: "Stores the trust status of the certificate chain.\nValidating the trust of the certificate chain may be complicated, and this field should only be populated by tools that actively check the status."}, + "dll.code_signature.valid": {Name: "dll.code_signature.valid", DataType: "boolean", Description: "Boolean to capture if the digital signature is verified against the binary content.\nLeave unpopulated if a certificate was unchecked."}, + "dll.hash.md5": {Name: "dll.hash.md5", DataType: "keyword", Description: "MD5 hash."}, + "dll.hash.sha1": {Name: "dll.hash.sha1", DataType: "keyword", Description: "SHA1 hash."}, + "dll.hash.sha256": {Name: "dll.hash.sha256", DataType: "keyword", Description: "SHA256 hash."}, + "dll.hash.sha384": {Name: "dll.hash.sha384", DataType: "keyword", Description: "SHA384 hash."}, + "dll.hash.sha512": {Name: "dll.hash.sha512", DataType: "keyword", Description: "SHA512 hash."}, + "dll.hash.ssdeep": {Name: "dll.hash.ssdeep", DataType: "keyword", Description: "SSDEEP hash."}, + "dll.hash.tlsh": {Name: "dll.hash.tlsh", DataType: "keyword", Description: "TLSH hash."}, + "dll.name": {Name: "dll.name", DataType: "keyword", Description: "Name of the library.\nThis generally maps to the name of the file on disk."}, + "dll.path": {Name: "dll.path", DataType: "keyword", Description: "Full file path of the library."}, + "dll.pe.architecture": {Name: "dll.pe.architecture", DataType: "keyword", Description: "CPU architecture target for the file."}, + "dll.pe.company": {Name: "dll.pe.company", DataType: "keyword", Description: "Internal company name of the file, provided at compile-time."}, + "dll.pe.description": {Name: "dll.pe.description", DataType: "keyword", Description: "Internal description of the file, provided at compile-time."}, + "dll.pe.file_version": {Name: "dll.pe.file_version", DataType: "keyword", Description: "Internal version of the file, provided at compile-time."}, + "dll.pe.go_import_hash": {Name: "dll.pe.go_import_hash", DataType: "keyword", Description: "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.\nThe algorithm used to calculate the Go symbol hash and a reference implementation are available [here](https://github.com/elastic/toutoumomoma)."}, + "dll.pe.go_imports": {Name: "dll.pe.go_imports", DataType: "flattened", Description: "List of imported Go language element names and types."}, + "dll.pe.go_imports_names_entropy": {Name: "dll.pe.go_imports_names_entropy", DataType: "long", Description: "Shannon entropy calculation from the list of Go imports."}, + "dll.pe.go_imports_names_var_entropy": {Name: "dll.pe.go_imports_names_var_entropy", DataType: "long", Description: "Variance for Shannon entropy calculation from the list of Go imports."}, + "dll.pe.go_stripped": {Name: "dll.pe.go_stripped", DataType: "boolean", Description: "Set to true if the file is a Go executable that has had its symbols stripped or obfuscated and false if an unobfuscated Go executable."}, + "dll.pe.imphash": {Name: "dll.pe.imphash", DataType: "keyword", Description: "A hash of the imports in a PE file. An imphash -- or 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.\nLearn more at https://www.fireeye.com/blog/threat-research/2014/01/tracking-malware-import-hashing.html."}, + "dll.pe.import_hash": {Name: "dll.pe.import_hash", DataType: "keyword", Description: "A hash of the imports in a PE file. 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.\nThis is a synonym for imphash."}, + "dll.pe.imports": {Name: "dll.pe.imports", DataType: "flattened", Array: true, Description: "List of imported element names and types."}, + "dll.pe.imports_names_entropy": {Name: "dll.pe.imports_names_entropy", DataType: "long", Description: "Shannon entropy calculation from the list of imported element names and types."}, + "dll.pe.imports_names_var_entropy": {Name: "dll.pe.imports_names_var_entropy", DataType: "long", Description: "Variance for Shannon entropy calculation from the list of imported element names and types."}, + "dll.pe.original_file_name": {Name: "dll.pe.original_file_name", DataType: "keyword", Description: "Internal name of the file, provided at compile-time."}, + "dll.pe.pehash": {Name: "dll.pe.pehash", DataType: "keyword", Description: "A hash of the PE header and data from one or more PE sections. An pehash can be used to cluster files by transforming structural information about a file into a hash value.\nLearn more at https://www.usenix.org/legacy/events/leet09/tech/full_papers/wicherski/wicherski_html/index.html."}, + "dll.pe.product": {Name: "dll.pe.product", DataType: "keyword", Description: "Internal product name of the file, provided at compile-time."}, + "dll.pe.sections": {Name: "dll.pe.sections", DataType: "nested", Array: true, Description: "An array containing an object for each section of the PE file.\nThe keys that should be present in these objects are defined by sub-fields underneath `pe.sections.*`."}, + "dll.pe.sections.entropy": {Name: "dll.pe.sections.entropy", DataType: "long", Description: "Shannon entropy calculation from the section."}, + "dll.pe.sections.name": {Name: "dll.pe.sections.name", DataType: "keyword", Description: "PE Section List name."}, + "dll.pe.sections.physical_size": {Name: "dll.pe.sections.physical_size", DataType: "long", Description: "PE Section List physical size."}, + "dll.pe.sections.var_entropy": {Name: "dll.pe.sections.var_entropy", DataType: "long", Description: "Variance for Shannon entropy calculation from the section."}, + "dll.pe.sections.virtual_size": {Name: "dll.pe.sections.virtual_size", DataType: "long", Description: "PE Section List virtual size. This is always the same as `physical_size`."}, + "dns.answers": {Name: "dns.answers", DataType: "object", Array: true, Description: "An array containing an object for each answer section returned by the server.\nThe 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.\nNot 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."}, + "dns.answers.class": {Name: "dns.answers.class", DataType: "keyword", Description: "The class of DNS data contained in this resource record."}, + "dns.answers.data": {Name: "dns.answers.data", DataType: "keyword", Description: "The data describing the resource.\nThe meaning of this data depends on the type and class of the resource record."}, + "dns.answers.name": {Name: "dns.answers.name", DataType: "keyword", Description: "The domain name to which this resource record pertains.\nIf 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."}, + "dns.answers.ttl": {Name: "dns.answers.ttl", DataType: "long", Description: "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."}, + "dns.answers.type": {Name: "dns.answers.type", DataType: "keyword", Description: "The type of data contained in this resource record."}, + "dns.header_flags": {Name: "dns.header_flags", DataType: "keyword", Array: true, Pattern: "(?:AA|AD|CD|DO|RA|RD|TC)", Description: "Array of 2 letter DNS header flags."}, + "dns.id": {Name: "dns.id", DataType: "keyword", Description: "The DNS packet identifier assigned by the program that generated the query. The identifier is copied to the response."}, + "dns.op_code": {Name: "dns.op_code", DataType: "keyword", Description: "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."}, + "dns.question.class": {Name: "dns.question.class", DataType: "keyword", Description: "The class of records being queried."}, + "dns.question.name": {Name: "dns.question.name", DataType: "keyword", Description: "The name being queried.\nIf 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."}, + "dns.question.registered_domain": {Name: "dns.question.registered_domain", DataType: "keyword", Description: "The highest registered domain, stripped of the subdomain.\nFor example, the registered domain for \"foo.example.com\" is \"example.com\".\nThis 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\"."}, + "dns.question.subdomain": {Name: "dns.question.subdomain", DataType: "keyword", Description: "The subdomain is all of the labels under the registered_domain.\nIf the domain has multiple levels of subdomain, such as \"sub2.sub1.example.com\", the subdomain field should contain \"sub2.sub1\", with no trailing period."}, + "dns.question.top_level_domain": {Name: "dns.question.top_level_domain", DataType: "keyword", Description: "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\".\nThis 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\"."}, + "dns.question.type": {Name: "dns.question.type", DataType: "keyword", Description: "The type of record being queried."}, + "dns.resolved_ip": {Name: "dns.resolved_ip", DataType: "ip", Array: true, Description: "Array containing all IPs seen in `answers.data`.\nThe `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."}, + "dns.response_code": {Name: "dns.response_code", DataType: "keyword", Description: "The DNS response code."}, + "dns.type": {Name: "dns.type", DataType: "keyword", Description: "The type of DNS event captured, query or answer.\nIf your source of DNS events only gives you DNS queries, you should only create dns events of type `dns.type:query`.\nIf 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."}, + "ecs.version": {Name: "ecs.version", DataType: "keyword", Description: "ECS version this event conforms to. `ecs.version` is a required field and must exist in all events.\nWhen querying across multiple indices -- which may conform to slightly different ECS versions -- this field lets integrations adjust to the schema version of the events."}, + "email.attachments": {Name: "email.attachments", DataType: "nested", Array: true, Description: "A list of objects describing the attachment files sent along with an email message."}, + "email.attachments.file.extension": {Name: "email.attachments.file.extension", DataType: "keyword", Description: "Attachment file extension, excluding the leading dot."}, + "email.attachments.file.hash.md5": {Name: "email.attachments.file.hash.md5", DataType: "keyword", Description: "MD5 hash."}, + "email.attachments.file.hash.sha1": {Name: "email.attachments.file.hash.sha1", DataType: "keyword", Description: "SHA1 hash."}, + "email.attachments.file.hash.sha256": {Name: "email.attachments.file.hash.sha256", DataType: "keyword", Description: "SHA256 hash."}, + "email.attachments.file.hash.sha384": {Name: "email.attachments.file.hash.sha384", DataType: "keyword", Description: "SHA384 hash."}, + "email.attachments.file.hash.sha512": {Name: "email.attachments.file.hash.sha512", DataType: "keyword", Description: "SHA512 hash."}, + "email.attachments.file.hash.ssdeep": {Name: "email.attachments.file.hash.ssdeep", DataType: "keyword", Description: "SSDEEP hash."}, + "email.attachments.file.hash.tlsh": {Name: "email.attachments.file.hash.tlsh", DataType: "keyword", Description: "TLSH hash."}, + "email.attachments.file.mime_type": {Name: "email.attachments.file.mime_type", DataType: "keyword", Description: "The MIME media type of the attachment.\nThis value will typically be extracted from the `Content-Type` MIME header field."}, + "email.attachments.file.name": {Name: "email.attachments.file.name", DataType: "keyword", Description: "Name of the attachment file including the file extension."}, + "email.attachments.file.size": {Name: "email.attachments.file.size", DataType: "long", Description: "Attachment file size in bytes."}, + "email.bcc.address": {Name: "email.bcc.address", DataType: "keyword", Array: true, Description: "The email address of BCC recipient"}, + "email.cc.address": {Name: "email.cc.address", DataType: "keyword", Array: true, Description: "The email address of CC recipient"}, + "email.content_type": {Name: "email.content_type", DataType: "keyword", Description: "Information about how the message is to be displayed.\nTypically a MIME type."}, + "email.delivery_timestamp": {Name: "email.delivery_timestamp", DataType: "date", Description: "The date and time when the email message was received by the service or client."}, + "email.direction": {Name: "email.direction", DataType: "keyword", Description: "The direction of the message based on the sending and receiving domains."}, + "email.from.address": {Name: "email.from.address", DataType: "keyword", Array: true, Description: "The email address of the sender, typically from the RFC 5322 `From:` header field."}, + "email.local_id": {Name: "email.local_id", DataType: "keyword", Description: "Unique identifier given to the email by the source that created the event.\nIdentifier is not persistent across hops."}, + "email.message_id": {Name: "email.message_id", DataType: "wildcard", Description: "Identifier from the RFC 5322 `Message-ID:` email header that refers to a particular email message."}, + "email.origination_timestamp": {Name: "email.origination_timestamp", DataType: "date", Description: "The date and time the email message was composed. Many email clients will fill in this value automatically when the message is sent by a user."}, + "email.reply_to.address": {Name: "email.reply_to.address", DataType: "keyword", Array: true, Description: "The address that replies should be delivered to based on the value in the RFC 5322 `Reply-To:` header."}, + "email.sender.address": {Name: "email.sender.address", DataType: "keyword", Description: "Per RFC 5322, specifies the address responsible for the actual transmission of the message."}, + "email.subject": {Name: "email.subject", DataType: "keyword", Description: "A brief summary of the topic of the message."}, + "email.to.address": {Name: "email.to.address", DataType: "keyword", Array: true, Description: "The email address of recipient"}, + "email.x_mailer": {Name: "email.x_mailer", DataType: "keyword", Description: "The name of the application that was used to draft and send the original email message."}, + "error.code": {Name: "error.code", DataType: "keyword", Description: "Error code describing the error."}, + "error.id": {Name: "error.id", DataType: "keyword", Description: "Unique identifier for the error."}, + "error.message": {Name: "error.message", DataType: "match_only_text", Description: "Error message."}, + "error.stack_trace": {Name: "error.stack_trace", DataType: "wildcard", Description: "The stack trace of this error in plain text."}, + "error.type": {Name: "error.type", DataType: "keyword", Description: "The type of the error, for example the class name of the exception."}, + "event.action": {Name: "event.action", DataType: "keyword", Description: "The action captured by the event.\nThis 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."}, + "event.agent_id_status": {Name: "event.agent_id_status", DataType: "keyword", Description: "Agents are normally responsible for populating the `agent.id` field value. If the system receiving events is capable of validating the value based on authentication information for the client then this field can be used to reflect the outcome of that validation.\nFor example if the agent's connection is authenticated with mTLS and the client cert contains the ID of the agent to which the cert was issued then the `agent.id` value in events can be checked against the certificate. If the values match then `event.agent_id_status: verified` is added to the event, otherwise one of the other allowed values should be used.\nIf no validation is performed then the field should be omitted.\nThe allowed values are:\n`verified` - The `agent.id` field value matches expected value obtained from auth metadata.\n`mismatch` - The `agent.id` field value does not match the expected value obtained from auth metadata.\n`missing` - There was no `agent.id` field in the event to validate.\n`auth_metadata_missing` - There was no auth metadata or it was missing information about the agent ID."}, + "event.category": {Name: "event.category", DataType: "keyword", Array: true, Pattern: "(?:api|authentication|configuration|database|driver|email|file|host|iam|intrusion_detection|library|malware|network|package|process|registry|session|threat|vulnerability|web)", Description: "This is one of four ECS Categorization Fields, and indicates the second level in the ECS category hierarchy.\n`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.\nThis field is an array. This will allow proper categorization of some events that fall in multiple categories."}, + "event.code": {Name: "event.code", DataType: "keyword", Description: "Identification code for this event, if one exists.\nSome 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."}, + "event.created": {Name: "event.created", DataType: "date", Description: "`event.created` contains the date/time when the event was first read by an agent, or by your pipeline.\nThis field is distinct from `@timestamp` in that `@timestamp` typically contain the time extracted from the original event.\nIn 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.\nIn case the two timestamps are identical, `@timestamp` should be used."}, + "event.dataset": {Name: "event.dataset", DataType: "keyword", Description: "Name of the dataset.\nIf 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.\nIt's recommended but not required to start the dataset name with the module name, followed by a dot, then the dataset name."}, + "event.duration": {Name: "event.duration", DataType: "long", Description: "Duration of the event in nanoseconds.\nIf `event.start` and `event.end` are known this value should be the difference between the end and start time."}, + "event.end": {Name: "event.end", DataType: "date", Description: "`event.end` contains the date when the event ended or when the activity was last observed."}, + "event.hash": {Name: "event.hash", DataType: "keyword", Description: "Hash (perhaps logstash fingerprint) of raw field to be able to demonstrate log integrity."}, + "event.id": {Name: "event.id", DataType: "keyword", Description: "Unique ID to describe the event."}, + "event.ingested": {Name: "event.ingested", DataType: "date", Description: "Timestamp when an event arrived in the central data store.\nThis 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.\nIn normal conditions, assuming no tampering, the timestamps should chronologically look like this: `@timestamp` < `event.created` < `event.ingested`."}, + "event.kind": {Name: "event.kind", DataType: "keyword", Pattern: "(?:alert|asset|enrichment|event|metric|pipeline_error|signal|state)", Description: "This is one of four ECS Categorization Fields, and indicates the highest level in the ECS category hierarchy.\n`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.\nThe 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 is coming in at a regular interval or not."}, + "event.module": {Name: "event.module", DataType: "keyword", Description: "Name of the module this data is coming from.\nIf 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."}, + "event.original": {Name: "event.original", DataType: "keyword", Description: "Raw text message of entire event. Used to demonstrate log integrity or where the full log message (before splitting it up in multiple parts) may be required, e.g. for reindex.\nThis field is not indexed and doc_values are disabled. It cannot be searched, but it can be retrieved from `_source`. If users wish to override this and index this field, please see `Field data types` in the `Elasticsearch Reference`."}, + "event.outcome": {Name: "event.outcome", DataType: "keyword", Pattern: "(?:failure|success|unknown)", Description: "This is one of four ECS Categorization Fields, and indicates the lowest level in the ECS category hierarchy.\n`event.outcome` simply denotes whether the event represents a success or a failure from the perspective of the entity that produced the event.\nNote that when a single transaction is described in multiple events, each event may populate different values of `event.outcome`, according to their perspective.\nAlso note that in the case of a compound event (a single event that contains multiple logical events), this field should be populated with the value that best captures the overall success or failure from the perspective of the event producer.\nFurther note that not all events will have an associated outcome. For example, this field is generally not populated for metric events, events with `event.type:info`, or any events for which an outcome does not make logical sense."}, + "event.provider": {Name: "event.provider", DataType: "keyword", Description: "Source of the event.\nEvent 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)."}, + "event.reason": {Name: "event.reason", DataType: "keyword", Description: "Reason why this event happened, according to the source.\nThis describes the why of a particular action or outcome captured in the event. Where `event.action` captures the action from the event, `event.reason` describes why that action was taken. For example, a web proxy with an `event.action` which denied the request may also populate `event.reason` with the reason why (e.g. `blocked site`)."}, + "event.reference": {Name: "event.reference", DataType: "keyword", Description: "Reference URL linking to additional information about this event.\nThis URL links to a static definition of this event. Alert events, indicated by `event.kind:alert`, are a common use case for this field."}, + "event.risk_score": {Name: "event.risk_score", DataType: "float", Description: "Risk score or priority of the event (e.g. security solutions). Use your system's original value here."}, + "event.risk_score_norm": {Name: "event.risk_score_norm", DataType: "float", Description: "Normalized risk score or priority of the event, on a scale of 0 to 100.\nThis 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."}, + "event.sequence": {Name: "event.sequence", DataType: "long", Description: "Sequence number of the event.\nThe sequence number is a value published by some event sources, to make the exact ordering of events unambiguous, regardless of the timestamp precision."}, + "event.severity": {Name: "event.severity", DataType: "long", Description: "The numeric severity of the event according to your event source.\nWhat 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.\nThe 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`."}, + "event.start": {Name: "event.start", DataType: "date", Description: "`event.start` contains the date when the event started or when the activity was first observed."}, + "event.timezone": {Name: "event.timezone", DataType: "keyword", Description: "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.\nAcceptable timezone formats are: a canonical ID (e.g. \"Europe/Amsterdam\"), abbreviated (e.g. \"EST\") or an HH:mm differential (e.g. \"-05:00\")."}, + "event.type": {Name: "event.type", DataType: "keyword", Array: true, Pattern: "(?:access|admin|allowed|change|connection|creation|deletion|denied|end|error|group|indicator|info|installation|protocol|start|user)", Description: "This is one of four ECS Categorization Fields, and indicates the third level in the ECS category hierarchy.\n`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.\nThis field is an array. This will allow proper categorization of some events that fall in multiple event types."}, + "event.url": {Name: "event.url", DataType: "keyword", Description: "URL linking to an external system to continue investigation of this event.\nThis URL links to another system where in-depth investigation of the specific occurrence of this event can take place. Alert events, indicated by `event.kind:alert`, are a common use case for this field."}, + "faas.coldstart": {Name: "faas.coldstart", DataType: "boolean", Description: "Boolean value indicating a cold start of a function."}, + "faas.execution": {Name: "faas.execution", DataType: "keyword", Description: "The execution ID of the current function execution."}, + "faas.id": {Name: "faas.id", DataType: "keyword", Description: "The unique identifier of a serverless function.\nFor AWS Lambda it's the function ARN (Amazon Resource Name) without a version or alias suffix."}, + "faas.name": {Name: "faas.name", DataType: "keyword", Description: "The name of a serverless function."}, + "faas.trigger.request_id": {Name: "faas.trigger.request_id", DataType: "keyword", Description: "The ID of the trigger request , message, event, etc."}, + "faas.trigger.type": {Name: "faas.trigger.type", DataType: "keyword", Pattern: "(?:datasource|http|other|pubsub|timer)", Description: "The trigger for the function execution."}, + "faas.version": {Name: "faas.version", DataType: "keyword", Description: "The version of a serverless function."}, + "file.accessed": {Name: "file.accessed", DataType: "date", Description: "Last time the file was accessed.\nNote that not all filesystems keep track of access time."}, + "file.attributes": {Name: "file.attributes", DataType: "keyword", Array: true, Description: "Array of file attributes.\nAttributes 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."}, + "file.code_signature.digest_algorithm": {Name: "file.code_signature.digest_algorithm", DataType: "keyword", Description: "The hashing algorithm used to sign the process.\nThis value can distinguish signatures when a file is signed multiple times by the same signer but with a different digest algorithm."}, + "file.code_signature.exists": {Name: "file.code_signature.exists", DataType: "boolean", Description: "Boolean to capture if a signature is present."}, + "file.code_signature.signing_id": {Name: "file.code_signature.signing_id", DataType: "keyword", Description: "The identifier used to sign the process.\nThis is used to identify the application manufactured by a software vendor. The field is relevant to Apple *OS only."}, + "file.code_signature.status": {Name: "file.code_signature.status", DataType: "keyword", Description: "Additional information about the certificate status.\nThis is useful for logging cryptographic errors with the certificate validity or trust status. Leave unpopulated if the validity or trust of the certificate was unchecked."}, + "file.code_signature.subject_name": {Name: "file.code_signature.subject_name", DataType: "keyword", Description: "Subject name of the code signer"}, + "file.code_signature.team_id": {Name: "file.code_signature.team_id", DataType: "keyword", Description: "The team identifier used to sign the process.\nThis is used to identify the team or vendor of a software product. The field is relevant to Apple *OS only."}, + "file.code_signature.timestamp": {Name: "file.code_signature.timestamp", DataType: "date", Description: "Date and time when the code signature was generated and signed."}, + "file.code_signature.trusted": {Name: "file.code_signature.trusted", DataType: "boolean", Description: "Stores the trust status of the certificate chain.\nValidating the trust of the certificate chain may be complicated, and this field should only be populated by tools that actively check the status."}, + "file.code_signature.valid": {Name: "file.code_signature.valid", DataType: "boolean", Description: "Boolean to capture if the digital signature is verified against the binary content.\nLeave unpopulated if a certificate was unchecked."}, + "file.created": {Name: "file.created", DataType: "date", Description: "File creation time.\nNote that not all filesystems store the creation time."}, + "file.ctime": {Name: "file.ctime", DataType: "date", Description: "Last time the file attributes or metadata changed.\nNote 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."}, + "file.device": {Name: "file.device", DataType: "keyword", Description: "Device that is the source of the file."}, + "file.directory": {Name: "file.directory", DataType: "keyword", Description: "Directory where the file is located. It should include the drive letter, when appropriate."}, + "file.drive_letter": {Name: "file.drive_letter", DataType: "keyword", Description: "Drive letter where the file is located. This field is only relevant on Windows.\nThe value should be uppercase, and not include the colon."}, + "file.elf.architecture": {Name: "file.elf.architecture", DataType: "keyword", Description: "Machine architecture of the ELF file."}, + "file.elf.byte_order": {Name: "file.elf.byte_order", DataType: "keyword", Description: "Byte sequence of ELF file."}, + "file.elf.cpu_type": {Name: "file.elf.cpu_type", DataType: "keyword", Description: "CPU type of the ELF file."}, + "file.elf.creation_date": {Name: "file.elf.creation_date", DataType: "date", Description: "Extracted when possible from the file's metadata. Indicates when it was built or compiled. It can also be faked by malware creators."}, + "file.elf.exports": {Name: "file.elf.exports", DataType: "flattened", Array: true, Description: "List of exported element names and types."}, + "file.elf.go_import_hash": {Name: "file.elf.go_import_hash", DataType: "keyword", Description: "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.\nThe algorithm used to calculate the Go symbol hash and a reference implementation are available [here](https://github.com/elastic/toutoumomoma)."}, + "file.elf.go_imports": {Name: "file.elf.go_imports", DataType: "flattened", Description: "List of imported Go language element names and types."}, + "file.elf.go_imports_names_entropy": {Name: "file.elf.go_imports_names_entropy", DataType: "long", Description: "Shannon entropy calculation from the list of Go imports."}, + "file.elf.go_imports_names_var_entropy": {Name: "file.elf.go_imports_names_var_entropy", DataType: "long", Description: "Variance for Shannon entropy calculation from the list of Go imports."}, + "file.elf.go_stripped": {Name: "file.elf.go_stripped", DataType: "boolean", Description: "Set to true if the file is a Go executable that has had its symbols stripped or obfuscated and false if an unobfuscated Go executable."}, + "file.elf.header.abi_version": {Name: "file.elf.header.abi_version", DataType: "keyword", Description: "Version of the ELF Application Binary Interface (ABI)."}, + "file.elf.header.class": {Name: "file.elf.header.class", DataType: "keyword", Description: "Header class of the ELF file."}, + "file.elf.header.data": {Name: "file.elf.header.data", DataType: "keyword", Description: "Data table of the ELF header."}, + "file.elf.header.entrypoint": {Name: "file.elf.header.entrypoint", DataType: "long", Description: "Header entrypoint of the ELF file."}, + "file.elf.header.object_version": {Name: "file.elf.header.object_version", DataType: "keyword", Description: "\"0x1\" for original ELF files."}, + "file.elf.header.os_abi": {Name: "file.elf.header.os_abi", DataType: "keyword", Description: "Application Binary Interface (ABI) of the Linux OS."}, + "file.elf.header.type": {Name: "file.elf.header.type", DataType: "keyword", Description: "Header type of the ELF file."}, + "file.elf.header.version": {Name: "file.elf.header.version", DataType: "keyword", Description: "Version of the ELF header."}, + "file.elf.import_hash": {Name: "file.elf.import_hash", DataType: "keyword", Description: "A hash of the imports in an ELF file. 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.\nThis is an ELF implementation of the Windows PE imphash."}, + "file.elf.imports": {Name: "file.elf.imports", DataType: "flattened", Array: true, Description: "List of imported element names and types."}, + "file.elf.imports_names_entropy": {Name: "file.elf.imports_names_entropy", DataType: "long", Description: "Shannon entropy calculation from the list of imported element names and types."}, + "file.elf.imports_names_var_entropy": {Name: "file.elf.imports_names_var_entropy", DataType: "long", Description: "Variance for Shannon entropy calculation from the list of imported element names and types."}, + "file.elf.sections": {Name: "file.elf.sections", DataType: "nested", Array: true, Description: "An array containing an object for each section of the ELF file.\nThe keys that should be present in these objects are defined by sub-fields underneath `elf.sections.*`."}, + "file.elf.sections.chi2": {Name: "file.elf.sections.chi2", DataType: "long", Description: "Chi-square probability distribution of the section."}, + "file.elf.sections.entropy": {Name: "file.elf.sections.entropy", DataType: "long", Description: "Shannon entropy calculation from the section."}, + "file.elf.sections.flags": {Name: "file.elf.sections.flags", DataType: "keyword", Description: "ELF Section List flags."}, + "file.elf.sections.name": {Name: "file.elf.sections.name", DataType: "keyword", Description: "ELF Section List name."}, + "file.elf.sections.physical_offset": {Name: "file.elf.sections.physical_offset", DataType: "keyword", Description: "ELF Section List offset."}, + "file.elf.sections.physical_size": {Name: "file.elf.sections.physical_size", DataType: "long", Description: "ELF Section List physical size."}, + "file.elf.sections.type": {Name: "file.elf.sections.type", DataType: "keyword", Description: "ELF Section List type."}, + "file.elf.sections.var_entropy": {Name: "file.elf.sections.var_entropy", DataType: "long", Description: "Variance for Shannon entropy calculation from the section."}, + "file.elf.sections.virtual_address": {Name: "file.elf.sections.virtual_address", DataType: "long", Description: "ELF Section List virtual address."}, + "file.elf.sections.virtual_size": {Name: "file.elf.sections.virtual_size", DataType: "long", Description: "ELF Section List virtual size."}, + "file.elf.segments": {Name: "file.elf.segments", DataType: "nested", Array: true, Description: "An array containing an object for each segment of the ELF file.\nThe keys that should be present in these objects are defined by sub-fields underneath `elf.segments.*`."}, + "file.elf.segments.sections": {Name: "file.elf.segments.sections", DataType: "keyword", Description: "ELF object segment sections."}, + "file.elf.segments.type": {Name: "file.elf.segments.type", DataType: "keyword", Description: "ELF object segment type."}, + "file.elf.shared_libraries": {Name: "file.elf.shared_libraries", DataType: "keyword", Array: true, Description: "List of shared libraries used by this ELF object."}, + "file.elf.telfhash": {Name: "file.elf.telfhash", DataType: "keyword", Description: "telfhash symbol hash for ELF file."}, + "file.extension": {Name: "file.extension", DataType: "keyword", Description: "File extension, excluding the leading dot.\nNote that when the file name has multiple extensions (example.tar.gz), only the last one should be captured (\"gz\", not \"tar.gz\")."}, + "file.fork_name": {Name: "file.fork_name", DataType: "keyword", Description: "A fork is additional data associated with a filesystem object.\nOn Linux, a resource fork is used to store additional data with a filesystem object. A file always has at least one fork for the data portion, and additional forks may exist.\nOn NTFS, this is analogous to an Alternate Data Stream (ADS), and the default data stream for a file is just called $DATA. Zone.Identifier is commonly used by Windows to track contents downloaded from the Internet. An ADS is typically of the form: `C:\\path\\to\\filename.extension:some_fork_name`, and `some_fork_name` is the value that should populate `fork_name`. `filename.extension` should populate `file.name`, and `extension` should populate `file.extension`. The full path, `file.path`, will include the fork name."}, + "file.gid": {Name: "file.gid", DataType: "keyword", Description: "Primary group ID (GID) of the file."}, + "file.group": {Name: "file.group", DataType: "keyword", Description: "Primary group name of the file."}, + "file.hash.md5": {Name: "file.hash.md5", DataType: "keyword", Description: "MD5 hash."}, + "file.hash.sha1": {Name: "file.hash.sha1", DataType: "keyword", Description: "SHA1 hash."}, + "file.hash.sha256": {Name: "file.hash.sha256", DataType: "keyword", Description: "SHA256 hash."}, + "file.hash.sha384": {Name: "file.hash.sha384", DataType: "keyword", Description: "SHA384 hash."}, + "file.hash.sha512": {Name: "file.hash.sha512", DataType: "keyword", Description: "SHA512 hash."}, + "file.hash.ssdeep": {Name: "file.hash.ssdeep", DataType: "keyword", Description: "SSDEEP hash."}, + "file.hash.tlsh": {Name: "file.hash.tlsh", DataType: "keyword", Description: "TLSH hash."}, + "file.inode": {Name: "file.inode", DataType: "keyword", Description: "Inode representing the file in the filesystem."}, + "file.macho.go_import_hash": {Name: "file.macho.go_import_hash", DataType: "keyword", Description: "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.\nThe algorithm used to calculate the Go symbol hash and a reference implementation are available [here](https://github.com/elastic/toutoumomoma)."}, + "file.macho.go_imports": {Name: "file.macho.go_imports", DataType: "flattened", Description: "List of imported Go language element names and types."}, + "file.macho.go_imports_names_entropy": {Name: "file.macho.go_imports_names_entropy", DataType: "long", Description: "Shannon entropy calculation from the list of Go imports."}, + "file.macho.go_imports_names_var_entropy": {Name: "file.macho.go_imports_names_var_entropy", DataType: "long", Description: "Variance for Shannon entropy calculation from the list of Go imports."}, + "file.macho.go_stripped": {Name: "file.macho.go_stripped", DataType: "boolean", Description: "Set to true if the file is a Go executable that has had its symbols stripped or obfuscated and false if an unobfuscated Go executable."}, + "file.macho.import_hash": {Name: "file.macho.import_hash", DataType: "keyword", Description: "A hash of the imports in a Mach-O file. 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.\nThis is a synonym for symhash."}, + "file.macho.imports": {Name: "file.macho.imports", DataType: "flattened", Array: true, Description: "List of imported element names and types."}, + "file.macho.imports_names_entropy": {Name: "file.macho.imports_names_entropy", DataType: "long", Description: "Shannon entropy calculation from the list of imported element names and types."}, + "file.macho.imports_names_var_entropy": {Name: "file.macho.imports_names_var_entropy", DataType: "long", Description: "Variance for Shannon entropy calculation from the list of imported element names and types."}, + "file.macho.sections": {Name: "file.macho.sections", DataType: "nested", Array: true, Description: "An array containing an object for each section of the Mach-O file.\nThe keys that should be present in these objects are defined by sub-fields underneath `macho.sections.*`."}, + "file.macho.sections.entropy": {Name: "file.macho.sections.entropy", DataType: "long", Description: "Shannon entropy calculation from the section."}, + "file.macho.sections.name": {Name: "file.macho.sections.name", DataType: "keyword", Description: "Mach-O Section List name."}, + "file.macho.sections.physical_size": {Name: "file.macho.sections.physical_size", DataType: "long", Description: "Mach-O Section List physical size."}, + "file.macho.sections.var_entropy": {Name: "file.macho.sections.var_entropy", DataType: "long", Description: "Variance for Shannon entropy calculation from the section."}, + "file.macho.sections.virtual_size": {Name: "file.macho.sections.virtual_size", DataType: "long", Description: "Mach-O Section List virtual size. This is always the same as `physical_size`."}, + "file.macho.symhash": {Name: "file.macho.symhash", DataType: "keyword", Description: "A hash of the imports in a Mach-O file. 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.\nThis is a Mach-O implementation of the Windows PE imphash"}, + "file.mime_type": {Name: "file.mime_type", DataType: "keyword", Description: "MIME type should identify the format of the file or stream of bytes using https://www.iana.org/assignments/media-types/media-types.xhtml[IANA official types], where possible. When more than one type is applicable, the most specific type should be used."}, + "file.mode": {Name: "file.mode", DataType: "keyword", Description: "Mode of the file in octal representation."}, + "file.mtime": {Name: "file.mtime", DataType: "date", Description: "Last time the file content was modified."}, + "file.name": {Name: "file.name", DataType: "keyword", Description: "Name of the file including the extension, without the directory."}, + "file.owner": {Name: "file.owner", DataType: "keyword", Description: "File owner's username."}, + "file.path": {Name: "file.path", DataType: "keyword", Description: "Full path to the file, including the file name. It should include the drive letter, when appropriate."}, + "file.pe.architecture": {Name: "file.pe.architecture", DataType: "keyword", Description: "CPU architecture target for the file."}, + "file.pe.company": {Name: "file.pe.company", DataType: "keyword", Description: "Internal company name of the file, provided at compile-time."}, + "file.pe.description": {Name: "file.pe.description", DataType: "keyword", Description: "Internal description of the file, provided at compile-time."}, + "file.pe.file_version": {Name: "file.pe.file_version", DataType: "keyword", Description: "Internal version of the file, provided at compile-time."}, + "file.pe.go_import_hash": {Name: "file.pe.go_import_hash", DataType: "keyword", Description: "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.\nThe algorithm used to calculate the Go symbol hash and a reference implementation are available [here](https://github.com/elastic/toutoumomoma)."}, + "file.pe.go_imports": {Name: "file.pe.go_imports", DataType: "flattened", Description: "List of imported Go language element names and types."}, + "file.pe.go_imports_names_entropy": {Name: "file.pe.go_imports_names_entropy", DataType: "long", Description: "Shannon entropy calculation from the list of Go imports."}, + "file.pe.go_imports_names_var_entropy": {Name: "file.pe.go_imports_names_var_entropy", DataType: "long", Description: "Variance for Shannon entropy calculation from the list of Go imports."}, + "file.pe.go_stripped": {Name: "file.pe.go_stripped", DataType: "boolean", Description: "Set to true if the file is a Go executable that has had its symbols stripped or obfuscated and false if an unobfuscated Go executable."}, + "file.pe.imphash": {Name: "file.pe.imphash", DataType: "keyword", Description: "A hash of the imports in a PE file. An imphash -- or 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.\nLearn more at https://www.fireeye.com/blog/threat-research/2014/01/tracking-malware-import-hashing.html."}, + "file.pe.import_hash": {Name: "file.pe.import_hash", DataType: "keyword", Description: "A hash of the imports in a PE file. 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.\nThis is a synonym for imphash."}, + "file.pe.imports": {Name: "file.pe.imports", DataType: "flattened", Array: true, Description: "List of imported element names and types."}, + "file.pe.imports_names_entropy": {Name: "file.pe.imports_names_entropy", DataType: "long", Description: "Shannon entropy calculation from the list of imported element names and types."}, + "file.pe.imports_names_var_entropy": {Name: "file.pe.imports_names_var_entropy", DataType: "long", Description: "Variance for Shannon entropy calculation from the list of imported element names and types."}, + "file.pe.original_file_name": {Name: "file.pe.original_file_name", DataType: "keyword", Description: "Internal name of the file, provided at compile-time."}, + "file.pe.pehash": {Name: "file.pe.pehash", DataType: "keyword", Description: "A hash of the PE header and data from one or more PE sections. An pehash can be used to cluster files by transforming structural information about a file into a hash value.\nLearn more at https://www.usenix.org/legacy/events/leet09/tech/full_papers/wicherski/wicherski_html/index.html."}, + "file.pe.product": {Name: "file.pe.product", DataType: "keyword", Description: "Internal product name of the file, provided at compile-time."}, + "file.pe.sections": {Name: "file.pe.sections", DataType: "nested", Array: true, Description: "An array containing an object for each section of the PE file.\nThe keys that should be present in these objects are defined by sub-fields underneath `pe.sections.*`."}, + "file.pe.sections.entropy": {Name: "file.pe.sections.entropy", DataType: "long", Description: "Shannon entropy calculation from the section."}, + "file.pe.sections.name": {Name: "file.pe.sections.name", DataType: "keyword", Description: "PE Section List name."}, + "file.pe.sections.physical_size": {Name: "file.pe.sections.physical_size", DataType: "long", Description: "PE Section List physical size."}, + "file.pe.sections.var_entropy": {Name: "file.pe.sections.var_entropy", DataType: "long", Description: "Variance for Shannon entropy calculation from the section."}, + "file.pe.sections.virtual_size": {Name: "file.pe.sections.virtual_size", DataType: "long", Description: "PE Section List virtual size. This is always the same as `physical_size`."}, + "file.size": {Name: "file.size", DataType: "long", Description: "File size in bytes.\nOnly relevant when `file.type` is \"file\"."}, + "file.target_path": {Name: "file.target_path", DataType: "keyword", Description: "Target path for symlinks."}, + "file.type": {Name: "file.type", DataType: "keyword", Description: "File type (file, dir, or symlink)."}, + "file.uid": {Name: "file.uid", DataType: "keyword", Description: "The user ID (UID) or security identifier (SID) of the file owner."}, + "file.x509.alternative_names": {Name: "file.x509.alternative_names", DataType: "keyword", Array: true, Description: "List of subject alternative names (SAN). Name types vary by certificate authority and certificate type but commonly contain IP addresses, DNS names (and wildcards), and email addresses."}, + "file.x509.issuer.common_name": {Name: "file.x509.issuer.common_name", DataType: "keyword", Array: true, Description: "List of common name (CN) of issuing certificate authority."}, + "file.x509.issuer.country": {Name: "file.x509.issuer.country", DataType: "keyword", Array: true, Description: "List of country \\(C) codes"}, + "file.x509.issuer.distinguished_name": {Name: "file.x509.issuer.distinguished_name", DataType: "keyword", Description: "Distinguished name (DN) of issuing certificate authority."}, + "file.x509.issuer.locality": {Name: "file.x509.issuer.locality", DataType: "keyword", Array: true, Description: "List of locality names (L)"}, + "file.x509.issuer.organization": {Name: "file.x509.issuer.organization", DataType: "keyword", Array: true, Description: "List of organizations (O) of issuing certificate authority."}, + "file.x509.issuer.organizational_unit": {Name: "file.x509.issuer.organizational_unit", DataType: "keyword", Array: true, Description: "List of organizational units (OU) of issuing certificate authority."}, + "file.x509.issuer.state_or_province": {Name: "file.x509.issuer.state_or_province", DataType: "keyword", Array: true, Description: "List of state or province names (ST, S, or P)"}, + "file.x509.not_after": {Name: "file.x509.not_after", DataType: "date", Description: "Time at which the certificate is no longer considered valid."}, + "file.x509.not_before": {Name: "file.x509.not_before", DataType: "date", Description: "Time at which the certificate is first considered valid."}, + "file.x509.public_key_algorithm": {Name: "file.x509.public_key_algorithm", DataType: "keyword", Description: "Algorithm used to generate the public key."}, + "file.x509.public_key_curve": {Name: "file.x509.public_key_curve", DataType: "keyword", Description: "The curve used by the elliptic curve public key algorithm. This is algorithm specific."}, + "file.x509.public_key_exponent": {Name: "file.x509.public_key_exponent", DataType: "long", Description: "Exponent used to derive the public key. This is algorithm specific."}, + "file.x509.public_key_size": {Name: "file.x509.public_key_size", DataType: "long", Description: "The size of the public key space in bits."}, + "file.x509.serial_number": {Name: "file.x509.serial_number", DataType: "keyword", Description: "Unique serial number issued by the certificate authority. For consistency, if this value is alphanumeric, it should be formatted without colons and uppercase characters."}, + "file.x509.signature_algorithm": {Name: "file.x509.signature_algorithm", DataType: "keyword", Description: "Identifier for certificate signature algorithm. We recommend using names found in Go Lang Crypto library. See https://github.com/golang/go/blob/go1.14/src/crypto/x509/x509.go#L337-L353."}, + "file.x509.subject.common_name": {Name: "file.x509.subject.common_name", DataType: "keyword", Array: true, Description: "List of common names (CN) of subject."}, + "file.x509.subject.country": {Name: "file.x509.subject.country", DataType: "keyword", Array: true, Description: "List of country \\(C) code"}, + "file.x509.subject.distinguished_name": {Name: "file.x509.subject.distinguished_name", DataType: "keyword", Description: "Distinguished name (DN) of the certificate subject entity."}, + "file.x509.subject.locality": {Name: "file.x509.subject.locality", DataType: "keyword", Array: true, Description: "List of locality names (L)"}, + "file.x509.subject.organization": {Name: "file.x509.subject.organization", DataType: "keyword", Array: true, Description: "List of organizations (O) of subject."}, + "file.x509.subject.organizational_unit": {Name: "file.x509.subject.organizational_unit", DataType: "keyword", Array: true, Description: "List of organizational units (OU) of subject."}, + "file.x509.subject.state_or_province": {Name: "file.x509.subject.state_or_province", DataType: "keyword", Array: true, Description: "List of state or province names (ST, S, or P)"}, + "file.x509.version_number": {Name: "file.x509.version_number", DataType: "keyword", Description: "Version of x509 format."}, + "group.domain": {Name: "group.domain", DataType: "keyword", Description: "Name of the directory the group is a member of.\nFor example, an LDAP or Active Directory domain name."}, + "group.id": {Name: "group.id", DataType: "keyword", Description: "Unique identifier for the group on the system/platform."}, + "group.name": {Name: "group.name", DataType: "keyword", Description: "Name of the group."}, + "host.architecture": {Name: "host.architecture", DataType: "keyword", Description: "Operating system architecture."}, + "host.boot.id": {Name: "host.boot.id", DataType: "keyword", Description: "Linux boot uuid taken from /proc/sys/kernel/random/boot_id. Note the boot_id value from /proc may or may not be the same in containers as on the host. Some container runtimes will bind mount a new boot_id value onto the proc file in each container."}, + "host.cpu.usage": {Name: "host.cpu.usage", DataType: "scaled_float", Description: "Percent CPU used which is normalized by the number of CPU cores and it ranges from 0 to 1.\nScaling factor: 1000.\nFor example: For a two core host, this value should be the average of the two cores, between 0 and 1."}, + "host.disk.read.bytes": {Name: "host.disk.read.bytes", DataType: "long", Description: "The total number of bytes (gauge) read successfully (aggregated from all disks) since the last metric collection."}, + "host.disk.write.bytes": {Name: "host.disk.write.bytes", DataType: "long", Description: "The total number of bytes (gauge) written successfully (aggregated from all disks) since the last metric collection."}, + "host.domain": {Name: "host.domain", DataType: "keyword", Description: "Name of the domain of which the host is a member.\nFor 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."}, + "host.geo.city_name": {Name: "host.geo.city_name", DataType: "keyword", Description: "City name."}, + "host.geo.continent_code": {Name: "host.geo.continent_code", DataType: "keyword", Description: "Two-letter code representing continent's name."}, + "host.geo.continent_name": {Name: "host.geo.continent_name", DataType: "keyword", Description: "Name of the continent."}, + "host.geo.country_iso_code": {Name: "host.geo.country_iso_code", DataType: "keyword", Description: "Country ISO code."}, + "host.geo.country_name": {Name: "host.geo.country_name", DataType: "keyword", Description: "Country name."}, + "host.geo.location": {Name: "host.geo.location", DataType: "geo_point", Description: "Longitude and latitude."}, + "host.geo.name": {Name: "host.geo.name", DataType: "keyword", Description: "User-defined description of a location, at the level of granularity they care about.\nCould be the name of their data centers, the floor number, if this describes a local physical entity, city names.\nNot typically used in automated geolocation."}, + "host.geo.postal_code": {Name: "host.geo.postal_code", DataType: "keyword", Description: "Postal code associated with the location.\nValues appropriate for this field may also be known as a postcode or ZIP code and will vary widely from country to country."}, + "host.geo.region_iso_code": {Name: "host.geo.region_iso_code", DataType: "keyword", Description: "Region ISO code."}, + "host.geo.region_name": {Name: "host.geo.region_name", DataType: "keyword", Description: "Region name."}, + "host.geo.timezone": {Name: "host.geo.timezone", DataType: "keyword", Description: "The time zone of the location, such as IANA time zone name."}, + "host.hostname": {Name: "host.hostname", DataType: "keyword", Description: "Hostname of the host.\nIt normally contains what the `hostname` command returns on the host machine."}, + "host.id": {Name: "host.id", DataType: "keyword", Description: "Unique host id.\nAs hostname is not always unique, use values that are meaningful in your environment.\nExample: The current usage of `beat.name`."}, + "host.ip": {Name: "host.ip", DataType: "ip", Array: true, Description: "Host ip addresses."}, + "host.mac": {Name: "host.mac", DataType: "keyword", Array: true, Pattern: "^[A-F0-9]{2}(-[A-F0-9]{2}){5,}$", Description: "Host MAC addresses.\nThe notation format from RFC 7042 is suggested: Each octet (that is, 8-bit byte) is represented by two [uppercase] hexadecimal digits giving the value of the octet as an unsigned integer. Successive octets are separated by a hyphen."}, + "host.name": {Name: "host.name", DataType: "keyword", Description: "Name of the host.\nIt can contain what hostname returns on Unix systems, the fully qualified domain name (FQDN), or a name specified by the user. The recommended value is the lowercase FQDN of the host."}, + "host.network.egress.bytes": {Name: "host.network.egress.bytes", DataType: "long", Description: "The number of bytes (gauge) sent out on all network interfaces by the host since the last metric collection."}, + "host.network.egress.packets": {Name: "host.network.egress.packets", DataType: "long", Description: "The number of packets (gauge) sent out on all network interfaces by the host since the last metric collection."}, + "host.network.ingress.bytes": {Name: "host.network.ingress.bytes", DataType: "long", Description: "The number of bytes received (gauge) on all network interfaces by the host since the last metric collection."}, + "host.network.ingress.packets": {Name: "host.network.ingress.packets", DataType: "long", Description: "The number of packets (gauge) received on all network interfaces by the host since the last metric collection."}, + "host.os.family": {Name: "host.os.family", DataType: "keyword", Description: "OS family (such as redhat, debian, freebsd, windows)."}, + "host.os.full": {Name: "host.os.full", DataType: "keyword", Description: "Operating system name, including the version or code name."}, + "host.os.kernel": {Name: "host.os.kernel", DataType: "keyword", Description: "Operating system kernel version as a raw string."}, + "host.os.name": {Name: "host.os.name", DataType: "keyword", Description: "Operating system name, without the version."}, + "host.os.platform": {Name: "host.os.platform", DataType: "keyword", Description: "Operating system platform (such centos, ubuntu, windows)."}, + "host.os.type": {Name: "host.os.type", DataType: "keyword", Pattern: "(?:android|ios|linux|macos|unix|windows)", Description: "Use the `os.type` field to categorize the operating system into one of the broad commercial families.\nIf the OS you're dealing with is not listed as an expected value, the field should not be populated. Please let us know by opening an issue with ECS, to propose its addition."}, + "host.os.version": {Name: "host.os.version", DataType: "keyword", Description: "Operating system version as a raw string."}, + "host.pid_ns_ino": {Name: "host.pid_ns_ino", DataType: "keyword", Description: "This is the inode number of the namespace in the namespace file system (nsfs). Unsigned int inum in include/linux/ns_common.h."}, + "host.risk.calculated_level": {Name: "host.risk.calculated_level", DataType: "keyword", Description: "A risk classification level calculated by an internal system as part of entity analytics and entity risk scoring."}, + "host.risk.calculated_score": {Name: "host.risk.calculated_score", DataType: "float", Description: "A risk classification score calculated by an internal system as part of entity analytics and entity risk scoring."}, + "host.risk.calculated_score_norm": {Name: "host.risk.calculated_score_norm", DataType: "float", Description: "A risk classification score calculated by an internal system as part of entity analytics and entity risk scoring, and normalized to a range of 0 to 100."}, + "host.risk.static_level": {Name: "host.risk.static_level", DataType: "keyword", Description: "A risk classification level obtained from outside the system, such as from some external Threat Intelligence Platform."}, + "host.risk.static_score": {Name: "host.risk.static_score", DataType: "float", Description: "A risk classification score obtained from outside the system, such as from some external Threat Intelligence Platform."}, + "host.risk.static_score_norm": {Name: "host.risk.static_score_norm", DataType: "float", Description: "A risk classification score obtained from outside the system, such as from some external Threat Intelligence Platform, and normalized to a range of 0 to 100."}, + "host.type": {Name: "host.type", DataType: "keyword", Description: "Type of host.\nFor 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."}, + "host.uptime": {Name: "host.uptime", DataType: "long", Description: "Seconds the host has been up."}, + "http.request.body.bytes": {Name: "http.request.body.bytes", DataType: "long", Description: "Size in bytes of the request body."}, + "http.request.body.content": {Name: "http.request.body.content", DataType: "wildcard", Description: "The full HTTP request body."}, + "http.request.bytes": {Name: "http.request.bytes", DataType: "long", Description: "Total size in bytes of the request (body and headers)."}, + "http.request.id": {Name: "http.request.id", DataType: "keyword", Description: "A unique identifier for each HTTP request to correlate logs between clients and servers in transactions.\nThe id may be contained in a non-standard HTTP header, such as `X-Request-ID` or `X-Correlation-ID`."}, + "http.request.method": {Name: "http.request.method", DataType: "keyword", Description: "HTTP request method.\nThe value should retain its casing from the original event. For example, `GET`, `get`, and `GeT` are all considered valid values for this field."}, + "http.request.mime_type": {Name: "http.request.mime_type", DataType: "keyword", Description: "Mime type of the body of the request.\nThis value must only be populated based on the content of the request body, not on the `Content-Type` header. Comparing the mime type of a request with the request's Content-Type header can be helpful in detecting threats or misconfigured clients."}, + "http.request.referrer": {Name: "http.request.referrer", DataType: "keyword", Description: "Referrer for this HTTP request."}, + "http.response.body.bytes": {Name: "http.response.body.bytes", DataType: "long", Description: "Size in bytes of the response body."}, + "http.response.body.content": {Name: "http.response.body.content", DataType: "wildcard", Description: "The full HTTP response body."}, + "http.response.bytes": {Name: "http.response.bytes", DataType: "long", Description: "Total size in bytes of the response (body and headers)."}, + "http.response.mime_type": {Name: "http.response.mime_type", DataType: "keyword", Description: "Mime type of the body of the response.\nThis value must only be populated based on the content of the response body, not on the `Content-Type` header. Comparing the mime type of a response with the response's Content-Type header can be helpful in detecting misconfigured servers."}, + "http.response.status_code": {Name: "http.response.status_code", DataType: "long", Description: "HTTP response status code."}, + "http.version": {Name: "http.version", DataType: "keyword", Description: "HTTP version."}, + "labels": {Name: "labels", DataType: "object", Description: "Custom key/value pairs.\nCan be used to add meta information to events. Should not contain nested objects. All values are stored as keyword.\nExample: `docker` and `k8s` labels."}, + "log.file.path": {Name: "log.file.path", DataType: "keyword", Description: "Full path to the log file this event came from, including the file name. It should include the drive letter, when appropriate.\nIf the event wasn't read from a log file, do not populate this field."}, + "log.level": {Name: "log.level", DataType: "keyword", Description: "Original log level of the log event.\nIf 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).\nSome examples are `warn`, `err`, `i`, `informational`."}, + "log.logger": {Name: "log.logger", DataType: "keyword", Description: "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."}, + "log.origin.file.line": {Name: "log.origin.file.line", DataType: "long", Description: "The line number of the file containing the source code which originated the log event."}, + "log.origin.file.name": {Name: "log.origin.file.name", DataType: "keyword", Description: "The name of the file containing the source code which originated the log event.\nNote that this field is not meant to capture the log file. The correct field to capture the log file is `log.file.path`."}, + "log.origin.function": {Name: "log.origin.function", DataType: "keyword", Description: "The name of the function or method which originated the log event."}, + "log.syslog": {Name: "log.syslog", DataType: "object", Description: "The Syslog metadata of the event, if the event was transmitted via Syslog. Please see RFCs 5424 or 3164."}, + "log.syslog.appname": {Name: "log.syslog.appname", DataType: "keyword", Description: "The device or application that originated the Syslog message, if available."}, + "log.syslog.facility.code": {Name: "log.syslog.facility.code", DataType: "long", Description: "The Syslog numeric facility of the log event, if available.\nAccording to RFCs 5424 and 3164, this value should be an integer between 0 and 23."}, + "log.syslog.facility.name": {Name: "log.syslog.facility.name", DataType: "keyword", Description: "The Syslog text-based facility of the log event, if available."}, + "log.syslog.hostname": {Name: "log.syslog.hostname", DataType: "keyword", Description: "The hostname, FQDN, or IP of the machine that originally sent the Syslog message. This is sourced from the hostname field of the syslog header. Depending on the environment, this value may be different from the host that handled the event, especially if the host handling the events is acting as a collector."}, + "log.syslog.msgid": {Name: "log.syslog.msgid", DataType: "keyword", Description: "An identifier for the type of Syslog message, if available. Only applicable for RFC 5424 messages."}, + "log.syslog.priority": {Name: "log.syslog.priority", DataType: "long", Description: "Syslog numeric priority of the event, if available.\nAccording to RFCs 5424 and 3164, the priority is 8 * facility + severity. This number is therefore expected to contain a value between 0 and 191."}, + "log.syslog.procid": {Name: "log.syslog.procid", DataType: "keyword", Description: "The process name or ID that originated the Syslog message, if available."}, + "log.syslog.severity.code": {Name: "log.syslog.severity.code", DataType: "long", Description: "The Syslog numeric severity of the log event, if available.\nIf 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`."}, + "log.syslog.severity.name": {Name: "log.syslog.severity.name", DataType: "keyword", Description: "The Syslog numeric severity of the log event, if available.\nIf 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`."}, + "log.syslog.structured_data": {Name: "log.syslog.structured_data", DataType: "flattened", Description: "Structured data expressed in RFC 5424 messages, if available. These are key-value pairs formed from the structured data portion of the syslog message, as defined in RFC 5424 Section 6.3."}, + "log.syslog.version": {Name: "log.syslog.version", DataType: "keyword", Description: "The version of the Syslog protocol specification. Only applicable for RFC 5424 messages."}, + "message": {Name: "message", DataType: "match_only_text", Description: "For log events the message field contains the log message, optimized for viewing in a log viewer.\nFor structured logs without an original message field, other fields can be concatenated to form a human-readable summary of the event.\nIf multiple messages exist, they can be combined into one message."}, + "network.application": {Name: "network.application", DataType: "keyword", Description: "When a specific application or service is identified from network connection details (source/dest IPs, ports, certificates, or wire format), this field captures the application's or service's name.\nFor example, the original event identifies the network connection being from a specific web service in a `https` network connection, like `facebook` or `twitter`.\nThe field value must be normalized to lowercase for querying."}, + "network.bytes": {Name: "network.bytes", DataType: "long", Description: "Total bytes transferred in both directions.\nIf `source.bytes` and `destination.bytes` are known, `network.bytes` is their sum."}, + "network.community_id": {Name: "network.community_id", DataType: "keyword", Description: "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.\nLearn more at https://github.com/corelight/community-id-spec."}, + "network.direction": {Name: "network.direction", DataType: "keyword", Pattern: "(?:egress|external|inbound|ingress|internal|outbound|unknown)", Description: "Direction of the network traffic.\nWhen mapping events from a host-based monitoring context, populate this field from the host's point of view, using the values \"ingress\" or \"egress\".\nWhen mapping events from a network or perimeter-based monitoring context, populate this field from the point of view of the network perimeter, using the values \"inbound\", \"outbound\", \"internal\" or \"external\".\nNote that \"internal\" is not crossing perimeter boundaries, and is meant to describe communication between two hosts within the perimeter. Note also that \"external\" is meant to describe traffic between two hosts that are external to the perimeter. This could for example be useful for ISPs or VPN service providers."}, + "network.forwarded_ip": {Name: "network.forwarded_ip", DataType: "ip", Description: "Host IP address when the source IP address is the proxy."}, + "network.iana_number": {Name: "network.iana_number", DataType: "keyword", Description: "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."}, + "network.inner": {Name: "network.inner", DataType: "object", Description: "Network.inner fields are added in addition to network.vlan fields to describe the innermost VLAN when q-in-q VLAN tagging is present. Allowed fields include vlan.id and vlan.name. Inner vlan fields are typically used when sending traffic with multiple 802.1q encapsulations to a network sensor (e.g. Zeek, Wireshark.)"}, + "network.inner.vlan.id": {Name: "network.inner.vlan.id", DataType: "keyword", Description: "VLAN ID as reported by the observer."}, + "network.inner.vlan.name": {Name: "network.inner.vlan.name", DataType: "keyword", Description: "Optional VLAN name as reported by the observer."}, + "network.name": {Name: "network.name", DataType: "keyword", Description: "Name given by operators to sections of their network."}, + "network.packets": {Name: "network.packets", DataType: "long", Description: "Total packets transferred in both directions.\nIf `source.packets` and `destination.packets` are known, `network.packets` is their sum."}, + "network.protocol": {Name: "network.protocol", DataType: "keyword", Description: "In the OSI Model this would be the Application Layer protocol. For example, `http`, `dns`, or `ssh`.\nThe field value must be normalized to lowercase for querying."}, + "network.transport": {Name: "network.transport", DataType: "keyword", Description: "Same as network.iana_number, but instead using the Keyword name of the transport layer (udp, tcp, ipv6-icmp, etc.)\nThe field value must be normalized to lowercase for querying."}, + "network.type": {Name: "network.type", DataType: "keyword", Description: "In the OSI Model this would be the Network Layer. ipv4, ipv6, ipsec, pim, etc\nThe field value must be normalized to lowercase for querying."}, + "network.vlan.id": {Name: "network.vlan.id", DataType: "keyword", Description: "VLAN ID as reported by the observer."}, + "network.vlan.name": {Name: "network.vlan.name", DataType: "keyword", Description: "Optional VLAN name as reported by the observer."}, + "observer.egress": {Name: "observer.egress", DataType: "object", Description: "Observer.egress holds information like interface number and name, vlan, and zone information to classify egress traffic. Single armed monitoring such as a network sensor on a span port should only use observer.ingress to categorize traffic."}, + "observer.egress.interface.alias": {Name: "observer.egress.interface.alias", DataType: "keyword", Description: "Interface alias as reported by the system, typically used in firewall implementations for e.g. inside, outside, or dmz logical interface naming."}, + "observer.egress.interface.id": {Name: "observer.egress.interface.id", DataType: "keyword", Description: "Interface ID as reported by an observer (typically SNMP interface ID)."}, + "observer.egress.interface.name": {Name: "observer.egress.interface.name", DataType: "keyword", Description: "Interface name as reported by the system."}, + "observer.egress.vlan.id": {Name: "observer.egress.vlan.id", DataType: "keyword", Description: "VLAN ID as reported by the observer."}, + "observer.egress.vlan.name": {Name: "observer.egress.vlan.name", DataType: "keyword", Description: "Optional VLAN name as reported by the observer."}, + "observer.egress.zone": {Name: "observer.egress.zone", DataType: "keyword", Description: "Network zone of outbound traffic as reported by the observer to categorize the destination area of egress traffic, e.g. Internal, External, DMZ, HR, Legal, etc."}, + "observer.geo.city_name": {Name: "observer.geo.city_name", DataType: "keyword", Description: "City name."}, + "observer.geo.continent_code": {Name: "observer.geo.continent_code", DataType: "keyword", Description: "Two-letter code representing continent's name."}, + "observer.geo.continent_name": {Name: "observer.geo.continent_name", DataType: "keyword", Description: "Name of the continent."}, + "observer.geo.country_iso_code": {Name: "observer.geo.country_iso_code", DataType: "keyword", Description: "Country ISO code."}, + "observer.geo.country_name": {Name: "observer.geo.country_name", DataType: "keyword", Description: "Country name."}, + "observer.geo.location": {Name: "observer.geo.location", DataType: "geo_point", Description: "Longitude and latitude."}, + "observer.geo.name": {Name: "observer.geo.name", DataType: "keyword", Description: "User-defined description of a location, at the level of granularity they care about.\nCould be the name of their data centers, the floor number, if this describes a local physical entity, city names.\nNot typically used in automated geolocation."}, + "observer.geo.postal_code": {Name: "observer.geo.postal_code", DataType: "keyword", Description: "Postal code associated with the location.\nValues appropriate for this field may also be known as a postcode or ZIP code and will vary widely from country to country."}, + "observer.geo.region_iso_code": {Name: "observer.geo.region_iso_code", DataType: "keyword", Description: "Region ISO code."}, + "observer.geo.region_name": {Name: "observer.geo.region_name", DataType: "keyword", Description: "Region name."}, + "observer.geo.timezone": {Name: "observer.geo.timezone", DataType: "keyword", Description: "The time zone of the location, such as IANA time zone name."}, + "observer.hostname": {Name: "observer.hostname", DataType: "keyword", Description: "Hostname of the observer."}, + "observer.ingress": {Name: "observer.ingress", DataType: "object", Description: "Observer.ingress holds information like interface number and name, vlan, and zone information to classify ingress traffic. Single armed monitoring such as a network sensor on a span port should only use observer.ingress to categorize traffic."}, + "observer.ingress.interface.alias": {Name: "observer.ingress.interface.alias", DataType: "keyword", Description: "Interface alias as reported by the system, typically used in firewall implementations for e.g. inside, outside, or dmz logical interface naming."}, + "observer.ingress.interface.id": {Name: "observer.ingress.interface.id", DataType: "keyword", Description: "Interface ID as reported by an observer (typically SNMP interface ID)."}, + "observer.ingress.interface.name": {Name: "observer.ingress.interface.name", DataType: "keyword", Description: "Interface name as reported by the system."}, + "observer.ingress.vlan.id": {Name: "observer.ingress.vlan.id", DataType: "keyword", Description: "VLAN ID as reported by the observer."}, + "observer.ingress.vlan.name": {Name: "observer.ingress.vlan.name", DataType: "keyword", Description: "Optional VLAN name as reported by the observer."}, + "observer.ingress.zone": {Name: "observer.ingress.zone", DataType: "keyword", Description: "Network zone of incoming traffic as reported by the observer to categorize the source area of ingress traffic. e.g. internal, External, DMZ, HR, Legal, etc."}, + "observer.ip": {Name: "observer.ip", DataType: "ip", Array: true, Description: "IP addresses of the observer."}, + "observer.mac": {Name: "observer.mac", DataType: "keyword", Array: true, Pattern: "^[A-F0-9]{2}(-[A-F0-9]{2}){5,}$", Description: "MAC addresses of the observer.\nThe notation format from RFC 7042 is suggested: Each octet (that is, 8-bit byte) is represented by two [uppercase] hexadecimal digits giving the value of the octet as an unsigned integer. Successive octets are separated by a hyphen."}, + "observer.name": {Name: "observer.name", DataType: "keyword", Description: "Custom name of the observer.\nThis 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.\nIf no custom name is needed, the field can be left empty."}, + "observer.os.family": {Name: "observer.os.family", DataType: "keyword", Description: "OS family (such as redhat, debian, freebsd, windows)."}, + "observer.os.full": {Name: "observer.os.full", DataType: "keyword", Description: "Operating system name, including the version or code name."}, + "observer.os.kernel": {Name: "observer.os.kernel", DataType: "keyword", Description: "Operating system kernel version as a raw string."}, + "observer.os.name": {Name: "observer.os.name", DataType: "keyword", Description: "Operating system name, without the version."}, + "observer.os.platform": {Name: "observer.os.platform", DataType: "keyword", Description: "Operating system platform (such centos, ubuntu, windows)."}, + "observer.os.type": {Name: "observer.os.type", DataType: "keyword", Pattern: "(?:android|ios|linux|macos|unix|windows)", Description: "Use the `os.type` field to categorize the operating system into one of the broad commercial families.\nIf the OS you're dealing with is not listed as an expected value, the field should not be populated. Please let us know by opening an issue with ECS, to propose its addition."}, + "observer.os.version": {Name: "observer.os.version", DataType: "keyword", Description: "Operating system version as a raw string."}, + "observer.product": {Name: "observer.product", DataType: "keyword", Description: "The product name of the observer."}, + "observer.serial_number": {Name: "observer.serial_number", DataType: "keyword", Description: "Observer serial number."}, + "observer.type": {Name: "observer.type", DataType: "keyword", Description: "The type of the observer the data is coming from.\nThere is no predefined list of observer types. Some examples are `forwarder`, `firewall`, `ids`, `ips`, `proxy`, `poller`, `sensor`, `APM server`."}, + "observer.vendor": {Name: "observer.vendor", DataType: "keyword", Description: "Vendor name of the observer."}, + "observer.version": {Name: "observer.version", DataType: "keyword", Description: "Observer version."}, + "orchestrator.api_version": {Name: "orchestrator.api_version", DataType: "keyword", Description: "API version being used to carry out the action"}, + "orchestrator.cluster.id": {Name: "orchestrator.cluster.id", DataType: "keyword", Description: "Unique ID of the cluster."}, + "orchestrator.cluster.name": {Name: "orchestrator.cluster.name", DataType: "keyword", Description: "Name of the cluster."}, + "orchestrator.cluster.url": {Name: "orchestrator.cluster.url", DataType: "keyword", Description: "URL of the API used to manage the cluster."}, + "orchestrator.cluster.version": {Name: "orchestrator.cluster.version", DataType: "keyword", Description: "The version of the cluster."}, + "orchestrator.namespace": {Name: "orchestrator.namespace", DataType: "keyword", Description: "Namespace in which the action is taking place."}, + "orchestrator.organization": {Name: "orchestrator.organization", DataType: "keyword", Description: "Organization affected by the event (for multi-tenant orchestrator setups)."}, + "orchestrator.resource.annotation": {Name: "orchestrator.resource.annotation", DataType: "keyword", Array: true, Description: "The list of annotations added to the resource."}, + "orchestrator.resource.id": {Name: "orchestrator.resource.id", DataType: "keyword", Description: "Unique ID of the resource being acted upon."}, + "orchestrator.resource.ip": {Name: "orchestrator.resource.ip", DataType: "ip", Array: true, Description: "IP address assigned to the resource associated with the event being observed. In the case of a Kubernetes Pod, this array would contain only one element: the IP of the Pod (as opposed to the Node on which the Pod is running)."}, + "orchestrator.resource.label": {Name: "orchestrator.resource.label", DataType: "keyword", Array: true, Description: "The list of labels added to the resource."}, + "orchestrator.resource.name": {Name: "orchestrator.resource.name", DataType: "keyword", Description: "Name of the resource being acted upon."}, + "orchestrator.resource.parent.type": {Name: "orchestrator.resource.parent.type", DataType: "keyword", Description: "Type or kind of the parent resource associated with the event being observed. In Kubernetes, this will be the name of a built-in workload resource (e.g., Deployment, StatefulSet, DaemonSet)."}, + "orchestrator.resource.type": {Name: "orchestrator.resource.type", DataType: "keyword", Description: "Type of resource being acted upon."}, + "orchestrator.type": {Name: "orchestrator.type", DataType: "keyword", Description: "Orchestrator cluster type (e.g. kubernetes, nomad or cloudfoundry)."}, + "organization.id": {Name: "organization.id", DataType: "keyword", Description: "Unique identifier for the organization."}, + "organization.name": {Name: "organization.name", DataType: "keyword", Description: "Organization name."}, + "package.architecture": {Name: "package.architecture", DataType: "keyword", Description: "Package architecture."}, + "package.build_version": {Name: "package.build_version", DataType: "keyword", Description: "Additional information about the build version of the installed package.\nFor example use the commit SHA of a non-released package."}, + "package.checksum": {Name: "package.checksum", DataType: "keyword", Description: "Checksum of the installed package for verification."}, + "package.description": {Name: "package.description", DataType: "keyword", Description: "Description of the package."}, + "package.install_scope": {Name: "package.install_scope", DataType: "keyword", Description: "Indicating how the package was installed, e.g. user-local, global."}, + "package.installed": {Name: "package.installed", DataType: "date", Description: "Time when package was installed."}, + "package.license": {Name: "package.license", DataType: "keyword", Description: "License under which the package was released.\nUse a short name, e.g. the license identifier from SPDX License List where possible (https://spdx.org/licenses/)."}, + "package.name": {Name: "package.name", DataType: "keyword", Description: "Package name"}, + "package.path": {Name: "package.path", DataType: "keyword", Description: "Path where the package is installed."}, + "package.reference": {Name: "package.reference", DataType: "keyword", Description: "Home page or reference URL of the software in this package, if available."}, + "package.size": {Name: "package.size", DataType: "long", Description: "Package size in bytes."}, + "package.type": {Name: "package.type", DataType: "keyword", Description: "Type of package.\nThis should contain the package file type, rather than the package manager name. Examples: rpm, dpkg, brew, npm, gem, nupkg, jar."}, + "package.version": {Name: "package.version", DataType: "keyword", Description: "Package version"}, + "process.args": {Name: "process.args", DataType: "keyword", Array: true, Description: "Array of process arguments, starting with the absolute path to the executable.\nMay be filtered to protect sensitive information."}, + "process.args_count": {Name: "process.args_count", DataType: "long", Description: "Length of the process.args array.\nThis 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."}, + "process.code_signature.digest_algorithm": {Name: "process.code_signature.digest_algorithm", DataType: "keyword", Description: "The hashing algorithm used to sign the process.\nThis value can distinguish signatures when a file is signed multiple times by the same signer but with a different digest algorithm."}, + "process.code_signature.exists": {Name: "process.code_signature.exists", DataType: "boolean", Description: "Boolean to capture if a signature is present."}, + "process.code_signature.signing_id": {Name: "process.code_signature.signing_id", DataType: "keyword", Description: "The identifier used to sign the process.\nThis is used to identify the application manufactured by a software vendor. The field is relevant to Apple *OS only."}, + "process.code_signature.status": {Name: "process.code_signature.status", DataType: "keyword", Description: "Additional information about the certificate status.\nThis is useful for logging cryptographic errors with the certificate validity or trust status. Leave unpopulated if the validity or trust of the certificate was unchecked."}, + "process.code_signature.subject_name": {Name: "process.code_signature.subject_name", DataType: "keyword", Description: "Subject name of the code signer"}, + "process.code_signature.team_id": {Name: "process.code_signature.team_id", DataType: "keyword", Description: "The team identifier used to sign the process.\nThis is used to identify the team or vendor of a software product. The field is relevant to Apple *OS only."}, + "process.code_signature.timestamp": {Name: "process.code_signature.timestamp", DataType: "date", Description: "Date and time when the code signature was generated and signed."}, + "process.code_signature.trusted": {Name: "process.code_signature.trusted", DataType: "boolean", Description: "Stores the trust status of the certificate chain.\nValidating the trust of the certificate chain may be complicated, and this field should only be populated by tools that actively check the status."}, + "process.code_signature.valid": {Name: "process.code_signature.valid", DataType: "boolean", Description: "Boolean to capture if the digital signature is verified against the binary content.\nLeave unpopulated if a certificate was unchecked."}, + "process.command_line": {Name: "process.command_line", DataType: "wildcard", Description: "Full command line that started the process, including the absolute path to the executable, and all arguments.\nSome arguments may be filtered to protect sensitive information."}, + "process.elf.architecture": {Name: "process.elf.architecture", DataType: "keyword", Description: "Machine architecture of the ELF file."}, + "process.elf.byte_order": {Name: "process.elf.byte_order", DataType: "keyword", Description: "Byte sequence of ELF file."}, + "process.elf.cpu_type": {Name: "process.elf.cpu_type", DataType: "keyword", Description: "CPU type of the ELF file."}, + "process.elf.creation_date": {Name: "process.elf.creation_date", DataType: "date", Description: "Extracted when possible from the file's metadata. Indicates when it was built or compiled. It can also be faked by malware creators."}, + "process.elf.exports": {Name: "process.elf.exports", DataType: "flattened", Array: true, Description: "List of exported element names and types."}, + "process.elf.go_import_hash": {Name: "process.elf.go_import_hash", DataType: "keyword", Description: "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.\nThe algorithm used to calculate the Go symbol hash and a reference implementation are available [here](https://github.com/elastic/toutoumomoma)."}, + "process.elf.go_imports": {Name: "process.elf.go_imports", DataType: "flattened", Description: "List of imported Go language element names and types."}, + "process.elf.go_imports_names_entropy": {Name: "process.elf.go_imports_names_entropy", DataType: "long", Description: "Shannon entropy calculation from the list of Go imports."}, + "process.elf.go_imports_names_var_entropy": {Name: "process.elf.go_imports_names_var_entropy", DataType: "long", Description: "Variance for Shannon entropy calculation from the list of Go imports."}, + "process.elf.go_stripped": {Name: "process.elf.go_stripped", DataType: "boolean", Description: "Set to true if the file is a Go executable that has had its symbols stripped or obfuscated and false if an unobfuscated Go executable."}, + "process.elf.header.abi_version": {Name: "process.elf.header.abi_version", DataType: "keyword", Description: "Version of the ELF Application Binary Interface (ABI)."}, + "process.elf.header.class": {Name: "process.elf.header.class", DataType: "keyword", Description: "Header class of the ELF file."}, + "process.elf.header.data": {Name: "process.elf.header.data", DataType: "keyword", Description: "Data table of the ELF header."}, + "process.elf.header.entrypoint": {Name: "process.elf.header.entrypoint", DataType: "long", Description: "Header entrypoint of the ELF file."}, + "process.elf.header.object_version": {Name: "process.elf.header.object_version", DataType: "keyword", Description: "\"0x1\" for original ELF files."}, + "process.elf.header.os_abi": {Name: "process.elf.header.os_abi", DataType: "keyword", Description: "Application Binary Interface (ABI) of the Linux OS."}, + "process.elf.header.type": {Name: "process.elf.header.type", DataType: "keyword", Description: "Header type of the ELF file."}, + "process.elf.header.version": {Name: "process.elf.header.version", DataType: "keyword", Description: "Version of the ELF header."}, + "process.elf.import_hash": {Name: "process.elf.import_hash", DataType: "keyword", Description: "A hash of the imports in an ELF file. 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.\nThis is an ELF implementation of the Windows PE imphash."}, + "process.elf.imports": {Name: "process.elf.imports", DataType: "flattened", Array: true, Description: "List of imported element names and types."}, + "process.elf.imports_names_entropy": {Name: "process.elf.imports_names_entropy", DataType: "long", Description: "Shannon entropy calculation from the list of imported element names and types."}, + "process.elf.imports_names_var_entropy": {Name: "process.elf.imports_names_var_entropy", DataType: "long", Description: "Variance for Shannon entropy calculation from the list of imported element names and types."}, + "process.elf.sections": {Name: "process.elf.sections", DataType: "nested", Array: true, Description: "An array containing an object for each section of the ELF file.\nThe keys that should be present in these objects are defined by sub-fields underneath `elf.sections.*`."}, + "process.elf.sections.chi2": {Name: "process.elf.sections.chi2", DataType: "long", Description: "Chi-square probability distribution of the section."}, + "process.elf.sections.entropy": {Name: "process.elf.sections.entropy", DataType: "long", Description: "Shannon entropy calculation from the section."}, + "process.elf.sections.flags": {Name: "process.elf.sections.flags", DataType: "keyword", Description: "ELF Section List flags."}, + "process.elf.sections.name": {Name: "process.elf.sections.name", DataType: "keyword", Description: "ELF Section List name."}, + "process.elf.sections.physical_offset": {Name: "process.elf.sections.physical_offset", DataType: "keyword", Description: "ELF Section List offset."}, + "process.elf.sections.physical_size": {Name: "process.elf.sections.physical_size", DataType: "long", Description: "ELF Section List physical size."}, + "process.elf.sections.type": {Name: "process.elf.sections.type", DataType: "keyword", Description: "ELF Section List type."}, + "process.elf.sections.var_entropy": {Name: "process.elf.sections.var_entropy", DataType: "long", Description: "Variance for Shannon entropy calculation from the section."}, + "process.elf.sections.virtual_address": {Name: "process.elf.sections.virtual_address", DataType: "long", Description: "ELF Section List virtual address."}, + "process.elf.sections.virtual_size": {Name: "process.elf.sections.virtual_size", DataType: "long", Description: "ELF Section List virtual size."}, + "process.elf.segments": {Name: "process.elf.segments", DataType: "nested", Array: true, Description: "An array containing an object for each segment of the ELF file.\nThe keys that should be present in these objects are defined by sub-fields underneath `elf.segments.*`."}, + "process.elf.segments.sections": {Name: "process.elf.segments.sections", DataType: "keyword", Description: "ELF object segment sections."}, + "process.elf.segments.type": {Name: "process.elf.segments.type", DataType: "keyword", Description: "ELF object segment type."}, + "process.elf.shared_libraries": {Name: "process.elf.shared_libraries", DataType: "keyword", Array: true, Description: "List of shared libraries used by this ELF object."}, + "process.elf.telfhash": {Name: "process.elf.telfhash", DataType: "keyword", Description: "telfhash symbol hash for ELF file."}, + "process.end": {Name: "process.end", DataType: "date", Description: "The time the process ended."}, + "process.entity_id": {Name: "process.entity_id", DataType: "keyword", Description: "Unique identifier for the process.\nThe implementation of this is specified by the data source, but some examples of what could be used here are a process-generated UUID, Sysmon Process GUIDs, or a hash of some uniquely identifying components of a process.\nConstructing a globally unique identifier is a common practice to mitigate PID reuse as well as to identify a specific process over time, across multiple monitored hosts."}, + "process.entry_leader.args": {Name: "process.entry_leader.args", DataType: "keyword", Array: true, Description: "Array of process arguments, starting with the absolute path to the executable.\nMay be filtered to protect sensitive information."}, + "process.entry_leader.args_count": {Name: "process.entry_leader.args_count", DataType: "long", Description: "Length of the process.args array.\nThis 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."}, + "process.entry_leader.attested_groups.name": {Name: "process.entry_leader.attested_groups.name", DataType: "keyword", Description: "Name of the group."}, + "process.entry_leader.attested_user.id": {Name: "process.entry_leader.attested_user.id", DataType: "keyword", Description: "Unique identifier of the user."}, + "process.entry_leader.attested_user.name": {Name: "process.entry_leader.attested_user.name", DataType: "keyword", Description: "Short name or login of the user."}, + "process.entry_leader.command_line": {Name: "process.entry_leader.command_line", DataType: "wildcard", Description: "Full command line that started the process, including the absolute path to the executable, and all arguments.\nSome arguments may be filtered to protect sensitive information."}, + "process.entry_leader.entity_id": {Name: "process.entry_leader.entity_id", DataType: "keyword", Description: "Unique identifier for the process.\nThe implementation of this is specified by the data source, but some examples of what could be used here are a process-generated UUID, Sysmon Process GUIDs, or a hash of some uniquely identifying components of a process.\nConstructing a globally unique identifier is a common practice to mitigate PID reuse as well as to identify a specific process over time, across multiple monitored hosts."}, + "process.entry_leader.entry_meta.source.ip": {Name: "process.entry_leader.entry_meta.source.ip", DataType: "ip", Description: "IP address of the source (IPv4 or IPv6)."}, + "process.entry_leader.entry_meta.type": {Name: "process.entry_leader.entry_meta.type", DataType: "keyword", Description: "The entry type for the entry session leader. Values include: init(e.g systemd), sshd, ssm, kubelet, teleport, terminal, console\nNote: This field is only set on process.session_leader."}, + "process.entry_leader.executable": {Name: "process.entry_leader.executable", DataType: "keyword", Description: "Absolute path to the process executable."}, + "process.entry_leader.group.id": {Name: "process.entry_leader.group.id", DataType: "keyword", Description: "Unique identifier for the group on the system/platform."}, + "process.entry_leader.group.name": {Name: "process.entry_leader.group.name", DataType: "keyword", Description: "Name of the group."}, + "process.entry_leader.interactive": {Name: "process.entry_leader.interactive", DataType: "boolean", Description: "Whether the process is connected to an interactive shell.\nProcess interactivity is inferred from the processes file descriptors. If the character device for the controlling tty is the same as stdin and stderr for the process, the process is considered interactive.\nNote: A non-interactive process can belong to an interactive session and is simply one that does not have open file descriptors reading the controlling TTY on FD 0 (stdin) or writing to the controlling TTY on FD 2 (stderr). A backgrounded process is still considered interactive if stdin and stderr are connected to the controlling TTY."}, + "process.entry_leader.name": {Name: "process.entry_leader.name", DataType: "keyword", Description: "Process name.\nSometimes called program name or similar."}, + "process.entry_leader.parent.entity_id": {Name: "process.entry_leader.parent.entity_id", DataType: "keyword", Description: "Unique identifier for the process.\nThe implementation of this is specified by the data source, but some examples of what could be used here are a process-generated UUID, Sysmon Process GUIDs, or a hash of some uniquely identifying components of a process.\nConstructing a globally unique identifier is a common practice to mitigate PID reuse as well as to identify a specific process over time, across multiple monitored hosts."}, + "process.entry_leader.parent.pid": {Name: "process.entry_leader.parent.pid", DataType: "long", Description: "Process id."}, + "process.entry_leader.parent.session_leader.entity_id": {Name: "process.entry_leader.parent.session_leader.entity_id", DataType: "keyword", Description: "Unique identifier for the process.\nThe implementation of this is specified by the data source, but some examples of what could be used here are a process-generated UUID, Sysmon Process GUIDs, or a hash of some uniquely identifying components of a process.\nConstructing a globally unique identifier is a common practice to mitigate PID reuse as well as to identify a specific process over time, across multiple monitored hosts."}, + "process.entry_leader.parent.session_leader.pid": {Name: "process.entry_leader.parent.session_leader.pid", DataType: "long", Description: "Process id."}, + "process.entry_leader.parent.session_leader.start": {Name: "process.entry_leader.parent.session_leader.start", DataType: "date", Description: "The time the process started."}, + "process.entry_leader.parent.session_leader.vpid": {Name: "process.entry_leader.parent.session_leader.vpid", DataType: "long", Description: "Virtual process id.\nThe process id within a pid namespace. This is not necessarily unique across all processes on the host but it is unique within the process namespace that the process exists within."}, + "process.entry_leader.parent.start": {Name: "process.entry_leader.parent.start", DataType: "date", Description: "The time the process started."}, + "process.entry_leader.parent.vpid": {Name: "process.entry_leader.parent.vpid", DataType: "long", Description: "Virtual process id.\nThe process id within a pid namespace. This is not necessarily unique across all processes on the host but it is unique within the process namespace that the process exists within."}, + "process.entry_leader.pid": {Name: "process.entry_leader.pid", DataType: "long", Description: "Process id."}, + "process.entry_leader.real_group.id": {Name: "process.entry_leader.real_group.id", DataType: "keyword", Description: "Unique identifier for the group on the system/platform."}, + "process.entry_leader.real_group.name": {Name: "process.entry_leader.real_group.name", DataType: "keyword", Description: "Name of the group."}, + "process.entry_leader.real_user.id": {Name: "process.entry_leader.real_user.id", DataType: "keyword", Description: "Unique identifier of the user."}, + "process.entry_leader.real_user.name": {Name: "process.entry_leader.real_user.name", DataType: "keyword", Description: "Short name or login of the user."}, + "process.entry_leader.same_as_process": {Name: "process.entry_leader.same_as_process", DataType: "boolean", Description: "This boolean is used to identify if a leader process is the same as the top level process.\nFor example, if `process.group_leader.same_as_process = true`, it means the process event in question is the leader of its process group. Details under `process.*` like `pid` would be the same under `process.group_leader.*` The same applies for both `process.session_leader` and `process.entry_leader`.\nThis field exists to the benefit of EQL and other rule engines since it's not possible to compare equality between two fields in a single document. e.g `process.entity_id` = `process.group_leader.entity_id` (top level process is the process group leader) OR `process.entity_id` = `process.entry_leader.entity_id` (top level process is the entry session leader)\nInstead these rules could be written like: `process.group_leader.same_as_process: true` OR `process.entry_leader.same_as_process: true`\nNote: This field is only set on `process.entry_leader`, `process.session_leader` and `process.group_leader`."}, + "process.entry_leader.saved_group.id": {Name: "process.entry_leader.saved_group.id", DataType: "keyword", Description: "Unique identifier for the group on the system/platform."}, + "process.entry_leader.saved_group.name": {Name: "process.entry_leader.saved_group.name", DataType: "keyword", Description: "Name of the group."}, + "process.entry_leader.saved_user.id": {Name: "process.entry_leader.saved_user.id", DataType: "keyword", Description: "Unique identifier of the user."}, + "process.entry_leader.saved_user.name": {Name: "process.entry_leader.saved_user.name", DataType: "keyword", Description: "Short name or login of the user."}, + "process.entry_leader.start": {Name: "process.entry_leader.start", DataType: "date", Description: "The time the process started."}, + "process.entry_leader.supplemental_groups.id": {Name: "process.entry_leader.supplemental_groups.id", DataType: "keyword", Description: "Unique identifier for the group on the system/platform."}, + "process.entry_leader.supplemental_groups.name": {Name: "process.entry_leader.supplemental_groups.name", DataType: "keyword", Description: "Name of the group."}, + "process.entry_leader.tty": {Name: "process.entry_leader.tty", DataType: "object", Description: "Information about the controlling TTY device. If set, the process belongs to an interactive session."}, + "process.entry_leader.tty.char_device.major": {Name: "process.entry_leader.tty.char_device.major", DataType: "long", Description: "The major number identifies the driver associated with the device. The character device's major and minor numbers can be algorithmically combined to produce the more familiar terminal identifiers such as \"ttyS0\" and \"pts/0\". For more details, please refer to the Linux kernel documentation."}, + "process.entry_leader.tty.char_device.minor": {Name: "process.entry_leader.tty.char_device.minor", DataType: "long", Description: "The minor number is used only by the driver specified by the major number; other parts of the kernel don’t use it, and merely pass it along to the driver. It is common for a driver to control several devices; the minor number provides a way for the driver to differentiate among them."}, + "process.entry_leader.user.id": {Name: "process.entry_leader.user.id", DataType: "keyword", Description: "Unique identifier of the user."}, + "process.entry_leader.user.name": {Name: "process.entry_leader.user.name", DataType: "keyword", Description: "Short name or login of the user."}, + "process.entry_leader.vpid": {Name: "process.entry_leader.vpid", DataType: "long", Description: "Virtual process id.\nThe process id within a pid namespace. This is not necessarily unique across all processes on the host but it is unique within the process namespace that the process exists within."}, + "process.entry_leader.working_directory": {Name: "process.entry_leader.working_directory", DataType: "keyword", Description: "The working directory of the process."}, + "process.env_vars": {Name: "process.env_vars", DataType: "keyword", Array: true, Description: "Array of environment variable bindings. Captured from a snapshot of the environment at the time of execution.\nMay be filtered to protect sensitive information."}, + "process.executable": {Name: "process.executable", DataType: "keyword", Description: "Absolute path to the process executable."}, + "process.exit_code": {Name: "process.exit_code", DataType: "long", Description: "The exit code of the process, if this is a termination event.\nThe field should be absent if there is no exit code for the event (e.g. process start)."}, + "process.group_leader.args": {Name: "process.group_leader.args", DataType: "keyword", Array: true, Description: "Array of process arguments, starting with the absolute path to the executable.\nMay be filtered to protect sensitive information."}, + "process.group_leader.args_count": {Name: "process.group_leader.args_count", DataType: "long", Description: "Length of the process.args array.\nThis 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."}, + "process.group_leader.command_line": {Name: "process.group_leader.command_line", DataType: "wildcard", Description: "Full command line that started the process, including the absolute path to the executable, and all arguments.\nSome arguments may be filtered to protect sensitive information."}, + "process.group_leader.entity_id": {Name: "process.group_leader.entity_id", DataType: "keyword", Description: "Unique identifier for the process.\nThe implementation of this is specified by the data source, but some examples of what could be used here are a process-generated UUID, Sysmon Process GUIDs, or a hash of some uniquely identifying components of a process.\nConstructing a globally unique identifier is a common practice to mitigate PID reuse as well as to identify a specific process over time, across multiple monitored hosts."}, + "process.group_leader.executable": {Name: "process.group_leader.executable", DataType: "keyword", Description: "Absolute path to the process executable."}, + "process.group_leader.group.id": {Name: "process.group_leader.group.id", DataType: "keyword", Description: "Unique identifier for the group on the system/platform."}, + "process.group_leader.group.name": {Name: "process.group_leader.group.name", DataType: "keyword", Description: "Name of the group."}, + "process.group_leader.interactive": {Name: "process.group_leader.interactive", DataType: "boolean", Description: "Whether the process is connected to an interactive shell.\nProcess interactivity is inferred from the processes file descriptors. If the character device for the controlling tty is the same as stdin and stderr for the process, the process is considered interactive.\nNote: A non-interactive process can belong to an interactive session and is simply one that does not have open file descriptors reading the controlling TTY on FD 0 (stdin) or writing to the controlling TTY on FD 2 (stderr). A backgrounded process is still considered interactive if stdin and stderr are connected to the controlling TTY."}, + "process.group_leader.name": {Name: "process.group_leader.name", DataType: "keyword", Description: "Process name.\nSometimes called program name or similar."}, + "process.group_leader.pid": {Name: "process.group_leader.pid", DataType: "long", Description: "Process id."}, + "process.group_leader.real_group.id": {Name: "process.group_leader.real_group.id", DataType: "keyword", Description: "Unique identifier for the group on the system/platform."}, + "process.group_leader.real_group.name": {Name: "process.group_leader.real_group.name", DataType: "keyword", Description: "Name of the group."}, + "process.group_leader.real_user.id": {Name: "process.group_leader.real_user.id", DataType: "keyword", Description: "Unique identifier of the user."}, + "process.group_leader.real_user.name": {Name: "process.group_leader.real_user.name", DataType: "keyword", Description: "Short name or login of the user."}, + "process.group_leader.same_as_process": {Name: "process.group_leader.same_as_process", DataType: "boolean", Description: "This boolean is used to identify if a leader process is the same as the top level process.\nFor example, if `process.group_leader.same_as_process = true`, it means the process event in question is the leader of its process group. Details under `process.*` like `pid` would be the same under `process.group_leader.*` The same applies for both `process.session_leader` and `process.entry_leader`.\nThis field exists to the benefit of EQL and other rule engines since it's not possible to compare equality between two fields in a single document. e.g `process.entity_id` = `process.group_leader.entity_id` (top level process is the process group leader) OR `process.entity_id` = `process.entry_leader.entity_id` (top level process is the entry session leader)\nInstead these rules could be written like: `process.group_leader.same_as_process: true` OR `process.entry_leader.same_as_process: true`\nNote: This field is only set on `process.entry_leader`, `process.session_leader` and `process.group_leader`."}, + "process.group_leader.saved_group.id": {Name: "process.group_leader.saved_group.id", DataType: "keyword", Description: "Unique identifier for the group on the system/platform."}, + "process.group_leader.saved_group.name": {Name: "process.group_leader.saved_group.name", DataType: "keyword", Description: "Name of the group."}, + "process.group_leader.saved_user.id": {Name: "process.group_leader.saved_user.id", DataType: "keyword", Description: "Unique identifier of the user."}, + "process.group_leader.saved_user.name": {Name: "process.group_leader.saved_user.name", DataType: "keyword", Description: "Short name or login of the user."}, + "process.group_leader.start": {Name: "process.group_leader.start", DataType: "date", Description: "The time the process started."}, + "process.group_leader.supplemental_groups.id": {Name: "process.group_leader.supplemental_groups.id", DataType: "keyword", Description: "Unique identifier for the group on the system/platform."}, + "process.group_leader.supplemental_groups.name": {Name: "process.group_leader.supplemental_groups.name", DataType: "keyword", Description: "Name of the group."}, + "process.group_leader.tty": {Name: "process.group_leader.tty", DataType: "object", Description: "Information about the controlling TTY device. If set, the process belongs to an interactive session."}, + "process.group_leader.tty.char_device.major": {Name: "process.group_leader.tty.char_device.major", DataType: "long", Description: "The major number identifies the driver associated with the device. The character device's major and minor numbers can be algorithmically combined to produce the more familiar terminal identifiers such as \"ttyS0\" and \"pts/0\". For more details, please refer to the Linux kernel documentation."}, + "process.group_leader.tty.char_device.minor": {Name: "process.group_leader.tty.char_device.minor", DataType: "long", Description: "The minor number is used only by the driver specified by the major number; other parts of the kernel don’t use it, and merely pass it along to the driver. It is common for a driver to control several devices; the minor number provides a way for the driver to differentiate among them."}, + "process.group_leader.user.id": {Name: "process.group_leader.user.id", DataType: "keyword", Description: "Unique identifier of the user."}, + "process.group_leader.user.name": {Name: "process.group_leader.user.name", DataType: "keyword", Description: "Short name or login of the user."}, + "process.group_leader.vpid": {Name: "process.group_leader.vpid", DataType: "long", Description: "Virtual process id.\nThe process id within a pid namespace. This is not necessarily unique across all processes on the host but it is unique within the process namespace that the process exists within."}, + "process.group_leader.working_directory": {Name: "process.group_leader.working_directory", DataType: "keyword", Description: "The working directory of the process."}, + "process.hash.md5": {Name: "process.hash.md5", DataType: "keyword", Description: "MD5 hash."}, + "process.hash.sha1": {Name: "process.hash.sha1", DataType: "keyword", Description: "SHA1 hash."}, + "process.hash.sha256": {Name: "process.hash.sha256", DataType: "keyword", Description: "SHA256 hash."}, + "process.hash.sha384": {Name: "process.hash.sha384", DataType: "keyword", Description: "SHA384 hash."}, + "process.hash.sha512": {Name: "process.hash.sha512", DataType: "keyword", Description: "SHA512 hash."}, + "process.hash.ssdeep": {Name: "process.hash.ssdeep", DataType: "keyword", Description: "SSDEEP hash."}, + "process.hash.tlsh": {Name: "process.hash.tlsh", DataType: "keyword", Description: "TLSH hash."}, + "process.interactive": {Name: "process.interactive", DataType: "boolean", Description: "Whether the process is connected to an interactive shell.\nProcess interactivity is inferred from the processes file descriptors. If the character device for the controlling tty is the same as stdin and stderr for the process, the process is considered interactive.\nNote: A non-interactive process can belong to an interactive session and is simply one that does not have open file descriptors reading the controlling TTY on FD 0 (stdin) or writing to the controlling TTY on FD 2 (stderr). A backgrounded process is still considered interactive if stdin and stderr are connected to the controlling TTY."}, + "process.io": {Name: "process.io", DataType: "object", Description: "A chunk of input or output (IO) from a single process.\nThis field only appears on the top level process object, which is the process that wrote the output or read the input."}, + "process.io.bytes_skipped": {Name: "process.io.bytes_skipped", DataType: "object", Array: true, Description: "An array of byte offsets and lengths denoting where IO data has been skipped."}, + "process.io.bytes_skipped.length": {Name: "process.io.bytes_skipped.length", DataType: "long", Description: "The length of bytes skipped."}, + "process.io.bytes_skipped.offset": {Name: "process.io.bytes_skipped.offset", DataType: "long", Description: "The byte offset into this event's io.text (or io.bytes in the future) where length bytes were skipped."}, + "process.io.max_bytes_per_process_exceeded": {Name: "process.io.max_bytes_per_process_exceeded", DataType: "boolean", Description: "If true, the process producing the output has exceeded the max_kilobytes_per_process configuration setting."}, + "process.io.text": {Name: "process.io.text", DataType: "wildcard", Description: "A chunk of output or input sanitized to UTF-8.\nBest efforts are made to ensure complete lines are captured in these events. Assumptions should NOT be made that multiple lines will appear in the same event. TTY output may contain terminal control codes such as for cursor movement, so some string queries may not match due to terminal codes inserted between characters of a word."}, + "process.io.total_bytes_captured": {Name: "process.io.total_bytes_captured", DataType: "long", Description: "The total number of bytes captured in this event."}, + "process.io.total_bytes_skipped": {Name: "process.io.total_bytes_skipped", DataType: "long", Description: "The total number of bytes that were not captured due to implementation restrictions such as buffer size limits. Implementors should strive to ensure this value is always zero"}, + "process.io.type": {Name: "process.io.type", DataType: "keyword", Description: "The type of object on which the IO action (read or write) was taken.\nCurrently only 'tty' is supported. Other types may be added in the future for 'file' and 'socket' support."}, + "process.macho.go_import_hash": {Name: "process.macho.go_import_hash", DataType: "keyword", Description: "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.\nThe algorithm used to calculate the Go symbol hash and a reference implementation are available [here](https://github.com/elastic/toutoumomoma)."}, + "process.macho.go_imports": {Name: "process.macho.go_imports", DataType: "flattened", Description: "List of imported Go language element names and types."}, + "process.macho.go_imports_names_entropy": {Name: "process.macho.go_imports_names_entropy", DataType: "long", Description: "Shannon entropy calculation from the list of Go imports."}, + "process.macho.go_imports_names_var_entropy": {Name: "process.macho.go_imports_names_var_entropy", DataType: "long", Description: "Variance for Shannon entropy calculation from the list of Go imports."}, + "process.macho.go_stripped": {Name: "process.macho.go_stripped", DataType: "boolean", Description: "Set to true if the file is a Go executable that has had its symbols stripped or obfuscated and false if an unobfuscated Go executable."}, + "process.macho.import_hash": {Name: "process.macho.import_hash", DataType: "keyword", Description: "A hash of the imports in a Mach-O file. 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.\nThis is a synonym for symhash."}, + "process.macho.imports": {Name: "process.macho.imports", DataType: "flattened", Array: true, Description: "List of imported element names and types."}, + "process.macho.imports_names_entropy": {Name: "process.macho.imports_names_entropy", DataType: "long", Description: "Shannon entropy calculation from the list of imported element names and types."}, + "process.macho.imports_names_var_entropy": {Name: "process.macho.imports_names_var_entropy", DataType: "long", Description: "Variance for Shannon entropy calculation from the list of imported element names and types."}, + "process.macho.sections": {Name: "process.macho.sections", DataType: "nested", Array: true, Description: "An array containing an object for each section of the Mach-O file.\nThe keys that should be present in these objects are defined by sub-fields underneath `macho.sections.*`."}, + "process.macho.sections.entropy": {Name: "process.macho.sections.entropy", DataType: "long", Description: "Shannon entropy calculation from the section."}, + "process.macho.sections.name": {Name: "process.macho.sections.name", DataType: "keyword", Description: "Mach-O Section List name."}, + "process.macho.sections.physical_size": {Name: "process.macho.sections.physical_size", DataType: "long", Description: "Mach-O Section List physical size."}, + "process.macho.sections.var_entropy": {Name: "process.macho.sections.var_entropy", DataType: "long", Description: "Variance for Shannon entropy calculation from the section."}, + "process.macho.sections.virtual_size": {Name: "process.macho.sections.virtual_size", DataType: "long", Description: "Mach-O Section List virtual size. This is always the same as `physical_size`."}, + "process.macho.symhash": {Name: "process.macho.symhash", DataType: "keyword", Description: "A hash of the imports in a Mach-O file. 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.\nThis is a Mach-O implementation of the Windows PE imphash"}, + "process.name": {Name: "process.name", DataType: "keyword", Description: "Process name.\nSometimes called program name or similar."}, + "process.parent.args": {Name: "process.parent.args", DataType: "keyword", Array: true, Description: "Array of process arguments, starting with the absolute path to the executable.\nMay be filtered to protect sensitive information."}, + "process.parent.args_count": {Name: "process.parent.args_count", DataType: "long", Description: "Length of the process.args array.\nThis 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."}, + "process.parent.code_signature.digest_algorithm": {Name: "process.parent.code_signature.digest_algorithm", DataType: "keyword", Description: "The hashing algorithm used to sign the process.\nThis value can distinguish signatures when a file is signed multiple times by the same signer but with a different digest algorithm."}, + "process.parent.code_signature.exists": {Name: "process.parent.code_signature.exists", DataType: "boolean", Description: "Boolean to capture if a signature is present."}, + "process.parent.code_signature.signing_id": {Name: "process.parent.code_signature.signing_id", DataType: "keyword", Description: "The identifier used to sign the process.\nThis is used to identify the application manufactured by a software vendor. The field is relevant to Apple *OS only."}, + "process.parent.code_signature.status": {Name: "process.parent.code_signature.status", DataType: "keyword", Description: "Additional information about the certificate status.\nThis is useful for logging cryptographic errors with the certificate validity or trust status. Leave unpopulated if the validity or trust of the certificate was unchecked."}, + "process.parent.code_signature.subject_name": {Name: "process.parent.code_signature.subject_name", DataType: "keyword", Description: "Subject name of the code signer"}, + "process.parent.code_signature.team_id": {Name: "process.parent.code_signature.team_id", DataType: "keyword", Description: "The team identifier used to sign the process.\nThis is used to identify the team or vendor of a software product. The field is relevant to Apple *OS only."}, + "process.parent.code_signature.timestamp": {Name: "process.parent.code_signature.timestamp", DataType: "date", Description: "Date and time when the code signature was generated and signed."}, + "process.parent.code_signature.trusted": {Name: "process.parent.code_signature.trusted", DataType: "boolean", Description: "Stores the trust status of the certificate chain.\nValidating the trust of the certificate chain may be complicated, and this field should only be populated by tools that actively check the status."}, + "process.parent.code_signature.valid": {Name: "process.parent.code_signature.valid", DataType: "boolean", Description: "Boolean to capture if the digital signature is verified against the binary content.\nLeave unpopulated if a certificate was unchecked."}, + "process.parent.command_line": {Name: "process.parent.command_line", DataType: "wildcard", Description: "Full command line that started the process, including the absolute path to the executable, and all arguments.\nSome arguments may be filtered to protect sensitive information."}, + "process.parent.elf.architecture": {Name: "process.parent.elf.architecture", DataType: "keyword", Description: "Machine architecture of the ELF file."}, + "process.parent.elf.byte_order": {Name: "process.parent.elf.byte_order", DataType: "keyword", Description: "Byte sequence of ELF file."}, + "process.parent.elf.cpu_type": {Name: "process.parent.elf.cpu_type", DataType: "keyword", Description: "CPU type of the ELF file."}, + "process.parent.elf.creation_date": {Name: "process.parent.elf.creation_date", DataType: "date", Description: "Extracted when possible from the file's metadata. Indicates when it was built or compiled. It can also be faked by malware creators."}, + "process.parent.elf.exports": {Name: "process.parent.elf.exports", DataType: "flattened", Array: true, Description: "List of exported element names and types."}, + "process.parent.elf.go_import_hash": {Name: "process.parent.elf.go_import_hash", DataType: "keyword", Description: "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.\nThe algorithm used to calculate the Go symbol hash and a reference implementation are available [here](https://github.com/elastic/toutoumomoma)."}, + "process.parent.elf.go_imports": {Name: "process.parent.elf.go_imports", DataType: "flattened", Description: "List of imported Go language element names and types."}, + "process.parent.elf.go_imports_names_entropy": {Name: "process.parent.elf.go_imports_names_entropy", DataType: "long", Description: "Shannon entropy calculation from the list of Go imports."}, + "process.parent.elf.go_imports_names_var_entropy": {Name: "process.parent.elf.go_imports_names_var_entropy", DataType: "long", Description: "Variance for Shannon entropy calculation from the list of Go imports."}, + "process.parent.elf.go_stripped": {Name: "process.parent.elf.go_stripped", DataType: "boolean", Description: "Set to true if the file is a Go executable that has had its symbols stripped or obfuscated and false if an unobfuscated Go executable."}, + "process.parent.elf.header.abi_version": {Name: "process.parent.elf.header.abi_version", DataType: "keyword", Description: "Version of the ELF Application Binary Interface (ABI)."}, + "process.parent.elf.header.class": {Name: "process.parent.elf.header.class", DataType: "keyword", Description: "Header class of the ELF file."}, + "process.parent.elf.header.data": {Name: "process.parent.elf.header.data", DataType: "keyword", Description: "Data table of the ELF header."}, + "process.parent.elf.header.entrypoint": {Name: "process.parent.elf.header.entrypoint", DataType: "long", Description: "Header entrypoint of the ELF file."}, + "process.parent.elf.header.object_version": {Name: "process.parent.elf.header.object_version", DataType: "keyword", Description: "\"0x1\" for original ELF files."}, + "process.parent.elf.header.os_abi": {Name: "process.parent.elf.header.os_abi", DataType: "keyword", Description: "Application Binary Interface (ABI) of the Linux OS."}, + "process.parent.elf.header.type": {Name: "process.parent.elf.header.type", DataType: "keyword", Description: "Header type of the ELF file."}, + "process.parent.elf.header.version": {Name: "process.parent.elf.header.version", DataType: "keyword", Description: "Version of the ELF header."}, + "process.parent.elf.import_hash": {Name: "process.parent.elf.import_hash", DataType: "keyword", Description: "A hash of the imports in an ELF file. 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.\nThis is an ELF implementation of the Windows PE imphash."}, + "process.parent.elf.imports": {Name: "process.parent.elf.imports", DataType: "flattened", Array: true, Description: "List of imported element names and types."}, + "process.parent.elf.imports_names_entropy": {Name: "process.parent.elf.imports_names_entropy", DataType: "long", Description: "Shannon entropy calculation from the list of imported element names and types."}, + "process.parent.elf.imports_names_var_entropy": {Name: "process.parent.elf.imports_names_var_entropy", DataType: "long", Description: "Variance for Shannon entropy calculation from the list of imported element names and types."}, + "process.parent.elf.sections": {Name: "process.parent.elf.sections", DataType: "nested", Array: true, Description: "An array containing an object for each section of the ELF file.\nThe keys that should be present in these objects are defined by sub-fields underneath `elf.sections.*`."}, + "process.parent.elf.sections.chi2": {Name: "process.parent.elf.sections.chi2", DataType: "long", Description: "Chi-square probability distribution of the section."}, + "process.parent.elf.sections.entropy": {Name: "process.parent.elf.sections.entropy", DataType: "long", Description: "Shannon entropy calculation from the section."}, + "process.parent.elf.sections.flags": {Name: "process.parent.elf.sections.flags", DataType: "keyword", Description: "ELF Section List flags."}, + "process.parent.elf.sections.name": {Name: "process.parent.elf.sections.name", DataType: "keyword", Description: "ELF Section List name."}, + "process.parent.elf.sections.physical_offset": {Name: "process.parent.elf.sections.physical_offset", DataType: "keyword", Description: "ELF Section List offset."}, + "process.parent.elf.sections.physical_size": {Name: "process.parent.elf.sections.physical_size", DataType: "long", Description: "ELF Section List physical size."}, + "process.parent.elf.sections.type": {Name: "process.parent.elf.sections.type", DataType: "keyword", Description: "ELF Section List type."}, + "process.parent.elf.sections.var_entropy": {Name: "process.parent.elf.sections.var_entropy", DataType: "long", Description: "Variance for Shannon entropy calculation from the section."}, + "process.parent.elf.sections.virtual_address": {Name: "process.parent.elf.sections.virtual_address", DataType: "long", Description: "ELF Section List virtual address."}, + "process.parent.elf.sections.virtual_size": {Name: "process.parent.elf.sections.virtual_size", DataType: "long", Description: "ELF Section List virtual size."}, + "process.parent.elf.segments": {Name: "process.parent.elf.segments", DataType: "nested", Array: true, Description: "An array containing an object for each segment of the ELF file.\nThe keys that should be present in these objects are defined by sub-fields underneath `elf.segments.*`."}, + "process.parent.elf.segments.sections": {Name: "process.parent.elf.segments.sections", DataType: "keyword", Description: "ELF object segment sections."}, + "process.parent.elf.segments.type": {Name: "process.parent.elf.segments.type", DataType: "keyword", Description: "ELF object segment type."}, + "process.parent.elf.shared_libraries": {Name: "process.parent.elf.shared_libraries", DataType: "keyword", Array: true, Description: "List of shared libraries used by this ELF object."}, + "process.parent.elf.telfhash": {Name: "process.parent.elf.telfhash", DataType: "keyword", Description: "telfhash symbol hash for ELF file."}, + "process.parent.end": {Name: "process.parent.end", DataType: "date", Description: "The time the process ended."}, + "process.parent.entity_id": {Name: "process.parent.entity_id", DataType: "keyword", Description: "Unique identifier for the process.\nThe implementation of this is specified by the data source, but some examples of what could be used here are a process-generated UUID, Sysmon Process GUIDs, or a hash of some uniquely identifying components of a process.\nConstructing a globally unique identifier is a common practice to mitigate PID reuse as well as to identify a specific process over time, across multiple monitored hosts."}, + "process.parent.executable": {Name: "process.parent.executable", DataType: "keyword", Description: "Absolute path to the process executable."}, + "process.parent.exit_code": {Name: "process.parent.exit_code", DataType: "long", Description: "The exit code of the process, if this is a termination event.\nThe field should be absent if there is no exit code for the event (e.g. process start)."}, + "process.parent.group.id": {Name: "process.parent.group.id", DataType: "keyword", Description: "Unique identifier for the group on the system/platform."}, + "process.parent.group.name": {Name: "process.parent.group.name", DataType: "keyword", Description: "Name of the group."}, + "process.parent.group_leader.entity_id": {Name: "process.parent.group_leader.entity_id", DataType: "keyword", Description: "Unique identifier for the process.\nThe implementation of this is specified by the data source, but some examples of what could be used here are a process-generated UUID, Sysmon Process GUIDs, or a hash of some uniquely identifying components of a process.\nConstructing a globally unique identifier is a common practice to mitigate PID reuse as well as to identify a specific process over time, across multiple monitored hosts."}, + "process.parent.group_leader.pid": {Name: "process.parent.group_leader.pid", DataType: "long", Description: "Process id."}, + "process.parent.group_leader.start": {Name: "process.parent.group_leader.start", DataType: "date", Description: "The time the process started."}, + "process.parent.group_leader.vpid": {Name: "process.parent.group_leader.vpid", DataType: "long", Description: "Virtual process id.\nThe process id within a pid namespace. This is not necessarily unique across all processes on the host but it is unique within the process namespace that the process exists within."}, + "process.parent.hash.md5": {Name: "process.parent.hash.md5", DataType: "keyword", Description: "MD5 hash."}, + "process.parent.hash.sha1": {Name: "process.parent.hash.sha1", DataType: "keyword", Description: "SHA1 hash."}, + "process.parent.hash.sha256": {Name: "process.parent.hash.sha256", DataType: "keyword", Description: "SHA256 hash."}, + "process.parent.hash.sha384": {Name: "process.parent.hash.sha384", DataType: "keyword", Description: "SHA384 hash."}, + "process.parent.hash.sha512": {Name: "process.parent.hash.sha512", DataType: "keyword", Description: "SHA512 hash."}, + "process.parent.hash.ssdeep": {Name: "process.parent.hash.ssdeep", DataType: "keyword", Description: "SSDEEP hash."}, + "process.parent.hash.tlsh": {Name: "process.parent.hash.tlsh", DataType: "keyword", Description: "TLSH hash."}, + "process.parent.interactive": {Name: "process.parent.interactive", DataType: "boolean", Description: "Whether the process is connected to an interactive shell.\nProcess interactivity is inferred from the processes file descriptors. If the character device for the controlling tty is the same as stdin and stderr for the process, the process is considered interactive.\nNote: A non-interactive process can belong to an interactive session and is simply one that does not have open file descriptors reading the controlling TTY on FD 0 (stdin) or writing to the controlling TTY on FD 2 (stderr). A backgrounded process is still considered interactive if stdin and stderr are connected to the controlling TTY."}, + "process.parent.macho.go_import_hash": {Name: "process.parent.macho.go_import_hash", DataType: "keyword", Description: "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.\nThe algorithm used to calculate the Go symbol hash and a reference implementation are available [here](https://github.com/elastic/toutoumomoma)."}, + "process.parent.macho.go_imports": {Name: "process.parent.macho.go_imports", DataType: "flattened", Description: "List of imported Go language element names and types."}, + "process.parent.macho.go_imports_names_entropy": {Name: "process.parent.macho.go_imports_names_entropy", DataType: "long", Description: "Shannon entropy calculation from the list of Go imports."}, + "process.parent.macho.go_imports_names_var_entropy": {Name: "process.parent.macho.go_imports_names_var_entropy", DataType: "long", Description: "Variance for Shannon entropy calculation from the list of Go imports."}, + "process.parent.macho.go_stripped": {Name: "process.parent.macho.go_stripped", DataType: "boolean", Description: "Set to true if the file is a Go executable that has had its symbols stripped or obfuscated and false if an unobfuscated Go executable."}, + "process.parent.macho.import_hash": {Name: "process.parent.macho.import_hash", DataType: "keyword", Description: "A hash of the imports in a Mach-O file. 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.\nThis is a synonym for symhash."}, + "process.parent.macho.imports": {Name: "process.parent.macho.imports", DataType: "flattened", Array: true, Description: "List of imported element names and types."}, + "process.parent.macho.imports_names_entropy": {Name: "process.parent.macho.imports_names_entropy", DataType: "long", Description: "Shannon entropy calculation from the list of imported element names and types."}, + "process.parent.macho.imports_names_var_entropy": {Name: "process.parent.macho.imports_names_var_entropy", DataType: "long", Description: "Variance for Shannon entropy calculation from the list of imported element names and types."}, + "process.parent.macho.sections": {Name: "process.parent.macho.sections", DataType: "nested", Array: true, Description: "An array containing an object for each section of the Mach-O file.\nThe keys that should be present in these objects are defined by sub-fields underneath `macho.sections.*`."}, + "process.parent.macho.sections.entropy": {Name: "process.parent.macho.sections.entropy", DataType: "long", Description: "Shannon entropy calculation from the section."}, + "process.parent.macho.sections.name": {Name: "process.parent.macho.sections.name", DataType: "keyword", Description: "Mach-O Section List name."}, + "process.parent.macho.sections.physical_size": {Name: "process.parent.macho.sections.physical_size", DataType: "long", Description: "Mach-O Section List physical size."}, + "process.parent.macho.sections.var_entropy": {Name: "process.parent.macho.sections.var_entropy", DataType: "long", Description: "Variance for Shannon entropy calculation from the section."}, + "process.parent.macho.sections.virtual_size": {Name: "process.parent.macho.sections.virtual_size", DataType: "long", Description: "Mach-O Section List virtual size. This is always the same as `physical_size`."}, + "process.parent.macho.symhash": {Name: "process.parent.macho.symhash", DataType: "keyword", Description: "A hash of the imports in a Mach-O file. 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.\nThis is a Mach-O implementation of the Windows PE imphash"}, + "process.parent.name": {Name: "process.parent.name", DataType: "keyword", Description: "Process name.\nSometimes called program name or similar."}, + "process.parent.pe.architecture": {Name: "process.parent.pe.architecture", DataType: "keyword", Description: "CPU architecture target for the file."}, + "process.parent.pe.company": {Name: "process.parent.pe.company", DataType: "keyword", Description: "Internal company name of the file, provided at compile-time."}, + "process.parent.pe.description": {Name: "process.parent.pe.description", DataType: "keyword", Description: "Internal description of the file, provided at compile-time."}, + "process.parent.pe.file_version": {Name: "process.parent.pe.file_version", DataType: "keyword", Description: "Internal version of the file, provided at compile-time."}, + "process.parent.pe.go_import_hash": {Name: "process.parent.pe.go_import_hash", DataType: "keyword", Description: "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.\nThe algorithm used to calculate the Go symbol hash and a reference implementation are available [here](https://github.com/elastic/toutoumomoma)."}, + "process.parent.pe.go_imports": {Name: "process.parent.pe.go_imports", DataType: "flattened", Description: "List of imported Go language element names and types."}, + "process.parent.pe.go_imports_names_entropy": {Name: "process.parent.pe.go_imports_names_entropy", DataType: "long", Description: "Shannon entropy calculation from the list of Go imports."}, + "process.parent.pe.go_imports_names_var_entropy": {Name: "process.parent.pe.go_imports_names_var_entropy", DataType: "long", Description: "Variance for Shannon entropy calculation from the list of Go imports."}, + "process.parent.pe.go_stripped": {Name: "process.parent.pe.go_stripped", DataType: "boolean", Description: "Set to true if the file is a Go executable that has had its symbols stripped or obfuscated and false if an unobfuscated Go executable."}, + "process.parent.pe.imphash": {Name: "process.parent.pe.imphash", DataType: "keyword", Description: "A hash of the imports in a PE file. An imphash -- or 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.\nLearn more at https://www.fireeye.com/blog/threat-research/2014/01/tracking-malware-import-hashing.html."}, + "process.parent.pe.import_hash": {Name: "process.parent.pe.import_hash", DataType: "keyword", Description: "A hash of the imports in a PE file. 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.\nThis is a synonym for imphash."}, + "process.parent.pe.imports": {Name: "process.parent.pe.imports", DataType: "flattened", Array: true, Description: "List of imported element names and types."}, + "process.parent.pe.imports_names_entropy": {Name: "process.parent.pe.imports_names_entropy", DataType: "long", Description: "Shannon entropy calculation from the list of imported element names and types."}, + "process.parent.pe.imports_names_var_entropy": {Name: "process.parent.pe.imports_names_var_entropy", DataType: "long", Description: "Variance for Shannon entropy calculation from the list of imported element names and types."}, + "process.parent.pe.original_file_name": {Name: "process.parent.pe.original_file_name", DataType: "keyword", Description: "Internal name of the file, provided at compile-time."}, + "process.parent.pe.pehash": {Name: "process.parent.pe.pehash", DataType: "keyword", Description: "A hash of the PE header and data from one or more PE sections. An pehash can be used to cluster files by transforming structural information about a file into a hash value.\nLearn more at https://www.usenix.org/legacy/events/leet09/tech/full_papers/wicherski/wicherski_html/index.html."}, + "process.parent.pe.product": {Name: "process.parent.pe.product", DataType: "keyword", Description: "Internal product name of the file, provided at compile-time."}, + "process.parent.pe.sections": {Name: "process.parent.pe.sections", DataType: "nested", Array: true, Description: "An array containing an object for each section of the PE file.\nThe keys that should be present in these objects are defined by sub-fields underneath `pe.sections.*`."}, + "process.parent.pe.sections.entropy": {Name: "process.parent.pe.sections.entropy", DataType: "long", Description: "Shannon entropy calculation from the section."}, + "process.parent.pe.sections.name": {Name: "process.parent.pe.sections.name", DataType: "keyword", Description: "PE Section List name."}, + "process.parent.pe.sections.physical_size": {Name: "process.parent.pe.sections.physical_size", DataType: "long", Description: "PE Section List physical size."}, + "process.parent.pe.sections.var_entropy": {Name: "process.parent.pe.sections.var_entropy", DataType: "long", Description: "Variance for Shannon entropy calculation from the section."}, + "process.parent.pe.sections.virtual_size": {Name: "process.parent.pe.sections.virtual_size", DataType: "long", Description: "PE Section List virtual size. This is always the same as `physical_size`."}, + "process.parent.pgid": {Name: "process.parent.pgid", DataType: "long", Description: "Deprecated for removal in next major version release. This field is superseded by `process.group_leader.pid`.\nIdentifier of the group of processes the process belongs to."}, + "process.parent.pid": {Name: "process.parent.pid", DataType: "long", Description: "Process id."}, + "process.parent.real_group.id": {Name: "process.parent.real_group.id", DataType: "keyword", Description: "Unique identifier for the group on the system/platform."}, + "process.parent.real_group.name": {Name: "process.parent.real_group.name", DataType: "keyword", Description: "Name of the group."}, + "process.parent.real_user.id": {Name: "process.parent.real_user.id", DataType: "keyword", Description: "Unique identifier of the user."}, + "process.parent.real_user.name": {Name: "process.parent.real_user.name", DataType: "keyword", Description: "Short name or login of the user."}, + "process.parent.saved_group.id": {Name: "process.parent.saved_group.id", DataType: "keyword", Description: "Unique identifier for the group on the system/platform."}, + "process.parent.saved_group.name": {Name: "process.parent.saved_group.name", DataType: "keyword", Description: "Name of the group."}, + "process.parent.saved_user.id": {Name: "process.parent.saved_user.id", DataType: "keyword", Description: "Unique identifier of the user."}, + "process.parent.saved_user.name": {Name: "process.parent.saved_user.name", DataType: "keyword", Description: "Short name or login of the user."}, + "process.parent.start": {Name: "process.parent.start", DataType: "date", Description: "The time the process started."}, + "process.parent.supplemental_groups.id": {Name: "process.parent.supplemental_groups.id", DataType: "keyword", Description: "Unique identifier for the group on the system/platform."}, + "process.parent.supplemental_groups.name": {Name: "process.parent.supplemental_groups.name", DataType: "keyword", Description: "Name of the group."}, + "process.parent.thread.capabilities.effective": {Name: "process.parent.thread.capabilities.effective", DataType: "keyword", Array: true, Pattern: "^(CAP_[A-Z_]+|\\d+)$", Description: "This is the set of capabilities used by the kernel to perform permission checks for the thread."}, + "process.parent.thread.capabilities.permitted": {Name: "process.parent.thread.capabilities.permitted", DataType: "keyword", Array: true, Pattern: "^(CAP_[A-Z_]+|\\d+)$", Description: "This is a limiting superset for the effective capabilities that the thread may assume."}, + "process.parent.thread.id": {Name: "process.parent.thread.id", DataType: "long", Description: "Thread ID."}, + "process.parent.thread.name": {Name: "process.parent.thread.name", DataType: "keyword", Description: "Thread name."}, + "process.parent.title": {Name: "process.parent.title", DataType: "keyword", Description: "Process title.\nThe 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."}, + "process.parent.tty": {Name: "process.parent.tty", DataType: "object", Description: "Information about the controlling TTY device. If set, the process belongs to an interactive session."}, + "process.parent.tty.char_device.major": {Name: "process.parent.tty.char_device.major", DataType: "long", Description: "The major number identifies the driver associated with the device. The character device's major and minor numbers can be algorithmically combined to produce the more familiar terminal identifiers such as \"ttyS0\" and \"pts/0\". For more details, please refer to the Linux kernel documentation."}, + "process.parent.tty.char_device.minor": {Name: "process.parent.tty.char_device.minor", DataType: "long", Description: "The minor number is used only by the driver specified by the major number; other parts of the kernel don’t use it, and merely pass it along to the driver. It is common for a driver to control several devices; the minor number provides a way for the driver to differentiate among them."}, + "process.parent.uptime": {Name: "process.parent.uptime", DataType: "long", Description: "Seconds the process has been up."}, + "process.parent.user.id": {Name: "process.parent.user.id", DataType: "keyword", Description: "Unique identifier of the user."}, + "process.parent.user.name": {Name: "process.parent.user.name", DataType: "keyword", Description: "Short name or login of the user."}, + "process.parent.vpid": {Name: "process.parent.vpid", DataType: "long", Description: "Virtual process id.\nThe process id within a pid namespace. This is not necessarily unique across all processes on the host but it is unique within the process namespace that the process exists within."}, + "process.parent.working_directory": {Name: "process.parent.working_directory", DataType: "keyword", Description: "The working directory of the process."}, + "process.pe.architecture": {Name: "process.pe.architecture", DataType: "keyword", Description: "CPU architecture target for the file."}, + "process.pe.company": {Name: "process.pe.company", DataType: "keyword", Description: "Internal company name of the file, provided at compile-time."}, + "process.pe.description": {Name: "process.pe.description", DataType: "keyword", Description: "Internal description of the file, provided at compile-time."}, + "process.pe.file_version": {Name: "process.pe.file_version", DataType: "keyword", Description: "Internal version of the file, provided at compile-time."}, + "process.pe.go_import_hash": {Name: "process.pe.go_import_hash", DataType: "keyword", Description: "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.\nThe algorithm used to calculate the Go symbol hash and a reference implementation are available [here](https://github.com/elastic/toutoumomoma)."}, + "process.pe.go_imports": {Name: "process.pe.go_imports", DataType: "flattened", Description: "List of imported Go language element names and types."}, + "process.pe.go_imports_names_entropy": {Name: "process.pe.go_imports_names_entropy", DataType: "long", Description: "Shannon entropy calculation from the list of Go imports."}, + "process.pe.go_imports_names_var_entropy": {Name: "process.pe.go_imports_names_var_entropy", DataType: "long", Description: "Variance for Shannon entropy calculation from the list of Go imports."}, + "process.pe.go_stripped": {Name: "process.pe.go_stripped", DataType: "boolean", Description: "Set to true if the file is a Go executable that has had its symbols stripped or obfuscated and false if an unobfuscated Go executable."}, + "process.pe.imphash": {Name: "process.pe.imphash", DataType: "keyword", Description: "A hash of the imports in a PE file. An imphash -- or 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.\nLearn more at https://www.fireeye.com/blog/threat-research/2014/01/tracking-malware-import-hashing.html."}, + "process.pe.import_hash": {Name: "process.pe.import_hash", DataType: "keyword", Description: "A hash of the imports in a PE file. 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.\nThis is a synonym for imphash."}, + "process.pe.imports": {Name: "process.pe.imports", DataType: "flattened", Array: true, Description: "List of imported element names and types."}, + "process.pe.imports_names_entropy": {Name: "process.pe.imports_names_entropy", DataType: "long", Description: "Shannon entropy calculation from the list of imported element names and types."}, + "process.pe.imports_names_var_entropy": {Name: "process.pe.imports_names_var_entropy", DataType: "long", Description: "Variance for Shannon entropy calculation from the list of imported element names and types."}, + "process.pe.original_file_name": {Name: "process.pe.original_file_name", DataType: "keyword", Description: "Internal name of the file, provided at compile-time."}, + "process.pe.pehash": {Name: "process.pe.pehash", DataType: "keyword", Description: "A hash of the PE header and data from one or more PE sections. An pehash can be used to cluster files by transforming structural information about a file into a hash value.\nLearn more at https://www.usenix.org/legacy/events/leet09/tech/full_papers/wicherski/wicherski_html/index.html."}, + "process.pe.product": {Name: "process.pe.product", DataType: "keyword", Description: "Internal product name of the file, provided at compile-time."}, + "process.pe.sections": {Name: "process.pe.sections", DataType: "nested", Array: true, Description: "An array containing an object for each section of the PE file.\nThe keys that should be present in these objects are defined by sub-fields underneath `pe.sections.*`."}, + "process.pe.sections.entropy": {Name: "process.pe.sections.entropy", DataType: "long", Description: "Shannon entropy calculation from the section."}, + "process.pe.sections.name": {Name: "process.pe.sections.name", DataType: "keyword", Description: "PE Section List name."}, + "process.pe.sections.physical_size": {Name: "process.pe.sections.physical_size", DataType: "long", Description: "PE Section List physical size."}, + "process.pe.sections.var_entropy": {Name: "process.pe.sections.var_entropy", DataType: "long", Description: "Variance for Shannon entropy calculation from the section."}, + "process.pe.sections.virtual_size": {Name: "process.pe.sections.virtual_size", DataType: "long", Description: "PE Section List virtual size. This is always the same as `physical_size`."}, + "process.pgid": {Name: "process.pgid", DataType: "long", Description: "Deprecated for removal in next major version release. This field is superseded by `process.group_leader.pid`.\nIdentifier of the group of processes the process belongs to."}, + "process.pid": {Name: "process.pid", DataType: "long", Description: "Process id."}, + "process.previous.args": {Name: "process.previous.args", DataType: "keyword", Array: true, Description: "Array of process arguments, starting with the absolute path to the executable.\nMay be filtered to protect sensitive information."}, + "process.previous.args_count": {Name: "process.previous.args_count", DataType: "long", Description: "Length of the process.args array.\nThis 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."}, + "process.previous.executable": {Name: "process.previous.executable", DataType: "keyword", Description: "Absolute path to the process executable."}, + "process.real_group.id": {Name: "process.real_group.id", DataType: "keyword", Description: "Unique identifier for the group on the system/platform."}, + "process.real_group.name": {Name: "process.real_group.name", DataType: "keyword", Description: "Name of the group."}, + "process.real_user.id": {Name: "process.real_user.id", DataType: "keyword", Description: "Unique identifier of the user."}, + "process.real_user.name": {Name: "process.real_user.name", DataType: "keyword", Description: "Short name or login of the user."}, + "process.saved_group.id": {Name: "process.saved_group.id", DataType: "keyword", Description: "Unique identifier for the group on the system/platform."}, + "process.saved_group.name": {Name: "process.saved_group.name", DataType: "keyword", Description: "Name of the group."}, + "process.saved_user.id": {Name: "process.saved_user.id", DataType: "keyword", Description: "Unique identifier of the user."}, + "process.saved_user.name": {Name: "process.saved_user.name", DataType: "keyword", Description: "Short name or login of the user."}, + "process.session_leader.args": {Name: "process.session_leader.args", DataType: "keyword", Array: true, Description: "Array of process arguments, starting with the absolute path to the executable.\nMay be filtered to protect sensitive information."}, + "process.session_leader.args_count": {Name: "process.session_leader.args_count", DataType: "long", Description: "Length of the process.args array.\nThis 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."}, + "process.session_leader.command_line": {Name: "process.session_leader.command_line", DataType: "wildcard", Description: "Full command line that started the process, including the absolute path to the executable, and all arguments.\nSome arguments may be filtered to protect sensitive information."}, + "process.session_leader.entity_id": {Name: "process.session_leader.entity_id", DataType: "keyword", Description: "Unique identifier for the process.\nThe implementation of this is specified by the data source, but some examples of what could be used here are a process-generated UUID, Sysmon Process GUIDs, or a hash of some uniquely identifying components of a process.\nConstructing a globally unique identifier is a common practice to mitigate PID reuse as well as to identify a specific process over time, across multiple monitored hosts."}, + "process.session_leader.executable": {Name: "process.session_leader.executable", DataType: "keyword", Description: "Absolute path to the process executable."}, + "process.session_leader.group.id": {Name: "process.session_leader.group.id", DataType: "keyword", Description: "Unique identifier for the group on the system/platform."}, + "process.session_leader.group.name": {Name: "process.session_leader.group.name", DataType: "keyword", Description: "Name of the group."}, + "process.session_leader.interactive": {Name: "process.session_leader.interactive", DataType: "boolean", Description: "Whether the process is connected to an interactive shell.\nProcess interactivity is inferred from the processes file descriptors. If the character device for the controlling tty is the same as stdin and stderr for the process, the process is considered interactive.\nNote: A non-interactive process can belong to an interactive session and is simply one that does not have open file descriptors reading the controlling TTY on FD 0 (stdin) or writing to the controlling TTY on FD 2 (stderr). A backgrounded process is still considered interactive if stdin and stderr are connected to the controlling TTY."}, + "process.session_leader.name": {Name: "process.session_leader.name", DataType: "keyword", Description: "Process name.\nSometimes called program name or similar."}, + "process.session_leader.parent.entity_id": {Name: "process.session_leader.parent.entity_id", DataType: "keyword", Description: "Unique identifier for the process.\nThe implementation of this is specified by the data source, but some examples of what could be used here are a process-generated UUID, Sysmon Process GUIDs, or a hash of some uniquely identifying components of a process.\nConstructing a globally unique identifier is a common practice to mitigate PID reuse as well as to identify a specific process over time, across multiple monitored hosts."}, + "process.session_leader.parent.pid": {Name: "process.session_leader.parent.pid", DataType: "long", Description: "Process id."}, + "process.session_leader.parent.session_leader.entity_id": {Name: "process.session_leader.parent.session_leader.entity_id", DataType: "keyword", Description: "Unique identifier for the process.\nThe implementation of this is specified by the data source, but some examples of what could be used here are a process-generated UUID, Sysmon Process GUIDs, or a hash of some uniquely identifying components of a process.\nConstructing a globally unique identifier is a common practice to mitigate PID reuse as well as to identify a specific process over time, across multiple monitored hosts."}, + "process.session_leader.parent.session_leader.pid": {Name: "process.session_leader.parent.session_leader.pid", DataType: "long", Description: "Process id."}, + "process.session_leader.parent.session_leader.start": {Name: "process.session_leader.parent.session_leader.start", DataType: "date", Description: "The time the process started."}, + "process.session_leader.parent.session_leader.vpid": {Name: "process.session_leader.parent.session_leader.vpid", DataType: "long", Description: "Virtual process id.\nThe process id within a pid namespace. This is not necessarily unique across all processes on the host but it is unique within the process namespace that the process exists within."}, + "process.session_leader.parent.start": {Name: "process.session_leader.parent.start", DataType: "date", Description: "The time the process started."}, + "process.session_leader.parent.vpid": {Name: "process.session_leader.parent.vpid", DataType: "long", Description: "Virtual process id.\nThe process id within a pid namespace. This is not necessarily unique across all processes on the host but it is unique within the process namespace that the process exists within."}, + "process.session_leader.pid": {Name: "process.session_leader.pid", DataType: "long", Description: "Process id."}, + "process.session_leader.real_group.id": {Name: "process.session_leader.real_group.id", DataType: "keyword", Description: "Unique identifier for the group on the system/platform."}, + "process.session_leader.real_group.name": {Name: "process.session_leader.real_group.name", DataType: "keyword", Description: "Name of the group."}, + "process.session_leader.real_user.id": {Name: "process.session_leader.real_user.id", DataType: "keyword", Description: "Unique identifier of the user."}, + "process.session_leader.real_user.name": {Name: "process.session_leader.real_user.name", DataType: "keyword", Description: "Short name or login of the user."}, + "process.session_leader.same_as_process": {Name: "process.session_leader.same_as_process", DataType: "boolean", Description: "This boolean is used to identify if a leader process is the same as the top level process.\nFor example, if `process.group_leader.same_as_process = true`, it means the process event in question is the leader of its process group. Details under `process.*` like `pid` would be the same under `process.group_leader.*` The same applies for both `process.session_leader` and `process.entry_leader`.\nThis field exists to the benefit of EQL and other rule engines since it's not possible to compare equality between two fields in a single document. e.g `process.entity_id` = `process.group_leader.entity_id` (top level process is the process group leader) OR `process.entity_id` = `process.entry_leader.entity_id` (top level process is the entry session leader)\nInstead these rules could be written like: `process.group_leader.same_as_process: true` OR `process.entry_leader.same_as_process: true`\nNote: This field is only set on `process.entry_leader`, `process.session_leader` and `process.group_leader`."}, + "process.session_leader.saved_group.id": {Name: "process.session_leader.saved_group.id", DataType: "keyword", Description: "Unique identifier for the group on the system/platform."}, + "process.session_leader.saved_group.name": {Name: "process.session_leader.saved_group.name", DataType: "keyword", Description: "Name of the group."}, + "process.session_leader.saved_user.id": {Name: "process.session_leader.saved_user.id", DataType: "keyword", Description: "Unique identifier of the user."}, + "process.session_leader.saved_user.name": {Name: "process.session_leader.saved_user.name", DataType: "keyword", Description: "Short name or login of the user."}, + "process.session_leader.start": {Name: "process.session_leader.start", DataType: "date", Description: "The time the process started."}, + "process.session_leader.supplemental_groups.id": {Name: "process.session_leader.supplemental_groups.id", DataType: "keyword", Description: "Unique identifier for the group on the system/platform."}, + "process.session_leader.supplemental_groups.name": {Name: "process.session_leader.supplemental_groups.name", DataType: "keyword", Description: "Name of the group."}, + "process.session_leader.tty": {Name: "process.session_leader.tty", DataType: "object", Description: "Information about the controlling TTY device. If set, the process belongs to an interactive session."}, + "process.session_leader.tty.char_device.major": {Name: "process.session_leader.tty.char_device.major", DataType: "long", Description: "The major number identifies the driver associated with the device. The character device's major and minor numbers can be algorithmically combined to produce the more familiar terminal identifiers such as \"ttyS0\" and \"pts/0\". For more details, please refer to the Linux kernel documentation."}, + "process.session_leader.tty.char_device.minor": {Name: "process.session_leader.tty.char_device.minor", DataType: "long", Description: "The minor number is used only by the driver specified by the major number; other parts of the kernel don’t use it, and merely pass it along to the driver. It is common for a driver to control several devices; the minor number provides a way for the driver to differentiate among them."}, + "process.session_leader.user.id": {Name: "process.session_leader.user.id", DataType: "keyword", Description: "Unique identifier of the user."}, + "process.session_leader.user.name": {Name: "process.session_leader.user.name", DataType: "keyword", Description: "Short name or login of the user."}, + "process.session_leader.vpid": {Name: "process.session_leader.vpid", DataType: "long", Description: "Virtual process id.\nThe process id within a pid namespace. This is not necessarily unique across all processes on the host but it is unique within the process namespace that the process exists within."}, + "process.session_leader.working_directory": {Name: "process.session_leader.working_directory", DataType: "keyword", Description: "The working directory of the process."}, + "process.start": {Name: "process.start", DataType: "date", Description: "The time the process started."}, + "process.supplemental_groups.id": {Name: "process.supplemental_groups.id", DataType: "keyword", Description: "Unique identifier for the group on the system/platform."}, + "process.supplemental_groups.name": {Name: "process.supplemental_groups.name", DataType: "keyword", Description: "Name of the group."}, + "process.thread.capabilities.effective": {Name: "process.thread.capabilities.effective", DataType: "keyword", Array: true, Pattern: "^(CAP_[A-Z_]+|\\d+)$", Description: "This is the set of capabilities used by the kernel to perform permission checks for the thread."}, + "process.thread.capabilities.permitted": {Name: "process.thread.capabilities.permitted", DataType: "keyword", Array: true, Pattern: "^(CAP_[A-Z_]+|\\d+)$", Description: "This is a limiting superset for the effective capabilities that the thread may assume."}, + "process.thread.id": {Name: "process.thread.id", DataType: "long", Description: "Thread ID."}, + "process.thread.name": {Name: "process.thread.name", DataType: "keyword", Description: "Thread name."}, + "process.title": {Name: "process.title", DataType: "keyword", Description: "Process title.\nThe 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."}, + "process.tty": {Name: "process.tty", DataType: "object", Description: "Information about the controlling TTY device. If set, the process belongs to an interactive session."}, + "process.tty.char_device.major": {Name: "process.tty.char_device.major", DataType: "long", Description: "The major number identifies the driver associated with the device. The character device's major and minor numbers can be algorithmically combined to produce the more familiar terminal identifiers such as \"ttyS0\" and \"pts/0\". For more details, please refer to the Linux kernel documentation."}, + "process.tty.char_device.minor": {Name: "process.tty.char_device.minor", DataType: "long", Description: "The minor number is used only by the driver specified by the major number; other parts of the kernel don’t use it, and merely pass it along to the driver. It is common for a driver to control several devices; the minor number provides a way for the driver to differentiate among them."}, + "process.tty.columns": {Name: "process.tty.columns", DataType: "long", Description: "The number of character columns per line. e.g terminal width\nTerminal sizes can change, so this value reflects the maximum value for a given IO event. i.e. where event.action = 'text_output'"}, + "process.tty.rows": {Name: "process.tty.rows", DataType: "long", Description: "The number of character rows in the terminal. e.g terminal height\nTerminal sizes can change, so this value reflects the maximum value for a given IO event. i.e. where event.action = 'text_output'"}, + "process.uptime": {Name: "process.uptime", DataType: "long", Description: "Seconds the process has been up."}, + "process.user.id": {Name: "process.user.id", DataType: "keyword", Description: "Unique identifier of the user."}, + "process.user.name": {Name: "process.user.name", DataType: "keyword", Description: "Short name or login of the user."}, + "process.vpid": {Name: "process.vpid", DataType: "long", Description: "Virtual process id.\nThe process id within a pid namespace. This is not necessarily unique across all processes on the host but it is unique within the process namespace that the process exists within."}, + "process.working_directory": {Name: "process.working_directory", DataType: "keyword", Description: "The working directory of the process."}, + "registry.data.bytes": {Name: "registry.data.bytes", DataType: "keyword", Description: "Original bytes written with base64 encoding.\nFor 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."}, + "registry.data.strings": {Name: "registry.data.strings", DataType: "wildcard", Array: true, Description: "Content when writing string types.\nPopulated 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\"`)."}, + "registry.data.type": {Name: "registry.data.type", DataType: "keyword", Description: "Standard registry type for encoding contents"}, + "registry.hive": {Name: "registry.hive", DataType: "keyword", Description: "Abbreviated name for the hive."}, + "registry.key": {Name: "registry.key", DataType: "keyword", Description: "Hive-relative path of keys."}, + "registry.path": {Name: "registry.path", DataType: "keyword", Description: "Full path, including hive, key and value"}, + "registry.value": {Name: "registry.value", DataType: "keyword", Description: "Name of the value written."}, + "related.hash": {Name: "related.hash", DataType: "keyword", Array: true, Description: "All the hashes seen on your event. Populating this field, then using it to search for hashes can help in situations where you're unsure what the hash algorithm is (and therefore which key name to search)."}, + "related.hosts": {Name: "related.hosts", DataType: "keyword", Array: true, Description: "All hostnames or other host identifiers seen on your event. Example identifiers include FQDNs, domain names, workstation names, or aliases."}, + "related.ip": {Name: "related.ip", DataType: "ip", Array: true, Description: "All of the IPs seen on your event."}, + "related.user": {Name: "related.user", DataType: "keyword", Array: true, Description: "All the user names or other user identifiers seen on the event."}, + "rule.author": {Name: "rule.author", DataType: "keyword", Array: true, Description: "Name, organization, or pseudonym of the author or authors who created the rule used to generate this event."}, + "rule.category": {Name: "rule.category", DataType: "keyword", Description: "A categorization value keyword used by the entity using the rule for detection of this event."}, + "rule.description": {Name: "rule.description", DataType: "keyword", Description: "The description of the rule generating the event."}, + "rule.id": {Name: "rule.id", DataType: "keyword", Description: "A rule ID that is unique within the scope of an agent, observer, or other entity using the rule for detection of this event."}, + "rule.license": {Name: "rule.license", DataType: "keyword", Description: "Name of the license under which the rule used to generate this event is made available."}, + "rule.name": {Name: "rule.name", DataType: "keyword", Description: "The name of the rule or signature generating the event."}, + "rule.reference": {Name: "rule.reference", DataType: "keyword", Description: "Reference URL to additional information about the rule used to generate this event.\nThe 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."}, + "rule.ruleset": {Name: "rule.ruleset", DataType: "keyword", Description: "Name of the ruleset, policy, group, or parent category in which the rule used to generate this event is a member."}, + "rule.uuid": {Name: "rule.uuid", DataType: "keyword", Description: "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."}, + "rule.version": {Name: "rule.version", DataType: "keyword", Description: "The version / revision of the rule being used for analysis."}, + "server.address": {Name: "server.address", DataType: "keyword", Description: "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.\nThen it should be duplicated to `.ip` or `.domain`, depending on which one it is."}, + "server.as.number": {Name: "server.as.number", DataType: "long", Description: "Unique number allocated to the autonomous system. The autonomous system number (ASN) uniquely identifies each network on the Internet."}, + "server.as.organization.name": {Name: "server.as.organization.name", DataType: "keyword", Description: "Organization name."}, + "server.bytes": {Name: "server.bytes", DataType: "long", Description: "Bytes sent from the server to the client."}, + "server.domain": {Name: "server.domain", DataType: "keyword", Description: "The domain name of the server system.\nThis value may be a host name, a fully qualified domain name, or another host naming format. The value may derive from the original event or be added from enrichment."}, + "server.geo.city_name": {Name: "server.geo.city_name", DataType: "keyword", Description: "City name."}, + "server.geo.continent_code": {Name: "server.geo.continent_code", DataType: "keyword", Description: "Two-letter code representing continent's name."}, + "server.geo.continent_name": {Name: "server.geo.continent_name", DataType: "keyword", Description: "Name of the continent."}, + "server.geo.country_iso_code": {Name: "server.geo.country_iso_code", DataType: "keyword", Description: "Country ISO code."}, + "server.geo.country_name": {Name: "server.geo.country_name", DataType: "keyword", Description: "Country name."}, + "server.geo.location": {Name: "server.geo.location", DataType: "geo_point", Description: "Longitude and latitude."}, + "server.geo.name": {Name: "server.geo.name", DataType: "keyword", Description: "User-defined description of a location, at the level of granularity they care about.\nCould be the name of their data centers, the floor number, if this describes a local physical entity, city names.\nNot typically used in automated geolocation."}, + "server.geo.postal_code": {Name: "server.geo.postal_code", DataType: "keyword", Description: "Postal code associated with the location.\nValues appropriate for this field may also be known as a postcode or ZIP code and will vary widely from country to country."}, + "server.geo.region_iso_code": {Name: "server.geo.region_iso_code", DataType: "keyword", Description: "Region ISO code."}, + "server.geo.region_name": {Name: "server.geo.region_name", DataType: "keyword", Description: "Region name."}, + "server.geo.timezone": {Name: "server.geo.timezone", DataType: "keyword", Description: "The time zone of the location, such as IANA time zone name."}, + "server.ip": {Name: "server.ip", DataType: "ip", Description: "IP address of the server (IPv4 or IPv6)."}, + "server.mac": {Name: "server.mac", DataType: "keyword", Pattern: "^[A-F0-9]{2}(-[A-F0-9]{2}){5,}$", Description: "MAC address of the server.\nThe notation format from RFC 7042 is suggested: Each octet (that is, 8-bit byte) is represented by two [uppercase] hexadecimal digits giving the value of the octet as an unsigned integer. Successive octets are separated by a hyphen."}, + "server.nat.ip": {Name: "server.nat.ip", DataType: "ip", Description: "Translated ip of destination based NAT sessions (e.g. internet to private DMZ)\nTypically used with load balancers, firewalls, or routers."}, + "server.nat.port": {Name: "server.nat.port", DataType: "long", Description: "Translated port of destination based NAT sessions (e.g. internet to private DMZ)\nTypically used with load balancers, firewalls, or routers."}, + "server.packets": {Name: "server.packets", DataType: "long", Description: "Packets sent from the server to the client."}, + "server.port": {Name: "server.port", DataType: "long", Description: "Port of the server."}, + "server.registered_domain": {Name: "server.registered_domain", DataType: "keyword", Description: "The highest registered server domain, stripped of the subdomain.\nFor example, the registered domain for \"foo.example.com\" is \"example.com\".\nThis 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\"."}, + "server.subdomain": {Name: "server.subdomain", DataType: "keyword", Description: "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.\nFor 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."}, + "server.top_level_domain": {Name: "server.top_level_domain", DataType: "keyword", Description: "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\".\nThis 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\"."}, + "server.user.domain": {Name: "server.user.domain", DataType: "keyword", Description: "Name of the directory the user is a member of.\nFor example, an LDAP or Active Directory domain name."}, + "server.user.email": {Name: "server.user.email", DataType: "keyword", Description: "User email address."}, + "server.user.full_name": {Name: "server.user.full_name", DataType: "keyword", Description: "User's full name, if available."}, + "server.user.group.domain": {Name: "server.user.group.domain", DataType: "keyword", Description: "Name of the directory the group is a member of.\nFor example, an LDAP or Active Directory domain name."}, + "server.user.group.id": {Name: "server.user.group.id", DataType: "keyword", Description: "Unique identifier for the group on the system/platform."}, + "server.user.group.name": {Name: "server.user.group.name", DataType: "keyword", Description: "Name of the group."}, + "server.user.hash": {Name: "server.user.hash", DataType: "keyword", Description: "Unique user hash to correlate information for a user in anonymized form.\nUseful if `user.id` or `user.name` contain confidential information and cannot be used."}, + "server.user.id": {Name: "server.user.id", DataType: "keyword", Description: "Unique identifier of the user."}, + "server.user.name": {Name: "server.user.name", DataType: "keyword", Description: "Short name or login of the user."}, + "server.user.roles": {Name: "server.user.roles", DataType: "keyword", Array: true, Description: "Array of user roles at the time of the event."}, + "service.address": {Name: "service.address", DataType: "keyword", Description: "Address where data about this service was collected from.\nThis should be a URI, network address (ipv4:port or [ipv6]:port) or a resource path (sockets)."}, + "service.environment": {Name: "service.environment", DataType: "keyword", Description: "Identifies the environment where the service is running.\nIf the same service runs in different environments (production, staging, QA, development, etc.), the environment can identify other instances of the same service. Can also group services and applications from the same environment."}, + "service.ephemeral_id": {Name: "service.ephemeral_id", DataType: "keyword", Description: "Ephemeral identifier of this service (if one exists).\nThis id normally changes across restarts, but `service.id` does not."}, + "service.id": {Name: "service.id", DataType: "keyword", Description: "Unique identifier of the running service. If the service is comprised of many nodes, the `service.id` should be the same for all nodes.\nThis 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.\nNote 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."}, + "service.name": {Name: "service.name", DataType: "keyword", Description: "Name of the service data is collected from.\nThe 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.\nIn 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."}, + "service.node.name": {Name: "service.node.name", DataType: "keyword", Description: "Name of a service node.\nThis 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.\nIn 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."}, + "service.node.role": {Name: "service.node.role", DataType: "keyword", Description: "Deprecated for removal in next major version release. This field will be superseded by `node.roles`.\nRole of a service node.\nThis allows for distinction between different running roles of the same service.\nIn the case of Kibana, the `service.node.role` could be `ui` or `background_tasks`.\nIn the case of Elasticsearch, the `service.node.role` could be `master` or `data`.\nOther services could use this to distinguish between a `web` and `worker` role running as part of the service."}, + "service.node.roles": {Name: "service.node.roles", DataType: "keyword", Array: true, Description: "Roles of a service node.\nThis allows for distinction between different running roles of the same service.\nIn the case of Kibana, the `service.node.role` could be `ui` or `background_tasks` or both.\nIn the case of Elasticsearch, the `service.node.role` could be `master` or `data` or both.\nOther services could use this to distinguish between a `web` and `worker` role running as part of the service."}, + "service.origin.address": {Name: "service.origin.address", DataType: "keyword", Description: "Address where data about this service was collected from.\nThis should be a URI, network address (ipv4:port or [ipv6]:port) or a resource path (sockets)."}, + "service.origin.environment": {Name: "service.origin.environment", DataType: "keyword", Description: "Identifies the environment where the service is running.\nIf the same service runs in different environments (production, staging, QA, development, etc.), the environment can identify other instances of the same service. Can also group services and applications from the same environment."}, + "service.origin.ephemeral_id": {Name: "service.origin.ephemeral_id", DataType: "keyword", Description: "Ephemeral identifier of this service (if one exists).\nThis id normally changes across restarts, but `service.id` does not."}, + "service.origin.id": {Name: "service.origin.id", DataType: "keyword", Description: "Unique identifier of the running service. If the service is comprised of many nodes, the `service.id` should be the same for all nodes.\nThis 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.\nNote 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."}, + "service.origin.name": {Name: "service.origin.name", DataType: "keyword", Description: "Name of the service data is collected from.\nThe 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.\nIn 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."}, + "service.origin.node.name": {Name: "service.origin.node.name", DataType: "keyword", Description: "Name of a service node.\nThis 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.\nIn 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."}, + "service.origin.node.role": {Name: "service.origin.node.role", DataType: "keyword", Description: "Deprecated for removal in next major version release. This field will be superseded by `node.roles`.\nRole of a service node.\nThis allows for distinction between different running roles of the same service.\nIn the case of Kibana, the `service.node.role` could be `ui` or `background_tasks`.\nIn the case of Elasticsearch, the `service.node.role` could be `master` or `data`.\nOther services could use this to distinguish between a `web` and `worker` role running as part of the service."}, + "service.origin.node.roles": {Name: "service.origin.node.roles", DataType: "keyword", Array: true, Description: "Roles of a service node.\nThis allows for distinction between different running roles of the same service.\nIn the case of Kibana, the `service.node.role` could be `ui` or `background_tasks` or both.\nIn the case of Elasticsearch, the `service.node.role` could be `master` or `data` or both.\nOther services could use this to distinguish between a `web` and `worker` role running as part of the service."}, + "service.origin.state": {Name: "service.origin.state", DataType: "keyword", Description: "Current state of the service."}, + "service.origin.type": {Name: "service.origin.type", DataType: "keyword", Description: "The type of the service data is collected from.\nThe type can be used to group and correlate logs and metrics from one service type.\nExample: If logs or metrics are collected from Elasticsearch, `service.type` would be `elasticsearch`."}, + "service.origin.version": {Name: "service.origin.version", DataType: "keyword", Description: "Version of the service the data was collected from.\nThis allows to look at a data set only for a specific version of a service."}, + "service.state": {Name: "service.state", DataType: "keyword", Description: "Current state of the service."}, + "service.target.address": {Name: "service.target.address", DataType: "keyword", Description: "Address where data about this service was collected from.\nThis should be a URI, network address (ipv4:port or [ipv6]:port) or a resource path (sockets)."}, + "service.target.environment": {Name: "service.target.environment", DataType: "keyword", Description: "Identifies the environment where the service is running.\nIf the same service runs in different environments (production, staging, QA, development, etc.), the environment can identify other instances of the same service. Can also group services and applications from the same environment."}, + "service.target.ephemeral_id": {Name: "service.target.ephemeral_id", DataType: "keyword", Description: "Ephemeral identifier of this service (if one exists).\nThis id normally changes across restarts, but `service.id` does not."}, + "service.target.id": {Name: "service.target.id", DataType: "keyword", Description: "Unique identifier of the running service. If the service is comprised of many nodes, the `service.id` should be the same for all nodes.\nThis 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.\nNote 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."}, + "service.target.name": {Name: "service.target.name", DataType: "keyword", Description: "Name of the service data is collected from.\nThe 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.\nIn 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."}, + "service.target.node.name": {Name: "service.target.node.name", DataType: "keyword", Description: "Name of a service node.\nThis 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.\nIn 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."}, + "service.target.node.role": {Name: "service.target.node.role", DataType: "keyword", Description: "Deprecated for removal in next major version release. This field will be superseded by `node.roles`.\nRole of a service node.\nThis allows for distinction between different running roles of the same service.\nIn the case of Kibana, the `service.node.role` could be `ui` or `background_tasks`.\nIn the case of Elasticsearch, the `service.node.role` could be `master` or `data`.\nOther services could use this to distinguish between a `web` and `worker` role running as part of the service."}, + "service.target.node.roles": {Name: "service.target.node.roles", DataType: "keyword", Array: true, Description: "Roles of a service node.\nThis allows for distinction between different running roles of the same service.\nIn the case of Kibana, the `service.node.role` could be `ui` or `background_tasks` or both.\nIn the case of Elasticsearch, the `service.node.role` could be `master` or `data` or both.\nOther services could use this to distinguish between a `web` and `worker` role running as part of the service."}, + "service.target.state": {Name: "service.target.state", DataType: "keyword", Description: "Current state of the service."}, + "service.target.type": {Name: "service.target.type", DataType: "keyword", Description: "The type of the service data is collected from.\nThe type can be used to group and correlate logs and metrics from one service type.\nExample: If logs or metrics are collected from Elasticsearch, `service.type` would be `elasticsearch`."}, + "service.target.version": {Name: "service.target.version", DataType: "keyword", Description: "Version of the service the data was collected from.\nThis allows to look at a data set only for a specific version of a service."}, + "service.type": {Name: "service.type", DataType: "keyword", Description: "The type of the service data is collected from.\nThe type can be used to group and correlate logs and metrics from one service type.\nExample: If logs or metrics are collected from Elasticsearch, `service.type` would be `elasticsearch`."}, + "service.version": {Name: "service.version", DataType: "keyword", Description: "Version of the service the data was collected from.\nThis allows to look at a data set only for a specific version of a service."}, + "source.address": {Name: "source.address", DataType: "keyword", Description: "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.\nThen it should be duplicated to `.ip` or `.domain`, depending on which one it is."}, + "source.as.number": {Name: "source.as.number", DataType: "long", Description: "Unique number allocated to the autonomous system. The autonomous system number (ASN) uniquely identifies each network on the Internet."}, + "source.as.organization.name": {Name: "source.as.organization.name", DataType: "keyword", Description: "Organization name."}, + "source.bytes": {Name: "source.bytes", DataType: "long", Description: "Bytes sent from the source to the destination."}, + "source.domain": {Name: "source.domain", DataType: "keyword", Description: "The domain name of the source system.\nThis value may be a host name, a fully qualified domain name, or another host naming format. The value may derive from the original event or be added from enrichment."}, + "source.geo.city_name": {Name: "source.geo.city_name", DataType: "keyword", Description: "City name."}, + "source.geo.continent_code": {Name: "source.geo.continent_code", DataType: "keyword", Description: "Two-letter code representing continent's name."}, + "source.geo.continent_name": {Name: "source.geo.continent_name", DataType: "keyword", Description: "Name of the continent."}, + "source.geo.country_iso_code": {Name: "source.geo.country_iso_code", DataType: "keyword", Description: "Country ISO code."}, + "source.geo.country_name": {Name: "source.geo.country_name", DataType: "keyword", Description: "Country name."}, + "source.geo.location": {Name: "source.geo.location", DataType: "geo_point", Description: "Longitude and latitude."}, + "source.geo.name": {Name: "source.geo.name", DataType: "keyword", Description: "User-defined description of a location, at the level of granularity they care about.\nCould be the name of their data centers, the floor number, if this describes a local physical entity, city names.\nNot typically used in automated geolocation."}, + "source.geo.postal_code": {Name: "source.geo.postal_code", DataType: "keyword", Description: "Postal code associated with the location.\nValues appropriate for this field may also be known as a postcode or ZIP code and will vary widely from country to country."}, + "source.geo.region_iso_code": {Name: "source.geo.region_iso_code", DataType: "keyword", Description: "Region ISO code."}, + "source.geo.region_name": {Name: "source.geo.region_name", DataType: "keyword", Description: "Region name."}, + "source.geo.timezone": {Name: "source.geo.timezone", DataType: "keyword", Description: "The time zone of the location, such as IANA time zone name."}, + "source.ip": {Name: "source.ip", DataType: "ip", Description: "IP address of the source (IPv4 or IPv6)."}, + "source.mac": {Name: "source.mac", DataType: "keyword", Pattern: "^[A-F0-9]{2}(-[A-F0-9]{2}){5,}$", Description: "MAC address of the source.\nThe notation format from RFC 7042 is suggested: Each octet (that is, 8-bit byte) is represented by two [uppercase] hexadecimal digits giving the value of the octet as an unsigned integer. Successive octets are separated by a hyphen."}, + "source.nat.ip": {Name: "source.nat.ip", DataType: "ip", Description: "Translated ip of source based NAT sessions (e.g. internal client to internet)\nTypically connections traversing load balancers, firewalls, or routers."}, + "source.nat.port": {Name: "source.nat.port", DataType: "long", Description: "Translated port of source based NAT sessions. (e.g. internal client to internet)\nTypically used with load balancers, firewalls, or routers."}, + "source.packets": {Name: "source.packets", DataType: "long", Description: "Packets sent from the source to the destination."}, + "source.port": {Name: "source.port", DataType: "long", Description: "Port of the source."}, + "source.registered_domain": {Name: "source.registered_domain", DataType: "keyword", Description: "The highest registered source domain, stripped of the subdomain.\nFor example, the registered domain for \"foo.example.com\" is \"example.com\".\nThis 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\"."}, + "source.subdomain": {Name: "source.subdomain", DataType: "keyword", Description: "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.\nFor 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."}, + "source.top_level_domain": {Name: "source.top_level_domain", DataType: "keyword", Description: "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\".\nThis 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\"."}, + "source.user.domain": {Name: "source.user.domain", DataType: "keyword", Description: "Name of the directory the user is a member of.\nFor example, an LDAP or Active Directory domain name."}, + "source.user.email": {Name: "source.user.email", DataType: "keyword", Description: "User email address."}, + "source.user.full_name": {Name: "source.user.full_name", DataType: "keyword", Description: "User's full name, if available."}, + "source.user.group.domain": {Name: "source.user.group.domain", DataType: "keyword", Description: "Name of the directory the group is a member of.\nFor example, an LDAP or Active Directory domain name."}, + "source.user.group.id": {Name: "source.user.group.id", DataType: "keyword", Description: "Unique identifier for the group on the system/platform."}, + "source.user.group.name": {Name: "source.user.group.name", DataType: "keyword", Description: "Name of the group."}, + "source.user.hash": {Name: "source.user.hash", DataType: "keyword", Description: "Unique user hash to correlate information for a user in anonymized form.\nUseful if `user.id` or `user.name` contain confidential information and cannot be used."}, + "source.user.id": {Name: "source.user.id", DataType: "keyword", Description: "Unique identifier of the user."}, + "source.user.name": {Name: "source.user.name", DataType: "keyword", Description: "Short name or login of the user."}, + "source.user.roles": {Name: "source.user.roles", DataType: "keyword", Array: true, Description: "Array of user roles at the time of the event."}, + "span.id": {Name: "span.id", DataType: "keyword", Description: "Unique identifier of the span within the scope of its trace.\nA span represents an operation within a transaction, such as a request to another service, or a database query."}, + "tags": {Name: "tags", DataType: "keyword", Array: true, Description: "List of keywords used to tag each event."}, + "threat.enrichments": {Name: "threat.enrichments", DataType: "nested", Array: true, Description: "A list of associated indicators objects enriching the event, and the context of that association/enrichment."}, + "threat.enrichments.indicator": {Name: "threat.enrichments.indicator", DataType: "object", Description: "Object containing associated indicators enriching the event."}, + "threat.enrichments.indicator.as.number": {Name: "threat.enrichments.indicator.as.number", DataType: "long", Description: "Unique number allocated to the autonomous system. The autonomous system number (ASN) uniquely identifies each network on the Internet."}, + "threat.enrichments.indicator.as.organization.name": {Name: "threat.enrichments.indicator.as.organization.name", DataType: "keyword", Description: "Organization name."}, + "threat.enrichments.indicator.confidence": {Name: "threat.enrichments.indicator.confidence", DataType: "keyword", Pattern: "(?:High|Low|Medium|None|Not Specified)", Description: "Identifies the vendor-neutral confidence rating using the None/Low/Medium/High scale defined in Appendix A of the STIX 2.1 framework. Vendor-specific confidence scales may be added as custom fields."}, + "threat.enrichments.indicator.description": {Name: "threat.enrichments.indicator.description", DataType: "keyword", Description: "Describes the type of action conducted by the threat."}, + "threat.enrichments.indicator.email.address": {Name: "threat.enrichments.indicator.email.address", DataType: "keyword", Description: "Identifies a threat indicator as an email address (irrespective of direction)."}, + "threat.enrichments.indicator.file.accessed": {Name: "threat.enrichments.indicator.file.accessed", DataType: "date", Description: "Last time the file was accessed.\nNote that not all filesystems keep track of access time."}, + "threat.enrichments.indicator.file.attributes": {Name: "threat.enrichments.indicator.file.attributes", DataType: "keyword", Array: true, Description: "Array of file attributes.\nAttributes 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."}, + "threat.enrichments.indicator.file.code_signature.digest_algorithm": {Name: "threat.enrichments.indicator.file.code_signature.digest_algorithm", DataType: "keyword", Description: "The hashing algorithm used to sign the process.\nThis value can distinguish signatures when a file is signed multiple times by the same signer but with a different digest algorithm."}, + "threat.enrichments.indicator.file.code_signature.exists": {Name: "threat.enrichments.indicator.file.code_signature.exists", DataType: "boolean", Description: "Boolean to capture if a signature is present."}, + "threat.enrichments.indicator.file.code_signature.signing_id": {Name: "threat.enrichments.indicator.file.code_signature.signing_id", DataType: "keyword", Description: "The identifier used to sign the process.\nThis is used to identify the application manufactured by a software vendor. The field is relevant to Apple *OS only."}, + "threat.enrichments.indicator.file.code_signature.status": {Name: "threat.enrichments.indicator.file.code_signature.status", DataType: "keyword", Description: "Additional information about the certificate status.\nThis is useful for logging cryptographic errors with the certificate validity or trust status. Leave unpopulated if the validity or trust of the certificate was unchecked."}, + "threat.enrichments.indicator.file.code_signature.subject_name": {Name: "threat.enrichments.indicator.file.code_signature.subject_name", DataType: "keyword", Description: "Subject name of the code signer"}, + "threat.enrichments.indicator.file.code_signature.team_id": {Name: "threat.enrichments.indicator.file.code_signature.team_id", DataType: "keyword", Description: "The team identifier used to sign the process.\nThis is used to identify the team or vendor of a software product. The field is relevant to Apple *OS only."}, + "threat.enrichments.indicator.file.code_signature.timestamp": {Name: "threat.enrichments.indicator.file.code_signature.timestamp", DataType: "date", Description: "Date and time when the code signature was generated and signed."}, + "threat.enrichments.indicator.file.code_signature.trusted": {Name: "threat.enrichments.indicator.file.code_signature.trusted", DataType: "boolean", Description: "Stores the trust status of the certificate chain.\nValidating the trust of the certificate chain may be complicated, and this field should only be populated by tools that actively check the status."}, + "threat.enrichments.indicator.file.code_signature.valid": {Name: "threat.enrichments.indicator.file.code_signature.valid", DataType: "boolean", Description: "Boolean to capture if the digital signature is verified against the binary content.\nLeave unpopulated if a certificate was unchecked."}, + "threat.enrichments.indicator.file.created": {Name: "threat.enrichments.indicator.file.created", DataType: "date", Description: "File creation time.\nNote that not all filesystems store the creation time."}, + "threat.enrichments.indicator.file.ctime": {Name: "threat.enrichments.indicator.file.ctime", DataType: "date", Description: "Last time the file attributes or metadata changed.\nNote 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."}, + "threat.enrichments.indicator.file.device": {Name: "threat.enrichments.indicator.file.device", DataType: "keyword", Description: "Device that is the source of the file."}, + "threat.enrichments.indicator.file.directory": {Name: "threat.enrichments.indicator.file.directory", DataType: "keyword", Description: "Directory where the file is located. It should include the drive letter, when appropriate."}, + "threat.enrichments.indicator.file.drive_letter": {Name: "threat.enrichments.indicator.file.drive_letter", DataType: "keyword", Description: "Drive letter where the file is located. This field is only relevant on Windows.\nThe value should be uppercase, and not include the colon."}, + "threat.enrichments.indicator.file.elf.architecture": {Name: "threat.enrichments.indicator.file.elf.architecture", DataType: "keyword", Description: "Machine architecture of the ELF file."}, + "threat.enrichments.indicator.file.elf.byte_order": {Name: "threat.enrichments.indicator.file.elf.byte_order", DataType: "keyword", Description: "Byte sequence of ELF file."}, + "threat.enrichments.indicator.file.elf.cpu_type": {Name: "threat.enrichments.indicator.file.elf.cpu_type", DataType: "keyword", Description: "CPU type of the ELF file."}, + "threat.enrichments.indicator.file.elf.creation_date": {Name: "threat.enrichments.indicator.file.elf.creation_date", DataType: "date", Description: "Extracted when possible from the file's metadata. Indicates when it was built or compiled. It can also be faked by malware creators."}, + "threat.enrichments.indicator.file.elf.exports": {Name: "threat.enrichments.indicator.file.elf.exports", DataType: "flattened", Array: true, Description: "List of exported element names and types."}, + "threat.enrichments.indicator.file.elf.go_import_hash": {Name: "threat.enrichments.indicator.file.elf.go_import_hash", DataType: "keyword", Description: "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.\nThe algorithm used to calculate the Go symbol hash and a reference implementation are available [here](https://github.com/elastic/toutoumomoma)."}, + "threat.enrichments.indicator.file.elf.go_imports": {Name: "threat.enrichments.indicator.file.elf.go_imports", DataType: "flattened", Description: "List of imported Go language element names and types."}, + "threat.enrichments.indicator.file.elf.go_imports_names_entropy": {Name: "threat.enrichments.indicator.file.elf.go_imports_names_entropy", DataType: "long", Description: "Shannon entropy calculation from the list of Go imports."}, + "threat.enrichments.indicator.file.elf.go_imports_names_var_entropy": {Name: "threat.enrichments.indicator.file.elf.go_imports_names_var_entropy", DataType: "long", Description: "Variance for Shannon entropy calculation from the list of Go imports."}, + "threat.enrichments.indicator.file.elf.go_stripped": {Name: "threat.enrichments.indicator.file.elf.go_stripped", DataType: "boolean", Description: "Set to true if the file is a Go executable that has had its symbols stripped or obfuscated and false if an unobfuscated Go executable."}, + "threat.enrichments.indicator.file.elf.header.abi_version": {Name: "threat.enrichments.indicator.file.elf.header.abi_version", DataType: "keyword", Description: "Version of the ELF Application Binary Interface (ABI)."}, + "threat.enrichments.indicator.file.elf.header.class": {Name: "threat.enrichments.indicator.file.elf.header.class", DataType: "keyword", Description: "Header class of the ELF file."}, + "threat.enrichments.indicator.file.elf.header.data": {Name: "threat.enrichments.indicator.file.elf.header.data", DataType: "keyword", Description: "Data table of the ELF header."}, + "threat.enrichments.indicator.file.elf.header.entrypoint": {Name: "threat.enrichments.indicator.file.elf.header.entrypoint", DataType: "long", Description: "Header entrypoint of the ELF file."}, + "threat.enrichments.indicator.file.elf.header.object_version": {Name: "threat.enrichments.indicator.file.elf.header.object_version", DataType: "keyword", Description: "\"0x1\" for original ELF files."}, + "threat.enrichments.indicator.file.elf.header.os_abi": {Name: "threat.enrichments.indicator.file.elf.header.os_abi", DataType: "keyword", Description: "Application Binary Interface (ABI) of the Linux OS."}, + "threat.enrichments.indicator.file.elf.header.type": {Name: "threat.enrichments.indicator.file.elf.header.type", DataType: "keyword", Description: "Header type of the ELF file."}, + "threat.enrichments.indicator.file.elf.header.version": {Name: "threat.enrichments.indicator.file.elf.header.version", DataType: "keyword", Description: "Version of the ELF header."}, + "threat.enrichments.indicator.file.elf.import_hash": {Name: "threat.enrichments.indicator.file.elf.import_hash", DataType: "keyword", Description: "A hash of the imports in an ELF file. 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.\nThis is an ELF implementation of the Windows PE imphash."}, + "threat.enrichments.indicator.file.elf.imports": {Name: "threat.enrichments.indicator.file.elf.imports", DataType: "flattened", Array: true, Description: "List of imported element names and types."}, + "threat.enrichments.indicator.file.elf.imports_names_entropy": {Name: "threat.enrichments.indicator.file.elf.imports_names_entropy", DataType: "long", Description: "Shannon entropy calculation from the list of imported element names and types."}, + "threat.enrichments.indicator.file.elf.imports_names_var_entropy": {Name: "threat.enrichments.indicator.file.elf.imports_names_var_entropy", DataType: "long", Description: "Variance for Shannon entropy calculation from the list of imported element names and types."}, + "threat.enrichments.indicator.file.elf.sections": {Name: "threat.enrichments.indicator.file.elf.sections", DataType: "nested", Array: true, Description: "An array containing an object for each section of the ELF file.\nThe keys that should be present in these objects are defined by sub-fields underneath `elf.sections.*`."}, + "threat.enrichments.indicator.file.elf.sections.chi2": {Name: "threat.enrichments.indicator.file.elf.sections.chi2", DataType: "long", Description: "Chi-square probability distribution of the section."}, + "threat.enrichments.indicator.file.elf.sections.entropy": {Name: "threat.enrichments.indicator.file.elf.sections.entropy", DataType: "long", Description: "Shannon entropy calculation from the section."}, + "threat.enrichments.indicator.file.elf.sections.flags": {Name: "threat.enrichments.indicator.file.elf.sections.flags", DataType: "keyword", Description: "ELF Section List flags."}, + "threat.enrichments.indicator.file.elf.sections.name": {Name: "threat.enrichments.indicator.file.elf.sections.name", DataType: "keyword", Description: "ELF Section List name."}, + "threat.enrichments.indicator.file.elf.sections.physical_offset": {Name: "threat.enrichments.indicator.file.elf.sections.physical_offset", DataType: "keyword", Description: "ELF Section List offset."}, + "threat.enrichments.indicator.file.elf.sections.physical_size": {Name: "threat.enrichments.indicator.file.elf.sections.physical_size", DataType: "long", Description: "ELF Section List physical size."}, + "threat.enrichments.indicator.file.elf.sections.type": {Name: "threat.enrichments.indicator.file.elf.sections.type", DataType: "keyword", Description: "ELF Section List type."}, + "threat.enrichments.indicator.file.elf.sections.var_entropy": {Name: "threat.enrichments.indicator.file.elf.sections.var_entropy", DataType: "long", Description: "Variance for Shannon entropy calculation from the section."}, + "threat.enrichments.indicator.file.elf.sections.virtual_address": {Name: "threat.enrichments.indicator.file.elf.sections.virtual_address", DataType: "long", Description: "ELF Section List virtual address."}, + "threat.enrichments.indicator.file.elf.sections.virtual_size": {Name: "threat.enrichments.indicator.file.elf.sections.virtual_size", DataType: "long", Description: "ELF Section List virtual size."}, + "threat.enrichments.indicator.file.elf.segments": {Name: "threat.enrichments.indicator.file.elf.segments", DataType: "nested", Array: true, Description: "An array containing an object for each segment of the ELF file.\nThe keys that should be present in these objects are defined by sub-fields underneath `elf.segments.*`."}, + "threat.enrichments.indicator.file.elf.segments.sections": {Name: "threat.enrichments.indicator.file.elf.segments.sections", DataType: "keyword", Description: "ELF object segment sections."}, + "threat.enrichments.indicator.file.elf.segments.type": {Name: "threat.enrichments.indicator.file.elf.segments.type", DataType: "keyword", Description: "ELF object segment type."}, + "threat.enrichments.indicator.file.elf.shared_libraries": {Name: "threat.enrichments.indicator.file.elf.shared_libraries", DataType: "keyword", Array: true, Description: "List of shared libraries used by this ELF object."}, + "threat.enrichments.indicator.file.elf.telfhash": {Name: "threat.enrichments.indicator.file.elf.telfhash", DataType: "keyword", Description: "telfhash symbol hash for ELF file."}, + "threat.enrichments.indicator.file.extension": {Name: "threat.enrichments.indicator.file.extension", DataType: "keyword", Description: "File extension, excluding the leading dot.\nNote that when the file name has multiple extensions (example.tar.gz), only the last one should be captured (\"gz\", not \"tar.gz\")."}, + "threat.enrichments.indicator.file.fork_name": {Name: "threat.enrichments.indicator.file.fork_name", DataType: "keyword", Description: "A fork is additional data associated with a filesystem object.\nOn Linux, a resource fork is used to store additional data with a filesystem object. A file always has at least one fork for the data portion, and additional forks may exist.\nOn NTFS, this is analogous to an Alternate Data Stream (ADS), and the default data stream for a file is just called $DATA. Zone.Identifier is commonly used by Windows to track contents downloaded from the Internet. An ADS is typically of the form: `C:\\path\\to\\filename.extension:some_fork_name`, and `some_fork_name` is the value that should populate `fork_name`. `filename.extension` should populate `file.name`, and `extension` should populate `file.extension`. The full path, `file.path`, will include the fork name."}, + "threat.enrichments.indicator.file.gid": {Name: "threat.enrichments.indicator.file.gid", DataType: "keyword", Description: "Primary group ID (GID) of the file."}, + "threat.enrichments.indicator.file.group": {Name: "threat.enrichments.indicator.file.group", DataType: "keyword", Description: "Primary group name of the file."}, + "threat.enrichments.indicator.file.hash.md5": {Name: "threat.enrichments.indicator.file.hash.md5", DataType: "keyword", Description: "MD5 hash."}, + "threat.enrichments.indicator.file.hash.sha1": {Name: "threat.enrichments.indicator.file.hash.sha1", DataType: "keyword", Description: "SHA1 hash."}, + "threat.enrichments.indicator.file.hash.sha256": {Name: "threat.enrichments.indicator.file.hash.sha256", DataType: "keyword", Description: "SHA256 hash."}, + "threat.enrichments.indicator.file.hash.sha384": {Name: "threat.enrichments.indicator.file.hash.sha384", DataType: "keyword", Description: "SHA384 hash."}, + "threat.enrichments.indicator.file.hash.sha512": {Name: "threat.enrichments.indicator.file.hash.sha512", DataType: "keyword", Description: "SHA512 hash."}, + "threat.enrichments.indicator.file.hash.ssdeep": {Name: "threat.enrichments.indicator.file.hash.ssdeep", DataType: "keyword", Description: "SSDEEP hash."}, + "threat.enrichments.indicator.file.hash.tlsh": {Name: "threat.enrichments.indicator.file.hash.tlsh", DataType: "keyword", Description: "TLSH hash."}, + "threat.enrichments.indicator.file.inode": {Name: "threat.enrichments.indicator.file.inode", DataType: "keyword", Description: "Inode representing the file in the filesystem."}, + "threat.enrichments.indicator.file.mime_type": {Name: "threat.enrichments.indicator.file.mime_type", DataType: "keyword", Description: "MIME type should identify the format of the file or stream of bytes using https://www.iana.org/assignments/media-types/media-types.xhtml[IANA official types], where possible. When more than one type is applicable, the most specific type should be used."}, + "threat.enrichments.indicator.file.mode": {Name: "threat.enrichments.indicator.file.mode", DataType: "keyword", Description: "Mode of the file in octal representation."}, + "threat.enrichments.indicator.file.mtime": {Name: "threat.enrichments.indicator.file.mtime", DataType: "date", Description: "Last time the file content was modified."}, + "threat.enrichments.indicator.file.name": {Name: "threat.enrichments.indicator.file.name", DataType: "keyword", Description: "Name of the file including the extension, without the directory."}, + "threat.enrichments.indicator.file.owner": {Name: "threat.enrichments.indicator.file.owner", DataType: "keyword", Description: "File owner's username."}, + "threat.enrichments.indicator.file.path": {Name: "threat.enrichments.indicator.file.path", DataType: "keyword", Description: "Full path to the file, including the file name. It should include the drive letter, when appropriate."}, + "threat.enrichments.indicator.file.pe.architecture": {Name: "threat.enrichments.indicator.file.pe.architecture", DataType: "keyword", Description: "CPU architecture target for the file."}, + "threat.enrichments.indicator.file.pe.company": {Name: "threat.enrichments.indicator.file.pe.company", DataType: "keyword", Description: "Internal company name of the file, provided at compile-time."}, + "threat.enrichments.indicator.file.pe.description": {Name: "threat.enrichments.indicator.file.pe.description", DataType: "keyword", Description: "Internal description of the file, provided at compile-time."}, + "threat.enrichments.indicator.file.pe.file_version": {Name: "threat.enrichments.indicator.file.pe.file_version", DataType: "keyword", Description: "Internal version of the file, provided at compile-time."}, + "threat.enrichments.indicator.file.pe.go_import_hash": {Name: "threat.enrichments.indicator.file.pe.go_import_hash", DataType: "keyword", Description: "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.\nThe algorithm used to calculate the Go symbol hash and a reference implementation are available [here](https://github.com/elastic/toutoumomoma)."}, + "threat.enrichments.indicator.file.pe.go_imports": {Name: "threat.enrichments.indicator.file.pe.go_imports", DataType: "flattened", Description: "List of imported Go language element names and types."}, + "threat.enrichments.indicator.file.pe.go_imports_names_entropy": {Name: "threat.enrichments.indicator.file.pe.go_imports_names_entropy", DataType: "long", Description: "Shannon entropy calculation from the list of Go imports."}, + "threat.enrichments.indicator.file.pe.go_imports_names_var_entropy": {Name: "threat.enrichments.indicator.file.pe.go_imports_names_var_entropy", DataType: "long", Description: "Variance for Shannon entropy calculation from the list of Go imports."}, + "threat.enrichments.indicator.file.pe.go_stripped": {Name: "threat.enrichments.indicator.file.pe.go_stripped", DataType: "boolean", Description: "Set to true if the file is a Go executable that has had its symbols stripped or obfuscated and false if an unobfuscated Go executable."}, + "threat.enrichments.indicator.file.pe.imphash": {Name: "threat.enrichments.indicator.file.pe.imphash", DataType: "keyword", Description: "A hash of the imports in a PE file. An imphash -- or 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.\nLearn more at https://www.fireeye.com/blog/threat-research/2014/01/tracking-malware-import-hashing.html."}, + "threat.enrichments.indicator.file.pe.import_hash": {Name: "threat.enrichments.indicator.file.pe.import_hash", DataType: "keyword", Description: "A hash of the imports in a PE file. 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.\nThis is a synonym for imphash."}, + "threat.enrichments.indicator.file.pe.imports": {Name: "threat.enrichments.indicator.file.pe.imports", DataType: "flattened", Array: true, Description: "List of imported element names and types."}, + "threat.enrichments.indicator.file.pe.imports_names_entropy": {Name: "threat.enrichments.indicator.file.pe.imports_names_entropy", DataType: "long", Description: "Shannon entropy calculation from the list of imported element names and types."}, + "threat.enrichments.indicator.file.pe.imports_names_var_entropy": {Name: "threat.enrichments.indicator.file.pe.imports_names_var_entropy", DataType: "long", Description: "Variance for Shannon entropy calculation from the list of imported element names and types."}, + "threat.enrichments.indicator.file.pe.original_file_name": {Name: "threat.enrichments.indicator.file.pe.original_file_name", DataType: "keyword", Description: "Internal name of the file, provided at compile-time."}, + "threat.enrichments.indicator.file.pe.pehash": {Name: "threat.enrichments.indicator.file.pe.pehash", DataType: "keyword", Description: "A hash of the PE header and data from one or more PE sections. An pehash can be used to cluster files by transforming structural information about a file into a hash value.\nLearn more at https://www.usenix.org/legacy/events/leet09/tech/full_papers/wicherski/wicherski_html/index.html."}, + "threat.enrichments.indicator.file.pe.product": {Name: "threat.enrichments.indicator.file.pe.product", DataType: "keyword", Description: "Internal product name of the file, provided at compile-time."}, + "threat.enrichments.indicator.file.pe.sections": {Name: "threat.enrichments.indicator.file.pe.sections", DataType: "nested", Array: true, Description: "An array containing an object for each section of the PE file.\nThe keys that should be present in these objects are defined by sub-fields underneath `pe.sections.*`."}, + "threat.enrichments.indicator.file.pe.sections.entropy": {Name: "threat.enrichments.indicator.file.pe.sections.entropy", DataType: "long", Description: "Shannon entropy calculation from the section."}, + "threat.enrichments.indicator.file.pe.sections.name": {Name: "threat.enrichments.indicator.file.pe.sections.name", DataType: "keyword", Description: "PE Section List name."}, + "threat.enrichments.indicator.file.pe.sections.physical_size": {Name: "threat.enrichments.indicator.file.pe.sections.physical_size", DataType: "long", Description: "PE Section List physical size."}, + "threat.enrichments.indicator.file.pe.sections.var_entropy": {Name: "threat.enrichments.indicator.file.pe.sections.var_entropy", DataType: "long", Description: "Variance for Shannon entropy calculation from the section."}, + "threat.enrichments.indicator.file.pe.sections.virtual_size": {Name: "threat.enrichments.indicator.file.pe.sections.virtual_size", DataType: "long", Description: "PE Section List virtual size. This is always the same as `physical_size`."}, + "threat.enrichments.indicator.file.size": {Name: "threat.enrichments.indicator.file.size", DataType: "long", Description: "File size in bytes.\nOnly relevant when `file.type` is \"file\"."}, + "threat.enrichments.indicator.file.target_path": {Name: "threat.enrichments.indicator.file.target_path", DataType: "keyword", Description: "Target path for symlinks."}, + "threat.enrichments.indicator.file.type": {Name: "threat.enrichments.indicator.file.type", DataType: "keyword", Description: "File type (file, dir, or symlink)."}, + "threat.enrichments.indicator.file.uid": {Name: "threat.enrichments.indicator.file.uid", DataType: "keyword", Description: "The user ID (UID) or security identifier (SID) of the file owner."}, + "threat.enrichments.indicator.file.x509.alternative_names": {Name: "threat.enrichments.indicator.file.x509.alternative_names", DataType: "keyword", Array: true, Description: "List of subject alternative names (SAN). Name types vary by certificate authority and certificate type but commonly contain IP addresses, DNS names (and wildcards), and email addresses."}, + "threat.enrichments.indicator.file.x509.issuer.common_name": {Name: "threat.enrichments.indicator.file.x509.issuer.common_name", DataType: "keyword", Array: true, Description: "List of common name (CN) of issuing certificate authority."}, + "threat.enrichments.indicator.file.x509.issuer.country": {Name: "threat.enrichments.indicator.file.x509.issuer.country", DataType: "keyword", Array: true, Description: "List of country \\(C) codes"}, + "threat.enrichments.indicator.file.x509.issuer.distinguished_name": {Name: "threat.enrichments.indicator.file.x509.issuer.distinguished_name", DataType: "keyword", Description: "Distinguished name (DN) of issuing certificate authority."}, + "threat.enrichments.indicator.file.x509.issuer.locality": {Name: "threat.enrichments.indicator.file.x509.issuer.locality", DataType: "keyword", Array: true, Description: "List of locality names (L)"}, + "threat.enrichments.indicator.file.x509.issuer.organization": {Name: "threat.enrichments.indicator.file.x509.issuer.organization", DataType: "keyword", Array: true, Description: "List of organizations (O) of issuing certificate authority."}, + "threat.enrichments.indicator.file.x509.issuer.organizational_unit": {Name: "threat.enrichments.indicator.file.x509.issuer.organizational_unit", DataType: "keyword", Array: true, Description: "List of organizational units (OU) of issuing certificate authority."}, + "threat.enrichments.indicator.file.x509.issuer.state_or_province": {Name: "threat.enrichments.indicator.file.x509.issuer.state_or_province", DataType: "keyword", Array: true, Description: "List of state or province names (ST, S, or P)"}, + "threat.enrichments.indicator.file.x509.not_after": {Name: "threat.enrichments.indicator.file.x509.not_after", DataType: "date", Description: "Time at which the certificate is no longer considered valid."}, + "threat.enrichments.indicator.file.x509.not_before": {Name: "threat.enrichments.indicator.file.x509.not_before", DataType: "date", Description: "Time at which the certificate is first considered valid."}, + "threat.enrichments.indicator.file.x509.public_key_algorithm": {Name: "threat.enrichments.indicator.file.x509.public_key_algorithm", DataType: "keyword", Description: "Algorithm used to generate the public key."}, + "threat.enrichments.indicator.file.x509.public_key_curve": {Name: "threat.enrichments.indicator.file.x509.public_key_curve", DataType: "keyword", Description: "The curve used by the elliptic curve public key algorithm. This is algorithm specific."}, + "threat.enrichments.indicator.file.x509.public_key_exponent": {Name: "threat.enrichments.indicator.file.x509.public_key_exponent", DataType: "long", Description: "Exponent used to derive the public key. This is algorithm specific."}, + "threat.enrichments.indicator.file.x509.public_key_size": {Name: "threat.enrichments.indicator.file.x509.public_key_size", DataType: "long", Description: "The size of the public key space in bits."}, + "threat.enrichments.indicator.file.x509.serial_number": {Name: "threat.enrichments.indicator.file.x509.serial_number", DataType: "keyword", Description: "Unique serial number issued by the certificate authority. For consistency, if this value is alphanumeric, it should be formatted without colons and uppercase characters."}, + "threat.enrichments.indicator.file.x509.signature_algorithm": {Name: "threat.enrichments.indicator.file.x509.signature_algorithm", DataType: "keyword", Description: "Identifier for certificate signature algorithm. We recommend using names found in Go Lang Crypto library. See https://github.com/golang/go/blob/go1.14/src/crypto/x509/x509.go#L337-L353."}, + "threat.enrichments.indicator.file.x509.subject.common_name": {Name: "threat.enrichments.indicator.file.x509.subject.common_name", DataType: "keyword", Array: true, Description: "List of common names (CN) of subject."}, + "threat.enrichments.indicator.file.x509.subject.country": {Name: "threat.enrichments.indicator.file.x509.subject.country", DataType: "keyword", Array: true, Description: "List of country \\(C) code"}, + "threat.enrichments.indicator.file.x509.subject.distinguished_name": {Name: "threat.enrichments.indicator.file.x509.subject.distinguished_name", DataType: "keyword", Description: "Distinguished name (DN) of the certificate subject entity."}, + "threat.enrichments.indicator.file.x509.subject.locality": {Name: "threat.enrichments.indicator.file.x509.subject.locality", DataType: "keyword", Array: true, Description: "List of locality names (L)"}, + "threat.enrichments.indicator.file.x509.subject.organization": {Name: "threat.enrichments.indicator.file.x509.subject.organization", DataType: "keyword", Array: true, Description: "List of organizations (O) of subject."}, + "threat.enrichments.indicator.file.x509.subject.organizational_unit": {Name: "threat.enrichments.indicator.file.x509.subject.organizational_unit", DataType: "keyword", Array: true, Description: "List of organizational units (OU) of subject."}, + "threat.enrichments.indicator.file.x509.subject.state_or_province": {Name: "threat.enrichments.indicator.file.x509.subject.state_or_province", DataType: "keyword", Array: true, Description: "List of state or province names (ST, S, or P)"}, + "threat.enrichments.indicator.file.x509.version_number": {Name: "threat.enrichments.indicator.file.x509.version_number", DataType: "keyword", Description: "Version of x509 format."}, + "threat.enrichments.indicator.first_seen": {Name: "threat.enrichments.indicator.first_seen", DataType: "date", Description: "The date and time when intelligence source first reported sighting this indicator."}, + "threat.enrichments.indicator.geo.city_name": {Name: "threat.enrichments.indicator.geo.city_name", DataType: "keyword", Description: "City name."}, + "threat.enrichments.indicator.geo.continent_code": {Name: "threat.enrichments.indicator.geo.continent_code", DataType: "keyword", Description: "Two-letter code representing continent's name."}, + "threat.enrichments.indicator.geo.continent_name": {Name: "threat.enrichments.indicator.geo.continent_name", DataType: "keyword", Description: "Name of the continent."}, + "threat.enrichments.indicator.geo.country_iso_code": {Name: "threat.enrichments.indicator.geo.country_iso_code", DataType: "keyword", Description: "Country ISO code."}, + "threat.enrichments.indicator.geo.country_name": {Name: "threat.enrichments.indicator.geo.country_name", DataType: "keyword", Description: "Country name."}, + "threat.enrichments.indicator.geo.location": {Name: "threat.enrichments.indicator.geo.location", DataType: "geo_point", Description: "Longitude and latitude."}, + "threat.enrichments.indicator.geo.name": {Name: "threat.enrichments.indicator.geo.name", DataType: "keyword", Description: "User-defined description of a location, at the level of granularity they care about.\nCould be the name of their data centers, the floor number, if this describes a local physical entity, city names.\nNot typically used in automated geolocation."}, + "threat.enrichments.indicator.geo.postal_code": {Name: "threat.enrichments.indicator.geo.postal_code", DataType: "keyword", Description: "Postal code associated with the location.\nValues appropriate for this field may also be known as a postcode or ZIP code and will vary widely from country to country."}, + "threat.enrichments.indicator.geo.region_iso_code": {Name: "threat.enrichments.indicator.geo.region_iso_code", DataType: "keyword", Description: "Region ISO code."}, + "threat.enrichments.indicator.geo.region_name": {Name: "threat.enrichments.indicator.geo.region_name", DataType: "keyword", Description: "Region name."}, + "threat.enrichments.indicator.geo.timezone": {Name: "threat.enrichments.indicator.geo.timezone", DataType: "keyword", Description: "The time zone of the location, such as IANA time zone name."}, + "threat.enrichments.indicator.ip": {Name: "threat.enrichments.indicator.ip", DataType: "ip", Description: "Identifies a threat indicator as an IP address (irrespective of direction)."}, + "threat.enrichments.indicator.last_seen": {Name: "threat.enrichments.indicator.last_seen", DataType: "date", Description: "The date and time when intelligence source last reported sighting this indicator."}, + "threat.enrichments.indicator.marking.tlp": {Name: "threat.enrichments.indicator.marking.tlp", DataType: "keyword", Pattern: "(?:AMBER|AMBER+STRICT|CLEAR|GREEN|RED|WHITE)", Description: "Traffic Light Protocol sharing markings."}, + "threat.enrichments.indicator.marking.tlp_version": {Name: "threat.enrichments.indicator.marking.tlp_version", DataType: "keyword", Description: "Traffic Light Protocol version."}, + "threat.enrichments.indicator.modified_at": {Name: "threat.enrichments.indicator.modified_at", DataType: "date", Description: "The date and time when intelligence source last modified information for this indicator."}, + "threat.enrichments.indicator.name": {Name: "threat.enrichments.indicator.name", DataType: "keyword", Description: "The display name indicator in an UI friendly format\nURL, IP address, email address, registry key, port number, hash value, or other relevant name can serve as the display name."}, + "threat.enrichments.indicator.port": {Name: "threat.enrichments.indicator.port", DataType: "long", Description: "Identifies a threat indicator as a port number (irrespective of direction)."}, + "threat.enrichments.indicator.provider": {Name: "threat.enrichments.indicator.provider", DataType: "keyword", Description: "The name of the indicator's provider."}, + "threat.enrichments.indicator.reference": {Name: "threat.enrichments.indicator.reference", DataType: "keyword", Description: "Reference URL linking to additional information about this indicator."}, + "threat.enrichments.indicator.registry.data.bytes": {Name: "threat.enrichments.indicator.registry.data.bytes", DataType: "keyword", Description: "Original bytes written with base64 encoding.\nFor 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."}, + "threat.enrichments.indicator.registry.data.strings": {Name: "threat.enrichments.indicator.registry.data.strings", DataType: "wildcard", Array: true, Description: "Content when writing string types.\nPopulated 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\"`)."}, + "threat.enrichments.indicator.registry.data.type": {Name: "threat.enrichments.indicator.registry.data.type", DataType: "keyword", Description: "Standard registry type for encoding contents"}, + "threat.enrichments.indicator.registry.hive": {Name: "threat.enrichments.indicator.registry.hive", DataType: "keyword", Description: "Abbreviated name for the hive."}, + "threat.enrichments.indicator.registry.key": {Name: "threat.enrichments.indicator.registry.key", DataType: "keyword", Description: "Hive-relative path of keys."}, + "threat.enrichments.indicator.registry.path": {Name: "threat.enrichments.indicator.registry.path", DataType: "keyword", Description: "Full path, including hive, key and value"}, + "threat.enrichments.indicator.registry.value": {Name: "threat.enrichments.indicator.registry.value", DataType: "keyword", Description: "Name of the value written."}, + "threat.enrichments.indicator.scanner_stats": {Name: "threat.enrichments.indicator.scanner_stats", DataType: "long", Description: "Count of AV/EDR vendors that successfully detected malicious file or URL."}, + "threat.enrichments.indicator.sightings": {Name: "threat.enrichments.indicator.sightings", DataType: "long", Description: "Number of times this indicator was observed conducting threat activity."}, + "threat.enrichments.indicator.type": {Name: "threat.enrichments.indicator.type", DataType: "keyword", Pattern: "(?:artifact|autonomous-system|directory|domain-name|email-addr|file|ipv4-addr|ipv6-addr|mac-addr|mutex|port|process|software|url|user-account|windows-registry-key|x509-certificate)", Description: "Type of indicator as represented by Cyber Observable in STIX 2.0."}, + "threat.enrichments.indicator.url.domain": {Name: "threat.enrichments.indicator.url.domain", DataType: "keyword", Description: "Domain of the url, such as \"www.elastic.co\".\nIn 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.\nIf the URL contains a literal IPv6 address enclosed by `[` and `]` (IETF RFC 2732), the `[` and `]` characters should also be captured in the `domain` field."}, + "threat.enrichments.indicator.url.extension": {Name: "threat.enrichments.indicator.url.extension", DataType: "keyword", Description: "The field contains the file extension from the original request url, excluding the leading dot.\nThe file extension is only set if it exists, as not every url has a file extension.\nThe leading period must not be included. For example, the value must be \"png\", not \".png\".\nNote that when the file name has multiple extensions (example.tar.gz), only the last one should be captured (\"gz\", not \"tar.gz\")."}, + "threat.enrichments.indicator.url.fragment": {Name: "threat.enrichments.indicator.url.fragment", DataType: "keyword", Description: "Portion of the url after the `#`, such as \"top\".\nThe `#` is not part of the fragment."}, + "threat.enrichments.indicator.url.full": {Name: "threat.enrichments.indicator.url.full", DataType: "wildcard", Description: "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."}, + "threat.enrichments.indicator.url.original": {Name: "threat.enrichments.indicator.url.original", DataType: "wildcard", Description: "Unmodified original url as seen in the event source.\nNote 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.\nThis field is meant to represent the URL as it was observed, complete or not."}, + "threat.enrichments.indicator.url.password": {Name: "threat.enrichments.indicator.url.password", DataType: "keyword", Description: "Password of the request."}, + "threat.enrichments.indicator.url.path": {Name: "threat.enrichments.indicator.url.path", DataType: "wildcard", Description: "Path of the request, such as \"/search\"."}, + "threat.enrichments.indicator.url.port": {Name: "threat.enrichments.indicator.url.port", DataType: "long", Description: "Port of the request, such as 443."}, + "threat.enrichments.indicator.url.query": {Name: "threat.enrichments.indicator.url.query", DataType: "keyword", Description: "The query field describes the query string of the request, such as \"q=elasticsearch\".\nThe `?` 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."}, + "threat.enrichments.indicator.url.registered_domain": {Name: "threat.enrichments.indicator.url.registered_domain", DataType: "keyword", Description: "The highest registered url domain, stripped of the subdomain.\nFor example, the registered domain for \"foo.example.com\" is \"example.com\".\nThis 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\"."}, + "threat.enrichments.indicator.url.scheme": {Name: "threat.enrichments.indicator.url.scheme", DataType: "keyword", Description: "Scheme of the request, such as \"https\".\nNote: The `:` is not part of the scheme."}, + "threat.enrichments.indicator.url.subdomain": {Name: "threat.enrichments.indicator.url.subdomain", DataType: "keyword", Description: "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.\nFor 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."}, + "threat.enrichments.indicator.url.top_level_domain": {Name: "threat.enrichments.indicator.url.top_level_domain", DataType: "keyword", Description: "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\".\nThis 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\"."}, + "threat.enrichments.indicator.url.username": {Name: "threat.enrichments.indicator.url.username", DataType: "keyword", Description: "Username of the request."}, + "threat.enrichments.indicator.x509.alternative_names": {Name: "threat.enrichments.indicator.x509.alternative_names", DataType: "keyword", Array: true, Description: "List of subject alternative names (SAN). Name types vary by certificate authority and certificate type but commonly contain IP addresses, DNS names (and wildcards), and email addresses."}, + "threat.enrichments.indicator.x509.issuer.common_name": {Name: "threat.enrichments.indicator.x509.issuer.common_name", DataType: "keyword", Array: true, Description: "List of common name (CN) of issuing certificate authority."}, + "threat.enrichments.indicator.x509.issuer.country": {Name: "threat.enrichments.indicator.x509.issuer.country", DataType: "keyword", Array: true, Description: "List of country \\(C) codes"}, + "threat.enrichments.indicator.x509.issuer.distinguished_name": {Name: "threat.enrichments.indicator.x509.issuer.distinguished_name", DataType: "keyword", Description: "Distinguished name (DN) of issuing certificate authority."}, + "threat.enrichments.indicator.x509.issuer.locality": {Name: "threat.enrichments.indicator.x509.issuer.locality", DataType: "keyword", Array: true, Description: "List of locality names (L)"}, + "threat.enrichments.indicator.x509.issuer.organization": {Name: "threat.enrichments.indicator.x509.issuer.organization", DataType: "keyword", Array: true, Description: "List of organizations (O) of issuing certificate authority."}, + "threat.enrichments.indicator.x509.issuer.organizational_unit": {Name: "threat.enrichments.indicator.x509.issuer.organizational_unit", DataType: "keyword", Array: true, Description: "List of organizational units (OU) of issuing certificate authority."}, + "threat.enrichments.indicator.x509.issuer.state_or_province": {Name: "threat.enrichments.indicator.x509.issuer.state_or_province", DataType: "keyword", Array: true, Description: "List of state or province names (ST, S, or P)"}, + "threat.enrichments.indicator.x509.not_after": {Name: "threat.enrichments.indicator.x509.not_after", DataType: "date", Description: "Time at which the certificate is no longer considered valid."}, + "threat.enrichments.indicator.x509.not_before": {Name: "threat.enrichments.indicator.x509.not_before", DataType: "date", Description: "Time at which the certificate is first considered valid."}, + "threat.enrichments.indicator.x509.public_key_algorithm": {Name: "threat.enrichments.indicator.x509.public_key_algorithm", DataType: "keyword", Description: "Algorithm used to generate the public key."}, + "threat.enrichments.indicator.x509.public_key_curve": {Name: "threat.enrichments.indicator.x509.public_key_curve", DataType: "keyword", Description: "The curve used by the elliptic curve public key algorithm. This is algorithm specific."}, + "threat.enrichments.indicator.x509.public_key_exponent": {Name: "threat.enrichments.indicator.x509.public_key_exponent", DataType: "long", Description: "Exponent used to derive the public key. This is algorithm specific."}, + "threat.enrichments.indicator.x509.public_key_size": {Name: "threat.enrichments.indicator.x509.public_key_size", DataType: "long", Description: "The size of the public key space in bits."}, + "threat.enrichments.indicator.x509.serial_number": {Name: "threat.enrichments.indicator.x509.serial_number", DataType: "keyword", Description: "Unique serial number issued by the certificate authority. For consistency, if this value is alphanumeric, it should be formatted without colons and uppercase characters."}, + "threat.enrichments.indicator.x509.signature_algorithm": {Name: "threat.enrichments.indicator.x509.signature_algorithm", DataType: "keyword", Description: "Identifier for certificate signature algorithm. We recommend using names found in Go Lang Crypto library. See https://github.com/golang/go/blob/go1.14/src/crypto/x509/x509.go#L337-L353."}, + "threat.enrichments.indicator.x509.subject.common_name": {Name: "threat.enrichments.indicator.x509.subject.common_name", DataType: "keyword", Array: true, Description: "List of common names (CN) of subject."}, + "threat.enrichments.indicator.x509.subject.country": {Name: "threat.enrichments.indicator.x509.subject.country", DataType: "keyword", Array: true, Description: "List of country \\(C) code"}, + "threat.enrichments.indicator.x509.subject.distinguished_name": {Name: "threat.enrichments.indicator.x509.subject.distinguished_name", DataType: "keyword", Description: "Distinguished name (DN) of the certificate subject entity."}, + "threat.enrichments.indicator.x509.subject.locality": {Name: "threat.enrichments.indicator.x509.subject.locality", DataType: "keyword", Array: true, Description: "List of locality names (L)"}, + "threat.enrichments.indicator.x509.subject.organization": {Name: "threat.enrichments.indicator.x509.subject.organization", DataType: "keyword", Array: true, Description: "List of organizations (O) of subject."}, + "threat.enrichments.indicator.x509.subject.organizational_unit": {Name: "threat.enrichments.indicator.x509.subject.organizational_unit", DataType: "keyword", Array: true, Description: "List of organizational units (OU) of subject."}, + "threat.enrichments.indicator.x509.subject.state_or_province": {Name: "threat.enrichments.indicator.x509.subject.state_or_province", DataType: "keyword", Array: true, Description: "List of state or province names (ST, S, or P)"}, + "threat.enrichments.indicator.x509.version_number": {Name: "threat.enrichments.indicator.x509.version_number", DataType: "keyword", Description: "Version of x509 format."}, + "threat.enrichments.matched.atomic": {Name: "threat.enrichments.matched.atomic", DataType: "keyword", Description: "Identifies the atomic indicator value that matched a local environment endpoint or network event."}, + "threat.enrichments.matched.field": {Name: "threat.enrichments.matched.field", DataType: "keyword", Description: "Identifies the field of the atomic indicator that matched a local environment endpoint or network event."}, + "threat.enrichments.matched.id": {Name: "threat.enrichments.matched.id", DataType: "keyword", Description: "Identifies the _id of the indicator document enriching the event."}, + "threat.enrichments.matched.index": {Name: "threat.enrichments.matched.index", DataType: "keyword", Description: "Identifies the _index of the indicator document enriching the event."}, + "threat.enrichments.matched.occurred": {Name: "threat.enrichments.matched.occurred", DataType: "date", Description: "Indicates when the indicator match was generated"}, + "threat.enrichments.matched.type": {Name: "threat.enrichments.matched.type", DataType: "keyword", Description: "Identifies the type of match that caused the event to be enriched with the given indicator"}, + "threat.feed.dashboard_id": {Name: "threat.feed.dashboard_id", DataType: "keyword", Description: "The saved object ID of the dashboard belonging to the threat feed for displaying dashboard links to threat feeds in Kibana."}, + "threat.feed.description": {Name: "threat.feed.description", DataType: "keyword", Description: "Description of the threat feed in a UI friendly format."}, + "threat.feed.name": {Name: "threat.feed.name", DataType: "keyword", Description: "The name of the threat feed in UI friendly format."}, + "threat.feed.reference": {Name: "threat.feed.reference", DataType: "keyword", Description: "Reference information for the threat feed in a UI friendly format."}, + "threat.framework": {Name: "threat.framework", DataType: "keyword", Description: "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."}, + "threat.group.alias": {Name: "threat.group.alias", DataType: "keyword", Array: true, Description: "The alias(es) of the group for a set of related intrusion activity that are tracked by a common name in the security community.\nWhile not required, you can use a MITRE ATT&CK® group alias(es)."}, + "threat.group.id": {Name: "threat.group.id", DataType: "keyword", Description: "The id of the group for a set of related intrusion activity that are tracked by a common name in the security community.\nWhile not required, you can use a MITRE ATT&CK® group id."}, + "threat.group.name": {Name: "threat.group.name", DataType: "keyword", Description: "The name of the group for a set of related intrusion activity that are tracked by a common name in the security community.\nWhile not required, you can use a MITRE ATT&CK® group name."}, + "threat.group.reference": {Name: "threat.group.reference", DataType: "keyword", Description: "The reference URL of the group for a set of related intrusion activity that are tracked by a common name in the security community.\nWhile not required, you can use a MITRE ATT&CK® group reference URL."}, + "threat.indicator.as.number": {Name: "threat.indicator.as.number", DataType: "long", Description: "Unique number allocated to the autonomous system. The autonomous system number (ASN) uniquely identifies each network on the Internet."}, + "threat.indicator.as.organization.name": {Name: "threat.indicator.as.organization.name", DataType: "keyword", Description: "Organization name."}, + "threat.indicator.confidence": {Name: "threat.indicator.confidence", DataType: "keyword", Pattern: "(?:High|Low|Medium|None|Not Specified)", Description: "Identifies the vendor-neutral confidence rating using the None/Low/Medium/High scale defined in Appendix A of the STIX 2.1 framework. Vendor-specific confidence scales may be added as custom fields."}, + "threat.indicator.description": {Name: "threat.indicator.description", DataType: "keyword", Description: "Describes the type of action conducted by the threat."}, + "threat.indicator.email.address": {Name: "threat.indicator.email.address", DataType: "keyword", Description: "Identifies a threat indicator as an email address (irrespective of direction)."}, + "threat.indicator.file.accessed": {Name: "threat.indicator.file.accessed", DataType: "date", Description: "Last time the file was accessed.\nNote that not all filesystems keep track of access time."}, + "threat.indicator.file.attributes": {Name: "threat.indicator.file.attributes", DataType: "keyword", Array: true, Description: "Array of file attributes.\nAttributes 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."}, + "threat.indicator.file.code_signature.digest_algorithm": {Name: "threat.indicator.file.code_signature.digest_algorithm", DataType: "keyword", Description: "The hashing algorithm used to sign the process.\nThis value can distinguish signatures when a file is signed multiple times by the same signer but with a different digest algorithm."}, + "threat.indicator.file.code_signature.exists": {Name: "threat.indicator.file.code_signature.exists", DataType: "boolean", Description: "Boolean to capture if a signature is present."}, + "threat.indicator.file.code_signature.signing_id": {Name: "threat.indicator.file.code_signature.signing_id", DataType: "keyword", Description: "The identifier used to sign the process.\nThis is used to identify the application manufactured by a software vendor. The field is relevant to Apple *OS only."}, + "threat.indicator.file.code_signature.status": {Name: "threat.indicator.file.code_signature.status", DataType: "keyword", Description: "Additional information about the certificate status.\nThis is useful for logging cryptographic errors with the certificate validity or trust status. Leave unpopulated if the validity or trust of the certificate was unchecked."}, + "threat.indicator.file.code_signature.subject_name": {Name: "threat.indicator.file.code_signature.subject_name", DataType: "keyword", Description: "Subject name of the code signer"}, + "threat.indicator.file.code_signature.team_id": {Name: "threat.indicator.file.code_signature.team_id", DataType: "keyword", Description: "The team identifier used to sign the process.\nThis is used to identify the team or vendor of a software product. The field is relevant to Apple *OS only."}, + "threat.indicator.file.code_signature.timestamp": {Name: "threat.indicator.file.code_signature.timestamp", DataType: "date", Description: "Date and time when the code signature was generated and signed."}, + "threat.indicator.file.code_signature.trusted": {Name: "threat.indicator.file.code_signature.trusted", DataType: "boolean", Description: "Stores the trust status of the certificate chain.\nValidating the trust of the certificate chain may be complicated, and this field should only be populated by tools that actively check the status."}, + "threat.indicator.file.code_signature.valid": {Name: "threat.indicator.file.code_signature.valid", DataType: "boolean", Description: "Boolean to capture if the digital signature is verified against the binary content.\nLeave unpopulated if a certificate was unchecked."}, + "threat.indicator.file.created": {Name: "threat.indicator.file.created", DataType: "date", Description: "File creation time.\nNote that not all filesystems store the creation time."}, + "threat.indicator.file.ctime": {Name: "threat.indicator.file.ctime", DataType: "date", Description: "Last time the file attributes or metadata changed.\nNote 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."}, + "threat.indicator.file.device": {Name: "threat.indicator.file.device", DataType: "keyword", Description: "Device that is the source of the file."}, + "threat.indicator.file.directory": {Name: "threat.indicator.file.directory", DataType: "keyword", Description: "Directory where the file is located. It should include the drive letter, when appropriate."}, + "threat.indicator.file.drive_letter": {Name: "threat.indicator.file.drive_letter", DataType: "keyword", Description: "Drive letter where the file is located. This field is only relevant on Windows.\nThe value should be uppercase, and not include the colon."}, + "threat.indicator.file.elf.architecture": {Name: "threat.indicator.file.elf.architecture", DataType: "keyword", Description: "Machine architecture of the ELF file."}, + "threat.indicator.file.elf.byte_order": {Name: "threat.indicator.file.elf.byte_order", DataType: "keyword", Description: "Byte sequence of ELF file."}, + "threat.indicator.file.elf.cpu_type": {Name: "threat.indicator.file.elf.cpu_type", DataType: "keyword", Description: "CPU type of the ELF file."}, + "threat.indicator.file.elf.creation_date": {Name: "threat.indicator.file.elf.creation_date", DataType: "date", Description: "Extracted when possible from the file's metadata. Indicates when it was built or compiled. It can also be faked by malware creators."}, + "threat.indicator.file.elf.exports": {Name: "threat.indicator.file.elf.exports", DataType: "flattened", Array: true, Description: "List of exported element names and types."}, + "threat.indicator.file.elf.go_import_hash": {Name: "threat.indicator.file.elf.go_import_hash", DataType: "keyword", Description: "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.\nThe algorithm used to calculate the Go symbol hash and a reference implementation are available [here](https://github.com/elastic/toutoumomoma)."}, + "threat.indicator.file.elf.go_imports": {Name: "threat.indicator.file.elf.go_imports", DataType: "flattened", Description: "List of imported Go language element names and types."}, + "threat.indicator.file.elf.go_imports_names_entropy": {Name: "threat.indicator.file.elf.go_imports_names_entropy", DataType: "long", Description: "Shannon entropy calculation from the list of Go imports."}, + "threat.indicator.file.elf.go_imports_names_var_entropy": {Name: "threat.indicator.file.elf.go_imports_names_var_entropy", DataType: "long", Description: "Variance for Shannon entropy calculation from the list of Go imports."}, + "threat.indicator.file.elf.go_stripped": {Name: "threat.indicator.file.elf.go_stripped", DataType: "boolean", Description: "Set to true if the file is a Go executable that has had its symbols stripped or obfuscated and false if an unobfuscated Go executable."}, + "threat.indicator.file.elf.header.abi_version": {Name: "threat.indicator.file.elf.header.abi_version", DataType: "keyword", Description: "Version of the ELF Application Binary Interface (ABI)."}, + "threat.indicator.file.elf.header.class": {Name: "threat.indicator.file.elf.header.class", DataType: "keyword", Description: "Header class of the ELF file."}, + "threat.indicator.file.elf.header.data": {Name: "threat.indicator.file.elf.header.data", DataType: "keyword", Description: "Data table of the ELF header."}, + "threat.indicator.file.elf.header.entrypoint": {Name: "threat.indicator.file.elf.header.entrypoint", DataType: "long", Description: "Header entrypoint of the ELF file."}, + "threat.indicator.file.elf.header.object_version": {Name: "threat.indicator.file.elf.header.object_version", DataType: "keyword", Description: "\"0x1\" for original ELF files."}, + "threat.indicator.file.elf.header.os_abi": {Name: "threat.indicator.file.elf.header.os_abi", DataType: "keyword", Description: "Application Binary Interface (ABI) of the Linux OS."}, + "threat.indicator.file.elf.header.type": {Name: "threat.indicator.file.elf.header.type", DataType: "keyword", Description: "Header type of the ELF file."}, + "threat.indicator.file.elf.header.version": {Name: "threat.indicator.file.elf.header.version", DataType: "keyword", Description: "Version of the ELF header."}, + "threat.indicator.file.elf.import_hash": {Name: "threat.indicator.file.elf.import_hash", DataType: "keyword", Description: "A hash of the imports in an ELF file. 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.\nThis is an ELF implementation of the Windows PE imphash."}, + "threat.indicator.file.elf.imports": {Name: "threat.indicator.file.elf.imports", DataType: "flattened", Array: true, Description: "List of imported element names and types."}, + "threat.indicator.file.elf.imports_names_entropy": {Name: "threat.indicator.file.elf.imports_names_entropy", DataType: "long", Description: "Shannon entropy calculation from the list of imported element names and types."}, + "threat.indicator.file.elf.imports_names_var_entropy": {Name: "threat.indicator.file.elf.imports_names_var_entropy", DataType: "long", Description: "Variance for Shannon entropy calculation from the list of imported element names and types."}, + "threat.indicator.file.elf.sections": {Name: "threat.indicator.file.elf.sections", DataType: "nested", Array: true, Description: "An array containing an object for each section of the ELF file.\nThe keys that should be present in these objects are defined by sub-fields underneath `elf.sections.*`."}, + "threat.indicator.file.elf.sections.chi2": {Name: "threat.indicator.file.elf.sections.chi2", DataType: "long", Description: "Chi-square probability distribution of the section."}, + "threat.indicator.file.elf.sections.entropy": {Name: "threat.indicator.file.elf.sections.entropy", DataType: "long", Description: "Shannon entropy calculation from the section."}, + "threat.indicator.file.elf.sections.flags": {Name: "threat.indicator.file.elf.sections.flags", DataType: "keyword", Description: "ELF Section List flags."}, + "threat.indicator.file.elf.sections.name": {Name: "threat.indicator.file.elf.sections.name", DataType: "keyword", Description: "ELF Section List name."}, + "threat.indicator.file.elf.sections.physical_offset": {Name: "threat.indicator.file.elf.sections.physical_offset", DataType: "keyword", Description: "ELF Section List offset."}, + "threat.indicator.file.elf.sections.physical_size": {Name: "threat.indicator.file.elf.sections.physical_size", DataType: "long", Description: "ELF Section List physical size."}, + "threat.indicator.file.elf.sections.type": {Name: "threat.indicator.file.elf.sections.type", DataType: "keyword", Description: "ELF Section List type."}, + "threat.indicator.file.elf.sections.var_entropy": {Name: "threat.indicator.file.elf.sections.var_entropy", DataType: "long", Description: "Variance for Shannon entropy calculation from the section."}, + "threat.indicator.file.elf.sections.virtual_address": {Name: "threat.indicator.file.elf.sections.virtual_address", DataType: "long", Description: "ELF Section List virtual address."}, + "threat.indicator.file.elf.sections.virtual_size": {Name: "threat.indicator.file.elf.sections.virtual_size", DataType: "long", Description: "ELF Section List virtual size."}, + "threat.indicator.file.elf.segments": {Name: "threat.indicator.file.elf.segments", DataType: "nested", Array: true, Description: "An array containing an object for each segment of the ELF file.\nThe keys that should be present in these objects are defined by sub-fields underneath `elf.segments.*`."}, + "threat.indicator.file.elf.segments.sections": {Name: "threat.indicator.file.elf.segments.sections", DataType: "keyword", Description: "ELF object segment sections."}, + "threat.indicator.file.elf.segments.type": {Name: "threat.indicator.file.elf.segments.type", DataType: "keyword", Description: "ELF object segment type."}, + "threat.indicator.file.elf.shared_libraries": {Name: "threat.indicator.file.elf.shared_libraries", DataType: "keyword", Array: true, Description: "List of shared libraries used by this ELF object."}, + "threat.indicator.file.elf.telfhash": {Name: "threat.indicator.file.elf.telfhash", DataType: "keyword", Description: "telfhash symbol hash for ELF file."}, + "threat.indicator.file.extension": {Name: "threat.indicator.file.extension", DataType: "keyword", Description: "File extension, excluding the leading dot.\nNote that when the file name has multiple extensions (example.tar.gz), only the last one should be captured (\"gz\", not \"tar.gz\")."}, + "threat.indicator.file.fork_name": {Name: "threat.indicator.file.fork_name", DataType: "keyword", Description: "A fork is additional data associated with a filesystem object.\nOn Linux, a resource fork is used to store additional data with a filesystem object. A file always has at least one fork for the data portion, and additional forks may exist.\nOn NTFS, this is analogous to an Alternate Data Stream (ADS), and the default data stream for a file is just called $DATA. Zone.Identifier is commonly used by Windows to track contents downloaded from the Internet. An ADS is typically of the form: `C:\\path\\to\\filename.extension:some_fork_name`, and `some_fork_name` is the value that should populate `fork_name`. `filename.extension` should populate `file.name`, and `extension` should populate `file.extension`. The full path, `file.path`, will include the fork name."}, + "threat.indicator.file.gid": {Name: "threat.indicator.file.gid", DataType: "keyword", Description: "Primary group ID (GID) of the file."}, + "threat.indicator.file.group": {Name: "threat.indicator.file.group", DataType: "keyword", Description: "Primary group name of the file."}, + "threat.indicator.file.hash.md5": {Name: "threat.indicator.file.hash.md5", DataType: "keyword", Description: "MD5 hash."}, + "threat.indicator.file.hash.sha1": {Name: "threat.indicator.file.hash.sha1", DataType: "keyword", Description: "SHA1 hash."}, + "threat.indicator.file.hash.sha256": {Name: "threat.indicator.file.hash.sha256", DataType: "keyword", Description: "SHA256 hash."}, + "threat.indicator.file.hash.sha384": {Name: "threat.indicator.file.hash.sha384", DataType: "keyword", Description: "SHA384 hash."}, + "threat.indicator.file.hash.sha512": {Name: "threat.indicator.file.hash.sha512", DataType: "keyword", Description: "SHA512 hash."}, + "threat.indicator.file.hash.ssdeep": {Name: "threat.indicator.file.hash.ssdeep", DataType: "keyword", Description: "SSDEEP hash."}, + "threat.indicator.file.hash.tlsh": {Name: "threat.indicator.file.hash.tlsh", DataType: "keyword", Description: "TLSH hash."}, + "threat.indicator.file.inode": {Name: "threat.indicator.file.inode", DataType: "keyword", Description: "Inode representing the file in the filesystem."}, + "threat.indicator.file.mime_type": {Name: "threat.indicator.file.mime_type", DataType: "keyword", Description: "MIME type should identify the format of the file or stream of bytes using https://www.iana.org/assignments/media-types/media-types.xhtml[IANA official types], where possible. When more than one type is applicable, the most specific type should be used."}, + "threat.indicator.file.mode": {Name: "threat.indicator.file.mode", DataType: "keyword", Description: "Mode of the file in octal representation."}, + "threat.indicator.file.mtime": {Name: "threat.indicator.file.mtime", DataType: "date", Description: "Last time the file content was modified."}, + "threat.indicator.file.name": {Name: "threat.indicator.file.name", DataType: "keyword", Description: "Name of the file including the extension, without the directory."}, + "threat.indicator.file.owner": {Name: "threat.indicator.file.owner", DataType: "keyword", Description: "File owner's username."}, + "threat.indicator.file.path": {Name: "threat.indicator.file.path", DataType: "keyword", Description: "Full path to the file, including the file name. It should include the drive letter, when appropriate."}, + "threat.indicator.file.pe.architecture": {Name: "threat.indicator.file.pe.architecture", DataType: "keyword", Description: "CPU architecture target for the file."}, + "threat.indicator.file.pe.company": {Name: "threat.indicator.file.pe.company", DataType: "keyword", Description: "Internal company name of the file, provided at compile-time."}, + "threat.indicator.file.pe.description": {Name: "threat.indicator.file.pe.description", DataType: "keyword", Description: "Internal description of the file, provided at compile-time."}, + "threat.indicator.file.pe.file_version": {Name: "threat.indicator.file.pe.file_version", DataType: "keyword", Description: "Internal version of the file, provided at compile-time."}, + "threat.indicator.file.pe.go_import_hash": {Name: "threat.indicator.file.pe.go_import_hash", DataType: "keyword", Description: "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.\nThe algorithm used to calculate the Go symbol hash and a reference implementation are available [here](https://github.com/elastic/toutoumomoma)."}, + "threat.indicator.file.pe.go_imports": {Name: "threat.indicator.file.pe.go_imports", DataType: "flattened", Description: "List of imported Go language element names and types."}, + "threat.indicator.file.pe.go_imports_names_entropy": {Name: "threat.indicator.file.pe.go_imports_names_entropy", DataType: "long", Description: "Shannon entropy calculation from the list of Go imports."}, + "threat.indicator.file.pe.go_imports_names_var_entropy": {Name: "threat.indicator.file.pe.go_imports_names_var_entropy", DataType: "long", Description: "Variance for Shannon entropy calculation from the list of Go imports."}, + "threat.indicator.file.pe.go_stripped": {Name: "threat.indicator.file.pe.go_stripped", DataType: "boolean", Description: "Set to true if the file is a Go executable that has had its symbols stripped or obfuscated and false if an unobfuscated Go executable."}, + "threat.indicator.file.pe.imphash": {Name: "threat.indicator.file.pe.imphash", DataType: "keyword", Description: "A hash of the imports in a PE file. An imphash -- or 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.\nLearn more at https://www.fireeye.com/blog/threat-research/2014/01/tracking-malware-import-hashing.html."}, + "threat.indicator.file.pe.import_hash": {Name: "threat.indicator.file.pe.import_hash", DataType: "keyword", Description: "A hash of the imports in a PE file. 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.\nThis is a synonym for imphash."}, + "threat.indicator.file.pe.imports": {Name: "threat.indicator.file.pe.imports", DataType: "flattened", Array: true, Description: "List of imported element names and types."}, + "threat.indicator.file.pe.imports_names_entropy": {Name: "threat.indicator.file.pe.imports_names_entropy", DataType: "long", Description: "Shannon entropy calculation from the list of imported element names and types."}, + "threat.indicator.file.pe.imports_names_var_entropy": {Name: "threat.indicator.file.pe.imports_names_var_entropy", DataType: "long", Description: "Variance for Shannon entropy calculation from the list of imported element names and types."}, + "threat.indicator.file.pe.original_file_name": {Name: "threat.indicator.file.pe.original_file_name", DataType: "keyword", Description: "Internal name of the file, provided at compile-time."}, + "threat.indicator.file.pe.pehash": {Name: "threat.indicator.file.pe.pehash", DataType: "keyword", Description: "A hash of the PE header and data from one or more PE sections. An pehash can be used to cluster files by transforming structural information about a file into a hash value.\nLearn more at https://www.usenix.org/legacy/events/leet09/tech/full_papers/wicherski/wicherski_html/index.html."}, + "threat.indicator.file.pe.product": {Name: "threat.indicator.file.pe.product", DataType: "keyword", Description: "Internal product name of the file, provided at compile-time."}, + "threat.indicator.file.pe.sections": {Name: "threat.indicator.file.pe.sections", DataType: "nested", Array: true, Description: "An array containing an object for each section of the PE file.\nThe keys that should be present in these objects are defined by sub-fields underneath `pe.sections.*`."}, + "threat.indicator.file.pe.sections.entropy": {Name: "threat.indicator.file.pe.sections.entropy", DataType: "long", Description: "Shannon entropy calculation from the section."}, + "threat.indicator.file.pe.sections.name": {Name: "threat.indicator.file.pe.sections.name", DataType: "keyword", Description: "PE Section List name."}, + "threat.indicator.file.pe.sections.physical_size": {Name: "threat.indicator.file.pe.sections.physical_size", DataType: "long", Description: "PE Section List physical size."}, + "threat.indicator.file.pe.sections.var_entropy": {Name: "threat.indicator.file.pe.sections.var_entropy", DataType: "long", Description: "Variance for Shannon entropy calculation from the section."}, + "threat.indicator.file.pe.sections.virtual_size": {Name: "threat.indicator.file.pe.sections.virtual_size", DataType: "long", Description: "PE Section List virtual size. This is always the same as `physical_size`."}, + "threat.indicator.file.size": {Name: "threat.indicator.file.size", DataType: "long", Description: "File size in bytes.\nOnly relevant when `file.type` is \"file\"."}, + "threat.indicator.file.target_path": {Name: "threat.indicator.file.target_path", DataType: "keyword", Description: "Target path for symlinks."}, + "threat.indicator.file.type": {Name: "threat.indicator.file.type", DataType: "keyword", Description: "File type (file, dir, or symlink)."}, + "threat.indicator.file.uid": {Name: "threat.indicator.file.uid", DataType: "keyword", Description: "The user ID (UID) or security identifier (SID) of the file owner."}, + "threat.indicator.file.x509.alternative_names": {Name: "threat.indicator.file.x509.alternative_names", DataType: "keyword", Array: true, Description: "List of subject alternative names (SAN). Name types vary by certificate authority and certificate type but commonly contain IP addresses, DNS names (and wildcards), and email addresses."}, + "threat.indicator.file.x509.issuer.common_name": {Name: "threat.indicator.file.x509.issuer.common_name", DataType: "keyword", Array: true, Description: "List of common name (CN) of issuing certificate authority."}, + "threat.indicator.file.x509.issuer.country": {Name: "threat.indicator.file.x509.issuer.country", DataType: "keyword", Array: true, Description: "List of country \\(C) codes"}, + "threat.indicator.file.x509.issuer.distinguished_name": {Name: "threat.indicator.file.x509.issuer.distinguished_name", DataType: "keyword", Description: "Distinguished name (DN) of issuing certificate authority."}, + "threat.indicator.file.x509.issuer.locality": {Name: "threat.indicator.file.x509.issuer.locality", DataType: "keyword", Array: true, Description: "List of locality names (L)"}, + "threat.indicator.file.x509.issuer.organization": {Name: "threat.indicator.file.x509.issuer.organization", DataType: "keyword", Array: true, Description: "List of organizations (O) of issuing certificate authority."}, + "threat.indicator.file.x509.issuer.organizational_unit": {Name: "threat.indicator.file.x509.issuer.organizational_unit", DataType: "keyword", Array: true, Description: "List of organizational units (OU) of issuing certificate authority."}, + "threat.indicator.file.x509.issuer.state_or_province": {Name: "threat.indicator.file.x509.issuer.state_or_province", DataType: "keyword", Array: true, Description: "List of state or province names (ST, S, or P)"}, + "threat.indicator.file.x509.not_after": {Name: "threat.indicator.file.x509.not_after", DataType: "date", Description: "Time at which the certificate is no longer considered valid."}, + "threat.indicator.file.x509.not_before": {Name: "threat.indicator.file.x509.not_before", DataType: "date", Description: "Time at which the certificate is first considered valid."}, + "threat.indicator.file.x509.public_key_algorithm": {Name: "threat.indicator.file.x509.public_key_algorithm", DataType: "keyword", Description: "Algorithm used to generate the public key."}, + "threat.indicator.file.x509.public_key_curve": {Name: "threat.indicator.file.x509.public_key_curve", DataType: "keyword", Description: "The curve used by the elliptic curve public key algorithm. This is algorithm specific."}, + "threat.indicator.file.x509.public_key_exponent": {Name: "threat.indicator.file.x509.public_key_exponent", DataType: "long", Description: "Exponent used to derive the public key. This is algorithm specific."}, + "threat.indicator.file.x509.public_key_size": {Name: "threat.indicator.file.x509.public_key_size", DataType: "long", Description: "The size of the public key space in bits."}, + "threat.indicator.file.x509.serial_number": {Name: "threat.indicator.file.x509.serial_number", DataType: "keyword", Description: "Unique serial number issued by the certificate authority. For consistency, if this value is alphanumeric, it should be formatted without colons and uppercase characters."}, + "threat.indicator.file.x509.signature_algorithm": {Name: "threat.indicator.file.x509.signature_algorithm", DataType: "keyword", Description: "Identifier for certificate signature algorithm. We recommend using names found in Go Lang Crypto library. See https://github.com/golang/go/blob/go1.14/src/crypto/x509/x509.go#L337-L353."}, + "threat.indicator.file.x509.subject.common_name": {Name: "threat.indicator.file.x509.subject.common_name", DataType: "keyword", Array: true, Description: "List of common names (CN) of subject."}, + "threat.indicator.file.x509.subject.country": {Name: "threat.indicator.file.x509.subject.country", DataType: "keyword", Array: true, Description: "List of country \\(C) code"}, + "threat.indicator.file.x509.subject.distinguished_name": {Name: "threat.indicator.file.x509.subject.distinguished_name", DataType: "keyword", Description: "Distinguished name (DN) of the certificate subject entity."}, + "threat.indicator.file.x509.subject.locality": {Name: "threat.indicator.file.x509.subject.locality", DataType: "keyword", Array: true, Description: "List of locality names (L)"}, + "threat.indicator.file.x509.subject.organization": {Name: "threat.indicator.file.x509.subject.organization", DataType: "keyword", Array: true, Description: "List of organizations (O) of subject."}, + "threat.indicator.file.x509.subject.organizational_unit": {Name: "threat.indicator.file.x509.subject.organizational_unit", DataType: "keyword", Array: true, Description: "List of organizational units (OU) of subject."}, + "threat.indicator.file.x509.subject.state_or_province": {Name: "threat.indicator.file.x509.subject.state_or_province", DataType: "keyword", Array: true, Description: "List of state or province names (ST, S, or P)"}, + "threat.indicator.file.x509.version_number": {Name: "threat.indicator.file.x509.version_number", DataType: "keyword", Description: "Version of x509 format."}, + "threat.indicator.first_seen": {Name: "threat.indicator.first_seen", DataType: "date", Description: "The date and time when intelligence source first reported sighting this indicator."}, + "threat.indicator.geo.city_name": {Name: "threat.indicator.geo.city_name", DataType: "keyword", Description: "City name."}, + "threat.indicator.geo.continent_code": {Name: "threat.indicator.geo.continent_code", DataType: "keyword", Description: "Two-letter code representing continent's name."}, + "threat.indicator.geo.continent_name": {Name: "threat.indicator.geo.continent_name", DataType: "keyword", Description: "Name of the continent."}, + "threat.indicator.geo.country_iso_code": {Name: "threat.indicator.geo.country_iso_code", DataType: "keyword", Description: "Country ISO code."}, + "threat.indicator.geo.country_name": {Name: "threat.indicator.geo.country_name", DataType: "keyword", Description: "Country name."}, + "threat.indicator.geo.location": {Name: "threat.indicator.geo.location", DataType: "geo_point", Description: "Longitude and latitude."}, + "threat.indicator.geo.name": {Name: "threat.indicator.geo.name", DataType: "keyword", Description: "User-defined description of a location, at the level of granularity they care about.\nCould be the name of their data centers, the floor number, if this describes a local physical entity, city names.\nNot typically used in automated geolocation."}, + "threat.indicator.geo.postal_code": {Name: "threat.indicator.geo.postal_code", DataType: "keyword", Description: "Postal code associated with the location.\nValues appropriate for this field may also be known as a postcode or ZIP code and will vary widely from country to country."}, + "threat.indicator.geo.region_iso_code": {Name: "threat.indicator.geo.region_iso_code", DataType: "keyword", Description: "Region ISO code."}, + "threat.indicator.geo.region_name": {Name: "threat.indicator.geo.region_name", DataType: "keyword", Description: "Region name."}, + "threat.indicator.geo.timezone": {Name: "threat.indicator.geo.timezone", DataType: "keyword", Description: "The time zone of the location, such as IANA time zone name."}, + "threat.indicator.ip": {Name: "threat.indicator.ip", DataType: "ip", Description: "Identifies a threat indicator as an IP address (irrespective of direction)."}, + "threat.indicator.last_seen": {Name: "threat.indicator.last_seen", DataType: "date", Description: "The date and time when intelligence source last reported sighting this indicator."}, + "threat.indicator.marking.tlp": {Name: "threat.indicator.marking.tlp", DataType: "keyword", Pattern: "(?:AMBER|AMBER+STRICT|CLEAR|GREEN|RED|WHITE)", Description: "Traffic Light Protocol sharing markings."}, + "threat.indicator.marking.tlp_version": {Name: "threat.indicator.marking.tlp_version", DataType: "keyword", Description: "Traffic Light Protocol version."}, + "threat.indicator.modified_at": {Name: "threat.indicator.modified_at", DataType: "date", Description: "The date and time when intelligence source last modified information for this indicator."}, + "threat.indicator.name": {Name: "threat.indicator.name", DataType: "keyword", Description: "The display name indicator in an UI friendly format\nURL, IP address, email address, registry key, port number, hash value, or other relevant name can serve as the display name."}, + "threat.indicator.port": {Name: "threat.indicator.port", DataType: "long", Description: "Identifies a threat indicator as a port number (irrespective of direction)."}, + "threat.indicator.provider": {Name: "threat.indicator.provider", DataType: "keyword", Description: "The name of the indicator's provider."}, + "threat.indicator.reference": {Name: "threat.indicator.reference", DataType: "keyword", Description: "Reference URL linking to additional information about this indicator."}, + "threat.indicator.registry.data.bytes": {Name: "threat.indicator.registry.data.bytes", DataType: "keyword", Description: "Original bytes written with base64 encoding.\nFor 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."}, + "threat.indicator.registry.data.strings": {Name: "threat.indicator.registry.data.strings", DataType: "wildcard", Array: true, Description: "Content when writing string types.\nPopulated 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\"`)."}, + "threat.indicator.registry.data.type": {Name: "threat.indicator.registry.data.type", DataType: "keyword", Description: "Standard registry type for encoding contents"}, + "threat.indicator.registry.hive": {Name: "threat.indicator.registry.hive", DataType: "keyword", Description: "Abbreviated name for the hive."}, + "threat.indicator.registry.key": {Name: "threat.indicator.registry.key", DataType: "keyword", Description: "Hive-relative path of keys."}, + "threat.indicator.registry.path": {Name: "threat.indicator.registry.path", DataType: "keyword", Description: "Full path, including hive, key and value"}, + "threat.indicator.registry.value": {Name: "threat.indicator.registry.value", DataType: "keyword", Description: "Name of the value written."}, + "threat.indicator.scanner_stats": {Name: "threat.indicator.scanner_stats", DataType: "long", Description: "Count of AV/EDR vendors that successfully detected malicious file or URL."}, + "threat.indicator.sightings": {Name: "threat.indicator.sightings", DataType: "long", Description: "Number of times this indicator was observed conducting threat activity."}, + "threat.indicator.type": {Name: "threat.indicator.type", DataType: "keyword", Pattern: "(?:artifact|autonomous-system|directory|domain-name|email-addr|file|ipv4-addr|ipv6-addr|mac-addr|mutex|port|process|software|url|user-account|windows-registry-key|x509-certificate)", Description: "Type of indicator as represented by Cyber Observable in STIX 2.0."}, + "threat.indicator.url.domain": {Name: "threat.indicator.url.domain", DataType: "keyword", Description: "Domain of the url, such as \"www.elastic.co\".\nIn 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.\nIf the URL contains a literal IPv6 address enclosed by `[` and `]` (IETF RFC 2732), the `[` and `]` characters should also be captured in the `domain` field."}, + "threat.indicator.url.extension": {Name: "threat.indicator.url.extension", DataType: "keyword", Description: "The field contains the file extension from the original request url, excluding the leading dot.\nThe file extension is only set if it exists, as not every url has a file extension.\nThe leading period must not be included. For example, the value must be \"png\", not \".png\".\nNote that when the file name has multiple extensions (example.tar.gz), only the last one should be captured (\"gz\", not \"tar.gz\")."}, + "threat.indicator.url.fragment": {Name: "threat.indicator.url.fragment", DataType: "keyword", Description: "Portion of the url after the `#`, such as \"top\".\nThe `#` is not part of the fragment."}, + "threat.indicator.url.full": {Name: "threat.indicator.url.full", DataType: "wildcard", Description: "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."}, + "threat.indicator.url.original": {Name: "threat.indicator.url.original", DataType: "wildcard", Description: "Unmodified original url as seen in the event source.\nNote 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.\nThis field is meant to represent the URL as it was observed, complete or not."}, + "threat.indicator.url.password": {Name: "threat.indicator.url.password", DataType: "keyword", Description: "Password of the request."}, + "threat.indicator.url.path": {Name: "threat.indicator.url.path", DataType: "wildcard", Description: "Path of the request, such as \"/search\"."}, + "threat.indicator.url.port": {Name: "threat.indicator.url.port", DataType: "long", Description: "Port of the request, such as 443."}, + "threat.indicator.url.query": {Name: "threat.indicator.url.query", DataType: "keyword", Description: "The query field describes the query string of the request, such as \"q=elasticsearch\".\nThe `?` 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."}, + "threat.indicator.url.registered_domain": {Name: "threat.indicator.url.registered_domain", DataType: "keyword", Description: "The highest registered url domain, stripped of the subdomain.\nFor example, the registered domain for \"foo.example.com\" is \"example.com\".\nThis 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\"."}, + "threat.indicator.url.scheme": {Name: "threat.indicator.url.scheme", DataType: "keyword", Description: "Scheme of the request, such as \"https\".\nNote: The `:` is not part of the scheme."}, + "threat.indicator.url.subdomain": {Name: "threat.indicator.url.subdomain", DataType: "keyword", Description: "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.\nFor 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."}, + "threat.indicator.url.top_level_domain": {Name: "threat.indicator.url.top_level_domain", DataType: "keyword", Description: "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\".\nThis 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\"."}, + "threat.indicator.url.username": {Name: "threat.indicator.url.username", DataType: "keyword", Description: "Username of the request."}, + "threat.indicator.x509.alternative_names": {Name: "threat.indicator.x509.alternative_names", DataType: "keyword", Array: true, Description: "List of subject alternative names (SAN). Name types vary by certificate authority and certificate type but commonly contain IP addresses, DNS names (and wildcards), and email addresses."}, + "threat.indicator.x509.issuer.common_name": {Name: "threat.indicator.x509.issuer.common_name", DataType: "keyword", Array: true, Description: "List of common name (CN) of issuing certificate authority."}, + "threat.indicator.x509.issuer.country": {Name: "threat.indicator.x509.issuer.country", DataType: "keyword", Array: true, Description: "List of country \\(C) codes"}, + "threat.indicator.x509.issuer.distinguished_name": {Name: "threat.indicator.x509.issuer.distinguished_name", DataType: "keyword", Description: "Distinguished name (DN) of issuing certificate authority."}, + "threat.indicator.x509.issuer.locality": {Name: "threat.indicator.x509.issuer.locality", DataType: "keyword", Array: true, Description: "List of locality names (L)"}, + "threat.indicator.x509.issuer.organization": {Name: "threat.indicator.x509.issuer.organization", DataType: "keyword", Array: true, Description: "List of organizations (O) of issuing certificate authority."}, + "threat.indicator.x509.issuer.organizational_unit": {Name: "threat.indicator.x509.issuer.organizational_unit", DataType: "keyword", Array: true, Description: "List of organizational units (OU) of issuing certificate authority."}, + "threat.indicator.x509.issuer.state_or_province": {Name: "threat.indicator.x509.issuer.state_or_province", DataType: "keyword", Array: true, Description: "List of state or province names (ST, S, or P)"}, + "threat.indicator.x509.not_after": {Name: "threat.indicator.x509.not_after", DataType: "date", Description: "Time at which the certificate is no longer considered valid."}, + "threat.indicator.x509.not_before": {Name: "threat.indicator.x509.not_before", DataType: "date", Description: "Time at which the certificate is first considered valid."}, + "threat.indicator.x509.public_key_algorithm": {Name: "threat.indicator.x509.public_key_algorithm", DataType: "keyword", Description: "Algorithm used to generate the public key."}, + "threat.indicator.x509.public_key_curve": {Name: "threat.indicator.x509.public_key_curve", DataType: "keyword", Description: "The curve used by the elliptic curve public key algorithm. This is algorithm specific."}, + "threat.indicator.x509.public_key_exponent": {Name: "threat.indicator.x509.public_key_exponent", DataType: "long", Description: "Exponent used to derive the public key. This is algorithm specific."}, + "threat.indicator.x509.public_key_size": {Name: "threat.indicator.x509.public_key_size", DataType: "long", Description: "The size of the public key space in bits."}, + "threat.indicator.x509.serial_number": {Name: "threat.indicator.x509.serial_number", DataType: "keyword", Description: "Unique serial number issued by the certificate authority. For consistency, if this value is alphanumeric, it should be formatted without colons and uppercase characters."}, + "threat.indicator.x509.signature_algorithm": {Name: "threat.indicator.x509.signature_algorithm", DataType: "keyword", Description: "Identifier for certificate signature algorithm. We recommend using names found in Go Lang Crypto library. See https://github.com/golang/go/blob/go1.14/src/crypto/x509/x509.go#L337-L353."}, + "threat.indicator.x509.subject.common_name": {Name: "threat.indicator.x509.subject.common_name", DataType: "keyword", Array: true, Description: "List of common names (CN) of subject."}, + "threat.indicator.x509.subject.country": {Name: "threat.indicator.x509.subject.country", DataType: "keyword", Array: true, Description: "List of country \\(C) code"}, + "threat.indicator.x509.subject.distinguished_name": {Name: "threat.indicator.x509.subject.distinguished_name", DataType: "keyword", Description: "Distinguished name (DN) of the certificate subject entity."}, + "threat.indicator.x509.subject.locality": {Name: "threat.indicator.x509.subject.locality", DataType: "keyword", Array: true, Description: "List of locality names (L)"}, + "threat.indicator.x509.subject.organization": {Name: "threat.indicator.x509.subject.organization", DataType: "keyword", Array: true, Description: "List of organizations (O) of subject."}, + "threat.indicator.x509.subject.organizational_unit": {Name: "threat.indicator.x509.subject.organizational_unit", DataType: "keyword", Array: true, Description: "List of organizational units (OU) of subject."}, + "threat.indicator.x509.subject.state_or_province": {Name: "threat.indicator.x509.subject.state_or_province", DataType: "keyword", Array: true, Description: "List of state or province names (ST, S, or P)"}, + "threat.indicator.x509.version_number": {Name: "threat.indicator.x509.version_number", DataType: "keyword", Description: "Version of x509 format."}, + "threat.software.alias": {Name: "threat.software.alias", DataType: "keyword", Array: true, Description: "The alias(es) of the software for a set of related intrusion activity that are tracked by a common name in the security community.\nWhile not required, you can use a MITRE ATT&CK® associated software description."}, + "threat.software.id": {Name: "threat.software.id", DataType: "keyword", Description: "The id of the software used by this threat to conduct behavior commonly modeled using MITRE ATT&CK®.\nWhile not required, you can use a MITRE ATT&CK® software id."}, + "threat.software.name": {Name: "threat.software.name", DataType: "keyword", Description: "The name of the software used by this threat to conduct behavior commonly modeled using MITRE ATT&CK®.\nWhile not required, you can use a MITRE ATT&CK® software name."}, + "threat.software.platforms": {Name: "threat.software.platforms", DataType: "keyword", Array: true, Pattern: "(?:AWS|Azure|Azure AD|GCP|Linux|Network|Office 365|SaaS|Windows|macOS)", Description: "The platforms of the software used by this threat to conduct behavior commonly modeled using MITRE ATT&CK®.\nWhile not required, you can use MITRE ATT&CK® software platform values."}, + "threat.software.reference": {Name: "threat.software.reference", DataType: "keyword", Description: "The reference URL of the software used by this threat to conduct behavior commonly modeled using MITRE ATT&CK®.\nWhile not required, you can use a MITRE ATT&CK® software reference URL."}, + "threat.software.type": {Name: "threat.software.type", DataType: "keyword", Pattern: "(?:Malware|Tool)", Description: "The type of software used by this threat to conduct behavior commonly modeled using MITRE ATT&CK®.\nWhile not required, you can use a MITRE ATT&CK® software type."}, + "threat.tactic.id": {Name: "threat.tactic.id", DataType: "keyword", Array: true, Description: "The id of tactic used by this threat. You can use a MITRE ATT&CK® tactic, for example. (ex. https://attack.mitre.org/tactics/TA0002/ )"}, + "threat.tactic.name": {Name: "threat.tactic.name", DataType: "keyword", Array: true, Description: "Name of the type of tactic used by this threat. You can use a MITRE ATT&CK® tactic, for example. (ex. https://attack.mitre.org/tactics/TA0002/)"}, + "threat.tactic.reference": {Name: "threat.tactic.reference", DataType: "keyword", Array: true, Description: "The reference url of tactic used by this threat. You can use a MITRE ATT&CK® tactic, for example. (ex. https://attack.mitre.org/tactics/TA0002/ )"}, + "threat.technique.id": {Name: "threat.technique.id", DataType: "keyword", Array: true, Description: "The id of technique used by this threat. You can use a MITRE ATT&CK® technique, for example. (ex. https://attack.mitre.org/techniques/T1059/)"}, + "threat.technique.name": {Name: "threat.technique.name", DataType: "keyword", Array: true, Description: "The name of technique used by this threat. You can use a MITRE ATT&CK® technique, for example. (ex. https://attack.mitre.org/techniques/T1059/)"}, + "threat.technique.reference": {Name: "threat.technique.reference", DataType: "keyword", Array: true, Description: "The reference url of technique used by this threat. You can use a MITRE ATT&CK® technique, for example. (ex. https://attack.mitre.org/techniques/T1059/)"}, + "threat.technique.subtechnique.id": {Name: "threat.technique.subtechnique.id", DataType: "keyword", Array: true, Description: "The full id of subtechnique used by this threat. You can use a MITRE ATT&CK® subtechnique, for example. (ex. https://attack.mitre.org/techniques/T1059/001/)"}, + "threat.technique.subtechnique.name": {Name: "threat.technique.subtechnique.name", DataType: "keyword", Array: true, Description: "The name of subtechnique used by this threat. You can use a MITRE ATT&CK® subtechnique, for example. (ex. https://attack.mitre.org/techniques/T1059/001/)"}, + "threat.technique.subtechnique.reference": {Name: "threat.technique.subtechnique.reference", DataType: "keyword", Array: true, Description: "The reference url of subtechnique used by this threat. You can use a MITRE ATT&CK® subtechnique, for example. (ex. https://attack.mitre.org/techniques/T1059/001/)"}, + "tls.cipher": {Name: "tls.cipher", DataType: "keyword", Description: "String indicating the cipher used during the current connection."}, + "tls.client.certificate": {Name: "tls.client.certificate", DataType: "keyword", Description: "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."}, + "tls.client.certificate_chain": {Name: "tls.client.certificate_chain", DataType: "keyword", Array: true, Description: "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."}, + "tls.client.hash.md5": {Name: "tls.client.hash.md5", DataType: "keyword", Description: "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."}, + "tls.client.hash.sha1": {Name: "tls.client.hash.sha1", DataType: "keyword", Description: "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."}, + "tls.client.hash.sha256": {Name: "tls.client.hash.sha256", DataType: "keyword", Description: "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."}, + "tls.client.issuer": {Name: "tls.client.issuer", DataType: "keyword", Description: "Distinguished name of subject of the issuer of the x.509 certificate presented by the client."}, + "tls.client.ja3": {Name: "tls.client.ja3", DataType: "keyword", Description: "A hash that identifies clients based on how they perform an SSL/TLS handshake."}, + "tls.client.not_after": {Name: "tls.client.not_after", DataType: "date", Description: "Date/Time indicating when client certificate is no longer considered valid."}, + "tls.client.not_before": {Name: "tls.client.not_before", DataType: "date", Description: "Date/Time indicating when client certificate is first considered valid."}, + "tls.client.server_name": {Name: "tls.client.server_name", DataType: "keyword", Description: "Also called an SNI, this tells the server which hostname to which the client is attempting to connect to. When this value is available, it should get copied to `destination.domain`."}, + "tls.client.subject": {Name: "tls.client.subject", DataType: "keyword", Description: "Distinguished name of subject of the x.509 certificate presented by the client."}, + "tls.client.supported_ciphers": {Name: "tls.client.supported_ciphers", DataType: "keyword", Array: true, Description: "Array of ciphers offered by the client during the client hello."}, + "tls.client.x509.alternative_names": {Name: "tls.client.x509.alternative_names", DataType: "keyword", Array: true, Description: "List of subject alternative names (SAN). Name types vary by certificate authority and certificate type but commonly contain IP addresses, DNS names (and wildcards), and email addresses."}, + "tls.client.x509.issuer.common_name": {Name: "tls.client.x509.issuer.common_name", DataType: "keyword", Array: true, Description: "List of common name (CN) of issuing certificate authority."}, + "tls.client.x509.issuer.country": {Name: "tls.client.x509.issuer.country", DataType: "keyword", Array: true, Description: "List of country \\(C) codes"}, + "tls.client.x509.issuer.distinguished_name": {Name: "tls.client.x509.issuer.distinguished_name", DataType: "keyword", Description: "Distinguished name (DN) of issuing certificate authority."}, + "tls.client.x509.issuer.locality": {Name: "tls.client.x509.issuer.locality", DataType: "keyword", Array: true, Description: "List of locality names (L)"}, + "tls.client.x509.issuer.organization": {Name: "tls.client.x509.issuer.organization", DataType: "keyword", Array: true, Description: "List of organizations (O) of issuing certificate authority."}, + "tls.client.x509.issuer.organizational_unit": {Name: "tls.client.x509.issuer.organizational_unit", DataType: "keyword", Array: true, Description: "List of organizational units (OU) of issuing certificate authority."}, + "tls.client.x509.issuer.state_or_province": {Name: "tls.client.x509.issuer.state_or_province", DataType: "keyword", Array: true, Description: "List of state or province names (ST, S, or P)"}, + "tls.client.x509.not_after": {Name: "tls.client.x509.not_after", DataType: "date", Description: "Time at which the certificate is no longer considered valid."}, + "tls.client.x509.not_before": {Name: "tls.client.x509.not_before", DataType: "date", Description: "Time at which the certificate is first considered valid."}, + "tls.client.x509.public_key_algorithm": {Name: "tls.client.x509.public_key_algorithm", DataType: "keyword", Description: "Algorithm used to generate the public key."}, + "tls.client.x509.public_key_curve": {Name: "tls.client.x509.public_key_curve", DataType: "keyword", Description: "The curve used by the elliptic curve public key algorithm. This is algorithm specific."}, + "tls.client.x509.public_key_exponent": {Name: "tls.client.x509.public_key_exponent", DataType: "long", Description: "Exponent used to derive the public key. This is algorithm specific."}, + "tls.client.x509.public_key_size": {Name: "tls.client.x509.public_key_size", DataType: "long", Description: "The size of the public key space in bits."}, + "tls.client.x509.serial_number": {Name: "tls.client.x509.serial_number", DataType: "keyword", Description: "Unique serial number issued by the certificate authority. For consistency, if this value is alphanumeric, it should be formatted without colons and uppercase characters."}, + "tls.client.x509.signature_algorithm": {Name: "tls.client.x509.signature_algorithm", DataType: "keyword", Description: "Identifier for certificate signature algorithm. We recommend using names found in Go Lang Crypto library. See https://github.com/golang/go/blob/go1.14/src/crypto/x509/x509.go#L337-L353."}, + "tls.client.x509.subject.common_name": {Name: "tls.client.x509.subject.common_name", DataType: "keyword", Array: true, Description: "List of common names (CN) of subject."}, + "tls.client.x509.subject.country": {Name: "tls.client.x509.subject.country", DataType: "keyword", Array: true, Description: "List of country \\(C) code"}, + "tls.client.x509.subject.distinguished_name": {Name: "tls.client.x509.subject.distinguished_name", DataType: "keyword", Description: "Distinguished name (DN) of the certificate subject entity."}, + "tls.client.x509.subject.locality": {Name: "tls.client.x509.subject.locality", DataType: "keyword", Array: true, Description: "List of locality names (L)"}, + "tls.client.x509.subject.organization": {Name: "tls.client.x509.subject.organization", DataType: "keyword", Array: true, Description: "List of organizations (O) of subject."}, + "tls.client.x509.subject.organizational_unit": {Name: "tls.client.x509.subject.organizational_unit", DataType: "keyword", Array: true, Description: "List of organizational units (OU) of subject."}, + "tls.client.x509.subject.state_or_province": {Name: "tls.client.x509.subject.state_or_province", DataType: "keyword", Array: true, Description: "List of state or province names (ST, S, or P)"}, + "tls.client.x509.version_number": {Name: "tls.client.x509.version_number", DataType: "keyword", Description: "Version of x509 format."}, + "tls.curve": {Name: "tls.curve", DataType: "keyword", Description: "String indicating the curve used for the given cipher, when applicable."}, + "tls.established": {Name: "tls.established", DataType: "boolean", Description: "Boolean flag indicating if the TLS negotiation was successful and transitioned to an encrypted tunnel."}, + "tls.next_protocol": {Name: "tls.next_protocol", DataType: "keyword", Description: "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."}, + "tls.resumed": {Name: "tls.resumed", DataType: "boolean", Description: "Boolean flag indicating if this TLS connection was resumed from an existing TLS negotiation."}, + "tls.server.certificate": {Name: "tls.server.certificate", DataType: "keyword", Description: "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."}, + "tls.server.certificate_chain": {Name: "tls.server.certificate_chain", DataType: "keyword", Array: true, Description: "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."}, + "tls.server.hash.md5": {Name: "tls.server.hash.md5", DataType: "keyword", Description: "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."}, + "tls.server.hash.sha1": {Name: "tls.server.hash.sha1", DataType: "keyword", Description: "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."}, + "tls.server.hash.sha256": {Name: "tls.server.hash.sha256", DataType: "keyword", Description: "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."}, + "tls.server.issuer": {Name: "tls.server.issuer", DataType: "keyword", Description: "Subject of the issuer of the x.509 certificate presented by the server."}, + "tls.server.ja3s": {Name: "tls.server.ja3s", DataType: "keyword", Description: "A hash that identifies servers based on how they perform an SSL/TLS handshake."}, + "tls.server.not_after": {Name: "tls.server.not_after", DataType: "date", Description: "Timestamp indicating when server certificate is no longer considered valid."}, + "tls.server.not_before": {Name: "tls.server.not_before", DataType: "date", Description: "Timestamp indicating when server certificate is first considered valid."}, + "tls.server.subject": {Name: "tls.server.subject", DataType: "keyword", Description: "Subject of the x.509 certificate presented by the server."}, + "tls.server.x509.alternative_names": {Name: "tls.server.x509.alternative_names", DataType: "keyword", Array: true, Description: "List of subject alternative names (SAN). Name types vary by certificate authority and certificate type but commonly contain IP addresses, DNS names (and wildcards), and email addresses."}, + "tls.server.x509.issuer.common_name": {Name: "tls.server.x509.issuer.common_name", DataType: "keyword", Array: true, Description: "List of common name (CN) of issuing certificate authority."}, + "tls.server.x509.issuer.country": {Name: "tls.server.x509.issuer.country", DataType: "keyword", Array: true, Description: "List of country \\(C) codes"}, + "tls.server.x509.issuer.distinguished_name": {Name: "tls.server.x509.issuer.distinguished_name", DataType: "keyword", Description: "Distinguished name (DN) of issuing certificate authority."}, + "tls.server.x509.issuer.locality": {Name: "tls.server.x509.issuer.locality", DataType: "keyword", Array: true, Description: "List of locality names (L)"}, + "tls.server.x509.issuer.organization": {Name: "tls.server.x509.issuer.organization", DataType: "keyword", Array: true, Description: "List of organizations (O) of issuing certificate authority."}, + "tls.server.x509.issuer.organizational_unit": {Name: "tls.server.x509.issuer.organizational_unit", DataType: "keyword", Array: true, Description: "List of organizational units (OU) of issuing certificate authority."}, + "tls.server.x509.issuer.state_or_province": {Name: "tls.server.x509.issuer.state_or_province", DataType: "keyword", Array: true, Description: "List of state or province names (ST, S, or P)"}, + "tls.server.x509.not_after": {Name: "tls.server.x509.not_after", DataType: "date", Description: "Time at which the certificate is no longer considered valid."}, + "tls.server.x509.not_before": {Name: "tls.server.x509.not_before", DataType: "date", Description: "Time at which the certificate is first considered valid."}, + "tls.server.x509.public_key_algorithm": {Name: "tls.server.x509.public_key_algorithm", DataType: "keyword", Description: "Algorithm used to generate the public key."}, + "tls.server.x509.public_key_curve": {Name: "tls.server.x509.public_key_curve", DataType: "keyword", Description: "The curve used by the elliptic curve public key algorithm. This is algorithm specific."}, + "tls.server.x509.public_key_exponent": {Name: "tls.server.x509.public_key_exponent", DataType: "long", Description: "Exponent used to derive the public key. This is algorithm specific."}, + "tls.server.x509.public_key_size": {Name: "tls.server.x509.public_key_size", DataType: "long", Description: "The size of the public key space in bits."}, + "tls.server.x509.serial_number": {Name: "tls.server.x509.serial_number", DataType: "keyword", Description: "Unique serial number issued by the certificate authority. For consistency, if this value is alphanumeric, it should be formatted without colons and uppercase characters."}, + "tls.server.x509.signature_algorithm": {Name: "tls.server.x509.signature_algorithm", DataType: "keyword", Description: "Identifier for certificate signature algorithm. We recommend using names found in Go Lang Crypto library. See https://github.com/golang/go/blob/go1.14/src/crypto/x509/x509.go#L337-L353."}, + "tls.server.x509.subject.common_name": {Name: "tls.server.x509.subject.common_name", DataType: "keyword", Array: true, Description: "List of common names (CN) of subject."}, + "tls.server.x509.subject.country": {Name: "tls.server.x509.subject.country", DataType: "keyword", Array: true, Description: "List of country \\(C) code"}, + "tls.server.x509.subject.distinguished_name": {Name: "tls.server.x509.subject.distinguished_name", DataType: "keyword", Description: "Distinguished name (DN) of the certificate subject entity."}, + "tls.server.x509.subject.locality": {Name: "tls.server.x509.subject.locality", DataType: "keyword", Array: true, Description: "List of locality names (L)"}, + "tls.server.x509.subject.organization": {Name: "tls.server.x509.subject.organization", DataType: "keyword", Array: true, Description: "List of organizations (O) of subject."}, + "tls.server.x509.subject.organizational_unit": {Name: "tls.server.x509.subject.organizational_unit", DataType: "keyword", Array: true, Description: "List of organizational units (OU) of subject."}, + "tls.server.x509.subject.state_or_province": {Name: "tls.server.x509.subject.state_or_province", DataType: "keyword", Array: true, Description: "List of state or province names (ST, S, or P)"}, + "tls.server.x509.version_number": {Name: "tls.server.x509.version_number", DataType: "keyword", Description: "Version of x509 format."}, + "tls.version": {Name: "tls.version", DataType: "keyword", Description: "Numeric part of the version parsed from the original string."}, + "tls.version_protocol": {Name: "tls.version_protocol", DataType: "keyword", Description: "Normalized lowercase protocol name parsed from original string."}, + "trace.id": {Name: "trace.id", DataType: "keyword", Description: "Unique identifier of the trace.\nA trace groups multiple events like transactions that belong together. For example, a user request handled by multiple inter-connected services."}, + "transaction.id": {Name: "transaction.id", DataType: "keyword", Description: "Unique identifier of the transaction within the scope of its trace.\nA transaction is the highest level of work measured within a service, such as a request to a server."}, + "url.domain": {Name: "url.domain", DataType: "keyword", Description: "Domain of the url, such as \"www.elastic.co\".\nIn 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.\nIf the URL contains a literal IPv6 address enclosed by `[` and `]` (IETF RFC 2732), the `[` and `]` characters should also be captured in the `domain` field."}, + "url.extension": {Name: "url.extension", DataType: "keyword", Description: "The field contains the file extension from the original request url, excluding the leading dot.\nThe file extension is only set if it exists, as not every url has a file extension.\nThe leading period must not be included. For example, the value must be \"png\", not \".png\".\nNote that when the file name has multiple extensions (example.tar.gz), only the last one should be captured (\"gz\", not \"tar.gz\")."}, + "url.fragment": {Name: "url.fragment", DataType: "keyword", Description: "Portion of the url after the `#`, such as \"top\".\nThe `#` is not part of the fragment."}, + "url.full": {Name: "url.full", DataType: "wildcard", Description: "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."}, + "url.original": {Name: "url.original", DataType: "wildcard", Description: "Unmodified original url as seen in the event source.\nNote 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.\nThis field is meant to represent the URL as it was observed, complete or not."}, + "url.password": {Name: "url.password", DataType: "keyword", Description: "Password of the request."}, + "url.path": {Name: "url.path", DataType: "wildcard", Description: "Path of the request, such as \"/search\"."}, + "url.port": {Name: "url.port", DataType: "long", Description: "Port of the request, such as 443."}, + "url.query": {Name: "url.query", DataType: "keyword", Description: "The query field describes the query string of the request, such as \"q=elasticsearch\".\nThe `?` 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."}, + "url.registered_domain": {Name: "url.registered_domain", DataType: "keyword", Description: "The highest registered url domain, stripped of the subdomain.\nFor example, the registered domain for \"foo.example.com\" is \"example.com\".\nThis 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\"."}, + "url.scheme": {Name: "url.scheme", DataType: "keyword", Description: "Scheme of the request, such as \"https\".\nNote: The `:` is not part of the scheme."}, + "url.subdomain": {Name: "url.subdomain", DataType: "keyword", Description: "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.\nFor 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."}, + "url.top_level_domain": {Name: "url.top_level_domain", DataType: "keyword", Description: "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\".\nThis 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\"."}, + "url.username": {Name: "url.username", DataType: "keyword", Description: "Username of the request."}, + "user.changes.domain": {Name: "user.changes.domain", DataType: "keyword", Description: "Name of the directory the user is a member of.\nFor example, an LDAP or Active Directory domain name."}, + "user.changes.email": {Name: "user.changes.email", DataType: "keyword", Description: "User email address."}, + "user.changes.full_name": {Name: "user.changes.full_name", DataType: "keyword", Description: "User's full name, if available."}, + "user.changes.group.domain": {Name: "user.changes.group.domain", DataType: "keyword", Description: "Name of the directory the group is a member of.\nFor example, an LDAP or Active Directory domain name."}, + "user.changes.group.id": {Name: "user.changes.group.id", DataType: "keyword", Description: "Unique identifier for the group on the system/platform."}, + "user.changes.group.name": {Name: "user.changes.group.name", DataType: "keyword", Description: "Name of the group."}, + "user.changes.hash": {Name: "user.changes.hash", DataType: "keyword", Description: "Unique user hash to correlate information for a user in anonymized form.\nUseful if `user.id` or `user.name` contain confidential information and cannot be used."}, + "user.changes.id": {Name: "user.changes.id", DataType: "keyword", Description: "Unique identifier of the user."}, + "user.changes.name": {Name: "user.changes.name", DataType: "keyword", Description: "Short name or login of the user."}, + "user.changes.roles": {Name: "user.changes.roles", DataType: "keyword", Array: true, Description: "Array of user roles at the time of the event."}, + "user.domain": {Name: "user.domain", DataType: "keyword", Description: "Name of the directory the user is a member of.\nFor example, an LDAP or Active Directory domain name."}, + "user.effective.domain": {Name: "user.effective.domain", DataType: "keyword", Description: "Name of the directory the user is a member of.\nFor example, an LDAP or Active Directory domain name."}, + "user.effective.email": {Name: "user.effective.email", DataType: "keyword", Description: "User email address."}, + "user.effective.full_name": {Name: "user.effective.full_name", DataType: "keyword", Description: "User's full name, if available."}, + "user.effective.group.domain": {Name: "user.effective.group.domain", DataType: "keyword", Description: "Name of the directory the group is a member of.\nFor example, an LDAP or Active Directory domain name."}, + "user.effective.group.id": {Name: "user.effective.group.id", DataType: "keyword", Description: "Unique identifier for the group on the system/platform."}, + "user.effective.group.name": {Name: "user.effective.group.name", DataType: "keyword", Description: "Name of the group."}, + "user.effective.hash": {Name: "user.effective.hash", DataType: "keyword", Description: "Unique user hash to correlate information for a user in anonymized form.\nUseful if `user.id` or `user.name` contain confidential information and cannot be used."}, + "user.effective.id": {Name: "user.effective.id", DataType: "keyword", Description: "Unique identifier of the user."}, + "user.effective.name": {Name: "user.effective.name", DataType: "keyword", Description: "Short name or login of the user."}, + "user.effective.roles": {Name: "user.effective.roles", DataType: "keyword", Array: true, Description: "Array of user roles at the time of the event."}, + "user.email": {Name: "user.email", DataType: "keyword", Description: "User email address."}, + "user.full_name": {Name: "user.full_name", DataType: "keyword", Description: "User's full name, if available."}, + "user.group.domain": {Name: "user.group.domain", DataType: "keyword", Description: "Name of the directory the group is a member of.\nFor example, an LDAP or Active Directory domain name."}, + "user.group.id": {Name: "user.group.id", DataType: "keyword", Description: "Unique identifier for the group on the system/platform."}, + "user.group.name": {Name: "user.group.name", DataType: "keyword", Description: "Name of the group."}, + "user.hash": {Name: "user.hash", DataType: "keyword", Description: "Unique user hash to correlate information for a user in anonymized form.\nUseful if `user.id` or `user.name` contain confidential information and cannot be used."}, + "user.id": {Name: "user.id", DataType: "keyword", Description: "Unique identifier of the user."}, + "user.name": {Name: "user.name", DataType: "keyword", Description: "Short name or login of the user."}, + "user.risk.calculated_level": {Name: "user.risk.calculated_level", DataType: "keyword", Description: "A risk classification level calculated by an internal system as part of entity analytics and entity risk scoring."}, + "user.risk.calculated_score": {Name: "user.risk.calculated_score", DataType: "float", Description: "A risk classification score calculated by an internal system as part of entity analytics and entity risk scoring."}, + "user.risk.calculated_score_norm": {Name: "user.risk.calculated_score_norm", DataType: "float", Description: "A risk classification score calculated by an internal system as part of entity analytics and entity risk scoring, and normalized to a range of 0 to 100."}, + "user.risk.static_level": {Name: "user.risk.static_level", DataType: "keyword", Description: "A risk classification level obtained from outside the system, such as from some external Threat Intelligence Platform."}, + "user.risk.static_score": {Name: "user.risk.static_score", DataType: "float", Description: "A risk classification score obtained from outside the system, such as from some external Threat Intelligence Platform."}, + "user.risk.static_score_norm": {Name: "user.risk.static_score_norm", DataType: "float", Description: "A risk classification score obtained from outside the system, such as from some external Threat Intelligence Platform, and normalized to a range of 0 to 100."}, + "user.roles": {Name: "user.roles", DataType: "keyword", Array: true, Description: "Array of user roles at the time of the event."}, + "user.target.domain": {Name: "user.target.domain", DataType: "keyword", Description: "Name of the directory the user is a member of.\nFor example, an LDAP or Active Directory domain name."}, + "user.target.email": {Name: "user.target.email", DataType: "keyword", Description: "User email address."}, + "user.target.full_name": {Name: "user.target.full_name", DataType: "keyword", Description: "User's full name, if available."}, + "user.target.group.domain": {Name: "user.target.group.domain", DataType: "keyword", Description: "Name of the directory the group is a member of.\nFor example, an LDAP or Active Directory domain name."}, + "user.target.group.id": {Name: "user.target.group.id", DataType: "keyword", Description: "Unique identifier for the group on the system/platform."}, + "user.target.group.name": {Name: "user.target.group.name", DataType: "keyword", Description: "Name of the group."}, + "user.target.hash": {Name: "user.target.hash", DataType: "keyword", Description: "Unique user hash to correlate information for a user in anonymized form.\nUseful if `user.id` or `user.name` contain confidential information and cannot be used."}, + "user.target.id": {Name: "user.target.id", DataType: "keyword", Description: "Unique identifier of the user."}, + "user.target.name": {Name: "user.target.name", DataType: "keyword", Description: "Short name or login of the user."}, + "user.target.roles": {Name: "user.target.roles", DataType: "keyword", Array: true, Description: "Array of user roles at the time of the event."}, + "user_agent.device.name": {Name: "user_agent.device.name", DataType: "keyword", Description: "Name of the device."}, + "user_agent.name": {Name: "user_agent.name", DataType: "keyword", Description: "Name of the user agent."}, + "user_agent.original": {Name: "user_agent.original", DataType: "keyword", Description: "Unparsed user_agent string."}, + "user_agent.os.family": {Name: "user_agent.os.family", DataType: "keyword", Description: "OS family (such as redhat, debian, freebsd, windows)."}, + "user_agent.os.full": {Name: "user_agent.os.full", DataType: "keyword", Description: "Operating system name, including the version or code name."}, + "user_agent.os.kernel": {Name: "user_agent.os.kernel", DataType: "keyword", Description: "Operating system kernel version as a raw string."}, + "user_agent.os.name": {Name: "user_agent.os.name", DataType: "keyword", Description: "Operating system name, without the version."}, + "user_agent.os.platform": {Name: "user_agent.os.platform", DataType: "keyword", Description: "Operating system platform (such centos, ubuntu, windows)."}, + "user_agent.os.type": {Name: "user_agent.os.type", DataType: "keyword", Pattern: "(?:android|ios|linux|macos|unix|windows)", Description: "Use the `os.type` field to categorize the operating system into one of the broad commercial families.\nIf the OS you're dealing with is not listed as an expected value, the field should not be populated. Please let us know by opening an issue with ECS, to propose its addition."}, + "user_agent.os.version": {Name: "user_agent.os.version", DataType: "keyword", Description: "Operating system version as a raw string."}, + "user_agent.version": {Name: "user_agent.version", DataType: "keyword", Description: "Version of the user agent."}, + "vulnerability.category": {Name: "vulnerability.category", DataType: "keyword", Array: true, Description: "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])\nThis field must be an array."}, + "vulnerability.classification": {Name: "vulnerability.classification", DataType: "keyword", Description: "The classification of the vulnerability scoring system. For example (https://www.first.org/cvss/)"}, + "vulnerability.description": {Name: "vulnerability.description", DataType: "keyword", Description: "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])"}, + "vulnerability.enumeration": {Name: "vulnerability.enumeration", DataType: "keyword", Description: "The type of identifier used for this vulnerability. For example (https://cve.mitre.org/about/)"}, + "vulnerability.id": {Name: "vulnerability.id", DataType: "keyword", Description: "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]"}, + "vulnerability.reference": {Name: "vulnerability.reference", DataType: "keyword", Description: "A resource that provides additional information, context, and mitigations for the identified vulnerability."}, + "vulnerability.report_id": {Name: "vulnerability.report_id", DataType: "keyword", Description: "The report or scan identification number."}, + "vulnerability.scanner.vendor": {Name: "vulnerability.scanner.vendor", DataType: "keyword", Description: "The name of the vulnerability scanner vendor."}, + "vulnerability.score.base": {Name: "vulnerability.score.base", DataType: "float", Description: "Scores can range from 0.0 to 10.0, with 10.0 being the most severe.\nBase 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)"}, + "vulnerability.score.environmental": {Name: "vulnerability.score.environmental", DataType: "float", Description: "Scores can range from 0.0 to 10.0, with 10.0 being the most severe.\nEnvironmental scores cover an assessment for any modified Base metrics, confidentiality, integrity, and availability requirements. For example (https://www.first.org/cvss/specification-document)"}, + "vulnerability.score.temporal": {Name: "vulnerability.score.temporal", DataType: "float", Description: "Scores can range from 0.0 to 10.0, with 10.0 being the most severe.\nTemporal scores cover an assessment for code maturity, remediation level, and confidence. For example (https://www.first.org/cvss/specification-document)"}, + "vulnerability.score.version": {Name: "vulnerability.score.version", DataType: "keyword", Description: "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.\nCVSS 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)"}, + "vulnerability.severity": {Name: "vulnerability.severity", DataType: "keyword", Description: "The severity of the vulnerability can help with metrics and internal prioritization regarding remediation. For example (https://nvd.nist.gov/vuln-metrics/cvss)"}, +}