--- title: "Muting XOps Stories" slug: "muting-xops-stories" tags: ["XOps"] updated: 2026-09-22T12:05:22Z published: 2026-09-22T12:05:22Z canonical: "knowledge.catonetworks.com/muting-xops-stories" --- > ## Documentation Index > Fetch the complete documentation index at: https://knowledge.catonetworks.com/llms.txt > Use this file to discover all available pages before exploring further. # Muting XOps Stories This article discusses how to create a rule that mutes XOps stories so that they do not appear on the Stories Workbench. ## Overview The XOps correlation engines (producers) analyze traffic data to find matches for potential threats or network degradation. If a match is identified, a story is generated in the [Stories Workbench](/v1/docs/reviewing-detection-response-xops-stories-in-the-stories-workbench) to help you understand and analyze the issue. If you do not want a story to be created, you can configure a Mute Stories rule. This reduces the generation of false positive stories and helps you focus your analysis on actual potential threats or network issues. Stories can be muted for a specific or unlimited time range Mute Stories rules are fully supported for stories generated by producers, such as: - Usage Anomaly - Cato Endpoint Alert - Microsoft Defender for Cloud Apps - Threat Prevention - Threat Hunting - Account Operations - Site Operations - Entra ID Alert - Wiz - SaaS Security - Cato Networks - Microsoft Endpoint Alert - DSPM Alerts - Microsoft Email Security - Predictive Insight - Google Applications You can see the full list of producers in the Detection & Response Policy > Mute Stories tab. For other story types, you can create mute stories rules based on a [limited set of conditions](/v1/docs/muting-xops-stories#muting-other-story-types). For a story to be muted, it must have an exact match or contain the predicates inserted in the Mute Stories rule. For example, if a rule contains 3 domains but only 2 are in the story, the story is muted. If a rule contains 2 domains and the story contains 3, it is not muted. Muted stories are not generated by default; however, this can be overridden by selecting it as a condition. **Note:** MDR customers can create and edit mute story rules for the Site Operations engine. If you wish to define mute stories for other engines, please contact [mdr@catonetworks.com](mailto:mdr@catonetworks.com). ### Prerequisites - An XOps license is required ## Muting Threat Prevention and Threat Hunting Stories You can define traffic from a trusted resource, which is then excluded from a story. For example, XOps stories are generated for the detection of potential scanning attempts, but the source of the scanning is known benign penetration testing. For Threat Prevention and Threat Hunting stories, a story is always created even when it is muted. Muting applies a mute flag to the story, ensuring it is excluded from reports and hidden from the Stories Workbench when the Threat Prevention or Threat Hunting filters are applied. Muted stories also do not trigger alerts by default according to the response policy There are two ways to add Mute Stories rules for Threat Prevention and Threat Hunting stories: - Create a rule in the [Detection & Response](/v1/docs/muting-xops-stories#showing-the-detection-response-mute-stories-rulebase) page - Create a rule from a story in the Stories Workbench. This method is helpful when you notice specific traffic in a story that you know is benign ## Muting UEBA Usage Anomaly and Events Anomaly Stories There are two ways to add Mute Stories rules for Usage Anomaly and Events Anomaly stories: - Create a rule in the [Detection & Response](/v1/docs/muting-xops-stories#showing-the-detection-response-mute-stories-rulebase) page - Create a rule from a story in the Stories Workbench. This method is helpful when you notice specific traffic in a story that you know is benign The following sections describe useful settings that are available for Usage Anomaly and Events Anomaly Mute Stories rules. #### Understanding Mute Stories Settings for Usage Anomaly Stories The XOps Usage Anomaly engine Identifies anomalies related to unusual usage in applications, and generates a story when an anomaly is detected. The Mute Stories policy lets you configure a rule for a Usage Anomaly story by specifying applications or application categories for the XOps engines to exclude. For example, if you know that a specific user uploads unusual amounts of data on OneDrive as part of their work requirements, create a rule configured with the specific **User** as the **Source** and **OneDrive** as the **Application**. It is possible for a Usage Anomaly story to involve more than one application. In such a case, the configured **Application** refers to the top application in the story. For example, if you configure the **Application** as **OneDrive**, this means that if the top application in the Usage Anomaly story is OneDrive, the XOps engine won't generate the story. However, if the top application is a different application, such as Dropbox, and OneDrive has the second-highest usage, then the story will still be generated. #### Understanding Mute Stories Settings for Events Anomaly Stories The XOps Events Anomaly engine detects anomalies that involve an entity on the network triggering an unusual number of security events, and generates a story when an anomaly is detected. The Mute Stories policy lets you configure a rule for an Events Anomaly story by specifying event types for the XOps engines to exclude. You can then further specify to exclude only the events generated by particular rules or IPS threats. For example, if a user generates an unusually large number of WAN Firewall events when performing known-benign activity, create a rule with the **User** configured as the **Source** and configure the **Events Anomaly Metric** as the **Event Type** of **WAN Firewall**. Then specify the rule within the WAN Firewall rulebase. ## Muting Site Operations Stories You can mute stories generated by specific network issues. For example, if you know a local ISP has a planned outage, you can mute stories generated by the Site down indication for the period of the outage. For Site Operations Stories, a story is always created even when it is muted. Muting applies a mute flag to the story, ensuring it is excluded from reports and hidden from the Stories Workbench when the Network Operations filter is applied. Muted stories also do not trigger alerts by default according to the response policy. For ILMM customers only, these story types are muted by default when the site’s links are not onboarded to the service: - Site Down - Link Down - ALT WAN Link Down - Quality SLA You can identify whether a story has been muted in the **Muted** column in the Incident Timeline of a story. ![Muted.png](https://cdn.document360.io/81d0367c-2b69-4ba8-b412-1c8f46ce677e/Images/Documentation/28977841879325.png?sv=2026-02-06&spr=https&st=2026-11-22T19%3A12%3A55Z&se=2026-11-22T20%3A12%3A55Z&sr=b&sp=r&sig=CQzVexL5M8muKeb3U8TqiBgZsfx%2FR41tnN5SSkQLGB4%3D) You can add Mute Stories rules for Site Operations stories by creating a rule in the [Detection & Response](/v1/docs/muting-xops-stories#showing-the-detection-response-mute-stories-rulebase) page. ## Muting Other Story Types You can mute other XOps story types that are not described in the sections above. This includes stories generated by the Generic Incident Producer, such as those based on [Cyera](/v1/docs/cyera-creating-the-xops-integration) and [Sentra](/v1/docs/sentra-configuring-the-xops-integration) integrations, as well as stories generated using other connectors for third-party integrations, such as the [Microsoft Defender for Endpoint](/v1/docs/microsoft-defender-for-endpoint-alerts-configuring-the-xops-integration) connector. For these story types, Mute Stories rules support only the **Producer** and **Indication ID** fields as matching conditions. This lets you mute stories from a specific producer, or mute stories generated for a specific indication. Other rule conditions are not supported. ## Items in a Detection & Response Mute Stories Rule The following table explains the items that you can use to define the settings for a Detection & Response Mute Stories rule. When you configure multiple objects in a setting, there is an OR relationship between them. For example, if there is a rule configured with sources including a **Site** and a **User**, the rule is applied when the traffic matches either the **Site** or the **User**. | Item | Description | | --- | --- | | **Producer** | The Detection & Response engine or engines the rule applies to. For more about these engines and the types of stories they detect, see [Using the Indications Catalog](/v1/docs/using-the-indications-catalog) | | **Indication ID** | The identifier for the indication used by the Detection & Response engines. Each **Indication ID** is associated with a Detection & Response engine query that identifies specific traffic parameters. If you define an **Indication ID**, the rule only excludes traffic from stories generated by the specific engine query associated with that **Indication ID**. If no **Indication ID** is defined, the traffic is excluded from all engine queries that match the rule settings. For more about Indications, see [Using the Indications Catalog](/v1/docs/using-the-indications-catalog). | | **Direction** (Threat Prevention, Threat Hunting, Usage Anomaly, and Events Anomaly stories) | Define the direction of the traffic flow that the rule applies to. Directions include: - **Inbound** - Traffic to your network originating at an external source - **Outbound** - Traffic from your network to an external source - **WANbound** - Traffic from your network to another site on your network - **All** of the above | | **Time Frame** | Select the time frame when the rule applies, or select **Unlimited** for the rule to continue to apply without expiration. When an expiration date is set: - For Threat Prevention and Threat Hunting stories the rule expires at the beginning of that date, in the time zone configured in the user profile settings in the Cato Management Application. - For Site Operations stories, you can select the time zone that the time frame applies to. Setting an expiration date is a recommended best practice for maintaining an effective security posture. | | **Source** | Source of the traffic for this rule. You can select one or more of the following **Source** types: - Threat Prevention and Threat Hunting stories - Site - IP - IP Range - User - Any - Site Operations - Site - Network Interface (LAN link) - WAN Link - Site Connection Type - Any | | **Device** (Threat Prevention, Threat Hunting, Usage Anomaly, and Events Anomaly stories) | The type of device the rule applies to, defined by operating system. | | **Destination** (Threat Prevention, Threat Hunting, Usage Anomaly, and Events Anomaly stories) | Destination of the traffic for this rule. You can select one or more of the following **Destination** types: - **IP** - **URL** - **Domain** - **FQDN** - **Application** - **Application Category** (for Usage Anomaly stories only) - **Any** For definitions of these objects, see [Reference for Rule Objects](/v1/docs/reference-for-rule-objects) | | **Events Anomaly Metric** (Events Anomaly stories) | Select the type of event to be muted. After you select the event type, you can specify a rule name or threat name. You can select one of the following event types: - **WAN Firewall** - **Internet Firewall** - **IPS** - **Anti-Malware** - **NG Anti-Malware** - **Any** | In addition to the above settings, the following information is shown for each Mute Stories rule: - **Author** - The user name of the user who created the rule. - **Created At** - Date the rule was created. ## Showing the Detection & Response Mute Stories Rulebase **To show the Detection & Response Mute Stories rulebase:** 1. From the navigation menu, click **Home > Detection & Response Policy**. ![Detection_Response_Allow_List.png](https://cdn.document360.io/81d0367c-2b69-4ba8-b412-1c8f46ce677e/Images/Documentation/28977841913501.png?sv=2026-02-06&spr=https&st=2026-11-22T19%3A12%3A55Z&se=2026-11-22T20%3A12%3A55Z&sr=b&sp=r&sig=UhMeAFN5W1ZZKznL4tezhpfsT4DNL02BmOkT4K0J5Wc%3D) ## Creating a Mute Stories Rule in the Detection & Response Page Add a new Mute Stories rule and configure the settings that define the traffic to be disregarded by the Detection & Response engines. ![Detection_Response_Allow_List_Add_to_Allowlist.png](https://cdn.document360.io/81d0367c-2b69-4ba8-b412-1c8f46ce677e/Images/Documentation/28977860324893.png?sv=2026-02-06&spr=https&st=2026-11-22T19%3A12%3A55Z&se=2026-11-22T20%3A12%3A55Z&sr=b&sp=r&sig=%2FwOKyVa6mVCmYz4eQOM8SRQVg1c8XQ%2BbSpkn1J7uZgw%3D) **To create a Detection & Response Mute Stories rule:** 1. From the navigation menu, click **Home > Detection & Response Policy**. 2. Select the **Mute Stories** tab. 3. Click **New**. The **Add to Mute Stories** panel opens. 4. Configure the settings for the rule as described above. 5. Click **Save**. The rule is added to the Mute Stories rulebase. ## Creating a Mute Stories Rule from a Story View the story drill-down in the Stories Workbench and use the **Story Actions** panel to create a Mute Stories rule. The following rule settings are autofilled based on data from the story: - **Direction** - **Source** - If the story contains multiple types of data for the source, they are all added in the **Source** setting. For example, if the story identified an **IP** and **Site** for a source, then both an **IP** and **Site** are autofilled in the **Source** section for the rule. - **Destination** - Autofilled based on the story **Targets** - If the story identified multiple **Targets**, they are all added in the **Destination** setting **To create a Mute Stories rule from a story:** 1. From the navigation menu, click **Home > Stories Workbench**. 2. Click the story to open the drill-down page for the story. 3. Click ![More_icon.png](https://cdn.document360.io/81d0367c-2b69-4ba8-b412-1c8f46ce677e/Images/Documentation/28977832907421.png?sv=2026-02-06&spr=https&st=2026-11-22T19%3A12%3A55Z&se=2026-11-22T20%3A12%3A55Z&sr=b&sp=r&sig=GJr56rA0vw5VKsUQQMsVK1bpXVaElh7iqEGvx4PR%2BPo%3D) to open the **Story Actions** panel. 4. Click **Add to New Mute Stories**. The **Add to New Mute Stories Rule** panel opens. ![Detection_Response_Allow_List_from_Story.png](https://cdn.document360.io/81d0367c-2b69-4ba8-b412-1c8f46ce677e/Images/Documentation/28977858122397.png?sv=2026-02-06&spr=https&st=2026-11-22T19%3A12%3A55Z&se=2026-11-22T20%3A12%3A55Z&sr=b&sp=r&sig=YfP%2BWtLvlVsepCufaTL9lqYI5F81w2yuFPO4Ex%2BysUU%3D) 5. Configure the settings for the rule as described above. 6. Click **Save**. The rule is added to the Mute Stories rulebase. 7. To show the Detection & Response Mute Stories rulebase, from the navigation menu click **Home > Detection & Response Policy**.