Business & Strategy
NIST CSF 2.0 Current and Target Profiles: Map Six Functions, Rank the Gaps, Plan Fixes
Advanced | 4 whiteboard pages · Task board: 5 columns (4 parent tasks, 12 subtasks)
Advanced: Assumes you know the technical terms and methods, and the steps are only outlined. Work through it on your own, guided by decision criteria and points to check.
Set a current profile beside a target profile across the six NIST CSF 2.0 Functions, then turn the gap into a prioritized improvement plan. Fill in four steps: set the goal and scope, rate each Function with evidence, rank the gaps by risk reduction and effort, then assign actions with owner, due date, and measure. Rate the current state on your own scale; if you use CSF Tiers too, they are not maturity levels. Unlike raising every maturity score, you pick the level each Function needs, so not everything lands on the top. It usually stalls when you fill every category at once, skip Govern, or aim everything at the top level; the board covers each. Start by opening your system inventory and listing one business, system, and site; review quarterly. Verify Function names against the latest NIST publication. This template was not made or reviewed by NIST or any other public agency. Four board pages; five task columns with four parent tasks of three subtasks each.
Once you have a free account, you can copy this template from the marketplace
Whiteboard preview
Read the whiteboard text as plain text
NIST CSF 2.0 Current and Target Profiles
How to use (4 pages): ① Write the goal and scale, and set the scope (boards①–⑤) → ② Describe the six Functions' current state with evidence; check pitfalls (boards⑥–⑨) → ③ Find the gaps and rank them by risk reduction and effort (boards⑩–⑫) → ④ Turn gaps into actions with owner, due date, and measure; review quarterly (boards⑬⑭)
1/4 Set scope and goal
① Goal and scale of the profile (start writing here)
- Why build the profile e.g. Let leadership and staff answer a customer's security questionnaire with the same explanation
- Who draws it and who approves it e.g. IT and each department head draw it, and the management meeting approves it
- Scale for the current state (set your own) e.g. 0 = not started 1 = partly done 2 = done across the scope 3 = measuring and improving
② The six CSF 2.0 Functions (write the outcomes that serve the goal in ①, in your own words)
- Our profile
- Govern GOVERN e.g. Risk policy, roles, and responsibilities are set, and leadership approves and monitors them. This steers the other five
- Identify IDENTIFY e.g. We know which assets to protect and the risks they carry
- Protect PROTECT e.g. Access control, training, and data protection are in place
- Detect DETECT e.g. We have a way to notice and investigate unusual activity
- Respond RESPOND e.g. Contacts and steps for when something happens are decided
- Recover RECOVER e.g. The steps and order for restoring from backups are decided
③ Scope: business
- e.g. The online sales business
- Out of scope: e.g. the old service ending this year
- Decided by: e.g. head of the business unit
④ Scope: system
- e.g. The order system and the member database
- Out of scope: e.g. the test environment (next quarter)
- Source of information: e.g. the system inventory
⑤ Scope: site
- e.g. Headquarters and the distribution warehouse (2 sites)
- Out of scope: e.g. overseas sales agents
- Check with: e.g. the general affairs lead at each site
2/4 Draw the current state
⑥ Current profile for the scope in ③–⑤ (rate on the ① scale; Tiers are not maturity levels)
| Outcome to watch (your words) | Current (① scale) | Evidence | Owner | |
|---|---|---|---|---|
| Govern (GV) | e.g. Leadership approves roles and responsibilities | e.g. 1: Policy exists but approval is not recorded | e.g. Policy update record | e.g. Executive owner and head of general affairs |
| Identify (ID) | e.g. Assets are listed | e.g. 1: Inventory covers headquarters only | e.g. System inventory | e.g. IT staff |
| Protect (PR) | e.g. Admin accounts are protected | e.g. 1: Multi-factor authentication for some admins only | e.g. Settings screen | e.g. IT staff |
| Detect (DE) | e.g. We can notice unusual activity | e.g. 1: Logs exist but nobody reviews them | e.g. Vendor confirmation | e.g. TBD |
| Respond (RS) | e.g. Response steps exist | e.g. 0 (provisional): no contact list found | e.g. Unconfirmed | e.g. Head of general affairs |
| Recover (RC) | e.g. We can restore from backups | e.g. 1: Backups are taken but never restored | e.g. Backup records | e.g. Outsourced vendor |
⑦ Pitfall: filling everything at once
- What happens: e.g. Every category is listed, the rating never ends, and after 2 months the table in ⑥ is still half empty
- How to check: e.g. Count the empty rows in ⑥ and the time spent rating
- Prevention: e.g. Start with the Functions that serve the goal in ① and defer the rest to the next quarter
⑧ Pitfall: skipping Govern, tech only
- What happens: e.g. Products get introduced, but nobody decides who decides and who is accountable
- How to check: e.g. Can the Govern row in ⑥ cite a record approved by leadership as evidence?
- Prevention: e.g. Fill the Govern row first and put one leadership member among the owners
⑨ Pitfall: setting every target to the top
- What happens: e.g. Every Function targets the top level, gaps balloon, and the plan becomes impossible to carry out
- How to check: e.g. Can you state in one sentence why each target level in ⑫ is needed?
- Prevention: e.g. Choose the level each Function needs from business risk and budget
3/4 Rank gaps by priority
⑩ Find gaps from the table in ⑥ (per row: current → gap → desired state)
- As-Is Current state e.g. Detect: logs are collected, but who reviews them and how often is not decided (level 1)
- Gap and issue e.g. It takes days to notice unusual activity, so the response starts late
- To-Be Desired state e.g. Staff check the logs of critical systems every business day (level 2)
⑪ Priority of the gaps in ⑩ (risk reduction × effort)
Vertical axis: Risk reduction (low → high) / Horizontal axis: Effort (low → high)
- Do first (high reduction, low effort) e.g. Standardize admin MFA on passkeys, with an authenticator app where passkeys are not yet usable
- Plan and proceed (high reduction, high effort) e.g. Write the restore procedure from backups and actually restore to verify it
- Fit in when possible (low reduction, low effort) e.g. Tidy permissions on unused shared folders
- Skip this time (low reduction, high effort) e.g. Replace devices at every site at once. Re-plot it on the matrix next quarter
⑫ Top three gaps from ⑪: target and reason (the target is the needed level, not the highest)
| Gap (current → target) | Target level | Reason | |
|---|---|---|---|
| Priority 1 | e.g. Admin MFA covers only some admins | e.g. 2: all admins covered | e.g. A hijacked admin account reaches every system |
| Priority 2 | e.g. Roles and responsibilities lack a record of leadership approval | e.g. 2: leadership approves and the policy records it | e.g. Without deciding who decides and who is accountable, other improvements stall |
| Priority 3 | e.g. Nothing has ever been restored from backup | e.g. 2: a procedure exists and a restore is recorded | e.g. To shorten business downtime in a ransomware attack |
4/4 Plan, run, and review
⑬ Turn the gaps in ⑫ into actions (owner, due date, measure)
| Action | Owner | Due | Measure | |
|---|---|---|---|---|
| Action 1 | e.g. Standardize admin MFA | e.g. IT staff | e.g. End of month 1 | e.g. Share of admins configured in the admin console |
| Action 2 | e.g. Match admin accounts to the inventory | e.g. IT staff | e.g. End of month 1 | e.g. Share of admin accounts matching the inventory |
| Action 3 | e.g. Leadership approves roles and responsibilities | e.g. Executive owner and head of general affairs | e.g. End of month 1 | e.g. Share of defined roles with an assigned person |
| Action 4 | e.g. Write the restore procedure from backups | e.g. Outsourced vendor and general affairs | e.g. End of month 2 | e.g. Number of critical systems with a restore procedure |
| Action 5 | e.g. Actually restore one system | e.g. Outsourced vendor | e.g. End of the quarter | e.g. Time taken to finish restoring |
⑭ Quarterly review (four steps against the pitfall of never reviewing it)
- Collect Collect the numbers e.g. Each owner enters the ⑬ numbers the week before the review
- Redraw Update the current profile e.g. At the start of review week, IT staff raise a level in ⑥ only for rows with evidence
- Reselect Revisit gaps and priorities e.g. Owners meet and reshuffle ⑪ and the top three in ⑫. If the business or sites change, fix ③–⑤ first
- Report Report to leadership and move to the next quarter e.g. Report how the top three gaps changed at the management meeting in 10 minutes
Task board contents
Not started 16 items
Set scope and goal
On page 1, set the goal of the profile, the scale for rating the current state, and the scope. Once the scope is set, the rows for the page 2 table and where to collect evidence become clear. Press Ctrl+F (⌘F on Mac) and type "3/4" to jump to page 3.
List scope items
Open your system inventory (or the org chart if you have none), write the goal in one line on the first note of board①, and list the business, system, and site in scope on boards③–⑤, one each. It takes about 15 minutes, and once it is set the rows on page 2 can be written.
Choose the scale
On the third note of board①, write a scale such as 0–3 and what each level means. Done when leadership and staff read it the same way.
Goal per Function
On the six Function notes of board②, write one outcome each that relates to the goal in ①, in your own words. Write Govern first rather than leaving it for later.
Draw current state
On page 2, draw the current profile for the scope in ③–⑤. Leaving no unsupported "done" is what makes the gaps on page 3 reliable.
Rate each Function
In the six rows of the table in board⑥, write the outcome to look at, the current level on the ① scale, and the owner. Done when every row has a level. If you cannot fill everything at once, start with the rows that serve the goal in ①.
Check the evidence
In the evidence column of board⑥, write how you checked: inventory, settings screen, admin console, update record, or vendor confirmation. Write "unconfirmed" for rows you cannot check and keep the level provisional.
Check the pitfalls
For the three pitfalls in boards⑦–⑨, rewrite what happens, how to check, and the preventive step for your own situation. If one applies, fix the table in ⑥ on the spot.
Rank the gaps
On page 3, write the gaps between current and target, and rank them by risk reduction and effort. The top gaps you pick become the source of the actions on page 4.
List the gaps
In the three steps of board⑩, write the current state, the gap, and the desired state from the rows of ⑥, one row at a time. Add a note for every row that shows a gap.
Plot on the matrix
In board⑪, place the gaps from ⑩ by risk reduction and effort. Done when every gap sits in some quadrant.
Explain the top 3
In the table of board⑫, write the top three gaps, the target level, and the reason. If a target is the highest level, check that you can explain in the reason column why it is really needed.
Plan, run, review
On page 4, turn the chosen gaps into actions with an owner, due date, and measure, and set up the quarterly review. Add the actions in ⑬ as tasks and follow the ones you have started in the Improving column of the task board.
Assign actions
In the table of board⑬, write actions, owners, and due dates, centered on the gaps in ⑫. You may split one gap into two actions or add other gaps found in ⑥. Done when every row has an owner.
Set the measures
In the measure column of board⑬, write numbers you can count from the inventory or admin console. Rewrite any measure that ends in done or not done as a rate or a count.
Schedule reviews
Following the four steps of board⑭, decide who runs the quarterly review and when. Done when the next review is on the calendar of everyone taking part.