The core difference
ISO/IEC 27001:2022 tells you what a management system must do. It has requirements written as “shall” statements in clauses 4 to 10, a set of 93 reference controls in Annex A, and an external audit by an accredited certification body that ends in a certificate. You either conform or you have nonconformities to fix.
The NIST Cybersecurity Framework (CSF) 2.0, published by the US National Institute of Standards and Technology on 26 February 2024, describes outcomes. NIST states plainly that the CSF does not prescribe how those outcomes are achieved. It gives you a shared vocabulary for where your security is today, where it needs to be and what to do first. Nobody audits you against it for a certificate, because there is no certificate to issue.
That single difference drives almost every practical decision. If someone needs to rely on your security without taking your word for it, they want a certificate or an attestation. If someone wants to understand your security posture and the plan to improve it, the CSF is often the clearer language.
Side by side
| ISO/IEC 27001:2022 | NIST CSF 2.0 | |
|---|---|---|
| What it is | International requirements standard for an information security management system (ISMS) | Voluntary US framework of cybersecurity outcomes |
| Published by | ISO and IEC | NIST, a US government agency |
| Current version | 2022, with Amendment 1:2024 (climate change considerations in 4.1 and 4.2) | 2.0, released 26 February 2024 |
| Structure | Clauses 4 to 10 (mandatory) plus 93 Annex A controls in four themes | Core of 6 functions, 22 categories and 106 subcategories, plus Profiles and Tiers |
| Certification | Yes, by an accredited certification body, three-year cycle with annual surveillance | No certification scheme; self-assessment or independent assessment only |
| Output | Certificate and Statement of Applicability | Current and target profiles, gap analysis and action plan |
| Risk approach | Required risk assessment and treatment process (6.1.2, 6.1.3) | Expects risk management (Govern function); doesn’t set a method |
| Who asks for it | Tenders, enterprise procurement, Australian and Asia-Pacific buyers, UK and Europe | US stakeholders, boards, insurers, investors; one option under Australian critical infrastructure rules |
What NIST CSF 2.0 contains
The CSF has three parts. The Core is the list of outcomes, grouped into six functions: Govern, Identify, Protect, Detect, Respond and Recover. Version 2.0 added Govern, which covers organisational context, risk management strategy, roles and responsibilities, policy, oversight and cybersecurity supply chain risk management. It also widened the framework’s stated audience from critical infrastructure to organisations of any size or sector.
Organisational Profiles describe your current or target posture against those outcomes. You can scope a profile to the whole organisation or to one system or threat, and NIST also publishes Community Profiles that a sector can use as a starting target. Tiers describe how rigorous your risk governance and management are, from Tier 1 (Partial) through Risk Informed and Repeatable to Tier 4 (Adaptive). Tiers are not maturity levels you must climb; NIST says to move up when risk or obligations justify it.
Our NIST CSF assessment page covers the functions and the assessment itself. The point for this comparison is that every part of the CSF is descriptive. It tells you what good outcomes look like and leaves the method, the evidence and the verification to you.
How they map: NIST’s informative references
NIST publishes informative references: mappings between CSF outcomes and other standards, frameworks and regulations. They sit in NIST’s Online Informative References (OLIR) catalogue and can be browsed through the CSF 2.0 Reference Tool. The catalogue includes a mapping between ISO/IEC 27001:2022 and CSF 2.0, so you don’t need to build the crosswalk from scratch. NIST notes that it does not test the correctness of mappings submitted by other organisations, so treat any mapping as a starting point and apply your own judgement.
Broadly, the two line up like this:
| CSF 2.0 function | Where ISO 27001 addresses it |
|---|---|
| Govern | Clause 4 (context, interested parties, scope), clause 5 (leadership, policy, roles), clause 6 (risk process, objectives), clause 9 (monitoring, internal audit, management review); Annex A controls 5.1 to 5.4 and supplier controls 5.19 to 5.23 |
| Identify | Risk assessment (clauses 6.1.2 and 8.2), asset inventory (5.9), classification (5.12), threat intelligence (5.7), vulnerability management (8.8), continual improvement (10.1) |
| Protect | Access control and identity (5.15 to 5.18, 8.2 to 8.5), awareness training (6.3), data protection (8.10 to 8.12, 8.24), configuration and secure development (8.9, 8.25 to 8.29), backups (8.13) |
| Detect | Logging (8.15), monitoring activities (8.16), event reporting and assessment (6.8, 5.25) |
| Respond | Incident management planning, response and learning (5.24 to 5.28) |
| Recover | Security during disruption and ICT readiness for business continuity (5.29, 5.30), backups (8.13) |
Two differences matter more than the mapping. First, ISO 27001 requires the management system around the controls: internal audit, management review, corrective action and a documented Statement of Applicability. The CSF expects oversight but doesn’t require that machinery. Second, the CSF has nothing like a certificate, while ISO 27001 has nothing like Tiers or profiles. An ISO 27001 auditor says whether you conform; a CSF profile says how far along you are. See Annex A controls explained and ISO 27001 clauses 4 to 10 for the detail on the ISO side.
Which buyers ask for which
Australian and Asia-Pacific buyers
Government and enterprise procurement in Australia names ISO 27001 far more often than the CSF, because it can be verified: a buyer can check your certificate and the accreditation of the body that issued it. See ISO 27001 for government tenders. Asian and European buyers lean the same way.
US customers and investors
US enterprises tend to use NIST CSF as the language of their security questionnaires and board reporting, then ask for a SOC 2 report or ISO 27001 certificate as the evidence. A CSF profile helps you answer their questions in their terms; it rarely replaces the report or certificate. Our ISO 27001 vs SOC 2 guide covers that choice. If you are selling to the US federal government or defence supply chain, the requirements are different again (for example NIST SP 800-171 and CMMC), and neither the CSF nor ISO 27001 satisfies them on its own.
Boards, insurers and critical infrastructure
Directors and cyber insurers like the CSF because its six functions make a clear one-page picture of risk. In Australia, the critical infrastructure risk management program rules list NIST CSF 2.0 as one of the frameworks a responsible entity can comply with, alongside AS ISO/IEC 27001, the Essential Eight, the C2M2 and the Australian Energy Sector Cyber Security Framework. Complying with a framework is not the same as being certified against it; is ISO 27001 mandatory in Australia? explains where those rules bite.
How to choose
| Your situation | Start with |
|---|---|
| A tender or contract requires certification | ISO 27001. A CSF assessment won’t meet a certification requirement |
| Your board or insurer wants a clear view of cyber risk and a plan | A NIST CSF current and target profile |
| US customers send questionnaires framed around NIST | Whatever evidence they accept (usually SOC 2 or ISO 27001), with a CSF profile to answer in their terms |
| You are a critical infrastructure responsible entity | Any listed framework; ISO 27001 if you also want a certificate customers can check |
| You are early and nobody is asking yet | The Essential Eight basics, then a CSF profile or ISO 27001 when a customer drives it. See Essential Eight vs ISO 27001 |
Using both together
The frameworks complement each other well, and the combination is common in organisations that report to boards and sell to enterprises.
- CSF first, ISO 27001 second. A current profile is a structured way to see the whole picture before you commit to certification. The gaps it finds feed straight into your ISO 27001 risk treatment plan. This overlaps with an ISO 27001 gap analysis, so do one exercise and map it both ways rather than two.
- ISO 27001 as the engine, CSF as the dashboard. Run the ISMS for certification and use a CSF profile to report progress to the board. Your risk register, Statement of Applicability and internal audit results provide the evidence behind each outcome.
- One set of evidence. The same access review, incident exercise or supplier assessment supports an ISO 27001 control and a CSF subcategory. Map once, collect once.
Where teams go wrong is treating the CSF score as proof. A self-assessed Tier 3 that nobody has verified carries little weight with a buyer, and an inflated current profile hides the gaps you most need to fix. The reverse mistake is assuming an ISO 27001 certificate automatically means a high CSF tier; certification shows a conforming system for the scope certified, not maturity across the whole organisation. Building one mapping that holds up for both, and keeping it honest, is the part we take on for clients.
Effort and timing
A CSF assessment is lighter than ISO 27001 because nothing has to be audited by a third party. ISO 27001 takes more effort because you must operate the management system and produce evidence before the certification audit. For a typical SME that is about eight weeks to audit-ready; see how long ISO 27001 takes and what drives ISO 27001 effort. Scope is the biggest lever in both.
Next step
If you are building ISO 27001 yourself and using the CSF to track progress, remember the standard requires internal audits that are objective and impartial. Staff can do them if they aren’t auditing their own work, which is hard in a small team, so many bring in an independent internal audit before Stage 1. If you are weighing up which framework your buyers actually need, book a free 30-minute consultation, or see how our ISO 27001 and NIST CSF services work.
