> 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-xpanse/reference/monitor-compliance-violations.md).

# Monitor Compliance Violations

The Attack Surface Compliance Violations Dashboard helps customers better understand how the issues on their external network impact compliance controls.

{% hint style="info" %}

### Note

Not all attack surface rules are mapped to the compliance frameworks as they are released. Cortex Xpanse continues to update the mapping as frequently as possible in order to ensure the dashboard is up to date based on the latest policies released in the platform.
{% endhint %}

The **Attack Surface Compliance Violations** dashboard takes a compliance-focused lens and applies it to the attack surface rules in Cortex Xpanse, so customers can better understand how the alerts and incidents on their external network impact compliance controls. The dashboard displays assessments for the following control families:

* NIST 800-53
* NIST 800-171
* CMMC L1-L5
* CMMC L1-L3

To view the **Attack Surface Compliance Violations Dashboard**, navigate to **Dashboards** → **Other Dashboards** → **Attack Surface Compliance Violations Dashboard**. Within each widget, select a control family from the drop-down menu to filter the data.

Cortex Xpanse worked with its internal subject matter experts as well as third party experts to develop these mappings against our attack surface rules assuming that all assets have been inventoried already. The mapping focuses on which rules may need to be reviewed because they could have led to a given service or issue being exposed to the Internet. As part of your investigation via the security impact analysis (SIA), give consideration for each control in each framework that is mapped as applicable to your security and compliance objectives.

Note that not all compliance violations can be detected from our scan data. Cortex Xpanse provides an external view of your attack surface. Some controls require data from internal scans or checks against internal controls and processes where Xpanse does not have visibility. The following sections list these specific controls for which Xpanse cannot make a determination regarding compliance:

* [NIST 800-53 Unevaluated Controls](/cortex-xpanse/reference/monitor-compliance-violations/nist-800-53-unevaluated-controls.md)
* [NIST 800-171 Unevaluated Controls](/cortex-xpanse/reference/monitor-compliance-violations/nist-800-171-unevaluated-controls.md)
* [CMMC L1-L5 Unevaluated Controls](/cortex-xpanse/reference/monitor-compliance-violations/cmmc-l1-l5-unevaluated-controls.md)


---

# 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-xpanse/reference/monitor-compliance-violations.md?ask=<question>&goal=<user_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.