> 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/nerc-cip/overview.md).

# NERC-CIP Overview

A NERC-CIP walkthrough and Dispel mapping of product offerings.

## What is NERC-CIP?

![](https://2668873066-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LqlTpechIfonX0FqSV8%2F-MXhObw-LakrfTjh3BlG%2F-MXhQOP6UmD1jEp5D9F2%2FNERCCIP.jpg?alt=media\&token=297387fe-70c3-4771-b56d-65697f8516f7)

The North American Electric Reliability Corporation (NERC) administers a Critical Infrastructure Protection program (CIP), which details the security requirements for any cyber assets considered "critical" to the North American electricity grid.&#x20;

CIP compliance is mandatory, and enforcement is achieved through self-reporting, audits, and investigations by NERC.

## What do all these sections mean?

Within CIP, each section focuses on a different area, and each section is currently on a different version. The naming convention is CIP-\[section]-\[version].

| Dispel Highlight | Section | Categorization | Currently Enforceable Standards                                         | Future Enforcement                               |
| ---------------- | ------- | -------------- | ----------------------------------------------------------------------- | ------------------------------------------------ |
|                  | CIP-002 | Management     | CIP-002-5.1a BES Cyber System Categorization                            |                                                  |
|                  | CIP-003 | Management     | CIP-003-7 Security Management Controls                                  | CIP-003-8                                        |
|                  | CIP-004 | Management     | CIP-004-6 Personnel & Training                                          |                                                  |
| ✔                | CIP-005 | Cyber          | CIP-005-5 Electronic Security Perimeters                                | CIP-005-6                                        |
|                  | CIP-006 | Physical       | CIP-006-6 Physical Security of BES Cyber Systems                        |                                                  |
| ✔                | CIP-007 | Cyber          | CIP-007-6 System Security Management                                    |                                                  |
|                  | CIP-008 | Management     | CIP-008-5 Incident Reporting and Response Planning                      | CIP-008-6                                        |
|                  | CIP-009 | Management     | CIP-009-6 Recovery Plans for BES Cyber Systems                          |                                                  |
|                  | CIP-010 | Management     | CIP-010-2 Configuration Change Management and Vulnerability Assessments | CIP-010-3                                        |
| ✔                | CIP-011 | Cyber          | CIP-011-2 Information Protection                                        |                                                  |
| ✔                | CIP-012 | Cyber          | N/A                                                                     | CIP-012-1 Communications between Control Centers |
| ✔                | CIP-013 | Cyber          | N/A                                                                     | CIP-013-1 Supply Chain Risk Management           |
|                  | CIP-014 | Physical       | CIP-014-2 Physical Security                                             |                                                  |

## How does Dispel help my organization align to NERC-CIP standards?

Dispel helps organizations in all Cyber-related sections. Dispel fulfills functionality relating to network and user security. For all sections, Dispel provides reports, inventories, and change logs supporting the monitoring requirements wherever relevant.

The following pages detail each requirement and corresponding Dispel feature where applicable in the Cyber sections. An Additional Sections page can be found containing summaries of the Physical and Management sections.

**CIP-005-5 Electronic Security Perimeters**

{% content-ref url="/pages/-Lu9EBiCmlkxyf0Oa2oi" %}
[CIP-005-5](/regulatory-framework-mappings/nerc-cip/cip-005-05.md)
{% endcontent-ref %}

**CIP-007-6 System Security Management**

{% content-ref url="/pages/-Lu9GyqkQ5LXcOq8xLq8" %}
[CIP-007-6](/regulatory-framework-mappings/nerc-cip/cip-007-6.md)
{% endcontent-ref %}

**CIP-011-2 Information Protection**

{% content-ref url="/pages/-Lu9Ii6zYs2ymg2BTaq5" %}
[CIP-011-2](/regulatory-framework-mappings/nerc-cip/cip-011-2.md)
{% endcontent-ref %}

**CIP-002-5.1, CIP-003-7, CIP-004-6, CIP-008-6, CIP-009-6, CIP-010-2**

{% content-ref url="/pages/-M0-aQINNyWOSPfRL6xy" %}
[Additional Sections](/regulatory-framework-mappings/nerc-cip/additional-sections.md)
{% endcontent-ref %}


---

# 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/nerc-cip/overview.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.
