> For the complete documentation index, see [llms.txt](https://docs.prismacloud.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.prismacloud.io/public-sector/disa-stig-support/disa-stig-compliance-template/mapping.md).

# Mapping

Prisma Cloud offers a compliance template for DISA STIGs. In many cases, DISA STIG checks map to checks already supported in the product. In some cases, we’ve implemented checks specifically to support STIGs. When configuring your compliance policy, simply select the DISA STIG template to enable all relevant checks to Alert.

| STIG Severity | Compute Severity |
| ------------- | ---------------- |
| CAT I         | High & Critical  |
| CAT II        | Medium           |
| CAT III       | Low              |

As new DISA STIGs are finalized and published they will be incorporated into the DISA STIG temaplate.

## DISA STIG\_ID mapping to Prisma Cloud Compute Compliance Check ID

Eight new compliance checks have been specifically added for the DISA STIG checks, in addition to 49 existing checks that already align with the STIG checks. The remaining 43 STIG checks are not applicable. For example, STIG ID: DKER-EE-002180, SAML integration, must be enabled in Docker Enterprise Universal Control Plane.

See the spreadsheet [here](https://docs.google.com/spreadsheets/d/1bhrzwBErrqqIW4xUEpOQQ07_JGwK_fxIh56JhEEJZDQ/edit?usp=sharing).


---

# 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://docs.prismacloud.io/public-sector/disa-stig-support/disa-stig-compliance-template/mapping.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.
