Compliance program

NERC CIP COMPLIANCE STAY ON THE GRID, STAY SAFE

NERC CIP (the North American Electric Reliability Corporation's Critical Infrastructure Protection standards) mandates security controls for the grid's cyber systems. Federal regulators warn that adversaries have inserted malicious software through the supply chain. We map your IT controls to NERC CIP for firms connected to utilities and keep evidence ready.

Who it is for
Critical infrastructure organizations connected to electric utilities
How it runs
An initial project, then quarterly or yearly maintenance
What you get
A NERC CIP policy set, a control mapping and an evidence index

Who NERC CIP applies to and how it reaches vendors

NERC CIP applies to registered entities: balancing authorities, certain distribution providers, generator owners and operators, reliability coordinators, and transmission owners and operators. Contractors and equipment vendors are not on that list. If you are one, the standards bind your utility customer, not you, and they reach you through its reviews, access rules and contracts.

Our NERC CIP consulting is IT-scoped: the program covers your IT systems and how they're governed. It doesn't take over a utility's own NERC CIP compliance for its grid systems.

NERC CIP requirements for contractors and vendors

Grid systems are rated low, medium or high impact, and what applies to you depends on the rating.

  • CIP-003-9, laptops and USB drivesLow impact sites. Before a contractor's laptop connects, the utility reviews it, for example its antivirus update level, application allowlisting or hardening, and adds protection first if needed. USB drives are scanned on a separate device before use (Attachment 1, Sections 5.2 and 5.3).
  • CIP-003-9, vendor remote accessLow impact sites that allow it. The utility needs ways to see vendor remote access, shut it off and detect malicious traffic in and out (Attachment 1, Section 6). Attachment 2 lists evidence such as pre-approval, log-on alerts and session recording.
  • CIP-010-4, patches and USB drivesMedium and high impact sites. The same malicious code checks apply, plus a review of your installed security patches, your patching process or other vulnerability mitigation. USB drives are authorized by user and location (Requirement R4, Attachment 1, Sections 2 and 3).
  • CIP-005-7, remote sessionsHigh impact sites, and medium impact sites that can be reached remotely. Every interactive remote session needs multi-factor authentication (Part 2.3), and the utility must be able to see and end active vendor sessions (Parts 2.4 and 2.5).
  • CIP-004-7, people with accessHigh impact sites, and medium impact sites that can be reached remotely. There, your people need training before access and at least every 15 calendar months, and the utility must be able to verify contractors' personnel risk assessments. After a termination action, their unescorted physical access and interactive remote access must be removed within 24 hours (Parts 2.2, 2.3, 3.4 and 5.1).
  • CIP-013-2, supply chain plansMedium and high impact only. The utility's plan must cover six vendor items: incident notice, coordinated response, notice when a vendor's access should end, disclosure of known vulnerabilities, software integrity checks and coordinated controls for vendor remote access (Parts 1.2.1 to 1.2.6).

NERC CIP vendor questionnaires and contract terms

CIP-013-2 gives vendors no duties of their own. The utility can pass its plan's vendor items to you through contract terms and security questionnaires.

The North American Transmission Forum's CIP-013 guidance, posted by NERC, builds on the Energy Sector Supply Chain Risk Questionnaire, which utilities, vendors and assessors developed to agree on what information is needed. The guidance says using it does not add to what the standard requires.

For contracts, the Edison Electric Institute publishes model procurement contract language, written by a committee from its member companies. Your own contract may differ from it. Version 4.0, from June 2026, has the contractor:

  • Document its patch and vulnerability management programs before delivering products or connecting devices
  • Provide a hash for its software and patches that meets a Federal Information Processing Standard, so files can be checked for tampering
  • Ship physical deliveries through trusted channels in tamper-evident packaging
  • Coordinate all remote access with the utility, from a computer not connected to the internet or other third-party networks at the same time
  • Get the utility's written approval before its people have access, with that access revoked right away when needed
  • Tell the utility within 24 hours after filing a security incident report with a state or federal agency

Where NERC CIP stands in 2026

Dates checked in 2026 against NERC bulletins and Federal Energy Regulatory Commission (FERC) orders.

CIP-003-9 has been in effect since April 1, 2026. The supply chain rewrite was still a draft at NERC's July 2026 ballot, and the next scheduled changes take effect in 2028 and 2029.

  • November 24, 2025: FERC Order No. 912 took effect. It directs NERC to address whether supply chain plans are sufficient to identify and respond to supply chain risks. NERC has 18 months to file.
  • In that order, FERC declined to require validating vendor data or renegotiating contracts. It also wrote that current supply chain standards do not require reassessing equipment before installation, which leaves a gap between the loading dock and go-live.
  • July 17, 2026: NERC's initial ballot closed on drafts CIP-013-4, at 30.64% approval, and CIP-010-6, at 64.55%. Both were still drafts in NERC's July 27, 2026 bulletin.
  • July 1, 2028: revised CIP standards that address virtualization take effect, including CIP-005-8, CIP-010-5 and CIP-013-3.
  • July 1, 2029: CIP-003-11 takes effect, approved by FERC Order No. 918. It merges the low impact electronic access and vendor remote access sections and widens malicious traffic detection to all inbound and outbound electronic access.
  • Also open: a NERC project on risk management for third-party cloud services (Project 2023-09).

How our NERC CIP governance program runs

  1. 01 AssessYou define the systems in scope. We review their IT controls against the NERC CIP requirements that apply and list the gaps.
  2. 02 BuildWe write the policy set, map each control to its requirement and build the evidence index.
  3. 03 MaintainEvery quarter or every year, we review the program and bring the policies and evidence up to date.
  4. 04 ReportYou see progress and what to fix next, with the records organized for review.

NERC CIP documentation the program produces

  • 01Policy setWritten NERC CIP policies for your IT systems, approved by you and reviewed on schedule.
  • 02Control mappingEach requirement in scope matched to the IT control that answers it, with gaps marked.
  • 03Evidence indexThe proof behind each control, such as reports and screenshots, and where it is kept.
  • 04Governance recordsWho owns the program, what was approved and when it was last reviewed.
  • 05Audit packageThe evidence organized in one package for a utility review or an audit.

Services that pair with the NERC CIP program

Each is a separate service, and none replaces the utility's own review.

  • Security-First Endpoint ManagementAntivirus and patches kept current on every laptop, with protection and patch status reports.
  • Secure Configuration and Hardening ManagementLaptops and servers set to recognized secure settings, with a hardening checklist and exceptions on record.
  • Vulnerability ManagementRegular scans with fixes tracked until closed, to document the vulnerability program a contract may ask about.
  • Cyber Insurance and Security Questionnaire SupportHelp answering a utility's security questionnaire, with the evidence behind each answer.
  • Incident Response ReadinessA written response plan and incident contact sheet, for the incident notice and coordination a utility may ask of vendors.
  • Vendor Remote Access GovernanceFor outside vendors who reach your own IT systems: their own limited access with a second sign-in step, shut off and recorded when the work is done. Your access into a utility stays under its control.

What we handle for NERC CIP, What stays with you

CyberBlip

  • Map your IT controls to the NERC CIP requirements in scope
  • Write and update the NERC CIP policy set
  • Document how security is governed and who approved what
  • Collect, organize and maintain the evidence
  • Prepare the records for review

You

  • Define which systems are in scope
  • Approve the policies and governance decisions
  • Name a person inside to own the program
  • Make the business and risk decisions
  • Bring in your lawyer for questions about contract terms

NERC CIP compliance questions

Does the laptop review apply if our laptop never goes online?

Yes, being offline doesn't take a laptop out of scope. NERC's definition of a Transient Cyber Asset covers a device such as a laptop that can transfer executable code and connects directly to in-scope utility equipment for 30 consecutive calendar days or less, and internet access is not one of the tests. For laptops that stay offline for weeks, see our guide to patching field laptops.

Does NERC CIP require full-disk encryption on contractor laptops?

Not directly. Neither CIP-003-9 nor CIP-010-4 lists it among the reviews for laptops managed by another party, and CIP-010-4 names it only for laptops the utility manages itself (Attachment 1, Section 1). A utility can still require encryption in its own vendor terms.

If our evidence is in order, will the utility let our laptop connect?

That decision stays with the utility. After its review, it decides whether more protection is needed and must put it in place before your laptop connects (CIP-003-9, Attachment 1, Section 5.2.2; CIP-010-4, Attachment 1, Section 2.3). Current protection and clear records help the review, but they don't replace it.

Can you help us answer a utility's security questionnaire?

Yes, through our Cyber Insurance and Security Questionnaire Support service. We draft the technical answers, gather the evidence behind them and flag any claim the evidence doesn't support. You approve the final answers, and business or legal questions stay with you and your attorney.

Will you handle our NERC CIP audit?

Not as part of this program. Formal NERC CIP audit defense and registered entity compliance are outside it. The program keeps your IT controls mapped, your policies current and your evidence organized for review.

Sources

Show all 13 sourcesHide sources
  1. CIP-003-9, Cyber Security, Security Management Controls NERC, 2023-03-16
  2. CIP-004-7, Cyber Security, Personnel and Training NERC, 2021-12-07
  3. CIP-005-7, Cyber Security, Electronic Security Perimeter(s) NERC, 2021-03-18
  4. CIP-010-4, Cyber Security, Configuration Change Management and Vulnerability Assessments NERC, 2021-03-18
  5. CIP-013-2, Cyber Security, Supply Chain Risk Management NERC, 2021-03-18
  6. Glossary of Terms Used in NERC Reliability Standards (Transient Cyber Asset) NERC
  7. Project 2023-04, CIP-003-11 Implementation Plan NERC, 2024-11
  8. Standards, Compliance, and Enforcement Bulletin (Project 2025-06 initial ballot results) NERC, 2026-07-27
  9. Standards, Compliance, and Enforcement Bulletin (U.S. effective dates for Reliability Standards) NERC, 2026-08-31
  10. Order No. 912, Supply Chain Risk Management Reliability Standards Revisions FERC, in the Federal Register, 2025-09-23
  11. Order No. 918, CIP-003-11 (Docket RM25-8-000) FERC, in the Federal Register, 2026-03-24
  12. Model Procurement Contract Language Addressing Cybersecurity Supply Chain Risk, Version 4.0 Edison Electric Institute, 2026-06
  13. CIP-013 Implementation Guidance, Supply Chain Risk Management Plans, Version 1.1 North American Transmission Forum, posted by NERC, 2023-10-23

Next step

Find out where you stand

Tell us how we can best support you.

Icons: Tabler Icons, MIT License. License text: /licenses/tabler-icons.txt