> For the complete documentation index, see [llms.txt](https://docs.dispel.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dispel.com/secure-and-govern/overview/supported-frameworks.md).

# Supported Frameworks

Dispel Compliance supports a wide range of frameworks.

Dispel ships with the following framework catalogs and profiles. New frameworks are added in subsequent releases.

| Framework                                  | Profile / Baseline                     | Notes                                                       |
| ------------------------------------------ | -------------------------------------- | ----------------------------------------------------------- |
| **NIST SP 800-53 Rev 5**                   | Low, Moderate, High, Privacy           | Full control catalog including control enhancements         |
| **NERC CIP**                               | Versions currently in effect           | Mapped to NIST 800-53 for cross-framework reconciliation    |
| **NIS2**                                   | Implementing Regulation (EU) 2024/2690 | Dispel-authored OSCAL catalog cross-walked to NIST 800-53   |
| **NIST Cybersecurity Framework (CSF) 2.0** | Core                                   | Subcategory-level coverage                                  |
| **SANS 5 Critical Controls**               | Core                                   | High-priority control set for rapid posture assessment      |
| **IEC 62443-3-3**                          | SL1 - 4, Baseline                      | Dispel-authored OSCAL catalog cross-walked to IEC 62443-3-3 |

{% hint style="info" %}
**A note on the NIS2 catalog**

The EU NIS2 Directive does not have an OSCAL catalog published by ENISA or any other authoritative body. Because NIS2 is the regulatory regime several Dispel customers are now reporting against, Dispel publishes a first-party OSCAL catalog derived directly from the legal text — *Implementing Regulation (EU) 2024/2690* — which contains the operational cybersecurity risk-management measures that competent authorities check against during a NIS2 audit.

<mark style="background-color:$danger;">**Always consult your own regulatory and compliance team to ensure you are complying with NIS2. Our catalog is an interpretation and does not constitute legal or regulatory advice. You are solely responsible for ensuring your compliance with all applicable laws and regulations.**</mark>

The Dispel NIS2 catalog is cross-walked to NIST SP 800-53 using the mapping table published by ENISA in its **Technical Implementation Guidance on Cybersecurity Risk Management Measures**. This means evidence collected for any 800-53 control automatically contributes to the corresponding NIS2 measure, and vice versa — there is no separate evidence pipeline to maintain. Auditors and competent authorities receive a NIS2-shaped OSCAL Component Definition that traces every measure back to the Implementing Regulation article it implements.

If ENISA publishes an official NIS2 OSCAL catalog in the future, Dispel will adopt it and migrate existing assessments without loss of history.
{% endhint %}


---

# 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.dispel.com/secure-and-govern/overview/supported-frameworks.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.