# Define Context options for Correlation Situation elements

Correlation Contexts define the patterns for matching groups of related events in traffic.

##

For more details about the product and how to configure features, click Help or press F1.

## Steps

1. On the Context tab of the Correlation Situation Properties dialog box, click Select.
2. Select the Context you want to associate with this Correlation Situation.

## Correlation Situation Properties dialog box

Use this dialog box to configure a Correlation Situation.

Note: We recommend that you use only the predefined Correlation Situation elements included in dynamic update packages. The use of custom Correlation Situations is an advanced feature that requires technical expertise.

Option | Definition
--- | ---
General tab
Name | Specifies a unique name for the Situation.
Comment | An optional comment for your own reference.
Vulnerability | Lists the known vulnerabilities associated with the Situation, if available.
Situation Type | Shows the Situation Type with which to associate this Situation.
Select | Opens the Select Element dialog box. You can only select one Situation Type for each Situation. The Situation Type specifies the branch of the Rules tree under which the Situation is included.
Description | Use the Description field to describe the traffic pattern that the Situation represents. This description is shown, for example, in log entries.
Severity | Select a Severity for the Situation. The Severity is shown in the logs and can be used in Alert Policies as a criterion for alert escalation.
Attacker | Select how the Attacker is determined when the Situation matches. This information is used for blacklisting and in log entries. None — Does not define the Attacker and Target information, so blacklisting entries cannot be created using the Attacker and Target options. IP Source or IP Destination— The IP addresses of the (last) packet that triggers the Situation. Because the packet can be a request or a reply, make sure to select the option correctly based on the pattern that the Situation detects to avoid reversed labeling. Connection Source or Connection Destination — IP addresses depend on which host opened the connection and provide a constant point of reference to the client and server in the communications.
Target | Select how the Target is determined when the Situation matches. This information is used for blacklisting and in log entries. None — Does not define the Attacker and Target information, so blacklisting entries cannot be created using the Attacker and Target options. IP Source or IP Destination— The IP addresses of the (last) packet that triggers the Situation. Because the packet can be a request or a reply, make sure to select the option correctly based on the pattern that the Situation detects to avoid reversed labeling. Connection Source or Connection Destination — IP addresses depend on which host opened the connection and provide a constant point of reference to the client and server in the communications.
Last Update in | Shows the dynamic update package number that the Situation was included in or changed in.
Supported Engine Versions | Specifies the supported engine versions for the Situation.
Category | Includes the Situation in predefined categories.
Select | Opens the Category Selection dialog box.

Option | Definition
--- | ---
Context tab
Context | Select the Context that you want to associate with this Correlation Situation: Compress — Combines repeated similar events into the same log entry, reducing the amount of data that is sent to the Log Server. Count — Finds recurring patterns in traffic by counting the times certain Situations occur within a defined time period. The Situation matches if the threshold values you set are exceeded. Group — Finds patterns in traffic by following if all events in the defined set of Situations match at least once in any order within the defined time period. Match — Allows filtering event data using filters. Sequence — Finds patterns in traffic by following if all events in the defined set of Situations match in a specific order within a defined time period. Note: These contexts are updated dynamically and can change. Click Select to select an element.
Parameters section (When Context is Group or Sequence)
Correlated Situations | Shows the situations that are correlated in this Correlation Situation.
Keep and forward events | When Yes is selected, log entries are created about events related to the correlated situations.
Time window size | The time period in which events must occur to be correlated.
Continuous responses | (When Context is Group) When Yes is selected, the NGFW Engine responds continuously to events.
Usage context | Specifies whether correlation is done only on the NGFW Engine, only on the Log Server, or on both the NGFW Engine and the Log Server. By default, correlation is done on both the NGFW Engine and the Log Server for custom Correlation Situations.

Option | Definition
--- | ---
Tags tab
Name | Shows the name of the tag.
Comment | Shows the comment associated with the tag.
Type | Shows the type of tag.
Add Tags | Opens the dialog box to add a tag. Select from the available options: Hardware Operating System Situation Tag Software

## Event Binding Properties dialog box

Use this dialog box to view the properties of Event Binding elements.

CAUTION:
Do not create Event Binding elements. Use the predefined Event Binding elements instead. The main options are explained here.

Option | Definition
--- | ---
Name | Specifies a unique name for the event binding.
Comment | An optional comment for your own reference.
Resources | Shows a list of log fields.
Search | Opens a search field for the selected element list.
Up (Backspace) | Returns to the previous folder.
Tools | Show Deleted Elements — Shows elements that have been moved to the Trash. Refresh View — Refreshes the list of elements.
Bindings table |
First binding | The first set of logs to use in Correlation Situations to bind together different types of events in traffic.
Second binding | The second set of logs to use in a sequence when using Correlation Situations to bind together different types of events in traffic.