> For the complete documentation index, see [llms.txt](https://docs.halosecurity.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.halosecurity.com/docs/platform/compliance.md).

# PCI Compliance

Manage PCI compliance for your assets.

Navigate to your dashboard and select the [PCI dashboard](https://app.halosecurity.com/user/security/dashboard/pci) to monitor and manage PCI compliance status. From here, you can easily see the status of targets that are in scope for PCI scanning and whether they are currently in compliance. If any reports have been reviewed and passed, you will be able to download them.

After the targets in PCI scope have been scanned, you may submit a report to be reviewed.

## Generate Report

Click the [**Generate Report**](https://app.halosecurity.com/user/security/pci/report) button or the **+** icon in the status card to generate a new PCI report.

Generating a report begins the PCI attestation process. During this process, you will be required to answer questions to the following:

* **Out of Scope targets**: A list of targets that have not been scoped for PCI compliance will be listed. Verify that none of these targets should fall within PCI scope.
* **Special Notes**: Certain software that may cause a risk if it is not implemented properly will be listed here. You must attest that these items have been securely implemented.
* **Load Balancers**: If load balancers are part of your your in-scope PCI infrastructure you will answer that here. If they are in use, the systems behind them need to be properly synchronized in terms of configurations.
* **Attestation**: Finally, you must name the report and give your name and job title.

Clicking "I Attest" will then submit the report for review.

## Review Process

All reports must be reviewed before they can be submitted to your acquiring banks or QSA. After a report has been attested to and submitted, it will go through the review process. You will then be notified whether the report has passed or been rejected.

## PCI Security Standards Council

For more information about PCI compliance and standards, please visit the PCI Security Standards Council:

{% embed url="<https://www.pcisecuritystandards.org>" %}

## Pages

<https://app.halosecurity.com/user/security/pci/>


---

# 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.halosecurity.com/docs/platform/compliance.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.
