← Resources
Guide

NERC CIP-005: electronic security perimeters and remote access, requirement by requirement

CIP-005-7 explained: the Electronic Security Perimeter (R1), remote access (R2), vendor access to EACMS and PACS (R3), who it applies to, and the evidence.

The short answer

CIP-005-7 is the NERC CIP standard for electronic security perimeters. It applies to high impact BES Cyber Systems and to medium impact BES Cyber Systems (many parts only where they have External Routable Connectivity). It has three requirements: R1, an Electronic Security Perimeter with every routable connection through an identified Electronic Access Point; R2, Interactive Remote Access through an Intermediate System with encryption and multi-factor authentication, plus ways to see and cut active vendor sessions; R3, the same see-and-cut control for vendor remote access to EACMS and PACS. Low impact sites are covered by CIP-003-9 instead.

Who CIP-005 applies to

CIP-005-7 applies to high impact BES Cyber Systems and medium impact BES Cyber Systems, and to their associated Protected Cyber Assets, EACMS and PACS as each requirement part states. Several parts apply at medium impact only where the system has External Routable Connectivity, or only at Control Centers. CIP-002 decides the impact rating, so start there.

Low impact sites, which is where most solar, wind and battery sites land, are not under CIP-005. Their equivalent controls are CIP-003-9 Attachment 1 Section 3 (electronic access) and Section 6 (vendor electronic remote access).

R1: the Electronic Security Perimeter

  • 1.1: all applicable Cyber Assets connected to a network via a routable protocol reside within a defined ESP.
  • 1.2: all External Routable Connectivity goes through an identified Electronic Access Point (EAP).
  • 1.3: inbound and outbound access permissions at each EAP, with the reason for granting access, and deny all other access by default.
  • 1.4: where technically feasible, authentication when establishing Dial-up Connectivity.
  • 1.5: methods for detecting known or suspected malicious communications, inbound and outbound (high impact, and medium impact at Control Centers).

R2: Remote Access Management

  • 2.1: Interactive Remote Access goes through an Intermediate System, so the remote computer never reaches the BES Cyber System directly.
  • 2.2: encryption that terminates at the Intermediate System.
  • 2.3: multi-factor authentication for every Interactive Remote Access session.
  • 2.4: one or more methods to determine active vendor remote access sessions, including Interactive Remote Access and system-to-system remote access.
  • 2.5: one or more methods to disable active vendor remote access, including both kinds.

R3: vendor remote access to EACMS and PACS

R3 was added in CIP-005-7. It applies to EACMS and PACS associated with high impact BES Cyber Systems, and with medium impact BES Cyber Systems that have External Routable Connectivity: the firewalls, jump hosts, authentication servers and badge systems around the protected systems.

  • 3.1: one or more methods to determine authenticated vendor-initiated remote connections.
  • 3.2: one or more methods to terminate authenticated vendor-initiated remote connections and control the ability to reconnect.

What an auditor asks to see

  • The ESP drawing and the list of EAPs, matching what is actually cabled.
  • Each EAP's rule set, with the documented reason for every permitted inbound and outbound rule, and proof of deny by default.
  • The Intermediate System design: where encryption terminates and how multi-factor authentication is enforced.
  • How active vendor sessions are seen and cut, with records from the audit period, for the BES Cyber Systems (R2) and for EACMS and PACS (R3).
  • Dated configuration copies over the audit period. The EAPs and Intermediate Systems are EACMS, so CIP-007 and CIP-010 apply to them as well.

Where CIP-005 programmes usually slip

  • A connection that never touches the EAP: an OEM cellular modem for warranty support, or a vendor VPN box added after commissioning, which breaks R1.2.
  • System-to-system vendor connections left out of the R2.4 and R2.5 process because nobody is logged in.
  • Vendor access to the jump host or badge system tracked less carefully than access to the protected systems, which is exactly what R3 covers.
  • Rules opened during commissioning with no reason recorded.

Coming version

CIP-005-8 takes effect on July 1, 2028 with the virtualization revisions. Until then, CIP-005-7 is the version audited.

Common questions

What is NERC CIP-005?

CIP-005 (Cyber Security - Electronic Security Perimeter(s)) is the NERC CIP standard that controls electronic access to high and medium impact BES Cyber Systems. The version audited today is CIP-005-7, with three requirements: R1 Electronic Security Perimeter, R2 Remote Access Management, and R3 Vendor Remote Access Management for EACMS and PACS.

Does CIP-005 apply to low impact sites?

No. CIP-005 applies to high and medium impact BES Cyber Systems. Low impact sites have no Electronic Security Perimeter; their electronic access controls are in CIP-003-9 Attachment 1 Section 3, and vendor remote access in Section 6.

What is the difference between CIP-005 R2 and R3?

R2 covers remote access to the BES Cyber Systems themselves and their Protected Cyber Assets: Intermediate System, encryption, multi-factor authentication, and methods to determine and disable active vendor remote access sessions. R3, added in CIP-005-7, applies the vendor part to the systems around them: methods to determine authenticated vendor-initiated remote connections to EACMS and PACS, and to terminate them and control the ability to reconnect.

When does CIP-005-8 take effect?

July 1, 2028, with the other NERC CIP virtualization revisions approved by FERC Order No. 919. Until then CIP-005-7 is the version audited.

What evidence does an auditor ask for under CIP-005?

The ESP drawing and the list of Electronic Access Points; each access point's rule set with the reason for every permitted rule and deny by default; the Intermediate System design, its encryption and MFA settings; and records showing how active vendor sessions are seen and cut, for BES Cyber Systems (R2) and for EACMS and PACS (R3).

General guidance, not legal or compliance advice. Your obligations depend on your registration and assets — confirm them with your compliance team and Regional Entity.

From the blog

More from Resources