NIS2
Identify your national implementation and prepare governance, security controls and incident reporting.
NERC Critical Infrastructure Protection Reliability Standards
Identify applicable bulk electric system cyber assets and build audit-ready controls.
Registered entities and qualifying bulk electric system assets under applicable NERC Reliability Standards and jurisdictional rules.
Evidence of applicable CIP controls, procedures, testing and reliability compliance.
Applicability depends on function and asset categorization. Use the approved implementation plans and confirm applicability with the relevant regional entity.
Monitor validation gaps, expired provider evidence and service changes that affect compliance.
Fill this in with your sponsor and send it to the people who own the work.
NERC CIP kickoff brief Business reason and required outcome [Contract, obligation or approval] Scope and exclusions [Entities, systems or activities, and reasons] Fixed deadlines and internal milestones [Date, source and owner] Executive sponsor and authorized signer [Names] Project lead and backup [Names] First workstream Determine registration and applicable assets · Reliability compliance + operations [Name and due date] People, effort and external costs [Estimate, owner and contingency] Evidence folder and reviewer access [Location, access owner and review date] Decisions and blockers [Item, options, owner and decision date] First week 1. Ask the first-step owner to bring the most recent system, activity or product inventory and the contract or rule driving the work. 2. Map one in-scope service or transaction, including providers and supporting systems. Check real evidence against the requirements and confirm whose responsibility each check is. 3. Record what the sponsor approved, open questions, work owners and the next date a decision is needed. Send the brief to everyone who needs to contribute evidence.
Checklist, instructions and 10 templates.
| Step | Owner | When to act | Estimated target | Deliverables | Status |
|---|---|---|---|---|---|
| Determine registration and applicable assets | Reliability compliance + operations | Before selecting requirements | Set a start date | Applicability matrix; BES cyber system inventory | Open |
| Translate requirements into control work | CIP lead + engineering | By applicable effective dates | Set a start date | Control owners; Procedures; Evidence plan | Open |
| Collect records and test readiness | Control owners + compliance team | On requirement-specific cycles | Set a start date | Evidence package; Exercise records; Findings tracker | Open |
| Support monitoring and manage remediation | Reliability compliance + management | On audit and ongoing | Set a start date | Monitoring package; Mitigation and reporting records | Open |
Targets use illustrative calendar-day estimates and assume the steps run in sequence. Check official dates and agree real durations with your team.
Identify registered functions and BES facilities. Categorize cyber systems and understand dependencies, impact criteria and jurisdictions.
Fictional details. Use the same fields with evidence from your work.
A reviewer can reach the same decision using the source and facts, or see exactly what remains unresolved.
Send confirmed obligations to the delivery team and record any unresolved decision with the appropriate authority or specialist.
Fictional details. Use the same fields with evidence from your work.
Each item has one accountable owner. The source and as-of date let a reviewer trace it back.
Share the reviewed inventory with the people building the control, privacy or testing scope.
Assign requirements for electronic and physical access, training, incident response, supply chain and configuration change according to asset scope.
Fictional details. Use the same fields with evidence from your work.
Every decision has one accountable person, a backup and a practical route to reach them.
Share the approved instructions with the people expected to follow them and test the handoffs at the next exercise.
Fictional details. Use the same fields with evidence from your work.
Every decision has one accountable person, a backup and a practical route to reach them.
Share the approved instructions with the people expected to follow them and test the handoffs at the next exercise.
Fictional details. Use the same fields with evidence from your work.
A reviewer can open the right file, reproduce the population filter and see who performed or approved the real task.
Send the index and access instructions to the assessor. Keep sensitive files in the approved evidence store.
Capture access, configuration, monitoring and recovery evidence. Exercise incident response and align reporting and testing with applicable versions.
Fictional details. Use the same fields with evidence from your work.
A reviewer can open the right file, reproduce the population filter and see who performed or approved the real task.
Send the index and access instructions to the assessor. Keep sensitive files in the approved evidence store.
Fictional details. Use the same fields with evidence from your work.
An absent participant can see what was tested, what happened and why an action was assigned.
Send approved findings to action owners and file the record for governance or assessment.
Fictional details. Use the same fields with evidence from your work.
The closure test addresses the original problem and has a dated result from an independent reviewer where required.
Send open items and decisions to governance, audit or the assessor on the applicable cadence.
Review regional monitoring requests, support evidence submission and track findings, self-reports and mitigation plans where applicable.
Fictional details. Use the same fields with evidence from your work.
The submitted package can be recreated from the index and the receipt is linked to the exact files.
Send the approved package through the official channel. Treat the download as an index, and use issuer forms where required.
Fictional details. Use the same fields with evidence from your work.
The closure test addresses the original problem and has a dated result from an independent reviewer where required.
Send open items and decisions to governance, audit or the assessor on the applicable cadence.