> 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-xsiam/detect-investigate-and-respond-to-threats/cortex-advanced-email-security/cortex-advanced-email-security-threat-detection-and-issues/email-security-analytics-rules.md). # Email Security Analytics Rules Configure Cortex XSIAM Email Security Analytics Rules to detect suspicious email activity and create issues. The Email Security Analytics Rules page offers a consolidated view of all Analytics BIOC and XSIAM Analytics rules used in the Cortex Advanced Email Security module to keep your email domains secure. You can see every Analytics rule that could generate an email security issue and take action to customize the rules for your organization. Within this unified 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 XSIAM Analytics rules by disabling or enabling specific ones. * View more information for a selected analytics rule, including all its variants, and pivot to the Cortex Analytics Reference for the specific rule. The Email Security **Analytics Rules** page is in **Modules** → **Email Security** → **Email Security Detection Rules**. The page displays the following properties of Analytics rules: * Modification Time: When the rule was last changed. * Name * Severity: Severity of the basic variant. * Severity Variations: Number of different variants for the rule, including their respective severities. * Status * Type: XSIAM Analytics or XSIAM Analytics BIOC * Tags: Detector tag * Description * Mitre Att\&ck Tactic * Mitre Att\&ck Technique * \# of Issues: Number of issues generated by the rule in all its variants. * Activation Prerequisites * Creation Time * Global Rule ID Use the right-click menu for the following actions: * Disable or enable a rule to customize issue generation based on the Analytics rule. * View all the email security issues that were generated by applying this rule. * Show or hide all rows with a specific 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 **More information** to display the Analytics Alert Reference. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://cortex-docs.paloaltonetworks.com/cortex-xsiam/detect-investigate-and-respond-to-threats/cortex-advanced-email-security/cortex-advanced-email-security-threat-detection-and-issues/email-security-analytics-rules.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.