Many NIST CSF 2.0 assessments end as a colour-coded heat map with no agreed target, no owners and no plan, because the Organisational Profile that should drive decisions was never properly built. CSF 2.0 (NIST CSWP 29) makes Organizational Profiles one of its three parts, and NIST SP 1301, the Quick-Start Guide for Creating and Using Organizational Profiles (final, 26 February 2024), sets out five steps: scope the Profile, gather information, create it, analyse gaps and create an action plan, then implement and update. This template turns those steps into a document you can complete: scope statement, roles, rating scale, a Current and Target worksheet with worked example rows, gap register and action plan. It complements NIST's own CSF 2.0 Organizational Profile Template spreadsheet rather than replacing it. It is written for GRC leads, CISOs and security architects running a first or refreshed Profile. For the framework itself see the NIST Cybersecurity Framework 2.0 Guide.
How to use this template
- Replace text in square brackets, such as [Organisation], [Profile owner] and [Business unit], with your own values.
- Download the current CSF 2.0 Organizational Profile Template spreadsheet from NIST and use this document as the cover, method and approval record; the worksheet in section 5 matches the spreadsheet's columns (identifier, description, Current practices, status and rating, Target priority and goals) so the two can be kept in step.
- SP 1301 allows columns to be added or removed and does not require Current and Target sections to have matching columns. Add an evidence reference column; auditors will ask for it.
- If a Community Profile fits your sector or threat, SP 1301 allows it to be copied in as the basis of the Target Profile and then adjusted. See the NIST CSF 2.0 Community Profiles Guide.
- An organisation can hold several Profiles with different scopes. Complete one copy of this template per Profile.
1. Profile identification and scope
| Field | Entry |
|---|---|
| Profile name and ID | [CSF-PROFILE-01: Group corporate IT] |
| Version and date | [v1.0, DD Month YYYY] |
| Reason for the Profile | [Annual programme baseline / regulatory alignment / post-acquisition integration / board request] |
| In scope | [Divisions, data types, technology, products, partners and suppliers covered] |
| Out of scope | [Excluded units or systems, with the Profile that covers them, if any] |
| Threat types addressed | [For example ransomware, business email compromise, insider misuse, supplier compromise] |
| Key assumptions | [For example shared identity platform managed by group IT] |
| Community Profile used as baseline | [Name and version, or "none"] |
| Profile owner | [Name, role] |
Scope is defined by the facts and assumptions agreed here. Any later change to scope requires a new version of the Profile.
2. Roles and responsibilities
| Role | Responsibility | Named person |
|---|---|---|
| Executive sponsor | Approves Target Profile priorities and the action plan; accepts residual gaps | [Name] |
| Profile owner | Runs the process, maintains the worksheet and reports progress | [CISO or GRC lead] |
| Function leads | Provide Current Profile evidence and propose Target goals for Govern, Identify, Protect, Detect, Respond and Recover | [One name per Function] |
| Risk management | Confirms target priorities against risk appetite and the risk register | [CRO or delegate] |
| Legal and compliance | Lists legal, regulatory and contractual requirements that drive targets | [Name] |
| Independent reviewer | Samples evidence and challenges ratings before approval | [Internal audit or second line] |
Record these assignments as evidence for GV.RR-02 (roles, responsibilities and authorities are established, communicated, understood and enforced). A Security RACI Matrix Template can carry the detail.
3. Information inputs
Gather and list the inputs used, with their version, before any rating starts. SP 1301 names organisational policies, risk management priorities, resources, and cybersecurity requirements and standards; target priorities are driven by strategic objectives, laws, regulations and risk responses.
- Mission and objectives: [strategy document, critical services list] (GV.OC-01).
- Legal, regulatory and contractual requirements: [for example NIS2, DORA, PCI DSS, customer contract clauses] (GV.OC-03).
- Risk appetite and tolerance: [approved statement and date] (GV.RM-02). See the Cyber Risk Appetite Statement Template.
- Risk register and top scenarios: [register extract]. See the Cyber Risk Scenario Library Guide.
- Existing assessments: [audit findings, ISO/IEC 27001 Statement of Applicability, penetration test results].
- Threat intelligence: [sector reports, internal incident history].
- Informative References chosen: [for example SP 800-53 Rev. 5, ISO/IEC 27001:2022, CIS Controls v8.1].
4. Rating and priority scales
SP 1301 lets organisations choose the scale (high, medium and low; 1 to 5; percentages; or red, amber and green). Pick one, define it and apply it consistently across every Profile so results can be compared.
| Current rating | Definition | Minimum evidence |
|---|---|---|
| 0 Not achieved | Outcome not addressed | Statement of absence |
| 1 Partially achieved | Ad hoc or covers part of scope | Examples of practice |
| 2 Largely achieved | Documented and mostly applied across scope | Approved procedure plus sample records |
| 3 Fully achieved | Documented, applied across scope and checked | Procedure, records and a test or review result under 12 months old |
| Target priority | Meaning |
|---|---|
| High | Required by law, contract or a top risk scenario; gap must be closed within [12] months |
| Medium | Supports top risks or significant improvement; plan within [24] months |
| Low | Desirable; maintain or improve opportunistically |
| Not applicable | Outcome excluded with documented rationale |
5. Profile worksheet
Complete one row per in-scope Subcategory (or your own outcome, which SP 1301 permits). The example rows show the level of detail expected; replace them with your own content.
| Outcome | Current practices | Current rating | Target priority | Target goals | Evidence ref |
|---|---|---|---|---|---|
| GV.RM-02 Risk appetite and tolerance statements established, communicated and maintained | [Draft statement, not board approved] | [1] | [High] | [Board-approved statement with quantitative tolerances, reviewed annually] | [EV-001] |
| GV.SC-07 Supplier and third-party risks understood, recorded, prioritised, assessed and monitored | [Questionnaire at onboarding only] | [1] | [High] | [Tiered suppliers with reassessment by tier and contract security clauses] | [EV-002] |
| ID.AM-02 Inventories of software, services and systems maintained | [CMDB covers on-premises servers; SaaS not included] | [1] | [High] | [Single inventory covering SaaS and cloud services with owners] | [EV-003] |
| ID.RA-01 Vulnerabilities identified, validated and recorded | [Weekly authenticated scanning of servers] | [2] | [Medium] | [Extend to cloud workloads and containers] | [EV-004] |
| PR.AA-01 Identities and credentials for users, services and hardware managed | [Joiner and leaver process for staff; service accounts unmanaged] | [1] | [High] | [Every service account, API key and workload identity has an owner and rotation schedule] | [EV-005] |
| PR.AA-05 Access permissions defined, managed, enforced and reviewed with least privilege | [Annual review of finance systems] | [2] | [High] | [Quarterly review for privileged and machine access] | [EV-006] |
| PR.DS-11 Backups created, protected, maintained and tested | [Nightly backups; restore test not recorded] | [2] | [High] | [Immutable copies and quarterly documented restore tests] | [EV-007] |
| DE.CM-09 Hardware, software, runtime environments and data monitored | [EDR on 85 percent of endpoints] | [2] | [High] | [EDR coverage above 98 percent with health alerting] | [EV-008] |
| RS.MA-01 Incident response plan executed with third parties once declared | [Plan exists, not exercised with suppliers] | [1] | [Medium] | [Annual exercise including key suppliers and insurer] | [EV-009] |
| RC.RP-01 Recovery portion of the plan executed once initiated | [Recovery steps embedded in IT runbooks] | [1] | [Medium] | [Tested recovery plan for top five services] | [EV-010] |
PR.AA-01 and PR.AA-03 explicitly cover services and hardware as well as users, so service accounts, API keys, certificates and AI agents belong in the Profile. See the Identity Security Programme Guide.
6. Gap analysis
Compare current practices (people, process and technology) against the Target goals for each row, using the outcome descriptions, Informative References and Implementation Examples, as SP 1301 step 4a describes. Record each difference as a candidate improvement.
| Gap ID | Outcome | Gap description | Risk if not closed | Linked scenario or requirement |
|---|---|---|---|---|
| [G-01] | [PR.AA-01] | [No owner or rotation for 600 service accounts] | [Credential abuse leading to data exposure] | [Risk scenario NHI-01; contract clause X] |
| [G-02] | [PR.DS-11] | [Restore capability unproven] | [Extended outage after ransomware] | [Scenario RAN-01] |
7. Action plan
SP 1301 step 4b asks that each action has an action, priority, owner, deadline and resources. Use Plans of Action and Milestones (POA&Ms) for longer remediation timelines.
| Action ID | Action | Closes gap | Priority | Owner | Deadline | Resources | Status |
|---|---|---|---|---|---|---|---|
| [A-01] | [Discover and assign owners to all service accounts] | [G-01] | [High] | [IAM lead] | [Q2] | [2 FTE months] | [Not started] |
| [A-02] | [Quarterly restore test for top five services] | [G-02] | [High] | [Infrastructure lead] | [Q1] | [Test environment] | [In progress] |
Track each action with KPIs, key risk indicators and risk assessments, as step 5a describes. See the Key Risk Indicators for Cyber Risk Guide.
8. Review, approval and update
- Approval: the executive sponsor approves the Target Profile and action plan. Residual gaps not funded are recorded as accepted risks with an expiry date.
- Update triggers: update the Profile when risks, likelihoods or impacts change (step 5b), and in any case [annually], after a significant incident, an acquisition, new regulation or a major architecture change.
- Reporting: report Target attainment and action plan progress to [Security governance committee] [quarterly]. See the Security Governance Committee Charter Template.
- Version control: keep every approved version; do not overwrite past ratings.
| Version | Date | Approved by | Summary of change |
|---|---|---|---|
| [1.0] | [Date] | [Name, role] | [Initial Profile] |
Implementation guidance
- Pilot one scope first. Run the template on a single business unit or critical service over four to eight weeks and test whether the rating scale produces consistent results between assessors before scaling.
- Set targets before rating. Agree Target priorities from requirements and risk first, so assessors are not tempted to set targets that match today's state.
- Demand evidence for ratings of 2 and 3. Ratings without evidence references are the main reason Profiles fail audit challenge.
- Trace to controls. NIST recommends the CSF 2.0 Reference Tool to trace Target Subcategories to SP 800-53 controls; use the same mapping to your ISO/IEC 27001 Statement of Applicability if you hold certification.
- Size to the organisation. A small organisation can complete one Profile in the NIST spreadsheet in a few workshops. A large group should run Profiles per business unit or critical service and roll up only Target attainment, not raw ratings.
- Measure. Report: percentage of in-scope outcomes at or above target; number of High priority gaps open past deadline; percentage of ratings with current evidence; Profiles reviewed in the last 12 months; and actions completed against plan.
Common mistakes to avoid: rating the whole Core when a third of it is out of scope, treating Tiers as a score to maximise, copying a Community Profile without adjusting priorities, and leaving machine identities outside PR.AA because no team owns them.
| Template section | NIST CSF 2.0 | NIST SP 800-53 Rev. 5 | SP 1301 step |
|---|---|---|---|
| 1 Scope | GV.OC-01 | PM-11 Mission and Business Process Definition | 1 |
| 2 Roles | GV.RR-02 | PM-2 Information Security Program Leadership Role | 1 |
| 3 Inputs | GV.OC-03, GV.RM-02 | PM-9 Risk Management Strategy | 2 |
| 5 Worksheet, 6 Gaps | ID.IM-01 | CA-2 Control Assessments | 3, 4a |
| 7 Action plan | ID.RA-06 | PM-4 Plan of Action and Milestones Process, CA-5 | 4b, 5a |
| 8 Review | GV.OV-01 | PM-6 Measures of Performance | 5b |
Standards and references
- NIST: SP 1301, CSF 2.0 Quick-Start Guide for Creating and Using Organizational Profiles
- NIST: CSF 2.0 Profiles and Organizational Profile Template
- NIST: Cybersecurity Framework 2.0
- NIST: SP 800-53 Rev. 5
- NIST: IR 8286 Rev. 1, Integrating Cybersecurity and Enterprise Risk Management
This template is provided for guidance and must be adapted to your organisation. Related NHI Mgmt Group resources: NIST Cybersecurity Framework 2.0 Guide · NIST CSF 2.0 Community Profiles Guide · NIST CSF 2.0 Govern Function Guide · Security Programme Maturity Assessment Template