The CIP Senior Manager: what CIP-003 R3 and R4 ask, and how delegations work
Who the CIP Senior Manager is, what CIP-003-9 R1, R3 and R4 require, where delegation is allowed, and the checks to run after a reorganization.
Every NERC CIP program has one named person at the top of it: the CIP Senior Manager. That person approves the cyber security policies, and in a few places the standards allow them to hand specific approvals to a delegate. The requirements behind this are short, which is why they are easy to let slip.
The usual way they slip is a reorganization. A merger, an acquisition or a new reporting line moves the CIP Senior Manager out of the role, nobody updates the designation, and the next policy approval or delegated sign-off is made by someone who no longer holds the authority on paper. This post covers what CIP-003-9 R1, R3 and R4 say, who they apply to, and the checks to run when people change.
Who the CIP Senior Manager is
The NERC Glossary defines the CIP Senior Manager as "A single senior management official with overall authority and responsibility for leading and managing implementation of and continuing adherence to the requirements within the NERC CIP Standards, CIP-002 through CIP-011."
Two parts of that definition do most of the work. "Single" means one person, not a committee or a shared role. "Overall authority and responsibility" means someone senior enough to actually direct the program. NERC has also approved a revised definition that ends "within the NERC Critical Infrastructure Protection Cyber Security Standards" instead of naming CIP-002 through CIP-011; the Glossary lists it as subject to future enforcement from July 1, 2028.
Which parts apply to which sites
CIP-003-9 applies to Responsible Entities (Balancing Authorities, certain Distribution Providers, Generator Operators, Generator Owners, Reliability Coordinators, Transmission Operators and Transmission Owners). Its requirements split by impact level like this:
- R1 (policies) has two parts: Part 1.1 lists nine topics for high and medium impact BES Cyber Systems, and Part 1.2 lists seven topics for assets containing low impact BES Cyber Systems. You cover whichever applies to you.
- R2 (the cyber security plan in Attachment 1) applies only to entities with at least one asset containing low impact BES Cyber Systems.
- R3 (identify the CIP Senior Manager) and R4 (delegations) are not tied to an impact level. A Responsible Entity whose sites are all low impact still needs a named CIP Senior Manager.
- Category 2 inverter-based resources registered with NERC are not BES facilities and are not subject to CIP, so registration alone does not create a CIP Senior Manager obligation.
R1: the 15-month policy approval
R1 reads: "Each Responsible Entity shall review and obtain CIP Senior Manager approval at least once every 15 calendar months for one or more documented cyber security policies" covering the listed topics. For low impact, those topics are cyber security awareness, physical security controls, electronic access controls, Cyber Security Incident response, Transient Cyber Assets and Removable Media malicious code risk mitigation, vendor electronic remote access security controls, and declaring and responding to CIP Exceptional Circumstances.
Note the wording: R1 says "CIP Senior Manager approval", not "CIP Senior Manager or delegate". The policy approval is one the CIP Senior Manager signs personally. The measure (M1) points to review records, such as revision history or document management workflow, and "documented approval by the CIP Senior Manager for each cyber security policy."
R3: identify by name, and document changes within 30 calendar days
R3 is one sentence: "Each Responsible Entity shall identify a CIP Senior Manager by name and document any change within 30 calendar days of the change."
By name means a person, not a job title. The measure (M3) gives the kind of evidence expected: "a dated and approved document from a high level official designating the name of the individual identified as the CIP Senior Manager." The date matters. An auditor checking the audit period needs to see who held the role on each day of it, and a designation with no date cannot show that. The ReliabilityFirst article listed in the sources makes the same point.
R4: delegations, if you use them
R4 requires "a documented process to delegate authority, unless no delegations are used." Where a delegation exists, it "shall be documented, including the name or title of the delegate, the specific actions delegated, and the date of the delegation; approved by the CIP Senior Manager; and updated within 30 days of any change to the delegation." The requirement says 30 days; its Violation Severity Levels count calendar days, so plan on calendar days.
Two details are easy to miss:
- Delegation is only possible "Where allowed by the CIP Standards". In the standards in force, the phrase "CIP Senior Manager or delegate" appears in CIP-002-5.1a R2 Part 2.2 (approving the BES Cyber System identifications every 15 calendar months), CIP-007-6 Part 2.4 (approving a revision or extension to a patch mitigation plan) and CIP-013-2 R3 (approving the supply chain cyber security risk management plan every 15 calendar months). Of these, only CIP-002-5.1a R2 matters at a site that is entirely low impact.
- "Delegation changes do not need to be reinstated with a change to the delegator." When the CIP Senior Manager changes, existing delegations stay valid. You do not have to re-sign them, but you still have to document the new CIP Senior Manager under R3.
If you do not delegate, a short statement from the CIP Senior Manager saying so keeps the question from coming up at audit. Naming a delegate by title rather than by name survives staff turnover, but not a reorganization that renames or removes the title.
Where reorganizations break this
- The CIP Senior Manager leaves or changes role, and no new designation is dated and approved within 30 calendar days.
- The next R1 policy approval is signed by the old CIP Senior Manager after they left the role, or by someone acting in the role who was never designated.
- A delegation names a title that the new organization chart no longer has, so later delegated approvals trace to nobody.
- An acquired site arrives with its own CIP Senior Manager and policies, and for a while it is unclear which designation applies. If you hold more than one NERC registration, ReliabilityFirst notes you may name a different CIP Senior Manager for each, but each registration needs its own clear, dated record.
- The signature on a CIP-002 or CIP-013 approval does not match the name or title in the delegation document.
Practical checks after a merger, acquisition or role change
- Add the CIP Senior Manager designation and the delegation list to the HR change checklist for the people involved, so a departure or new title triggers a review the same week.
- Document a new designation when the change takes effect, not at the end of the 30 days; the window is for slow paperwork, not for a planned handover.
- Re-check every delegation made by title against the new organization chart, and update any that changed within 30 days.
- List each approval due in the next few months (R1 policies, CIP-002 R2 identifications, CIP-013 R3 plan) and confirm who is allowed to sign each one.
- After an acquisition, decide which designation, policies and delegations govern the acquired sites, and record the date that decision took effect.
- Keep the old documents. CIP-003-9 asks entities to retain evidence of each requirement for three calendar years, and the auditor will want the history, not just today's version.
What an auditor typically asks for
- The CIP Senior Manager designation for each period under audit: dated, naming the individual, approved by a high level official (M3).
- Each change of CIP Senior Manager, with the date of the change and the date it was documented, to check the 30 calendar days.
- The documented delegation process, or the statement that no delegations are used; each delegation with name or title, actions, date and the CIP Senior Manager's approval (M4).
- The R1 policies with their review history and the CIP Senior Manager's approval, at intervals of no more than 15 calendar months.
- For each delegated approval, a signature that matches a delegation in force on the date it was signed. One practical habit, suggested by ReliabilityFirst, is to attach a copy of the delegation to each document the delegate signs.
How GridSafe helps
These requirements are about documents and signatures, and no device log can prove who your CIP Senior Manager is. What helps is keeping the documents in one place with their dates, approvals and review clocks. CIPStart keeps the CIP-003-9 R1 policies with version history, role-gated approval and a 15-month review clock, and its DocPilot add-on can draft an R3 Senior Manager designation for a person to review and approve. GridShield lays CIP evidence out against the RSAW worksheets; for CIP-003, that evidence is the documents you upload.