Best practice for general search constraints
When searching for events, consider these general guidelines:
-
Many fields require wildcards for partial-match searches. All fields accept wildcards for these searches. For more information, refer to Wildcards and symbols in searches.
-
All fields accept negation (
!). -
All fields accept comma-separated lists of search values. Records that contain any of the listed values in the specified field match that search criteria.
-
All fields accept comma-separated lists enclosed in quotation marks as search values.
-
For fields that may contain only a single value, records with the specified field containing the exact string specified within the quotation marks match the search criteria. For instance, a search for
A, B, "C, D, E"will match records where the specified field contains"A"or"B"or"C, D, E". This permits matching on fields that include the comma in possible values. -
For fields that may contain multiple values at the same time, records with the specified fields containing all of the values in the quote-enclosed comma-separated list match that search criteria.
-
For fields that may contain multiple values at the same time, search criteria may include single values as well as quote-enclosed comma-separated lists. For instance, a search for
A, B, "C, D, E"on a field that may contain one of more of these letters matches records where the specified field containsAorB, or all ofC,D, andE.
-
-
Specify
n/ain any field to identify events where information is not available for that field; use!n/ato identify the events where that field is populated. -
You can precede many numeric fields with greater than (
>), greater than or equal to (>=), less than (<), less than or equal to (<=), equal to (=), or not equal to (<>) operators.
Note | When you search a field with long complicated values (such as SHA-256 hash values), copy the search criteria value from source material and paste it into the appropriate field on the search page. |