Checklist: mapping cybersecurity jobs, skills and training to the NICE Framework
Twelve steps for putting NIST’s voluntary Workforce Framework for Cybersecurity (SP 800-181 Rev. 1) to work: pinning the component version, mapping jobs to Work Roles, checking the 2025 and 2026 changes, assessing competencies and tying it all to CSF 2.0.
A shared vocabulary for cybersecurity work
The Workforce Framework for Cybersecurity, known as the NICE Framework, is NIST Special Publication 800-181 Revision 1, published in November 2020 [1]. NIST calls it a fundamental reference for describing and sharing information about cybersecurity work, expressed as Task statements with supporting Knowledge and Skill statements [1]. NIST says it is used by employers, educators and providers across sectors for career discovery, hiring, job descriptions, training and workforce planning [5]. It is guidance: nothing in it obliges a bank, health system or agency to adopt it, although a policy or contract might.
The publication describes the structure; the content, Work Role Categories, Work Roles, Competency Areas and Task, Knowledge and Skill statements, is published separately as versioned components [2]. As checked on November 14, 2026, NIST’s current versions page lists components version 2.2.0 and dates it April 28, 2025, while NIST’s change log dates the same release April 28, 2026, and lists version 2.1.0 as December 3, 2025 [2] [3]. The two NIST pages give different years for the same release, and the change log describes 2.2.0 as a revision to 2.1.0. We report both dates.
How to read the steps
Because the framework is voluntary, no step is a legal requirement. NIST guidance marks a step that SP 800-181 Rev. 1, NIST’s NICE pages or the Cybersecurity Framework 2.0 describes; Our suggestion marks a step that goes beyond them. The owner shown is a typical role, not one NIST assigns. Any rule that requires a particular employer to use the framework is outside this checklist; how any of it applies to a given organization is a question for its own counsel and human resources staff. This page is not legal advice.
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 head of human resources
Our suggestion. NIST lists these uses, from job descriptions and candidate assessment to tracking workforce capabilities and role-based training [5], and describes the framework as a reference source organizations can build on [1]. Recording the purpose sets how much detail the rest of the work needs.
Security workforce lead
NIST guidance. Components are versioned separately from SP 800-181 Rev. 1 and come as a spreadsheet, a JSON document and a browsable online version [2]. NIST says a change log and unique version identifiers maintain version control as components change, and that earlier versions stay available for use [6]. Recording the version number in each document is our suggestion.
Security workforce lead with team managers
NIST guidance on the building blocks: Task statements describe the work, Tasks include associated Knowledge and Skill statements, and Work Role names are not synonymous with job titles [1]. Listing the work as Tasks before looking at job titles is our suggestion.
Security workforce lead
NIST guidance. Work Role names are not synonymous with job titles or occupations; one Work Role, such as Software Developer, can apply to many titles, and several roles can be combined into one job [1].
Security workforce lead
NIST guidance. Version 2.0.0 (March 5, 2025) removed the Cyberspace Effects and Cyberspace Intelligence categories, which NIST says can now be found in the DoD Cyber Workforce Framework, and added the OT Cybersecurity Engineering role (DD-WRL-009); 2.1.0 updated the AI Security competency area (NF-COM-002); 2.2.0 added the C-SCRM role (OG-WRL-017) [3].
Security workforce lead
NIST guidance. The publication cautions users against modifying existing statements, Work Role names and descriptions, or Competency titles, because changes cause misalignment with outside sources, and says users can create new statements, roles and competencies instead [1].
Security workforce lead with human resources
NIST guidance for competencies: they are defined through an employer-driven approach, learner-focused, and observable and measurable, and the publication gives a lab-based demonstration as an example assessment method [1]. The framework does not define proficiency levels such as basic or advanced and leaves them to other models [1], so setting them is our suggestion.
CISO
NIST guidance. The publication says teams can be built with Work Roles, a top-down approach that starts with the work to be done, or with Competencies, a bottom-up approach [1]. Recording vacant roles as gaps is our suggestion.
CISO with the head of human resources
NIST guidance. CSF 2.0 outcomes GV.RR-02 (roles, responsibilities and authorities are established, communicated, understood and enforced) and GV.RR-04 (cybersecurity is included in human resources practices) cover this [4]. NIST publishes a mapping of NICE components v2.0.0 to CSF 2.0 [2].
Hiring managers with human resources
NIST guidance. Creating job descriptions and assessing candidate skills are among the uses NIST lists [5]. Using the statements’ identifiers in the description so later version changes can be traced is our suggestion.
Security workforce lead
NIST guidance. CSF 2.0 outcome PR.AT-02 is that individuals in specialized roles get awareness and training so they have the knowledge and skills to perform relevant tasks with cybersecurity risks in mind [4], and NIST lists role-based training and career planning among the framework’s uses [5].
Security workforce lead
NIST guidance. NIST says major and minor updates are shared for public comment before they are final, and that stakeholders can send a change request at any time, and that a request is not guaranteed to become a candidate for comment [6]. A yearly re-check of the mapping is our suggestion.
Spotted an error? Tell us and we will check it and correct the checklist where needed.