Security programme self-assessments often produce a single maturity number that nobody can explain, defend or act on, because the scale, evidence rules and scope were never written down. This template gives you a repeatable worksheet across the six NIST CSF 2.0 Functions (Govern, Identify, Protect, Detect, Respond and Recover) and their 22 Categories, with a defined five-level maturity scale, evidence requirements, a target-setting step and a results summary for leadership. It uses the CSF 2.0 Tiers (Partial, Risk Informed, Repeatable, Adaptive, from NIST CSWP 29 published 26 February 2024) as a cross-check on how risk is governed and managed, rather than as the score itself. It is written for CISOs, GRC leads and internal assessors running an annual or pre-investment self-assessment. For the maturity concepts behind it see the GRC Maturity Model; for subcategory-level Current and Target Profiles use the CSF 2.0 Organisational Profiles Template.
How to use this template
- Replace text in square brackets, such as [Organisation], [Assessment lead] and [Scope], with your own values.
- Assess at Category level for a programme view (22 Categories). Drop to Subcategory level only where a Category scores low or matters most; that detail belongs in an Organisational Profile.
- Agree the scale and evidence rules in sections 3 and 4 before any interviews. Changing them mid-assessment invalidates comparisons.
- Set the target level for each Category from risk and requirements, not from what seems achievable.
- Repeat with the same scale each year so results show trend. Keep the completed worksheet and evidence index as the audit trail.
1. Assessment scope and context
| Field | Entry |
|---|---|
| Assessment ID and date | [SPMA-2026-01, DD Month YYYY] |
| Purpose | [Annual baseline / board request / pre-budget / post-incident / regulatory preparation] |
| Scope | [Whole organisation / business unit / critical service] |
| Exclusions and rationale | [For example OT environment assessed separately] |
| Previous assessment | [ID and date, or "first assessment"] |
| Frameworks referenced | [NIST CSF 2.0; optionally ISO/IEC 27001:2022, CIS Controls v8.1] |
2. Assessment team and participants
| Role | Responsibility | Name |
|---|---|---|
| Sponsor | Commissions the assessment, receives results, approves targets | [Name] |
| Assessment lead | Plans, runs workshops, applies the scale consistently, drafts the report | [Name] |
| Category respondents | Describe current practice and supply evidence | [One owner per Category] |
| Calibration reviewer | Samples evidence and challenges scores before results are final | [Second line or internal audit] |
A self-assessment is only as credible as its challenge step. Where possible, have someone outside the Security Function review a sample of scores.
3. Maturity scale
| Level | Name | Description |
|---|---|---|
| 0 | Absent | No activity addressing the Category |
| 1 | Initial | Activity happens ad hoc, depends on individuals and covers part of the scope |
| 2 | Developing | Activity is planned and partly documented; applied in some areas or inconsistently |
| 3 | Defined | Approved policy and procedures exist and are applied across the scope, with named owners |
| 4 | Managed | Performance is measured against targets, reviewed regularly and corrected when it drifts |
| 5 | Optimised | Practice improves continuously from metrics, lessons learned and threat changes, and is automated where sensible |
Use whole numbers. If a Category sits between two levels, score the lower and record what is missing in the gap column.
4. Evidence rules
- Level 1 and 2: respondent description plus at least one example (ticket, email, report).
- Level 3: approved policy or standard, procedure, named owner, and sample records showing it is applied across the scope.
- Level 4: level 3 evidence plus metrics with targets, at least two reporting periods of results, and records of corrective action.
- Level 5: level 4 evidence plus documented improvements made from metrics or lessons learned in the last 12 months.
- Evidence age: evidence older than 12 months does not support level 3 or above.
- No evidence: the score is capped at 1 regardless of the description.
5. Self-assessment worksheet
Score each Category. The prompts are starting questions; add your own. Record the evidence reference so the calibration reviewer can sample it.
| Function | Category | Assessment prompt | Current (0 to 5) | Target | Evidence ref | Key gap |
|---|---|---|---|---|---|---|
| Govern | GV.OC Organizational Context | Are mission, stakeholders and legal and contractual requirements documented and used in risk decisions? | [ ] | [ ] | [ ] | [ ] |
| GV.RM Risk Management Strategy | Is there an approved risk appetite and a standard method for rating cyber risk? | [ ] | [ ] | [ ] | [ ] | |
| GV.RR Roles, Responsibilities, and Authorities | Are security roles, authority and resources defined and approved, for example in a programme charter? | [ ] | [ ] | [ ] | [ ] | |
| GV.PO Policy | Are policies approved, communicated, reviewed and enforced? | [ ] | [ ] | [ ] | [ ] | |
| GV.OV Oversight | Does leadership review security performance and adjust strategy? | [ ] | [ ] | [ ] | [ ] | |
| GV.SC Cybersecurity Supply Chain Risk Management | Are suppliers tiered, assessed and monitored according to risk? | [ ] | [ ] | [ ] | [ ] | |
| Identify | ID.AM Asset Management | Are hardware, software, cloud services, data and identities inventoried with owners? | [ ] | [ ] | [ ] | [ ] |
| ID.RA Risk Assessment | Are vulnerabilities, threats and impacts assessed and recorded in a register? | [ ] | [ ] | [ ] | [ ] | |
| ID.IM Improvement | Are improvements identified from assessments, tests, exercises and incidents and tracked? | [ ] | [ ] | [ ] | [ ] | |
| Protect | PR.AA Identity Management, Authentication, and Access Control | Are human and non-human identities managed, strongly authenticated and given least privilege? | [ ] | [ ] | [ ] | [ ] |
| PR.AT Awareness and Training | Do staff and privileged users receive role-based training with measured effect? | [ ] | [ ] | [ ] | [ ] | |
| PR.DS Data Security | Is data classified and protected at rest and in transit, with tested backups? | [ ] | [ ] | [ ] | [ ] | |
| PR.PS Platform Security | Are configurations hardened, software maintained and logs generated? | [ ] | [ ] | [ ] | [ ] | |
| PR.IR Technology Infrastructure Resilience | Are networks segmented and capacity and resilience planned? | [ ] | [ ] | [ ] | [ ] | |
| Detect | DE.CM Continuous Monitoring | Are networks, endpoints, cloud, identities and suppliers monitored for adverse events? | [ ] | [ ] | [ ] | [ ] |
| DE.AE Adverse Event Analysis | Are alerts correlated, triaged and escalated to incidents against defined criteria? | [ ] | [ ] | [ ] | [ ] | |
| Respond | RS.MA Incident Management | Is there an approved, exercised incident response plan with third parties? | [ ] | [ ] | [ ] | [ ] |
| RS.AN Incident Analysis | Are investigations, root cause and evidence preservation performed? | [ ] | [ ] | [ ] | [ ] | |
| RS.CO Incident Response Reporting and Communication | Are regulators, customers and stakeholders notified on time? | [ ] | [ ] | [ ] | [ ] | |
| RS.MI Incident Mitigation | Can incidents be contained and eradicated quickly, including credential revocation? | [ ] | [ ] | [ ] | [ ] | |
| Recover | RC.RP Incident Recovery Plan Execution | Are recovery plans tested and restoration integrity verified? | [ ] | [ ] | [ ] | [ ] |
| RC.CO Incident Recovery Communication | Is recovery progress communicated to stakeholders? | [ ] | [ ] | [ ] | [ ] |
For PR.AA, score human and non-human identities separately if their practices differ; service accounts, API keys and AI agents are often one or two levels behind workforce identity. The NHI Risk Scoring Guide helps scope that population.
6. Tier cross-check
After scoring, check the overall picture against the CSF 2.0 Tiers. CSWP 29 describes them as a progression from informal, ad hoc responses to approaches that are agile, risk-informed and continuously improving, and encourages progression to higher Tiers when risks or mandates are greater or a cost-benefit analysis supports it.
| Tier | Governance and management characteristics (CSWP 29, summarised) | Typical worksheet pattern |
|---|---|---|
| 1 Partial | Ad hoc governance; case-by-case management; limited awareness of supplier risk | Most Categories at 0 to 1 |
| 2 Risk Informed | Management approves practices but not organisation-wide policy; informal information sharing | Govern at 2, others mixed 1 to 2 |
| 3 Repeatable | Practices approved as policy and reviewed; organisation-wide approach; supplier risk formally acted on | Most Categories at 3, Govern at 3 or above |
| 4 Adaptive | Risk management part of culture; practices adapt from lessons and predictive indicators; near real-time supplier risk information | Most Categories at 4 to 5 |
If the worksheet suggests level 4 across Protect but the Tier cross-check suggests Tier 2, scores are probably inflated or Govern is lagging. Revisit evidence before reporting.
7. Results summary and priorities
| Function | Average current | Average target | Largest gap Category | Change since last assessment |
|---|---|---|---|---|
| Govern | [ ] | [ ] | [ ] | [ ] |
| Identify | [ ] | [ ] | [ ] | [ ] |
| Protect | [ ] | [ ] | [ ] | [ ] |
| Detect | [ ] | [ ] | [ ] | [ ] |
| Respond | [ ] | [ ] | [ ] | [ ] |
| Recover | [ ] | [ ] | [ ] | [ ] |
List the top five improvement priorities, each with owner, deadline and the risk scenario it reduces. Report Function averages only alongside the Category detail; an average hides a single weak Category such as RS.MA that could dominate loss. See the Board Cyber Risk Reporting Guide.
8. Sign-off and next assessment
- Calibration complete: [reviewer name, date, number of scores changed].
- Approved by: [sponsor name, date].
- Next assessment due: [date, normally 12 months], or earlier after a major incident, acquisition or reorganisation.
Implementation guidance
- Plan (weeks 1 to 2): confirm scope, scale and evidence rules with the sponsor; send respondents the worksheet and evidence list in advance.
- Collect (weeks 2 to 5): run one 60 to 90 minute workshop per Function; respondents score first, the lead challenges against the evidence rules.
- Calibrate (week 6): the reviewer samples at least [20] percent of scores at level 3 or above and adjusts where evidence is missing.
- Report (week 7): results summary, top priorities and Tier cross-check to [Security governance committee].
- Act and track: feed priorities into the roadmap and budget; link each to an Organisational Profile action where one exists.
Small organisations can complete the worksheet in two half-day sessions with an external facilitator; score at Function level first, then Category level for Govern and Protect. Large organisations should run the template per business unit with a shared calibration reviewer, then compare units rather than averaging them.
Useful measures: percentage of Categories at or above target; number of scores changed at calibration (high numbers mean the scale is unclear); evidence age; year-on-year change per Function; and priorities delivered by their deadline.
Common failure patterns: averaging all 22 Categories into one number for the board; letting respondents set their own targets; accepting level 3 or 4 without metrics; assessing only technical Functions and skipping Govern; and repeating the assessment with a changed scale so trends are meaningless.
| Template section | NIST CSF 2.0 | NIST SP 800-53 Rev. 5 |
|---|---|---|
| 1 Scope, 3 Scale, 4 Evidence | GV.RM-06 | CA-2 Control Assessments |
| 5 Worksheet | ID.IM-01 | CA-2, CA-7 Continuous Monitoring |
| 7 Results and priorities | GV.OV-03, ID.RA-06 | PM-6 Measures of Performance, PM-4 Plan of Action and Milestones Process |
| 8 Sign-off | GV.OV-01 | PM-9 Risk Management Strategy |
Standards and references
- NIST: CSWP 29, The NIST Cybersecurity Framework (CSF) 2.0
- NIST: SP 1301, CSF 2.0 Quick-Start Guide for Creating and Using Organizational Profiles
- NIST: Cybersecurity Framework 2.0
- NIST: SP 800-53 Rev. 5
This template is provided for guidance and must be adapted to your organisation. Related NHI Mgmt Group resources: GRC Maturity Model · CSF 2.0 Organisational Profiles Template · NIST Cybersecurity Framework 2.0 Guide · C2M2 Cybersecurity Capability Maturity Model Guide · Security Programme Charter Template