dataphleet Book a demo

CIP-003-9 Automated today

Security Management Controls

CIP-003-9 sets the management controls for cyber security. Cyber security policies must be reviewed and approved by the CIP Senior Manager at least every 15 calendar months (R1). Any entity with low impact BES Cyber Systems must implement a cyber security plan covering the Attachment 1 sections, which now include vendor electronic remote access controls (R2). The CIP Senior Manager must be identified by name, with changes documented within 30 days (R3). Delegations of authority must be documented (R4).

Key facts
StatusEffective April 1, 2026
U.S. effective dateApril 1, 2026
Policy review (R1)Every 15 calendar months, approved by the CIP Senior Manager
New in -9Attachment 1 Section 6: vendor electronic remote access security controls for low impact BES Cyber Systems
CIP Senior Manager (R3)Named; changes documented within 30 calendar days
Next versionsCIP-003-10 (July 1, 2028), CIP-003-11 (July 1, 2029)
RelatedCIP-002-5.1a, CIP-004-7

What CIP-003-9 requires

Our plain-language summary of each requirement. The standard's text governs.

R1

Policies

Review and obtain CIP Senior Manager approval at least every 15 calendar months for documented policies covering the required topics for high, medium and low impact systems.

R2

Low impact plan

Implement documented cyber security plans for low impact BES Cyber Systems that include the sections in Attachment 1: awareness, physical and electronic access controls, incident response, transient cyber assets and removable media, and vendor electronic remote access.

R3

Name the CIP Senior Manager

Identify the CIP Senior Manager by name and document any change within 30 calendar days.

R4

Delegations

Implement a documented process to delegate authority, recording the delegate's name or title, the actions delegated and the date.

Evidence an auditor will ask for

  • Policies with dated CIP Senior Manager approvals within 15 months
  • The low impact plan, section by section, with implementation evidence
  • CIP Senior Manager identification and change records
  • Delegation records

Where teams get caught

  • Section 6 vendor remote access controls not yet documented
  • A leadership change documented on day 45
  • Low impact plans that differ site to site with no single view

What data phleet does for CIP-003-9

  • Tracks R1 policies for required topics, review dates and approval within 15 months
  • Reviews the low impact plan section by section for required content, including Section 6 vendor remote access
  • Verifies the CIP Senior Manager record and the 30-day change rule, and records delegations
  • Flags every gap with its VSL, linked to the source evidence
data phleet CIP-003-9 governance screen
CIP-003-9 governance in a demo environment. The CIP Senior Manager and delegations tracked against R3 and R4; a change not documented within 30 days is flagged with its VSL.

CIP-003-9 questions

What's new in CIP-003-9?

Attachment 1 Section 6, which requires low impact entities to implement controls for vendor electronic remote access. CIP-003-9 became effective in the U.S. on April 1, 2026.

How often must CIP security policies be approved?

At least once every 15 calendar months, by the CIP Senior Manager.

See your CIP-003-9 evidence, organized.

Book 30 minutes. Bring one site's records and we'll surface the evidence live, show you the gaps and walk through the reports.

Book a demo