> ## 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.
# Filtering Rules from the Orchestration Rules Page
| | | | | |
| --------------------- | --------- | ------------ | ----------- | ----------- |
| **Role Availability** | Read-Only | Investigator | **Analyst** | **Manager** |
USM Anywhere enables you to make the sensor drop future events that match the rule. These future events are neither correlated nor stored. Through these rules, you are able to define which event data you are going to store in USM Anywhere. You pay for the data you use, so discarded event information is not stored and does not count against the service-level tier of an account. This rule runs on a sensor and control node. The action of this rule has no recovery, so you must be careful when creating the rule. This action can cause a user-generated data loss environment.
**Note:** Filtering rules are not retroactive. The rule applies to future items and it does not apply to previous items, even if those items follow the rule.
**Important:** You can't use a correlation list when you create a filtering rule.
**To create a rule for filtering events**
1. Go to **Settings > Rules**.
2. Select **Create Orchestration Rule > Filtering 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.
* **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. Click Save.
The created rule displays in the list of rules. You can see it from **Settings > Rules**. See [Orchestration Rules](/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 test the match criteria of a filter rule**
1. Create a test event suppression rule.
2. Add the desired match criteria for the target filter rule action.
3. Enable the rule.
4. Go to Settings > Rules to verify that the rule is working as desired.
5. In the All Orchestration Rules page, click the 
icon of the filter rule you want to test.
The events, which triggered the rule and are suppressed, display.
6. Create a filtering rule with the exact same match criteria if the event information displayed is correct. If the event information displayed is not correct, modify the suppression rule match criteria until the correct values are found that suppresses the correct event data. Then generate the filter rule.
**To filter filtering rules by name**
1. Go to **Settings > Rules**.
2. Click the box next to Filter By.
3. Enter your search.
**To filter filtering 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 filtering 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 filtering 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 filtering rule**
1. Go to **Settings > Rules**.
2. Click the 
icon of the rule you want to enable.
**To disable a filtering rule**
1. Go to **Settings > Rules**.
2. Click the 
icon of the rule you want to disable.
**To enable all filtering 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 filtering 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**.