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

# Creating SentinelOne Response Action Rules

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

You can create orchestration rules in USM Anywhere that automatically trigger a SentinelOne response action when events or alarms, match the criteria that you specify. This way, you can automate the way you filter IP addresses into the policies within the SentinelOne UI.

After you create a rule, new events or alarms that match the rule conditions will trigger the SentinelOne response action to create a new incident. The rule does not trigger for existing events or alarms.

You can create a new rule as follows:

* **From the Rules page**: The Rules page provides access to all of your orchestration rules. The Orchestration Rules list includes suppression rules, alarm rules, event rules, filtering rules, notification rules, and response action rules. You can create new rules using the specific matching conditions that you define, as well as edit, delete, and enable or disable rules. See [Orchestration Rules](/documentation/usm-anywhere/user-guide/rules-management/orchestration-rules) for more information about managing orchestration rules.

  Go to **Settings > Rules** and select **Response Action Rules** on the left navigation panel. Then click **Create Response Action Rule** to define the new rule.

* **From the App**: Go to the BlueApp for SentinelOne page and click the **Rules** tab. Click **Create New Rule** to define the new rule.

**To define a new SentinelOne response action rule**

1. Enter a name for the rule.

2. Select the App Action for the rule and specify the information for the SentinelOne incident.

   The SentinelOne parameters that you set will depend on which of the following actions you select:

   * Create a New Incident from an Alarm

   This is the default action if you create the rule after applying a SentinelOne response action to an alarm. Use this action to run a new SentinelOne rule for the addresses of a new alarm that satisfies the matching criteria.

   * Create a New Issue from Event-Based Orchestration

   Use this action to add information to the designated SentinelOne groups based on an incident for any event that satisfies the matching criteria.

3. At the bottom of the dialog box, set the Rule Condition parameters to specify the criteria for a matching alarm or event to trigger the rule.

   <Frame>
     <img src="https://mintcdn.com/levelblue-5324744e/MlnJpGwLYAWOIbAS/images/usm-anywhere/rules-conditions.webp?fit=max&auto=format&n=MlnJpGwLYAWOIbAS&q=85&s=ab8b4ad291c81ed750be057ef5b00663" alt="" width="576" height="192" data-path="images/usm-anywhere/rules-conditions.webp" />
   </Frame>

   * If you create the rule from an applied action, this section provides suggested property/value pairs from the selected alarm or event that you can use as conditions for the rule. Click the <img src="https://mintcdn.com/levelblue-5324744e/jTImDFBjBH7kNNGB/images/central-any-app/buttons/trash-alt.svg?fit=max&auto=format&n=jTImDFBjBH7kNNGB&q=85&s=7fcb12066bec17b51a7ebd4cad626542" className="inline m-0" width="24" height="24" data-path="images/central-any-app/buttons/trash-alt.svg" /> icon to delete the items that you do not want to include in the matching conditions. You can also add other conditions that are not suggested.
   * If you create the rule from the Rules page, you must use the Add Condition and Add Group functions to define the property/value pairs that you want to use as conditions for the rule.
   * At the bottom of the dialog box, click **More** to display the optional multiple occurrence and window length parameters.

   <AccordionGroup>
     <Accordion title="Conditional Expression">
       Select an operator and add one or more conditions to form the conditional expression. You can include a condition group to evaluate a subset of conditions. The Current Rule pane displays the constructed expression in standard syntax. The box displays a red border if the expression is syntactically invalid as currently specified. A valid expression is required to save the rule definition.

       Select the operator used to determine the match for multiple conditions:

       * **AND**: Match all conditions.
       * **OR**: Match any one condition.
       * **AND NOT**: Exclude items matching all conditions after the first.
       * **OR NOT**: Include all items that do not match any conditions after the first.

       Click **Add Condition** to add a condition. For each condition, specify the field name, evaluator, and value. If the evaluation returns true for the condition, it is a match.

       Click **Add Group** to add a condition group. A new group includes a condition and its own operator used to match the conditions within the group. You can nest condition groups.
     </Accordion>

     <Accordion title="Occurrences">
       Specify the number of event or alarm occurrences that produce a match on the conditional expression to trigger the rule. The default value is 1. You can enter the number of occurrences or use the arrow to scroll the value up or down.

       USM Anywhere uses this in conjunction with the Length option to specify the number of occurrences within a time period that will trigger the rule. For example, you can define a rule to trigger for an unauthorized access 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> login occurs three times within a five-minute window.
     </Accordion>

     <Accordion title="Length">
       Specify the length of the window to identify a match for multiple occurrences. Enter the number and choose a time unit value of seconds, minutes, or hours. This time period identifies the amount of time that transpires from the first occurrence to the last occurrence. If the number of occurrences is not met within this period, the rule does not trigger.
     </Accordion>
   </AccordionGroup>

4. Click **Save Rule**.

5. In the confirmation dialog box, click **OK**.