PE Header Fields
editPE Header Fields
editThese fields contain Windows Portable Executable (PE) metadata.
PE Header Field Details
editField | Description | Level |
---|---|---|
CPU architecture target for the file. type: keyword example: |
extended |
|
Internal company name of the file, provided at compile-time. type: keyword example: |
extended |
|
Internal description of the file, provided at compile-time. type: keyword example: |
extended |
|
Internal version of the file, provided at compile-time. type: keyword example: |
extended |
|
A hash of the Go language imports in a PE file excluding standard library imports. An import hash can be used to fingerprint binaries even after recompilation or other code-level transformations have occurred, which would change more traditional hash values. The algorithm used to calculate the Go symbol hash and a reference implementation are available [here](https://github.com/elastic/toutoumomoma). type: keyword example: |
extended |
|
List of imported Go language element names and types. type: flattened |
extended |
|
Shannon entropy calculation from the list of Go imports. type: long |
extended |
|
Variance for Shannon entropy calculation from the list of Go imports. type: long |
extended |
|
Set to true if the file is a Go executable that has had its symbols stripped or obfuscated and false if an unobfuscated Go executable. type: boolean |
extended |
|
A hash of the imports in a PE file. An imphash — or import hash — can be used to fingerprint binaries even after recompilation or other code-level transformations have occurred, which would change more traditional hash values. Learn more at https://www.fireeye.com/blog/threat-research/2014/01/tracking-malware-import-hashing.html. type: keyword example: |
extended |
|
A hash of the imports in a PE file. An import hash can be used to fingerprint binaries even after recompilation or other code-level transformations have occurred, which would change more traditional hash values. This is a synonym for imphash. type: keyword example: |
extended |
|
List of imported element names and types. type: flattened Note: this field should contain an array of values. |
extended |
|
Shannon entropy calculation from the list of imported element names and types. type: long |
extended |
|
Variance for Shannon entropy calculation from the list of imported element names and types. type: long |
extended |
|
Internal name of the file, provided at compile-time. type: keyword example: |
extended |
|
A hash of the PE header and data from one or more PE sections. An pehash can be used to cluster files by transforming structural information about a file into a hash value. Learn more at https://www.usenix.org/legacy/events/leet09/tech/full_papers/wicherski/wicherski_html/index.html. type: keyword example: |
extended |
|
Internal product name of the file, provided at compile-time. type: keyword example: |
extended |
|
An array containing an object for each section of the PE file. The keys that should be present in these objects are defined by sub-fields underneath type: nested Note: this field should contain an array of values. |
extended |
|
Shannon entropy calculation from the section. type: long |
extended |
|
PE Section List name. type: keyword |
extended |
|
PE Section List physical size. type: long |
extended |
|
Variance for Shannon entropy calculation from the section. type: long |
extended |
|
PE Section List virtual size. This is always the same as type: long |
extended |
Field Reuse
editThe pe
fields are expected to be nested at:
-
dll.pe
-
file.pe
-
process.pe
Note also that the pe
fields are not expected to be used directly at the root of the events.