> ## Documentation Index
> Fetch the complete documentation index at: https://docs.levelblue.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Response Action Rules from the Orchestration Rules Page
| | | | | |
| --------------------- | --------- | ------------ | ----------- | ----------- |
| **Role Availability** | Read-Only | Investigator | **Analyst** | **Manager** |
**To create a notification rule from the Orchestration rules page**
1. Go to **Settings > Rules**.
2. Select **Create Orchestration Rule > Response Action Rule**.
3. Select a Boolean operator.
The options are AND, OR, AND NOT, and OR NOT.
4. 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.
5. Click **Add Conditions** and select the property values you want to include in the rule to create a matching condition.
**Note:** If the field is related to the name of a country, you should use the country code defined by the [ISO 3166](https://www.iso.org/iso-3166-country-codes.html).
**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](/documentation/usm-anywhere/user-guide/rules-management/mapping-field) of a Field for more information.
6. (Optional.) Click **Add Group** to group your conditions.
**Note:** See [Operators in the Orchestration Rules](/documentation/usm-anywhere/user-guide/rules-management/orchestration-rules-operators) for more information.
7. 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.
**Note:** The current rule box shows you the syntax of your rule, and the rule verification box reviews that syntax before saving the rule.
8. 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.
9. Enter a name for the rule.
10. (Optional.) Enter a description for identifying this rule.
11. Select an Action Type:
* **AT\&T Cybersecurity Forensics and Response App:** See [Scheduling a Forensics and Response Job](/documentation/usm-anywhere/alienapps-guide/forensics-response/log-collect-blueapp-forensics-resp) for more information.
* **Authenticated Asset Scanner:** See [Performing Vulnerability Scans](/documentation/usm-anywhere/user-guide/vulnerability-assessment/perf-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](/documentation/usm-anywhere/agents/alienvault-agents) for more information.
12. Select an App Action.
The options vary depending on the selected action type.
13. 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.
**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 for an unauthorized access attempt when a failed SSH login occurs three times within a five-minute window.
14. Click **Save**.
The created rule displays in the list of rules. You can see it from **Settings > Rules**. See [Orchestration Rules](https://cybersecurity.att.com/documentation/usm-anywhere/user-guide/rules-management/orchestration-rules) for more information.
**Important:** It takes a few minutes for an orchestration rule to become active.
**To filter response action rules by name**
1. Go to **Settings > Rules**.
2. Click the box next to Filter By.
3. Enter your search.
**To filter response action rules by rule status**
1. Go to **Settings > Rules**.
2. Click the combo box next to Rule Status.
3. Select **All Rules**, **Enabled**, or **Disabled**.
**To edit a response action rule**
1. Go to **Settings > Rules**.
2. Click the 
icon of the rule you want to edit.
3. Modify the data of the items that need to be modified.
4. Click **Next**.
5. Click **Save**.
**To delete a response action rule**
1. Go to **Settings > Rules**.
2. Click the 
icon of the rule you want to delete.
3. Confirm by clicking **Accept**.
**To enable a response action rule**
1. Go to **Settings > Rules**.
2. Click the 
icon of the rule you want to enable.
**To disable a response action rule**
1. Go to **Settings > Rules**.
2. Click the 
icon of the rule you want to disable.
**To enable all response action rules**
1. Go to **Settings > Rules**.
2. In the list of rules, select the first checkbox in the first column to select all the rules.
3. Click **Enable All Rules**.
**To disable all response action rules**
1. Go to **Settings > Rules**.
2. In the list of rules, select the first checkbox in the first column to select all the rules.
3. Click **Disable All Rules**.
4. Confirm by clicking **Accept**.