TroutTrout

NERC CIP compliance checklist for electric utilities.

CIP-003-9 has applied since April 1, 2026. If vendors reach your substations or SCADA remotely, it applies to you. Here is what each standard asks for, and the evidence to show.

Last updated:

NERC CIP compliance in short

NERC CIP compliance means meeting standards CIP-002 to CIP-015 and proving it with evidence. Since April 1, 2026, CIP-003-9 also requires low-impact sites to control vendor remote access. Start with an asset inventory (CIP-002). Then route every vendor and remote session through one Intermediate System with MFA (CIP-003, CIP-005). Then plan internal network monitoring (CIP-015).

Trout Access Gate is that Intermediate System, built for OT. It brokers every remote session in front of the machine, enforces MFA even on PLCs and RTUs that cannot run it, records the session, and ends a vendor's access on demand. It runs on premise with no cloud dependency, so no BES traffic and no audit data leave your environment. It connects to your existing network and is installed in a day.

What changed in 2026

What changed for NERC CIP in 2026?

CIP-003-9 brought low-impact sites into vendor access control. FERC approved it in March 2023, and the NERC implementation plan set it to apply 36 months later, on April 1, 2026. CIP-015-1 adds monitoring inside the perimeter. FERC approved it in Order No. 907 on June 26, 2025, and directed NERC to extend it to access control and monitoring systems outside the ESP.

Apr 2026

CIP-003-9 applies

Low-impact vendor remote access controls apply now. Audits check for them.

Oct 2028

CIP-015 at control centers

Other medium impact systems follow 24 months later, per the CIP-015 implementation plan.

$1M

Per violation, per day

The statutory cap in Federal Power Act section 316A, adjusted each year for inflation.

CIP-003-9, low impact

What are the NERC CIP low impact requirements under CIP-003-9?

CIP-003-9 Attachment 1, Section 6 applies to every low-impact asset that allows vendor electronic remote access. You need a method to determine that access, a method to disable it, and a method to detect known or suspected malicious communications on it.

If a vendor still uses a VPN or a modem straight to a substation device, that is the finding. The fix is to route every vendor session through one broker that checks the person, records the session and lets you end it. Auditors ask for vendor session records tied to named users, and a written procedure to disable access. See secure OT remote access for the access patterns in detail, and Access Gate secure remote access for how the broker works.

CIP-005, remote access

What is a CIP-005 Intermediate System?

An Intermediate System is the jump point every Interactive Remote Access session must pass through. CIP-005-7 R2.1 requires it so the remote computer never reaches a high or medium impact asset directly. R2.2 requires encryption that ends at the Intermediate System. R2.3 requires multi-factor authentication. R2.4 and R2.5 require methods to determine and disable active vendor remote access.

Classic designs put firewalls and jump hosts at every VLAN boundary, which is slow to change on a live grid. Access Gate is the Intermediate System, placed beside the network. It brokers and records each session in front of the machine, enforces MFA, and ends a vendor session on demand. No VLAN rework and no maintenance window.

CIP-015, internal monitoring

What does CIP-015 internal network security monitoring require?

CIP-015-1 R1 requires network data feeds inside the Electronic Security Perimeter of high impact systems and medium impact systems with External Routable Connectivity. You must monitor connections, devices and communications, then detect and evaluate anomalous activity. R2 and R3 require you to retain the data and protect it.

Perimeter controls say nothing about traffic between two machines that both sit inside the ESP. That is the path attackers use once they are in. CISA reported that Volt Typhoon kept access in some US critical infrastructure networks for at least five years.

Access Gate covers the traffic that crosses it. It logs those flows, keeps them on premise, and raises alerts on new assets, new services and zone crossings. That is part of a CIP-015 data feed, not all of it: traffic between two machines that never reaches the gate needs its own sensor. Plan the CIP-015 feed as a separate deployment from the CIP-005 Intermediate System, which by definition sits outside the ESP.

NERC CIP monitoring obligations by standard
StandardMonitoring obligationApplies to
CIP-003-9 Section 6Determine, disable, and detect malicious communications on vendor electronic remote access.Low-impact BES Cyber Systems, since April 1, 2026.
CIP-005-7 R2Intermediate System, encryption and MFA for Interactive Remote Access. Determine and disable active vendor sessions.High impact, and medium impact with External Routable Connectivity.
CIP-007 R4Log security events, alert on them, retain logs, and review them on a schedule.High and medium impact BES Cyber Systems.
CIP-010 R2Monitor for changes to the baseline configuration.High impact BES Cyber Systems.
CIP-015-1 R1 to R3Data feeds inside the ESP, detect and evaluate anomalous activity, retain and protect the data.High impact, and medium impact with External Routable Connectivity. Phased from October 1, 2028.

Confirm versions and dates with your Regional Entity before an audit submission.

NERC CIP compliance checklist

The NERC CIP compliance checklist, standard by standard.

Most utilities that struggle in an audit are not missing a whole standard. They cannot produce evidence for a control they already run. Work through the list in order. Flag every item with no documentation, or no test in the last 12 months.

NERC CIP compliance checklist: what to do and the evidence to keep
StandardWhat to doEvidence auditors ask for
CIP-002Inventory every device on the network, including equipment too old to run an agent. Rate each against the impact criteria and keep the rationale.A dated asset list with impact ratings and how each device was found.
CIP-003-9Route all vendor access at low-impact sites through one broker. No direct VPN or dial-in to a device.Vendor session records tied to named users, and a written procedure to disable access.
CIP-004Tie every session to a named person with a role. Retire shared accounts.Access history and revocation logs.
CIP-005Define each ESP. Send every Interactive Remote Access session through an Intermediate System with MFA.ESP diagrams, remote access logs, and proof you can end a session.
CIP-007Disable unneeded ports and services, patch, and prevent malware. Enforce authentication on every system, including OT that cannot do it alone. Centralize security event logs.Port and patch records, authentication records, and a tamper-evident audit trail.
CIP-008 / CIP-009Keep incident response and recovery plans current, and test them.The plans, test records from the last cycle, and an event timeline you can produce.
CIP-011Identify where BES Cyber System Information lives, restrict who can read it, and document how media is disposed of.A BCSI inventory, access lists, and disposal records.
CIP-012Encrypt or otherwise protect real-time data sent between control centers.A plan naming the protected links and the method used.
CIP-010 / CIP-013Track baseline changes. Keep vendor sessions logged, time-limited and revocable.Baseline deltas with timestamps, and vendor session records.
CIP-015Monitor traffic between machines inside the ESP. Detect and evaluate anomalies. Retain the data.Data feed placement, anomaly records, and a retention policy.
CIP-006Control and log physical access to BES Cyber Systems.Physical access logs aligned to the systems they protect.
CIP-014If you own critical transmission stations, assess them, have the assessment verified, and keep a physical security plan.The risk assessment, the third-party verification, and the plan.

Fix the gaps in dependency order.

Start with CIP-002, because every other control depends on knowing what you protect. The asset inventory gives you that list of machines, with its history. The impact rating stays your call. Then CIP-003 and CIP-005 vendor access, now required at low-impact sites. Then CIP-007 authentication and CIP-015 monitoring. If you also run NIST SP 800-171 or CMMC, access control, logging and incident response overlap. Build the evidence once and map it across.

Access Gate against NERC CIP

Which evidence does Access Gate produce for each standard?

CIP-002BES Cyber System categorization
PARTIAL

Identify BES Cyber Systems and rate each one high, medium or low impact.

A list of the machines seen on the network, with nothing to install on them. The impact rating stays your call.

CIP-003-9Security management controls
YES

Low-impact sites: determine and disable vendor electronic remote access, and detect malicious communications (Section 6).

Every vendor session goes through the gate, tied to a named user, logged, recorded, and ended on demand. Detection rules and alerts run on the brokered traffic.

CIP-004Personnel and training
PARTIAL

Personnel risk assessment, training, and access management.

Per-user, per-machine access rules, with access history and revocation in the logs.

CIP-005-7Electronic security perimeter
YES

Route all Interactive Remote Access through an Intermediate System, with encryption and MFA (R2.1 to R2.3). Determine and disable active vendor sessions (R2.4, R2.5).

Access Gate is the Intermediate System. MFA on every session, session recordings, and a list of active vendor sessions you can end.

CIP-006Physical security
OUT OF SCOPE

Physical access controls for BES Cyber Systems.

Outside software scope. Logical access logs sit next to your physical access records.

CIP-007Systems security management
PARTIAL

Ports and services (R1), patching (R2), malware prevention (R3), security event logging (R4), and authentication enforcement (R5).

Authentication enforced in front of legacy PLCs, HMIs and RTUs that cannot do it alone, and a central log of every connection. Patching and malware prevention stay yours.

CIP-008 / CIP-009Incident response and recovery
PARTIAL

Documented, tested incident response and recovery plans.

Session logs and recordings to rebuild a timeline. The plans and their tests stay yours.

CIP-011Information protection
PARTIAL

Identify BES Cyber System Information and protect it in storage, transit and use, then at disposal.

Session recordings and logs stay on premise, readable only by the roles you grant. Your BCSI program and disposal records stay yours.

CIP-012Communications between control centers
OUT OF SCOPE

Protect the confidentiality and integrity of real-time assessment and monitoring data sent between control centers.

Outside Access Gate's scope. The encrypted control-center link is your WAN or VPN.

CIP-010Configuration change management
PARTIAL

Baseline configurations, change monitoring, and vulnerability assessments.

A record of who connected to which machine, and when, during each change.

CIP-013Supply chain risk management
YES

Vendor risk management plans, including vendor remote access.

Vendor sessions brokered, recorded, time-limited and revocable, the same controls as CIP-005 R2.4 and R2.5.

CIP-014Physical security of transmission
OUT OF SCOPE

Risk assessment, third-party verification and a physical security plan for critical transmission stations and substations.

Outside software scope.

CIP-015-1Internal network security monitoring
PARTIAL

Network data feeds inside the ESP, and methods to detect and evaluate anomalous activity (R1.1 to R1.3).

Traffic that crosses the gate is logged, kept on premise, and alerts fire on new assets, new services and zone crossings. Traffic that never reaches the gate needs another sensor.

Key
YESDirectly addressed. Audit-ready evidence generated.
PARTIALAccess Gate provides the data. You complete the process.
MANUALPhysical security and control-center links. Outside Access Gate's scope.
Coverage at a glance
3

Fully covered

7

Partially covered

3

Out of scope

CIP-007 asks for authentication and event logging on every system. Legacy OT cannot do either alone. Access Gate adds both in front of the devices. Patching and malware prevention stay yours.

What to do next

What should each type of utility do next?

Your next move depends on what kind of utility you are.

Municipal utilities

City-owned electric departments with substations and SCADA. Low-impact sites are now covered by CIP-003-9. Often no dedicated OT security staff.

Highest urgency

Suggested next step

Start with a focused CIP pilot. Get audit-ready evidence for CIP-002 and CIP-003, now that low-impact vendor remote access controls apply.

Rural electric cooperatives

Member-owned co-ops on aging distribution infrastructure. CIP-003-9 vendor access controls are new territory. Tight budgets.

High urgency

Suggested next step

Request a pilot scoped to CIP-003 vendor access controls.

Independent power producers

Generation operators already in CIP scope. CIP-005 vendor session controls and the coming CIP-015 monitoring deadlines open new gaps.

High urgency

Suggested next step

Map your existing controls against CIP-005 R2 and CIP-015 R1. Access Gate fills the vendor session and internal monitoring gaps.

Transmission owners and operators

High and medium impact systems across many substations. CIP-015 applies to control centers from October 1, 2028.

Strategic

Suggested next step

Evaluate one gate per site for multi-site ESPs, with no change to the existing network.

The CIP compliance pilot

Get audit-ready evidence in three phases.

First, full asset inventory (CIP-002). Then ESP and vendor access controls (CIP-003, CIP-005). Finally, authentication and internal monitoring (CIP-007, CIP-015). Evidence packages delivered.

Done

Reach audit-ready without touching devices.

Nothing to install on machines. No firmware changes and no downtime. It suits CIP environments where change approvals take months.

Self-reporting lowers penalties.

Self-reported violations with a corrective action plan are treated more favorably. Violations found in an audit weigh against you.

Related regulations

Operating water or wastewater systems too?

Many electric utility operators also run water and wastewater infrastructure. New York imposes a parallel set of OT cybersecurity regulations under DOH and DEC. Drinking water (DOH): January 1, 2027. Wastewater (DEC): March 11, 2027. See our NY State EFC SECURE & DEC/DOH compliance guide for the parallel water-sector requirements, the 12-step EFC checklist, and NIST CSF 2.0 mapping.

For the full reference architecture behind CIP-005 remote access, CIP-007 system security, and CIP-010 change management, see the Zero Trust for Utility OT whitepaper. It covers commissioning and brownfield deployment, the four-pillar coverage map, and the NERC CIP matrix by control family.

CIP-002 starts with identifying and categorizing your BES Cyber Systems, which is a risk assessment before it is a compliance exercise. Our walkthrough on how to perform a risk assessment on your OT environment covers asset discovery, consequence rating, and scoping without active scans that a relay or an RTU will not survive.

Questions

Common questions about NERC CIP compliance.

Apr 2026

CIP-003-9 has applied since April 1, 2026

NERC CIP is the set of Critical Infrastructure Protection standards, CIP-002 to CIP-015, that every registered owner and operator of the North American bulk electric system must meet. Compliance means running the required controls and keeping the evidence an auditor asks for. FERC approves the standards and can enforce them with penalties of up to $1 million per violation per day.

The NERC CIP standards in force run from CIP-002 to CIP-015: CIP-002 BES Cyber System categorization, CIP-003 security management controls, CIP-004 personnel and training, CIP-005 electronic security perimeters, CIP-006 physical security, CIP-007 systems security management, CIP-008 incident reporting and response, CIP-009 recovery plans, CIP-010 configuration change management, CIP-011 information protection, CIP-012 communications between control centers, CIP-013 supply chain risk management, CIP-014 physical security of transmission, and CIP-015 internal network security monitoring.

CIP-003-9 has applied since April 1, 2026. Section 6 requires every entity with low-impact BES Cyber Systems that allows vendor electronic remote access to have methods to determine that access, disable it, and detect known or suspected malicious communications on it.

CIP-005-7 R2.1 requires all Interactive Remote Access to high and medium impact BES Cyber Systems to go through an Intermediate System, so the remote computer never reaches the asset directly. R2.2 and R2.3 add encryption and multi-factor authentication. R2.4 and R2.5 require methods to determine and disable active vendor sessions. Access Gate is an Intermediate System built for OT: it brokers and records every session, enforces MFA even on legacy PLCs and RTUs, and ends a vendor session on demand, on premise with no cloud dependency.

CIP-015-1 requires network data feeds inside the Electronic Security Perimeter of high impact and medium impact (with External Routable Connectivity) BES Cyber Systems, and methods to detect and evaluate anomalous activity. FERC approved it in Order No. 907 on June 26, 2025. Under NERC's implementation plan, systems at control centers must comply from October 1, 2028 and the other medium impact systems 24 months later.

CIP-002, asset identification and categorization. Every other control depends on a complete inventory of BES Cyber Systems and their impact ratings. You cannot scope or evidence CIP-005, CIP-007 or CIP-015 until you know what you are protecting.

CIP-005-7 R2.3 requires MFA for Interactive Remote Access, and CIP-007 R5 requires authentication enforcement on the systems themselves. Legacy PLCs and HMIs cannot do either alone. Access Gate enforces multi-factor authentication at the network layer, in front of the device, without changing firmware, so the control applies without touching the OT equipment.

No single product delivers compliance. A platform supports specific controls and produces evidence: asset lists, vendor access records, MFA enforcement and internal monitoring. Physical security, policies and tested response plans remain the utility's own work. The coverage table on this page shows what is covered, partial and manual.

Access Gate connects to your existing network and is installed in a day. The CIP pilot then produces audit-ready evidence in three phases: asset inventory (CIP-002), vendor remote access controls (CIP-003, CIP-005), then authentication and internal monitoring (CIP-007, CIP-015).

Section 316A of the Federal Power Act allows civil penalties of up to $1 million per violation per day, a cap FERC adjusts each year for inflation. Self-reported violations with a corrective action plan are treated more favorably than violations found in an audit.