as:
  description: An autonomous system (AS) is a collection of connected Internet Protocol
    (IP) routing prefixes under the control of one or more network operators on behalf
    of a single administrative entity or domain that presents a common, clearly defined
    routing policy to the internet.
  fields:
    as.number:
      dashed_name: as-number
      description: Unique number allocated to the autonomous system. The autonomous
        system number (ASN) uniquely identifies each network on the Internet.
      example: 15169
      flat_name: as.number
      level: extended
      name: number
      normalize: []
      short: Unique number allocated to the autonomous system.
      type: long
    as.organization.name:
      dashed_name: as-organization-name
      description: Organization name.
      example: Google LLC
      flat_name: as.organization.name
      ignore_above: 1024
      level: extended
      multi_fields:
      - flat_name: as.organization.name.text
        name: text
        norms: false
        type: text
      name: organization.name
      normalize: []
      short: Organization name.
      type: keyword
  group: 2
  name: as
  prefix: as.
  reusable:
    expected:
    - as: as
      at: client
      full: client.as
    - as: as
      at: destination
      full: destination.as
    - as: as
      at: server
      full: server.as
    - as: as
      at: source
      full: source.as
    - as: as
      at: threat.indicator
      beta: Reusing the `as` fields in this location is currently considered beta.
      full: threat.indicator.as
    - as: as
      at: threat.enrichments.indicator
      beta: Reusing the `as` fields in this location is currently considered beta.
      full: threat.enrichments.indicator.as
    top_level: false
  short: Fields describing an Autonomous System (Internet routing prefix).
  title: Autonomous System
  type: group
base:
  description: The `base` field set contains all fields which are at the root of the
    events. These fields are common across all types of events.
  fields:
    '@timestamp':
      dashed_name: timestamp
      description: 'Date/time when the event originated.

        This is the date/time extracted from the event, typically representing when
        the event was generated by the source.

        If the event source has no original timestamp, this value is typically populated
        by the first time the event was received by the pipeline.

        Required field for all events.'
      example: '2016-05-23T08:05:34.853Z'
      flat_name: '@timestamp'
      level: core
      name: '@timestamp'
      normalize: []
      required: true
      short: Date/time when the event originated.
      type: date
    labels:
      dashed_name: labels
      description: 'Custom key/value pairs.

        Can be used to add meta information to events. Should not contain nested objects.
        All values are stored as keyword.

        Example: `docker` and `k8s` labels.'
      example: '{"application": "foo-bar", "env": "production"}'
      flat_name: labels
      level: core
      name: labels
      normalize: []
      object_type: keyword
      short: Custom key/value pairs.
      type: object
    message:
      dashed_name: message
      description: 'For log events the message field contains the log message, optimized
        for viewing in a log viewer.

        For structured logs without an original message field, other fields can be
        concatenated to form a human-readable summary of the event.

        If multiple messages exist, they can be combined into one message.'
      example: Hello World
      flat_name: message
      level: core
      name: message
      normalize: []
      norms: false
      short: Log message optimized for viewing in a log viewer.
      type: text
    tags:
      dashed_name: tags
      description: List of keywords used to tag each event.
      example: '["production", "env2"]'
      flat_name: tags
      ignore_above: 1024
      level: core
      name: tags
      normalize:
      - array
      short: List of keywords used to tag each event.
      type: keyword
  group: 1
  name: base
  prefix: ''
  root: true
  short: All fields defined directly at the root of the events.
  title: Base
  type: group
client:
  description: 'A client is defined as the initiator of a network connection for events
    regarding sessions, connections, or bidirectional flow records.

    For TCP events, the client is the initiator of the TCP connection that sends the
    SYN packet(s). For other protocols, the client is generally the initiator or requestor
    in the network transaction. Some systems use the term "originator" to refer the
    client in TCP connections. The client fields describe details about the system
    acting as the client in the network event. Client fields are usually populated
    in conjunction with server fields. Client fields are generally not populated for
    packet-level events.

    Client / server representations can add semantic context to an exchange, which
    is helpful to visualize the data in certain situations. If your context falls
    in that category, you should still ensure that source and destination are filled
    appropriately.'
  fields:
    client.address:
      dashed_name: client-address
      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.

        Then it should be duplicated to `.ip` or `.domain`, depending on which one
        it is.'
      flat_name: client.address
      ignore_above: 1024
      level: extended
      name: address
      normalize: []
      short: Client network address.
      type: keyword
    client.as.number:
      dashed_name: client-as-number
      description: Unique number allocated to the autonomous system. The autonomous
        system number (ASN) uniquely identifies each network on the Internet.
      example: 15169
      flat_name: client.as.number
      level: extended
      name: number
      normalize: []
      original_fieldset: as
      short: Unique number allocated to the autonomous system.
      type: long
    client.as.organization.name:
      dashed_name: client-as-organization-name
      description: Organization name.
      example: Google LLC
      flat_name: client.as.organization.name
      ignore_above: 1024
      level: extended
      multi_fields:
      - flat_name: client.as.organization.name.text
        name: text
        norms: false
        type: text
      name: organization.name
      normalize: []
      original_fieldset: as
      short: Organization name.
      type: keyword
    client.bytes:
      dashed_name: client-bytes
      description: Bytes sent from the client to the server.
      example: 184
      flat_name: client.bytes
      format: bytes
      level: core
      name: bytes
      normalize: []
      short: Bytes sent from the client to the server.
      type: long
    client.domain:
      dashed_name: client-domain
      description: Client domain.
      flat_name: client.domain
      ignore_above: 1024
      level: core
      name: domain
      normalize: []
      short: Client domain.
      type: keyword
    client.geo.city_name:
      dashed_name: client-geo-city-name
      description: City name.
      example: Montreal
      flat_name: client.geo.city_name
      ignore_above: 1024
      level: core
      name: city_name
      normalize: []
      original_fieldset: geo
      short: City name.
      type: keyword
    client.geo.continent_code:
      dashed_name: client-geo-continent-code
      description: Two-letter code representing continent's name.
      example: NA
      flat_name: client.geo.continent_code
      ignore_above: 1024
      level: core
      name: continent_code
      normalize: []
      original_fieldset: geo
      short: Continent code.
      type: keyword
    client.geo.continent_name:
      dashed_name: client-geo-continent-name
      description: Name of the continent.
      example: North America
      flat_name: client.geo.continent_name
      ignore_above: 1024
      level: core
      name: continent_name
      normalize: []
      original_fieldset: geo
      short: Name of the continent.
      type: keyword
    client.geo.country_iso_code:
      dashed_name: client-geo-country-iso-code
      description: Country ISO code.
      example: CA
      flat_name: client.geo.country_iso_code
      ignore_above: 1024
      level: core
      name: country_iso_code
      normalize: []
      original_fieldset: geo
      short: Country ISO code.
      type: keyword
    client.geo.country_name:
      dashed_name: client-geo-country-name
      description: Country name.
      example: Canada
      flat_name: client.geo.country_name
      ignore_above: 1024
      level: core
      name: country_name
      normalize: []
      original_fieldset: geo
      short: Country name.
      type: keyword
    client.geo.location:
      dashed_name: client-geo-location
      description: Longitude and latitude.
      example: '{ "lon": -73.614830, "lat": 45.505918 }'
      flat_name: client.geo.location
      level: core
      name: location
      normalize: []
      original_fieldset: geo
      short: Longitude and latitude.
      type: geo_point
    client.geo.name:
      dashed_name: client-geo-name
      description: 'User-defined description of a location, at the level of granularity
        they care about.

        Could be the name of their data centers, the floor number, if this describes
        a local physical entity, city names.

        Not typically used in automated geolocation.'
      example: boston-dc
      flat_name: client.geo.name
      ignore_above: 1024
      level: extended
      name: name
      normalize: []
      original_fieldset: geo
      short: User-defined description of a location.
      type: keyword
    client.geo.postal_code:
      dashed_name: client-geo-postal-code
      description: 'Postal code associated with the location.

        Values appropriate for this field may also be known as a postcode or ZIP code
        and will vary widely from country to country.'
      example: 94040
      flat_name: client.geo.postal_code
      ignore_above: 1024
      level: core
      name: postal_code
      normalize: []
      original_fieldset: geo
      short: Postal code.
      type: keyword
    client.geo.region_iso_code:
      dashed_name: client-geo-region-iso-code
      description: Region ISO code.
      example: CA-QC
      flat_name: client.geo.region_iso_code
      ignore_above: 1024
      level: core
      name: region_iso_code
      normalize: []
      original_fieldset: geo
      short: Region ISO code.
      type: keyword
    client.geo.region_name:
      dashed_name: client-geo-region-name
      description: Region name.
      example: Quebec
      flat_name: client.geo.region_name
      ignore_above: 1024
      level: core
      name: region_name
      normalize: []
      original_fieldset: geo
      short: Region name.
      type: keyword
    client.geo.timezone:
      dashed_name: client-geo-timezone
      description: The time zone of the location, such as IANA time zone name.
      example: America/Argentina/Buenos_Aires
      flat_name: client.geo.timezone
      ignore_above: 1024
      level: core
      name: timezone
      normalize: []
      original_fieldset: geo
      short: Time zone.
      type: keyword
    client.ip:
      dashed_name: client-ip
      description: IP address of the client (IPv4 or IPv6).
      flat_name: client.ip
      level: core
      name: ip
      normalize: []
      short: IP address of the client.
      type: ip
    client.mac:
      dashed_name: client-mac
      description: 'MAC address of the client.

        The 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.'
      example: 00-00-5E-00-53-23
      flat_name: client.mac
      ignore_above: 1024
      level: core
      name: mac
      normalize: []
      short: MAC address of the client.
      type: keyword
    client.nat.ip:
      dashed_name: client-nat-ip
      description: 'Translated IP of source based NAT sessions (e.g. internal client
        to internet).

        Typically connections traversing load balancers, firewalls, or routers.'
      flat_name: client.nat.ip
      level: extended
      name: nat.ip
      normalize: []
      short: Client NAT ip address
      type: ip
    client.nat.port:
      dashed_name: client-nat-port
      description: 'Translated port of source based NAT sessions (e.g. internal client
        to internet).

        Typically connections traversing load balancers, firewalls, or routers.'
      flat_name: client.nat.port
      format: string
      level: extended
      name: nat.port
      normalize: []
      short: Client NAT port
      type: long
    client.packets:
      dashed_name: client-packets
      description: Packets sent from the client to the server.
      example: 12
      flat_name: client.packets
      level: core
      name: packets
      normalize: []
      short: Packets sent from the client to the server.
      type: long
    client.port:
      dashed_name: client-port
      description: Port of the client.
      flat_name: client.port
      format: string
      level: core
      name: port
      normalize: []
      short: Port of the client.
      type: long
    client.registered_domain:
      dashed_name: client-registered-domain
      description: 'The highest registered client domain, stripped of the subdomain.

        For example, the registered domain for "foo.example.com" is "example.com".

        This value can be determined precisely with a list like the public suffix
        list (http://publicsuffix.org). Trying to approximate this by simply taking
        the last two labels will not work well for TLDs such as "co.uk".'
      example: example.com
      flat_name: client.registered_domain
      ignore_above: 1024
      level: extended
      name: registered_domain
      normalize: []
      short: The highest registered client domain, stripped of the subdomain.
      type: keyword
    client.subdomain:
      dashed_name: client-subdomain
      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.

        For example the subdomain portion of "www.east.mydomain.co.uk" is "east".
        If the domain has multiple levels of subdomain, such as "sub2.sub1.example.com",
        the subdomain field should contain "sub2.sub1", with no trailing period.'
      example: east
      flat_name: client.subdomain
      ignore_above: 1024
      level: extended
      name: subdomain
      normalize: []
      short: The subdomain of the domain.
      type: keyword
    client.top_level_domain:
      dashed_name: client-top-level-domain
      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".

        This value can be determined precisely with a list like the public suffix
        list (http://publicsuffix.org). Trying to approximate this by simply taking
        the last label will not work well for effective TLDs such as "co.uk".'
      example: co.uk
      flat_name: client.top_level_domain
      ignore_above: 1024
      level: extended
      name: top_level_domain
      normalize: []
      short: The effective top level domain (com, org, net, co.uk).
      type: keyword
    client.user.domain:
      dashed_name: client-user-domain
      description: 'Name of the directory the user is a member of.

        For example, an LDAP or Active Directory domain name.'
      flat_name: client.user.domain
      ignore_above: 1024
      level: extended
      name: domain
      normalize: []
      original_fieldset: user
      short: Name of the directory the user is a member of.
      type: keyword
    client.user.email:
      dashed_name: client-user-email
      description: User email address.
      flat_name: client.user.email
      ignore_above: 1024
      level: extended
      name: email
      normalize: []
      original_fieldset: user
      short: User email address.
      type: keyword
    client.user.extra:
      dashed_name: client-user-extra
      description: 'Additional information in key/value pairs.

        For additional information provided by the authenticator to events.

        Note: Not searchable or filterable.'
      enabled: false
      example: '{"authenticator": "ldap", "cipher": "argon2"}'
      flat_name: client.user.extra
      level: custom
      name: extra
      normalize: []
      object_type: keyword
      original_fieldset: user
      short: Custom key/value pairs.
      type: object
    client.user.full_name:
      dashed_name: client-user-full-name
      description: User's full name, if available.
      example: Albert Einstein
      flat_name: client.user.full_name
      ignore_above: 1024
      level: extended
      multi_fields:
      - flat_name: client.user.full_name.text
        name: text
        norms: false
        type: text
      name: full_name
      normalize: []
      original_fieldset: user
      short: User's full name, if available.
      type: keyword
    client.user.group.domain:
      dashed_name: client-user-group-domain
      description: 'Name of the directory the group is a member of.

        For example, an LDAP or Active Directory domain name.'
      flat_name: client.user.group.domain
      ignore_above: 1024
      level: extended
      name: domain
      normalize: []
      original_fieldset: group
      short: Name of the directory the group is a member of.
      type: keyword
    client.user.group.id:
      dashed_name: client-user-group-id
      description: Unique identifier for the group on the system/platform.
      flat_name: client.user.group.id
      ignore_above: 1024
      level: extended
      name: id
      normalize: []
      original_fieldset: group
      short: Unique identifier for the group on the system/platform.
      type: keyword
    client.user.group.name:
      dashed_name: client-user-group-name
      description: Name of the group.
      flat_name: client.user.group.name
      ignore_above: 1024
      level: extended
      name: name
      normalize: []
      original_fieldset: group
      short: Name of the group.
      type: keyword
    client.user.hash:
      dashed_name: client-user-hash
      description: 'Unique user hash to correlate information for a user in anonymized
        form.

        Useful if `user.id` or `user.name` contain confidential information and cannot
        be used.'
      flat_name: client.user.hash
      ignore_above: 1024
      level: extended
      name: hash
      normalize: []
      original_fieldset: user
      short: Unique user hash to correlate information for a user in anonymized form.
      type: keyword
    client.user.id:
      dashed_name: client-user-id
      description: Unique identifier of the user.
      flat_name: client.user.id
      ignore_above: 1024
      level: core
      name: id
      normalize: []
      original_fieldset: user
      short: Unique identifier of the user.
      type: keyword
    client.user.name:
      dashed_name: client-user-name
      description: Short name or login of the user.
      example: albert
      flat_name: client.user.name
      ignore_above: 1024
      level: core
      multi_fields:
      - flat_name: client.user.name.text
        name: text
        norms: false
        type: text
      name: name
      normalize: []
      original_fieldset: user
      short: Short name or login of the user.
      type: keyword
    client.user.roles:
      dashed_name: client-user-roles
      description: Array of user roles at the time of the event.
      example: '["kibana_admin", "reporting_user"]'
      flat_name: client.user.roles
      ignore_above: 1024
      level: extended
      name: roles
      normalize:
      - array
      original_fieldset: user
      short: Array of user roles at the time of the event.
      type: keyword
  group: 2
  name: client
  nestings:
  - client.as
  - client.geo
  - client.user
  prefix: client.
  reused_here:
  - full: client.as
    schema_name: as
    short: Fields describing an Autonomous System (Internet routing prefix).
  - full: client.geo
    schema_name: geo
    short: Fields describing a location.
  - full: client.user
    schema_name: user
    short: Fields to describe the user relevant to the event.
  short: Fields about the client side of a network connection, used with server.
  title: Client
  type: group
container:
  description: 'Container fields are used for meta information about the specific
    container that is the source of information.

    These fields help correlate data based containers from any runtime.'
  fields:
    container.id:
      dashed_name: container-id
      description: Unique container id.
      flat_name: container.id
      ignore_above: 1024
      level: core
      name: id
      normalize: []
      short: Unique container id.
      type: keyword
    container.image.name:
      dashed_name: container-image-name
      description: Name of the image the container was built on.
      flat_name: container.image.name
      ignore_above: 1024
      level: extended
      name: image.name
      normalize: []
      short: Name of the image the container was built on.
      type: keyword
    container.image.tag:
      dashed_name: container-image-tag
      description: Container image tags.
      flat_name: container.image.tag
      ignore_above: 1024
      level: extended
      name: image.tag
      normalize:
      - array
      short: Container image tags.
      type: keyword
    container.labels:
      dashed_name: container-labels
      description: Image labels.
      flat_name: container.labels
      level: extended
      name: labels
      normalize: []
      object_type: keyword
      short: Image labels.
      type: object
    container.name:
      dashed_name: container-name
      description: Container name.
      flat_name: container.name
      ignore_above: 1024
      level: extended
      name: name
      normalize: []
      short: Container name.
      type: keyword
    container.runtime:
      dashed_name: container-runtime
      description: Runtime managing this container.
      example: docker
      flat_name: container.runtime
      ignore_above: 1024
      level: extended
      name: runtime
      normalize: []
      short: Runtime managing this container.
      type: keyword
  group: 2
  name: container
  prefix: container.
  short: Fields describing the container that generated this event.
  title: Container
  type: group
destination:
  description: 'Destination fields capture details about the receiver of a network
    exchange/packet. These fields are populated from a network event, packet, or other
    event containing details of a network transaction.

    Destination fields are usually populated in conjunction with source fields. The
    source and destination fields are considered the baseline and should always be
    filled if an event contains source and destination details from a network transaction.
    If the event also contains identification of the client and server roles, then
    the client and server fields should also be populated.'
  fields:
    destination.address:
      dashed_name: destination-address
      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.

        Then it should be duplicated to `.ip` or `.domain`, depending on which one
        it is.'
      flat_name: destination.address
      ignore_above: 1024
      level: extended
      name: address
      normalize: []
      short: Destination network address.
      type: keyword
    destination.as.number:
      dashed_name: destination-as-number
      description: Unique number allocated to the autonomous system. The autonomous
        system number (ASN) uniquely identifies each network on the Internet.
      example: 15169
      flat_name: destination.as.number
      level: extended
      name: number
      normalize: []
      original_fieldset: as
      short: Unique number allocated to the autonomous system.
      type: long
    destination.as.organization.name:
      dashed_name: destination-as-organization-name
      description: Organization name.
      example: Google LLC
      flat_name: destination.as.organization.name
      ignore_above: 1024
      level: extended
      multi_fields:
      - flat_name: destination.as.organization.name.text
        name: text
        norms: false
        type: text
      name: organization.name
      normalize: []
      original_fieldset: as
      short: Organization name.
      type: keyword
    destination.bytes:
      dashed_name: destination-bytes
      description: Bytes sent from the destination to the source.
      example: 184
      flat_name: destination.bytes
      format: bytes
      level: core
      name: bytes
      normalize: []
      short: Bytes sent from the destination to the source.
      type: long
    destination.domain:
      dashed_name: destination-domain
      description: Destination domain.
      flat_name: destination.domain
      ignore_above: 1024
      level: core
      name: domain
      normalize: []
      short: Destination domain.
      type: keyword
    destination.geo.city_name:
      dashed_name: destination-geo-city-name
      description: City name.
      example: Montreal
      flat_name: destination.geo.city_name
      ignore_above: 1024
      level: core
      name: city_name
      normalize: []
      original_fieldset: geo
      short: City name.
      type: keyword
    destination.geo.continent_code:
      dashed_name: destination-geo-continent-code
      description: Two-letter code representing continent's name.
      example: NA
      flat_name: destination.geo.continent_code
      ignore_above: 1024
      level: core
      name: continent_code
      normalize: []
      original_fieldset: geo
      short: Continent code.
      type: keyword
    destination.geo.continent_name:
      dashed_name: destination-geo-continent-name
      description: Name of the continent.
      example: North America
      flat_name: destination.geo.continent_name
      ignore_above: 1024
      level: core
      name: continent_name
      normalize: []
      original_fieldset: geo
      short: Name of the continent.
      type: keyword
    destination.geo.country_iso_code:
      dashed_name: destination-geo-country-iso-code
      description: Country ISO code.
      example: CA
      flat_name: destination.geo.country_iso_code
      ignore_above: 1024
      level: core
      name: country_iso_code
      normalize: []
      original_fieldset: geo
      short: Country ISO code.
      type: keyword
    destination.geo.country_name:
      dashed_name: destination-geo-country-name
      description: Country name.
      example: Canada
      flat_name: destination.geo.country_name
      ignore_above: 1024
      level: core
      name: country_name
      normalize: []
      original_fieldset: geo
      short: Country name.
      type: keyword
    destination.geo.location:
      dashed_name: destination-geo-location
      description: Longitude and latitude.
      example: '{ "lon": -73.614830, "lat": 45.505918 }'
      flat_name: destination.geo.location
      level: core
      name: location
      normalize: []
      original_fieldset: geo
      short: Longitude and latitude.
      type: geo_point
    destination.geo.name:
      dashed_name: destination-geo-name
      description: 'User-defined description of a location, at the level of granularity
        they care about.

        Could be the name of their data centers, the floor number, if this describes
        a local physical entity, city names.

        Not typically used in automated geolocation.'
      example: boston-dc
      flat_name: destination.geo.name
      ignore_above: 1024
      level: extended
      name: name
      normalize: []
      original_fieldset: geo
      short: User-defined description of a location.
      type: keyword
    destination.geo.postal_code:
      dashed_name: destination-geo-postal-code
      description: 'Postal code associated with the location.

        Values appropriate for this field may also be known as a postcode or ZIP code
        and will vary widely from country to country.'
      example: 94040
      flat_name: destination.geo.postal_code
      ignore_above: 1024
      level: core
      name: postal_code
      normalize: []
      original_fieldset: geo
      short: Postal code.
      type: keyword
    destination.geo.region_iso_code:
      dashed_name: destination-geo-region-iso-code
      description: Region ISO code.
      example: CA-QC
      flat_name: destination.geo.region_iso_code
      ignore_above: 1024
      level: core
      name: region_iso_code
      normalize: []
      original_fieldset: geo
      short: Region ISO code.
      type: keyword
    destination.geo.region_name:
      dashed_name: destination-geo-region-name
      description: Region name.
      example: Quebec
      flat_name: destination.geo.region_name
      ignore_above: 1024
      level: core
      name: region_name
      normalize: []
      original_fieldset: geo
      short: Region name.
      type: keyword
    destination.geo.timezone:
      dashed_name: destination-geo-timezone
      description: The time zone of the location, such as IANA time zone name.
      example: America/Argentina/Buenos_Aires
      flat_name: destination.geo.timezone
      ignore_above: 1024
      level: core
      name: timezone
      normalize: []
      original_fieldset: geo
      short: Time zone.
      type: keyword
    destination.ip:
      dashed_name: destination-ip
      description: IP address of the destination (IPv4 or IPv6).
      flat_name: destination.ip
      level: core
      name: ip
      normalize: []
      short: IP address of the destination.
      type: ip
    destination.mac:
      dashed_name: destination-mac
      description: 'MAC address of the destination.

        The 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.'
      example: 00-00-5E-00-53-23
      flat_name: destination.mac
      ignore_above: 1024
      level: core
      name: mac
      normalize: []
      short: MAC address of the destination.
      type: keyword
    destination.nat.ip:
      dashed_name: destination-nat-ip
      description: 'Translated ip of destination based NAT sessions (e.g. internet
        to private DMZ)

        Typically used with load balancers, firewalls, or routers.'
      flat_name: destination.nat.ip
      level: extended
      name: nat.ip
      normalize: []
      short: Destination NAT ip
      type: ip
    destination.nat.port:
      dashed_name: destination-nat-port
      description: 'Port the source session is translated to by NAT Device.

        Typically used with load balancers, firewalls, or routers.'
      flat_name: destination.nat.port
      format: string
      level: extended
      name: nat.port
      normalize: []
      short: Destination NAT Port
      type: long
    destination.packets:
      dashed_name: destination-packets
      description: Packets sent from the destination to the source.
      example: 12
      flat_name: destination.packets
      level: core
      name: packets
      normalize: []
      short: Packets sent from the destination to the source.
      type: long
    destination.port:
      dashed_name: destination-port
      description: Port of the destination.
      flat_name: destination.port
      format: string
      level: core
      name: port
      normalize: []
      short: Port of the destination.
      type: long
    destination.registered_domain:
      dashed_name: destination-registered-domain
      description: 'The highest registered destination domain, stripped of the subdomain.

        For example, the registered domain for "foo.example.com" is "example.com".

        This value can be determined precisely with a list like the public suffix
        list (http://publicsuffix.org). Trying to approximate this by simply taking
        the last two labels will not work well for TLDs such as "co.uk".'
      example: example.com
      flat_name: destination.registered_domain
      ignore_above: 1024
      level: extended
      name: registered_domain
      normalize: []
      short: The highest registered destination domain, stripped of the subdomain.
      type: keyword
    destination.subdomain:
      dashed_name: destination-subdomain
      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.

        For example the subdomain portion of "www.east.mydomain.co.uk" is "east".
        If the domain has multiple levels of subdomain, such as "sub2.sub1.example.com",
        the subdomain field should contain "sub2.sub1", with no trailing period.'
      example: east
      flat_name: destination.subdomain
      ignore_above: 1024
      level: extended
      name: subdomain
      normalize: []
      short: The subdomain of the domain.
      type: keyword
    destination.top_level_domain:
      dashed_name: destination-top-level-domain
      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".

        This value can be determined precisely with a list like the public suffix
        list (http://publicsuffix.org). Trying to approximate this by simply taking
        the last label will not work well for effective TLDs such as "co.uk".'
      example: co.uk
      flat_name: destination.top_level_domain
      ignore_above: 1024
      level: extended
      name: top_level_domain
      normalize: []
      short: The effective top level domain (com, org, net, co.uk).
      type: keyword
    destination.user.domain:
      dashed_name: destination-user-domain
      description: 'Name of the directory the user is a member of.

        For example, an LDAP or Active Directory domain name.'
      flat_name: destination.user.domain
      ignore_above: 1024
      level: extended
      name: domain
      normalize: []
      original_fieldset: user
      short: Name of the directory the user is a member of.
      type: keyword
    destination.user.email:
      dashed_name: destination-user-email
      description: User email address.
      flat_name: destination.user.email
      ignore_above: 1024
      level: extended
      name: email
      normalize: []
      original_fieldset: user
      short: User email address.
      type: keyword
    destination.user.extra:
      dashed_name: destination-user-extra
      description: 'Additional information in key/value pairs.

        For additional information provided by the authenticator to events.

        Note: Not searchable or filterable.'
      enabled: false
      example: '{"authenticator": "ldap", "cipher": "argon2"}'
      flat_name: destination.user.extra
      level: custom
      name: extra
      normalize: []
      object_type: keyword
      original_fieldset: user
      short: Custom key/value pairs.
      type: object
    destination.user.full_name:
      dashed_name: destination-user-full-name
      description: User's full name, if available.
      example: Albert Einstein
      flat_name: destination.user.full_name
      ignore_above: 1024
      level: extended
      multi_fields:
      - flat_name: destination.user.full_name.text
        name: text
        norms: false
        type: text
      name: full_name
      normalize: []
      original_fieldset: user
      short: User's full name, if available.
      type: keyword
    destination.user.group.domain:
      dashed_name: destination-user-group-domain
      description: 'Name of the directory the group is a member of.

        For example, an LDAP or Active Directory domain name.'
      flat_name: destination.user.group.domain
      ignore_above: 1024
      level: extended
      name: domain
      normalize: []
      original_fieldset: group
      short: Name of the directory the group is a member of.
      type: keyword
    destination.user.group.id:
      dashed_name: destination-user-group-id
      description: Unique identifier for the group on the system/platform.
      flat_name: destination.user.group.id
      ignore_above: 1024
      level: extended
      name: id
      normalize: []
      original_fieldset: group
      short: Unique identifier for the group on the system/platform.
      type: keyword
    destination.user.group.name:
      dashed_name: destination-user-group-name
      description: Name of the group.
      flat_name: destination.user.group.name
      ignore_above: 1024
      level: extended
      name: name
      normalize: []
      original_fieldset: group
      short: Name of the group.
      type: keyword
    destination.user.hash:
      dashed_name: destination-user-hash
      description: 'Unique user hash to correlate information for a user in anonymized
        form.

        Useful if `user.id` or `user.name` contain confidential information and cannot
        be used.'
      flat_name: destination.user.hash
      ignore_above: 1024
      level: extended
      name: hash
      normalize: []
      original_fieldset: user
      short: Unique user hash to correlate information for a user in anonymized form.
      type: keyword
    destination.user.id:
      dashed_name: destination-user-id
      description: Unique identifier of the user.
      flat_name: destination.user.id
      ignore_above: 1024
      level: core
      name: id
      normalize: []
      original_fieldset: user
      short: Unique identifier of the user.
      type: keyword
    destination.user.name:
      dashed_name: destination-user-name
      description: Short name or login of the user.
      example: albert
      flat_name: destination.user.name
      ignore_above: 1024
      level: core
      multi_fields:
      - flat_name: destination.user.name.text
        name: text
        norms: false
        type: text
      name: name
      normalize: []
      original_fieldset: user
      short: Short name or login of the user.
      type: keyword
    destination.user.roles:
      dashed_name: destination-user-roles
      description: Array of user roles at the time of the event.
      example: '["kibana_admin", "reporting_user"]'
      flat_name: destination.user.roles
      ignore_above: 1024
      level: extended
      name: roles
      normalize:
      - array
      original_fieldset: user
      short: Array of user roles at the time of the event.
      type: keyword
  group: 2
  name: destination
  nestings:
  - destination.as
  - destination.geo
  - destination.user
  prefix: destination.
  reused_here:
  - full: destination.as
    schema_name: as
    short: Fields describing an Autonomous System (Internet routing prefix).
  - full: destination.geo
    schema_name: geo
    short: Fields describing a location.
  - full: destination.user
    schema_name: user
    short: Fields to describe the user relevant to the event.
  short: Fields about the destination side of a network connection, used with source.
  title: Destination
  type: group
ecs:
  description: Meta-information specific to ECS.
  fields:
    ecs.version:
      dashed_name: ecs-version
      description: 'ECS version this event conforms to. `ecs.version` is a required
        field and must exist in all events.

        Must match `^(?<major>[0-9]+)\.(?<minor>[0-9]+)\.(?<patch>[0-9]+)$`.

        When querying across multiple indices -- which may conform to slightly different
        ECS versions -- this field lets integrations adjust to the schema version
        of the events.'
      example: 1.0.0
      flat_name: ecs.version
      ignore_above: 1024
      level: core
      name: version
      normalize: []
      required: true
      short: ECS version this event conforms to.
      type: keyword
  group: 2
  name: ecs
  prefix: ecs.
  short: Meta-information specific to ECS.
  title: ECS
  type: group
error:
  description: 'These fields can represent errors of any kind.

    Use them for errors that happen while fetching events or in cases where the event
    itself contains an error.'
  fields:
    error.code:
      dashed_name: error-code
      description: Error code describing the error.
      flat_name: error.code
      ignore_above: 1024
      level: core
      name: code
      normalize: []
      short: Error code describing the error.
      type: keyword
    error.id:
      dashed_name: error-id
      description: Unique identifier for the error.
      flat_name: error.id
      ignore_above: 1024
      level: core
      name: id
      normalize: []
      short: Unique identifier for the error.
      type: keyword
    error.message:
      dashed_name: error-message
      description: Error message.
      flat_name: error.message
      level: core
      name: message
      normalize: []
      norms: false
      short: Error message.
      type: text
    error.stack.head:
      dashed_name: error-stack-head
      description: 'The first line of the stack trace useful for aggregation.

        This is an attribute of the `stack` object, unlike `stack_trace`.'
      flat_name: error.stack.head
      ignore_above: 1024
      level: custom
      name: stack.head
      normalize: []
      short: Head of the stack trace.
      type: keyword
    error.stack.previous_trace:
      dashed_name: error-stack-previous-trace
      description: The previous stack trace.
      doc_values: false
      flat_name: error.stack.previous_trace
      index: false
      level: custom
      multi_fields:
      - flat_name: error.stack.previous_trace.text
        name: text
        norms: false
        type: text
      name: stack.previous_trace
      normalize: []
      short: The previous stack trace.
      type: keyword
    error.stack_trace:
      dashed_name: error-stack-trace
      description: The stack trace of this error in plain text.
      doc_values: false
      flat_name: error.stack_trace
      index: false
      level: extended
      multi_fields:
      - flat_name: error.stack_trace.text
        name: text
        norms: false
        type: text
      name: stack_trace
      normalize: []
      short: The stack trace of this error in plain text.
      type: keyword
    error.type:
      dashed_name: error-type
      description: The type of the error, for example the class name of the exception.
      example: java.lang.NullPointerException
      flat_name: error.type
      ignore_above: 1024
      level: extended
      name: type
      normalize: []
      short: The type of the error, for example the class name of the exception.
      type: keyword
  group: 2
  name: error
  prefix: error.
  short: Fields about errors of any kind.
  title: Error
  type: group
event:
  description: 'The event fields are used for context information about the log or
    metric event itself.

    A log is defined as an event containing details of something that happened. Log
    events must include the time at which the thing happened. Examples of log events
    include a process starting on a host, a network packet being sent from a source
    to a destination, or a network connection between a client and a server being
    initiated or closed. A metric is defined as an event containing one or more numerical
    measurements and the time at which the measurement was taken. Examples of metric
    events include memory pressure measured on a host and device temperature. See
    the `event.kind` definition in this section for additional details about metric
    and state events.'
  fields:
    event.action:
      dashed_name: event-action
      description: 'The action captured by the event.

        This describes the information in the event. It is more specific than `event.category`.
        Examples are `group-add`, `process-started`, `file-created`. The value is
        normally defined by the implementer.'
      example: user-password-change
      flat_name: event.action
      ignore_above: 1024
      level: core
      name: action
      normalize: []
      short: The action captured by the event.
      type: keyword
    event.agent_id_status:
      dashed_name: event-agent-id-status
      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.

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

        If no validation is performed then the field should be omitted.

        The allowed values are:

        `verified` - The `agent.id` field value matches expected value obtained from
        auth metadata.

        `mismatch` - The `agent.id` field value does not match the expected value
        obtained from auth metadata.

        `missing` - There was no `agent.id` field in the event to validate.

        `auth_metadata_missing` - There was no auth metadata or it was missing information
        about the agent ID.'
      example: verified
      flat_name: event.agent_id_status
      ignore_above: 1024
      level: extended
      name: agent_id_status
      normalize: []
      short: Validation status of the event's agent.id field.
      type: keyword
    event.category:
      allowed_values:
      - description: Events in this category are related to the challenge and response
          process in which credentials are supplied and verified to allow the creation
          of a session. Common sources for these logs are Windows event logs and ssh
          logs. Visualize and analyze events in this category to look for failed logins,
          and other authentication-related activity.
        expected_event_types:
        - start
        - end
        - info
        name: authentication
      - description: 'Events in the configuration category have to deal with creating,
          modifying, or deleting the settings or parameters of an application, process,
          or system.

          Example sources include security policy change logs, configuration auditing
          logging, and system integrity monitoring.'
        expected_event_types:
        - access
        - change
        - creation
        - deletion
        - info
        name: configuration
      - description: The database category denotes events and metrics relating to
          a data storage and retrieval system. Note that use of this category is not
          limited to relational database systems. Examples include event logs from
          MS SQL, MySQL, Elasticsearch, MongoDB, etc. Use this category to visualize
          and analyze database activity such as accesses and changes.
        expected_event_types:
        - access
        - change
        - info
        - error
        name: database
      - description: 'Events in the driver category have to do with operating system
          device drivers and similar software entities such as Windows drivers, kernel
          extensions, kernel modules, etc.

          Use events and metrics in this category to visualize and analyze driver-related
          activity and status on hosts.'
        expected_event_types:
        - change
        - end
        - info
        - start
        name: driver
      - description: Relating to a set of information that has been created on, or
          has existed on a filesystem. Use this category of events to visualize and
          analyze the creation, access, and deletions of files. Events in this category
          can come from both host-based and network-based sources. An example source
          of a network-based detection of a file transfer would be the Zeek file.log.
        expected_event_types:
        - change
        - creation
        - deletion
        - info
        name: file
      - description: 'Use this category to visualize and analyze information such
          as host inventory or host lifecycle events.

          Most of the events in this category can usually be observed from the outside,
          such as from a hypervisor or a control plane''s point of view. Some can
          also be seen from within, such as "start" or "end".

          Note that this category is for information about hosts themselves; it is
          not meant to capture activity "happening on a host".'
        expected_event_types:
        - access
        - change
        - end
        - info
        - start
        name: host
      - description: Identity and access management (IAM) events relating to users,
          groups, and administration. Use this category to visualize and analyze IAM-related
          logs and data from active directory, LDAP, Okta, Duo, and other IAM systems.
        expected_event_types:
        - admin
        - change
        - creation
        - deletion
        - group
        - info
        - user
        name: iam
      - description: Relating to intrusion detections from IDS/IPS systems and functions,
          both network and host-based. Use this category to visualize and analyze
          intrusion detection alerts from systems such as Snort, Suricata, and Palo
          Alto threat detections.
        expected_event_types:
        - allowed
        - denied
        - info
        name: intrusion_detection
      - description: Malware detection events and alerts. Use this category to visualize
          and analyze malware detections from EDR/EPP systems such as Elastic Endpoint
          Security, Symantec Endpoint Protection, Crowdstrike, and network IDS/IPS
          systems such as Suricata, or other sources of malware-related events such
          as Palo Alto Networks threat logs and Wildfire logs.
        expected_event_types:
        - info
        name: malware
      - description: Relating to all network activity, including network connection
          lifecycle, network traffic, and essentially any event that includes an IP
          address. Many events containing decoded network protocol transactions fit
          into this category. Use events in this category to visualize or analyze
          counts of network ports, protocols, addresses, geolocation information,
          etc.
        expected_event_types:
        - access
        - allowed
        - connection
        - denied
        - end
        - info
        - protocol
        - start
        name: network
      - description: Relating to software packages installed on hosts. Use this category
          to visualize and analyze inventory of software installed on various hosts,
          or to determine host vulnerability in the absence of vulnerability scan
          data.
        expected_event_types:
        - access
        - change
        - deletion
        - info
        - installation
        - start
        name: package
      - description: Use this category of events to visualize and analyze process-specific
          information such as lifecycle events or process ancestry.
        expected_event_types:
        - access
        - change
        - end
        - info
        - start
        name: process
      - description: Having to do with settings and assets stored in the Windows registry.
          Use this category to visualize and analyze activity such as registry access
          and modifications.
        expected_event_types:
        - access
        - change
        - creation
        - deletion
        name: registry
      - description: The session category is applied to events and metrics regarding
          logical persistent connections to hosts and services. Use this category
          to visualize and analyze interactive or automated persistent connections
          between assets. Data for this category may come from Windows Event logs,
          SSH logs, or stateless sessions such as HTTP cookie-based sessions, etc.
        expected_event_types:
        - start
        - end
        - info
        name: session
      - description: Use this category to visualize and analyze events describing
          threat actors' targets, motives, or behaviors.
        expected_event_types:
        - indicator
        name: threat
      - description: 'Relating to web server access. Use this category to create a
          dashboard of web server/proxy activity from apache, IIS, nginx web servers,
          etc. Note: events from network observers such as Zeek http log may also
          be included in this category.'
        expected_event_types:
        - access
        - error
        - info
        name: web
      dashed_name: event-category
      description: 'This is one of four ECS Categorization Fields, and indicates the
        second level in the ECS category hierarchy.

        `event.category` represents the "big buckets" of ECS categories. For example,
        filtering on `event.category:process` yields all events relating to process
        activity. This field is closely related to `event.type`, which is used as
        a subcategory.

        This field is an array. This will allow proper categorization of some events
        that fall in multiple categories.'
      example: authentication
      flat_name: event.category
      ignore_above: 1024
      level: core
      name: category
      normalize:
      - array
      short: Event category. The second categorization field in the hierarchy.
      type: keyword
    event.code:
      dashed_name: event-code
      description: 'Identification code for this event, if one exists.

        Some event sources use event codes to identify messages unambiguously, regardless
        of message language or wording adjustments over time. An example of this is
        the Windows Event ID.'
      example: 4648
      flat_name: event.code
      ignore_above: 1024
      level: extended
      name: code
      normalize: []
      short: Identification code for this event.
      type: keyword
    event.created:
      dashed_name: event-created
      description: 'event.created contains the date/time when the event was first
        read by an agent, or by your pipeline.

        This field is distinct from @timestamp in that @timestamp typically contain
        the time extracted from the original event.

        In most situations, these two timestamps will be slightly different. The difference
        can be used to calculate the delay between your source generating an event,
        and the time when your agent first processed it. This can be used to monitor
        your agent''s or pipeline''s ability to keep up with your event source.

        In case the two timestamps are identical, @timestamp should be used.'
      example: '2016-05-23T08:05:34.857Z'
      flat_name: event.created
      level: core
      name: created
      normalize: []
      short: Time when the event was first read by an agent or by your pipeline.
      type: date
    event.dataset:
      dashed_name: event-dataset
      description: 'Name of the dataset.

        If an event source publishes more than one type of log or events (e.g. access
        log, error log), the dataset is used to specify which one the event comes
        from.

        It''s recommended but not required to start the dataset name with the module
        name, followed by a dot, then the dataset name.'
      example: apache.access
      flat_name: event.dataset
      ignore_above: 1024
      level: core
      name: dataset
      normalize: []
      short: Name of the dataset.
      type: keyword
    event.duration:
      dashed_name: event-duration
      description: 'Duration of the event in nanoseconds.

        If event.start and event.end are known this value should be the difference
        between the end and start time.'
      flat_name: event.duration
      format: duration
      input_format: nanoseconds
      level: core
      name: duration
      normalize: []
      output_format: asMilliseconds
      output_precision: 1
      short: Duration of the event in nanoseconds.
      type: long
    event.end:
      dashed_name: event-end
      description: event.end contains the date when the event ended or when the activity
        was last observed.
      flat_name: event.end
      level: extended
      name: end
      normalize: []
      short: event.end contains the date when the event ended or when the activity
        was last observed.
      type: date
    event.hash:
      dashed_name: event-hash
      description: Hash (perhaps logstash fingerprint) of raw field to be able to
        demonstrate log integrity.
      example: 123456789012345678901234567890ABCD
      flat_name: event.hash
      ignore_above: 1024
      level: extended
      name: hash
      normalize: []
      short: Hash (perhaps logstash fingerprint) of raw field to be able to demonstrate
        log integrity.
      type: keyword
    event.id:
      dashed_name: event-id
      description: Unique ID to describe the event.
      example: 8a4f500d
      flat_name: event.id
      ignore_above: 1024
      level: core
      name: id
      normalize: []
      short: Unique ID to describe the event.
      type: keyword
    event.ingested:
      dashed_name: event-ingested
      description: 'Timestamp when an event arrived in the central data store.

        This is different from `@timestamp`, which is when the event originally occurred.  It''s
        also different from `event.created`, which is meant to capture the first time
        an agent saw the event.

        In normal conditions, assuming no tampering, the timestamps should chronologically
        look like this: `@timestamp` < `event.created` < `event.ingested`.'
      example: '2016-05-23T08:05:35.101Z'
      flat_name: event.ingested
      level: core
      name: ingested
      normalize: []
      short: Timestamp when an event arrived in the central data store.
      type: date
    event.kind:
      allowed_values:
      - description: 'This value indicates an event such as an alert or notable event,
          triggered by a detection rule executing externally to the Elastic Stack.

          `event.kind:alert` is often populated for events coming from firewalls,
          intrusion detection systems, endpoint detection and response systems, and
          so on.

          This value is not used by Elastic solutions for alert documents that are
          created by rules executing within the Kibana alerting framework.'
        name: alert
      - description: 'The `enrichment` value indicates an event collected to provide
          additional context, often to other events.

          An example is collecting indicators of compromise (IOCs) from a threat intelligence
          provider with the intent to use those values to enrich other events. The
          IOC events from the intelligence provider should be categorized as `event.kind:enrichment`.'
        name: enrichment
      - description: This value is the most general and most common value for this
          field. It is used to represent events that indicate that something happened.
        name: event
      - description: 'This value is used to indicate that this event describes a numeric
          measurement taken at given point in time.

          Examples include CPU utilization, memory usage, or device temperature.

          Metric events are often collected on a predictable frequency, such as once
          every few seconds, or once a minute, but can also be used to describe ad-hoc
          numeric metric queries.'
        name: metric
      - description: 'The state value is similar to metric, indicating that this event
          describes a measurement taken at given point in time, except that the measurement
          does not result in a numeric value, but rather one of a fixed set of categorical
          values that represent conditions or states.

          Examples include periodic events reporting Elasticsearch cluster state (green/yellow/red),
          the state of a TCP connection (open, closed, fin_wait, etc.), the state
          of a host with respect to a software vulnerability (vulnerable, not vulnerable),
          and the state of a system regarding compliance with a regulatory standard
          (compliant, not compliant).

          Note that an event that describes a change of state would not use `event.kind:state`,
          but instead would use ''event.kind:event'' since a state change fits the
          more general event definition of something that happened.

          State events are often collected on a predictable frequency, such as once
          every few seconds, once a minute, once an hour, or once a day, but can also
          be used to describe ad-hoc state queries.'
        name: state
      - description: This value indicates that an error occurred during the ingestion
          of this event, and that event data may be missing, inconsistent, or incorrect.
          `event.kind:pipeline_error` is often associated with parsing errors.
        name: pipeline_error
      - description: 'This value is used by Elastic solutions (e.g., Security, Observability)
          for alert documents that are created by rules executing within the Kibana
          alerting framework.

          Usage of this value is reserved, and data ingestion pipelines must not populate
          `event.kind` with the value "signal".'
        name: signal
      dashed_name: event-kind
      description: 'This is one of four ECS Categorization Fields, and indicates the
        highest level in the ECS category hierarchy.

        `event.kind` gives high-level information about what type of information the
        event contains, without being specific to the contents of the event. For example,
        values of this field distinguish alert events from metric events.

        The value of this field can be used to inform how these kinds of events should
        be handled. They may warrant different retention, different access control,
        it may also help understand whether the data coming in at a regular interval
        or not.'
      example: alert
      flat_name: event.kind
      ignore_above: 1024
      level: core
      name: kind
      normalize: []
      short: The kind of the event. The highest categorization field in the hierarchy.
      type: keyword
    event.module:
      dashed_name: event-module
      description: 'Name of the module this data is coming from.

        If your monitoring agent supports the concept of modules or plugins to process
        events of a given source (e.g. Apache logs), `event.module` should contain
        the name of this module.'
      example: apache
      flat_name: event.module
      ignore_above: 1024
      level: core
      name: module
      normalize: []
      short: Name of the module this data is coming from.
      type: keyword
    event.original:
      dashed_name: event-original
      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.

        This 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`.'
      doc_values: false
      example: Sep 19 08:26:10 host CEF:0&#124;Security&#124; threatmanager&#124;1.0&#124;100&#124;
        worm successfully stopped&#124;10&#124;src=10.0.0.1 dst=2.1.2.2spt=1232
      flat_name: event.original
      index: false
      level: core
      name: original
      normalize: []
      short: Raw text message of entire event.
      type: keyword
    event.outcome:
      allowed_values:
      - description: Indicates that this event describes a failed result. A common
          example is `event.category:file AND event.type:access AND event.outcome:failure`
          to indicate that a file access was attempted, but was not successful.
        name: failure
      - description: Indicates that this event describes a successful result. A common
          example is `event.category:file AND event.type:create AND event.outcome:success`
          to indicate that a file was successfully created.
        name: success
      - description: Indicates that this event describes only an attempt for which
          the result is unknown from the perspective of the event producer. For example,
          if the event contains information only about the request side of a transaction
          that results in a response, populating `event.outcome:unknown` in the request
          event is appropriate. The unknown value should not be used when an outcome
          doesn't make logical sense for the event. In such cases `event.outcome`
          should not be populated.
        name: unknown
      dashed_name: event-outcome
      description: 'This is one of four ECS Categorization Fields, and indicates the
        lowest level in the ECS category hierarchy.

        `event.outcome` simply denotes whether the event represents a success or a
        failure from the perspective of the entity that produced the event.

        Note that when a single transaction is described in multiple events, each
        event may populate different values of `event.outcome`, according to their
        perspective.

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

        Further 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.'
      example: success
      flat_name: event.outcome
      ignore_above: 1024
      level: core
      name: outcome
      normalize: []
      short: The outcome of the event. The lowest level categorization field in the
        hierarchy.
      type: keyword
    event.provider:
      dashed_name: event-provider
      description: 'Source of the event.

        Event transports such as Syslog or the Windows Event Log typically mention
        the source of an event. It can be the name of the software that generated
        the event (e.g. Sysmon, httpd), or of a subsystem of the operating system
        (kernel, Microsoft-Windows-Security-Auditing).'
      example: kernel
      flat_name: event.provider
      ignore_above: 1024
      level: extended
      name: provider
      normalize: []
      short: Source of the event.
      type: keyword
    event.reason:
      dashed_name: event-reason
      description: 'Reason why this event happened, according to the source.

        This 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`).'
      example: Terminated an unexpected process
      flat_name: event.reason
      ignore_above: 1024
      level: extended
      name: reason
      normalize: []
      short: Reason why this event happened, according to the source
      type: keyword
    event.reference:
      dashed_name: event-reference
      description: 'Reference URL linking to additional information about this event.

        This URL links to a static definition of this event. Alert events, indicated
        by `event.kind:alert`, are a common use case for this field.'
      example: https://system.example.com/event/#0001234
      flat_name: event.reference
      ignore_above: 1024
      level: extended
      name: reference
      normalize: []
      short: Event reference URL
      type: keyword
    event.risk_score:
      dashed_name: event-risk-score
      description: Risk score or priority of the event (e.g. security solutions).
        Use your system's original value here.
      flat_name: event.risk_score
      level: core
      name: risk_score
      normalize: []
      short: Risk score or priority of the event (e.g. security solutions). Use your
        system's original value here.
      type: float
    event.risk_score_norm:
      dashed_name: event-risk-score-norm
      description: 'Normalized risk score or priority of the event, on a scale of
        0 to 100.

        This is mainly useful if you use more than one system that assigns risk scores,
        and you want to see a normalized value across all systems.'
      flat_name: event.risk_score_norm
      level: extended
      name: risk_score_norm
      normalize: []
      short: Normalized risk score or priority of the event (0-100).
      type: float
    event.sequence:
      dashed_name: event-sequence
      description: 'Sequence number of the event.

        The sequence number is a value published by some event sources, to make the
        exact ordering of events unambiguous, regardless of the timestamp precision.'
      flat_name: event.sequence
      format: string
      level: extended
      name: sequence
      normalize: []
      short: Sequence number of the event.
      type: long
    event.severity:
      dashed_name: event-severity
      description: 'The numeric severity of the event according to your event source.

        What the different severity values mean can be different between sources and
        use cases. It''s up to the implementer to make sure severities are consistent
        across events from the same source.

        The Syslog severity belongs in `log.syslog.severity.code`. `event.severity`
        is meant to represent the severity according to the event source (e.g. firewall,
        IDS). If the event source does not publish its own severity, you may optionally
        copy the `log.syslog.severity.code` to `event.severity`.'
      example: 7
      flat_name: event.severity
      format: string
      level: core
      name: severity
      normalize: []
      short: Numeric severity of the event.
      type: long
    event.start:
      dashed_name: event-start
      description: event.start contains the date when the event started or when the
        activity was first observed.
      flat_name: event.start
      level: extended
      name: start
      normalize: []
      short: event.start contains the date when the event started or when the activity
        was first observed.
      type: date
    event.timezone:
      dashed_name: event-timezone
      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.

        Acceptable timezone formats are: a canonical ID (e.g. "Europe/Amsterdam"),
        abbreviated (e.g. "EST") or an HH:mm differential (e.g. "-05:00").'
      flat_name: event.timezone
      ignore_above: 1024
      level: extended
      name: timezone
      normalize: []
      short: Event time zone.
      type: keyword
    event.type:
      allowed_values:
      - description: The access event type is used for the subset of events within
          a category that indicate that something was accessed. Common examples include
          `event.category:database AND event.type:access`, or `event.category:file
          AND event.type:access`. Note for file access, both directory listings and
          file opens should be included in this subcategory. You can further distinguish
          access operations using the ECS `event.action` field.
        name: access
      - description: 'The admin event type is used for the subset of events within
          a category that are related to admin objects. For example, administrative
          changes within an IAM framework that do not specifically affect a user or
          group (e.g., adding new applications to a federation solution or connecting
          discrete forests in Active Directory) would fall into this subcategory.
          Common example: `event.category:iam AND event.type:change AND event.type:admin`.
          You can further distinguish admin operations using the ECS `event.action`
          field.'
        name: admin
      - description: The allowed event type is used for the subset of events within
          a category that indicate that something was allowed. Common examples include
          `event.category:network AND event.type:connection AND event.type:allowed`
          (to indicate a network firewall event for which the firewall disposition
          was to allow the connection to complete) and `event.category:intrusion_detection
          AND event.type:allowed` (to indicate a network intrusion prevention system
          event for which the IPS disposition was to allow the connection to complete).
          You can further distinguish allowed operations using the ECS `event.action`
          field, populating with values of your choosing, such as "allow", "detect",
          or "pass".
        name: allowed
      - description: The change event type is used for the subset of events within
          a category that indicate that something has changed. If semantics best describe
          an event as modified, then include them in this subcategory. Common examples
          include `event.category:process AND event.type:change`, and `event.category:file
          AND event.type:change`. You can further distinguish change operations using
          the ECS `event.action` field.
        name: change
      - description: Used primarily with `event.category:network` this value is used
          for the subset of network traffic that includes sufficient information for
          the event to be included in flow or connection analysis. Events in this
          subcategory will contain at least source and destination IP addresses, source
          and destination TCP/UDP ports, and will usually contain counts of bytes
          and/or packets transferred. Events in this subcategory may contain unidirectional
          or bidirectional information, including summary information. Use this subcategory
          to visualize and analyze network connections. Flow analysis, including Netflow,
          IPFIX, and other flow-related events fit in this subcategory. Note that
          firewall events from many Next-Generation Firewall (NGFW) devices will also
          fit into this subcategory.  A common filter for flow/connection information
          would be `event.category:network AND event.type:connection AND event.type:end`
          (to view or analyze all completed network connections, ignoring mid-flow
          reports). You can further distinguish connection events using the ECS `event.action`
          field, populating with values of your choosing, such as "timeout", or "reset".
        name: connection
      - description: The "creation" event type is used for the subset of events within
          a category that indicate that something was created. A common example is
          `event.category:file AND event.type:creation`.
        name: creation
      - description: The deletion event type is used for the subset of events within
          a category that indicate that something was deleted. A common example is
          `event.category:file AND event.type:deletion` to indicate that a file has
          been deleted.
        name: deletion
      - description: The denied event type is used for the subset of events within
          a category that indicate that something was denied. Common examples include
          `event.category:network AND event.type:denied` (to indicate a network firewall
          event for which the firewall disposition was to deny the connection) and
          `event.category:intrusion_detection AND event.type:denied` (to indicate
          a network intrusion prevention system event for which the IPS disposition
          was to deny the connection to complete). You can further distinguish denied
          operations using the ECS `event.action` field, populating with values of
          your choosing, such as "blocked", "dropped", or "quarantined".
        name: denied
      - description: The end event type is used for the subset of events within a
          category that indicate something has ended. A common example is `event.category:process
          AND event.type:end`.
        name: end
      - description: The error event type is used for the subset of events within
          a category that indicate or describe an error. A common example is `event.category:database
          AND event.type:error`. Note that pipeline errors that occur during the event
          ingestion process should not use this `event.type` value. Instead, they
          should use `event.kind:pipeline_error`.
        name: error
      - description: 'The group event type is used for the subset of events within
          a category that are related to group objects. Common example: `event.category:iam
          AND event.type:creation AND event.type:group`. You can further distinguish
          group operations using the ECS `event.action` field.'
        name: group
      - description: 'The indicator event type is used for the subset of events within
          a category that contain details about indicators of compromise (IOCs).

          A common example is `event.category:threat AND event.type:indicator`.'
        name: indicator
      - description: The info event type is used for the subset of events within a
          category that indicate that they are purely informational, and don't report
          a state change, or any type of action. For example, an initial run of a
          file integrity monitoring system (FIM), where an agent reports all files
          under management, would fall into the "info" subcategory. Similarly, an
          event containing a dump of all currently running processes (as opposed to
          reporting that a process started/ended) would fall into the "info" subcategory.
          An additional common examples is `event.category:intrusion_detection AND
          event.type:info`.
        name: info
      - description: The installation event type is used for the subset of events
          within a category that indicate that something was installed. A common example
          is `event.category:package` AND `event.type:installation`.
        name: installation
      - description: The protocol event type is used for the subset of events within
          a category that indicate that they contain protocol details or analysis,
          beyond simply identifying the protocol. Generally, network events that contain
          specific protocol details will fall into this subcategory. A common example
          is `event.category:network AND event.type:protocol AND event.type:connection
          AND event.type:end` (to indicate that the event is a network connection
          event sent at the end of a connection that also includes a protocol detail
          breakdown). Note that events that only indicate the name or id of the protocol
          should not use the protocol value. Further note that when the protocol subcategory
          is used, the identified protocol is populated in the ECS `network.protocol`
          field.
        name: protocol
      - description: The start event type is used for the subset of events within
          a category that indicate something has started. A common example is `event.category:process
          AND event.type:start`.
        name: start
      - description: 'The user event type is used for the subset of events within
          a category that are related to user objects. Common example: `event.category:iam
          AND event.type:deletion AND event.type:user`. You can further distinguish
          user operations using the ECS `event.action` field.'
        name: user
      dashed_name: event-type
      description: 'This is one of four ECS Categorization Fields, and indicates the
        third level in the ECS category hierarchy.

        `event.type` represents a categorization "sub-bucket" that, when used along
        with the `event.category` field values, enables filtering events down to a
        level appropriate for single visualization.

        This field is an array. This will allow proper categorization of some events
        that fall in multiple event types.'
      flat_name: event.type
      ignore_above: 1024
      level: core
      name: type
      normalize:
      - array
      short: Event type. The third categorization field in the hierarchy.
      type: keyword
    event.url:
      dashed_name: event-url
      description: 'URL linking to an external system to continue investigation of
        this event.

        This 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.'
      example: https://mysystem.example.com/alert/5271dedb-f5b0-4218-87f0-4ac4870a38fe
      flat_name: event.url
      ignore_above: 1024
      level: extended
      name: url
      normalize: []
      short: Event investigation URL
      type: keyword
  group: 2
  name: event
  prefix: event.
  short: Fields breaking down the event details.
  title: Event
  type: group
geo:
  description: 'Geo fields can carry data about a specific location related to an
    event.

    This geolocation information can be derived from techniques such as Geo IP, or
    be user-supplied.'
  fields:
    geo.city_name:
      dashed_name: geo-city-name
      description: City name.
      example: Montreal
      flat_name: geo.city_name
      ignore_above: 1024
      level: core
      name: city_name
      normalize: []
      short: City name.
      type: keyword
    geo.continent_code:
      dashed_name: geo-continent-code
      description: Two-letter code representing continent's name.
      example: NA
      flat_name: geo.continent_code
      ignore_above: 1024
      level: core
      name: continent_code
      normalize: []
      short: Continent code.
      type: keyword
    geo.continent_name:
      dashed_name: geo-continent-name
      description: Name of the continent.
      example: North America
      flat_name: geo.continent_name
      ignore_above: 1024
      level: core
      name: continent_name
      normalize: []
      short: Name of the continent.
      type: keyword
    geo.country_iso_code:
      dashed_name: geo-country-iso-code
      description: Country ISO code.
      example: CA
      flat_name: geo.country_iso_code
      ignore_above: 1024
      level: core
      name: country_iso_code
      normalize: []
      short: Country ISO code.
      type: keyword
    geo.country_name:
      dashed_name: geo-country-name
      description: Country name.
      example: Canada
      flat_name: geo.country_name
      ignore_above: 1024
      level: core
      name: country_name
      normalize: []
      short: Country name.
      type: keyword
    geo.location:
      dashed_name: geo-location
      description: Longitude and latitude.
      example: '{ "lon": -73.614830, "lat": 45.505918 }'
      flat_name: geo.location
      level: core
      name: location
      normalize: []
      short: Longitude and latitude.
      type: geo_point
    geo.name:
      dashed_name: geo-name
      description: 'User-defined description of a location, at the level of granularity
        they care about.

        Could be the name of their data centers, the floor number, if this describes
        a local physical entity, city names.

        Not typically used in automated geolocation.'
      example: boston-dc
      flat_name: geo.name
      ignore_above: 1024
      level: extended
      name: name
      normalize: []
      short: User-defined description of a location.
      type: keyword
    geo.postal_code:
      dashed_name: geo-postal-code
      description: 'Postal code associated with the location.

        Values appropriate for this field may also be known as a postcode or ZIP code
        and will vary widely from country to country.'
      example: 94040
      flat_name: geo.postal_code
      ignore_above: 1024
      level: core
      name: postal_code
      normalize: []
      short: Postal code.
      type: keyword
    geo.region_iso_code:
      dashed_name: geo-region-iso-code
      description: Region ISO code.
      example: CA-QC
      flat_name: geo.region_iso_code
      ignore_above: 1024
      level: core
      name: region_iso_code
      normalize: []
      short: Region ISO code.
      type: keyword
    geo.region_name:
      dashed_name: geo-region-name
      description: Region name.
      example: Quebec
      flat_name: geo.region_name
      ignore_above: 1024
      level: core
      name: region_name
      normalize: []
      short: Region name.
      type: keyword
    geo.timezone:
      dashed_name: geo-timezone
      description: The time zone of the location, such as IANA time zone name.
      example: America/Argentina/Buenos_Aires
      flat_name: geo.timezone
      ignore_above: 1024
      level: core
      name: timezone
      normalize: []
      short: Time zone.
      type: keyword
  group: 2
  name: geo
  prefix: geo.
  reusable:
    expected:
    - as: geo
      at: client
      full: client.geo
    - as: geo
      at: destination
      full: destination.geo
    - as: geo
      at: observer
      full: observer.geo
    - as: geo
      at: host
      full: host.geo
    - as: geo
      at: server
      full: server.geo
    - as: geo
      at: source
      full: source.geo
    - as: geo
      at: threat.indicator
      beta: Reusing the `geo` fields in this location is currently considered beta.
      full: threat.indicator.geo
    - as: geo
      at: threat.enrichments.indicator
      beta: Reusing the `geo` fields in this location is currently considered beta.
      full: threat.enrichments.indicator.geo
    top_level: false
  short: Fields describing a location.
  title: Geo
  type: group
git:
  description: Fields related to git repositories
  fields:
    git.commit.author:
      dashed_name: git-commit-author
      description: The author of the git commit
      flat_name: git.commit.author
      ignore_above: 1024
      level: custom
      name: commit.author
      normalize: []
      short: The author of the git commit
      type: keyword
    git.commit.hash.sha1.full:
      dashed_name: git-commit-hash-sha1-full
      description: The full sha1 hash of a git commit
      flat_name: git.commit.hash.sha1.full
      ignore_above: 1024
      level: custom
      name: commit.hash.sha1.full
      normalize: []
      short: The full sha1 hash of a git commit
      type: keyword
    git.commit.hash.sha1.short:
      dashed_name: git-commit-hash-sha1-short
      description: The short sha1 hash of a git commit
      flat_name: git.commit.hash.sha1.short
      ignore_above: 1024
      level: custom
      name: commit.hash.sha1.short
      normalize: []
      short: The short sha1 hash of a git commit
      type: keyword
    git.repo.name:
      dashed_name: git-repo-name
      description: The name of the git repo
      flat_name: git.repo.name
      ignore_above: 1024
      level: custom
      name: repo.name
      normalize: []
      short: The name of the git repo
      type: keyword
    git.repo.url.domain:
      dashed_name: git-repo-url-domain
      description: Domain of the url
      flat_name: git.repo.url.domain
      ignore_above: 1024
      level: custom
      name: repo.url.domain
      normalize: []
      short: Domain of the url
      type: keyword
    git.repo.url.full:
      dashed_name: git-repo-url-full
      description: Unmodified original url as seen in the event source.
      flat_name: git.repo.url.full
      ignore_above: 1024
      level: custom
      name: repo.url.full
      normalize: []
      short: The full url
      type: keyword
    git.repo.url.original:
      dashed_name: git-repo-url-original
      description: Unmodified original url as seen in the event source.
      flat_name: git.repo.url.original
      ignore_above: 1024
      level: custom
      name: repo.url.original
      normalize: []
      short: Unmodified original url as seen in the event source.
      type: keyword
    git.repo.url.scheme:
      dashed_name: git-repo-url-scheme
      description: Scheme of the request, such as "https" or "ssh"
      flat_name: git.repo.url.scheme
      ignore_above: 1024
      level: custom
      name: repo.url.scheme
      normalize: []
      short: Scheme of the request, such as "https" or "ssh"
      type: keyword
  group: 2
  name: git
  prefix: git.
  short: Fields related to git repositories
  title: Git
  type: group
hash:
  description: 'The hash fields represent different bitwise hash algorithms and their
    values.

    Field names for common hashes (e.g. MD5, SHA1) are predefined. Add fields for
    other hashes by lowercasing the hash algorithm name and using underscore separators
    as appropriate (snake case, e.g. sha3_512).

    Note that this fieldset is used for common hashes that may be computed over a
    range of generic bytes. Entity-specific hashes such as ja3 or imphash are placed
    in the fieldsets to which they relate (tls and pe, respectively).'
  fields:
    hash.md5:
      dashed_name: hash-md5
      description: MD5 hash.
      flat_name: hash.md5
      ignore_above: 1024
      level: extended
      name: md5
      normalize: []
      short: MD5 hash.
      type: keyword
    hash.sha1:
      dashed_name: hash-sha1
      description: SHA1 hash.
      flat_name: hash.sha1
      ignore_above: 1024
      level: extended
      name: sha1
      normalize: []
      short: SHA1 hash.
      type: keyword
    hash.sha256:
      dashed_name: hash-sha256
      description: SHA256 hash.
      flat_name: hash.sha256
      ignore_above: 1024
      level: extended
      name: sha256
      normalize: []
      short: SHA256 hash.
      type: keyword
    hash.sha512:
      dashed_name: hash-sha512
      description: SHA512 hash.
      flat_name: hash.sha512
      ignore_above: 1024
      level: extended
      name: sha512
      normalize: []
      short: SHA512 hash.
      type: keyword
    hash.ssdeep:
      dashed_name: hash-ssdeep
      description: SSDEEP hash.
      flat_name: hash.ssdeep
      ignore_above: 1024
      level: extended
      name: ssdeep
      normalize: []
      short: SSDEEP hash.
      type: keyword
  group: 2
  name: hash
  prefix: hash.
  reusable:
    expected:
    - as: hash
      at: file
      full: file.hash
    - as: hash
      at: process
      full: process.hash
    - as: hash
      at: dll
      full: dll.hash
    - as: hash
      at: threat.indicator
      beta: Reusing the `hash` fields in this location is currently considered beta.
      full: threat.indicator.hash
    - as: hash
      at: threat.enrichments.indicator
      beta: Reusing the `hash` fields in this location is currently considered beta.
      full: threat.enrichments.indicator.hash
    top_level: false
  short: Hashes, usually file hashes.
  title: Hash
  type: group
host:
  description: 'A host is defined as a general computing instance.

    ECS host.* fields should be populated with details about the host on which the
    event happened, or from which the measurement was taken. Host types include hardware,
    virtual machines, Docker containers, and Kubernetes nodes.'
  fields:
    host.architecture:
      dashed_name: host-architecture
      description: Operating system architecture.
      example: x86_64
      flat_name: host.architecture
      ignore_above: 1024
      level: core
      name: architecture
      normalize: []
      short: Operating system architecture.
      type: keyword
    host.cpu.usage:
      dashed_name: host-cpu-usage
      description: 'Percent CPU used which is normalized by the number of CPU cores
        and it ranges from 0 to 1.

        Scaling factor: 1000.

        For example: For a two core host, this value should be the average of the
        two cores, between 0 and 1.'
      flat_name: host.cpu.usage
      level: extended
      name: cpu.usage
      normalize: []
      scaling_factor: 1000
      short: Percent CPU used, between 0 and 1.
      type: scaled_float
    host.disk.read.bytes:
      dashed_name: host-disk-read-bytes
      description: The total number of bytes (gauge) read successfully (aggregated
        from all disks) since the last metric collection.
      flat_name: host.disk.read.bytes
      level: extended
      name: disk.read.bytes
      normalize: []
      short: The number of bytes read by all disks.
      type: long
    host.disk.write.bytes:
      dashed_name: host-disk-write-bytes
      description: The total number of bytes (gauge) written successfully (aggregated
        from all disks) since the last metric collection.
      flat_name: host.disk.write.bytes
      level: extended
      name: disk.write.bytes
      normalize: []
      short: The number of bytes written on all disks.
      type: long
    host.domain:
      dashed_name: host-domain
      description: 'Name of the domain of which the host is a member.

        For example, on Windows this could be the host''s Active Directory domain
        or NetBIOS domain name. For Linux this could be the domain of the host''s
        LDAP provider.'
      example: CONTOSO
      flat_name: host.domain
      ignore_above: 1024
      level: extended
      name: domain
      normalize: []
      short: Name of the directory the group is a member of.
      type: keyword
    host.geo.city_name:
      dashed_name: host-geo-city-name
      description: City name.
      example: Montreal
      flat_name: host.geo.city_name
      ignore_above: 1024
      level: core
      name: city_name
      normalize: []
      original_fieldset: geo
      short: City name.
      type: keyword
    host.geo.continent_code:
      dashed_name: host-geo-continent-code
      description: Two-letter code representing continent's name.
      example: NA
      flat_name: host.geo.continent_code
      ignore_above: 1024
      level: core
      name: continent_code
      normalize: []
      original_fieldset: geo
      short: Continent code.
      type: keyword
    host.geo.continent_name:
      dashed_name: host-geo-continent-name
      description: Name of the continent.
      example: North America
      flat_name: host.geo.continent_name
      ignore_above: 1024
      level: core
      name: continent_name
      normalize: []
      original_fieldset: geo
      short: Name of the continent.
      type: keyword
    host.geo.country_iso_code:
      dashed_name: host-geo-country-iso-code
      description: Country ISO code.
      example: CA
      flat_name: host.geo.country_iso_code
      ignore_above: 1024
      level: core
      name: country_iso_code
      normalize: []
      original_fieldset: geo
      short: Country ISO code.
      type: keyword
    host.geo.country_name:
      dashed_name: host-geo-country-name
      description: Country name.
      example: Canada
      flat_name: host.geo.country_name
      ignore_above: 1024
      level: core
      name: country_name
      normalize: []
      original_fieldset: geo
      short: Country name.
      type: keyword
    host.geo.location:
      dashed_name: host-geo-location
      description: Longitude and latitude.
      example: '{ "lon": -73.614830, "lat": 45.505918 }'
      flat_name: host.geo.location
      level: core
      name: location
      normalize: []
      original_fieldset: geo
      short: Longitude and latitude.
      type: geo_point
    host.geo.name:
      dashed_name: host-geo-name
      description: 'User-defined description of a location, at the level of granularity
        they care about.

        Could be the name of their data centers, the floor number, if this describes
        a local physical entity, city names.

        Not typically used in automated geolocation.'
      example: boston-dc
      flat_name: host.geo.name
      ignore_above: 1024
      level: extended
      name: name
      normalize: []
      original_fieldset: geo
      short: User-defined description of a location.
      type: keyword
    host.geo.postal_code:
      dashed_name: host-geo-postal-code
      description: 'Postal code associated with the location.

        Values appropriate for this field may also be known as a postcode or ZIP code
        and will vary widely from country to country.'
      example: 94040
      flat_name: host.geo.postal_code
      ignore_above: 1024
      level: core
      name: postal_code
      normalize: []
      original_fieldset: geo
      short: Postal code.
      type: keyword
    host.geo.region_iso_code:
      dashed_name: host-geo-region-iso-code
      description: Region ISO code.
      example: CA-QC
      flat_name: host.geo.region_iso_code
      ignore_above: 1024
      level: core
      name: region_iso_code
      normalize: []
      original_fieldset: geo
      short: Region ISO code.
      type: keyword
    host.geo.region_name:
      dashed_name: host-geo-region-name
      description: Region name.
      example: Quebec
      flat_name: host.geo.region_name
      ignore_above: 1024
      level: core
      name: region_name
      normalize: []
      original_fieldset: geo
      short: Region name.
      type: keyword
    host.geo.timezone:
      dashed_name: host-geo-timezone
      description: The time zone of the location, such as IANA time zone name.
      example: America/Argentina/Buenos_Aires
      flat_name: host.geo.timezone
      ignore_above: 1024
      level: core
      name: timezone
      normalize: []
      original_fieldset: geo
      short: Time zone.
      type: keyword
    host.hostname:
      dashed_name: host-hostname
      description: 'Hostname of the host.

        It normally contains what the `hostname` command returns on the host machine.'
      flat_name: host.hostname
      ignore_above: 1024
      level: core
      name: hostname
      normalize: []
      short: Hostname of the host.
      type: keyword
    host.id:
      dashed_name: host-id
      description: 'Unique host id.

        As hostname is not always unique, use values that are meaningful in your environment.

        Example: The current usage of `beat.name`.'
      flat_name: host.id
      ignore_above: 1024
      level: core
      name: id
      normalize: []
      short: Unique host id.
      type: keyword
    host.ip:
      dashed_name: host-ip
      description: Host ip addresses.
      flat_name: host.ip
      level: core
      name: ip
      normalize:
      - array
      short: Host ip addresses.
      type: ip
    host.mac:
      dashed_name: host-mac
      description: 'Host MAC addresses.

        The 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.'
      example: '["00-00-5E-00-53-23", "00-00-5E-00-53-24"]'
      flat_name: host.mac
      ignore_above: 1024
      level: core
      name: mac
      normalize:
      - array
      short: Host MAC addresses.
      type: keyword
    host.name:
      dashed_name: host-name
      description: 'Name of the host.

        It can contain what `hostname` returns on Unix systems, the fully qualified
        domain name, or a name specified by the user. The sender decides which value
        to use.'
      flat_name: host.name
      ignore_above: 1024
      level: core
      name: name
      normalize: []
      short: Name of the host.
      type: keyword
    host.network.egress.bytes:
      dashed_name: host-network-egress-bytes
      description: The number of bytes (gauge) sent out on all network interfaces
        by the host since the last metric collection.
      flat_name: host.network.egress.bytes
      level: extended
      name: network.egress.bytes
      normalize: []
      short: The number of bytes sent on all network interfaces.
      type: long
    host.network.egress.packets:
      dashed_name: host-network-egress-packets
      description: The number of packets (gauge) sent out on all network interfaces
        by the host since the last metric collection.
      flat_name: host.network.egress.packets
      level: extended
      name: network.egress.packets
      normalize: []
      short: The number of packets sent on all network interfaces.
      type: long
    host.network.ingress.bytes:
      dashed_name: host-network-ingress-bytes
      description: The number of bytes received (gauge) on all network interfaces
        by the host since the last metric collection.
      flat_name: host.network.ingress.bytes
      level: extended
      name: network.ingress.bytes
      normalize: []
      short: The number of bytes received on all network interfaces.
      type: long
    host.network.ingress.packets:
      dashed_name: host-network-ingress-packets
      description: The number of packets (gauge) received on all network interfaces
        by the host since the last metric collection.
      flat_name: host.network.ingress.packets
      level: extended
      name: network.ingress.packets
      normalize: []
      short: The number of packets received on all network interfaces.
      type: long
    host.os.family:
      dashed_name: host-os-family
      description: OS family (such as redhat, debian, freebsd, windows).
      example: debian
      flat_name: host.os.family
      ignore_above: 1024
      level: extended
      name: family
      normalize: []
      original_fieldset: os
      short: OS family (such as redhat, debian, freebsd, windows).
      type: keyword
    host.os.full:
      dashed_name: host-os-full
      description: Operating system name, including the version or code name.
      example: Mac OS Mojave
      flat_name: host.os.full
      ignore_above: 1024
      level: extended
      multi_fields:
      - flat_name: host.os.full.text
        name: text
        norms: false
        type: text
      name: full
      normalize: []
      original_fieldset: os
      short: Operating system name, including the version or code name.
      type: keyword
    host.os.kernel:
      dashed_name: host-os-kernel
      description: Operating system kernel version as a raw string.
      example: 4.4.0-112-generic
      flat_name: host.os.kernel
      ignore_above: 1024
      level: extended
      name: kernel
      normalize: []
      original_fieldset: os
      short: Operating system kernel version as a raw string.
      type: keyword
    host.os.name:
      dashed_name: host-os-name
      description: Operating system name, without the version.
      example: Mac OS X
      flat_name: host.os.name
      ignore_above: 1024
      level: extended
      multi_fields:
      - flat_name: host.os.name.text
        name: text
        norms: false
        type: text
      name: name
      normalize: []
      original_fieldset: os
      short: Operating system name, without the version.
      type: keyword
    host.os.platform:
      dashed_name: host-os-platform
      description: Operating system platform (such centos, ubuntu, windows).
      example: darwin
      flat_name: host.os.platform
      ignore_above: 1024
      level: extended
      name: platform
      normalize: []
      original_fieldset: os
      short: Operating system platform (such centos, ubuntu, windows).
      type: keyword
    host.os.type:
      dashed_name: host-os-type
      description: 'Use the `os.type` field to categorize the operating system into
        one of the broad commercial families.

        One of these following values should be used (lowercase): linux, macos, unix,
        windows.

        If the OS you''re dealing with is not in the list, the field should not be
        populated. Please let us know by opening an issue with ECS, to propose its
        addition.'
      example: macos
      flat_name: host.os.type
      ignore_above: 1024
      level: extended
      name: type
      normalize: []
      original_fieldset: os
      short: 'Which commercial OS family (one of: linux, macos, unix or windows).'
      type: keyword
    host.os.version:
      dashed_name: host-os-version
      description: Operating system version as a raw string.
      example: 10.14.1
      flat_name: host.os.version
      ignore_above: 1024
      level: extended
      name: version
      normalize: []
      original_fieldset: os
      short: Operating system version as a raw string.
      type: keyword
    host.type:
      dashed_name: host-type
      description: 'Type of host.

        For Cloud providers this can be the machine type like `t2.medium`. If vm,
        this could be the container, for example, or other information meaningful
        in your environment.'
      flat_name: host.type
      ignore_above: 1024
      level: core
      name: type
      normalize: []
      short: Type of host.
      type: keyword
    host.uptime:
      dashed_name: host-uptime
      description: Seconds the host has been up.
      example: 1325
      flat_name: host.uptime
      level: extended
      name: uptime
      normalize: []
      short: Seconds the host has been up.
      type: long
    host.user.domain:
      dashed_name: host-user-domain
      description: 'Name of the directory the user is a member of.

        For example, an LDAP or Active Directory domain name.'
      flat_name: host.user.domain
      ignore_above: 1024
      level: extended
      name: domain
      normalize: []
      original_fieldset: user
      short: Name of the directory the user is a member of.
      type: keyword
    host.user.email:
      dashed_name: host-user-email
      description: User email address.
      flat_name: host.user.email
      ignore_above: 1024
      level: extended
      name: email
      normalize: []
      original_fieldset: user
      short: User email address.
      type: keyword
    host.user.extra:
      dashed_name: host-user-extra
      description: 'Additional information in key/value pairs.

        For additional information provided by the authenticator to events.

        Note: Not searchable or filterable.'
      enabled: false
      example: '{"authenticator": "ldap", "cipher": "argon2"}'
      flat_name: host.user.extra
      level: custom
      name: extra
      normalize: []
      object_type: keyword
      original_fieldset: user
      short: Custom key/value pairs.
      type: object
    host.user.full_name:
      dashed_name: host-user-full-name
      description: User's full name, if available.
      example: Albert Einstein
      flat_name: host.user.full_name
      ignore_above: 1024
      level: extended
      multi_fields:
      - flat_name: host.user.full_name.text
        name: text
        norms: false
        type: text
      name: full_name
      normalize: []
      original_fieldset: user
      short: User's full name, if available.
      type: keyword
    host.user.group.domain:
      dashed_name: host-user-group-domain
      description: 'Name of the directory the group is a member of.

        For example, an LDAP or Active Directory domain name.'
      flat_name: host.user.group.domain
      ignore_above: 1024
      level: extended
      name: domain
      normalize: []
      original_fieldset: group
      short: Name of the directory the group is a member of.
      type: keyword
    host.user.group.id:
      dashed_name: host-user-group-id
      description: Unique identifier for the group on the system/platform.
      flat_name: host.user.group.id
      ignore_above: 1024
      level: extended
      name: id
      normalize: []
      original_fieldset: group
      short: Unique identifier for the group on the system/platform.
      type: keyword
    host.user.group.name:
      dashed_name: host-user-group-name
      description: Name of the group.
      flat_name: host.user.group.name
      ignore_above: 1024
      level: extended
      name: name
      normalize: []
      original_fieldset: group
      short: Name of the group.
      type: keyword
    host.user.hash:
      dashed_name: host-user-hash
      description: 'Unique user hash to correlate information for a user in anonymized
        form.

        Useful if `user.id` or `user.name` contain confidential information and cannot
        be used.'
      flat_name: host.user.hash
      ignore_above: 1024
      level: extended
      name: hash
      normalize: []
      original_fieldset: user
      short: Unique user hash to correlate information for a user in anonymized form.
      type: keyword
    host.user.id:
      dashed_name: host-user-id
      description: Unique identifier of the user.
      flat_name: host.user.id
      ignore_above: 1024
      level: core
      name: id
      normalize: []
      original_fieldset: user
      short: Unique identifier of the user.
      type: keyword
    host.user.name:
      dashed_name: host-user-name
      description: Short name or login of the user.
      example: albert
      flat_name: host.user.name
      ignore_above: 1024
      level: core
      multi_fields:
      - flat_name: host.user.name.text
        name: text
        norms: false
        type: text
      name: name
      normalize: []
      original_fieldset: user
      short: Short name or login of the user.
      type: keyword
    host.user.roles:
      dashed_name: host-user-roles
      description: Array of user roles at the time of the event.
      example: '["kibana_admin", "reporting_user"]'
      flat_name: host.user.roles
      ignore_above: 1024
      level: extended
      name: roles
      normalize:
      - array
      original_fieldset: user
      short: Array of user roles at the time of the event.
      type: keyword
  group: 2
  name: host
  nestings:
  - host.geo
  - host.os
  - host.user
  prefix: host.
  reused_here:
  - full: host.geo
    schema_name: geo
    short: Fields describing a location.
  - full: host.os
    schema_name: os
    short: OS fields contain information about the operating system.
  - full: host.user
    schema_name: user
    short: This reuse is deprecated and will be removed in the next major ECS version.
  short: Fields describing the relevant computing instance.
  title: Host
  type: group
http:
  description: Fields related to HTTP activity. Use the `url` field set to store the
    url of the request.
  fields:
    http.request.body.bytes:
      dashed_name: http-request-body-bytes
      description: Size in bytes of the request body.
      example: 887
      flat_name: http.request.body.bytes
      format: bytes
      level: extended
      name: request.body.bytes
      normalize: []
      short: Size in bytes of the request body.
      type: long
    http.request.body.content:
      dashed_name: http-request-body-content
      description: The full HTTP request body.
      example: Hello world
      flat_name: http.request.body.content
      ignore_above: 1024
      level: extended
      multi_fields:
      - flat_name: http.request.body.content.text
        name: text
        norms: false
        type: text
      name: request.body.content
      normalize: []
      short: The full HTTP request body.
      type: keyword
    http.request.bytes:
      dashed_name: http-request-bytes
      description: Total size in bytes of the request (body and headers).
      example: 1437
      flat_name: http.request.bytes
      format: bytes
      level: extended
      name: request.bytes
      normalize: []
      short: Total size in bytes of the request (body and headers).
      type: long
    http.request.headers:
      dashed_name: http-request-headers
      description: 'Request headers in key/value pairs.

        Can be used add request header information to events. Should not contain nested
        objects. All values are stored as keyword.'
      example: '{"content-type": "application/json", "cache-status": "Miss"}'
      flat_name: http.request.headers
      level: custom
      name: request.headers
      normalize: []
      object_type: keyword
      short: Custom key/value pairs.
      type: object
    http.request.id:
      dashed_name: http-request-id
      description: 'A unique identifier for each HTTP request to correlate logs between
        clients and servers in transactions.

        The id may be contained in a non-standard HTTP header, such as `X-Request-ID`
        or `X-Correlation-ID`.'
      example: 123e4567-e89b-12d3-a456-426614174000
      flat_name: http.request.id
      ignore_above: 1024
      level: extended
      name: request.id
      normalize: []
      short: HTTP request ID.
      type: keyword
    http.request.method:
      dashed_name: http-request-method
      description: 'HTTP request method.

        Prior to ECS 1.6.0 the following guidance was provided:

        "The field value must be normalized to lowercase for querying."

        As of ECS 1.6.0, the guidance is deprecated because the original case of the
        method may be useful in anomaly detection.  Original case will be mandated
        in ECS 2.0.0'
      example: GET, POST, PUT, PoST
      flat_name: http.request.method
      ignore_above: 1024
      level: extended
      name: request.method
      normalize: []
      short: HTTP request method.
      type: keyword
    http.request.mime_type:
      dashed_name: http-request-mime-type
      description: 'Mime type of the body of the request.

        This 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.'
      example: image/gif
      flat_name: http.request.mime_type
      ignore_above: 1024
      level: extended
      name: request.mime_type
      normalize: []
      short: Mime type of the body of the request.
      type: keyword
    http.request.referrer:
      dashed_name: http-request-referrer
      description: Referrer for this HTTP request.
      example: https://blog.example.com/
      flat_name: http.request.referrer
      ignore_above: 1024
      level: extended
      name: request.referrer
      normalize: []
      short: Referrer for this HTTP request.
      type: keyword
    http.response.body.bytes:
      dashed_name: http-response-body-bytes
      description: Size in bytes of the response body.
      example: 887
      flat_name: http.response.body.bytes
      format: bytes
      level: extended
      name: response.body.bytes
      normalize: []
      short: Size in bytes of the response body.
      type: long
    http.response.body.content:
      dashed_name: http-response-body-content
      description: The full HTTP response body.
      example: Hello world
      flat_name: http.response.body.content
      ignore_above: 1024
      level: extended
      multi_fields:
      - flat_name: http.response.body.content.text
        name: text
        norms: false
        type: text
      name: response.body.content
      normalize: []
      short: The full HTTP response body.
      type: keyword
    http.response.bytes:
      dashed_name: http-response-bytes
      description: Total size in bytes of the response (body and headers).
      example: 1437
      flat_name: http.response.bytes
      format: bytes
      level: extended
      name: response.bytes
      normalize: []
      short: Total size in bytes of the response (body and headers).
      type: long
    http.response.headers:
      dashed_name: http-response-headers
      description: 'Response headers in key/value pairs.

        Can be used add response header information to events. Should not contain
        nested objects. All values are stored as keyword.'
      example: '{"content-type": "application/json", "cache-status": "Miss"}'
      flat_name: http.response.headers
      level: custom
      name: response.headers
      normalize: []
      object_type: keyword
      short: Custom key/value pairs.
      type: object
    http.response.mime_type:
      dashed_name: http-response-mime-type
      description: 'Mime type of the body of the response.

        This 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.'
      example: image/gif
      flat_name: http.response.mime_type
      ignore_above: 1024
      level: extended
      name: response.mime_type
      normalize: []
      short: Mime type of the body of the response.
      type: keyword
    http.response.status_code:
      dashed_name: http-response-status-code
      description: HTTP response status code.
      example: 404
      flat_name: http.response.status_code
      format: string
      level: extended
      name: response.status_code
      normalize: []
      short: HTTP response status code.
      type: long
    http.version:
      dashed_name: http-version
      description: HTTP version.
      example: 1.1
      flat_name: http.version
      ignore_above: 1024
      level: extended
      name: version
      normalize: []
      short: HTTP version.
      type: keyword
  group: 2
  name: http
  prefix: http.
  short: Fields describing an HTTP request.
  title: HTTP
  type: group
interface:
  description: The interface fields are used to record ingress and egress interface
    information when reported by an observer (e.g. firewall, router, load balancer)
    in the context of the observer handling a network connection.  In the case of
    a single observer interface (e.g. network sensor on a span port) only the observer.ingress
    information should be populated.
  fields:
    interface.alias:
      dashed_name: interface-alias
      description: Interface alias as reported by the system, typically used in firewall
        implementations for e.g. inside, outside, or dmz logical interface naming.
      example: outside
      flat_name: interface.alias
      ignore_above: 1024
      level: extended
      name: alias
      normalize: []
      short: Interface alias
      type: keyword
    interface.id:
      dashed_name: interface-id
      description: Interface ID as reported by an observer (typically SNMP interface
        ID).
      example: 10
      flat_name: interface.id
      ignore_above: 1024
      level: extended
      name: id
      normalize: []
      short: Interface ID
      type: keyword
    interface.name:
      dashed_name: interface-name
      description: Interface name as reported by the system.
      example: eth0
      flat_name: interface.name
      ignore_above: 1024
      level: extended
      name: name
      normalize: []
      short: Interface name
      type: keyword
  group: 2
  name: interface
  prefix: interface.
  reusable:
    expected:
    - as: interface
      at: observer.ingress
      full: observer.ingress.interface
    - as: interface
      at: observer.egress
      full: observer.egress.interface
    top_level: false
  short: Fields to describe observer interface information.
  title: Interface
  type: group
log:
  description: 'Details about the event''s logging mechanism or logging transport.

    The log.* fields are typically populated with details about the logging mechanism
    used to create and/or transport the event. For example, syslog details belong
    under `log.syslog.*`.

    The details specific to your event source are typically not logged under `log.*`,
    but rather in `event.*` or in other ECS fields.'
  fields:
    log.file.path:
      dashed_name: log-file-path
      description: 'Full path to the log file this event came from, including the
        file name. It should include the drive letter, when appropriate.

        If the event wasn''t read from a log file, do not populate this field.'
      example: /var/log/fun-times.log
      flat_name: log.file.path
      ignore_above: 1024
      level: extended
      name: file.path
      normalize: []
      short: Full path to the log file this event came from.
      type: keyword
    log.level:
      dashed_name: log-level
      description: 'Original log level of the log event.

        If the source of the event provides a log level or textual severity, this
        is the one that goes in `log.level`. If your source doesn''t specify one,
        you may put your event transport''s severity here (e.g. Syslog severity).

        Some examples are `warn`, `err`, `i`, `informational`.'
      example: error
      flat_name: log.level
      ignore_above: 1024
      level: core
      name: level
      normalize: []
      short: Log level of the log event.
      type: keyword
    log.logger:
      dashed_name: log-logger
      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.
      example: org.elasticsearch.bootstrap.Bootstrap
      flat_name: log.logger
      ignore_above: 1024
      level: core
      name: logger
      normalize: []
      short: Name of the logger.
      type: keyword
    log.origin.file.line:
      dashed_name: log-origin-file-line
      description: The line number of the file containing the source code which originated
        the log event.
      example: 42
      flat_name: log.origin.file.line
      level: extended
      name: origin.file.line
      normalize: []
      short: The line number of the file which originated the log event.
      type: integer
    log.origin.file.name:
      dashed_name: log-origin-file-name
      description: 'The name of the file containing the source code which originated
        the log event.

        Note that this field is not meant to capture the log file. The correct field
        to capture the log file is `log.file.path`.'
      example: Bootstrap.java
      flat_name: log.origin.file.name
      ignore_above: 1024
      level: extended
      name: origin.file.name
      normalize: []
      short: The code file which originated the log event.
      type: keyword
    log.origin.function:
      dashed_name: log-origin-function
      description: The name of the function or method which originated the log event.
      example: init
      flat_name: log.origin.function
      ignore_above: 1024
      level: extended
      name: origin.function
      normalize: []
      short: The function which originated the log event.
      type: keyword
    log.original:
      dashed_name: log-original
      description: 'Deprecated for removal in next major version release. This field
        is superseded by  `event.original`.

        This is the original log message and contains the full log message before
        splitting it up in multiple parts.

        In contrast to the `message` field which can contain an extracted part of
        the log message, this field contains the original, full log message. It can
        have already some modifications applied like encoding or new lines removed
        to clean up the log message.

        This field is not indexed and doc_values are disabled so it can''t be queried
        but the value can be retrieved from `_source`.'
      doc_values: false
      example: Sep 19 08:26:10 localhost My log
      flat_name: log.original
      index: false
      level: core
      name: original
      normalize: []
      short: Deprecated original log message with light interpretation only (encoding,
        newlines).
      type: keyword
    log.syslog:
      dashed_name: log-syslog
      description: The Syslog metadata of the event, if the event was transmitted
        via Syslog. Please see RFCs 5424 or 3164.
      flat_name: log.syslog
      level: extended
      name: syslog
      normalize: []
      short: Syslog metadata
      type: object
    log.syslog.facility.code:
      dashed_name: log-syslog-facility-code
      description: 'The Syslog numeric facility of the log event, if available.

        According to RFCs 5424 and 3164, this value should be an integer between 0
        and 23.'
      example: 23
      flat_name: log.syslog.facility.code
      format: string
      level: extended
      name: syslog.facility.code
      normalize: []
      short: Syslog numeric facility of the event.
      type: long
    log.syslog.facility.name:
      dashed_name: log-syslog-facility-name
      description: The Syslog text-based facility of the log event, if available.
      example: local7
      flat_name: log.syslog.facility.name
      ignore_above: 1024
      level: extended
      name: syslog.facility.name
      normalize: []
      short: Syslog text-based facility of the event.
      type: keyword
    log.syslog.priority:
      dashed_name: log-syslog-priority
      description: 'Syslog numeric priority of the event, if available.

        According to RFCs 5424 and 3164, the priority is 8 * facility + severity.
        This number is therefore expected to contain a value between 0 and 191.'
      example: 135
      flat_name: log.syslog.priority
      format: string
      level: extended
      name: syslog.priority
      normalize: []
      short: Syslog priority of the event.
      type: long
    log.syslog.severity.code:
      dashed_name: log-syslog-severity-code
      description: 'The Syslog numeric severity of the log event, if available.

        If the event source publishing via Syslog provides a different numeric severity
        value (e.g. firewall, IDS), your source''s numeric severity should go to `event.severity`.
        If the event source does not specify a distinct severity, you can optionally
        copy the Syslog severity to `event.severity`.'
      example: 3
      flat_name: log.syslog.severity.code
      level: extended
      name: syslog.severity.code
      normalize: []
      short: Syslog numeric severity of the event.
      type: long
    log.syslog.severity.name:
      dashed_name: log-syslog-severity-name
      description: 'The Syslog numeric severity of the log event, if available.

        If the event source publishing via Syslog provides a different severity value
        (e.g. firewall, IDS), your source''s text severity should go to `log.level`.
        If the event source does not specify a distinct severity, you can optionally
        copy the Syslog severity to `log.level`.'
      example: Error
      flat_name: log.syslog.severity.name
      ignore_above: 1024
      level: extended
      name: syslog.severity.name
      normalize: []
      short: Syslog text-based severity of the event.
      type: keyword
  group: 2
  name: log
  prefix: log.
  short: Details about the event's logging mechanism.
  title: Log
  type: group
metrics:
  description: 'Fields for metrics generated from logs.

    Subkeys of this field should generally follow Prometheus naming convention, paying
    particular attention to the suffix.

    "A metric name should have a suffix indicating the unit, in plural form."  e.g.
    ttfb.seconds, heap.bytes, size.megabytes etc.

    https://prometheus.io/docs/practices/naming/'
  fields:
    metrics.puppet.changes.total:
      dashed_name: metrics-puppet-changes-total
      description: total number of changes performed in a puppet run
      flat_name: metrics.puppet.changes.total
      level: custom
      name: puppet.changes.total
      normalize: []
      short: total number of changes performed in a puppet run
      type: long
    metrics.puppet.resources.changed.total:
      dashed_name: metrics-puppet-resources-changed-total
      description: number of resources puppet changed
      flat_name: metrics.puppet.resources.changed.total
      level: custom
      name: puppet.resources.changed.total
      normalize: []
      short: number of resources puppet changed
      type: long
    metrics.puppet.resources.corrective_change.total:
      dashed_name: metrics-puppet-resources-corrective-change-total
      description: number of resources puppet corrective changes made
      flat_name: metrics.puppet.resources.corrective_change.total
      level: custom
      name: puppet.resources.corrective_change.total
      normalize: []
      short: number of resources puppet corrective changes made
      type: long
    metrics.puppet.resources.failed.total:
      dashed_name: metrics-puppet-resources-failed-total
      description: number of resources puppet failed to manage
      flat_name: metrics.puppet.resources.failed.total
      level: custom
      name: puppet.resources.failed.total
      normalize: []
      short: number of resources puppet failed to manage
      type: long
    metrics.puppet.resources.failed_to_restart.total:
      dashed_name: metrics-puppet-resources-failed-to-restart-total
      description: number of resources puppet failed to restart
      flat_name: metrics.puppet.resources.failed_to_restart.total
      level: custom
      name: puppet.resources.failed_to_restart.total
      normalize: []
      short: number of resources puppet failed to restart
      type: long
    metrics.puppet.resources.out_of_sync.total:
      dashed_name: metrics-puppet-resources-out-of-sync-total
      description: number of resources puppet found to be out_of_sync
      flat_name: metrics.puppet.resources.out_of_sync.total
      level: custom
      name: puppet.resources.out_of_sync.total
      normalize: []
      short: number of resources puppet found to be out_of_sync
      type: long
    metrics.puppet.resources.restarted.total:
      dashed_name: metrics-puppet-resources-restarted-total
      description: number of resources puppet restarted
      flat_name: metrics.puppet.resources.restarted.total
      level: custom
      name: puppet.resources.restarted.total
      normalize: []
      short: number of resources puppet restarted
      type: long
    metrics.puppet.resources.scheduled.total:
      dashed_name: metrics-puppet-resources-scheduled-total
      description: number of resources puppet scheduled
      flat_name: metrics.puppet.resources.scheduled.total
      level: custom
      name: puppet.resources.scheduled.total
      normalize: []
      short: number of resources puppet scheduled
      type: long
    metrics.puppet.resources.skipped.total:
      dashed_name: metrics-puppet-resources-skipped-total
      description: number of resources puppet skipped
      flat_name: metrics.puppet.resources.skipped.total
      level: custom
      name: puppet.resources.skipped.total
      normalize: []
      short: number of resources puppet skipped
      type: long
    metrics.puppet.resources.total:
      dashed_name: metrics-puppet-resources-total
      description: Total number of resources affected
      flat_name: metrics.puppet.resources.total
      level: custom
      name: puppet.resources.total
      normalize: []
      short: Total number of resources affected
      type: long
    metrics.puppet.runtime:
      dashed_name: metrics-puppet-runtime
      description: total seconds spent executing a specific resource
      example: '{"schedule": {"seconds": 0.25}}'
      flat_name: metrics.puppet.runtime
      level: custom
      name: puppet.runtime
      normalize: []
      short: total number of seconds spent executing a specific resource
      type: object
    metrics.ttfb.seconds:
      dashed_name: metrics-ttfb-seconds
      description: Time to first byte in seconds.
      flat_name: metrics.ttfb.seconds
      level: custom
      name: ttfb.seconds
      normalize: []
      short: Time to first byte in seconds.
      type: half_float
  group: 2
  name: metrics
  prefix: metrics.
  short: Fields for metrics generated from logs.
  title: Metrics
  type: group
network:
  description: 'The network is defined as the communication path over which a host
    or network event happens.

    The network.* fields should be populated with details about the network activity
    associated with an event.'
  fields:
    network.application:
      dashed_name: network-application
      description: 'A name given to an application level protocol. This can be arbitrarily
        assigned for things like microservices, but also apply to things like skype,
        icq, facebook, twitter. This would be used in situations where the vendor
        or service can be decoded such as from the source/dest IP owners, ports, or
        wire format.

        The field value must be normalized to lowercase for querying. See the documentation
        section "Implementing ECS".'
      example: aim
      flat_name: network.application
      ignore_above: 1024
      level: extended
      name: application
      normalize: []
      short: Application level protocol name.
      type: keyword
    network.bytes:
      dashed_name: network-bytes
      description: 'Total bytes transferred in both directions.

        If `source.bytes` and `destination.bytes` are known, `network.bytes` is their
        sum.'
      example: 368
      flat_name: network.bytes
      format: bytes
      level: core
      name: bytes
      normalize: []
      short: Total bytes transferred in both directions.
      type: long
    network.community_id:
      dashed_name: network-community-id
      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.

        Learn more at https://github.com/corelight/community-id-spec.'
      example: 1:hO+sN4H+MG5MY/8hIrXPqc4ZQz0=
      flat_name: network.community_id
      ignore_above: 1024
      level: extended
      name: community_id
      normalize: []
      short: A hash of source and destination IPs and ports.
      type: keyword
    network.direction:
      dashed_name: network-direction
      description: "Direction of the network traffic.\nRecommended values are:\n \
        \ * ingress\n  * egress\n  * inbound\n  * outbound\n  * internal\n  * external\n\
        \  * unknown\n\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."
      example: inbound
      flat_name: network.direction
      ignore_above: 1024
      level: core
      name: direction
      normalize: []
      short: Direction of the network traffic.
      type: keyword
    network.forwarded_ip:
      dashed_name: network-forwarded-ip
      description: Host IP address when the source IP address is the proxy.
      example: 192.1.1.2
      flat_name: network.forwarded_ip
      level: core
      name: forwarded_ip
      normalize: []
      short: Host IP address when the source IP address is the proxy.
      type: ip
    network.iana_number:
      dashed_name: network-iana-number
      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.
      example: 6
      flat_name: network.iana_number
      ignore_above: 1024
      level: extended
      name: iana_number
      normalize: []
      short: IANA Protocol Number.
      type: keyword
    network.inner:
      dashed_name: network-inner
      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.)
      flat_name: network.inner
      level: extended
      name: inner
      normalize: []
      short: Inner VLAN tag information
      type: object
    network.inner.vlan.id:
      dashed_name: network-inner-vlan-id
      description: VLAN ID as reported by the observer.
      example: 10
      flat_name: network.inner.vlan.id
      ignore_above: 1024
      level: extended
      name: id
      normalize: []
      original_fieldset: vlan
      short: VLAN ID as reported by the observer.
      type: keyword
    network.inner.vlan.name:
      dashed_name: network-inner-vlan-name
      description: Optional VLAN name as reported by the observer.
      example: outside
      flat_name: network.inner.vlan.name
      ignore_above: 1024
      level: extended
      name: name
      normalize: []
      original_fieldset: vlan
      short: Optional VLAN name as reported by the observer.
      type: keyword
    network.name:
      dashed_name: network-name
      description: Name given by operators to sections of their network.
      example: Guest Wifi
      flat_name: network.name
      ignore_above: 1024
      level: extended
      name: name
      normalize: []
      short: Name given by operators to sections of their network.
      type: keyword
    network.packets:
      dashed_name: network-packets
      description: 'Total packets transferred in both directions.

        If `source.packets` and `destination.packets` are known, `network.packets`
        is their sum.'
      example: 24
      flat_name: network.packets
      level: core
      name: packets
      normalize: []
      short: Total packets transferred in both directions.
      type: long
    network.protocol:
      dashed_name: network-protocol
      description: 'L7 Network protocol name. ex. http, lumberjack, transport protocol.

        The field value must be normalized to lowercase for querying. See the documentation
        section "Implementing ECS".'
      example: http
      flat_name: network.protocol
      ignore_above: 1024
      level: core
      name: protocol
      normalize: []
      short: L7 Network protocol name.
      type: keyword
    network.tcp_flags:
      dashed_name: network-tcp-flags
      description: 'Array of TCP Flags found in the packet.

        The field value must be normalized to lowercase for querying.'
      example: '["ack", "fin"]'
      flat_name: network.tcp_flags
      ignore_above: 1024
      level: custom
      name: tcp_flags
      normalize:
      - array
      short: Array of TCP Flags found in the packet.
      type: keyword
    network.transport:
      dashed_name: network-transport
      description: 'Same as network.iana_number, but instead using the Keyword name
        of the transport layer (udp, tcp, ipv6-icmp, etc.)

        The field value must be normalized to lowercase for querying. See the documentation
        section "Implementing ECS".'
      example: tcp
      flat_name: network.transport
      ignore_above: 1024
      level: core
      name: transport
      normalize: []
      short: Protocol Name corresponding to the field `iana_number`.
      type: keyword
    network.type:
      dashed_name: network-type
      description: 'In the OSI Model this would be the Network Layer. ipv4, ipv6,
        ipsec, pim, etc

        The field value must be normalized to lowercase for querying. See the documentation
        section "Implementing ECS".'
      example: ipv4
      flat_name: network.type
      ignore_above: 1024
      level: core
      name: type
      normalize: []
      short: In the OSI Model this would be the Network Layer. ipv4, ipv6, ipsec,
        pim, etc
      type: keyword
    network.vlan.id:
      dashed_name: network-vlan-id
      description: VLAN ID as reported by the observer.
      example: 10
      flat_name: network.vlan.id
      ignore_above: 1024
      level: extended
      name: id
      normalize: []
      original_fieldset: vlan
      short: VLAN ID as reported by the observer.
      type: keyword
    network.vlan.name:
      dashed_name: network-vlan-name
      description: Optional VLAN name as reported by the observer.
      example: outside
      flat_name: network.vlan.name
      ignore_above: 1024
      level: extended
      name: name
      normalize: []
      original_fieldset: vlan
      short: Optional VLAN name as reported by the observer.
      type: keyword
  group: 2
  name: network
  nestings:
  - network.inner.vlan
  - network.vlan
  prefix: network.
  reused_here:
  - full: network.vlan
    schema_name: vlan
    short: Fields to describe observed VLAN information.
  - full: network.inner.vlan
    schema_name: vlan
    short: Fields to describe observed VLAN information.
  short: Fields describing the communication path over which the event happened.
  title: Network
  type: group
normalized:
  description: 'Fields generated and normalized by the logging pipeline, but normally
    hidden from view in the Kibana Discover app and saved search results in the Dashboard
    app.

    This field is intended to contain fields that generally duplicate other fields
    and clutter the view.

    This field is hidden superficially by an entry in the index pattern source filters.'
  fields:
    normalized.dropped.field_type_mismatch:
      dashed_name: normalized-dropped-field-type-mismatch
      description: 'Array of dropped field names due to a type conflict.

        Values in this field are the equivalent of those in error type `mapper_parsing_exception`.'
      flat_name: normalized.dropped.field_type_mismatch
      ignore_above: 1024
      level: custom
      name: dropped.field_type_mismatch
      normalize: []
      short: Array of field names dropped due to a type conflict.
      type: keyword
    normalized.dropped.no_such_field:
      dashed_name: normalized-dropped-no-such-field
      description: 'Array of dropped field names due to no available field definition.

        Values in this field would normally be dropped silently by ElasticSearch.'
      flat_name: normalized.dropped.no_such_field
      ignore_above: 1024
      level: custom
      name: dropped.no_such_field
      normalize: []
      short: Array of field names dropped due to having no field definition.
      type: keyword
    normalized.message:
      dashed_name: normalized-message
      description: 'The message field downcased, truncated to 256 characters, and
        indexed in an aggregatable form.

        The downcasing and truncation is handled by the Logstash pipeline.

        Ideally, this should be a multi-field of the message field, but lacking a
        truncation feature, this behavior is currently impossible.  For more information,
        see: https://github.com/elastic/elasticsearch/issues/60329'
      example: Hello World
      flat_name: normalized.message
      ignore_above: 256
      level: custom
      name: message
      normalize: []
      short: Log message optimized for aggregations.
      type: keyword
  group: 2
  name: normalized
  prefix: normalized.
  short: Fields generated and normalized by the logging pipeline.
  title: Normalized
  type: group
observer:
  description: 'An observer is defined as a special network, security, or application
    device used to detect, observe, or create network, security, or application-related
    events and metrics.

    This could be a custom hardware appliance or a server that has been configured
    to run special network, security, or application software. Examples include firewalls,
    web proxies, intrusion detection/prevention systems, network monitoring sensors,
    web application firewalls, data loss prevention systems, and APM servers. The
    observer.* fields shall be populated with details of the system, if any, that
    detects, observes and/or creates a network, security, or application event or
    metric. Message queues and ETL components used in processing events or metrics
    are not considered observers in ECS.'
  fields:
    observer.egress:
      dashed_name: observer-egress
      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.
      flat_name: observer.egress
      level: extended
      name: egress
      normalize: []
      short: Object field for egress information
      type: object
    observer.egress.interface.alias:
      dashed_name: observer-egress-interface-alias
      description: Interface alias as reported by the system, typically used in firewall
        implementations for e.g. inside, outside, or dmz logical interface naming.
      example: outside
      flat_name: observer.egress.interface.alias
      ignore_above: 1024
      level: extended
      name: alias
      normalize: []
      original_fieldset: interface
      short: Interface alias
      type: keyword
    observer.egress.interface.id:
      dashed_name: observer-egress-interface-id
      description: Interface ID as reported by an observer (typically SNMP interface
        ID).
      example: 10
      flat_name: observer.egress.interface.id
      ignore_above: 1024
      level: extended
      name: id
      normalize: []
      original_fieldset: interface
      short: Interface ID
      type: keyword
    observer.egress.interface.name:
      dashed_name: observer-egress-interface-name
      description: Interface name as reported by the system.
      example: eth0
      flat_name: observer.egress.interface.name
      ignore_above: 1024
      level: extended
      name: name
      normalize: []
      original_fieldset: interface
      short: Interface name
      type: keyword
    observer.egress.vlan.id:
      dashed_name: observer-egress-vlan-id
      description: VLAN ID as reported by the observer.
      example: 10
      flat_name: observer.egress.vlan.id
      ignore_above: 1024
      level: extended
      name: id
      normalize: []
      original_fieldset: vlan
      short: VLAN ID as reported by the observer.
      type: keyword
    observer.egress.vlan.name:
      dashed_name: observer-egress-vlan-name
      description: Optional VLAN name as reported by the observer.
      example: outside
      flat_name: observer.egress.vlan.name
      ignore_above: 1024
      level: extended
      name: name
      normalize: []
      original_fieldset: vlan
      short: Optional VLAN name as reported by the observer.
      type: keyword
    observer.egress.zone:
      dashed_name: observer-egress-zone
      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.
      example: Public_Internet
      flat_name: observer.egress.zone
      ignore_above: 1024
      level: extended
      name: egress.zone
      normalize: []
      short: Observer Egress zone
      type: keyword
    observer.geo.city_name:
      dashed_name: observer-geo-city-name
      description: City name.
      example: Montreal
      flat_name: observer.geo.city_name
      ignore_above: 1024
      level: core
      name: city_name
      normalize: []
      original_fieldset: geo
      short: City name.
      type: keyword
    observer.geo.continent_code:
      dashed_name: observer-geo-continent-code
      description: Two-letter code representing continent's name.
      example: NA
      flat_name: observer.geo.continent_code
      ignore_above: 1024
      level: core
      name: continent_code
      normalize: []
      original_fieldset: geo
      short: Continent code.
      type: keyword
    observer.geo.continent_name:
      dashed_name: observer-geo-continent-name
      description: Name of the continent.
      example: North America
      flat_name: observer.geo.continent_name
      ignore_above: 1024
      level: core
      name: continent_name
      normalize: []
      original_fieldset: geo
      short: Name of the continent.
      type: keyword
    observer.geo.country_iso_code:
      dashed_name: observer-geo-country-iso-code
      description: Country ISO code.
      example: CA
      flat_name: observer.geo.country_iso_code
      ignore_above: 1024
      level: core
      name: country_iso_code
      normalize: []
      original_fieldset: geo
      short: Country ISO code.
      type: keyword
    observer.geo.country_name:
      dashed_name: observer-geo-country-name
      description: Country name.
      example: Canada
      flat_name: observer.geo.country_name
      ignore_above: 1024
      level: core
      name: country_name
      normalize: []
      original_fieldset: geo
      short: Country name.
      type: keyword
    observer.geo.location:
      dashed_name: observer-geo-location
      description: Longitude and latitude.
      example: '{ "lon": -73.614830, "lat": 45.505918 }'
      flat_name: observer.geo.location
      level: core
      name: location
      normalize: []
      original_fieldset: geo
      short: Longitude and latitude.
      type: geo_point
    observer.geo.name:
      dashed_name: observer-geo-name
      description: 'User-defined description of a location, at the level of granularity
        they care about.

        Could be the name of their data centers, the floor number, if this describes
        a local physical entity, city names.

        Not typically used in automated geolocation.'
      example: boston-dc
      flat_name: observer.geo.name
      ignore_above: 1024
      level: extended
      name: name
      normalize: []
      original_fieldset: geo
      short: User-defined description of a location.
      type: keyword
    observer.geo.postal_code:
      dashed_name: observer-geo-postal-code
      description: 'Postal code associated with the location.

        Values appropriate for this field may also be known as a postcode or ZIP code
        and will vary widely from country to country.'
      example: 94040
      flat_name: observer.geo.postal_code
      ignore_above: 1024
      level: core
      name: postal_code
      normalize: []
      original_fieldset: geo
      short: Postal code.
      type: keyword
    observer.geo.region_iso_code:
      dashed_name: observer-geo-region-iso-code
      description: Region ISO code.
      example: CA-QC
      flat_name: observer.geo.region_iso_code
      ignore_above: 1024
      level: core
      name: region_iso_code
      normalize: []
      original_fieldset: geo
      short: Region ISO code.
      type: keyword
    observer.geo.region_name:
      dashed_name: observer-geo-region-name
      description: Region name.
      example: Quebec
      flat_name: observer.geo.region_name
      ignore_above: 1024
      level: core
      name: region_name
      normalize: []
      original_fieldset: geo
      short: Region name.
      type: keyword
    observer.geo.timezone:
      dashed_name: observer-geo-timezone
      description: The time zone of the location, such as IANA time zone name.
      example: America/Argentina/Buenos_Aires
      flat_name: observer.geo.timezone
      ignore_above: 1024
      level: core
      name: timezone
      normalize: []
      original_fieldset: geo
      short: Time zone.
      type: keyword
    observer.hostname:
      dashed_name: observer-hostname
      description: Hostname of the observer.
      flat_name: observer.hostname
      ignore_above: 1024
      level: core
      name: hostname
      normalize: []
      short: Hostname of the observer.
      type: keyword
    observer.ingress:
      dashed_name: observer-ingress
      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.
      flat_name: observer.ingress
      level: extended
      name: ingress
      normalize: []
      short: Object field for ingress information
      type: object
    observer.ingress.interface.alias:
      dashed_name: observer-ingress-interface-alias
      description: Interface alias as reported by the system, typically used in firewall
        implementations for e.g. inside, outside, or dmz logical interface naming.
      example: outside
      flat_name: observer.ingress.interface.alias
      ignore_above: 1024
      level: extended
      name: alias
      normalize: []
      original_fieldset: interface
      short: Interface alias
      type: keyword
    observer.ingress.interface.id:
      dashed_name: observer-ingress-interface-id
      description: Interface ID as reported by an observer (typically SNMP interface
        ID).
      example: 10
      flat_name: observer.ingress.interface.id
      ignore_above: 1024
      level: extended
      name: id
      normalize: []
      original_fieldset: interface
      short: Interface ID
      type: keyword
    observer.ingress.interface.name:
      dashed_name: observer-ingress-interface-name
      description: Interface name as reported by the system.
      example: eth0
      flat_name: observer.ingress.interface.name
      ignore_above: 1024
      level: extended
      name: name
      normalize: []
      original_fieldset: interface
      short: Interface name
      type: keyword
    observer.ingress.vlan.id:
      dashed_name: observer-ingress-vlan-id
      description: VLAN ID as reported by the observer.
      example: 10
      flat_name: observer.ingress.vlan.id
      ignore_above: 1024
      level: extended
      name: id
      normalize: []
      original_fieldset: vlan
      short: VLAN ID as reported by the observer.
      type: keyword
    observer.ingress.vlan.name:
      dashed_name: observer-ingress-vlan-name
      description: Optional VLAN name as reported by the observer.
      example: outside
      flat_name: observer.ingress.vlan.name
      ignore_above: 1024
      level: extended
      name: name
      normalize: []
      original_fieldset: vlan
      short: Optional VLAN name as reported by the observer.
      type: keyword
    observer.ingress.zone:
      dashed_name: observer-ingress-zone
      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.
      example: DMZ
      flat_name: observer.ingress.zone
      ignore_above: 1024
      level: extended
      name: ingress.zone
      normalize: []
      short: Observer ingress zone
      type: keyword
    observer.ip:
      dashed_name: observer-ip
      description: IP addresses of the observer.
      flat_name: observer.ip
      level: core
      name: ip
      normalize:
      - array
      short: IP addresses of the observer.
      type: ip
    observer.mac:
      dashed_name: observer-mac
      description: 'MAC addresses of the observer.

        The 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.'
      example: '["00-00-5E-00-53-23", "00-00-5E-00-53-24"]'
      flat_name: observer.mac
      ignore_above: 1024
      level: core
      name: mac
      normalize:
      - array
      short: MAC addresses of the observer.
      type: keyword
    observer.name:
      dashed_name: observer-name
      description: 'Custom name of the observer.

        This is a name that can be given to an observer. This can be helpful for example
        if multiple firewalls of the same model are used in an organization.

        If no custom name is needed, the field can be left empty.'
      example: 1_proxySG
      flat_name: observer.name
      ignore_above: 1024
      level: extended
      name: name
      normalize: []
      short: Custom name of the observer.
      type: keyword
    observer.os.family:
      dashed_name: observer-os-family
      description: OS family (such as redhat, debian, freebsd, windows).
      example: debian
      flat_name: observer.os.family
      ignore_above: 1024
      level: extended
      name: family
      normalize: []
      original_fieldset: os
      short: OS family (such as redhat, debian, freebsd, windows).
      type: keyword
    observer.os.full:
      dashed_name: observer-os-full
      description: Operating system name, including the version or code name.
      example: Mac OS Mojave
      flat_name: observer.os.full
      ignore_above: 1024
      level: extended
      multi_fields:
      - flat_name: observer.os.full.text
        name: text
        norms: false
        type: text
      name: full
      normalize: []
      original_fieldset: os
      short: Operating system name, including the version or code name.
      type: keyword
    observer.os.kernel:
      dashed_name: observer-os-kernel
      description: Operating system kernel version as a raw string.
      example: 4.4.0-112-generic
      flat_name: observer.os.kernel
      ignore_above: 1024
      level: extended
      name: kernel
      normalize: []
      original_fieldset: os
      short: Operating system kernel version as a raw string.
      type: keyword
    observer.os.name:
      dashed_name: observer-os-name
      description: Operating system name, without the version.
      example: Mac OS X
      flat_name: observer.os.name
      ignore_above: 1024
      level: extended
      multi_fields:
      - flat_name: observer.os.name.text
        name: text
        norms: false
        type: text
      name: name
      normalize: []
      original_fieldset: os
      short: Operating system name, without the version.
      type: keyword
    observer.os.platform:
      dashed_name: observer-os-platform
      description: Operating system platform (such centos, ubuntu, windows).
      example: darwin
      flat_name: observer.os.platform
      ignore_above: 1024
      level: extended
      name: platform
      normalize: []
      original_fieldset: os
      short: Operating system platform (such centos, ubuntu, windows).
      type: keyword
    observer.os.type:
      dashed_name: observer-os-type
      description: 'Use the `os.type` field to categorize the operating system into
        one of the broad commercial families.

        One of these following values should be used (lowercase): linux, macos, unix,
        windows.

        If the OS you''re dealing with is not in the list, the field should not be
        populated. Please let us know by opening an issue with ECS, to propose its
        addition.'
      example: macos
      flat_name: observer.os.type
      ignore_above: 1024
      level: extended
      name: type
      normalize: []
      original_fieldset: os
      short: 'Which commercial OS family (one of: linux, macos, unix or windows).'
      type: keyword
    observer.os.version:
      dashed_name: observer-os-version
      description: Operating system version as a raw string.
      example: 10.14.1
      flat_name: observer.os.version
      ignore_above: 1024
      level: extended
      name: version
      normalize: []
      original_fieldset: os
      short: Operating system version as a raw string.
      type: keyword
    observer.product:
      dashed_name: observer-product
      description: The product name of the observer.
      example: s200
      flat_name: observer.product
      ignore_above: 1024
      level: extended
      name: product
      normalize: []
      short: The product name of the observer.
      type: keyword
    observer.serial_number:
      dashed_name: observer-serial-number
      description: Observer serial number.
      flat_name: observer.serial_number
      ignore_above: 1024
      level: extended
      name: serial_number
      normalize: []
      short: Observer serial number.
      type: keyword
    observer.type:
      dashed_name: observer-type
      description: 'The type of the observer the data is coming from.

        There is no predefined list of observer types. Some examples are `forwarder`,
        `firewall`, `ids`, `ips`, `proxy`, `poller`, `sensor`, `APM server`.'
      example: firewall
      flat_name: observer.type
      ignore_above: 1024
      level: core
      name: type
      normalize: []
      short: The type of the observer the data is coming from.
      type: keyword
    observer.vendor:
      dashed_name: observer-vendor
      description: Vendor name of the observer.
      example: Symantec
      flat_name: observer.vendor
      ignore_above: 1024
      level: core
      name: vendor
      normalize: []
      short: Vendor name of the observer.
      type: keyword
    observer.version:
      dashed_name: observer-version
      description: Observer version.
      flat_name: observer.version
      ignore_above: 1024
      level: core
      name: version
      normalize: []
      short: Observer version.
      type: keyword
  group: 2
  name: observer
  nestings:
  - observer.egress.interface
  - observer.egress.vlan
  - observer.geo
  - observer.ingress.interface
  - observer.ingress.vlan
  - observer.os
  prefix: observer.
  reused_here:
  - full: observer.geo
    schema_name: geo
    short: Fields describing a location.
  - full: observer.ingress.interface
    schema_name: interface
    short: Fields to describe observer interface information.
  - full: observer.egress.interface
    schema_name: interface
    short: Fields to describe observer interface information.
  - full: observer.os
    schema_name: os
    short: OS fields contain information about the operating system.
  - full: observer.ingress.vlan
    schema_name: vlan
    short: Fields to describe observed VLAN information.
  - full: observer.egress.vlan
    schema_name: vlan
    short: Fields to describe observed VLAN information.
  short: Fields describing an entity observing the event from outside the host.
  title: Observer
  type: group
orchestrator:
  description: Fields that describe the resources which container orchestrators manage
    or act upon.
  fields:
    orchestrator.api_version:
      dashed_name: orchestrator-api-version
      description: API version being used to carry out the action
      example: v1beta1
      flat_name: orchestrator.api_version
      ignore_above: 1024
      level: extended
      name: api_version
      normalize: []
      short: API version being used to carry out the action
      type: keyword
    orchestrator.cluster.name:
      dashed_name: orchestrator-cluster-name
      description: Name of the cluster.
      flat_name: orchestrator.cluster.name
      ignore_above: 1024
      level: extended
      name: cluster.name
      normalize: []
      short: Name of the cluster.
      type: keyword
    orchestrator.cluster.url:
      dashed_name: orchestrator-cluster-url
      description: URL of the API used to manage the cluster.
      flat_name: orchestrator.cluster.url
      ignore_above: 1024
      level: extended
      name: cluster.url
      normalize: []
      short: URL of the API used to manage the cluster.
      type: keyword
    orchestrator.cluster.version:
      dashed_name: orchestrator-cluster-version
      description: The version of the cluster.
      flat_name: orchestrator.cluster.version
      ignore_above: 1024
      level: extended
      name: cluster.version
      normalize: []
      short: The version of the cluster.
      type: keyword
    orchestrator.namespace:
      dashed_name: orchestrator-namespace
      description: Namespace in which the action is taking place.
      example: kube-system
      flat_name: orchestrator.namespace
      ignore_above: 1024
      level: extended
      name: namespace
      normalize: []
      short: Namespace in which the action is taking place.
      type: keyword
    orchestrator.organization:
      dashed_name: orchestrator-organization
      description: Organization affected by the event (for multi-tenant orchestrator
        setups).
      example: elastic
      flat_name: orchestrator.organization
      ignore_above: 1024
      level: extended
      name: organization
      normalize: []
      short: Organization affected by the event (for multi-tenant orchestrator setups).
      type: keyword
    orchestrator.resource.annotation:
      dashed_name: orchestrator-resource-annotation
      description: The list of annotations added to the resource.
      example: '[''key1:value1'', ''key2:value2'', ''key3:value3'']'
      flat_name: orchestrator.resource.annotation
      ignore_above: 1024
      level: extended
      name: resource.annotation
      normalize:
      - array
      short: The list of annotations added to the resource.
      type: keyword
    orchestrator.resource.id:
      dashed_name: orchestrator-resource-id
      description: Unique ID of the resource being acted upon.
      flat_name: orchestrator.resource.id
      ignore_above: 1024
      level: extended
      name: resource.id
      normalize: []
      short: Unique ID of the resource being acted upon.
      type: keyword
    orchestrator.resource.label:
      dashed_name: orchestrator-resource-label
      description: The list of labels added to the resource.
      example: '[''key1:value1'', ''key2:value2'', ''key3:value3'']'
      flat_name: orchestrator.resource.label
      ignore_above: 1024
      level: extended
      name: resource.label
      normalize:
      - array
      short: The list of labels added to the resource.
      type: keyword
    orchestrator.resource.name:
      dashed_name: orchestrator-resource-name
      description: Name of the resource being acted upon.
      example: test-pod-cdcws
      flat_name: orchestrator.resource.name
      ignore_above: 1024
      level: extended
      name: resource.name
      normalize: []
      short: Name of the resource being acted upon.
      type: keyword
    orchestrator.resource.type:
      dashed_name: orchestrator-resource-type
      description: Type of resource being acted upon.
      example: service
      flat_name: orchestrator.resource.type
      ignore_above: 1024
      level: extended
      name: resource.type
      normalize: []
      short: Type of resource being acted upon.
      type: keyword
    orchestrator.type:
      dashed_name: orchestrator-type
      description: Orchestrator cluster type (e.g. kubernetes, nomad or cloudfoundry).
      example: kubernetes
      flat_name: orchestrator.type
      ignore_above: 1024
      level: extended
      name: type
      normalize: []
      short: Orchestrator cluster type (e.g. kubernetes, nomad or cloudfoundry).
      type: keyword
  group: 2
  name: orchestrator
  prefix: orchestrator.
  short: Fields relevant to container orchestrators.
  title: Orchestrator
  type: group
os:
  description: The OS fields contain information about the operating system.
  fields:
    os.family:
      dashed_name: os-family
      description: OS family (such as redhat, debian, freebsd, windows).
      example: debian
      flat_name: os.family
      ignore_above: 1024
      level: extended
      name: family
      normalize: []
      short: OS family (such as redhat, debian, freebsd, windows).
      type: keyword
    os.full:
      dashed_name: os-full
      description: Operating system name, including the version or code name.
      example: Mac OS Mojave
      flat_name: os.full
      ignore_above: 1024
      level: extended
      multi_fields:
      - flat_name: os.full.text
        name: text
        norms: false
        type: text
      name: full
      normalize: []
      short: Operating system name, including the version or code name.
      type: keyword
    os.kernel:
      dashed_name: os-kernel
      description: Operating system kernel version as a raw string.
      example: 4.4.0-112-generic
      flat_name: os.kernel
      ignore_above: 1024
      level: extended
      name: kernel
      normalize: []
      short: Operating system kernel version as a raw string.
      type: keyword
    os.name:
      dashed_name: os-name
      description: Operating system name, without the version.
      example: Mac OS X
      flat_name: os.name
      ignore_above: 1024
      level: extended
      multi_fields:
      - flat_name: os.name.text
        name: text
        norms: false
        type: text
      name: name
      normalize: []
      short: Operating system name, without the version.
      type: keyword
    os.platform:
      dashed_name: os-platform
      description: Operating system platform (such centos, ubuntu, windows).
      example: darwin
      flat_name: os.platform
      ignore_above: 1024
      level: extended
      name: platform
      normalize: []
      short: Operating system platform (such centos, ubuntu, windows).
      type: keyword
    os.type:
      dashed_name: os-type
      description: 'Use the `os.type` field to categorize the operating system into
        one of the broad commercial families.

        One of these following values should be used (lowercase): linux, macos, unix,
        windows.

        If the OS you''re dealing with is not in the list, the field should not be
        populated. Please let us know by opening an issue with ECS, to propose its
        addition.'
      example: macos
      flat_name: os.type
      ignore_above: 1024
      level: extended
      name: type
      normalize: []
      short: 'Which commercial OS family (one of: linux, macos, unix or windows).'
      type: keyword
    os.version:
      dashed_name: os-version
      description: Operating system version as a raw string.
      example: 10.14.1
      flat_name: os.version
      ignore_above: 1024
      level: extended
      name: version
      normalize: []
      short: Operating system version as a raw string.
      type: keyword
  group: 2
  name: os
  prefix: os.
  reusable:
    expected:
    - as: os
      at: observer
      full: observer.os
    - as: os
      at: host
      full: host.os
    - as: os
      at: user_agent
      full: user_agent.os
    top_level: false
  short: OS fields contain information about the operating system.
  title: Operating System
  type: group
package:
  description: These fields contain information about an installed software package.
    It contains general information about a package, such as name, version or size.
    It also contains installation details, such as time or location.
  fields:
    package.architecture:
      dashed_name: package-architecture
      description: Package architecture.
      example: x86_64
      flat_name: package.architecture
      ignore_above: 1024
      level: extended
      name: architecture
      normalize: []
      short: Package architecture.
      type: keyword
    package.build_version:
      dashed_name: package-build-version
      description: 'Additional information about the build version of the installed
        package.

        For example use the commit SHA of a non-released package.'
      example: 36f4f7e89dd61b0988b12ee000b98966867710cd
      flat_name: package.build_version
      ignore_above: 1024
      level: extended
      name: build_version
      normalize: []
      short: Build version information
      type: keyword
    package.checksum:
      dashed_name: package-checksum
      description: Checksum of the installed package for verification.
      example: 68b329da9893e34099c7d8ad5cb9c940
      flat_name: package.checksum
      ignore_above: 1024
      level: extended
      name: checksum
      normalize: []
      short: Checksum of the installed package for verification.
      type: keyword
    package.description:
      dashed_name: package-description
      description: Description of the package.
      example: Open source programming language to build simple/reliable/efficient
        software.
      flat_name: package.description
      ignore_above: 1024
      level: extended
      name: description
      normalize: []
      short: Description of the package.
      type: keyword
    package.install_scope:
      dashed_name: package-install-scope
      description: Indicating how the package was installed, e.g. user-local, global.
      example: global
      flat_name: package.install_scope
      ignore_above: 1024
      level: extended
      name: install_scope
      normalize: []
      short: Indicating how the package was installed, e.g. user-local, global.
      type: keyword
    package.installed:
      dashed_name: package-installed
      description: Time when package was installed.
      flat_name: package.installed
      level: extended
      name: installed
      normalize: []
      short: Time when package was installed.
      type: date
    package.license:
      dashed_name: package-license
      description: 'License under which the package was released.

        Use a short name, e.g. the license identifier from SPDX License List where
        possible (https://spdx.org/licenses/).'
      example: Apache License 2.0
      flat_name: package.license
      ignore_above: 1024
      level: extended
      name: license
      normalize: []
      short: Package license
      type: keyword
    package.name:
      dashed_name: package-name
      description: Package name
      example: go
      flat_name: package.name
      ignore_above: 1024
      level: extended
      name: name
      normalize: []
      short: Package name
      type: keyword
    package.path:
      dashed_name: package-path
      description: Path where the package is installed.
      example: /usr/local/Cellar/go/1.12.9/
      flat_name: package.path
      ignore_above: 1024
      level: extended
      name: path
      normalize: []
      short: Path where the package is installed.
      type: keyword
    package.reference:
      dashed_name: package-reference
      description: Home page or reference URL of the software in this package, if
        available.
      example: https://golang.org
      flat_name: package.reference
      ignore_above: 1024
      level: extended
      name: reference
      normalize: []
      short: Package home page or reference URL
      type: keyword
    package.size:
      dashed_name: package-size
      description: Package size in bytes.
      example: 62231
      flat_name: package.size
      format: string
      level: extended
      name: size
      normalize: []
      short: Package size in bytes.
      type: long
    package.type:
      dashed_name: package-type
      description: 'Type of package.

        This should contain the package file type, rather than the package manager
        name. Examples: rpm, dpkg, brew, npm, gem, nupkg, jar.'
      example: rpm
      flat_name: package.type
      ignore_above: 1024
      level: extended
      name: type
      normalize: []
      short: Package type
      type: keyword
    package.version:
      dashed_name: package-version
      description: Package version
      example: 1.12.9
      flat_name: package.version
      ignore_above: 1024
      level: extended
      name: version
      normalize: []
      short: Package version
      type: keyword
  group: 2
  name: package
  prefix: package.
  short: These fields contain information about an installed software package.
  title: Package
  type: group
process:
  description: 'These fields contain information about a process.

    These fields can help you correlate metrics information with a process id/name
    from a log message.  The `process.pid` often stays in the metric itself and is
    copied to the global field for correlation.'
  fields:
    process.args:
      dashed_name: process-args
      description: 'Array of process arguments, starting with the absolute path to
        the executable.

        May be filtered to protect sensitive information.'
      example: '["/usr/bin/ssh", "-l", "user", "10.0.0.16"]'
      flat_name: process.args
      ignore_above: 1024
      level: extended
      name: args
      normalize:
      - array
      short: Array of process arguments.
      type: keyword
    process.args_count:
      dashed_name: process-args-count
      description: 'Length of the process.args array.

        This field can be useful for querying or performing bucket analysis on how
        many arguments were provided to start a process. More arguments may be an
        indication of suspicious activity.'
      example: 4
      flat_name: process.args_count
      level: extended
      name: args_count
      normalize: []
      short: Length of the process.args array.
      type: long
    process.command_line:
      dashed_name: process-command-line
      description: 'Full command line that started the process, including the absolute
        path to the executable, and all arguments.

        Some arguments may be filtered to protect sensitive information.'
      example: /usr/bin/ssh -l user 10.0.0.16
      flat_name: process.command_line
      ignore_above: 1024
      level: extended
      multi_fields:
      - flat_name: process.command_line.text
        name: text
        norms: false
        type: text
      name: command_line
      normalize: []
      short: Full command line that started the process.
      type: keyword
    process.entity_id:
      dashed_name: process-entity-id
      description: 'Unique identifier for the process.

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

        Constructing 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.'
      example: c2c455d9f99375d
      flat_name: process.entity_id
      ignore_above: 1024
      level: extended
      name: entity_id
      normalize: []
      short: Unique identifier for the process.
      type: keyword
    process.executable:
      dashed_name: process-executable
      description: Absolute path to the process executable.
      example: /usr/bin/ssh
      flat_name: process.executable
      ignore_above: 1024
      level: extended
      multi_fields:
      - flat_name: process.executable.text
        name: text
        norms: false
        type: text
      name: executable
      normalize: []
      short: Absolute path to the process executable.
      type: keyword
    process.exit_code:
      dashed_name: process-exit-code
      description: 'The exit code of the process, if this is a termination event.

        The field should be absent if there is no exit code for the event (e.g. process
        start).'
      example: 137
      flat_name: process.exit_code
      level: extended
      name: exit_code
      normalize: []
      short: The exit code of the process.
      type: long
    process.name:
      dashed_name: process-name
      description: 'Process name.

        Sometimes called program name or similar.'
      example: ssh
      flat_name: process.name
      ignore_above: 1024
      level: extended
      multi_fields:
      - flat_name: process.name.text
        name: text
        norms: false
        type: text
      name: name
      normalize: []
      short: Process name.
      type: keyword
    process.pgid:
      dashed_name: process-pgid
      description: Identifier of the group of processes the process belongs to.
      flat_name: process.pgid
      format: string
      level: extended
      name: pgid
      normalize: []
      short: Identifier of the group of processes the process belongs to.
      type: long
    process.pid:
      dashed_name: process-pid
      description: Process id.
      example: 4242
      flat_name: process.pid
      format: string
      level: core
      name: pid
      normalize: []
      short: Process id.
      type: long
    process.ppid:
      dashed_name: process-ppid
      description: Parent process' pid.
      example: 4241
      flat_name: process.ppid
      format: string
      level: extended
      name: ppid
      normalize: []
      short: Parent process' pid.
      type: long
    process.start:
      dashed_name: process-start
      description: The time the process started.
      example: '2016-05-23T08:05:34.853Z'
      flat_name: process.start
      level: extended
      name: start
      normalize: []
      short: The time the process started.
      type: date
    process.thread.id:
      dashed_name: process-thread-id
      description: Thread ID.
      example: 4242
      flat_name: process.thread.id
      format: string
      level: extended
      name: thread.id
      normalize: []
      short: Thread ID.
      type: long
    process.thread.name:
      dashed_name: process-thread-name
      description: Thread name.
      example: thread-0
      flat_name: process.thread.name
      ignore_above: 1024
      level: extended
      name: thread.name
      normalize: []
      short: Thread name.
      type: keyword
    process.title:
      dashed_name: process-title
      description: 'Process title.

        The proctitle, some times the same as process name. Can also be different:
        for example a browser setting its title to the web page currently opened.'
      flat_name: process.title
      ignore_above: 1024
      level: extended
      multi_fields:
      - flat_name: process.title.text
        name: text
        norms: false
        type: text
      name: title
      normalize: []
      short: Process title.
      type: keyword
    process.uptime:
      dashed_name: process-uptime
      description: Seconds the process has been up.
      example: 1325
      flat_name: process.uptime
      level: extended
      name: uptime
      normalize: []
      short: Seconds the process has been up.
      type: long
    process.working_directory:
      dashed_name: process-working-directory
      description: The working directory of the process.
      example: /home/alice
      flat_name: process.working_directory
      ignore_above: 1024
      level: extended
      multi_fields:
      - flat_name: process.working_directory.text
        name: text
        norms: false
        type: text
      name: working_directory
      normalize: []
      short: The working directory of the process.
      type: keyword
  group: 2
  name: process
  nestings:
  - process.code_signature
  - process.elf
  - process.hash
  - process.parent
  - process.pe
  prefix: process.
  reusable:
    expected:
    - as: parent
      at: process
      full: process.parent
      short_override: Information about the parent process.
    top_level: true
  reused_here:
  - full: process.code_signature
    schema_name: code_signature
    short: These fields contain information about binary code signatures.
  - beta: This field reuse is beta and subject to change.
    full: process.elf
    schema_name: elf
    short: These fields contain Linux Executable Linkable Format (ELF) metadata.
  - full: process.hash
    schema_name: hash
    short: Hashes, usually file hashes.
  - full: process.pe
    schema_name: pe
    short: These fields contain Windows Portable Executable (PE) metadata.
  - full: process.parent
    schema_name: process
    short: Information about the parent process.
  short: These fields contain information about a process.
  title: Process
  type: group
rule:
  description: 'Rule fields are used to capture the specifics of any observer or agent
    rules that generate alerts or other notable events.

    Examples of data sources that would populate the rule fields include: network
    admission control platforms, network or host IDS/IPS, network firewalls, web application
    firewalls, url filters, endpoint detection and response (EDR) systems, etc.'
  fields:
    rule.author:
      dashed_name: rule-author
      description: Name, organization, or pseudonym of the author or authors who created
        the rule used to generate this event.
      example: '["Star-Lord"]'
      flat_name: rule.author
      ignore_above: 1024
      level: extended
      name: author
      normalize:
      - array
      short: Rule author
      type: keyword
    rule.category:
      dashed_name: rule-category
      description: A categorization value keyword used by the entity using the rule
        for detection of this event.
      example: Attempted Information Leak
      flat_name: rule.category
      ignore_above: 1024
      level: extended
      name: category
      normalize: []
      short: Rule category
      type: keyword
    rule.description:
      dashed_name: rule-description
      description: The description of the rule generating the event.
      example: Block requests to public DNS over HTTPS / TLS protocols
      flat_name: rule.description
      ignore_above: 1024
      level: extended
      name: description
      normalize: []
      short: Rule description
      type: keyword
    rule.id:
      dashed_name: rule-id
      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.
      example: 101
      flat_name: rule.id
      ignore_above: 1024
      level: extended
      name: id
      normalize: []
      short: Rule ID
      type: keyword
    rule.license:
      dashed_name: rule-license
      description: Name of the license under which the rule used to generate this
        event is made available.
      example: Apache 2.0
      flat_name: rule.license
      ignore_above: 1024
      level: extended
      name: license
      normalize: []
      short: Rule license
      type: keyword
    rule.name:
      dashed_name: rule-name
      description: The name of the rule or signature generating the event.
      example: BLOCK_DNS_over_TLS
      flat_name: rule.name
      ignore_above: 1024
      level: extended
      name: name
      normalize: []
      short: Rule name
      type: keyword
    rule.reference:
      dashed_name: rule-reference
      description: 'Reference URL to additional information about the rule used to
        generate this event.

        The URL can point to the vendor''s documentation about the rule. If that''s
        not available, it can also be a link to a more general page describing this
        type of alert.'
      example: https://en.wikipedia.org/wiki/DNS_over_TLS
      flat_name: rule.reference
      ignore_above: 1024
      level: extended
      name: reference
      normalize: []
      short: Rule reference URL
      type: keyword
    rule.ruleset:
      dashed_name: rule-ruleset
      description: Name of the ruleset, policy, group, or parent category in which
        the rule used to generate this event is a member.
      example: Standard_Protocol_Filters
      flat_name: rule.ruleset
      ignore_above: 1024
      level: extended
      name: ruleset
      normalize: []
      short: Rule ruleset
      type: keyword
    rule.uuid:
      dashed_name: rule-uuid
      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.
      example: 1100110011
      flat_name: rule.uuid
      ignore_above: 1024
      level: extended
      name: uuid
      normalize: []
      short: Rule UUID
      type: keyword
    rule.version:
      dashed_name: rule-version
      description: The version / revision of the rule being used for analysis.
      example: 1.1
      flat_name: rule.version
      ignore_above: 1024
      level: extended
      name: version
      normalize: []
      short: Rule version
      type: keyword
  group: 2
  name: rule
  prefix: rule.
  short: Fields to capture details about rules used to generate alerts or other notable
    events.
  title: Rule
  type: group
server:
  description: 'A Server is defined as the responder in a network connection for events
    regarding sessions, connections, or bidirectional flow records.

    For TCP events, the server is the receiver of the initial SYN packet(s) of the
    TCP connection. For other protocols, the server is generally the responder in
    the network transaction. Some systems actually use the term "responder" to refer
    the server in TCP connections. The server fields describe details about the system
    acting as the server in the network event. Server fields are usually populated
    in conjunction with client fields. Server fields are generally not populated for
    packet-level events.

    Client / server representations can add semantic context to an exchange, which
    is helpful to visualize the data in certain situations. If your context falls
    in that category, you should still ensure that source and destination are filled
    appropriately.'
  fields:
    server.address:
      dashed_name: server-address
      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.

        Then it should be duplicated to `.ip` or `.domain`, depending on which one
        it is.'
      flat_name: server.address
      ignore_above: 1024
      level: extended
      name: address
      normalize: []
      short: Server network address.
      type: keyword
    server.as.number:
      dashed_name: server-as-number
      description: Unique number allocated to the autonomous system. The autonomous
        system number (ASN) uniquely identifies each network on the Internet.
      example: 15169
      flat_name: server.as.number
      level: extended
      name: number
      normalize: []
      original_fieldset: as
      short: Unique number allocated to the autonomous system.
      type: long
    server.as.organization.name:
      dashed_name: server-as-organization-name
      description: Organization name.
      example: Google LLC
      flat_name: server.as.organization.name
      ignore_above: 1024
      level: extended
      multi_fields:
      - flat_name: server.as.organization.name.text
        name: text
        norms: false
        type: text
      name: organization.name
      normalize: []
      original_fieldset: as
      short: Organization name.
      type: keyword
    server.bytes:
      dashed_name: server-bytes
      description: Bytes sent from the server to the client.
      example: 184
      flat_name: server.bytes
      format: bytes
      level: core
      name: bytes
      normalize: []
      short: Bytes sent from the server to the client.
      type: long
    server.domain:
      dashed_name: server-domain
      description: Server domain.
      flat_name: server.domain
      ignore_above: 1024
      level: core
      name: domain
      normalize: []
      short: Server domain.
      type: keyword
    server.geo.city_name:
      dashed_name: server-geo-city-name
      description: City name.
      example: Montreal
      flat_name: server.geo.city_name
      ignore_above: 1024
      level: core
      name: city_name
      normalize: []
      original_fieldset: geo
      short: City name.
      type: keyword
    server.geo.continent_code:
      dashed_name: server-geo-continent-code
      description: Two-letter code representing continent's name.
      example: NA
      flat_name: server.geo.continent_code
      ignore_above: 1024
      level: core
      name: continent_code
      normalize: []
      original_fieldset: geo
      short: Continent code.
      type: keyword
    server.geo.continent_name:
      dashed_name: server-geo-continent-name
      description: Name of the continent.
      example: North America
      flat_name: server.geo.continent_name
      ignore_above: 1024
      level: core
      name: continent_name
      normalize: []
      original_fieldset: geo
      short: Name of the continent.
      type: keyword
    server.geo.country_iso_code:
      dashed_name: server-geo-country-iso-code
      description: Country ISO code.
      example: CA
      flat_name: server.geo.country_iso_code
      ignore_above: 1024
      level: core
      name: country_iso_code
      normalize: []
      original_fieldset: geo
      short: Country ISO code.
      type: keyword
    server.geo.country_name:
      dashed_name: server-geo-country-name
      description: Country name.
      example: Canada
      flat_name: server.geo.country_name
      ignore_above: 1024
      level: core
      name: country_name
      normalize: []
      original_fieldset: geo
      short: Country name.
      type: keyword
    server.geo.location:
      dashed_name: server-geo-location
      description: Longitude and latitude.
      example: '{ "lon": -73.614830, "lat": 45.505918 }'
      flat_name: server.geo.location
      level: core
      name: location
      normalize: []
      original_fieldset: geo
      short: Longitude and latitude.
      type: geo_point
    server.geo.name:
      dashed_name: server-geo-name
      description: 'User-defined description of a location, at the level of granularity
        they care about.

        Could be the name of their data centers, the floor number, if this describes
        a local physical entity, city names.

        Not typically used in automated geolocation.'
      example: boston-dc
      flat_name: server.geo.name
      ignore_above: 1024
      level: extended
      name: name
      normalize: []
      original_fieldset: geo
      short: User-defined description of a location.
      type: keyword
    server.geo.postal_code:
      dashed_name: server-geo-postal-code
      description: 'Postal code associated with the location.

        Values appropriate for this field may also be known as a postcode or ZIP code
        and will vary widely from country to country.'
      example: 94040
      flat_name: server.geo.postal_code
      ignore_above: 1024
      level: core
      name: postal_code
      normalize: []
      original_fieldset: geo
      short: Postal code.
      type: keyword
    server.geo.region_iso_code:
      dashed_name: server-geo-region-iso-code
      description: Region ISO code.
      example: CA-QC
      flat_name: server.geo.region_iso_code
      ignore_above: 1024
      level: core
      name: region_iso_code
      normalize: []
      original_fieldset: geo
      short: Region ISO code.
      type: keyword
    server.geo.region_name:
      dashed_name: server-geo-region-name
      description: Region name.
      example: Quebec
      flat_name: server.geo.region_name
      ignore_above: 1024
      level: core
      name: region_name
      normalize: []
      original_fieldset: geo
      short: Region name.
      type: keyword
    server.geo.timezone:
      dashed_name: server-geo-timezone
      description: The time zone of the location, such as IANA time zone name.
      example: America/Argentina/Buenos_Aires
      flat_name: server.geo.timezone
      ignore_above: 1024
      level: core
      name: timezone
      normalize: []
      original_fieldset: geo
      short: Time zone.
      type: keyword
    server.ip:
      dashed_name: server-ip
      description: IP address of the server (IPv4 or IPv6).
      flat_name: server.ip
      level: core
      name: ip
      normalize: []
      short: IP address of the server.
      type: ip
    server.mac:
      dashed_name: server-mac
      description: 'MAC address of the server.

        The 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.'
      example: 00-00-5E-00-53-23
      flat_name: server.mac
      ignore_above: 1024
      level: core
      name: mac
      normalize: []
      short: MAC address of the server.
      type: keyword
    server.nat.ip:
      dashed_name: server-nat-ip
      description: 'Translated ip of destination based NAT sessions (e.g. internet
        to private DMZ)

        Typically used with load balancers, firewalls, or routers.'
      flat_name: server.nat.ip
      level: extended
      name: nat.ip
      normalize: []
      short: Server NAT ip
      type: ip
    server.nat.port:
      dashed_name: server-nat-port
      description: 'Translated port of destination based NAT sessions (e.g. internet
        to private DMZ)

        Typically used with load balancers, firewalls, or routers.'
      flat_name: server.nat.port
      format: string
      level: extended
      name: nat.port
      normalize: []
      short: Server NAT port
      type: long
    server.packets:
      dashed_name: server-packets
      description: Packets sent from the server to the client.
      example: 12
      flat_name: server.packets
      level: core
      name: packets
      normalize: []
      short: Packets sent from the server to the client.
      type: long
    server.port:
      dashed_name: server-port
      description: Port of the server.
      flat_name: server.port
      format: string
      level: core
      name: port
      normalize: []
      short: Port of the server.
      type: long
    server.registered_domain:
      dashed_name: server-registered-domain
      description: 'The highest registered server domain, stripped of the subdomain.

        For example, the registered domain for "foo.example.com" is "example.com".

        This value can be determined precisely with a list like the public suffix
        list (http://publicsuffix.org). Trying to approximate this by simply taking
        the last two labels will not work well for TLDs such as "co.uk".'
      example: example.com
      flat_name: server.registered_domain
      ignore_above: 1024
      level: extended
      name: registered_domain
      normalize: []
      short: The highest registered server domain, stripped of the subdomain.
      type: keyword
    server.subdomain:
      dashed_name: server-subdomain
      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.

        For example the subdomain portion of "www.east.mydomain.co.uk" is "east".
        If the domain has multiple levels of subdomain, such as "sub2.sub1.example.com",
        the subdomain field should contain "sub2.sub1", with no trailing period.'
      example: east
      flat_name: server.subdomain
      ignore_above: 1024
      level: extended
      name: subdomain
      normalize: []
      short: The subdomain of the domain.
      type: keyword
    server.top_level_domain:
      dashed_name: server-top-level-domain
      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".

        This value can be determined precisely with a list like the public suffix
        list (http://publicsuffix.org). Trying to approximate this by simply taking
        the last label will not work well for effective TLDs such as "co.uk".'
      example: co.uk
      flat_name: server.top_level_domain
      ignore_above: 1024
      level: extended
      name: top_level_domain
      normalize: []
      short: The effective top level domain (com, org, net, co.uk).
      type: keyword
    server.user.domain:
      dashed_name: server-user-domain
      description: 'Name of the directory the user is a member of.

        For example, an LDAP or Active Directory domain name.'
      flat_name: server.user.domain
      ignore_above: 1024
      level: extended
      name: domain
      normalize: []
      original_fieldset: user
      short: Name of the directory the user is a member of.
      type: keyword
    server.user.email:
      dashed_name: server-user-email
      description: User email address.
      flat_name: server.user.email
      ignore_above: 1024
      level: extended
      name: email
      normalize: []
      original_fieldset: user
      short: User email address.
      type: keyword
    server.user.extra:
      dashed_name: server-user-extra
      description: 'Additional information in key/value pairs.

        For additional information provided by the authenticator to events.

        Note: Not searchable or filterable.'
      enabled: false
      example: '{"authenticator": "ldap", "cipher": "argon2"}'
      flat_name: server.user.extra
      level: custom
      name: extra
      normalize: []
      object_type: keyword
      original_fieldset: user
      short: Custom key/value pairs.
      type: object
    server.user.full_name:
      dashed_name: server-user-full-name
      description: User's full name, if available.
      example: Albert Einstein
      flat_name: server.user.full_name
      ignore_above: 1024
      level: extended
      multi_fields:
      - flat_name: server.user.full_name.text
        name: text
        norms: false
        type: text
      name: full_name
      normalize: []
      original_fieldset: user
      short: User's full name, if available.
      type: keyword
    server.user.group.domain:
      dashed_name: server-user-group-domain
      description: 'Name of the directory the group is a member of.

        For example, an LDAP or Active Directory domain name.'
      flat_name: server.user.group.domain
      ignore_above: 1024
      level: extended
      name: domain
      normalize: []
      original_fieldset: group
      short: Name of the directory the group is a member of.
      type: keyword
    server.user.group.id:
      dashed_name: server-user-group-id
      description: Unique identifier for the group on the system/platform.
      flat_name: server.user.group.id
      ignore_above: 1024
      level: extended
      name: id
      normalize: []
      original_fieldset: group
      short: Unique identifier for the group on the system/platform.
      type: keyword
    server.user.group.name:
      dashed_name: server-user-group-name
      description: Name of the group.
      flat_name: server.user.group.name
      ignore_above: 1024
      level: extended
      name: name
      normalize: []
      original_fieldset: group
      short: Name of the group.
      type: keyword
    server.user.hash:
      dashed_name: server-user-hash
      description: 'Unique user hash to correlate information for a user in anonymized
        form.

        Useful if `user.id` or `user.name` contain confidential information and cannot
        be used.'
      flat_name: server.user.hash
      ignore_above: 1024
      level: extended
      name: hash
      normalize: []
      original_fieldset: user
      short: Unique user hash to correlate information for a user in anonymized form.
      type: keyword
    server.user.id:
      dashed_name: server-user-id
      description: Unique identifier of the user.
      flat_name: server.user.id
      ignore_above: 1024
      level: core
      name: id
      normalize: []
      original_fieldset: user
      short: Unique identifier of the user.
      type: keyword
    server.user.name:
      dashed_name: server-user-name
      description: Short name or login of the user.
      example: albert
      flat_name: server.user.name
      ignore_above: 1024
      level: core
      multi_fields:
      - flat_name: server.user.name.text
        name: text
        norms: false
        type: text
      name: name
      normalize: []
      original_fieldset: user
      short: Short name or login of the user.
      type: keyword
    server.user.roles:
      dashed_name: server-user-roles
      description: Array of user roles at the time of the event.
      example: '["kibana_admin", "reporting_user"]'
      flat_name: server.user.roles
      ignore_above: 1024
      level: extended
      name: roles
      normalize:
      - array
      original_fieldset: user
      short: Array of user roles at the time of the event.
      type: keyword
  group: 2
  name: server
  nestings:
  - server.as
  - server.geo
  - server.user
  prefix: server.
  reused_here:
  - full: server.as
    schema_name: as
    short: Fields describing an Autonomous System (Internet routing prefix).
  - full: server.geo
    schema_name: geo
    short: Fields describing a location.
  - full: server.user
    schema_name: user
    short: Fields to describe the user relevant to the event.
  short: Fields about the server side of a network connection, used with client.
  title: Server
  type: group
service:
  description: 'The service fields describe the service for or from which the data
    was collected.

    These fields help you find and correlate logs for a specific service and version.'
  fields:
    service.ephemeral_id:
      dashed_name: service-ephemeral-id
      description: 'Ephemeral identifier of this service (if one exists).

        This id normally changes across restarts, but `service.id` does not.'
      example: 8a4f500f
      flat_name: service.ephemeral_id
      ignore_above: 1024
      level: extended
      name: ephemeral_id
      normalize: []
      short: Ephemeral identifier of this service.
      type: keyword
    service.id:
      dashed_name: service-id
      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.

        This id should uniquely identify the service. This makes it possible to correlate
        logs and metrics for one specific service, no matter which particular node
        emitted the event.

        Note that if you need to see the events from one specific host of the service,
        you should filter on that `host.name` or `host.id` instead.'
      example: d37e5ebfe0ae6c4972dbe9f0174a1637bb8247f6
      flat_name: service.id
      ignore_above: 1024
      level: core
      name: id
      normalize: []
      short: Unique identifier of the running service.
      type: keyword
    service.name:
      dashed_name: service-name
      description: 'Name of the service data is collected from.

        The name of the service is normally user given. This allows for distributed
        services that run on multiple hosts to correlate the related instances based
        on the name.

        In the case of Elasticsearch the `service.name` could contain the cluster
        name. For Beats the `service.name` is by default a copy of the `service.type`
        field if no name is specified.'
      example: elasticsearch-metrics
      flat_name: service.name
      ignore_above: 1024
      level: core
      name: name
      normalize: []
      short: Name of the service.
      type: keyword
    service.node.name:
      dashed_name: service-node-name
      description: 'Name of a service node.

        This allows for two nodes of the same service running on the same host to
        be differentiated. Therefore, `service.node.name` should typically be unique
        across nodes of a given service.

        In the case of Elasticsearch, the `service.node.name` could contain the unique
        node name within the Elasticsearch cluster. In cases where the service doesn''t
        have the concept of a node name, the host name or container name can be used
        to distinguish running instances that make up this service. If those do not
        provide uniqueness (e.g. multiple instances of the service running on the
        same host) - the node name can be manually set.'
      example: instance-0000000016
      flat_name: service.node.name
      ignore_above: 1024
      level: extended
      name: node.name
      normalize: []
      short: Name of the service node.
      type: keyword
    service.state:
      dashed_name: service-state
      description: Current state of the service.
      flat_name: service.state
      ignore_above: 1024
      level: core
      name: state
      normalize: []
      short: Current state of the service.
      type: keyword
    service.type:
      dashed_name: service-type
      description: 'The type of the service data is collected from.

        The type can be used to group and correlate logs and metrics from one service
        type.

        Example: If logs or metrics are collected from Elasticsearch, `service.type`
        would be `elasticsearch`.'
      example: elasticsearch
      flat_name: service.type
      ignore_above: 1024
      level: core
      name: type
      normalize: []
      short: The type of the service.
      type: keyword
    service.version:
      dashed_name: service-version
      description: 'Version of the service the data was collected from.

        This allows to look at a data set only for a specific version of a service.'
      example: 3.2.4
      flat_name: service.version
      ignore_above: 1024
      level: core
      name: version
      normalize: []
      short: Version of the service.
      type: keyword
  group: 2
  name: service
  prefix: service.
  short: Fields describing the service for or from which the data was collected.
  title: Service
  type: group
source:
  description: 'Source fields capture details about the sender of a network exchange/packet.
    These fields are populated from a network event, packet, or other event containing
    details of a network transaction.

    Source fields are usually populated in conjunction with destination fields. The
    source and destination fields are considered the baseline and should always be
    filled if an event contains source and destination details from a network transaction.
    If the event also contains identification of the client and server roles, then
    the client and server fields should also be populated.'
  fields:
    source.address:
      dashed_name: source-address
      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.

        Then it should be duplicated to `.ip` or `.domain`, depending on which one
        it is.'
      flat_name: source.address
      ignore_above: 1024
      level: extended
      name: address
      normalize: []
      short: Source network address.
      type: keyword
    source.as.number:
      dashed_name: source-as-number
      description: Unique number allocated to the autonomous system. The autonomous
        system number (ASN) uniquely identifies each network on the Internet.
      example: 15169
      flat_name: source.as.number
      level: extended
      name: number
      normalize: []
      original_fieldset: as
      short: Unique number allocated to the autonomous system.
      type: long
    source.as.organization.name:
      dashed_name: source-as-organization-name
      description: Organization name.
      example: Google LLC
      flat_name: source.as.organization.name
      ignore_above: 1024
      level: extended
      multi_fields:
      - flat_name: source.as.organization.name.text
        name: text
        norms: false
        type: text
      name: organization.name
      normalize: []
      original_fieldset: as
      short: Organization name.
      type: keyword
    source.bytes:
      dashed_name: source-bytes
      description: Bytes sent from the source to the destination.
      example: 184
      flat_name: source.bytes
      format: bytes
      level: core
      name: bytes
      normalize: []
      short: Bytes sent from the source to the destination.
      type: long
    source.domain:
      dashed_name: source-domain
      description: Source domain.
      flat_name: source.domain
      ignore_above: 1024
      level: core
      name: domain
      normalize: []
      short: Source domain.
      type: keyword
    source.geo.city_name:
      dashed_name: source-geo-city-name
      description: City name.
      example: Montreal
      flat_name: source.geo.city_name
      ignore_above: 1024
      level: core
      name: city_name
      normalize: []
      original_fieldset: geo
      short: City name.
      type: keyword
    source.geo.continent_code:
      dashed_name: source-geo-continent-code
      description: Two-letter code representing continent's name.
      example: NA
      flat_name: source.geo.continent_code
      ignore_above: 1024
      level: core
      name: continent_code
      normalize: []
      original_fieldset: geo
      short: Continent code.
      type: keyword
    source.geo.continent_name:
      dashed_name: source-geo-continent-name
      description: Name of the continent.
      example: North America
      flat_name: source.geo.continent_name
      ignore_above: 1024
      level: core
      name: continent_name
      normalize: []
      original_fieldset: geo
      short: Name of the continent.
      type: keyword
    source.geo.country_iso_code:
      dashed_name: source-geo-country-iso-code
      description: Country ISO code.
      example: CA
      flat_name: source.geo.country_iso_code
      ignore_above: 1024
      level: core
      name: country_iso_code
      normalize: []
      original_fieldset: geo
      short: Country ISO code.
      type: keyword
    source.geo.country_name:
      dashed_name: source-geo-country-name
      description: Country name.
      example: Canada
      flat_name: source.geo.country_name
      ignore_above: 1024
      level: core
      name: country_name
      normalize: []
      original_fieldset: geo
      short: Country name.
      type: keyword
    source.geo.location:
      dashed_name: source-geo-location
      description: Longitude and latitude.
      example: '{ "lon": -73.614830, "lat": 45.505918 }'
      flat_name: source.geo.location
      level: core
      name: location
      normalize: []
      original_fieldset: geo
      short: Longitude and latitude.
      type: geo_point
    source.geo.name:
      dashed_name: source-geo-name
      description: 'User-defined description of a location, at the level of granularity
        they care about.

        Could be the name of their data centers, the floor number, if this describes
        a local physical entity, city names.

        Not typically used in automated geolocation.'
      example: boston-dc
      flat_name: source.geo.name
      ignore_above: 1024
      level: extended
      name: name
      normalize: []
      original_fieldset: geo
      short: User-defined description of a location.
      type: keyword
    source.geo.postal_code:
      dashed_name: source-geo-postal-code
      description: 'Postal code associated with the location.

        Values appropriate for this field may also be known as a postcode or ZIP code
        and will vary widely from country to country.'
      example: 94040
      flat_name: source.geo.postal_code
      ignore_above: 1024
      level: core
      name: postal_code
      normalize: []
      original_fieldset: geo
      short: Postal code.
      type: keyword
    source.geo.region_iso_code:
      dashed_name: source-geo-region-iso-code
      description: Region ISO code.
      example: CA-QC
      flat_name: source.geo.region_iso_code
      ignore_above: 1024
      level: core
      name: region_iso_code
      normalize: []
      original_fieldset: geo
      short: Region ISO code.
      type: keyword
    source.geo.region_name:
      dashed_name: source-geo-region-name
      description: Region name.
      example: Quebec
      flat_name: source.geo.region_name
      ignore_above: 1024
      level: core
      name: region_name
      normalize: []
      original_fieldset: geo
      short: Region name.
      type: keyword
    source.geo.timezone:
      dashed_name: source-geo-timezone
      description: The time zone of the location, such as IANA time zone name.
      example: America/Argentina/Buenos_Aires
      flat_name: source.geo.timezone
      ignore_above: 1024
      level: core
      name: timezone
      normalize: []
      original_fieldset: geo
      short: Time zone.
      type: keyword
    source.ip:
      dashed_name: source-ip
      description: IP address of the source (IPv4 or IPv6).
      flat_name: source.ip
      level: core
      name: ip
      normalize: []
      short: IP address of the source.
      type: ip
    source.mac:
      dashed_name: source-mac
      description: 'MAC address of the source.

        The 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.'
      example: 00-00-5E-00-53-23
      flat_name: source.mac
      ignore_above: 1024
      level: core
      name: mac
      normalize: []
      short: MAC address of the source.
      type: keyword
    source.nat.ip:
      dashed_name: source-nat-ip
      description: 'Translated ip of source based NAT sessions (e.g. internal client
        to internet)

        Typically connections traversing load balancers, firewalls, or routers.'
      flat_name: source.nat.ip
      level: extended
      name: nat.ip
      normalize: []
      short: Source NAT ip
      type: ip
    source.nat.port:
      dashed_name: source-nat-port
      description: 'Translated port of source based NAT sessions. (e.g. internal client
        to internet)

        Typically used with load balancers, firewalls, or routers.'
      flat_name: source.nat.port
      format: string
      level: extended
      name: nat.port
      normalize: []
      short: Source NAT port
      type: long
    source.packets:
      dashed_name: source-packets
      description: Packets sent from the source to the destination.
      example: 12
      flat_name: source.packets
      level: core
      name: packets
      normalize: []
      short: Packets sent from the source to the destination.
      type: long
    source.port:
      dashed_name: source-port
      description: Port of the source.
      flat_name: source.port
      format: string
      level: core
      name: port
      normalize: []
      short: Port of the source.
      type: long
    source.registered_domain:
      dashed_name: source-registered-domain
      description: 'The highest registered source domain, stripped of the subdomain.

        For example, the registered domain for "foo.example.com" is "example.com".

        This value can be determined precisely with a list like the public suffix
        list (http://publicsuffix.org). Trying to approximate this by simply taking
        the last two labels will not work well for TLDs such as "co.uk".'
      example: example.com
      flat_name: source.registered_domain
      ignore_above: 1024
      level: extended
      name: registered_domain
      normalize: []
      short: The highest registered source domain, stripped of the subdomain.
      type: keyword
    source.subdomain:
      dashed_name: source-subdomain
      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.

        For example the subdomain portion of "www.east.mydomain.co.uk" is "east".
        If the domain has multiple levels of subdomain, such as "sub2.sub1.example.com",
        the subdomain field should contain "sub2.sub1", with no trailing period.'
      example: east
      flat_name: source.subdomain
      ignore_above: 1024
      level: extended
      name: subdomain
      normalize: []
      short: The subdomain of the domain.
      type: keyword
    source.top_level_domain:
      dashed_name: source-top-level-domain
      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".

        This value can be determined precisely with a list like the public suffix
        list (http://publicsuffix.org). Trying to approximate this by simply taking
        the last label will not work well for effective TLDs such as "co.uk".'
      example: co.uk
      flat_name: source.top_level_domain
      ignore_above: 1024
      level: extended
      name: top_level_domain
      normalize: []
      short: The effective top level domain (com, org, net, co.uk).
      type: keyword
    source.user.domain:
      dashed_name: source-user-domain
      description: 'Name of the directory the user is a member of.

        For example, an LDAP or Active Directory domain name.'
      flat_name: source.user.domain
      ignore_above: 1024
      level: extended
      name: domain
      normalize: []
      original_fieldset: user
      short: Name of the directory the user is a member of.
      type: keyword
    source.user.email:
      dashed_name: source-user-email
      description: User email address.
      flat_name: source.user.email
      ignore_above: 1024
      level: extended
      name: email
      normalize: []
      original_fieldset: user
      short: User email address.
      type: keyword
    source.user.extra:
      dashed_name: source-user-extra
      description: 'Additional information in key/value pairs.

        For additional information provided by the authenticator to events.

        Note: Not searchable or filterable.'
      enabled: false
      example: '{"authenticator": "ldap", "cipher": "argon2"}'
      flat_name: source.user.extra
      level: custom
      name: extra
      normalize: []
      object_type: keyword
      original_fieldset: user
      short: Custom key/value pairs.
      type: object
    source.user.full_name:
      dashed_name: source-user-full-name
      description: User's full name, if available.
      example: Albert Einstein
      flat_name: source.user.full_name
      ignore_above: 1024
      level: extended
      multi_fields:
      - flat_name: source.user.full_name.text
        name: text
        norms: false
        type: text
      name: full_name
      normalize: []
      original_fieldset: user
      short: User's full name, if available.
      type: keyword
    source.user.group.domain:
      dashed_name: source-user-group-domain
      description: 'Name of the directory the group is a member of.

        For example, an LDAP or Active Directory domain name.'
      flat_name: source.user.group.domain
      ignore_above: 1024
      level: extended
      name: domain
      normalize: []
      original_fieldset: group
      short: Name of the directory the group is a member of.
      type: keyword
    source.user.group.id:
      dashed_name: source-user-group-id
      description: Unique identifier for the group on the system/platform.
      flat_name: source.user.group.id
      ignore_above: 1024
      level: extended
      name: id
      normalize: []
      original_fieldset: group
      short: Unique identifier for the group on the system/platform.
      type: keyword
    source.user.group.name:
      dashed_name: source-user-group-name
      description: Name of the group.
      flat_name: source.user.group.name
      ignore_above: 1024
      level: extended
      name: name
      normalize: []
      original_fieldset: group
      short: Name of the group.
      type: keyword
    source.user.hash:
      dashed_name: source-user-hash
      description: 'Unique user hash to correlate information for a user in anonymized
        form.

        Useful if `user.id` or `user.name` contain confidential information and cannot
        be used.'
      flat_name: source.user.hash
      ignore_above: 1024
      level: extended
      name: hash
      normalize: []
      original_fieldset: user
      short: Unique user hash to correlate information for a user in anonymized form.
      type: keyword
    source.user.id:
      dashed_name: source-user-id
      description: Unique identifier of the user.
      flat_name: source.user.id
      ignore_above: 1024
      level: core
      name: id
      normalize: []
      original_fieldset: user
      short: Unique identifier of the user.
      type: keyword
    source.user.name:
      dashed_name: source-user-name
      description: Short name or login of the user.
      example: albert
      flat_name: source.user.name
      ignore_above: 1024
      level: core
      multi_fields:
      - flat_name: source.user.name.text
        name: text
        norms: false
        type: text
      name: name
      normalize: []
      original_fieldset: user
      short: Short name or login of the user.
      type: keyword
    source.user.roles:
      dashed_name: source-user-roles
      description: Array of user roles at the time of the event.
      example: '["kibana_admin", "reporting_user"]'
      flat_name: source.user.roles
      ignore_above: 1024
      level: extended
      name: roles
      normalize:
      - array
      original_fieldset: user
      short: Array of user roles at the time of the event.
      type: keyword
  group: 2
  name: source
  nestings:
  - source.as
  - source.geo
  - source.user
  prefix: source.
  reused_here:
  - full: source.as
    schema_name: as
    short: Fields describing an Autonomous System (Internet routing prefix).
  - full: source.geo
    schema_name: geo
    short: Fields describing a location.
  - full: source.user
    schema_name: user
    short: Fields to describe the user relevant to the event.
  short: Fields about the source side of a network connection, used with destination.
  title: Source
  type: group
tls:
  description: Fields related to a TLS connection. These fields focus on the TLS protocol
    itself and intentionally avoids in-depth analysis of the related x.509 certificate
    files.
  fields:
    tls.cipher:
      dashed_name: tls-cipher
      description: String indicating the cipher used during the current connection.
      example: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256
      flat_name: tls.cipher
      ignore_above: 1024
      level: extended
      name: cipher
      normalize: []
      short: String indicating the cipher used during the current connection.
      type: keyword
    tls.client.certificate:
      dashed_name: tls-client-certificate
      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.
      example: MII...
      flat_name: tls.client.certificate
      ignore_above: 1024
      level: extended
      name: client.certificate
      normalize: []
      short: PEM-encoded stand-alone certificate offered by the client.
      type: keyword
    tls.client.certificate_chain:
      dashed_name: tls-client-certificate-chain
      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.
      example: '["MII...", "MII..."]'
      flat_name: tls.client.certificate_chain
      ignore_above: 1024
      level: extended
      name: client.certificate_chain
      normalize:
      - array
      short: Array of PEM-encoded certificates that make up the certificate chain
        offered by the client.
      type: keyword
    tls.client.hash.md5:
      dashed_name: tls-client-hash-md5
      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.
      example: 0F76C7F2C55BFD7D8E8B8F4BFBF0C9EC
      flat_name: tls.client.hash.md5
      ignore_above: 1024
      level: extended
      name: client.hash.md5
      normalize: []
      short: Certificate fingerprint using the MD5 digest of DER-encoded version of
        certificate offered by the client.
      type: keyword
    tls.client.hash.sha1:
      dashed_name: tls-client-hash-sha1
      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.
      example: 9E393D93138888D288266C2D915214D1D1CCEB2A
      flat_name: tls.client.hash.sha1
      ignore_above: 1024
      level: extended
      name: client.hash.sha1
      normalize: []
      short: Certificate fingerprint using the SHA1 digest of DER-encoded version
        of certificate offered by the client.
      type: keyword
    tls.client.hash.sha256:
      dashed_name: tls-client-hash-sha256
      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.
      example: 0687F666A054EF17A08E2F2162EAB4CBC0D265E1D7875BE74BF3C712CA92DAF0
      flat_name: tls.client.hash.sha256
      ignore_above: 1024
      level: extended
      name: client.hash.sha256
      normalize: []
      short: Certificate fingerprint using the SHA256 digest of DER-encoded version
        of certificate offered by the client.
      type: keyword
    tls.client.issuer:
      dashed_name: tls-client-issuer
      description: Distinguished name of subject of the issuer of the x.509 certificate
        presented by the client.
      example: CN=Example Root CA, OU=Infrastructure Team, DC=example, DC=com
      flat_name: tls.client.issuer
      ignore_above: 1024
      level: extended
      name: client.issuer
      normalize: []
      short: Distinguished name of subject of the issuer of the x.509 certificate
        presented by the client.
      type: keyword
    tls.client.ja3:
      dashed_name: tls-client-ja3
      description: A hash that identifies clients based on how they perform an SSL/TLS
        handshake.
      example: d4e5b18d6b55c71272893221c96ba240
      flat_name: tls.client.ja3
      ignore_above: 1024
      level: extended
      name: client.ja3
      normalize: []
      short: A hash that identifies clients based on how they perform an SSL/TLS handshake.
      type: keyword
    tls.client.not_after:
      dashed_name: tls-client-not-after
      description: Date/Time indicating when client certificate is no longer considered
        valid.
      example: '2021-01-01T00:00:00.000Z'
      flat_name: tls.client.not_after
      level: extended
      name: client.not_after
      normalize: []
      short: Date/Time indicating when client certificate is no longer considered
        valid.
      type: date
    tls.client.not_before:
      dashed_name: tls-client-not-before
      description: Date/Time indicating when client certificate is first considered
        valid.
      example: '1970-01-01T00:00:00.000Z'
      flat_name: tls.client.not_before
      level: extended
      name: client.not_before
      normalize: []
      short: Date/Time indicating when client certificate is first considered valid.
      type: date
    tls.client.server_name:
      dashed_name: tls-client-server-name
      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`.
      example: www.elastic.co
      flat_name: tls.client.server_name
      ignore_above: 1024
      level: extended
      name: client.server_name
      normalize: []
      short: Hostname the client is trying to connect to. Also called the SNI.
      type: keyword
    tls.client.subject:
      dashed_name: tls-client-subject
      description: Distinguished name of subject of the x.509 certificate presented
        by the client.
      example: CN=myclient, OU=Documentation Team, DC=example, DC=com
      flat_name: tls.client.subject
      ignore_above: 1024
      level: extended
      name: client.subject
      normalize: []
      short: Distinguished name of subject of the x.509 certificate presented by the
        client.
      type: keyword
    tls.client.supported_ciphers:
      dashed_name: tls-client-supported-ciphers
      description: Array of ciphers offered by the client during the client hello.
      example: '["TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384", "TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384",
        "..."]'
      flat_name: tls.client.supported_ciphers
      ignore_above: 1024
      level: extended
      name: client.supported_ciphers
      normalize:
      - array
      short: Array of ciphers offered by the client during the client hello.
      type: keyword
    tls.client.x509.alternative_names:
      dashed_name: tls-client-x509-alternative-names
      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.
      example: '*.elastic.co'
      flat_name: tls.client.x509.alternative_names
      ignore_above: 1024
      level: extended
      name: alternative_names
      normalize:
      - array
      original_fieldset: x509
      short: List of subject alternative names (SAN).
      type: keyword
    tls.client.x509.issuer.common_name:
      dashed_name: tls-client-x509-issuer-common-name
      description: List of common name (CN) of issuing certificate authority.
      example: Example SHA2 High Assurance Server CA
      flat_name: tls.client.x509.issuer.common_name
      ignore_above: 1024
      level: extended
      name: issuer.common_name
      normalize:
      - array
      original_fieldset: x509
      short: List of common name (CN) of issuing certificate authority.
      type: keyword
    tls.client.x509.issuer.country:
      dashed_name: tls-client-x509-issuer-country
      description: List of country (C) codes
      example: US
      flat_name: tls.client.x509.issuer.country
      ignore_above: 1024
      level: extended
      name: issuer.country
      normalize:
      - array
      original_fieldset: x509
      short: List of country (C) codes
      type: keyword
    tls.client.x509.issuer.distinguished_name:
      dashed_name: tls-client-x509-issuer-distinguished-name
      description: Distinguished name (DN) of issuing certificate authority.
      example: C=US, O=Example Inc, OU=www.example.com, CN=Example SHA2 High Assurance
        Server CA
      flat_name: tls.client.x509.issuer.distinguished_name
      ignore_above: 1024
      level: extended
      name: issuer.distinguished_name
      normalize: []
      original_fieldset: x509
      short: Distinguished name (DN) of issuing certificate authority.
      type: keyword
    tls.client.x509.issuer.locality:
      dashed_name: tls-client-x509-issuer-locality
      description: List of locality names (L)
      example: Mountain View
      flat_name: tls.client.x509.issuer.locality
      ignore_above: 1024
      level: extended
      name: issuer.locality
      normalize:
      - array
      original_fieldset: x509
      short: List of locality names (L)
      type: keyword
    tls.client.x509.issuer.organization:
      dashed_name: tls-client-x509-issuer-organization
      description: List of organizations (O) of issuing certificate authority.
      example: Example Inc
      flat_name: tls.client.x509.issuer.organization
      ignore_above: 1024
      level: extended
      name: issuer.organization
      normalize:
      - array
      original_fieldset: x509
      short: List of organizations (O) of issuing certificate authority.
      type: keyword
    tls.client.x509.issuer.organizational_unit:
      dashed_name: tls-client-x509-issuer-organizational-unit
      description: List of organizational units (OU) of issuing certificate authority.
      example: www.example.com
      flat_name: tls.client.x509.issuer.organizational_unit
      ignore_above: 1024
      level: extended
      name: issuer.organizational_unit
      normalize:
      - array
      original_fieldset: x509
      short: List of organizational units (OU) of issuing certificate authority.
      type: keyword
    tls.client.x509.issuer.state_or_province:
      dashed_name: tls-client-x509-issuer-state-or-province
      description: List of state or province names (ST, S, or P)
      example: California
      flat_name: tls.client.x509.issuer.state_or_province
      ignore_above: 1024
      level: extended
      name: issuer.state_or_province
      normalize:
      - array
      original_fieldset: x509
      short: List of state or province names (ST, S, or P)
      type: keyword
    tls.client.x509.not_after:
      dashed_name: tls-client-x509-not-after
      description: Time at which the certificate is no longer considered valid.
      example: 2020-07-16 03:15:39
      flat_name: tls.client.x509.not_after
      level: extended
      name: not_after
      normalize: []
      original_fieldset: x509
      short: Time at which the certificate is no longer considered valid.
      type: date
    tls.client.x509.not_before:
      dashed_name: tls-client-x509-not-before
      description: Time at which the certificate is first considered valid.
      example: 2019-08-16 01:40:25
      flat_name: tls.client.x509.not_before
      level: extended
      name: not_before
      normalize: []
      original_fieldset: x509
      short: Time at which the certificate is first considered valid.
      type: date
    tls.client.x509.public_key_algorithm:
      dashed_name: tls-client-x509-public-key-algorithm
      description: Algorithm used to generate the public key.
      example: RSA
      flat_name: tls.client.x509.public_key_algorithm
      ignore_above: 1024
      level: extended
      name: public_key_algorithm
      normalize: []
      original_fieldset: x509
      short: Algorithm used to generate the public key.
      type: keyword
    tls.client.x509.public_key_curve:
      dashed_name: tls-client-x509-public-key-curve
      description: The curve used by the elliptic curve public key algorithm. This
        is algorithm specific.
      example: nistp521
      flat_name: tls.client.x509.public_key_curve
      ignore_above: 1024
      level: extended
      name: public_key_curve
      normalize: []
      original_fieldset: x509
      short: The curve used by the elliptic curve public key algorithm. This is algorithm
        specific.
      type: keyword
    tls.client.x509.public_key_exponent:
      dashed_name: tls-client-x509-public-key-exponent
      description: Exponent used to derive the public key. This is algorithm specific.
      doc_values: false
      example: 65537
      flat_name: tls.client.x509.public_key_exponent
      index: false
      level: extended
      name: public_key_exponent
      normalize: []
      original_fieldset: x509
      short: Exponent used to derive the public key. This is algorithm specific.
      type: long
    tls.client.x509.public_key_size:
      dashed_name: tls-client-x509-public-key-size
      description: The size of the public key space in bits.
      example: 2048
      flat_name: tls.client.x509.public_key_size
      level: extended
      name: public_key_size
      normalize: []
      original_fieldset: x509
      short: The size of the public key space in bits.
      type: long
    tls.client.x509.serial_number:
      dashed_name: tls-client-x509-serial-number
      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.
      example: 55FBB9C7DEBF09809D12CCAA
      flat_name: tls.client.x509.serial_number
      ignore_above: 1024
      level: extended
      name: serial_number
      normalize: []
      original_fieldset: x509
      short: Unique serial number issued by the certificate authority.
      type: keyword
    tls.client.x509.signature_algorithm:
      dashed_name: tls-client-x509-signature-algorithm
      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.
      example: SHA256-RSA
      flat_name: tls.client.x509.signature_algorithm
      ignore_above: 1024
      level: extended
      name: signature_algorithm
      normalize: []
      original_fieldset: x509
      short: Identifier for certificate signature algorithm.
      type: keyword
    tls.client.x509.subject.common_name:
      dashed_name: tls-client-x509-subject-common-name
      description: List of common names (CN) of subject.
      example: shared.global.example.net
      flat_name: tls.client.x509.subject.common_name
      ignore_above: 1024
      level: extended
      name: subject.common_name
      normalize:
      - array
      original_fieldset: x509
      short: List of common names (CN) of subject.
      type: keyword
    tls.client.x509.subject.country:
      dashed_name: tls-client-x509-subject-country
      description: List of country (C) code
      example: US
      flat_name: tls.client.x509.subject.country
      ignore_above: 1024
      level: extended
      name: subject.country
      normalize:
      - array
      original_fieldset: x509
      short: List of country (C) code
      type: keyword
    tls.client.x509.subject.distinguished_name:
      dashed_name: tls-client-x509-subject-distinguished-name
      description: Distinguished name (DN) of the certificate subject entity.
      example: C=US, ST=California, L=San Francisco, O=Example, Inc., CN=shared.global.example.net
      flat_name: tls.client.x509.subject.distinguished_name
      ignore_above: 1024
      level: extended
      name: subject.distinguished_name
      normalize: []
      original_fieldset: x509
      short: Distinguished name (DN) of the certificate subject entity.
      type: keyword
    tls.client.x509.subject.locality:
      dashed_name: tls-client-x509-subject-locality
      description: List of locality names (L)
      example: San Francisco
      flat_name: tls.client.x509.subject.locality
      ignore_above: 1024
      level: extended
      name: subject.locality
      normalize:
      - array
      original_fieldset: x509
      short: List of locality names (L)
      type: keyword
    tls.client.x509.subject.organization:
      dashed_name: tls-client-x509-subject-organization
      description: List of organizations (O) of subject.
      example: Example, Inc.
      flat_name: tls.client.x509.subject.organization
      ignore_above: 1024
      level: extended
      name: subject.organization
      normalize:
      - array
      original_fieldset: x509
      short: List of organizations (O) of subject.
      type: keyword
    tls.client.x509.subject.organizational_unit:
      dashed_name: tls-client-x509-subject-organizational-unit
      description: List of organizational units (OU) of subject.
      flat_name: tls.client.x509.subject.organizational_unit
      ignore_above: 1024
      level: extended
      name: subject.organizational_unit
      normalize:
      - array
      original_fieldset: x509
      short: List of organizational units (OU) of subject.
      type: keyword
    tls.client.x509.subject.state_or_province:
      dashed_name: tls-client-x509-subject-state-or-province
      description: List of state or province names (ST, S, or P)
      example: California
      flat_name: tls.client.x509.subject.state_or_province
      ignore_above: 1024
      level: extended
      name: subject.state_or_province
      normalize:
      - array
      original_fieldset: x509
      short: List of state or province names (ST, S, or P)
      type: keyword
    tls.client.x509.version_number:
      dashed_name: tls-client-x509-version-number
      description: Version of x509 format.
      example: 3
      flat_name: tls.client.x509.version_number
      ignore_above: 1024
      level: extended
      name: version_number
      normalize: []
      original_fieldset: x509
      short: Version of x509 format.
      type: keyword
    tls.curve:
      dashed_name: tls-curve
      description: String indicating the curve used for the given cipher, when applicable.
      example: secp256r1
      flat_name: tls.curve
      ignore_above: 1024
      level: extended
      name: curve
      normalize: []
      short: String indicating the curve used for the given cipher, when applicable.
      type: keyword
    tls.established:
      dashed_name: tls-established
      description: Boolean flag indicating if the TLS negotiation was successful and
        transitioned to an encrypted tunnel.
      flat_name: tls.established
      level: extended
      name: established
      normalize: []
      short: Boolean flag indicating if the TLS negotiation was successful and transitioned
        to an encrypted tunnel.
      type: boolean
    tls.next_protocol:
      dashed_name: tls-next-protocol
      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.
      example: http/1.1
      flat_name: tls.next_protocol
      ignore_above: 1024
      level: extended
      name: next_protocol
      normalize: []
      short: String indicating the protocol being tunneled.
      type: keyword
    tls.resumed:
      dashed_name: tls-resumed
      description: Boolean flag indicating if this TLS connection was resumed from
        an existing TLS negotiation.
      flat_name: tls.resumed
      level: extended
      name: resumed
      normalize: []
      short: Boolean flag indicating if this TLS connection was resumed from an existing
        TLS negotiation.
      type: boolean
    tls.server.certificate:
      dashed_name: tls-server-certificate
      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.
      example: MII...
      flat_name: tls.server.certificate
      ignore_above: 1024
      level: extended
      name: server.certificate
      normalize: []
      short: PEM-encoded stand-alone certificate offered by the server.
      type: keyword
    tls.server.certificate_chain:
      dashed_name: tls-server-certificate-chain
      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.
      example: '["MII...", "MII..."]'
      flat_name: tls.server.certificate_chain
      ignore_above: 1024
      level: extended
      name: server.certificate_chain
      normalize:
      - array
      short: Array of PEM-encoded certificates that make up the certificate chain
        offered by the server.
      type: keyword
    tls.server.hash.md5:
      dashed_name: tls-server-hash-md5
      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.
      example: 0F76C7F2C55BFD7D8E8B8F4BFBF0C9EC
      flat_name: tls.server.hash.md5
      ignore_above: 1024
      level: extended
      name: server.hash.md5
      normalize: []
      short: Certificate fingerprint using the MD5 digest of DER-encoded version of
        certificate offered by the server.
      type: keyword
    tls.server.hash.sha1:
      dashed_name: tls-server-hash-sha1
      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.
      example: 9E393D93138888D288266C2D915214D1D1CCEB2A
      flat_name: tls.server.hash.sha1
      ignore_above: 1024
      level: extended
      name: server.hash.sha1
      normalize: []
      short: Certificate fingerprint using the SHA1 digest of DER-encoded version
        of certificate offered by the server.
      type: keyword
    tls.server.hash.sha256:
      dashed_name: tls-server-hash-sha256
      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.
      example: 0687F666A054EF17A08E2F2162EAB4CBC0D265E1D7875BE74BF3C712CA92DAF0
      flat_name: tls.server.hash.sha256
      ignore_above: 1024
      level: extended
      name: server.hash.sha256
      normalize: []
      short: Certificate fingerprint using the SHA256 digest of DER-encoded version
        of certificate offered by the server.
      type: keyword
    tls.server.issuer:
      dashed_name: tls-server-issuer
      description: Subject of the issuer of the x.509 certificate presented by the
        server.
      example: CN=Example Root CA, OU=Infrastructure Team, DC=example, DC=com
      flat_name: tls.server.issuer
      ignore_above: 1024
      level: extended
      name: server.issuer
      normalize: []
      short: Subject of the issuer of the x.509 certificate presented by the server.
      type: keyword
    tls.server.ja3s:
      dashed_name: tls-server-ja3s
      description: A hash that identifies servers based on how they perform an SSL/TLS
        handshake.
      example: 394441ab65754e2207b1e1b457b3641d
      flat_name: tls.server.ja3s
      ignore_above: 1024
      level: extended
      name: server.ja3s
      normalize: []
      short: A hash that identifies servers based on how they perform an SSL/TLS handshake.
      type: keyword
    tls.server.not_after:
      dashed_name: tls-server-not-after
      description: Timestamp indicating when server certificate is no longer considered
        valid.
      example: '2021-01-01T00:00:00.000Z'
      flat_name: tls.server.not_after
      level: extended
      name: server.not_after
      normalize: []
      short: Timestamp indicating when server certificate is no longer considered
        valid.
      type: date
    tls.server.not_before:
      dashed_name: tls-server-not-before
      description: Timestamp indicating when server certificate is first considered
        valid.
      example: '1970-01-01T00:00:00.000Z'
      flat_name: tls.server.not_before
      level: extended
      name: server.not_before
      normalize: []
      short: Timestamp indicating when server certificate is first considered valid.
      type: date
    tls.server.subject:
      dashed_name: tls-server-subject
      description: Subject of the x.509 certificate presented by the server.
      example: CN=www.example.com, OU=Infrastructure Team, DC=example, DC=com
      flat_name: tls.server.subject
      ignore_above: 1024
      level: extended
      name: server.subject
      normalize: []
      short: Subject of the x.509 certificate presented by the server.
      type: keyword
    tls.server.x509.alternative_names:
      dashed_name: tls-server-x509-alternative-names
      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.
      example: '*.elastic.co'
      flat_name: tls.server.x509.alternative_names
      ignore_above: 1024
      level: extended
      name: alternative_names
      normalize:
      - array
      original_fieldset: x509
      short: List of subject alternative names (SAN).
      type: keyword
    tls.server.x509.issuer.common_name:
      dashed_name: tls-server-x509-issuer-common-name
      description: List of common name (CN) of issuing certificate authority.
      example: Example SHA2 High Assurance Server CA
      flat_name: tls.server.x509.issuer.common_name
      ignore_above: 1024
      level: extended
      name: issuer.common_name
      normalize:
      - array
      original_fieldset: x509
      short: List of common name (CN) of issuing certificate authority.
      type: keyword
    tls.server.x509.issuer.country:
      dashed_name: tls-server-x509-issuer-country
      description: List of country (C) codes
      example: US
      flat_name: tls.server.x509.issuer.country
      ignore_above: 1024
      level: extended
      name: issuer.country
      normalize:
      - array
      original_fieldset: x509
      short: List of country (C) codes
      type: keyword
    tls.server.x509.issuer.distinguished_name:
      dashed_name: tls-server-x509-issuer-distinguished-name
      description: Distinguished name (DN) of issuing certificate authority.
      example: C=US, O=Example Inc, OU=www.example.com, CN=Example SHA2 High Assurance
        Server CA
      flat_name: tls.server.x509.issuer.distinguished_name
      ignore_above: 1024
      level: extended
      name: issuer.distinguished_name
      normalize: []
      original_fieldset: x509
      short: Distinguished name (DN) of issuing certificate authority.
      type: keyword
    tls.server.x509.issuer.locality:
      dashed_name: tls-server-x509-issuer-locality
      description: List of locality names (L)
      example: Mountain View
      flat_name: tls.server.x509.issuer.locality
      ignore_above: 1024
      level: extended
      name: issuer.locality
      normalize:
      - array
      original_fieldset: x509
      short: List of locality names (L)
      type: keyword
    tls.server.x509.issuer.organization:
      dashed_name: tls-server-x509-issuer-organization
      description: List of organizations (O) of issuing certificate authority.
      example: Example Inc
      flat_name: tls.server.x509.issuer.organization
      ignore_above: 1024
      level: extended
      name: issuer.organization
      normalize:
      - array
      original_fieldset: x509
      short: List of organizations (O) of issuing certificate authority.
      type: keyword
    tls.server.x509.issuer.organizational_unit:
      dashed_name: tls-server-x509-issuer-organizational-unit
      description: List of organizational units (OU) of issuing certificate authority.
      example: www.example.com
      flat_name: tls.server.x509.issuer.organizational_unit
      ignore_above: 1024
      level: extended
      name: issuer.organizational_unit
      normalize:
      - array
      original_fieldset: x509
      short: List of organizational units (OU) of issuing certificate authority.
      type: keyword
    tls.server.x509.issuer.state_or_province:
      dashed_name: tls-server-x509-issuer-state-or-province
      description: List of state or province names (ST, S, or P)
      example: California
      flat_name: tls.server.x509.issuer.state_or_province
      ignore_above: 1024
      level: extended
      name: issuer.state_or_province
      normalize:
      - array
      original_fieldset: x509
      short: List of state or province names (ST, S, or P)
      type: keyword
    tls.server.x509.not_after:
      dashed_name: tls-server-x509-not-after
      description: Time at which the certificate is no longer considered valid.
      example: 2020-07-16 03:15:39
      flat_name: tls.server.x509.not_after
      level: extended
      name: not_after
      normalize: []
      original_fieldset: x509
      short: Time at which the certificate is no longer considered valid.
      type: date
    tls.server.x509.not_before:
      dashed_name: tls-server-x509-not-before
      description: Time at which the certificate is first considered valid.
      example: 2019-08-16 01:40:25
      flat_name: tls.server.x509.not_before
      level: extended
      name: not_before
      normalize: []
      original_fieldset: x509
      short: Time at which the certificate is first considered valid.
      type: date
    tls.server.x509.public_key_algorithm:
      dashed_name: tls-server-x509-public-key-algorithm
      description: Algorithm used to generate the public key.
      example: RSA
      flat_name: tls.server.x509.public_key_algorithm
      ignore_above: 1024
      level: extended
      name: public_key_algorithm
      normalize: []
      original_fieldset: x509
      short: Algorithm used to generate the public key.
      type: keyword
    tls.server.x509.public_key_curve:
      dashed_name: tls-server-x509-public-key-curve
      description: The curve used by the elliptic curve public key algorithm. This
        is algorithm specific.
      example: nistp521
      flat_name: tls.server.x509.public_key_curve
      ignore_above: 1024
      level: extended
      name: public_key_curve
      normalize: []
      original_fieldset: x509
      short: The curve used by the elliptic curve public key algorithm. This is algorithm
        specific.
      type: keyword
    tls.server.x509.public_key_exponent:
      dashed_name: tls-server-x509-public-key-exponent
      description: Exponent used to derive the public key. This is algorithm specific.
      doc_values: false
      example: 65537
      flat_name: tls.server.x509.public_key_exponent
      index: false
      level: extended
      name: public_key_exponent
      normalize: []
      original_fieldset: x509
      short: Exponent used to derive the public key. This is algorithm specific.
      type: long
    tls.server.x509.public_key_size:
      dashed_name: tls-server-x509-public-key-size
      description: The size of the public key space in bits.
      example: 2048
      flat_name: tls.server.x509.public_key_size
      level: extended
      name: public_key_size
      normalize: []
      original_fieldset: x509
      short: The size of the public key space in bits.
      type: long
    tls.server.x509.serial_number:
      dashed_name: tls-server-x509-serial-number
      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.
      example: 55FBB9C7DEBF09809D12CCAA
      flat_name: tls.server.x509.serial_number
      ignore_above: 1024
      level: extended
      name: serial_number
      normalize: []
      original_fieldset: x509
      short: Unique serial number issued by the certificate authority.
      type: keyword
    tls.server.x509.signature_algorithm:
      dashed_name: tls-server-x509-signature-algorithm
      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.
      example: SHA256-RSA
      flat_name: tls.server.x509.signature_algorithm
      ignore_above: 1024
      level: extended
      name: signature_algorithm
      normalize: []
      original_fieldset: x509
      short: Identifier for certificate signature algorithm.
      type: keyword
    tls.server.x509.subject.common_name:
      dashed_name: tls-server-x509-subject-common-name
      description: List of common names (CN) of subject.
      example: shared.global.example.net
      flat_name: tls.server.x509.subject.common_name
      ignore_above: 1024
      level: extended
      name: subject.common_name
      normalize:
      - array
      original_fieldset: x509
      short: List of common names (CN) of subject.
      type: keyword
    tls.server.x509.subject.country:
      dashed_name: tls-server-x509-subject-country
      description: List of country (C) code
      example: US
      flat_name: tls.server.x509.subject.country
      ignore_above: 1024
      level: extended
      name: subject.country
      normalize:
      - array
      original_fieldset: x509
      short: List of country (C) code
      type: keyword
    tls.server.x509.subject.distinguished_name:
      dashed_name: tls-server-x509-subject-distinguished-name
      description: Distinguished name (DN) of the certificate subject entity.
      example: C=US, ST=California, L=San Francisco, O=Example, Inc., CN=shared.global.example.net
      flat_name: tls.server.x509.subject.distinguished_name
      ignore_above: 1024
      level: extended
      name: subject.distinguished_name
      normalize: []
      original_fieldset: x509
      short: Distinguished name (DN) of the certificate subject entity.
      type: keyword
    tls.server.x509.subject.locality:
      dashed_name: tls-server-x509-subject-locality
      description: List of locality names (L)
      example: San Francisco
      flat_name: tls.server.x509.subject.locality
      ignore_above: 1024
      level: extended
      name: subject.locality
      normalize:
      - array
      original_fieldset: x509
      short: List of locality names (L)
      type: keyword
    tls.server.x509.subject.organization:
      dashed_name: tls-server-x509-subject-organization
      description: List of organizations (O) of subject.
      example: Example, Inc.
      flat_name: tls.server.x509.subject.organization
      ignore_above: 1024
      level: extended
      name: subject.organization
      normalize:
      - array
      original_fieldset: x509
      short: List of organizations (O) of subject.
      type: keyword
    tls.server.x509.subject.organizational_unit:
      dashed_name: tls-server-x509-subject-organizational-unit
      description: List of organizational units (OU) of subject.
      flat_name: tls.server.x509.subject.organizational_unit
      ignore_above: 1024
      level: extended
      name: subject.organizational_unit
      normalize:
      - array
      original_fieldset: x509
      short: List of organizational units (OU) of subject.
      type: keyword
    tls.server.x509.subject.state_or_province:
      dashed_name: tls-server-x509-subject-state-or-province
      description: List of state or province names (ST, S, or P)
      example: California
      flat_name: tls.server.x509.subject.state_or_province
      ignore_above: 1024
      level: extended
      name: subject.state_or_province
      normalize:
      - array
      original_fieldset: x509
      short: List of state or province names (ST, S, or P)
      type: keyword
    tls.server.x509.version_number:
      dashed_name: tls-server-x509-version-number
      description: Version of x509 format.
      example: 3
      flat_name: tls.server.x509.version_number
      ignore_above: 1024
      level: extended
      name: version_number
      normalize: []
      original_fieldset: x509
      short: Version of x509 format.
      type: keyword
    tls.version:
      dashed_name: tls-version
      description: Numeric part of the version parsed from the original string.
      example: '1.2'
      flat_name: tls.version
      ignore_above: 1024
      level: extended
      name: version
      normalize: []
      short: Numeric part of the version parsed from the original string.
      type: keyword
    tls.version_protocol:
      dashed_name: tls-version-protocol
      description: Normalized lowercase protocol name parsed from original string.
      example: tls
      flat_name: tls.version_protocol
      ignore_above: 1024
      level: extended
      name: version_protocol
      normalize: []
      short: Normalized lowercase protocol name parsed from original string.
      type: keyword
  group: 2
  name: tls
  nestings:
  - tls.client.x509
  - tls.server.x509
  prefix: tls.
  reused_here:
  - full: tls.client.x509
    schema_name: x509
    short: These fields contain x509 certificate metadata.
  - full: tls.server.x509
    schema_name: x509
    short: These fields contain x509 certificate metadata.
  short: Fields describing a TLS connection.
  title: TLS
  type: group
tracing:
  description: 'Distributed tracing makes it possible to analyze performance throughout
    a microservice architecture all in one view. This is accomplished by tracing all
    of the requests - from the initial web request in the front-end service - to queries
    made through multiple back-end services.

    Unlike most field sets in ECS, the tracing fields are *not* nested under the field
    set name. In other words, the correct field name is `trace.id`, not `tracing.trace.id`,
    and so on.'
  fields:
    span.id:
      dashed_name: span-id
      description: 'Unique identifier of the span within the scope of its trace.

        A span represents an operation within a transaction, such as a request to
        another service, or a database query.'
      example: 3ff9a8981b7ccd5a
      flat_name: span.id
      ignore_above: 1024
      level: extended
      name: span.id
      normalize: []
      short: Unique identifier of the span within the scope of its trace.
      type: keyword
    trace.id:
      dashed_name: trace-id
      description: 'Unique identifier of the trace.

        A trace groups multiple events like transactions that belong together. For
        example, a user request handled by multiple inter-connected services.'
      example: 4bf92f3577b34da6a3ce929d0e0e4736
      flat_name: trace.id
      ignore_above: 1024
      level: extended
      name: trace.id
      normalize: []
      short: Unique identifier of the trace.
      type: keyword
    transaction.id:
      dashed_name: transaction-id
      description: 'Unique identifier of the transaction within the scope of its trace.

        A transaction is the highest level of work measured within a service, such
        as a request to a server.'
      example: 00f067aa0ba902b7
      flat_name: transaction.id
      ignore_above: 1024
      level: extended
      name: transaction.id
      normalize: []
      short: Unique identifier of the transaction within the scope of its trace.
      type: keyword
  group: 2
  name: tracing
  prefix: ''
  root: true
  short: Fields related to distributed tracing.
  title: Tracing
  type: group
url:
  description: URL fields provide support for complete or partial URLs, and supports
    the breaking down into scheme, domain, path, and so on.
  fields:
    url.domain:
      dashed_name: url-domain
      description: 'Domain of the url, such as "www.elastic.co".

        In some cases a URL may refer to an IP and/or port directly, without a domain
        name. In this case, the IP address would go to the `domain` field.

        If the URL contains a literal IPv6 address enclosed by `[` and `]` (IETF RFC
        2732), the `[` and `]` characters should also be captured in the `domain`
        field.'
      example: www.elastic.co
      flat_name: url.domain
      ignore_above: 1024
      level: extended
      name: domain
      normalize: []
      short: Domain of the url.
      type: keyword
    url.extension:
      dashed_name: url-extension
      description: 'The field contains the file extension from the original request
        url, excluding the leading dot.

        The file extension is only set if it exists, as not every url has a file extension.

        The leading period must not be included. For example, the value must be "png",
        not ".png".

        Note that when the file name has multiple extensions (example.tar.gz), only
        the last one should be captured ("gz", not "tar.gz").'
      example: png
      flat_name: url.extension
      ignore_above: 1024
      level: extended
      name: extension
      normalize: []
      short: File extension from the request url, excluding the leading dot.
      type: keyword
    url.fragment:
      dashed_name: url-fragment
      description: 'Portion of the url after the `#`, such as "top".

        The `#` is not part of the fragment.'
      flat_name: url.fragment
      ignore_above: 1024
      level: extended
      name: fragment
      normalize: []
      short: Portion of the url after the `#`.
      type: keyword
    url.full:
      dashed_name: url-full
      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.
      example: https://www.elastic.co:443/search?q=elasticsearch#top
      flat_name: url.full
      ignore_above: 1024
      level: extended
      multi_fields:
      - flat_name: url.full.text
        name: text
        norms: false
        type: text
      name: full
      normalize: []
      short: Full unparsed URL.
      type: keyword
    url.original:
      dashed_name: url-original
      description: 'Unmodified original url as seen in the event source.

        Note that in network monitoring, the observed URL may be a full URL, whereas
        in access logs, the URL is often just represented as a path.

        This field is meant to represent the URL as it was observed, complete or not.'
      example: https://www.elastic.co:443/search?q=elasticsearch#top or /search?q=elasticsearch
      flat_name: url.original
      ignore_above: 1024
      level: extended
      multi_fields:
      - flat_name: url.original.text
        name: text
        norms: false
        type: text
      name: original
      normalize: []
      short: Unmodified original url as seen in the event source.
      type: keyword
    url.password:
      dashed_name: url-password
      description: Password of the request.
      flat_name: url.password
      ignore_above: 1024
      level: extended
      name: password
      normalize: []
      short: Password of the request.
      type: keyword
    url.path:
      dashed_name: url-path
      description: Path of the request, such as "/search".
      flat_name: url.path
      ignore_above: 1024
      level: extended
      name: path
      normalize: []
      short: Path of the request, such as "/search".
      type: keyword
    url.port:
      dashed_name: url-port
      description: Port of the request, such as 443.
      example: 443
      flat_name: url.port
      format: string
      level: extended
      name: port
      normalize: []
      short: Port of the request, such as 443.
      type: long
    url.query:
      dashed_name: url-query
      description: 'The query field describes the query string of the request, such
        as "q=elasticsearch".

        The `?` is excluded from the query string. If a URL contains no `?`, there
        is no query field. If there is a `?` but no query, the query field exists
        with an empty string. The `exists` query can be used to differentiate between
        the two cases.'
      flat_name: url.query
      ignore_above: 1024
      level: extended
      name: query
      normalize: []
      short: Query string of the request.
      type: keyword
    url.registered_domain:
      dashed_name: url-registered-domain
      description: 'The highest registered url domain, stripped of the subdomain.

        For example, the registered domain for "foo.example.com" is "example.com".

        This value can be determined precisely with a list like the public suffix
        list (http://publicsuffix.org). Trying to approximate this by simply taking
        the last two labels will not work well for TLDs such as "co.uk".'
      example: example.com
      flat_name: url.registered_domain
      ignore_above: 1024
      level: extended
      name: registered_domain
      normalize: []
      short: The highest registered url domain, stripped of the subdomain.
      type: keyword
    url.scheme:
      dashed_name: url-scheme
      description: 'Scheme of the request, such as "https".

        Note: The `:` is not part of the scheme.'
      example: https
      flat_name: url.scheme
      ignore_above: 1024
      level: extended
      name: scheme
      normalize: []
      short: Scheme of the url.
      type: keyword
    url.subdomain:
      dashed_name: url-subdomain
      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.

        For example the subdomain portion of "www.east.mydomain.co.uk" is "east".
        If the domain has multiple levels of subdomain, such as "sub2.sub1.example.com",
        the subdomain field should contain "sub2.sub1", with no trailing period.'
      example: east
      flat_name: url.subdomain
      ignore_above: 1024
      level: extended
      name: subdomain
      normalize: []
      short: The subdomain of the domain.
      type: keyword
    url.top_level_domain:
      dashed_name: url-top-level-domain
      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".

        This value can be determined precisely with a list like the public suffix
        list (http://publicsuffix.org). Trying to approximate this by simply taking
        the last label will not work well for effective TLDs such as "co.uk".'
      example: co.uk
      flat_name: url.top_level_domain
      ignore_above: 1024
      level: extended
      name: top_level_domain
      normalize: []
      short: The effective top level domain (com, org, net, co.uk).
      type: keyword
    url.username:
      dashed_name: url-username
      description: Username of the request.
      flat_name: url.username
      ignore_above: 1024
      level: extended
      name: username
      normalize: []
      short: Username of the request.
      type: keyword
  group: 2
  name: url
  prefix: url.
  reusable:
    expected:
    - as: url
      at: threat.indicator
      beta: Reusing the `url` fields in this location is currently considered beta.
      full: threat.indicator.url
    - as: url
      at: threat.enrichments.indicator
      beta: Reusing the `url` fields in this location is currently considered beta.
      full: threat.enrichments.indicator.url
    top_level: true
  short: Fields that let you store URLs in various forms.
  title: URL
  type: group
user:
  description: 'The user fields describe information about the user that is relevant
    to the event.

    Fields can have one entry or multiple entries. If a user has more than one id,
    provide an array that includes all of them.'
  fields:
    user.changes.domain:
      dashed_name: user-changes-domain
      description: 'Name of the directory the user is a member of.

        For example, an LDAP or Active Directory domain name.'
      flat_name: user.changes.domain
      ignore_above: 1024
      level: extended
      name: domain
      normalize: []
      original_fieldset: user
      short: Name of the directory the user is a member of.
      type: keyword
    user.changes.email:
      dashed_name: user-changes-email
      description: User email address.
      flat_name: user.changes.email
      ignore_above: 1024
      level: extended
      name: email
      normalize: []
      original_fieldset: user
      short: User email address.
      type: keyword
    user.changes.extra:
      dashed_name: user-changes-extra
      description: 'Additional information in key/value pairs.

        For additional information provided by the authenticator to events.

        Note: Not searchable or filterable.'
      enabled: false
      example: '{"authenticator": "ldap", "cipher": "argon2"}'
      flat_name: user.changes.extra
      level: custom
      name: extra
      normalize: []
      object_type: keyword
      original_fieldset: user
      short: Custom key/value pairs.
      type: object
    user.changes.full_name:
      dashed_name: user-changes-full-name
      description: User's full name, if available.
      example: Albert Einstein
      flat_name: user.changes.full_name
      ignore_above: 1024
      level: extended
      multi_fields:
      - flat_name: user.changes.full_name.text
        name: text
        norms: false
        type: text
      name: full_name
      normalize: []
      original_fieldset: user
      short: User's full name, if available.
      type: keyword
    user.changes.group.domain:
      dashed_name: user-changes-group-domain
      description: 'Name of the directory the group is a member of.

        For example, an LDAP or Active Directory domain name.'
      flat_name: user.changes.group.domain
      ignore_above: 1024
      level: extended
      name: domain
      normalize: []
      original_fieldset: group
      short: Name of the directory the group is a member of.
      type: keyword
    user.changes.group.id:
      dashed_name: user-changes-group-id
      description: Unique identifier for the group on the system/platform.
      flat_name: user.changes.group.id
      ignore_above: 1024
      level: extended
      name: id
      normalize: []
      original_fieldset: group
      short: Unique identifier for the group on the system/platform.
      type: keyword
    user.changes.group.name:
      dashed_name: user-changes-group-name
      description: Name of the group.
      flat_name: user.changes.group.name
      ignore_above: 1024
      level: extended
      name: name
      normalize: []
      original_fieldset: group
      short: Name of the group.
      type: keyword
    user.changes.hash:
      dashed_name: user-changes-hash
      description: 'Unique user hash to correlate information for a user in anonymized
        form.

        Useful if `user.id` or `user.name` contain confidential information and cannot
        be used.'
      flat_name: user.changes.hash
      ignore_above: 1024
      level: extended
      name: hash
      normalize: []
      original_fieldset: user
      short: Unique user hash to correlate information for a user in anonymized form.
      type: keyword
    user.changes.id:
      dashed_name: user-changes-id
      description: Unique identifier of the user.
      flat_name: user.changes.id
      ignore_above: 1024
      level: core
      name: id
      normalize: []
      original_fieldset: user
      short: Unique identifier of the user.
      type: keyword
    user.changes.name:
      dashed_name: user-changes-name
      description: Short name or login of the user.
      example: albert
      flat_name: user.changes.name
      ignore_above: 1024
      level: core
      multi_fields:
      - flat_name: user.changes.name.text
        name: text
        norms: false
        type: text
      name: name
      normalize: []
      original_fieldset: user
      short: Short name or login of the user.
      type: keyword
    user.changes.roles:
      dashed_name: user-changes-roles
      description: Array of user roles at the time of the event.
      example: '["kibana_admin", "reporting_user"]'
      flat_name: user.changes.roles
      ignore_above: 1024
      level: extended
      name: roles
      normalize:
      - array
      original_fieldset: user
      short: Array of user roles at the time of the event.
      type: keyword
    user.domain:
      dashed_name: user-domain
      description: 'Name of the directory the user is a member of.

        For example, an LDAP or Active Directory domain name.'
      flat_name: user.domain
      ignore_above: 1024
      level: extended
      name: domain
      normalize: []
      short: Name of the directory the user is a member of.
      type: keyword
    user.effective.domain:
      dashed_name: user-effective-domain
      description: 'Name of the directory the user is a member of.

        For example, an LDAP or Active Directory domain name.'
      flat_name: user.effective.domain
      ignore_above: 1024
      level: extended
      name: domain
      normalize: []
      original_fieldset: user
      short: Name of the directory the user is a member of.
      type: keyword
    user.effective.email:
      dashed_name: user-effective-email
      description: User email address.
      flat_name: user.effective.email
      ignore_above: 1024
      level: extended
      name: email
      normalize: []
      original_fieldset: user
      short: User email address.
      type: keyword
    user.effective.extra:
      dashed_name: user-effective-extra
      description: 'Additional information in key/value pairs.

        For additional information provided by the authenticator to events.

        Note: Not searchable or filterable.'
      enabled: false
      example: '{"authenticator": "ldap", "cipher": "argon2"}'
      flat_name: user.effective.extra
      level: custom
      name: extra
      normalize: []
      object_type: keyword
      original_fieldset: user
      short: Custom key/value pairs.
      type: object
    user.effective.full_name:
      dashed_name: user-effective-full-name
      description: User's full name, if available.
      example: Albert Einstein
      flat_name: user.effective.full_name
      ignore_above: 1024
      level: extended
      multi_fields:
      - flat_name: user.effective.full_name.text
        name: text
        norms: false
        type: text
      name: full_name
      normalize: []
      original_fieldset: user
      short: User's full name, if available.
      type: keyword
    user.effective.group.domain:
      dashed_name: user-effective-group-domain
      description: 'Name of the directory the group is a member of.

        For example, an LDAP or Active Directory domain name.'
      flat_name: user.effective.group.domain
      ignore_above: 1024
      level: extended
      name: domain
      normalize: []
      original_fieldset: group
      short: Name of the directory the group is a member of.
      type: keyword
    user.effective.group.id:
      dashed_name: user-effective-group-id
      description: Unique identifier for the group on the system/platform.
      flat_name: user.effective.group.id
      ignore_above: 1024
      level: extended
      name: id
      normalize: []
      original_fieldset: group
      short: Unique identifier for the group on the system/platform.
      type: keyword
    user.effective.group.name:
      dashed_name: user-effective-group-name
      description: Name of the group.
      flat_name: user.effective.group.name
      ignore_above: 1024
      level: extended
      name: name
      normalize: []
      original_fieldset: group
      short: Name of the group.
      type: keyword
    user.effective.hash:
      dashed_name: user-effective-hash
      description: 'Unique user hash to correlate information for a user in anonymized
        form.

        Useful if `user.id` or `user.name` contain confidential information and cannot
        be used.'
      flat_name: user.effective.hash
      ignore_above: 1024
      level: extended
      name: hash
      normalize: []
      original_fieldset: user
      short: Unique user hash to correlate information for a user in anonymized form.
      type: keyword
    user.effective.id:
      dashed_name: user-effective-id
      description: Unique identifier of the user.
      flat_name: user.effective.id
      ignore_above: 1024
      level: core
      name: id
      normalize: []
      original_fieldset: user
      short: Unique identifier of the user.
      type: keyword
    user.effective.name:
      dashed_name: user-effective-name
      description: Short name or login of the user.
      example: albert
      flat_name: user.effective.name
      ignore_above: 1024
      level: core
      multi_fields:
      - flat_name: user.effective.name.text
        name: text
        norms: false
        type: text
      name: name
      normalize: []
      original_fieldset: user
      short: Short name or login of the user.
      type: keyword
    user.effective.roles:
      dashed_name: user-effective-roles
      description: Array of user roles at the time of the event.
      example: '["kibana_admin", "reporting_user"]'
      flat_name: user.effective.roles
      ignore_above: 1024
      level: extended
      name: roles
      normalize:
      - array
      original_fieldset: user
      short: Array of user roles at the time of the event.
      type: keyword
    user.email:
      dashed_name: user-email
      description: User email address.
      flat_name: user.email
      ignore_above: 1024
      level: extended
      name: email
      normalize: []
      short: User email address.
      type: keyword
    user.extra:
      dashed_name: user-extra
      description: 'Additional information in key/value pairs.

        For additional information provided by the authenticator to events.

        Note: Not searchable or filterable.'
      enabled: false
      example: '{"authenticator": "ldap", "cipher": "argon2"}'
      flat_name: user.extra
      level: custom
      name: extra
      normalize: []
      object_type: keyword
      short: Custom key/value pairs.
      type: object
    user.full_name:
      dashed_name: user-full-name
      description: User's full name, if available.
      example: Albert Einstein
      flat_name: user.full_name
      ignore_above: 1024
      level: extended
      multi_fields:
      - flat_name: user.full_name.text
        name: text
        norms: false
        type: text
      name: full_name
      normalize: []
      short: User's full name, if available.
      type: keyword
    user.group.domain:
      dashed_name: user-group-domain
      description: 'Name of the directory the group is a member of.

        For example, an LDAP or Active Directory domain name.'
      flat_name: user.group.domain
      ignore_above: 1024
      level: extended
      name: domain
      normalize: []
      original_fieldset: group
      short: Name of the directory the group is a member of.
      type: keyword
    user.group.id:
      dashed_name: user-group-id
      description: Unique identifier for the group on the system/platform.
      flat_name: user.group.id
      ignore_above: 1024
      level: extended
      name: id
      normalize: []
      original_fieldset: group
      short: Unique identifier for the group on the system/platform.
      type: keyword
    user.group.name:
      dashed_name: user-group-name
      description: Name of the group.
      flat_name: user.group.name
      ignore_above: 1024
      level: extended
      name: name
      normalize: []
      original_fieldset: group
      short: Name of the group.
      type: keyword
    user.hash:
      dashed_name: user-hash
      description: 'Unique user hash to correlate information for a user in anonymized
        form.

        Useful if `user.id` or `user.name` contain confidential information and cannot
        be used.'
      flat_name: user.hash
      ignore_above: 1024
      level: extended
      name: hash
      normalize: []
      short: Unique user hash to correlate information for a user in anonymized form.
      type: keyword
    user.id:
      dashed_name: user-id
      description: Unique identifier of the user.
      flat_name: user.id
      ignore_above: 1024
      level: core
      name: id
      normalize: []
      short: Unique identifier of the user.
      type: keyword
    user.name:
      dashed_name: user-name
      description: Short name or login of the user.
      example: albert
      flat_name: user.name
      ignore_above: 1024
      level: core
      multi_fields:
      - flat_name: user.name.text
        name: text
        norms: false
        type: text
      name: name
      normalize: []
      short: Short name or login of the user.
      type: keyword
    user.roles:
      dashed_name: user-roles
      description: Array of user roles at the time of the event.
      example: '["kibana_admin", "reporting_user"]'
      flat_name: user.roles
      ignore_above: 1024
      level: extended
      name: roles
      normalize:
      - array
      short: Array of user roles at the time of the event.
      type: keyword
    user.target.domain:
      dashed_name: user-target-domain
      description: 'Name of the directory the user is a member of.

        For example, an LDAP or Active Directory domain name.'
      flat_name: user.target.domain
      ignore_above: 1024
      level: extended
      name: domain
      normalize: []
      original_fieldset: user
      short: Name of the directory the user is a member of.
      type: keyword
    user.target.email:
      dashed_name: user-target-email
      description: User email address.
      flat_name: user.target.email
      ignore_above: 1024
      level: extended
      name: email
      normalize: []
      original_fieldset: user
      short: User email address.
      type: keyword
    user.target.extra:
      dashed_name: user-target-extra
      description: 'Additional information in key/value pairs.

        For additional information provided by the authenticator to events.

        Note: Not searchable or filterable.'
      enabled: false
      example: '{"authenticator": "ldap", "cipher": "argon2"}'
      flat_name: user.target.extra
      level: custom
      name: extra
      normalize: []
      object_type: keyword
      original_fieldset: user
      short: Custom key/value pairs.
      type: object
    user.target.full_name:
      dashed_name: user-target-full-name
      description: User's full name, if available.
      example: Albert Einstein
      flat_name: user.target.full_name
      ignore_above: 1024
      level: extended
      multi_fields:
      - flat_name: user.target.full_name.text
        name: text
        norms: false
        type: text
      name: full_name
      normalize: []
      original_fieldset: user
      short: User's full name, if available.
      type: keyword
    user.target.group.domain:
      dashed_name: user-target-group-domain
      description: 'Name of the directory the group is a member of.

        For example, an LDAP or Active Directory domain name.'
      flat_name: user.target.group.domain
      ignore_above: 1024
      level: extended
      name: domain
      normalize: []
      original_fieldset: group
      short: Name of the directory the group is a member of.
      type: keyword
    user.target.group.id:
      dashed_name: user-target-group-id
      description: Unique identifier for the group on the system/platform.
      flat_name: user.target.group.id
      ignore_above: 1024
      level: extended
      name: id
      normalize: []
      original_fieldset: group
      short: Unique identifier for the group on the system/platform.
      type: keyword
    user.target.group.name:
      dashed_name: user-target-group-name
      description: Name of the group.
      flat_name: user.target.group.name
      ignore_above: 1024
      level: extended
      name: name
      normalize: []
      original_fieldset: group
      short: Name of the group.
      type: keyword
    user.target.hash:
      dashed_name: user-target-hash
      description: 'Unique user hash to correlate information for a user in anonymized
        form.

        Useful if `user.id` or `user.name` contain confidential information and cannot
        be used.'
      flat_name: user.target.hash
      ignore_above: 1024
      level: extended
      name: hash
      normalize: []
      original_fieldset: user
      short: Unique user hash to correlate information for a user in anonymized form.
      type: keyword
    user.target.id:
      dashed_name: user-target-id
      description: Unique identifier of the user.
      flat_name: user.target.id
      ignore_above: 1024
      level: core
      name: id
      normalize: []
      original_fieldset: user
      short: Unique identifier of the user.
      type: keyword
    user.target.name:
      dashed_name: user-target-name
      description: Short name or login of the user.
      example: albert
      flat_name: user.target.name
      ignore_above: 1024
      level: core
      multi_fields:
      - flat_name: user.target.name.text
        name: text
        norms: false
        type: text
      name: name
      normalize: []
      original_fieldset: user
      short: Short name or login of the user.
      type: keyword
    user.target.roles:
      dashed_name: user-target-roles
      description: Array of user roles at the time of the event.
      example: '["kibana_admin", "reporting_user"]'
      flat_name: user.target.roles
      ignore_above: 1024
      level: extended
      name: roles
      normalize:
      - array
      original_fieldset: user
      short: Array of user roles at the time of the event.
      type: keyword
  group: 2
  name: user
  nestings:
  - user.changes
  - user.effective
  - user.group
  - user.target
  prefix: user.
  reusable:
    expected:
    - as: user
      at: client
      full: client.user
    - as: user
      at: destination
      full: destination.user
    - as: user
      at: server
      full: server.user
    - as: user
      at: source
      full: source.user
    - as: target
      at: user
      full: user.target
      short_override: Targeted user of action taken.
    - as: effective
      at: user
      full: user.effective
      short_override: User whose privileges were assumed.
    - as: changes
      at: user
      full: user.changes
      short_override: Captures changes made to a user.
    - as: user
      at: host
      full: host.user
      short_override: This reuse is deprecated and will be removed in the next major
        ECS version.
    top_level: true
  reused_here:
  - full: user.group
    schema_name: group
    short: User's group relevant to the event.
  - full: user.target
    schema_name: user
    short: Targeted user of action taken.
  - full: user.effective
    schema_name: user
    short: User whose privileges were assumed.
  - full: user.changes
    schema_name: user
    short: Captures changes made to a user.
  short: Fields to describe the user relevant to the event.
  title: User
  type: group
user_agent:
  description: 'The user_agent fields normally come from a browser request.

    They often show up in web service logs coming from the parsed user agent string.'
  fields:
    user_agent.device.name:
      dashed_name: user-agent-device-name
      description: Name of the device.
      example: iPhone
      flat_name: user_agent.device.name
      ignore_above: 1024
      level: extended
      name: device.name
      normalize: []
      short: Name of the device.
      type: keyword
    user_agent.name:
      dashed_name: user-agent-name
      description: Name of the user agent.
      example: Safari
      flat_name: user_agent.name
      ignore_above: 1024
      level: extended
      name: name
      normalize: []
      short: Name of the user agent.
      type: keyword
    user_agent.original:
      dashed_name: user-agent-original
      description: Unparsed user_agent string.
      example: Mozilla/5.0 (iPhone; CPU iPhone OS 12_1 like Mac OS X) AppleWebKit/605.1.15
        (KHTML, like Gecko) Version/12.0 Mobile/15E148 Safari/604.1
      flat_name: user_agent.original
      ignore_above: 1024
      level: extended
      multi_fields:
      - flat_name: user_agent.original.text
        name: text
        norms: false
        type: text
      name: original
      normalize: []
      short: Unparsed user_agent string.
      type: keyword
    user_agent.os.family:
      dashed_name: user-agent-os-family
      description: OS family (such as redhat, debian, freebsd, windows).
      example: debian
      flat_name: user_agent.os.family
      ignore_above: 1024
      level: extended
      name: family
      normalize: []
      original_fieldset: os
      short: OS family (such as redhat, debian, freebsd, windows).
      type: keyword
    user_agent.os.full:
      dashed_name: user-agent-os-full
      description: Operating system name, including the version or code name.
      example: Mac OS Mojave
      flat_name: user_agent.os.full
      ignore_above: 1024
      level: extended
      multi_fields:
      - flat_name: user_agent.os.full.text
        name: text
        norms: false
        type: text
      name: full
      normalize: []
      original_fieldset: os
      short: Operating system name, including the version or code name.
      type: keyword
    user_agent.os.kernel:
      dashed_name: user-agent-os-kernel
      description: Operating system kernel version as a raw string.
      example: 4.4.0-112-generic
      flat_name: user_agent.os.kernel
      ignore_above: 1024
      level: extended
      name: kernel
      normalize: []
      original_fieldset: os
      short: Operating system kernel version as a raw string.
      type: keyword
    user_agent.os.name:
      dashed_name: user-agent-os-name
      description: Operating system name, without the version.
      example: Mac OS X
      flat_name: user_agent.os.name
      ignore_above: 1024
      level: extended
      multi_fields:
      - flat_name: user_agent.os.name.text
        name: text
        norms: false
        type: text
      name: name
      normalize: []
      original_fieldset: os
      short: Operating system name, without the version.
      type: keyword
    user_agent.os.platform:
      dashed_name: user-agent-os-platform
      description: Operating system platform (such centos, ubuntu, windows).
      example: darwin
      flat_name: user_agent.os.platform
      ignore_above: 1024
      level: extended
      name: platform
      normalize: []
      original_fieldset: os
      short: Operating system platform (such centos, ubuntu, windows).
      type: keyword
    user_agent.os.type:
      dashed_name: user-agent-os-type
      description: 'Use the `os.type` field to categorize the operating system into
        one of the broad commercial families.

        One of these following values should be used (lowercase): linux, macos, unix,
        windows.

        If the OS you''re dealing with is not in the list, the field should not be
        populated. Please let us know by opening an issue with ECS, to propose its
        addition.'
      example: macos
      flat_name: user_agent.os.type
      ignore_above: 1024
      level: extended
      name: type
      normalize: []
      original_fieldset: os
      short: 'Which commercial OS family (one of: linux, macos, unix or windows).'
      type: keyword
    user_agent.os.version:
      dashed_name: user-agent-os-version
      description: Operating system version as a raw string.
      example: 10.14.1
      flat_name: user_agent.os.version
      ignore_above: 1024
      level: extended
      name: version
      normalize: []
      original_fieldset: os
      short: Operating system version as a raw string.
      type: keyword
    user_agent.version:
      dashed_name: user-agent-version
      description: Version of the user agent.
      example: 12.0
      flat_name: user_agent.version
      ignore_above: 1024
      level: extended
      name: version
      normalize: []
      short: Version of the user agent.
      type: keyword
  group: 2
  name: user_agent
  nestings:
  - user_agent.os
  prefix: user_agent.
  reused_here:
  - full: user_agent.os
    schema_name: os
    short: OS fields contain information about the operating system.
  short: Fields to describe a browser user_agent string.
  title: User agent
  type: group
