Type to search.

Translate SID

Serverless

Elastic Cloud Serverless projects are autoscaled environments, fully managed by Elastic and available on Elastic Cloud.

Availability

  • Generally available

    This functionality is generally available and ready for production usage.

Serverless interfaces and procedures might differ from classic Elastic Stack deployments.

Stack

The Elastic Stack includes Elastic's core products such as Elasticsearch, Kibana, Logstash, and Beats.

Availability

  • Generally available

    This functionality is generally available and ready for production usage.

Unless stated otherwise on the page, this functionality is available when your Elastic Stack is deployed on Elastic Cloud Hosted, Elastic Cloud Enterprise, Elastic Cloud on Kubernetes, and self-managed environments.

This documentation corresponds to the latest patch available for each minor version. If you're not using the latest patch, check the release notes for changes.

The translate_sid processor translates a Windows security identifier (SID) into an account name. It retrieves the name of the account associated with the SID, the first domain on which the SID is found, and the type of account. This is only available on Windows.

Every account on a network is issued a unique SID when the account is first created. Internal processes in Windows refer to an account’s SID rather than the account’s user or group name, and these values sometimes appear in logs.

If the SID is invalid (malformed) or does not map to any account on the local system or domain, the processor will return an error unless ignore_failure is set.

Example

YAML 
- translate_sid:
    field: winlog.event_data.MemberSid
    account_name_target: user.name
    domain_target: user.domain
    ignore_missing: true
    ignore_failure: true

Configuration settings

Note

Elastic Agent processors execute before ingest pipelines, which means that your processor configurations cannot refer to fields that are created by ingest pipelines or Logstash. For more limitations, refer to What are some limitations of using processors?

Name Required Default Description
field Yes Source field containing a Windows security identifier (SID).
account_name_target Yes* Target field for the account name value.
account_type_target Yes* Target field for the account type value.
domain_target Yes* Target field for the domain value.
ignore_missing No false Ignore errors when the source field is missing.
ignore_failure No false Ignore all errors produced by the processor.
  • At least one of account_name_target, account_type_target, and domain_target must be configured.