Start hereDefine the function and evidence boundary
~20 days leftOpen step
Guide library
Framework North America

DOE C2M2

DOE C2M2 v2.1 cybersecurity maturity self-assessment

Use C2M2 to find which cybersecurity practices actually operate across a business function and turn the gaps into investment decisions. The same v2.1 model supports electricity, oil and natural gas teams and organizations in other sectors.

Issuing authority
U.S. Department of Energy, Office of Cybersecurity, Energy Security, and Emergency Response
Timing
DOE designed the model to support a self-evaluation for one function in one day. For a first assessment, schedule evidence collection before the workshop and executive review afterwards. Review action progress quarterly as an internal planning cadence and reassess following major changes or on the approved schedule.
Reviewed
Inside this guide
4 steps · 4 templates

Who it applies to

A voluntary self-assessment of a defined function and its supporting IT and operational technology. Use the earlier electricity and oil and gas editions for historical comparison, and record their version before comparing results. Track separate binding obligations in your own compliance register.

What you’ll produce

A repeatable, evidence-backed baseline across the ten domains, approved maturity targets for the assessed function and a funded improvement plan with retest dates.

C2M2 v2.1 groups 356 practices into ten domains. Each domain has its own cumulative maturity levels from MIL0 to MIL3. The tool counts Fully Implemented and Largely Implemented as performed. Partial implementation can block a higher level even when other practices at that level are operating. DOE offers no-cost facilitation to eligible U.S. energy organizations. Budget staff time, evidence review and remediation separately.

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 C2M2 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  Define the function and evidence boundary · Executive sponsor + function owner + IT and OT leads [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 business function needs a result that management can act on?
  • Which shared services and vendor responsibilities are inside that decision?
  • Who can approve funding and verify the next assessment?

Worked scenario

A utility scopes the assessment to distribution control. The OT lead brings access review and recovery drill records. A pipeline operator could use the same model for remote compressor monitoring, bringing contractor access records and restoration exercises. Both record where a shared IT service operates, who owns it and how evidence applies to the chosen function.

DATES AND TRIGGERS

Official milestones

See the deadline calendar
The whole journeyabout 20 days across 4 steps
  1. 01Define the function and evidence boundary, Executive sponsor + function owner + IT and OT leads, about 5 days
  2. 02Run the self-evaluation and validate scores, Facilitator + practice owners + independent reviewer, about 3 days
  3. 03Set targets and fund the work, Function owner + enterprise risk + finance, about 7 days
  4. 04Retest and report changes, Control owners + validation lead + leadership, 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
Define the function and evidence boundaryExecutive sponsor + function owner + IT and OT leadsBefore collecting evidenceSet a start dateAssessment charter and evidence mapOpen
Run the self-evaluation and validate scoresFacilitator + practice owners + independent reviewerAt the workshop and before releasing resultsSet a start datePractice scoring and review logOpen
Set targets and fund the workFunction owner + enterprise risk + financeAt the first governance review after assessmentSet a start dateFunded improvement and risk registerOpen
Retest and report changesControl owners + validation lead + leadershipAt closure, material changes and the next baselineSet a start dateRetest and leadership briefOpen
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

    Define the function and evidence boundary

    Who Executive sponsor + function owner + IT and OT leads When Before collecting evidence

    Identify the critical outcome, dependencies, locations and third parties. Assign a workshop facilitator and domain owners. Mark where shared services supply evidence and document exclusions and handling rules.

    What to produce

    Assessment charter and evidence mapSigned charter and evidence register

    Gather first

    • Service map
    • Asset inventory
    • Vendor list
    • Business impact assessment
    • Current C2M2 model

    How to prepare it

    1. Describe one function, its critical outcome, accountable owner, included locations and operational systems. Attach the boundary diagram and record excluded functions.
    2. List shared services and vendors, the practices they support and the team authorized to provide evidence. Assign a facilitator and named owners for the workshop.
    3. For each evidence source record the system, period, custodian, secure location and any gaps. Agree what can be summarized outside the workshop.

    Worked example

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

    Electricity example
    Distribution control covers two operating centers and associated remote access. Corporate identity is a dependency. Corporate payroll is outside the scope.
    Oil and gas example
    For compressor monitoring, include the dispatch center, contractor maintenance access and communications supporting monitoring. Record separately whether retail systems are outside the function.

    Check before handing it over

    The sponsor and operators agree the scope and can point to owners for each important dependency.

    Send the approved charter and evidence requests to workshop participants.

  2. 02

    Run the self-evaluation and validate scores

    Who Facilitator + practice owners + independent reviewer When At the workshop and before releasing results

    Use the current DOE tool and record the evidence and rationale for each practice response. Resolve conflicting answers, flag evidence gaps and calculate the highest cumulative level met in each domain.

    What to produce

    Practice scoring and review logWorkbook with one row per practice

    Gather first

    • DOE worksheet or tool export
    • Signed charter
    • Evidence map
    • Operator interviews

    How to prepare it

    1. Record the practice identifier, domain, level, response, evidence date and supporting explanation. Describe what is missing when a practice is only partly implemented.
    2. Walk through disagreements with the people operating the process. Record missing evidence and the date for verification, and rerun scoring once the disposition is agreed.
    3. Check each domain independently. Confirm that all practices in the target level and lower levels are marked performed before awarding that level.

    Worked example

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

    Fictional scoring decision
    The team reports an inherited account review for all sites. The export covers only one of two sites. Record the missing coverage and conservatively score the practice as Partially Implemented until the other site is verified.

    Check before handing it over

    The reviewer can reproduce each domain rating and trace disputed answers to the recorded evidence.

    Send the reviewed ratings and open questions to risk and finance.

  3. 03

    Set targets and fund the work

    Who Function owner + enterprise risk + finance When At the first governance review after assessment

    Choose a target for each domain based on operational consequences, threat exposure and resources. Convert each priority gap into an owner, cost estimate, dependency, milestone and measurable acceptance check. Obtain explicit decisions on deferred risks.

    What to produce

    Funded improvement and risk registerGovernance spreadsheet and decision note

    Gather first

    • Reviewed domain results
    • Threat profile
    • Business impact assessment
    • Budget and staffing forecasts

    How to prepare it

    1. Record current and target levels for each domain and explain the operational reason. Identify dependencies and high impact gaps that need attention regardless of maturity target.
    2. Break each approved gap into a deliverable, owner, budget range, milestone and independent acceptance check.
    3. Obtain a recorded decision on funding or deferral. Assign interim safeguards, an accountable risk owner and a date to reconsider deferred items.

    Worked example

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

    Fictional budget decision
    Vendor account review is incomplete for two remotely supported stations. Fund an owner to reconcile the vendor roster with active accounts at both sites and show signed exception decisions before closure.

    Check before handing it over

    Each approved action can be funded, scheduled and tested by a person other than its owner.

    Give the approved work and dates to delivery leads.

  4. 04

    Retest and report changes

    Who Control owners + validation lead + leadership When At closure, material changes and the next baseline

    Retest completed actions using fresh operational evidence. Compare equivalent scope and model versions when reporting progress, and explain differences. Keep assessment results in the approved repository and share a summary with leadership.

    What to produce

    Retest and leadership briefRetest log and one page executive brief

    Gather first

    • Baseline and scoring rationale
    • Change records
    • Current operational evidence
    • Action register

    How to prepare it

    1. Freeze the retest scope and collect independent operating evidence for the agreed period. Compare sample results to the acceptance check and reopen failed actions.
    2. Show baseline, current and target maturity by domain. Flag changes in version, scope or evidence quality that limit comparison.
    3. List the highest unresolved operational exposures, assigned decisions, budget and upcoming dates. Store detailed evidence in the approved repository.

    Worked example

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

    Fictional retest
    The reviewer traces active contractor accounts at both stations to approved owners and current access decisions. One expired account was still active, so the action remains open pending correction and a fresh review.

    Check before handing it over

    Leadership can distinguish closed work, failed retests and open risk decisions.

    Update the action register and schedule the next review.

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