> For the complete documentation index, see [llms.txt](https://appsecurity.gitbook.io/offensive/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://appsecurity.gitbook.io/offensive/appsec/auditing-and-compliance.md).

# Audit and Compliance

We should also understand topics of compliance audits and security benchmarks. This includes CIS, PCI DSS, DISA STIG and so on.

Not everybody knows them, but knowing them can make a big difference not just in front of the client. For instance we should know:

* What are the organizations who made them?
* What are they actually testing / bench-marking?
* When and why does it makes sense to comply with them?

Here’s a quick way to get up to speed:

**CIS**

* Center for Internet Security ([homepage](https://www.cisecurity.org/))
* CIS Benchmarks ([link](https://www.cisecurity.org/cis-benchmarks/))
* FAQ ([link](https://www.cisecurity.org/cis-benchmarks/cis-benchmarks-faq/))

**PCI DSS**

* Payment Card Industry ([homepage](https://www.pcisecuritystandards.org/))
* Data Security Standard ([link](https://www.pcisecuritystandards.org/document_library))
* FAQ ([link](https://www.pcicomplianceguide.org/faq/))

**DISA STIG**

* Defense Information Systems Agency ([homepage](https://www.disa.mil/))
* Security Technical Implementation Guides ([link](https://public.cyber.mil/stigs/))
* FAQ ([link](https://public.cyber.mil/stigs/faqs/))

**MSCT**

* Microsoft Security Compliance Toolkit ([link](https://docs.microsoft.com/en-us/windows/security/threat-protection/security-compliance-toolkit-10))

## Useful platforms

[SafeBase](https://safebase.io/) – предлагает комплаенс – предлагает набор соглашений, который вы можете себе перенять, тем самым описав процессы с точки зрения безопасности мы можем убедить кастомера, что у нас все ОК.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://appsecurity.gitbook.io/offensive/appsec/auditing-and-compliance.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.