This section provides information on supported fields and operations for the Historical Search. See the relevant section below:
Supported fields
Name | Display Value | Artifacts |
|---|---|---|
All Events | Default (Empty) | All |
Activity | Activity | All |
Command line | CommandLine | Process |
Device name | DeviceName | All |
IP address | IpAddress | Network |
MD5 | MD5 | File |
Parent Process ID | Ppid | Process |
Parent Process Name | ParentProcessName | Process |
Process ID | Pid | Process |
Process name | ProcessName | Process |
Sha1 | Sha1 | File |
Sha256 | Sha256 | File |
User name | UserName | All |
Note
When you use MD5, SHA-1, or SHA-256, it means the hashes correspond to a file.
When you use IP address, it means the destination address.
Supported logical operators
ANDOR
Note
DeviceName can be joined with any other field using the
ANDlogical operator.For client systems with EDR client version 3.3.x or earlier, the result doesn't appear on the Historical Search dashboard when searched with the
ANDlogical operator for artifacts DeviceName and ProcessName.Example: DeviceName = 7ws3342
ANDProcessName = cmd.exeCommandLine and IpAddress can't be joined using the
ANDlogical operator, but can be joined using theORlogical operator.CommandLine and ProcessName can be joined using the
ANDlogical operator.
Supported operators
Name | Display Value |
|---|---|
Activity |
|
DeviceName |
|
ProcessName |
|
CommandLine |
|
IpAddress |
|
ParentProcessName |
|
Pid |
|
Ppid |
|
Sha256 |
|
MD5 |
|
Sha1 |
|
UserName |
|
Network DstPort |
|
Score |
|
Integrity |
|
Logon LogonId |
|
Note
containsonly applies if the time range is <= 24 hours.
Allowed operations
=!=The values passed to
=and!=are case-sensitive.When a field is included in a search, the results returned must contain a value in the field included in the search.
If the search is based on an IP address, only the results with values in the IP address field are returned.
Example:
"fieldName != value" means "(fieldName exists and fieldName != value)"ipAddress != 10.1.1.1 and DeviceName = '7xblah'ipAddress = destination IP at that moment.
Excludes all network traces with that IP address.
starts withincontainsnot containsThe value passed to
inis case-sensitive.The values passed to
starts with,contains, andnot containsare case-insensitive.Queries with the operators
starts withandcontains, all special characters, and" "(blank space) need to be escaped.Note
This isn't the case for the
equalsandnot equalsoperators.When a value in the query contains double quotes that need to be escaped, the value must be enclosed in double quotes as shown below:
Example: CommandLine =
"C:\Program Files (x86)\Google\Update\GoogleUpdate.exe" /ua /installsource schedulerTo be written as: CommandLine =
"C:\Program Files (x86)\Google\Update\GoogleUpdate.exe\" /ua /installsource schedulerWhen the value contains a space, the whole value must be enclosed in double quotes as shown below:
Example: CommandLine =
C:\Windows\System32\svchost.exe -k wsappxTo be written as: CommandLine =
"C:\Windows\System32\svchost.exe -k wsappx"For the
contains,not contains, andstarts withoperators, all special characters need to be escaped with backslashes as shown below:Example: Value =
C:\Windows\System32\svchost.exe -k wsappxTo be written as:
CommandLine contains "C\:\\Windows\\System32\\svchost.exe\ -k\ wsappx"
This behavior applies to both Historical Search and Device Search.
Example:
"fieldName not contains value"means"(fieldName exists and fieldName not contains value)".