> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/cortex-xdr-5.x/detect-investigate-and-respond-to-threats/threat-management/analytics/view-and-manage-analytics-rules.md). # View and manage Analytics rules The Analytics Rules page offers a consolidated view of all Analytics BIOC and XDR Analytics rules which are crucial to your organization's security posture. Designed to provide complete transparency, this centralized hub enables EDR experts and SOC analysts to gain a comprehensive understanding of every Analytics rule that could generate an issue and take action accordingly. For more information, see [Analytics issues and Analytics BIOCs](#UUID-0aab368a-0f6a-d485-4fba-1896599ed0c1). Within the unified Analytics rules table, you can leverage powerful capabilities to manage and investigate Analytics rules effectively. * Get an understanding of all the rules that generated an issue in one place. * Filter rules by name or description for seamless integration with issue investigations. * Filter rules by any column, including "Variant Severities" to quickly locate rule variants associated with specific severity criteria. * Order by any column, enabling you to prioritize and evaluate issues based on severity, name, modification time, and other critical factors. * Fine-tune your XDR Analytics rules by disabling or enabling specific ones, and changing the severity of the rules or the rule variants. * View more information for a selected analytics rule, including all its variants, and pivot to the [Cortex Analytics Reference](https://cortex-docs.paloaltonetworks.com/analytics-alerts) for the specific rule. The **Analytics Rules** page is under **Threat Management** → **Detection Rules**. Some of the displayed properties are listed below: | | | | -------------------------- | -------------------------------------------------------------------------------- | | Column name | Description | | Modification Time | When the rule was last changed | | Name | Name of the rule | | Severity | Severity of the basic variant | | Severity Variations | Number of different variants for the rule, including their respective severities | | Severity Modification time | Last time the severity for any of the rule’s variants was changed | | Severity Modification user | Latest user who changed the severity of any rule variant | | Severity Modified | Yes/No indicating if the severity for any of the rule variants was changed | | Status | Enabled or Disable | | Type | XDR Analytics or XDR Analytics BIOC | | Tags | Detector tag | | Description | Cortex XDR defined description of the rule | | Mitre Att\&ck Tactic | Goals an adversary is trying to achieve during a cyberattack | | Mitre Att\&ck Technique | Adversary tactics and techniques used in cyberattacks | | # of Issues | Number of issues generated by the rule in all its variants | Use the right click menu for the following actions: * **Disable** or **enable** a rule to customize issue generation based on the Analytics rule. * **View Rule** or **Edit Rule** depending on your permissions. #### View Rule View the rule with all its variants, including their respective descriptions, tags, and severities in the **View Analytics Rule** screen. * For more information about the Mitre Att\&ck techniques and tactics, click the tag to display its explanation in the MITRE ATT\&CK database. * For more information about the rule, click **View Rule**, and click **More information** to display the Analytics Alert Reference. #### Edit Rule Edit Rule is available only if you have the necessary Edit permissions. View the rule details as described in the **View Rule** section. Customize the severity of the issues triggered by the analytics rule, or any of its variants, to align with your organizational needs in the **Edit Analytics Rule** screen. Some of the reasons you may want to change a severity level are below, although the list is not exhaustive. * Lowering a severity for specific rules, suspected as false positives, to reduce the number of issues raised by Cortex XDR. * Raising a severity for specific rules, to trigger generating issues for a specific behavior in Cortex XDR. * Customizing the severity of a specific logic to be immune to content updates, thus keeping the same custom severity, agnostic to Cortex XDRsuggestion. Edit the severity of a rule or one or more of its variants: 1. Right click the rule and select **Edit Rule**. 2. In the variant you want to change, select the severity you want.

Warning

Changing the default severity may result in issues not being triggered or too many issues being triggered. Please consider this carefully before you change the severity recommended by Cortex XDR. Any responsibility for not getting issues triggered as a result of changing the severity will be yours.

If the severity determined by Cortex XDR was changed, to revert to the default, click **Reset to default** next to the severity.

Note

The default severity is updated by content updates. If a content update determines a new default severity for the rule that's the same as the value you had previously determined, you won't have the option to reset to default. For example, if the default was Informational, and you changed the severity to Medium, and after a content update Cortex XDR now determines the default to be Medium, the Reset to default option won't be displayed.

3. Click **Save**. * **Show rows** or **hide rows** with a specific rule. * **Copy entire row**. {% hint style="info" %} ### Note When you select multiple rows, you can only enable or disable the selected rules. {% endhint %} --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://cortex-docs.paloaltonetworks.com/cortex-xdr-5.x/detect-investigate-and-respond-to-threats/threat-management/analytics/view-and-manage-analytics-rules.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.