In this example, an orchestration rule is created to generate an alarm Alarms provide notification of an event or sequence of events that require attention or investigation. whenever a user, who is included in a correlation list, generates an event.
Note: See Correlation Lists for more information.
To create an orchestration rule for generating an alarm when a user, included in a correlation list, generates an event
- Go to Settings > Rules > Correlation Lists.
- Click New List.
- Enter a name for the correlation list in the Name field and, if desired, a description to clarify its use in the Description field.
- Click Add Item to include the user names to your list.
- Click Save.
- Go to Settings > Rules.
- Click Create Orchestration Rule > Alarm Rule.
Select a Boolean operator.
The options are AND, OR, AND NOT, and OR NOT.
Select a packet type in the Match drop-down list.
- Logs: Use this packet type for event-based rules.
- Configuration Issues: Use this packet type for configuration issues-based rules1.
- Vulnerabilities: Use this packet type for vulnerabilities-based rules.
- System Events: Use this packet type for system events-based rules.
- Console User Events: Use this packet type for console user events-based rules.
Click Add Conditions and select these property values.
- Click Next.
Important: A dialog box opens if there are warning messages. Click Cancel to review the warning messages, or click Accept to continue creating the rule.
- Enter a name for the rule (for instance "Alarm for undesirable users") and, if desired, a description to clarify its use in the Description field.
- Select an intent.
- Enter a method.
- Select a strategy.
- Enter a priority.
- Configure a mute duration set in seconds, minutes, and hours.
Modify these two options:
- Occurrences: Specify the number of event occurrences that produce a match on the conditional expression to trigger the rule. You can enter the number of occurrences or use the arrow to scroll the value up or down. You need to enter a number between 1 and 100.
Length: Specify the length of the timespan used to identify a match for multiple occurrences. Enter the number and choose a value of seconds, minutes, or hours.
This duration identifies the amount of time that transpires from the beginning to the end of the occurrence. If the number of occurrences is not met within this period, the rule is not a match.
In this example, the rule applies when the configured conditions happen five times every three hours.
These two options function together to specify the number of occurrences within a time period that will produce a match for the rule. For example, you can define a rule to trigger an alarm Alarms provide notification of an event or sequence of events that require attention or investigation. for an unauthorized access An incident-type categorization that may be a precursor to other actions or stages of an attack. attempt when a failed SSH Program to securely log into another computer over a network, execute commands in a remote machine, and move files from one machine to another through Secure Copy (SCP). login Log in (verb): Process in which an individual gains access to a computer system after providing sufficient credentials to authenticate their unique identity. Login (noun): User credentials, typically a username and matching password. occurs three times within a five-minute window.
(Optional.) Select the fields that you want to display in the generated alarm.
You can select or remove the fields you want to include in the details of the alarm by clicking the and the icons.
The created rule displays in the list of rules. You can see it from Settings > Rules. See Orchestration Rules for more information.
Important: The valid characters for the correlation list name are uppercase letters (A-Z), lowercase letters (a-z), numerical digits (0-9), and underscore (_). You are allowed to enter from 1 to 64 characters.
The intent describes the context of the behavior that is being observed. These intents roughly map to the stages of the intrusion kill chains but are collapsed to ensure that each is discrete. See Intent for more information about the available threat categories.
If known, it is the method of attack or infiltration Indicator that specifies the method of attack that generated an alarm. For Open Threat Exchange® (OTX™) pulses, this method is the pulse name. associated with the indicator that generated the alarm.
Note: This is a required field; if you do not complete this field, the Save button remains inactive.
The strategy describes the broad-based strategy or behavior that is detected. The intention is to describe the malicious Activity in a system that exceeds or misuses that access in a manner that negatively affects the confidentiality, integrity, or availability of the organization's information systems. user's strategy to achieve their goal.
See Priority Field for Alarms for more information.
You can use the mute value to set the period of time during which, once an alarm is createdUSM Anywhere will not create a new alarm based on the same conditions.
Note: Take care to set a mute duration that is long enough to cover the span of time in which matching events will occur to maximize the efficacy of your mute.
Important: If your USM Anywhere™ is restarted when one of your alarm mutes is active, or if there is an update or hotfix, the alarm mute will be canceled.
Important: It takes a few minutes for an orchestration rule to become active.