> 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.md).

# DISA STIG Compliance Template

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.

Release v21\_04\_412 include the Docker Enterprise 2.x Linux/UNIX STIG compliance checks into the [“DISA STIG” compliance template.](https://docs.paloaltonetworks.com/prisma/prisma-cloud/21-04/prisma-cloud-compute-edition-admin/compliance/disa_stig_docker_enterprise.html) When you create a new compliance policy and select the DISA STIG compliance template, you will automatically receive alerts based on the checks aligned with the STIG. The mapping of the STIG\_ID to Prisma Cloud Compute Compliance Check ID can be found [here.](https://docs.prismacloud.io/public-sector/disa-stig-support/disa-stig-compliance-template/mapping.md)

## Release STIG findings

Every release of Prisma Cloud Compute we perform an [SCAP](https://csrc.nist.gov/projects/security-content-automation-protocol/) scan of the Console and Defender images. The scan is performed with [OpenSCAP](https://www.open-scap.org/) using the [Compliance as Code](https://github.com/ComplianceAsCode) benchmark checks:

* Benchmark URL: scap-security-guide-\<latest>/ssg-rhel8-ds.xml
* Benchmark ID: xccdf\_org.ssgproject.content\_benchmark\_RHEL-8
* Profile ID: xccdf\_org.ssgproject.content\_profile\_stig

All Prisma Cloud Compute findings are posted [here.](https://github.com/PaloAltoNetworks/pc-docs-md/tree/main/compute-edition/public-sector/release-findings/release-findings.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://docs.prismacloud.io/public-sector/disa-stig-support/disa-stig-compliance-template.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.
