CIS Controls
CIS Controls vs NIST CSF: Safeguards vs Functions
3 July 2026 · Updated 5 Sept 2026
The CIS Controls are prescriptive safeguards that say what to do; NIST CSF is an outcome based framework of six functions that says what to achieve. CIS Controls v8.1 maps directly to NIST CSF 2.0, so the two work as a pair, the CSF as the risk management structure and the CIS Controls as the task list that fills it.
Framework comparisons usually force a choice. This one should not. The CIS Controls and NIST CSF answer different questions, and the strongest programs run both.
What is the difference between the CIS Controls and NIST CSF?
The difference is prescription versus outcome. The CIS Critical Security Controls (CIS Controls) say exactly what to do: 18 controls broken into 153 named safeguards, each a concrete action. The NIST Cybersecurity Framework (CSF) says what to achieve, organising cyber risk into six functions and leaving the specific controls to the organisation.
Think of it as instructions versus objectives. NIST CSF says an organisation should be able to detect cyber security events. The CIS Controls say collect and retain audit logs, operate network monitoring, deploy malware defences. NIST CSF gives leadership a common language for cyber risk that a board and an auditor both understand. The CIS Controls give the security team a prioritised backlog. Neither replaces the other. One frames the problem, the other works it. For the CIS side in full, see what the CIS Controls are; for the NIST side, see what NIST CSF is.
How do the CIS Controls and NIST CSF compare?
The CIS Controls and NIST CSF compare across their nature, structure and intended user, and they operate at different layers of a security program.
| Dimension | CIS Controls | NIST CSF |
|---|---|---|
| Nature | Prescriptive: specific safeguards | Outcome based: desired results |
| Set by | Center for Internet Security | US National Institute of Standards and Technology |
| Structure | 18 controls, 153 safeguards, three Implementation Groups | Six functions, categories and subcategories |
| Answers | What do we actually do | What must we achieve, and how mature are we |
| Primary user | Security and IT teams | Leadership, risk and audit |
| Measurement | Safeguards implemented per Implementation Group | Profiles and tiers against desired outcomes |
| Best at | Executing a defensible baseline | Communicating and governing cyber risk |
The comparison shows why pairing them works. The CIS Controls are strong exactly where NIST CSF is deliberately vague, at the level of concrete action, and NIST CSF is strong where the CIS Controls do not reach, at the level of risk governance and executive communication.
What are the six NIST CSF 2.0 functions?
The six NIST CSF 2.0 functions are Govern, Identify, Protect, Detect, Respond and Recover. They organise every cyber security outcome the framework describes into a structure leadership can reason about.
- Govern sets the cyber risk strategy, roles and oversight
- Identify builds an understanding of assets, suppliers and risks
- Protect puts safeguards in place to secure those assets
- Detect finds cyber security events as they happen
- Respond manages and contains incidents
- Recover restores systems and services after an incident
Govern is the significant one. NIST added it as a distinct function in version 2.0, elevating governance from something implied to a first class part of the framework. This is the change CIS mirrored in v8.1, which is why the two versions align so cleanly. For the NIST framework on its own terms, what NIST CSF is covers it, and NIST CSF vs the Essential Eight puts it against the Australian mandate. For the full Essential Eight picture, the Essential Eight guide covers the maturity model in detail.
Do the CIS Controls map to NIST CSF?
Yes, and the mapping is official and current. CIS Controls v8.1 realigned its NIST CSF mappings to match NIST CSF 2.0 and added the Govern security function to its own structure to keep the two in step. Every CIS safeguard carries a NIST CSF function tag, so an organisation running the CIS Controls can show precisely which NIST outcomes each safeguard delivers.
This is what makes the pairing practical rather than theoretical. An organisation can adopt NIST CSF as the framework it reports against to its board and auditors, then implement the CIS Controls as the mechanism that produces those outcomes, and the mapping proves the link. When someone asks how the Protect function is actually achieved, the answer points to the CIS safeguards tagged to it. The v8.1 realignment means the mapping is to the current CSF, not an older revision, so the traceability holds up under scrutiny.
Should we use the CIS Controls or NIST CSF?
Most programs use both, matched to the audience. In the programs we assess, the two run as a pair, not a choice. NIST CSF is the right language for leadership, risk committees and auditors because it frames cyber security as risk outcomes across six functions rather than a list of technical tasks. It answers the board’s question, are we managing this well. The CIS Controls answer the engineer’s question, what do I build first.
Where only one can start, let the audience decide. A small business that needs to improve its actual defences quickly is better served starting with the CIS Controls at IG1, 56 concrete safeguards it can work through. An organisation that needs to demonstrate governance and communicate risk upward gets more from adopting NIST CSF as the structure, then filling it with CIS safeguards. Either way the mapping means the organisation is not locked in. Start with one, add the other, and the traceability is already built. For help placing these against Australian requirements, a virtual CISO can set the structure. If government data is in scope, an IRAP assessment covers the layer above both.
Frequently asked questions
What is the difference between the CIS Controls and NIST CSF?
The CIS Controls are prescriptive, naming the specific safeguards to implement. NIST CSF is outcome based, describing the results to achieve across six functions and leaving the how to the organisation. The CIS Controls are the actions, NIST CSF is the risk management structure around them.
Do the CIS Controls map to NIST CSF?
Yes. CIS Controls v8.1 realigned its NIST CSF mappings to match NIST CSF 2.0 and added the Govern security function. Each CIS safeguard is tagged to a NIST CSF function, so an organisation can show how its prescriptive controls satisfy the outcome based framework.
Should we use the CIS Controls or NIST CSF?
Most organisations use both. NIST CSF gives leadership a risk management structure across Govern, Identify, Protect, Detect, Respond and Recover. The CIS Controls give the technical team a prioritised task list that delivers those outcomes. They complement rather than compete. The CIS Implementation Groups let an organisation scale that task list to its size, and CIS Controls vs the Essential Eight shows how both fit the Australian context.
Is NIST CSF or the CIS Controls better for a small business?
The CIS Controls are usually the easier start for a small business because IG1 gives 56 concrete actions to work through. NIST CSF is stronger when an organisation needs to communicate cyber risk to a board or align with a wider risk program.
What are the six NIST CSF 2.0 functions?
The six NIST CSF 2.0 functions are Govern, Identify, Protect, Detect, Respond and Recover. Govern was added as a distinct function in version 2.0 to reflect that cyber risk is a governance responsibility, and CIS Controls v8.1 mirrored this by adding its own Govern function.
Written by Gaurav Vikash, an ASD endorsed IRAP assessor and senior cyber security leader with 18 years of experience across Australia, the UK and Asia, including CISO and senior security leadership roles. He holds CISSP, CISA, CISM and CRISC and is an ISO 27001 Lead Auditor and ISO 42001 Lead Implementer, and speaks regularly at industry conferences.
Sources:
- CIS Critical Security Controls Version 8.1, Center for Internet Security, accessed 3 July 2026
- The 18 CIS Critical Security Controls, Center for Internet Security, accessed 3 July 2026
- The NIST Cybersecurity Framework (CSF) 2.0, National Institute of Standards and Technology, 26 February 2024
- CIS Critical Security Controls Implementation Groups, Center for Internet Security, accessed 3 July 2026
Last updated: 5 September, 2026
