schemas/v1/policy/policy.yaml

'@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
Endpoint.configuration:
  dashed_name: Endpoint-configuration
  description: Configuration fields represent the intended and applied setting for
    fields not part of a Policy setting This reflects what a given field is configured
    to do. The actual state of that same field is found in Endpoint.state
  flat_name: Endpoint.configuration
  level: custom
  name: configuration
  normalize: []
  short: The intended and applied setting for fields not part of a Policy setting
  type: object
Endpoint.configuration.isolation:
  dashed_name: Endpoint-configuration-isolation
  description: Configuration setting for Host Isolation from the network
  flat_name: Endpoint.configuration.isolation
  level: custom
  name: configuration.isolation
  normalize: []
  short: Configuration setting for Host Isolation from the network
  type: boolean
Endpoint.policy:
  dashed_name: Endpoint-policy
  description: The policy fields are used to hold information about applied policy.
  flat_name: Endpoint.policy
  level: custom
  name: policy
  normalize: []
  short: The policy fields are used to hold information about applied policy.
  type: object
Endpoint.policy.applied:
  dashed_name: Endpoint-policy-applied
  description: information about the policy that is applied
  flat_name: Endpoint.policy.applied
  level: custom
  name: policy.applied
  normalize: []
  short: information about the policy that is applied
  type: object
Endpoint.policy.applied.actions:
  dashed_name: Endpoint-policy-applied-actions
  description: actions applied during the application of the policy
  enabled: false
  flat_name: Endpoint.policy.applied.actions
  level: custom
  name: policy.applied.actions
  normalize: []
  short: actions applied during the application of the policy
  type: nested
Endpoint.policy.applied.actions.message:
  dashed_name: Endpoint-policy-applied-actions-message
  description: message about the application of the action to further qualify the
    status of the action
  flat_name: Endpoint.policy.applied.actions.message
  ignore_above: 1024
  level: custom
  name: policy.applied.actions.message
  normalize: []
  short: message about the application of the action to further qualify the status
    of the action
  type: keyword
Endpoint.policy.applied.actions.name:
  dashed_name: Endpoint-policy-applied-actions-name
  description: name of the action that was applied
  flat_name: Endpoint.policy.applied.actions.name
  ignore_above: 1024
  level: custom
  name: policy.applied.actions.name
  normalize: []
  short: name of the action that was applied
  type: keyword
Endpoint.policy.applied.actions.status:
  dashed_name: Endpoint-policy-applied-actions-status
  description: the status of the action
  flat_name: Endpoint.policy.applied.actions.status
  ignore_above: 1024
  level: custom
  name: policy.applied.actions.status
  normalize: []
  short: the status of the action
  type: keyword
Endpoint.policy.applied.artifacts:
  dashed_name: Endpoint-policy-applied-artifacts
  description: information about protection artifacts applied.
  flat_name: Endpoint.policy.applied.artifacts
  level: custom
  name: policy.applied.artifacts
  normalize: []
  short: information about protection artifacts applied.
  type: object
Endpoint.policy.applied.artifacts.global:
  dashed_name: Endpoint-policy-applied-artifacts-global
  description: information about global protection artifacts applied.
  flat_name: Endpoint.policy.applied.artifacts.global
  level: custom
  name: policy.applied.artifacts.global
  normalize: []
  short: information about global protection artifacts applied.
  type: object
Endpoint.policy.applied.artifacts.global.channel:
  dashed_name: Endpoint-policy-applied-artifacts-global-channel
  description: global artifacts rollout channel
  flat_name: Endpoint.policy.applied.artifacts.global.channel
  ignore_above: 1024
  level: custom
  name: policy.applied.artifacts.global.channel
  normalize: []
  short: global artifacts rollout channel
  type: keyword
Endpoint.policy.applied.artifacts.global.identifiers:
  dashed_name: Endpoint-policy-applied-artifacts-global-identifiers
  description: the identifiers of global artifacts applied.
  flat_name: Endpoint.policy.applied.artifacts.global.identifiers
  level: custom
  name: policy.applied.artifacts.global.identifiers
  normalize: []
  short: the identifiers of global artifacts applied.
  type: nested
Endpoint.policy.applied.artifacts.global.identifiers.name:
  dashed_name: Endpoint-policy-applied-artifacts-global-identifiers-name
  description: the name of global artifact applied.
  flat_name: Endpoint.policy.applied.artifacts.global.identifiers.name
  ignore_above: 1024
  level: custom
  name: policy.applied.artifacts.global.identifiers.name
  normalize: []
  short: the name of global artifact applied.
  type: keyword
Endpoint.policy.applied.artifacts.global.identifiers.sha256:
  dashed_name: Endpoint-policy-applied-artifacts-global-identifiers-sha256
  description: the sha256 of global artifacts applied.
  flat_name: Endpoint.policy.applied.artifacts.global.identifiers.sha256
  ignore_above: 1024
  level: custom
  name: policy.applied.artifacts.global.identifiers.sha256
  normalize: []
  short: the sha256 of global artifacts applied.
  type: keyword
Endpoint.policy.applied.artifacts.global.snapshot:
  dashed_name: Endpoint-policy-applied-artifacts-global-snapshot
  description: the snapshot date of applied global artifacts or 'latest'
  flat_name: Endpoint.policy.applied.artifacts.global.snapshot
  ignore_above: 1024
  level: custom
  name: policy.applied.artifacts.global.snapshot
  normalize: []
  short: the snapshot date of applied global artifacts or 'latest'
  type: keyword
Endpoint.policy.applied.artifacts.global.update_age:
  dashed_name: Endpoint-policy-applied-artifacts-global-update-age
  description: number of days since global artifacts were made up-to-date
  flat_name: Endpoint.policy.applied.artifacts.global.update_age
  level: custom
  name: policy.applied.artifacts.global.update_age
  normalize: []
  short: number of days since global artifacts were made up-to-date
  type: unsigned_long
Endpoint.policy.applied.artifacts.global.version:
  dashed_name: Endpoint-policy-applied-artifacts-global-version
  description: the version of global artifacts applied.
  flat_name: Endpoint.policy.applied.artifacts.global.version
  ignore_above: 1024
  level: custom
  name: policy.applied.artifacts.global.version
  normalize: []
  short: the version of global artifacts applied.
  type: keyword
Endpoint.policy.applied.artifacts.user:
  dashed_name: Endpoint-policy-applied-artifacts-user
  description: information about user protection artifacts applied.
  flat_name: Endpoint.policy.applied.artifacts.user
  level: custom
  name: policy.applied.artifacts.user
  normalize: []
  short: information about user protection artifacts applied.
  type: object
Endpoint.policy.applied.artifacts.user.identifiers:
  dashed_name: Endpoint-policy-applied-artifacts-user-identifiers
  description: the identifiers of user artifacts applied.
  flat_name: Endpoint.policy.applied.artifacts.user.identifiers
  level: custom
  name: policy.applied.artifacts.user.identifiers
  normalize: []
  short: the identifiers of user artifacts applied.
  type: nested
Endpoint.policy.applied.artifacts.user.identifiers.name:
  dashed_name: Endpoint-policy-applied-artifacts-user-identifiers-name
  description: the name of user artifact applied.
  flat_name: Endpoint.policy.applied.artifacts.user.identifiers.name
  ignore_above: 1024
  level: custom
  name: policy.applied.artifacts.user.identifiers.name
  normalize: []
  short: the name of user artifact applied.
  type: keyword
Endpoint.policy.applied.artifacts.user.identifiers.sha256:
  dashed_name: Endpoint-policy-applied-artifacts-user-identifiers-sha256
  description: the sha256 of user artifacts applied.
  flat_name: Endpoint.policy.applied.artifacts.user.identifiers.sha256
  ignore_above: 1024
  level: custom
  name: policy.applied.artifacts.user.identifiers.sha256
  normalize: []
  short: the sha256 of user artifacts applied.
  type: keyword
Endpoint.policy.applied.artifacts.user.version:
  dashed_name: Endpoint-policy-applied-artifacts-user-version
  description: the version of user artifacts applied.
  flat_name: Endpoint.policy.applied.artifacts.user.version
  ignore_above: 1024
  level: custom
  name: policy.applied.artifacts.user.version
  normalize: []
  short: the version of user artifacts applied.
  type: keyword
Endpoint.policy.applied.endpoint_policy_version:
  dashed_name: Endpoint-policy-applied-endpoint-policy-version
  description: the version of this applied policy
  flat_name: Endpoint.policy.applied.endpoint_policy_version
  ignore_above: 1024
  level: custom
  name: policy.applied.endpoint_policy_version
  normalize: []
  short: the version of this applied policy
  type: keyword
Endpoint.policy.applied.id:
  dashed_name: Endpoint-policy-applied-id
  description: the id of the applied policy
  flat_name: Endpoint.policy.applied.id
  ignore_above: 1024
  level: custom
  name: policy.applied.id
  normalize: []
  short: the id of the applied policy
  type: keyword
Endpoint.policy.applied.name:
  dashed_name: Endpoint-policy-applied-name
  description: the name of this applied policy
  flat_name: Endpoint.policy.applied.name
  ignore_above: 1024
  level: custom
  name: policy.applied.name
  normalize: []
  short: the name of this applied policy
  type: keyword
Endpoint.policy.applied.response:
  dashed_name: Endpoint-policy-applied-response
  description: the response of actions that failed in the applied policy
  enabled: false
  flat_name: Endpoint.policy.applied.response
  level: custom
  name: policy.applied.response
  normalize: []
  short: the response of actions that failed in the applied policy
  type: object
Endpoint.policy.applied.response.configurations:
  dashed_name: Endpoint-policy-applied-response-configurations
  description: the configurations of the applied policy
  enabled: false
  flat_name: Endpoint.policy.applied.response.configurations
  level: custom
  name: policy.applied.response.configurations
  normalize: []
  short: the configurations of the applied policy
  type: object
Endpoint.policy.applied.response.configurations.antivirus_registration:
  dashed_name: Endpoint-policy-applied-response-configurations-antivirus-registration
  description: overall antivirus registration configuration and status of the applied
    policy
  enabled: false
  flat_name: Endpoint.policy.applied.response.configurations.antivirus_registration
  level: custom
  name: policy.applied.response.configurations.antivirus_registration
  normalize: []
  short: overall antivirus registration configuration and status of the applied policy
  type: object
Endpoint.policy.applied.response.configurations.antivirus_registration.concerned_actions:
  dashed_name: Endpoint-policy-applied-response-configurations-antivirus-registration-concerned-actions
  description: all actions that were taken for antivirus registration
  flat_name: Endpoint.policy.applied.response.configurations.antivirus_registration.concerned_actions
  ignore_above: 1024
  level: custom
  name: policy.applied.response.configurations.antivirus_registration.concerned_actions
  normalize: []
  short: all actions that were taken for antivirus registration
  type: keyword
Endpoint.policy.applied.response.configurations.antivirus_registration.status:
  dashed_name: Endpoint-policy-applied-response-configurations-antivirus-registration-status
  description: the overall status of antivirus registration, this is correlated to
    the status of concerned actions but  not a simple sum of the actions
  flat_name: Endpoint.policy.applied.response.configurations.antivirus_registration.status
  ignore_above: 1024
  level: custom
  name: policy.applied.response.configurations.antivirus_registration.status
  normalize: []
  short: the overall status of antivirus registration
  type: keyword
Endpoint.policy.applied.response.configurations.attack_surface_reduction.concerned_actions:
  dashed_name: Endpoint-policy-applied-response-configurations-attack-surface-reduction-concerned-actions
  description: all actions that were taken for attack surface reduction
  flat_name: Endpoint.policy.applied.response.configurations.attack_surface_reduction.concerned_actions
  ignore_above: 1024
  level: custom
  name: policy.applied.response.configurations.attack_surface_reduction.concerned_actions
  normalize: []
  short: all actions that were taken for attack surface reduction
  type: keyword
Endpoint.policy.applied.response.configurations.attack_surface_reduction.status:
  dashed_name: Endpoint-policy-applied-response-configurations-attack-surface-reduction-status
  description: the overall status of attack surface reduction, this is correlated
    to the status of concerned actions but not a simple sum of the actions
  flat_name: Endpoint.policy.applied.response.configurations.attack_surface_reduction.status
  ignore_above: 1024
  level: custom
  name: policy.applied.response.configurations.attack_surface_reduction.status
  normalize: []
  short: overall status of attack surface reduction
  type: keyword
Endpoint.policy.applied.response.configurations.behavior_protection.concerned_actions:
  dashed_name: Endpoint-policy-applied-response-configurations-behavior-protection-concerned-actions
  description: all actions that were taken for behavior_protection
  flat_name: Endpoint.policy.applied.response.configurations.behavior_protection.concerned_actions
  ignore_above: 1024
  level: custom
  name: policy.applied.response.configurations.behavior_protection.concerned_actions
  normalize: []
  short: all actions that were taken for behavior_protection
  type: keyword
Endpoint.policy.applied.response.configurations.behavior_protection.status:
  dashed_name: Endpoint-policy-applied-response-configurations-behavior-protection-status
  description: the overall status of behavior_protection, this is correlated to the
    status of concerned actions  but not a simple sum of the actions
  flat_name: Endpoint.policy.applied.response.configurations.behavior_protection.status
  ignore_above: 1024
  level: custom
  name: policy.applied.response.configurations.behavior_protection.status
  normalize: []
  short: overall status of behavior_protection
  type: keyword
Endpoint.policy.applied.response.configurations.events:
  dashed_name: Endpoint-policy-applied-response-configurations-events
  description: overall event collection configuration and status of the applied policy
  flat_name: Endpoint.policy.applied.response.configurations.events
  level: custom
  name: policy.applied.response.configurations.events
  normalize: []
  short: overall event collection configuration and status of the applied policy
  type: object
Endpoint.policy.applied.response.configurations.events.concerned_actions:
  dashed_name: Endpoint-policy-applied-response-configurations-events-concerned-actions
  description: all actions that were taken for event collection
  flat_name: Endpoint.policy.applied.response.configurations.events.concerned_actions
  ignore_above: 1024
  level: custom
  name: policy.applied.response.configurations.events.concerned_actions
  normalize: []
  short: all actions that were taken for event collection
  type: keyword
Endpoint.policy.applied.response.configurations.events.status:
  dashed_name: Endpoint-policy-applied-response-configurations-events-status
  description: the overall status of event collection, this is correlated to the status
    of concerned actions  but not a simple sum of the actions
  flat_name: Endpoint.policy.applied.response.configurations.events.status
  ignore_above: 1024
  level: custom
  name: policy.applied.response.configurations.events.status
  normalize: []
  short: the overall status of event collection
  type: keyword
Endpoint.policy.applied.response.configurations.host_isolation.concerned_actions:
  dashed_name: Endpoint-policy-applied-response-configurations-host-isolation-concerned-actions
  description: all actions that were taken for host isolation
  flat_name: Endpoint.policy.applied.response.configurations.host_isolation.concerned_actions
  ignore_above: 1024
  level: custom
  name: policy.applied.response.configurations.host_isolation.concerned_actions
  normalize: []
  short: all actions that were taken for host isolation
  type: keyword
Endpoint.policy.applied.response.configurations.host_isolation.status:
  dashed_name: Endpoint-policy-applied-response-configurations-host-isolation-status
  description: the overall status of host isolation, this is correlated to the status
    of concerned actions  but not a simple sum of the actions
  flat_name: Endpoint.policy.applied.response.configurations.host_isolation.status
  ignore_above: 1024
  level: custom
  name: policy.applied.response.configurations.host_isolation.status
  normalize: []
  short: overall status of host isolation
  type: keyword
Endpoint.policy.applied.response.configurations.logging:
  dashed_name: Endpoint-policy-applied-response-configurations-logging
  description: overall logging configuration and status of the applied policy
  flat_name: Endpoint.policy.applied.response.configurations.logging
  level: custom
  name: policy.applied.response.configurations.logging
  normalize: []
  short: overall logging configuration and status of the applied policy
  type: object
Endpoint.policy.applied.response.configurations.logging.concerned_actions:
  dashed_name: Endpoint-policy-applied-response-configurations-logging-concerned-actions
  description: all actions that were taken for logging
  flat_name: Endpoint.policy.applied.response.configurations.logging.concerned_actions
  ignore_above: 1024
  level: custom
  name: policy.applied.response.configurations.logging.concerned_actions
  normalize: []
  short: all actions that were taken for logging
  type: keyword
Endpoint.policy.applied.response.configurations.logging.status:
  dashed_name: Endpoint-policy-applied-response-configurations-logging-status
  description: the overall status of logging, this is correlated to the status of
    concerned actions but  not a simple sum of the actions
  flat_name: Endpoint.policy.applied.response.configurations.logging.status
  ignore_above: 1024
  level: custom
  name: policy.applied.response.configurations.logging.status
  normalize: []
  short: the overall status of logging
  type: keyword
Endpoint.policy.applied.response.configurations.malware:
  dashed_name: Endpoint-policy-applied-response-configurations-malware
  description: overall malware configuration and status of the applied policy
  flat_name: Endpoint.policy.applied.response.configurations.malware
  level: custom
  name: policy.applied.response.configurations.malware
  normalize: []
  short: overall malware configuration and status of the applied policy
  type: object
Endpoint.policy.applied.response.configurations.malware.concerned_actions:
  dashed_name: Endpoint-policy-applied-response-configurations-malware-concerned-actions
  description: all actions that were taken for malware
  flat_name: Endpoint.policy.applied.response.configurations.malware.concerned_actions
  ignore_above: 1024
  level: custom
  name: policy.applied.response.configurations.malware.concerned_actions
  normalize: []
  short: all actions that were taken for malware
  type: keyword
Endpoint.policy.applied.response.configurations.malware.status:
  dashed_name: Endpoint-policy-applied-response-configurations-malware-status
  description: the overall status of malware, this is correlated to the status of
    concerned actions  but not a simple sum of the actions
  flat_name: Endpoint.policy.applied.response.configurations.malware.status
  ignore_above: 1024
  level: custom
  name: policy.applied.response.configurations.malware.status
  normalize: []
  short: the overall status of malware
  type: keyword
Endpoint.policy.applied.response.configurations.memory_protection:
  dashed_name: Endpoint-policy-applied-response-configurations-memory-protection
  description: overall memory_protection configuration and status of the applied policy
  flat_name: Endpoint.policy.applied.response.configurations.memory_protection
  level: custom
  name: policy.applied.response.configurations.memory_protection
  normalize: []
  short: overall memory_protection configuration and status of the applied policy
  type: object
Endpoint.policy.applied.response.configurations.memory_protection.concerned_actions:
  dashed_name: Endpoint-policy-applied-response-configurations-memory-protection-concerned-actions
  description: all actions that were taken for memory_protection
  flat_name: Endpoint.policy.applied.response.configurations.memory_protection.concerned_actions
  ignore_above: 1024
  level: custom
  name: policy.applied.response.configurations.memory_protection.concerned_actions
  normalize: []
  short: all actions that were taken for memory_protection
  type: keyword
Endpoint.policy.applied.response.configurations.memory_protection.status:
  dashed_name: Endpoint-policy-applied-response-configurations-memory-protection-status
  description: the overall status of memory_protection, this is correlated to the
    status of concerned actions but not a simple sum of the actions
  flat_name: Endpoint.policy.applied.response.configurations.memory_protection.status
  ignore_above: 1024
  level: custom
  name: policy.applied.response.configurations.memory_protection.status
  normalize: []
  short: the overall status of memory_protection
  type: keyword
Endpoint.policy.applied.response.configurations.ransomware.concerned_actions:
  dashed_name: Endpoint-policy-applied-response-configurations-ransomware-concerned-actions
  description: all actions that were taken for ransomware
  flat_name: Endpoint.policy.applied.response.configurations.ransomware.concerned_actions
  ignore_above: 1024
  level: custom
  name: policy.applied.response.configurations.ransomware.concerned_actions
  normalize: []
  short: all actions that were taken for ransomware
  type: keyword
Endpoint.policy.applied.response.configurations.ransomware.status:
  dashed_name: Endpoint-policy-applied-response-configurations-ransomware-status
  description: the overall status of ransomware, this is correlated to the status
    of concerned actions  but not a simple sum of the actions
  flat_name: Endpoint.policy.applied.response.configurations.ransomware.status
  ignore_above: 1024
  level: custom
  name: policy.applied.response.configurations.ransomware.status
  normalize: []
  short: overall status of ransomware
  type: keyword
Endpoint.policy.applied.response.configurations.streaming:
  dashed_name: Endpoint-policy-applied-response-configurations-streaming
  description: overall data streaming configuration and status of the applied policy
  flat_name: Endpoint.policy.applied.response.configurations.streaming
  level: custom
  name: policy.applied.response.configurations.streaming
  normalize: []
  short: overall data streaming configuration and status of the applied policy
  type: object
Endpoint.policy.applied.response.configurations.streaming.concerned_actions:
  dashed_name: Endpoint-policy-applied-response-configurations-streaming-concerned-actions
  description: all actions that were taken for data streaming
  flat_name: Endpoint.policy.applied.response.configurations.streaming.concerned_actions
  ignore_above: 1024
  level: custom
  name: policy.applied.response.configurations.streaming.concerned_actions
  normalize: []
  short: all actions that were taken for data streaming
  type: keyword
Endpoint.policy.applied.response.configurations.streaming.status:
  dashed_name: Endpoint-policy-applied-response-configurations-streaming-status
  description: the overall status of data streaming, this is correlated to the status
    of concerned actions  but not a simple sum of the actions
  flat_name: Endpoint.policy.applied.response.configurations.streaming.status
  ignore_above: 1024
  level: custom
  name: policy.applied.response.configurations.streaming.status
  normalize: []
  short: overall status of data streaming
  type: keyword
Endpoint.policy.applied.response.diagnostic:
  dashed_name: Endpoint-policy-applied-response-diagnostic
  description: the diagnostic configurations of the applied policy
  enabled: false
  flat_name: Endpoint.policy.applied.response.diagnostic
  level: custom
  name: policy.applied.response.diagnostic
  normalize: []
  short: the diagnostic configurations of the applied policy
  type: object
Endpoint.policy.applied.response.diagnostic.behavior_protection.concerned_actions:
  dashed_name: Endpoint-policy-applied-response-diagnostic-behavior-protection-concerned-actions
  description: all actions that were taken for the diagnostic configuration of behavior
    protection
  flat_name: Endpoint.policy.applied.response.diagnostic.behavior_protection.concerned_actions
  ignore_above: 1024
  level: custom
  name: policy.applied.response.diagnostic.behavior_protection.concerned_actions
  normalize: []
  short: all actions that were taken for the diagnostic configuration of behavior
    protection
  type: keyword
Endpoint.policy.applied.response.diagnostic.behavior_protection.status:
  dashed_name: Endpoint-policy-applied-response-diagnostic-behavior-protection-status
  description: the overall status of the diagnostic configuration of behavior protection,
    this is correlated to  the status of concerned actions but not a simple sum of
    the actions
  flat_name: Endpoint.policy.applied.response.diagnostic.behavior_protection.status
  ignore_above: 1024
  level: custom
  name: policy.applied.response.diagnostic.behavior_protection.status
  normalize: []
  short: overall status of diagnostic behavior protection
  type: keyword
Endpoint.policy.applied.response.diagnostic.credential_protection.concerned_actions:
  dashed_name: Endpoint-policy-applied-response-diagnostic-credential-protection-concerned-actions
  description: all actions that were taken for the diagnostic configuration of credential
    protection
  flat_name: Endpoint.policy.applied.response.diagnostic.credential_protection.concerned_actions
  ignore_above: 1024
  level: custom
  name: policy.applied.response.diagnostic.credential_protection.concerned_actions
  normalize: []
  short: all actions that were taken for the diagnostic configuration of credential
    protection
  type: keyword
Endpoint.policy.applied.response.diagnostic.credential_protection.status:
  dashed_name: Endpoint-policy-applied-response-diagnostic-credential-protection-status
  description: the overall status of the diagnostic configuration of credential protection,
    this is correlated to  the status of concerned actions but not a simple sum of
    the actions
  flat_name: Endpoint.policy.applied.response.diagnostic.credential_protection.status
  ignore_above: 1024
  level: custom
  name: policy.applied.response.diagnostic.credential_protection.status
  normalize: []
  short: overall status of diagnostic behavior protection
  type: keyword
Endpoint.policy.applied.response.diagnostic.malware.concerned_actions:
  dashed_name: Endpoint-policy-applied-response-diagnostic-malware-concerned-actions
  description: all actions that were taken for the diagnostic configuration of malware
  flat_name: Endpoint.policy.applied.response.diagnostic.malware.concerned_actions
  ignore_above: 1024
  level: custom
  name: policy.applied.response.diagnostic.malware.concerned_actions
  normalize: []
  short: all actions that were taken for the diagnostic configuration of malware
  type: keyword
Endpoint.policy.applied.response.diagnostic.malware.status:
  dashed_name: Endpoint-policy-applied-response-diagnostic-malware-status
  description: the overall status of the diagnostic configuration of malware, this
    is correlated to  the status of concerned actions but not a simple sum of the
    actions
  flat_name: Endpoint.policy.applied.response.diagnostic.malware.status
  ignore_above: 1024
  level: custom
  name: policy.applied.response.diagnostic.malware.status
  normalize: []
  short: overall status of diagnostic malware
  type: keyword
Endpoint.policy.applied.response.diagnostic.memory_protection.concerned_actions:
  dashed_name: Endpoint-policy-applied-response-diagnostic-memory-protection-concerned-actions
  description: all actions that were taken for the diagnostic configuration of memory
    protection
  flat_name: Endpoint.policy.applied.response.diagnostic.memory_protection.concerned_actions
  ignore_above: 1024
  level: custom
  name: policy.applied.response.diagnostic.memory_protection.concerned_actions
  normalize: []
  short: all actions that were taken for the diagnostic configuration of memory protection
  type: keyword
Endpoint.policy.applied.response.diagnostic.memory_protection.status:
  dashed_name: Endpoint-policy-applied-response-diagnostic-memory-protection-status
  description: the overall status of the diagnostic configuration of memory protection,
    this is correlated to  the status of concerned actions but not a simple sum of
    the actions
  flat_name: Endpoint.policy.applied.response.diagnostic.memory_protection.status
  ignore_above: 1024
  level: custom
  name: policy.applied.response.diagnostic.memory_protection.status
  normalize: []
  short: overall status of diagnostic memory protection
  type: keyword
Endpoint.policy.applied.response.diagnostic.memory_scan.concerned_actions:
  dashed_name: Endpoint-policy-applied-response-diagnostic-memory-scan-concerned-actions
  description: all actions that were taken for the diagnostic configuration of memory
    scan
  flat_name: Endpoint.policy.applied.response.diagnostic.memory_scan.concerned_actions
  ignore_above: 1024
  level: custom
  name: policy.applied.response.diagnostic.memory_scan.concerned_actions
  normalize: []
  short: all actions that were taken for the diagnostic configuration of memory scan
  type: keyword
Endpoint.policy.applied.response.diagnostic.memory_scan.status:
  dashed_name: Endpoint-policy-applied-response-diagnostic-memory-scan-status
  description: the overall status of the diagnostic configuration of memory scan,
    this is correlated to  the status of concerned actions but not a simple sum of
    the actions
  flat_name: Endpoint.policy.applied.response.diagnostic.memory_scan.status
  ignore_above: 1024
  level: custom
  name: policy.applied.response.diagnostic.memory_scan.status
  normalize: []
  short: overall status of diagnostic memory scan
  type: keyword
Endpoint.policy.applied.response.diagnostic.ransomware.concerned_actions:
  dashed_name: Endpoint-policy-applied-response-diagnostic-ransomware-concerned-actions
  description: all actions that were taken for the diagnostic configuration of ransomware
  flat_name: Endpoint.policy.applied.response.diagnostic.ransomware.concerned_actions
  ignore_above: 1024
  level: custom
  name: policy.applied.response.diagnostic.ransomware.concerned_actions
  normalize: []
  short: all actions that were taken for the diagnostic configuration of ransomware
  type: keyword
Endpoint.policy.applied.response.diagnostic.ransomware.status:
  dashed_name: Endpoint-policy-applied-response-diagnostic-ransomware-status
  description: the overall status of the diagnostic configuration of ransomware, this
    is correlated to  the status of concerned actions but not a simple sum of the
    actions
  flat_name: Endpoint.policy.applied.response.diagnostic.ransomware.status
  ignore_above: 1024
  level: custom
  name: policy.applied.response.diagnostic.ransomware.status
  normalize: []
  short: overall status of diagnostic ransomware
  type: keyword
Endpoint.policy.applied.status:
  dashed_name: Endpoint-policy-applied-status
  description: the status of the applied policy
  flat_name: Endpoint.policy.applied.status
  ignore_above: 1024
  level: custom
  name: policy.applied.status
  normalize: []
  short: the status of the applied policy
  type: keyword
Endpoint.policy.applied.version:
  dashed_name: Endpoint-policy-applied-version
  description: the version of this applied policy
  flat_name: Endpoint.policy.applied.version
  ignore_above: 1024
  level: custom
  name: policy.applied.version
  normalize: []
  short: the version of this applied policy
  type: keyword
Endpoint.state:
  dashed_name: Endpoint-state
  description: Represents the current state of a non-policy setting These fields reflect
    the current status of a field, which may differ from what it is configured to
    be (see Endpoint.configuration)
  flat_name: Endpoint.state
  level: custom
  name: state
  normalize: []
  short: The current state of a non-policy setting
  type: object
Endpoint.state.isolation:
  dashed_name: Endpoint-state-isolation
  description: Current network isolation state of the host
  flat_name: Endpoint.state.isolation
  level: custom
  name: state.isolation
  normalize: []
  short: Current network isolation state of the host
  type: boolean
agent.build.original:
  dashed_name: agent-build-original
  description: 'Extended build information for the agent.

    This field is intended to contain any build information that a data source may
    provide, no specific formatting is required.'
  example: metricbeat version 7.6.0 (amd64), libbeat 7.6.0 [6a23e8f8f30f5001ba344e4e54d8d9cb82cb107c
    built 2020-02-05 23:10:10 +0000 UTC]
  flat_name: agent.build.original
  ignore_above: 1024
  level: core
  name: build.original
  normalize: []
  short: Extended build information for the agent.
  type: keyword
agent.id:
  dashed_name: agent-id
  description: 'Unique identifier of this agent (if one exists).

    Example: For Beats this would be beat.id.'
  example: 8a4f500d
  flat_name: agent.id
  ignore_above: 1024
  level: core
  name: id
  normalize: []
  short: Unique identifier of this agent.
  type: keyword
agent.type:
  dashed_name: agent-type
  description: 'Type of the agent.

    The agent type always stays the same and should be given by the agent used. In
    case of Filebeat the agent would always be Filebeat also if two Filebeat instances
    are run on the same machine.'
  example: filebeat
  flat_name: agent.type
  ignore_above: 1024
  level: core
  name: type
  normalize: []
  short: Type of the agent.
  type: keyword
agent.version:
  dashed_name: agent-version
  description: Version of the agent.
  example: 6.0.0-rc2
  flat_name: agent.version
  ignore_above: 1024
  level: core
  name: version
  normalize: []
  short: Version of the agent.
  type: keyword
data_stream.dataset:
  dashed_name: data-stream-dataset
  description: Data stream dataset name.
  example: nginx.access
  flat_name: data_stream.dataset
  level: custom
  name: dataset
  normalize: []
  short: The field can contain anything that makes sense to signify the source of
    the data.
  type: constant_keyword
data_stream.namespace:
  dashed_name: data-stream-namespace
  description: Data stream namespace.
  example: production
  flat_name: data_stream.namespace
  level: custom
  name: namespace
  normalize: []
  short: A user defined namespace. Namespaces are useful to allow grouping of data.
  type: constant_keyword
data_stream.type:
  dashed_name: data-stream-type
  description: Data stream type.
  example: logs
  flat_name: data_stream.type
  level: custom
  name: type
  normalize: []
  short: An overarching type for the data stream.
  type: constant_keyword
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.

    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
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.category:
  allowed_values:
  - description: Events in this category annotate API calls that occured on a system.
      Typical sources for those events could be from the Operating System level through
      the native libraries (for example Windows Win32, Linux libc, etc.), or managed
      sources of events (such as ETW, syslog), but can also include network protocols
      (such as SOAP, RPC, Websocket, REST, etc.)
    expected_event_types:
    - access
    - admin
    - allowed
    - change
    - creation
    - deletion
    - denied
    - end
    - info
    - start
    - user
    name: api
  - 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: 'This category is used for events relating to email messages, email
      attachments, and email network or protocol activity.

      Emails events can be produced by email security gateways, mail transfer agents,
      email cloud service providers, or mail server monitoring applications.'
    expected_event_types:
    - info
    name: email
  - 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:
    - access
    - 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: Events in this category refer to the loading of a library, such as
      (dll / so / dynlib), into a process. Use this category to visualize and analyze
      library loading related activity on hosts.  Keep in mind that driver related
      activity will be captured under the "driver" category above.
    expected_event_types:
    - start
    name: library
  - 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 vulnerability scan results. Use this category to analyze
      vulnerabilities detected by Tenable, Qualys, internal scanners, and other vulnerability
      management sources.
    expected_event_types:
    - info
    name: vulnerability
  - 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.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
  - beta: This event categorization value is beta and subject to change.
    description: 'This value indicates events whose primary purpose is to store an
      inventory of assets/entities and their attributes. Assets/entities are objects
      (such as users and hosts) that are expected to be subjects of detailed analysis
      within the system.

      Examples include lists of user identities or accounts ingested from directory
      services such as Active Directory (AD), inventory of hosts pulled from configuration
      management databases (CMDB), and lists of cloud storage buckets pulled from
      cloud provider APIs.

      This value is used by Elastic Security for asset management solutions. `event.kind:
      asset` is not used for normal system events or logs that are coming from an
      asset/entity, nor is it used for system events or logs coming from a directory
      or CMDB system.'
    name: asset
  - 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 is 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.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.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.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
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.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
  pattern: ^[A-F0-9]{2}(-[A-F0-9]{2}){5,}$
  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 (FQDN), or a name specified by the user. The recommended value is the lowercase
    FQDN of the host.'
  flat_name: host.name
  ignore_above: 1024
  level: core
  name: name
  normalize: []
  short: Name of the host.
  type: keyword
host.os.Ext:
  dashed_name: host-os-Ext
  description: Object for all custom defined fields to live in.
  flat_name: host.os.Ext
  level: custom
  name: Ext
  normalize: []
  original_fieldset: os
  short: Object for all custom defined fields to live in.
  type: object
host.os.Ext.variant:
  dashed_name: host-os-Ext-variant
  description: A string value or phrase that further aid to classify or qualify the
    operating system (OS).  For example the distribution for a Linux OS will be entered
    in this field.
  example: Ubuntu
  flat_name: host.os.Ext.variant
  ignore_above: 1024
  level: custom
  name: Ext.variant
  normalize: []
  original_fieldset: os
  short: A string value or phrase that further aid to classify or qualify the operating
    system (OS).
  type: keyword
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.caseless
    ignore_above: 1024
    name: caseless
    normalizer: lowercase
    type: keyword
  - 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.caseless
    ignore_above: 1024
    name: caseless
    normalizer: lowercase
    type: keyword
  - 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.

    If the OS you''re dealing with is not listed as an expected value, the field should
    not be populated. Please let us know by opening an issue with ECS, to propose
    its addition.'
  example: macos
  expected_values:
  - linux
  - macos
  - unix
  - windows
  - ios
  - android
  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, windows, ios or
    android).'
  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
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: []
  short: Log message optimized for viewing in a log viewer.
  type: match_only_text