Start hereConfirm adoption and scope the assets
~31 days leftOpen step
Guide library
Framework North America

DOE and NARUC DER Cybersecurity Baselines

Cybersecurity baselines for electric distribution and DER

Use the DOE and NARUC baselines to decide which distribution and distributed energy resource assets to secure first, who owns each control, and what evidence will show it works.

Issuing authority
U.S. Department of Energy and National Association of Regulatory Utility Commissioners
Timing
The national guidance describes a phased approach. Use the dates in the applicable order or agreement when the baselines have been adopted. For an internal pilot, reserve time to scope one service, agree the first implementation group, and plan production work around approved operating windows.
Reviewed
Inside this guide
4 steps · 4 templates

Who it applies to

Electric distribution utilities and connected distributed energy resource (DER) owners, operators and aggregators, plus utility commissions and other oversight bodies. The publications provide a baseline resource. Confirm any binding state order, tariff, contract, or other local adoption terms for your service territory.

What you’ll produce

A signed asset scope, a baseline crosswalk tied to responsible parties, an agreed implementation schedule and an evidence pack for operators and applicable oversight.

DOE and NARUC released the baseline recommendations in 2024 and interim scoping and prioritization guidance in 2025. The latter helps teams choose the most consequential assets and the first controls when work needs to be staged. Budget for asset discovery, vendor coordination, shared control changes, operational change windows and verification.

TEAM KICKOFF

Run the project

Go to the roadmap

Decisions 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

  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.

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 and NARUC DER Cybersecurity Baselines 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  Confirm adoption and scope the assets · Regulatory counsel + distribution operator + aggregator lead [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
  1. Record the requirement or claim, the person responsible, the period and the result. Link to the original report, configuration, test or case record.
  2. 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.
  3. 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.
  4. Share through the agreed channel. Keep sensitive originals in a restricted location and link any redacted copies to the corresponding originals.
BEFORE YOU START

How this works in practice

Two questions to check scope

  • Which commission, tariff or agreement actually applies?
  • What connected equipment and shared services could materially affect distribution reliability?
  • Who can implement and verify protections that span utility, aggregator and vendor systems?

Worked scenario

A utility and a battery aggregator assess the shared services that support a group of connected storage sites. They identify the operations that affect reliability, confirm which organization manages accounts and recovery for the shared service, and organize implementation around the most consequential dependencies.

What to read next

  • DOE Electricity Cybersecurity RMP

    Use the risk management process for executive decisions about treatment and remaining exposure.

  • DOE C2M2

    Use the maturity model to assess whether practices operate across the broader function.

DATES AND TRIGGERS

Official milestones

See the deadline calendar
The whole journeyabout 31 days across 4 steps
  1. 01Confirm adoption and scope the assets, Regulatory counsel + distribution operator + aggregator lead, about 6 days
  2. 02Map baselines and choose the first work, OT security lead + service owners + supplier assurance, about 8 days
  3. 03Implement through operations and vendor agreements, Engineering + procurement + operations change owner, about 12 days
  4. 04Verify coverage and report progress, Control owners + independent reviewer + regulatory liaison, about 5 days
IMPLEMENTATION ROADMAP

Step by step

Checklist, instructions and 4 templates.

View plan as a table
Project roadmap with current target dates and completion status
StepOwnerWhen to actEstimated targetDeliverablesStatus
Confirm adoption and scope the assetsRegulatory counsel + distribution operator + aggregator leadBefore budget, rollout or regulatory commitmentSet a start dateAdoption and asset scope decisionOpen
Map baselines and choose the first workOT security lead + service owners + supplier assuranceBefore committing the roadmapSet a start dateBaseline control and priority crosswalkOpen
Implement through operations and vendor agreementsEngineering + procurement + operations change ownerBefore changes and supplier renewalsSet a start dateImplementation plan and responsibility recordOpen
Verify coverage and report progressControl owners + independent reviewer + regulatory liaisonAfter each phase and at applicable review datesSet a start dateVerification pack and exception registerOpen
0 of 4 completeOpen workspace

Targets use illustrative calendar-day estimates and assume the steps run in sequence. Check official dates and agree real durations with your team.

  1. 01

    Confirm adoption and scope the assets

    Who Regulatory counsel + distribution operator + aggregator lead When Before budget, rollout or regulatory commitment

    Record the applicable requirements, due dates and responsible entities. Map the operational outcomes, assets, sites and vendor services. Assign a consequence rating and explain any exclusions.

    What to produce

    Adoption and asset scope decisionAdoption memo and critical asset spreadsheet

    Gather first

    • Utility orders
    • Tariffs and agreements
    • Service inventory
    • DER site register
    • Dependency map

    How to prepare it

    1. Record the authority, applicable clause, covered entity, due date and approving owner. For voluntary adoption, record the internal decision and review date.
    2. List assets, shared services, owner, operator, location grouping and effect on distribution reliability. Explain the consequence rating and the source of each entry.
    3. Review disputed scope with the utility and aggregator. Keep named owners, exclusion rationale and a signed scope version.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Worked asset scope
    A controller service supports three battery sites and is shared across two contracts. Retain it in the asset list with both contracts, one named service owner and the affected distribution operation.

    Check before handing it over

    Every included or excluded material dependency has a written rationale and an owner.

    Send the approved asset list to security, operations and procurement.

  2. 02

    Map baselines and choose the first work

    Who OT security lead + service owners + supplier assurance When Before committing the roadmap

    Record the baseline reference and the assets and teams responsible for implementation. Compare existing safeguards against the baseline and use the interim guidance to sequence gaps. Agree owners and escalation thresholds.

    What to produce

    Baseline control and priority crosswalkBaseline-to-asset spreadsheet

    Gather first

    • Approved asset inventory
    • Baselines
    • Interim guidance
    • Current policies and evidence

    How to prepare it

    1. Create one row per baseline and relevant asset grouping. Record the reference, owner, current evidence, gap and required due date.
    2. Apply the scoping and prioritization criteria to choose the first work. Document risk from dependencies and exceptions.
    3. Review ownership across utility and vendor teams. Add acceptance criteria, effort and schedule for each priority item.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Worked control row
    Baseline 2.R addresses system backup and restoration planning. The service owner attaches the current plan, identifies an untested dependency and schedules an approved restoration exercise before treating the gap as resolved.

    Check before handing it over

    Each priority links to an asset, an actual baseline and a testable gap.

    Route the approved priorities to change planning.

  3. 03

    Implement through operations and vendor agreements

    Who Engineering + procurement + operations change owner When Before changes and supplier renewals

    Agree implementation, support and evidence duties with each party. Define test and rollback criteria, authorize the change window, and preserve required operations and recovery paths.

    What to produce

    Implementation plan and responsibility recordChange plan and supplier responsibility schedule

    Gather first

    • Priority crosswalk
    • Support agreements
    • Safety procedures
    • Change windows
    • Acceptance checks

    How to prepare it

    1. Assign a lead, system owner, supplier contact and reviewer. Write who operates each shared control and who reports failures.
    2. Set the planned change window and acceptance evidence. Define the condition for rolling back and who can make that decision.
    3. Review dependencies and safety constraints with operations. Save approval and arrange for a safe follow-up check.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Worked supplier handoff
    The aggregator maintains the service configuration backup. The utility provides a scheduled test window and signs off on restoration evidence. Both name an escalation contact.

    Check before handing it over

    The implementation has approved roles, timing, acceptance criteria and a rollback decision owner.

    Pass the approved work to the change owner and independent reviewer.

  4. 04

    Verify coverage and report progress

    Who Control owners + independent reviewer + regulatory liaison When After each phase and at applicable review dates

    Check the deployed control against its stated coverage and expected result. Reconcile exceptions, material inventory change and vendor dependencies. Report progress and remaining risk to the correct decision maker.

    What to produce

    Verification pack and exception registerEvidence index and exception report

    Gather first

    • Change records
    • Review plan
    • Operating evidence
    • Approved scope
    • Reporting dates

    How to prepare it

    1. Trace implemented work to the asset crosswalk and record the test method, date, result and reviewer.
    2. Log failed checks or missing coverage with an owner, approved interim safeguards and a follow-up date.
    3. Reconcile evidence to the reporting scope. Submit the approved summary to the appropriate internal or external recipient and retain the receipt.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Worked exception decision
    A scheduled restoration proves the primary site can recover. A connected site lacks valid evidence, so it stays open in the exception register pending a separate exercise.

    Check before handing it over

    Progress totals reflect actual asset coverage and each exception has a decision and due date.

    Send the approved summary to the operator and any required oversight body.

PRIMARY REFERENCES

Official sources

How we build these guides

Keyboard shortcuts

⌘K or /
Search everything
?
This list
g h
Home
g l
Guide library
g f
Find my path
g t
Templates
g p
Playbooks
g w
My workspace
g d
Deadline calendar
g c
Regulatory changes