> 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/regulatory-framework-mappings/master.md).

# Introduction

This guide shows how Dispel's technology supports regulatory and framework requirements and guidelines.

## Welcome

This handbook will walk you through cybersecurity regulatory frameworks specific to various industries, and explain how Dispel aligns to their stated requirements. 

Regulatory frameworks are released by industry-leading bodies to guide cybersecurity practices in their respective fields. 

Dispel's technology helps companies uphold many of the cybersecurity requirements and recommendations that these organizations release.

The regulatory frameworks discussed in this guide include: 

* [**AWWA Security Guidance**](/regulatory-framework-mappings/awwa-security-guidance/process-control-system-security-guidance-for-the-water-sector-witaf-503.md)
* [**DHS Trusted Internet Connections**](/regulatory-framework-mappings/dhs-tic/overview.md)
* [**IEC 62443**](/regulatory-framework-mappings/iec-62443/iec-62443.md)
* [**NERC CIP**](/regulatory-framework-mappings/nerc-cip/overview.md)
* [**NIST CSF 1.1**](/regulatory-framework-mappings/nist-csf-1.1/nist-cybersecurity-framework-1.1.md)
* [**NIST-800-82**](/regulatory-framework-mappings/section-5-ics-security-architecture.md)

If you don't see your framework listed, please contact Dispel at <hello@dispel.io>.


---

# 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/regulatory-framework-mappings/master.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.