Most organisations cite the NICE Framework in job adverts and training plans, but few use it the way it is built: as a structured, versioned set of tasks, knowledge and skills that can be assessed. The NICE Framework (NIST SP 800-181 Rev. 1, the Workforce Framework for Cybersecurity) is the US reference for describing cybersecurity work, and its components are revised separately from the publication, several times since 2024. Figures quoted online, such as "52 work roles in 7 categories", describe an older components release and are now out of date. This guide explains the current structure, what changed between versions, how to use it for role design, hiring, training and team planning, and where identity and non-human identity work fits. It is for security leaders, workforce and HR partners, training designers and practitioners planning their own development.
Key takeaways
- The publication and the components are separate. SP 800-181 Rev. 1 (November 2020) defines the model; the work roles, competency areas and TKS statements are versioned components, currently v2.2.0 (April 2026).
- Five work role categories remain. Version 2.0.0 (March 2025) removed Cyberspace Effects and Cyberspace Intelligence, which now sit in the DoD Cyber Workforce Framework.
- Work roles are not job titles. A role is a grouping of tasks; one job may combine several roles, and one role may be spread across several jobs.
- TKS statements are the working unit. Tasks, Knowledge and Skill statements, over 2,000 of them, are what you assess, train and write into job descriptions.
- Identity work needs tailoring. Machine identity, secrets and AI agent governance are spread across existing roles, so organisations should build their own competencies from TKS statements.
What it is and who it applies to
The NICE Framework is published by the National Initiative for Cybersecurity Education (NICE), led by NIST. It is voluntary guidance and gives a common language for describing cybersecurity work and the people who do it. SP 800-181 Rev. 1 names three audiences: employers (describing work, hiring, developing and retaining staff), education and training providers (designing learning that matches employer needs), and learners (exploring cybersecurity work and showing what they can do).
US federal agencies use NICE work roles when coding cybersecurity positions; the change log, for example, records the Systems Developer role (OPM code 632) being deprecated in components v1.0.0. Outside government, it is widely used as a vocabulary for job architecture and training catalogues, and it is the US counterpart of the European Cybersecurity Skills Framework: see the ENISA ECSF Skills Framework Guide. For career routes using these frameworks, see the Cybersecurity Careers Guide.
SP 800-181 Rev. 1 sets four principles: agility (adapting to change), flexibility (fitting each organisation's context), interoperability (consistent terms so workforce information can be exchanged) and modularity (extending the approach to other workforces such as privacy or software development).
Structure and key requirements
Building blocks
| Element | Definition (SP 800-181 Rev. 1, paraphrased) | How you use it |
|---|---|---|
| Task statement | An activity directed towards organisational objectives | Describe the work in a position, write objectives, build task lists |
| Knowledge statement | A retrievable set of concepts held in memory | Define course content and knowledge tests |
| Skill statement | The capacity to perform an observable action | Design practical assessments and labs |
| Competency (Competency Area) | A mechanism for organisations to assess learners, with a name, description, assessment method and associated TKS | Cross-cutting capability such as AI security or cyber resiliency, used for hiring, credentialing or training |
| Work Role | A grouping of work for which someone is responsible or accountable, made up of tasks | Job architecture, position coding, career pathways |
| Team | Built top-down from work roles or bottom-up from competencies | Team design and gap analysis |
Rev. 1 deprecated the older Categories such as "Securely Provision" and the Specialty Areas, and merged the former Ability statements into Skill statements. Organisations still using the original 2017 work roles may continue to do so, but the mapping effort grows with each components release.
Components versions
| Components version | Released | Main changes (NIST change log) |
|---|---|---|
| 2017 components | November 2020 | First release as a separate spreadsheet alongside SP 800-181 Rev. 1 |
| 1.0.0 | 5 March 2024 | First major revision: names, descriptions and codes updated; TKS statements largely revised with new IDs; Insider Threat Analysis added; Systems Developer deprecated; competency areas confirmed |
| 2.0.0 | 5 March 2025 | Cyberspace Effects and Cyberspace Intelligence categories and roles removed (now in DoD DCWF); Operational Technology (OT) Cybersecurity Engineering added (DD-WRL-009); Digital Evidence Analysis and Insider Threat Analysis updated; Cyber Resiliency competency updated |
| 2.1.0 | 3 December 2025 | Cybercrime Investigation (IN-WRL-001) comprehensively revised; Artificial Intelligence (AI) Security competency area (NF-COM-002) updated |
| 2.2.0 (current) | 28 April 2026 | Cybersecurity Supply Chain Risk Management (C-SCRM) work role added (OG-WRL-017); Cryptography (NF-COM-006) and DevSecOps (NF-COM-008) competency areas updated |
NIST's revision policy allows major releases no more than once a year and minor releases no more than twice a year, with public comment for both, so plan for an annual review of any internal mapping. The March 2025 components poster gives 11 competency areas and 2,111 TKS statements (942 tasks, 631 knowledge, 538 skills) for v2.0.0; counts move slightly with each release. The components are published in NIST's Cybersecurity and Privacy Reference Tool, as XLSX and JSON downloads, through NICE Framework Online on CISA's NICCS site, and in the Credential Transparency Description Language. Note that third-party summaries, and at the time of checking the NICCS overview page itself, may still describe v1.0.0 (7 categories, 52 roles).
Work role categories
| Category | Example work roles |
|---|---|
| Oversight and Governance (OG) | Executive Cybersecurity Leadership, Cybersecurity Policy and Planning, Cybersecurity Workforce Management, Security Control Assessment, Systems Authorization, Privacy Compliance, Technology Program Auditing, Cybersecurity Supply Chain Risk Management |
| Design and Development (DD) | Operational Technology (OT) Cybersecurity Engineering, among others |
| Implementation and Operation | Roles that run and administer systems and networks |
| Protection and Defense (PD) | Insider Threat Analysis, among others |
| Investigation (IN) | Cybercrime Investigation, Digital Evidence Analysis |
Download the current components for the full list with IDs rather than relying on any copy, including this table.
Identity and NHI requirements
The NICE Framework is not a control framework, so it imposes no identity requirements. The practical question is whether the roles you staff actually cover identity work, which today includes service accounts, API keys, certificates, workload identities and AI agents as well as human access.
- Find the TKS, not a role: identity tasks are distributed across implementation, protection and governance roles. Search the TKS statements for authentication, access control, credentials, certificates and cryptography, and assemble an organisation-specific competency from them, which SP 800-181 Rev. 1 explicitly allows.
- Use the new competency areas: the AI Security (NF-COM-002), Cryptography (NF-COM-006) and DevSecOps (NF-COM-008) competency areas, all updated in 2025 and 2026, are the closest fit for agent, PKI and pipeline secrets work.
- Assign ownership tasks to roles: NHI ownership, attestation and decommissioning should appear as tasks in a named role description, not as an assumption. See the Identity Team Operating Model and Workforce Planning Guide.
- Supply chain identity: the C-SCRM work role added in v2.2.0 is the natural home for third-party token and integration oversight.
- Career mapping: for individual paths, see the IAM Engineer Career Guide.
Implementation steps
- Pick and pin a version: download the current components (v2.2.0 at the time of writing) as JSON or XLSX and record the version in every artefact you build.
- Inventory the work: list what your security function actually does, using task statements, before looking at titles.
- Map positions to roles: map each position to one primary work role and any secondary roles; expect many positions to span two or three.
- Add organisation-specific tasks: where work is missing (for example NHI attestation or agent permission reviews), write tasks following NIST's TKS authoring conventions and tag them as local.
- Set proficiency: NIST's proficiency guidance (January 2026) uses the seven SFIA levels of responsibility; choose a level per position.
- Use it in hiring: write adverts and interview questions from tasks and skills rather than certificate lists. See the Cybersecurity Skills Gap and Hiring Guide.
- Align training: tag courses and labs to knowledge and skill statements so you can see coverage per role.
- Run a gap analysis: compare required TKS per role with what staff can show, and decide between upskilling, hiring or third-party support, as NIST's CSF 2.0 workforce quick-start guide (SP 1308) suggests.
- Review on release: when NIST issues a new components version, diff the JSON against your pinned version and update the mappings that changed.
Worked example: an identity security engineer position
The following is an illustration of the method, not a NIST mapping. An organisation creating an identity security engineer position would start by listing the work: operating the identity provider, running access reviews, managing service account and API key lifecycles, operating the internal certificate authority and reviewing permissions granted to AI agents.
- Primary role: choose the Implementation and Operation role whose tasks best match day-to-day administration of identity and access systems, after reading its task list in the current components.
- Secondary roles: add a Protection and Defense role if the position investigates suspicious authentication, and an Oversight and Governance role such as Security Control Assessment if it evidences controls for audit.
- Competency areas: attach Cryptography for PKI work and AI Security for agent permissions, then pick the specific skill statements to assess.
- Local tasks: write two or three organisation-specific tasks, for example "Attest ownership of non-human identities quarterly" and "Revoke credentials granted to a supplier at contract exit", in the same imperative style as NIST tasks.
- Assessment: use the skill statements to design a practical exercise for interview and for the annual review, so the same definition drives hiring and development.
Building a team works the same way at a larger scale. SP 800-181 Rev. 1 describes two directions: top-down, starting from the work roles a mission needs, and bottom-up, starting from the competencies the team must hold. Most security functions use both, top-down for headcount planning and bottom-up for cross-cutting areas such as AI security that no single role owns.
Small versus large organisations: a team of five should not map 2,000 statements. Pick the four to six work roles that matter, use their task lists to write job descriptions and development plans, and stop there. Large employers and federal agencies benefit from loading the components into an HR or learning system, coding positions and reporting coverage by role and competency.
Evidence and assessment
There is no NICE certification of organisations or people. Evidence is internal, and it is worth keeping because auditors and regulators increasingly ask how security staffing matches risk (CSF 2.0 GV.RR-03 and GV.RR-04 are examples).
| Use | Evidence to keep | Measure |
|---|---|---|
| Position coding | Position to work role map with components version | Percentage of security positions mapped to a current role |
| Hiring | Job descriptions citing tasks and skills | Percentage of security adverts built from TKS statements |
| Training | Course to TKS tagging | Coverage of required skills per role by available training |
| Proficiency | Assessed level per person and role | Gap between required and assessed proficiency |
| Critical capability | Named people per critical role | Roles with single-person dependency |
| Currency | Change log review record | Months since mappings were checked against the current release |
Mapping to other frameworks
| Framework | Relationship to NICE |
|---|---|
| NIST CSF 2.0 | NIST publishes a NICE to CSF 2.0 crosswalk; GV.RR-04 puts cybersecurity into HR practices and SP 1308 uses NICE as the common language |
| ENISA ECSF | European counterpart built around role profiles; see the ECSF guide for its 12 profiles |
| DoD Cyber Workforce Framework (DCWF) | Holds the cyberspace effects and intelligence roles removed from NICE in v2.0.0 |
| SFIA | NIST's proficiency guidance uses SFIA's seven levels of responsibility |
| NIST SP 800-53 Rev 5 | PM-13 Security and Privacy Workforce and AT-3 Role-based Training are where NICE-based role definitions become control evidence |
| ISO/IEC 27001:2022 | Clause 7.2 Competence asks for determined and evidenced competence; NICE roles and TKS can supply the definitions |
See the NIST CSF 2.0 Govern Function Guide for GV.RR.
Common pitfalls
- Quoting stale numbers: "52 work roles in 7 categories" is the v1.0.0 picture; two categories have since moved to the DCWF and new roles have been added.
- Treating roles as job titles: one-to-one mapping produces unrealistic job descriptions with a hundred tasks, or leaves work unassigned.
- Unpinned versions: mappings built on old TKS IDs silently break, since v1.0.0 assigned new IDs to revised statements.
- Using it only for hiring: the value is in development and gap analysis; adverts alone do not change capability.
- No local tasks: emerging work such as AI agent governance or NHI lifecycle management is left out because no role names it.
- Over-engineering in small teams: mapping every statement wastes months; select roles that matter.
Practitioner checklist
- Download the current NICE Framework components and record the version (v2.2.0 as of October 2026).
- Map every security position to primary and secondary work roles.
- Add local task statements for NHI, secrets and AI agent work, tagged as organisation-specific.
- Set a required proficiency level per position using the SFIA-based guidance.
- Write job descriptions and interview plans from tasks and skills.
- Tag training content to knowledge and skill statements and report coverage.
- Identify single-person dependencies in critical roles.
- Review mappings against the NIST change log at each new components release.
Standards and references
- NIST: SP 800-181 Rev. 1 Workforce Framework for Cybersecurity (NICE Framework)
- NIST: NICE Framework Current Versions
- NIST: NICE Framework Components Change Logs
- NIST: NICE Framework Revisions
- NIST: Work Roles and Levels of Responsibility
- CISA NICCS: NICE Framework
- NIST: SP 1308 CSF 2.0 Cybersecurity, ERM and Workforce Management Quick-Start Guide
Related NHI Mgmt Group resources: Cybersecurity Careers Guide · ENISA ECSF Skills Framework Guide · Identity Team Operating Model and Workforce Planning Guide · Cybersecurity Skills Gap and Hiring Guide