- Elastic Common Schema (ECS) Reference: other versions:
- Overview
- Using ECS
- ECS Field Reference
- Base Fields
- Agent Fields
- Autonomous System Fields
- Client Fields
- Cloud Fields
- Code Signature Fields
- Container Fields
- Data Stream Fields
- Destination Fields
- Device Fields
- DLL Fields
- DNS Fields
- ECS Fields
- ELF Header Fields
- Email Fields
- Error Fields
- Event Fields
- FaaS Fields
- File Fields
- Geo Fields
- Group Fields
- Hash Fields
- Host Fields
- HTTP Fields
- Interface Fields
- Log Fields
- Mach-O Header Fields
- Network Fields
- Observer Fields
- Orchestrator Fields
- Organization Fields
- Operating System Fields
- Package Fields
- PE Header Fields
- Process Fields
- Registry Fields
- Related Fields
- Risk information Fields
- Rule Fields
- Server Fields
- Service Fields
- Source Fields
- Threat Fields
- TLS Fields
- Tracing Fields
- URL Fields
- User Fields
- User agent Fields
- VLAN Fields
- Volume Fields
- Vulnerability Fields
- x509 Certificate Fields
- ECS Categorization Fields
- Migrating to ECS
- Additional Information
- Release Notes
Hash Fields
editHash Fields
editThe 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).
Hash Field Details
editField | Description | Level |
---|---|---|
[beta] 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: |
extended |
|
MD5 hash. type: keyword |
extended |
|
SHA1 hash. type: keyword |
extended |
|
SHA256 hash. type: keyword |
extended |
|
SHA384 hash. type: keyword |
extended |
|
SHA512 hash. type: keyword |
extended |
|
SSDEEP hash. type: keyword |
extended |
|
TLSH hash. type: keyword |
extended |
Field Reuse
editThe hash
fields are expected to be nested at:
-
dll.hash
-
email.attachments.file.hash
-
file.hash
-
process.hash
Note also that the hash
fields are not expected to be used directly at the root of the events.
On this page