Hash fields
Elastic Cloud Serverless projects are autoscaled environments, fully managed by Elastic and available on Elastic Cloud. Availability This functionality is generally available and ready for production usage. Serverless interfaces and procedures might differ from classic Elastic Stack deployments. The Elastic Stack includes Elastic's core products such as Elasticsearch, Kibana, Logstash, and Beats. Availability 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.
Serverless
Generally available
Stack
Generally available
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).
| Field | Description | Level |
|---|---|---|
| hash.cdhash | This field is beta and subject to change. Code directory hash, utilized to uniquely identify and authenticate the integrity of the executable code. type: keyword example: 3783b4052fd474dbe30676b45c329e7a6d44acd9 |
extended |
| hash.md5 | MD5 hash. type: keyword |
extended |
| hash.sha1 | SHA1 hash. type: keyword |
extended |
| hash.sha256 | SHA256 hash. type: keyword |
extended |
| hash.sha384 | SHA384 hash. type: keyword |
extended |
| hash.sha512 | SHA512 hash. type: keyword |
extended |
| hash.ssdeep | SSDEEP hash. type: keyword |
extended |
| hash.tlsh | TLSH hash. type: keyword |
extended |
The hash fields are expected to be nested at:
dll.hashemail.attachments.file.hashfile.hashprocess.hash
Note also that the hash fields are not expected to be used directly at the root of the events.