> For the complete documentation index, see [llms.txt](https://help.aikido.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.aikido.dev/compliance-and-reporting/reports/security-audit-report.md).
# Security Audit Report
The [Security Audit Report](https://app.aikido.dev/reports/audit-reports/external/create) gives you a structured overview of your current security posture. It is designed for sharing with customers, auditors, leadership, or internal stakeholders who need a clear summary of how security is managed.
You choose which sections to include before generating the report. This allows you to tailor it to a specific audience, such as a sales prospect, compliance audit, or board update.
## When to use this report
Use the Security Audit Report when you need to:
* Respond to a customer security questionnaire
* Provide evidence during an audit
* Document your current compliance coverage
## Available Sections
You can include any combination of the following fields.
**Aikido Benchmark**
**OWASP Top 10**
**SLA Compliance**
**Scan History**
**Issue Insights**
**Open Issues Snapshot**
**Cloud Compliance**
**Compliance Frameworks**
You can include summaries for supported frameworks and standards. These sections show which topics you currently comply with based on your configured checks.
Supported frameworks include:
* ISO 27001:2022
* SOC 2
* CIS v8.1 Controls
* CIS AWS Benchmark
* NIS2 Directive
* NIST 800-53
* PCI DSS v4.0
* HIPAA
* DORA
* HITRUST LVL3
* GDPR
* ENS
* UK Cyber Essentials
This section is useful for procurement reviews, enterprise sales, and audit preparation.
---
# 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://help.aikido.dev/compliance-and-reporting/reports/security-audit-report.md?ask=&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.
