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

# Compliance reporting

Compliance reporting in Devolutions PAM generates audit trails on access, authentication, and privileged activity to meet standards like ISO 27001 and SOC 2.

**Compliance reporting** provides evidence that organizational systems and processes meet regulatory or industry-specific standards. These [reports](/pam/concepts/reporting-and-dashboards.md) typically include data on access control, authentication, auditing, and privileged account activity, helping organizations demonstrate compliance with frameworks like ISO 27001, SOC 2, HIPAA, or GDPR.

In Devolutions products, particularly Devolutions PAM and Devolutions Server, compliance reporting is supported through detailed auditing, role-based access control, and activity logging. Reports can be generated to show who accessed which resource, when, and under what circumstances, making it easier to respond to internal audits or external regulatory reviews.

By centralizing and automating these reports, Devolutions helps reduce manual effort, improve transparency, and ensure accountability in privileged access management practices.

#### Compliance reporting aliases

* Regulatory reporting
* Audit compliance
* Standards-based reporting

#### Related topics

* [Logs, reports, and audits](https://docs.devolutions.net/rdm/concepts/advanced-concepts/logs-reports-and-audits)
* [Permissions/RBAC/Roles](https://docs.devolutions.net/rdm/concepts/advanced-concepts/permissions-rbac-and-roles)
* [Security](https://docs.devolutions.net/rdm/concepts/advanced-concepts/security)

#### See also

* [Devolutions Blog – Decoding PAM: Core concepts and application](https://blog.devolutions.net/2024/08/decoding-pam-core-concepts-and-application/?utm_source=chatgpt.com)


---

# 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.devolutions.net/pam/concepts/compliance-reporting.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.