> 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 第 5 版** | 低、中、高、隐私 | 包含控制增强项的完整控制目录 |
| **NERC CIP** | 当前生效版本 | 映射到 NIST 800-53，以便进行跨框架对照 |
| **NIS2** | 实施条例（EU）2024/2690 | Dispel 编写的 OSCAL 目录，与 NIST 800-53 交叉映射 |
| **NIST 网络安全框架（CSF）2.0** | 核心 | 子类别级覆盖 |
| **SANS 5 项关键控制** | 核心 | 用于快速态势评估的高优先级控制集 |
| **IEC 62443-3-3** | SL1 - 4，基线 | Dispel 编写的 OSCAL 目录，与 IEC 62443-3-3 交叉映射 |
{% hint style="info" %}
**关于 NIS2 目录的说明**
欧盟 NIS2 指令并没有由 ENISA 或任何其他权威机构发布的 OSCAL 目录。由于 NIS2 是若干 Dispel 客户目前正在据以报告的监管制度，Dispel 发布了一个直接源自法律文本的第一方 OSCAL 目录—— *实施条例（EU）2024/2690* ——其中包含主管当局在 NIS2 审计中核查的运营性网络安全风险管理措施。
**请始终咨询您自己的法规与合规团队，以确保您符合 NIS2。我们的目录仅为一种解读，不构成法律或监管建议。您须自行负责确保遵守所有适用的法律法规。**
Dispel 的 NIS2 目录使用 ENISA 在其发布的映射表与 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=&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.