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

# Example: Creating a Suppression Rule for Sudo Events

|                       |           |              |             |             |
| --------------------- | --------- | ------------ | ----------- | ----------- |
| **Role Availability** | Read-Only | Investigator | **Analyst** | **Manager** |

In this example, we are going to create a suppression rule to avoid having a lot of <Tooltip tip="A program for UNIX-like computer operating systems that allows users to run programs with the security privileges of another user, by default the superuser.">sudo</Tooltip> <Tooltip tip="Any traffic or data exchange detected by LevelBlue products through a sensor or external devices such as a firewall.">events</Tooltip>. You can create this rule whenever you trust the origin <Tooltip tip="Reference to a computer on a network.">host</Tooltip>, or because you need to do maintenance. This way you will avoid noise in your list of events.

<Note>
  **Note:** You can also create your own rules from the Events page, which is an easier way to configure the matching conditions. See [Creating Suppression Rules from the Events Page](/documentation/usm-anywhere/user-guide/events/supression-rule) for more information.
</Note>

**To create a suppression rule for avoiding Sudo events**

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

2. Select **Create Orchestration Rule > Suppression 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.

   <Frame>
     <img src="https://mintcdn.com/levelblue-5324744e/JttNYaikKbN1las-/images/usm-anywhere/matchcombofiltsupp.webp?fit=max&auto=format&n=JttNYaikKbN1las-&q=85&s=ef7be78ac0d34c2a47ca89c8bc6813df" alt="" width="308" height="263" data-path="images/usm-anywhere/matchcombofiltsupp.webp" />
   </Frame>

   * **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.
   * **Alarms:** Use this packet type for console user alarms-based rules.

5. Select these property values:

   <Frame>
     <img src="https://mintcdn.com/levelblue-5324744e/3onSl9Btf_NxCVCb/images/usm-anywhere/examplesuppression.webp?fit=max&auto=format&n=3onSl9Btf_NxCVCb&q=85&s=a5af7054958186276fa21478b700fb63" alt="" width="951" height="532" data-path="images/usm-anywhere/examplesuppression.webp" />
   </Frame>

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

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

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.

8. Click **Next**.

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

   <Warning>
     **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.
   </Warning>

9. Enter a name for the rule.

10. (Optional.) Enter a description for identifying this rule.

11. 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>
      **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>

12. Click Save.

    The created rule displays in the list of rules. You can see it from **Settings > Rules**.  See [Suppression Rules from the Orchestration Rules Page](/documentation/usm-anywhere/user-guide/rules-management/suppression-rules) for more information.

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