Role Availability | Read-Only | Investigator | Analyst | Manager |
To create a response action rule
- Go to Settings > Rules.
-
Select Create Orchestration Rule > Response Action 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.
- Alarms: Use this packet type for console user alarms-based rules.
- Click Add Condition and select the property values you want to include in the rule to create a matching condition.
-
(Optional.) Click Add Group to group your conditions.
Note: See Operators in the Orchestration Rules for more information.
-
In the Occurrences text box, enter the number of event occurrences that you want to produce a match on the conditional expression to trigger the rule.
You can enter the number of occurrences or use the arrows to scroll the value up or down. You can enter a number between 1 and 100.
- 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.
- (Optional.) Enter a description for identifying this rule.
- Select an Action Type:
- AT&T Cybersecurity Forensics Process and method of investigation, including the collection, recording, and analysis of events to discover the source of network attacks and other potentially malicious or harmful activities. and Response App: See Scheduling a Forensics and Response Job for more information.
- Authenticated Asset Scanner: See Performing Vulnerability Scans for more information.
- Agent Query: You can run a user-initiated agent query. There are several ad-hoc queries, which are in your environment by default. These queries generate events which can be used for a forensic investigation, so you can focus on fast response and remediation. See The LevelBlue Agent for more information.
-
Select an App Action.
The options vary depending on the selected action type.
-
In the Length text box, specify the timespan that you want to use to identify a match for multiple occurrences. Enter the number in the text box, and then use the drop-down menu to select 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.
-
Click Save.
The created rule displays in the list of rules. You can see it from Settings > Rules. See Orchestration Rules for more information.
Note: If the field is related to the name of a country, you should use the country code defined by the ISO 3166.
Note: The Sources or Destinations field needs to match the universally unique identifier (UUID) of the event or alarm. You can use the Source Name or Destination Name field instead.
Important: Instead of using the equals and equals, case insensitive operators for array fields, LevelBlue recommends the use of the in or contains operators.
Note: If you need to add a property value that maps with a property key, you need to know the mapping of the field. See Determining the Mapping of a Field for more information.
Note: The current rule box shows you the syntax of your rule, and the rule verification box reviews that syntax before saving the rule.
Note: Your defined length and occurrences 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.
Important: It takes a few minutes for an orchestration rule to become active.
To filter
- Go to Settings > Rules.
- Click the box next to Filter By.
- Enter your search.
To filter
- Go to Settings > Rules.
- Click the combo box next to Rule Status.
- Select All Rules, Enabled, or Disabled.
To edit a response action rule
- Go to Settings > Rules.
- Click the icon of the rule you want to edit.
- Modify the data of the items that need to be modified.
- Click Next.
- Click Save.
To delete a response action rule
- Go to Settings > Rules.
- Click the icon of the rule you want to delete.
- Confirm by clicking Accept.
To enable a response action rule
- Go to Settings > Rules.
- Click the icon of the rule you want to enable.
To disable an response action rule
- Go to Settings > Rules.
- Click the icon of the rule you want to disable.
To enable all response action rules
- Go to Settings > Rules.
- In the list of rules, select the first checkbox in the first column to select all the rules.
- Click Enable All Rules.
To disable all response action rules
- Go to Settings > Rules.
- In the list of rules, select the first checkbox in the first column to select all the rules.
- Click Disable All Rules.
- Confirm by clicking Accept.