DOE Electricity Cybersecurity RMP
DOE electricity cybersecurity risk management process
Use DOE’s electricity risk management process to connect operating risks at plants, substations and control centers to business decisions and executive funding.
- Issuing authority
- U.S. Department of Energy (DOE), with NIST and NERC
- Timing
- The guideline describes an ongoing process. Start before approving an operational technology change or renewing a decision about residual risk. As an internal planning example, allow one week to set scope, two weeks to assess the priority function and its dependencies, then review decisions and owners at the next executive risk meeting.
- Reviewed
- Inside this guide
- 4 steps · 4 templates
Who it applies to
Generation, transmission, distribution, electricity marketing and supporting vendors. DOE’s 2012 guidance applies its process at organization, mission or business process, and information system tiers. Check applicable reliability standards, utility orders and contract requirements separately.
What you’ll produce
A signed risk strategy, a scenario register linking system findings to business outcomes, approved treatment decisions and repeatable checks that prove those decisions work.
DOE structures the work around four activities: frame, assess, respond and monitor. Preserve the same assumptions when tracking a risk over time. GAO’s electric grid review recommended that DOE cover distribution networks in its strategic plan after finding that the plans it reviewed did not fully address distribution risks. Budget engineering time, replacement or support costs, outage windows, temporary safeguards and independent retesting.
Run the project
Go to the roadmapDecisions for leadership
- Which risks will we reduce and how will we measure it?
- Set a target for each priority service or outcome. Use a current baseline to decide the investment needed, what can be phased in, and who accepts remaining risk.
- Who will do the work and who can sign?
- Appoint a sponsor, a day-to-day lead and a named owner for every workstream. Set aside their time and decide who can approve the outcome, accept remaining risk or authorize a filing.
- Which deadlines can we promise?
- Separate fixed external dates from internal targets. Confirm dependencies such as a vendor, test lab or assessor, and approve a backup plan if their dates slip.
How to spend the first week
- Ask the first-step owner to bring the most recent system, activity or product inventory and the contract or rule driving the work.
- Select one service and test a high-impact control with its owner. Record what actually happened, what failed and the proposed target.
- 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.
What to review each week
Monitor progress against the target, failed control tests and gaps that leave a critical service exposed.
Kickoff brief to share with your team
Fill this in with your sponsor and send it to the people who own the work.
DOE Electricity Cybersecurity RMP 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 Frame the decision across all three tiers · Executive sponsor + enterprise risk + operations leadership [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. Select one service and test a high-impact control with its owner. Record what actually happened, what failed and the proposed target. 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.
How to hand off evidence
- Record the requirement or claim, the person responsible, the period and the result. Link to the original report, configuration, test or case record.
- Include the version, system or product, date, and how you gathered the record. When a report covers a group of items, retain its filters and reconcile the count to the source.
- Ask the reviewer to open the evidence and reproduce the key check. Record their decision and date. Keep missing items or failures visible with an owner, a due date and a retest when needed.
- Share through the agreed channel. Keep sensitive originals in a restricted location and link any redacted copies to the corresponding originals.
How this works in practice
Two questions to check scope
- What operational outcome could be lost, and for how long?
- Who can authorize a change or accept the remaining risk?
- What check shows the response works without disrupting operations?
Worked scenario
A utility groups several aging monitoring systems under one distribution function. Operations explains how long staff can maintain service without the monitoring feed. Engineering and security identify the shared dependencies, finance prices the options, and leadership approves the work and a review date for remaining risk.
What to read next
- DOE C2M2
Use C2M2 to assess whether risk management practices operate across the chosen function.
Official milestones
See the deadline calendar- May 2012
DOE publishes the electricity RMP guideline
The guideline adapts NIST’s organizational risk methodology to the electricity subsector.
Official reference (opens in a new tab)
- 01Frame the decision across all three tiers, Executive sponsor + enterprise risk + operations leadership, about 5 days
- 02Assess scenarios and document uncertainty, Operations engineer + cybersecurity risk assessor + safety lead, about 10 days
- 03Select and fund a response, Accountable risk owner + finance + procurement and operations, about 5 days
- 04Validate effectiveness and revisit the decision, Control owner + independent reviewer + risk committee, about 5 days
Step by step
Checklist, instructions and 4 templates.
View plan as a table
| Step | Owner | When to act | Estimated target | Deliverables | Status |
|---|---|---|---|---|---|
| Frame the decision across all three tiers | Executive sponsor + enterprise risk + operations leadership | Before gathering assessment evidence | Set a start date | Risk strategy and tier crosswalk | Open |
| Assess scenarios and document uncertainty | Operations engineer + cybersecurity risk assessor + safety lead | Before prioritizing treatments or authorizing changes | Set a start date | Scenario register and risk assessment | Open |
| Select and fund a response | Accountable risk owner + finance + procurement and operations | At the decision gate and before the next change window | Set a start date | Response decision and funded plan | Open |
| Validate effectiveness and revisit the decision | Control owner + independent reviewer + risk committee | After deployment, at agreed reviews and after material changes | Set a start date | Risk monitoring and retest plan | Open |
Targets use illustrative calendar-day estimates and assume the steps run in sequence. Check official dates and agree real durations with your team.
- 01
Frame the decision across all three tiers
Write the operating outcome, constraints, risk criteria and delegation limits. Name the business and system owners and document the site and vendor dependencies the assessment will consider.
What to produce
Risk strategy and tier crosswalkSigned policy memo and responsibility matrix
Gather first
- Business impact assessment
- Asset and dependency inventory
- Existing risk policy
- Applicable rules and contracts
How to prepare it
- Name the organization decision maker, the business process owner and the system owner for each area. Record which decisions go to each owner.
- Set criteria for evaluating safety, reliability, recovery time, financial effect and customer impact. Document which criteria require escalation and who can approve an exception.
- List assumptions and operating constraints such as outage windows and supplier support. Obtain sign-off and give the assessment team the approved version.
Worked example
Fictional details. Use the same fields with evidence from your work.
- Worked scope example
- Organization objective: maintain distribution reliability. Business process: fault response. System scope: dispatch communications and monitoring at two sites. Loss of both feeds requires immediate escalation.
Check before handing it over
Each assessed system has a named owner and a documented link to an electricity service outcome.
Share the accepted version and scoring criteria with the assessment team.
- 02
Assess scenarios and document uncertainty
Define a credible initiating event and operational consequence. Record exposure, control effectiveness, likelihood and impact with rationale. Trace system observations to business consequences and identify common dependencies.
What to produce
Scenario register and risk assessmentScenario spreadsheet and evidence index
Gather first
- Approved criteria
- System diagrams
- Incident and maintenance history
- Vendor contracts
- Operator interviews
How to prepare it
- Write a scenario as a cause, a failed safeguard and a business consequence. Note primary and shared dependencies.
- Record existing safeguards and evidence of how they operate. Rate likelihood and impact using the agreed criteria and identify material uncertainty.
- Review common causes before aggregating site ratings. Record cross-site exposure, reviewer, open evidence requests and reassessment date.
Worked example
Fictional details. Use the same fields with evidence from your work.
- Worked scenario
- A shared communications supplier outage prevents remote status confirmation at both sites. Operators use a documented fallback. Rate the effect using measured drill recovery time and assign an owner to confirm supplier restoration assumptions.
Check before handing it over
Each rating can be reconstructed from assumptions, operating evidence and an approved impact scale.
Send jointly reviewed scenarios to the risk owner and finance.
- 03
Select and fund a response
Compare mitigation, transfer, avoidance and acceptance. Estimate costs, dependencies and operational constraints. Record interim protections, owner, residual risk and formal approval.
What to produce
Response decision and funded planOptions analysis and approval record
Gather first
- Scenario register
- Risk tolerance
- Cost and staffing estimates
- Approved outage windows
- Supplier terms
How to prepare it
- Record two realistic response options where available, their estimated cost, expected risk reduction, dependencies and effect on operations.
- Name an owner, interim safeguard and measurable acceptance criterion. State the estimated remaining risk for each option.
- Obtain a funding or acceptance decision from the authorized owner. Record the date, review trigger and next milestone for reassessment.
Worked example
Fictional details. Use the same fields with evidence from your work.
- Worked decision
- Leadership funds a second communications path for the priority site. The owner agrees to test failover during an approved window and document restoration time against the business process recovery target.
Check before handing it over
The decision has funding or explicit acceptance, and the team knows how it will prove completion.
Send approved work to engineering and track it in the risk register.
- 04
Validate effectiveness and revisit the decision
Test each agreed outcome with a safe method approved by operations. Report results, exceptions and changes to the risk owner. Reassess when the assumptions, suppliers or operating environment change.
What to produce
Risk monitoring and retest planControl verification and decision calendar
Gather first
- Approved response
- Change approval
- Operator runbook
- Verification evidence
- Committee schedule
How to prepare it
- Record the planned check, frequency, operating conditions, evidence owner and escalation threshold.
- Use an approved method or exercise to check the response without introducing unacceptable operational risk. Save the result and reconcile exceptions.
- Update the risk score and decision log if effectiveness, dependencies or operating conditions change. Document the next review date and accountable owner.
Worked example
Fictional details. Use the same fields with evidence from your work.
- Worked retest
- During a scheduled exercise, the backup path starts but the recovery target is missed. Reopen the treatment item, document the recovery time and assign a second verified exercise after the fix.
Check before handing it over
The recorded result supports the risk decision and shows what the business still needs to resolve.
Send open exceptions and funding decisions to the next steering meeting.
Official sources
- DOE electricity risk management overview (opens in a new tab)
- DOE RMP guideline and tier worksheets (opens in a new tab)
- NIST SP 800-39 risk management (opens in a new tab)
- GAO electric grid cybersecurity risks (opens in a new tab)
- DOE threat profile development guidance (opens in a new tab)