> ## 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

<Icon icon="users" iconType="solid" /> Role Availability | ❌ Read-Only ✔️ Analyst ✔️ Manager

**To create a response action rule**

1. 1. Go to **Settings > Rules**.

2. 2. Select **Create Orchestration Rule > Create Response Action Rule**.3.

   <Frame>
     <img src="https://mintcdn.com/levelblue-5324744e/jQPcuDOyVbjBzeJd/images/usm-central/createresponseactionrule_thumb_0_60.webp?fit=max&auto=format&n=jQPcuDOyVbjBzeJd&q=85&s=aa92c66cef4bc580086c46af723a036b" alt="" width="90" height="60" data-path="images/usm-central/createresponseactionrule_thumb_0_60.webp" />
   </Frame>

3. Enter a name for the rule.

4. Select a deployment.

5. Select an Action Type:

   * **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 that can be used for a forensic investigation, so you can focus on fast response and remediation. See [LevelBlue Agent Events and Queries](/usm-anywhere/agents/agent-query) for more information.

   * **Authenticated Asset Scanner**: See [Performing Vulnerability Scans](/usm-anywhere/user-guide/vulnerability-assessment/perf-vulnerability-scans) for more information.

   * **Cisco Umbrella**: This is used to stop current and emergent threats over all ports and protocols. See [BlueApp for Cisco Umbrella Actions](/usm-anywhere/alienapps-guide/cisco-umbrella/actions-alienapp-cisco-umbrella) for more information.

     <Note>
       This option displays if your environment has Cisco Umbrella Events.
     </Note>

   * **LevelBlue <Tooltip tip="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.">Forensics</Tooltip> and Response App**: See [Scheduling a Forensics and Response Job](/usm-anywhere/alienapps-guide/forensics-response/log-collect-blueapp-forensics-resp) for more information.

6. Click **Add Condition** 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>

   <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.
   </Note>

7. (Optional.) Click **Add Group** to group your conditions.

   <Note>
     See [Operators in the Orchestration Rules](/usm-anywhere/user-guide/rules-management/orchestration-rules-operators) for more information.
   </Note>

8. 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.

9. (Optional.) Click the **More** link to include a multiple occurrence parameter.

10. 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 <Tooltip tip="Alarms provide notification of an event or sequence of events that require attention or investigation.">alarm</Tooltip> for an <Tooltip tip="An incident-type categorization that may be a precursor to other actions or stages of an attack.">unauthorized access</Tooltip> attempt when a failed <Tooltip tip="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).">SSH</Tooltip> <Tooltip tip="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.">login</Tooltip> occurs three times within a five-minute window.
    </Note>

11. Click **Save Rule**.

    The created rule displays in the list of rules.

    <Warning>
      It takes a few minutes for an orchestration rule to become active.
    </Warning>

**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 deployment**

1. Go to **Settings > Rules**.
2. In the left navigation pane, click **Response Action Rules**.
3. Click the box **Deployment**.
4. Select **All Rules**, **Enabled**, or **Disabled**.

**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. On the left navigation pane, click **Response Action Rules**.
3. Click the <img src="https://mintcdn.com/levelblue-5324744e/ZS7tUvuIZXE1ELcm/images/usm-central/pencil-new.svg?fit=max&auto=format&n=ZS7tUvuIZXE1ELcm&q=85&s=ef34511f95396df10c672cb09965a4d6" className="inline m-0" width="24" height="24" data-path="images/usm-central/pencil-new.svg" /> icon of the rule you want to edit.
4. Modify the data of the items that need to be modified.
5. Click **Save Rule**.

**To delete a response action rule**

1. Go to **Settings > Rules**.
2. On the left navigation pane, click **Response Action Rules**.
3. Click the <img src="https://mintcdn.com/levelblue-5324744e/cXQBEU4dvbfLKeHt/images/usm-central/trash-alt.svg?fit=max&auto=format&n=cXQBEU4dvbfLKeHt&q=85&s=fecf181b20d0b4c6b4c73a22fa1e6d45" className="inline m-0" width="24" height="24" data-path="images/usm-central/trash-alt.svg" /> icon of the rule you want to delete.
4. Confirm by clicking **Accept**.

**To enable a response action rule**

1. Go to **Settings > Rules**.
2. On the left navigation pane, click **Response Action Rules**.
3. Click the <img src="https://mintcdn.com/levelblue-5324744e/cXQBEU4dvbfLKeHt/images/usm-central/toggle-off-new.svg?fit=max&auto=format&n=cXQBEU4dvbfLKeHt&q=85&s=71f6047f03fc3b253f63cd97a7480d67" className="inline m-0" width="32" height="16" data-path="images/usm-central/toggle-off-new.svg" /> icon of the rule you want to enable.

**To disable an response action rule**

1. Go to **Settings > Rules**.
2. On the left navigation pane, click **Response Action Rules**.
3. Click the <img src="https://mintcdn.com/levelblue-5324744e/cXQBEU4dvbfLKeHt/images/usm-central/toggle-on-new.svg?fit=max&auto=format&n=cXQBEU4dvbfLKeHt&q=85&s=7764d181eb11032a60a4736a445697ed" className="inline m-0" width="32" height="16" data-path="images/usm-central/toggle-on-new.svg" /> icon of the rule you want to disable.

**To enable all response action rules**

1. Go to **Settings > Rules**.
2. On the left navigation pane, click **Response Action Rules**.
3. In the list of rules, select the first checkbox in the first column to select all the rules.
4. Click **Enable All Rules**.

**To disable all response action rules**

1. Go to **Settings > Rules**.
2. On the left navigation pane, click **Response Action Rules**.
3. In the list of rules, select the first checkbox in the first column to select all the rules.
4. Click **Disable All Rules**.
5. Confirm by clicking **Accept**.
