> 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/documentation/documentation-zh/bao-hu-yu-zhi-li/overview/supported-frameworks.md).

# 受支持的框架

Dispel 合规支持广泛的框架。

Dispel 随附以下框架目录和配置文件。后续版本将陆续添加新框架。

| 框架                        | 配置文件 / 基线           | 备注                                           |
| ------------------------- | ------------------- | -------------------------------------------- |
| **NIST SP 800-53 Rev 5**  | 低、中、高、隐私            | 完整控制目录，包括控制增强项                               |
| **NERC CIP**              | 当前生效的版本             | 映射至 NIST 800-53，以便进行跨框架协调                    |
| **NIS2**                  | 实施条例 (EU) 2024/2690 | 由 Dispel 编写、与 NIST 800-53 进行交叉映射的 OSCAL 目录   |
| **NIST 网络安全框架 (CSF) 2.0** | 核心                  | 覆盖至子类别级别                                     |
| **SANS 五项关键控制**           | 核心                  | 用于快速评估安全态势的高优先级控制集                           |
| **IEC 62443-3-3**         | SL1–4，基线            | 由 Dispel 编写、与 IEC 62443-3-3 进行交叉映射的 OSCAL 目录 |

{% hint style="info" %}
**关于 NIS2 目录的说明**

欧盟 NIS2 指令尚无由 ENISA 或其他权威机构发布的 OSCAL 目录。由于 NIS2 是 Dispel 的多家客户目前用于报告合规情况的监管制度，Dispel 发布了一个一方 OSCAL 目录，该目录直接根据法律文本编制—— *实施条例 (EU) 2024/2690* ——其中规定了主管机关在 NIS2 审计期间核查的网络安全风险管理操作措施。

<mark style="background-color:$danger;">**请务必咨询您所在机构的监管与合规团队，以确保遵守 NIS2。我们的目录仅代表一种解读，不构成法律或监管建议。您须自行负责确保遵守所有适用的法律法规。**</mark>

Dispel 的 NIS2 目录通过 ENISA 发布于其 **《网络安全风险管理措施技术实施指南》**&#x4E2D;公布的映射表，与 NIST SP 800-53 进行了交叉映射。这意味着，为任何 800-53 控制收集的证据都会自动计入相应的 NIS2 措施，反之亦然——无需维护单独的证据管道。审计员和主管机关会收到符合 NIS2 结构的 OSCAL 组件定义，其中每项措施都可追溯至其所落实的《实施条例》条款。

如果 ENISA 将来发布官方的 NIS2 OSCAL 目录，Dispel 将采用该目录，并迁移现有评估，同时保留完整历史记录。
{% 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/documentation/documentation-zh/bao-hu-yu-zhi-li/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.
