Start hereSet the profile scope
~77 days leftOpen step
Guide library
Framework Global

NIST CSF 2.0

NIST Cybersecurity Framework 2.0

Create a common view of cybersecurity risk and turn gaps into an action plan.

Who it applies to

Organizations of any size seeking an outcomes-based way to govern and improve cybersecurity risk.

What you’ll produce

Current and Target Organizational Profiles and a prioritized improvement plan.

CSF outcomes provide a common language. Choose implementation controls based on your risks, obligations and resources.

See CISA’s latest exploited vulnerabilities
TEAM KICKOFF

Run the project

Go to the roadmap

Decisions for leadership

Which services must keep running?
Ask leadership to name essential services and the consequences it can tolerate. Start with a business objective such as shipping orders or delivering care, then identify supporting technology.
Which gaps will we pay to close first?
Use impact, threat exposure and dependencies to rank outcomes. Ask Engineering for estimated people and tooling costs, and name the executive permitted to accept residual risk.
How do we measure progress?
Agree what evidence will show the target is met. Decide which service owners report changes and how often the risk forum reviews exceptions.

How to spend the first week

  1. Choose an essential service and map who relies on it, what can interrupt it, and which suppliers and teams keep it running.
  2. Inspect one real outcome from each function relevant to your scope. For example, restore one workload and time how long it takes.
  3. Review the gaps with the sponsor. Choose the first funded change, its owner, and how the business will confirm it worked.

What to review each week

Track high-priority target outcomes without evidence, open work whose dependencies have slipped and risks that have passed their approval expiry.

Kickoff brief to share with your team

Fill this in with your sponsor and send it to the people who own the work.

NIST CSF 2.0 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  Set the profile scope · Risk lead + 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. Choose an essential service and map who relies on it, what can interrupt it, and which suppliers and teams keep it running.
2. Inspect one real outcome from each function relevant to your scope. For example, restore one workload and time how long it takes.
3. Review the gaps with the sponsor. Choose the first funded change, its owner, and how the business will confirm it worked.
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.
Plan evidence for NIST CSF 2.0 and other programs
The whole journeyabout 77 days across 4 steps
  1. 01Set the profile scopeRisk lead + leadership · ~14 days
  2. 02Build the Current ProfileSecurity + service owners · ~21 days
  3. 03Set the Target ProfileLeadership + risk owners · ~14 days
  4. 04Execute and refreshControl owners · ~28 days
IMPLEMENTATION ROADMAP

Step by step

Checklist, instructions and 11 templates.

View plan as a table
Project roadmap with current target dates and completion status
StepOwnerWhen to actEstimated targetDeliverablesStatus
Set the profile scopeRisk lead + leadershipAt initiationSet a start dateScope memo; Stakeholder list; Risk contextOpen
Build the Current ProfileSecurity + service ownersAfter discoverySet a start dateCurrent Profile; Evidence inventoryOpen
Set the Target ProfileLeadership + risk ownersAfter current state assessmentSet a start dateTarget Profile; Gap analysis; Funding decisionOpen
Execute and refreshControl ownersOngoingSet a start dateAction plan; Measures; Updated profilesOpen
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

    Set the profile scope

    Who Risk lead + leadership When At initiation

    Set business objectives, critical services, obligations and stakeholders. Decide which environments and third parties belong in the profile.

    How to do this step

    Before you start

    Business objectives, inventory, stakeholder requirements, recent incidents and critical service maps.

    1. Choose an organizational scope or a clearly bounded service. Record the outcome it supports and named owners for assets and vendors.
    2. List business, legal and threat drivers. Keep the reason for selecting outcomes with the profile.
    3. Agree with the sponsor on assumptions, exclusions and the time horizon for setting the target.

    What a reviewer should see

    The scope says that fulfillment depends on the warehouse API and identity provider and names the owners who verified those dependencies.

    When to escalate

    Escalate an essential service whose owner or upstream dependencies are unknown.

    What to produce

    Scope memoMemo

    Gather first

    • Service inventory and architecture
    • Customer commitments and contracts
    • Applicable criteria or legal text

    How to prepare it

    1. Write the exact decision this memo supports. Name the legal entity, service, environments and dates. Attach a boundary diagram and state which people, vendors and processes can affect the scope.
    2. List the exclusions next to the inclusion list. Give a reason for each one and describe any shared service that crosses the boundary.
    3. Review the draft with service owners and the person making the decision. Freeze the approved version and add a review date or trigger for changes.

    Worked example

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

    Decision
    Cover the hosted billing service for the April to June review.
    In scope
    Production billing API, hosting, releases and production access.
    Excluded and why
    Internal HR tool. It has no access to billing systems or data.
    Dependencies
    Cloud hosting and corporate identity provider.
    Approval
    Service owner approves after checking the architecture and contract.

    Check before handing it over

    A reviewer can use the memo to classify a named system and see how shared dependencies are handled.

    Give the approved scope and any open questions to whoever will map requirements, select samples or review the engagement.

    Stakeholder listMemo

    Gather first

    • Named roles, on-call contacts and authority
    • Realistic use cases and deadlines
    • Service and vendor dependencies

    How to prepare it

    1. Start with the event or decision and identify who acts first, who has approval authority and who covers absences.
    2. Write the sequence of handoffs and the information each recipient needs. Name the channel, timing and escalation if no one responds.
    3. Rehearse a case and record what broke. Fix missing contacts, duplicate ownership or gaps before approving the playbook or role map.

    Worked example

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

    Event or activity
    Unusual activity detected in support export portal
    First action and owner
    On-call engineer opens a restricted incident case and preserves logs.
    Decision owner and backup
    Privacy lead or legal duty contact will determine reporting.
    Handoff and clock
    Send incident ID, UTC timestamp and known scope immediately.
    Validation
    Exercise completed and backup contact reached.

    Check before handing it over

    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.

    Risk contextSpreadsheet

    Gather first

    • Processing or service design and affected people
    • Threats, consequences and assessment triggers
    • Risk methodology and current safeguards

    How to prepare it

    1. Screen the activity against the applicable assessment trigger. Describe the real scenario and who or what could be harmed. Record likelihood and consequence using your criteria.
    2. Describe existing safeguards. Decide what reduces the risk and what risk remains after those measures. For a required impact assessment, document necessity, alternatives and consultation where applicable.
    3. Send the result to the person who can approve, change or stop the activity. Set a review trigger and keep evidence of the decision.

    Worked example

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

    Activity and risk
    Account recovery could expose invoices to an impersonator.
    Affected people or assets
    Customer account contacts and invoices
    Current controls
    Recovery uses verified channel. Sampled evidence linked.
    Proposed treatment
    Require a second check for requests to change the billing address.
    Remaining risk and decision
    Moderate under company method. Approval required before launch.
    Owner and review trigger
    Product risk owner, repeat when recovery flow changes

    Check before handing it over

    The assessment explains the potential harm, why each measure helps and who accepts the remaining risk.

    Give the signed review to the owner of the launch or processing decision. Use the regulator’s assessment form where one applies.

  2. 02

    Build the Current Profile

    Who Security + service owners When After discovery

    Map existing cybersecurity outcomes across Govern, Identify, Protect, Detect, Respond and Recover. Link each assessed outcome to evidence.

    How to do this step

    Before you start

    Selected outcomes, actual configurations, tickets, security events and recent test results.

    1. Ask owners to explain and demonstrate how the outcome is achieved. Use source evidence when available and record its date and boundary.
    2. Record what actually happens in operation. For a backup recovery outcome, inspect the date, scope, elapsed time and integrity check from a real restore exercise.
    3. Mark gaps and evidence limitations explicitly. Validate the Current Profile with the service and risk owners.

    What a reviewer should see

    One current outcome links to the last restore test and states that the order processing database recovered successfully while the queue dependency was outside the test.

    When to escalate

    Raise an outcome recorded as achieved when a critical dependency has never been tested or observed.

    What to produce

    Current ProfileSpreadsheet

    Gather first

    • Baseline evidence
    • Approved target or success definition
    • Dates, denominator and responsible service

    How to prepare it

    1. Pick a measure or outcome with a clear definition. Record the population, reporting period and evidence source so others can calculate it.
    2. Record the current state, target and gap. Add the change needed, accountable owner and next date to collect evidence.
    3. Check the numbers against source data and explain material exceptions or changes in scope before sharing.

    Worked example

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

    Outcome
    Administrators receive quarterly access review.
    Current and evidence
    11 of 12 eligible roles reviewed, IAM export as of 30 Sep 2026.
    Target
    All eligible roles reviewed
    Gap and action
    One role missed. Reconcile new roles before next review.
    Owner and review
    IAM lead, next quarter

    Check before handing it over

    The baseline and target use comparable scope. A reviewer can find the denominator and supporting records.

    Use approved gaps to prioritize the roadmap and refresh the baseline after the next review.

    Evidence inventorySpreadsheet

    Gather first

    • Control descriptions and test request
    • Source system records
    • Defined period and evidence access rules

    How to prepare it

    1. Create a register keyed by control, requirement or request. Export native records with the filters, timestamps and operator details needed to interpret them.
    2. Link to a restricted copy of each artifact. Note time zone, scope, date range, export method and whether the evidence shows design or actual operation.
    3. Test the links using the reviewer’s permissions. Flag missing periods or evidence and track a follow-up instead of filling in records retrospectively.

    Worked example

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

    Evidence ID
    EV-021
    Control or request
    AC-04, October administrator review
    Period and scope
    1 to 31 Oct 2026 UTC, production tenant
    Source and capture
    IAM export filtered to active elevated roles
    Link or record ID
    Restricted workpaper EV-021 plus ticket IAM-114
    Reviewer and status
    Security assurance, verified

    Check before handing it over

    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.

  3. 03

    Set the Target Profile

    Who Leadership + risk owners When After current state assessment

    Prioritize target outcomes with stakeholders. Use Tiers where useful to communicate the rigor of risk governance and management.

    How to do this step

    Before you start

    Current Profile, impact tolerances, known threats, cost estimates and work dependencies.

    1. Describe what needs to improve and for which assets. Set an observable measure and the date by which the team expects to meet it.
    2. Compare current and target outcomes. Rank gaps using customer or operational impact, external exposure, cost and dependencies.
    3. Write implementation tickets with clear completion evidence. Give tradeoffs and risks outside the funded plan to the decision owner.

    What a reviewer should see

    The target says the order service, including its queue, must restore to the agreed business tolerance and identifies the exercise that will demonstrate it.

    When to escalate

    Raise any target that lacks a funding decision, an owner or a test.

    What to produce

    Target ProfileSpreadsheet

    Gather first

    • Baseline evidence
    • Approved target or success definition
    • Dates, denominator and responsible service

    How to prepare it

    1. Pick a measure or outcome with a clear definition. Record the population, reporting period and evidence source so others can calculate it.
    2. Record the current state, target and gap. Add the change needed, accountable owner and next date to collect evidence.
    3. Check the numbers against source data and explain material exceptions or changes in scope before sharing.

    Worked example

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

    Outcome
    Administrators receive quarterly access review.
    Current and evidence
    11 of 12 eligible roles reviewed, IAM export as of 30 Sep 2026.
    Target
    All eligible roles reviewed
    Gap and action
    One role missed. Reconcile new roles before next review.
    Owner and review
    IAM lead, next quarter

    Check before handing it over

    The baseline and target use comparable scope. A reviewer can find the denominator and supporting records.

    Use approved gaps to prioritize the roadmap and refresh the baseline after the next review.

    Gap analysisSpreadsheet

    Gather first

    • Baseline evidence
    • Approved target or success definition
    • Dates, denominator and responsible service

    How to prepare it

    1. Pick a measure or outcome with a clear definition. Record the population, reporting period and evidence source so others can calculate it.
    2. Record the current state, target and gap. Add the change needed, accountable owner and next date to collect evidence.
    3. Check the numbers against source data and explain material exceptions or changes in scope before sharing.

    Worked example

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

    Outcome
    Administrators receive quarterly access review.
    Current and evidence
    11 of 12 eligible roles reviewed, IAM export as of 30 Sep 2026.
    Target
    All eligible roles reviewed
    Gap and action
    One role missed. Reconcile new roles before next review.
    Owner and review
    IAM lead, next quarter

    Check before handing it over

    The baseline and target use comparable scope. A reviewer can find the denominator and supporting records.

    Use approved gaps to prioritize the roadmap and refresh the baseline after the next review.

    Funding decisionMemo

    Gather first

    • Agenda or decision request
    • Current performance measures and findings
    • Proposed actions and participants

    How to prepare it

    1. Write what decision is needed and list the reports or records the decision maker reviewed. Capture the date, people and decision authority.
    2. Record the decision, alternatives considered, any remaining risk and exactly who will do what by when.
    3. Send notes for factual review. File the approved record and add actions to the working tracker so progress reaches the next review.

    Worked example

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

    Item
    Approve a fix for the missing access-removal retry.
    Inputs reviewed
    September test results and IAM incident root-cause notes.
    Decision
    Approve automatic retry plus daily reconciliation.
    Action and due date
    Platform lead to ship and test by 2026-11-28.
    Residual risk and follow-up
    Manual review remains until rollout. Check at December meeting.

    Check before handing it over

    The minutes identify the person who approved each action and the date the decision will be revisited.

    Give owners the actions and add the approved record to the relevant audit or governance file.

  4. 04

    Execute and refresh

    Who Control owners When Ongoing

    Assign remediation actions, measures and review dates. Refresh profiles after major changes or significant incidents.

    How to do this step

    Before you start

    Funded action plan, baseline evidence, implementation records and risk approval decisions.

    1. Run the acceptance check before closing work. Compare it with the baseline and document remaining limitations.
    2. Update the Current Profile when operation changes. Track open work and report the impact of delays to the sponsoring team.
    3. Refresh target outcomes when threats, incidents, suppliers or business priorities change.

    What a reviewer should see

    A before-and-after test connects the funded work to the updated profile and records what still needs attention.

    When to escalate

    Escalate missed commitments affecting essential services or relevant risks accepted beyond their approval date.

    What to produce

    Action planSpreadsheet

    Gather first

    • Finding, risk or test exception
    • Root-cause analysis
    • Named owner, due date and expected evidence

    How to prepare it

    1. Record the observation and link the exact test or requirement. Describe the business effect and investigate why the issue was able to happen.
    2. Separate immediate containment from the permanent fix. Give each action an owner, date, verification method and any required approval for deferral.
    3. Retest against the original failure once the fix is live. Record who accepted the outcome and keep unresolved issues visible.

    Worked example

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

    Finding or risk
    F-008, a departed contractor retained production access
    Cause and effect
    HR event never reached IAM. Admin access remained active.
    Action and owner
    Revoke access and alert on failed HR sync. IAM lead.
    Due and status
    2026-11-28, in progress
    Closure test
    Simulate departure and verify access disappears within policy
    Approver and evidence
    Risk owner, ticket IAM-114 and retest results

    Check before handing it over

    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.

    MeasuresSpreadsheet

    Gather first

    • Baseline evidence
    • Approved target or success definition
    • Dates, denominator and responsible service

    How to prepare it

    1. Pick a measure or outcome with a clear definition. Record the population, reporting period and evidence source so others can calculate it.
    2. Record the current state, target and gap. Add the change needed, accountable owner and next date to collect evidence.
    3. Check the numbers against source data and explain material exceptions or changes in scope before sharing.

    Worked example

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

    Outcome
    Administrators receive quarterly access review.
    Current and evidence
    11 of 12 eligible roles reviewed, IAM export as of 30 Sep 2026.
    Target
    All eligible roles reviewed
    Gap and action
    One role missed. Reconcile new roles before next review.
    Owner and review
    IAM lead, next quarter

    Check before handing it over

    The baseline and target use comparable scope. A reviewer can find the denominator and supporting records.

    Use approved gaps to prioritize the roadmap and refresh the baseline after the next review.

    Updated profilesSpreadsheet

    Gather first

    • Baseline evidence
    • Approved target or success definition
    • Dates, denominator and responsible service

    How to prepare it

    1. Pick a measure or outcome with a clear definition. Record the population, reporting period and evidence source so others can calculate it.
    2. Record the current state, target and gap. Add the change needed, accountable owner and next date to collect evidence.
    3. Check the numbers against source data and explain material exceptions or changes in scope before sharing.

    Worked example

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

    Outcome
    Administrators receive quarterly access review.
    Current and evidence
    11 of 12 eligible roles reviewed, IAM export as of 30 Sep 2026.
    Target
    All eligible roles reviewed
    Gap and action
    One role missed. Reconcile new roles before next review.
    Owner and review
    IAM lead, next quarter

    Check before handing it over

    The baseline and target use comparable scope. A reviewer can find the denominator and supporting records.

    Use approved gaps to prioritize the roadmap and refresh the baseline after 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