NERC CIP-003-9, "Cyber Security — Security Management Controls," is the mandatory, FERC-approved Reliability Standard that requires utilities and grid operators to maintain documented cyber security governance for BES Cyber Systems — the standard that, per its Purpose clause, exists "to specify consistent and sustainable security management controls that establish responsibility and accountability to protect BES Cyber Systems against compromise that could lead to misoperation or instability in the Bulk Electric System (BES)." Unlike most other CIP standards, CIP-003 reaches beyond the high and medium impact systems governed by CIP-002 through CIP-011: its Requirement R2 and Attachment 1 impose a separate, lighter-weight set of controls directly on low impact BES Cyber Systems, which most other CIP standards do not individually address. CIP-003-9 was adopted by the NERC Board of Trustees on 16 November 2022 and approved by FERC on 16 March 2023 (Docket No. RD23-3-000); per NERC's implementation plan it became effective and enforceable on 1 April 2026, and remains the enforceable version today even though a successor, CIP-003-11, is already FERC-approved for a 2029 compliance date (see below).
Key takeaways
- Three versions are FERC-approved and apply in sequence.
- Cyber Security Awareness — reinforce cyber security practices at least once every 15 calendar months.
- CIP-003-11 was drafted under NERC's Project 2023-04 on top of CIP-003-10, the virtualization revision.
- The same facts feed CIP-013 procurement questions.
Who must comply?
CIP-003 applies to Balancing Authorities, Distribution Providers that own certain underfrequency/undervoltage load-shedding systems, Remedial Action Schemes, Protection Systems, or Cranking Path facilities subject to a NERC or Regional Reliability Standard, Generator Operators and Owners, Reliability Coordinators, and Transmission Operators and Owners — collectively "Responsible Entities." Exemptions include Cyber Assets at facilities regulated by the Canadian Nuclear Safety Commission, communication networks and links between discrete Electronic Security Perimeters, and systems regulated by the U.S. Nuclear Regulatory Commission under 10 C.F.R. § 73.54.
Which CIP-003 version applies, and when?
Three versions are FERC-approved and apply in sequence. NERC's standard pages give the dates: CIP-003-9 is "Mandatory Subject to Enforcement" from 1 April 2026 with an inactive date of 30 June 2028; CIP-003-10 is effective from 1 July 2028 to 30 June 2029; and CIP-003-11 is effective from 1 July 2029.
| Version | Key dates (NERC / FERC) | Applies | What changes |
|---|---|---|---|
| CIP-003-9 | Board 16 Nov 2022; FERC 16 Mar 2023 (RD23-3-000) | 1 Apr 2026 – 30 Jun 2028 | Adds Attachment 1 Section 6, vendor electronic remote access controls for low impact assets |
| CIP-003-10 | Board 9 May 2024; FERC Order No. 919, 19 Mar 2026 (RM24-8-000) | 1 Jul 2028 – 30 Jun 2029 | Virtualization wording: Shared Cyber Infrastructure (SCI), Cyber Systems, "per system capability"; time-sensitive exclusion now reads "Protection Systems" |
| CIP-003-11 | Board 10 Dec 2024; FERC Order No. 918, 19 Mar 2026 (RM25-8-000) | from 1 Jul 2029 | Rewrites Attachment 1 Section 3: detection on all access, user authentication, credential protection in transit; folds Section 6 into Section 3 |
Both orders took effect on 26 May 2026, so a low impact program moves through two transitions inside a year.
What does R1's 15-month policy review cover?
Requirement R1 requires each Responsible Entity to "review and obtain CIP Senior Manager approval at least once every 15 calendar months for one or more documented cyber security policies" that collectively address two distinct topic sets, scaled by impact rating:
| Part | Scope | Topics the policy must address |
|---|---|---|
| 1.1 | High and medium impact BES Cyber Systems, if any | Personnel and training (CIP-004); Electronic Security Perimeters including Interactive Remote Access (CIP-005); physical security (CIP-006); system security management (CIP-007); incident reporting and response planning (CIP-008); recovery plans (CIP-009); configuration change management and vulnerability assessments (CIP-010); information protection (CIP-011); and declaring/responding to CIP Exceptional Circumstances |
| 1.2 | Assets with low impact BES Cyber Systems, if any | Cyber security awareness; physical security controls; electronic access controls; Cyber Security Incident response; Transient Cyber Asset and Removable Media malicious code risk mitigation; vendor electronic remote access security controls; and declaring/responding to CIP Exceptional Circumstances |
Violation Risk Factor is Medium, and the standard's own measures note that evidence "may include, but are not limited to, policy documents; revision history, records of review, or workflow evidence from a document management system." In CIP-003-11, Part 1.2 drops to six topics, because vendor electronic access becomes part of electronic access controls.
What does Attachment 1 require for low impact BES Cyber Systems?
Requirement R2 requires every Responsible Entity with at least one low impact BES Cyber System to implement one or more documented cyber security plan(s) covering all six sections of Attachment 1 of CIP-003-9:
Cyber Security Awareness— reinforce cyber security practices at least once every 15 calendar months. Physical Security Controls— control physical access, based on need, to the asset (or the low impact systems' locations within it) and to the Cyber Asset(s) providing the Section 3.1 electronic access controls. Electronic Access Controls— Part 3.1 permits "only necessary inbound and outbound electronic access" for routable-protocol communications between a low impact BES Cyber System and a Cyber Asset outside the asset, except time-sensitive protection or control traffic between intelligent electronic devices (the standard's example is IEC TR 61850-90-5 R-GOOSE); Part 3.2 requires authenticating all Dial-up Connectivity, per Cyber Asset capability. CIP-003-9's Section 3 has no detection requirement; that is Section 6.3, vendor access only. Cyber Security Incident Response— response plan(s) covering identification, classification and response, notifying the Electricity Information Sharing and Analysis Center (E-ISAC) of Reportable incidents, roles, incident handling, testing "at least once every 36 calendar months," and updating the plan within 180 calendar days of a test or actual Reportable Cyber Security Incident. Transient Cyber Asset and Removable Media Malicious Code Risk Mitigation— differentiated controls depending on whether a Transient Cyber Asset is managed by the Responsible Entity (antivirus, application whitelisting, or another mitigation method) or by another party (review of the other party's anti-malware or hardening practices, plus any additional mitigation needed before connection); for Removable Media, detection of malicious code using a separate Cyber Asset and mitigation before connecting the media to a low impact BES Cyber System. Vendor Electronic Remote Access Security Controls— for assets allowing vendor electronic remote access established under Section 3.1, one or more methods each to determine vendor remote access (6.1), disable it (6.2), and detect "known or suspected inbound and outbound malicious communications for vendor electronic remote access" (6.3).
The standard explicitly relieves entities of an inventory burden: "An inventory, list, or discrete identification of low impact BES Cyber Systems or their BES Cyber Assets is not required. Lists of authorized users are not required." Attachment 2's evidence examples include alerts on vendor log-on (6.1), disabled accounts (6.2) and IDS/IPS or log reviews (6.3).
What do R3 and R4 require of the CIP Senior Manager?
Requirement R3 requires each Responsible Entity to "identify a CIP Senior Manager by name and document any change within 30 calendar days of the change." Requirement R4 requires a documented process to delegate authority — where the CIP Standards allow delegation, each delegation must record the delegate's name or title, the specific actions delegated, and the date, be approved by the CIP Senior Manager, and be updated within 30 days of any change; delegation changes "do not need to be reinstated with a change to the delegator." Per CIP-003-9's Compliance section, "each Responsible Entity shall retain evidence of each requirement in this standard for three calendar years".
What does CIP-003-11 change in Attachment 1?
CIP-003-11 was drafted under NERC's Project 2023-04 on top of CIP-003-10, the virtualization revision. FERC approved CIP-003-10 in Order No. 919 (91 FR 13957). FERC approved CIP-003-11 the same day in Order No. 918 (Docket No. RM25-8-000, 91 FR 13952, effective 26 May 2026). NERC submitted CIP-003-11 "to mitigate risks posed by a coordinated cyberattack on low-impact facilities, the aggregate impact of which could be much greater" than any single low impact compromise, by "adding controls to authenticate remote users, protecting authentication information in transit, and detecting malicious communications to or between assets containing low impact BES Cyber Systems with external routable connectivity."
The new Section 3.1 applies where access crosses the asset boundary on a routable protocol and is not time-sensitive Protection System traffic:
| CIP-003-11 Part | Requirement | Where it was in CIP-003-9 |
|---|---|---|
| 3.1.1 | Permit only necessary inbound and outbound electronic access | Section 3.1 |
| 3.1.2 | Detect known or suspected malicious communications for both inbound and outbound electronic access | Section 6.3, vendor access only |
| 3.1.3 | Authenticate each user before access to a network containing low impact BCS through which user-initiated access is permitted | New |
| 3.1.4 | Protect user authentication information in transit for that access | New |
| 3.1.5 | Methods for determining vendor electronic access, where permitted | Section 6.1 |
| 3.1.6 | Methods for disabling vendor electronic access, where permitted | Section 6.2 |
CIP-003-11's Attachment 2 names the kinds of evidence that fit: PKI, LDAP, RADIUS or multi-factor authentication for 3.1.3, and an encrypted protocol or service (HTTPS, SSH) or an IPsec or SSL VPN for 3.1.4.
Per NERC's implementation plan, the standard becomes effective "on the first day of the first calendar quarter that is thirty-six (36) months after the effective date of the applicable governmental authority's order" — 26 May 2026 plus 36 months gives 1 July 2029. The expanded Section 3.1.2 detection scope is due by "the later of: (1) April 1, 2029; or (2) the effective date of Reliability Standard CIP-003-11," so 1 July 2029 either way. The drafting team chose that timeline so that entities "will have at least three years from the effective date of Reliability Standard CIP-003-9 to implement the additional controls contemplated by CIP-003-11."
What will a utility ask a device or remote-access vendor for?
CIP-003 binds the utility, not the manufacturer, but most Attachment 1 controls depend on facts only the vendor can supply:
| Attachment 1 control | What the utility has to show | What the vendor can ship |
|---|---|---|
| 3.1 (3.1.1 in -11): necessary access only | A rationale for each permitted inbound and outbound flow | A port, protocol and direction list per firmware release; which services can be disabled |
| 3.2: Dial-up authentication | Authentication per capability | Modem options (dial-back, dial-out only) and how to set them |
| 6.1 / 6.2 (3.1.5 / 3.1.6 in -11): determine and disable vendor access | Methods to see and switch off vendor sessions | The remote-support architecture, session logs, and a local way to disable vendor access |
| 6.3 (3.1.2 in -11): detect malicious communications | IDS/IPS, anti-malware or log review | The expected traffic profile (peers, protocols, polling intervals) and a syslog or similar log export |
| 3.1.3 / 3.1.4 (new in -11) | User authentication and credentials protected in transit | Support for RADIUS or LDAP, SSH and TLS management, and a way to turn off Telnet and plain HTTP |
| 5.2: vendor-managed Transient Cyber Assets | Review of the vendor's anti-malware and hardening before connection | A written statement of the field laptop's antivirus update process, whitelisting and hardening |
| 4: incident response | E-ISAC notification of Reportable incidents | A PSIRT contact and an advisory channel (PSIRT setup guide) |
The same facts feed CIP-013 procurement questions. Component capabilities such as authentication and encrypted management map onto IEC 62443-4-2.
Worked example: how does a low impact substation plan cover a vendor's remote support?
Synthetic example. The utility, vendor, device and dates are invented for illustration.
"Ridgeway Electric" has a low impact substation with an RTU from "Kestrel Controls", whose engineers support it remotely. Ridgeway's plan:
Section 3.1 (today)The substation firewall permits DNP3 from the RTU to the control center and HTTPS from Ridgeway's jump host to the RTU's web interface. Everything else is denied, with a recorded reason per rule. Section 6.1Kestrel staff reach the RTU only through the jump host, and the jump host alerts on each vendor log-on. Section 6.2The Kestrel account is disabled by default and enabled per support ticket for the session window. Section 6.3An IDS sensor on the substation uplink inspects vendor sessions, and the security team reviews its alerts weekly. Section 5.2Before a Kestrel field engineer plugs a laptop into the RTU, Ridgeway checks Kestrel's written statement of antivirus update level and hardening, and records whether extra mitigation was needed. 2029 updateFor 1 July 2029, Ridgeway widens IDS coverage to all inbound and outbound access, including the DNP3 traffic (3.1.2), adds multi-factor authentication at the jump host (3.1.3), and asks Kestrel to confirm that Telnet can be disabled on the RTU firmware so that only HTTPS and SSH carry credentials (3.1.4).
What are the common pitfalls?
- Citing "Section 3.1.2" against CIP-003-9. That Part exists only in CIP-003-11; under CIP-003-9 the detection duty is Section 6.3 and covers vendor electronic remote access only.
- Planning a jump from CIP-003-9 to CIP-003-11. NERC lists CIP-003-10 as effective from 1 July 2028 to 30 June 2029, so the virtualization wording (SCI, "per system capability") applies for a year first.
- Reviewing a vendor laptop after it is connected. Section 5.2 requires the review, and any extra mitigation, before connection.
- Assuming encrypted management can be added later. A device with only Telnet or HTTP logins may need a firmware update or a VPN to meet 3.1.4.
What is a workable starting point?
Separate the R1 policy-review calendar from the R2 Attachment 1 workThe 15-month approval is a governance checkpoint; Attachment 1's six sections are the controls it describes, and each can fail on its own. Plan detection for all inbound and outbound traffic, not just vendor accessTooling scoped to vendor sessions for Section 6.3 will need a broader buildout for Section 3.1.2 by 1 July 2029. Name the CIP Senior ManagerR3 requires the individual "by name," with changes documented within 30 calendar days. Track CIP-003-10 and CIP-003-11 as two dated stepsCIP-003-10's virtualization wording applies from 1 July 2028; CIP-003-11 replaces it on 1 July 2029. Update the plan's terminology for SCI in 2028 and the Section 3 controls in 2029. Ask each device vendor for the table aboveat the next purchase or support renewal, and file the answers with the plan.
Internal network security monitoring inside high impact and medium impact (with External Routable Connectivity) perimeters is a separate standard, CIP-015; for the wider OT program context, see the NIST SP 800-82 guide.
SoftWSP's OT Snapshot builds an inventory of hosts, ports, services and protocols seen in captured traffic and flags SSH, Telnet, RDP and VNC sessions crossing the internal/external boundary, which helps check a Section 3.1 flow list; it is not an intrusion detection system. The device firmware security assessment extracts an SBOM from a firmware image as CycloneDX 1.6 JSON, matches its components against NVD, CISA KEV, FIRST EPSS and CISA CSAF ICS advisories, and produces an AI-drafted report with a citation for each finding, reviewed by an engineer. A vendor can open the resulting CycloneDX file in the SBOM viewer before sharing it with a utility.
This guide quotes NERC's published standards, standard pages and implementation plan, and FERC Order Nos. 918 and 919; it is not compliance or legal advice. CIP-003-9 is the enforceable version on 13 November 2026.
Put this guide to work
Frequently asked questions
What is NERC CIP-003-9, and who must comply?
CIP-003, "Cyber Security — Security Management Controls," is the mandatory, FERC-approved NERC Reliability Standard that requires utilities and grid operators to maintain documented cyber security policies and governance for BES Cyber Systems. Per its own Purpose clause, it exists "to specify consistent and sustainable security management controls that establish responsibility and accountability to protect BES Cyber Systems against compromise that could lead to misoperation or instability in the Bulk Electric System (BES)." The currently enforceable version, CIP-003-9, was adopted by the NERC Board of Trustees on 16 November 2022 and approved by FERC on 16 March 2023 (Docket No. RD23-3-000); per NERC's implementation plan it became effective and enforceable on 1 April 2026. It applies to Balancing Authorities, certain Distribution Providers, Generator Operators and Owners, Reliability Coordinators, and Transmission Operators and Owners — collectively "Responsible Entities" — covering both the high/medium impact BES Cyber Systems categorized under [CIP-002](/guides/nerc-cip-002-bes-cyber-system-categorization/) and, through a separate set of requirements, low impact BES Cyber Systems.
What does Requirement R1's cyber security policy review actually require?
R1 requires each Responsible Entity to "review and obtain CIP Senior Manager approval at least once every 15 calendar months for one or more documented cyber security policies" covering two distinct topic sets. For high and medium impact BES Cyber Systems (Part 1.1), the policies must collectively address nine topics mirroring the other CIP standards: personnel and training (CIP-004), electronic security perimeters including interactive remote access (CIP-005), physical security (CIP-006), system security management (CIP-007), incident reporting and response planning (CIP-008), recovery plans (CIP-009), configuration change management and vulnerability assessments (CIP-010), information protection (CIP-011), and declaring/responding to CIP Exceptional Circumstances. For assets with low impact BES Cyber Systems (Part 1.2), the policies must instead address seven topics: cyber security awareness, physical security controls, electronic access controls, Cyber Security Incident response, Transient Cyber Asset and Removable Media malicious code risk mitigation, vendor electronic remote access security controls, and declaring/responding to CIP Exceptional Circumstances.
What does Attachment 1 require for low impact BES Cyber Systems under Requirement R2?
R2 requires each Responsible Entity with low impact BES Cyber Systems to implement one or more documented cyber security plan(s) covering all six sections of Attachment 1: Section 1 (reinforce cyber security practices at least once every 15 calendar months); Section 2 (control physical access to the asset and to the electronic-access-control Cyber Assets, based on need); Section 3 (electronic access controls — Part 3.1 permits only necessary inbound and outbound electronic access using a routable protocol; Part 3.2 requires authenticating all Dial-up Connectivity); Section 4 (a Cyber Security Incident response plan covering identification/classification/response, E-ISAC notification of Reportable Cyber Security Incidents, roles and responsibilities, incident handling, testing at least once every 36 calendar months, and updates within 180 calendar days of a test or actual incident); Section 5 (malicious code risk mitigation for Transient Cyber Assets and Removable Media, differentiated by whether the asset is managed by the Responsible Entity or a third party); and Section 6 (vendor electronic remote access security controls — methods to determine, disable, and detect malicious communications in vendor remote access). The standard explicitly notes that "an inventory, list, or discrete identification of low impact BES Cyber Systems or their BES Cyber Assets is not required."
What do Requirements R3 and R4 require, and is CIP-003-9 already being replaced?
R3 requires each Responsible Entity to "identify a CIP Senior Manager by name and document any change within 30 calendar days of the change." R4 requires a documented delegation process: if the CIP Senior Manager delegates authority for specific actions, the delegation must be documented by name or title, the specific actions delegated, and the date, approved by the CIP Senior Manager, and updated within 30 days of any change. Evidence for all four requirements must be retained for three calendar years. A successor is already FERC-approved: on 19 March 2026 the Federal Energy Regulatory Commission issued Order No. 918 (Docket No. RM25-8-000, published in the Federal Register on 24 March 2026 at 91 FR 13952), approving Reliability Standard CIP-003-11, which adds controls to authenticate remote users, protect authentication information in transit, and detect malicious communications across all inbound/outbound electronic access to low impact BES Cyber Systems with external routable connectivity — expanding the vendor-only detection scope of CIP-003-9's Attachment 1 Section 6.3. Per NERC's implementation plan, CIP-003-11 becomes effective "the first day of the first calendar quarter that is thirty-six (36) months after" the FERC order's 26 May 2026 effective date — 1 July 2029 — at which point CIP-003-10, the virtualization revision that NERC lists as effective from 1 July 2028 in place of CIP-003-9, retires.
Sources
- NERC: CIP-003-9 — Cyber Security – Security Management Controls (currently effective standard, full text: Purpose, Applicability, Requirements R1-R4 with Attachments 1-2, Compliance, Version History)
- Federal Register: Order No. 918; Critical Infrastructure Protection Reliability Standard CIP-003-11 — Cyber Security — Security Management Controls, 91 FR 13952 (FERC, Docket No. RM25-8-000, issued 2026-03-19, published 2026-03-24, effective 2026-05-26) — approves CIP-003-11, which supersedes CIP-003-10
- NERC: Implementation Plan, Project 2023-04 Modifications to CIP-003, Reliability Standard CIP-003-11 (September 2024) — effective-date formula, CIP-003-9's 1 April 2026 effective date, and the retirement clause for CIP-003-10/CIP-003-9
- Federal Register: Order No. 919; Virtualization Reliability Standards, 91 FR 13957 (FERC, Docket No. RM24-8-000, issued 2026-03-19, published 2026-03-24, effective 2026-05-26) — approves CIP-003-10 among 11 virtualization-revision CIP standards
- NERC: CIP-003-11 — Cyber Security – Security Management Controls (Attachment 1 Section 3.1.1-3.1.6, R1 Part 1.2.1-1.2.6, Attachment 2 evidence examples)
- NERC: CIP-003-10 — Cyber Security – Security Management Controls (virtualization revision; SCI, per system capability)
- NERC standard page: CIP-003-9 (Mandatory Subject to Enforcement; effective 04/01/2026, inactive 06/30/2028)
- NERC standard page: CIP-003-10 (Subject to Future Enforcement; effective 07/01/2028, inactive 06/30/2029)
- NERC standard page: CIP-003-11 (Subject to Future Enforcement; Board 12/10/2024, FERC 03/19/2026, effective 07/01/2029)
About this guide
SoftWSP OT/ICS Desk
Covers the OT/ICS security cluster: 79 guides.

In this cluster
Questions about this page?
