You can use predefined field names as keywords in filter criteria. The query result only shows log records that match the criteria in the specified field. If you do not use field names, the query result shows records that match the criteria in all fields.
This table shows the predefined field keywords. Some fields also support keyword aliases that you can type as alternatives to the primary keyword.
Keyword |
Keyword Alias |
Description |
---|---|---|
|
|
Severity of the event |
|
|
Potential risk from the application, of the event |
|
|
Name of the protection |
|
|
Type of protection |
|
|
Level of confidence that an event is malicious |
|
|
Action taken by a security rule |
|
|
Software Blade |
|
|
Traffic destination IP address, DNS name or Check Point network object name |
|
|
Name of originating Security Gateway |
|
|
Service that generated the log entry |
|
|
Traffic source IP address, DNS name or Check Point network object name |
|
|
User name |
Syntax for a field name query:
<field name>:<values>
To search for rule number, use the Rule field name. For example:
rule:7.1
If you use the rule number as a filter, rules in all the Layers with that number are matched.
To search for a rule name, you must not use the Rule field. Use free text. For example:
"Block Credit Cards"
Best practice: Do a free text search for the rule name. Make sure rule names are unique and not reused in different Layers.
Examples:
source:192.168.2.1
action:(Reject OR Block)
You can use the OR Boolean operator in parentheses to include multiple criteria values.
Important - When you use fields with multiple values, you must: