Checklist: building and using a NIST CSF 2.0 Organizational Profile, with the Govern Function and Tiers
Twelve steps for putting the voluntary NIST Cybersecurity Framework 2.0 to work: scoping a profile, recording current and target outcomes, starting with Govern, choosing Tiers, and turning the gaps into an action plan the executive team owns.
A framework, not a rule
NIST published version 2.0 of the Cybersecurity Framework as NIST Cybersecurity White Paper 29 on February 26, 2024 [1] [2]. It is guidance: NIST calls it a foundational resource that may be adopted voluntarily and through governmental policies and mandates, and says it describes outcomes without prescribing how to achieve them [1]. Nothing in it obliges an organization to build a profile; a law, regulator, contract or internal policy might. Its three parts are the Core (outcomes under six Functions: Govern, Identify, Protect, Detect, Respond and Recover), Organizational Profiles, and Tiers [1].
Where the steps come from
The steps follow the five-step profile process in section 3.1 of CSWP 29, with the Govern outcomes from Appendix A, the Tiers from section 3.2 and Appendix B, and the column layout from NIST’s quick-start guide on Organizational Profiles, Special Publication 1301 (February 2024) [1] [3]. Because the whole framework is voluntary, no step is a legal requirement; a step labeled as our suggestion goes beyond what NIST describes. The owner shown under each step is a typical role; NIST says the person responsible for an outcome varies by organization [1]. As checked on November 14, 2026, CSWP 29 remains the current version on NIST’s publication page [2].
Moraph’s teams help organizations with work like this. See our solutions.
The checklist
Tick the steps as you go. The ticks are kept in this browser only; nothing is sent to us.
CISO with the general counsel
CSWP 29 section 1 says the CSF may be adopted voluntarily and through governmental policies and mandates [1]. Recording which applies is our suggestion, so the profile’s audience and evidence standard are clear.
CISO
Step 1 in CSWP 29 section 3.1 is to document the facts and assumptions that define the scope, and says an organization can have as many profiles as it wants, for example one for its financial systems or for ransomware affecting them [1]. SP 1301 suggests scoping by technology, data type or users [3].
Governance, risk and compliance lead
Step 2 in CSWP 29 section 3.1 lists these as examples of the information needed [1].
Executive team, led by the chief risk officer or CISO
Appendix A of CSWP 29 lists the six Govern categories (GV.OC, GV.RM, GV.RR, GV.PO, GV.OV and GV.SC), including GV.OC-03 on legal, regulatory and contractual requirements, GV.RM-02 on risk appetite and tolerance statements, and GV.RR-01 on leadership accountability [1]. Section 2 says Govern informs how an organization will implement the other five Functions, but also that the Core’s order does not imply sequence; starting with Govern is our suggestion.
CISO with business owners
CSWP 29 section 3.1 defines the Target Profile as the desired outcomes selected and prioritized, taking account of new requirements, technology and threat trends [1]. SP 1301 steps 3d and 3e add Goals and a Priority field, and calls prioritization the defining feature of a profile [3].
CISO, agreed with the executive team
CSWP 29 section 3.2 says an organization can choose to use the Tiers, Partial (Tier 1), Risk Informed (Tier 2), Repeatable (Tier 3) and Adaptive (Tier 4), to inform its Current and Target Profiles, and that moving up is encouraged when risks or mandates are greater or a cost-benefit analysis supports it. Appendix B illustrates each Tier for governance and for risk management [1].
Governance, risk and compliance lead with the program office
Step 4 in CSWP 29 section 3.1 is to analyze the gaps and create a prioritized action plan, naming a risk register, risk detail report or POA&M as examples [1].
Chief risk officer
CSWP 29 section 5.1 describes executives setting priorities, risk appetite and resources, and practitioners reporting indicators back; section 5.2 covers integration with enterprise risk management [1]. Outcome GV.RM-03 in Appendix A is that cybersecurity risk management is included in enterprise risk management processes [1].
CISO
Step 5 in CSWP 29 section 3.1 is to implement the plan and update the profile, and NIST says the steps can be repeated as often as needed [1]. A fixed review schedule, for example yearly, is our suggestion.
Spotted an error? Tell us and we will check it and correct the checklist where needed.