> 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/cloud-security/cortex-cloud-saas-security/detection-rules.md).
# Detection Rules
View Cloud Security Posture Rules in Cortex XSIAM to detect SaaS application risks.
Detection Rules help you identify policies that are already in place and available out-of-the-box to help you remediate configuration issues with SaaS applications. Follow the steps below to view SaaS Detection Rules.
1. Navigate to **Modules > SaaS Security > Detection Rules**. This takes you to the Cloud Posture Security Rules page.
2. Here you can select **SaaS or AI > Filter In** to see a full list of available out-of-the-box rules.
3. Select a Rule to view more details. Options include:
4. **Rule Details**: Displays a detailed description of the Rule and outlines execution scope.
5. **Compliance Controls**: Maps this rule's execution logic to framework controls (such as SOC 2, ISO 27001, or CIS Benchmarks) for compliance audits.
---
# 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/cloud-security/cortex-cloud-saas-security/detection-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.