Breach Risk Direct.
Compliance

NIST CSF 2.0 vs ISO 27001 vs CIS Controls: Which Framework Should You Build On?

Only one of the three gets you a certificate. Another speaks the language of underwriters. Here's what each typically costs, how regulators in different regions see it, and which one to build on first.

Breach Risk Direct editorial team · November 2026 · 11 min read

You're choosing what to build on, not one framework forever

Most companies don't pick between NIST CSF 2.0, ISO 27001 and the CIS Controls in the abstract. Something forces the choice. A large customer sends a supplier questionnaire that asks for an ISO certificate. A regulator publishes new rules. Or a cyber insurance renewal comes back with a longer application and a higher retention. The question underneath is always the same: which framework earns the most credit with the people who control your revenue and your risk transfer, for the least wasted effort?

The usual NIST CSF vs ISO 27001 debate misses that these three do different jobs. ISO/IEC 27001 is a management-system standard you can be certified against. NIST CSF 2.0 is an outcome-based framework for governing and discussing cyber risk. The CIS Controls are a prioritized list of technical safeguards. Mature programs often use all three: ISO for external proof, NIST CSF for board reporting, CIS for the engineering backlog. What you have to decide is which one becomes the backbone and which ones you map to it.

Advertisement

This comparison judges them on four things buyers live with: whether you can certify, how customers and regulators in different regions read each one, what implementation costs, and how well each lines up with underwriting questionnaires.

What each framework actually asks of you

AttributeNIST CSF 2.0ISO/IEC 27001:2022CIS Controls v8.1
PublisherUS National Institute of Standards and TechnologyISO and IEC (international standards bodies)Center for Internet Security (nonprofit)
StructureSix functions (Govern, Identify, Protect, Detect, Respond, Recover), divided into categories and subcategoriesManagement-system clauses plus an Annex A reference set of controls18 controls with safeguards tiered into Implementation Groups IG1–IG3
NatureOutcomes and profiles; tells you what to achieveRisk-based management system; tells you how to run securityPrescriptive technical actions; tells you what to do first
Cost to obtainFreeStandard is purchased; certification is paidFree to download (registration required)
CertifiableNoYes, through accredited certification bodiesNo formal certification

Version 2.0 of the NIST framework, released in 2024, added the Govern function and dropped the critical-infrastructure framing. That matters outside the US: it's now positioned for organizations of any type and in any country. The 2022 revision of ISO 27001 reorganized the Annex A controls and added new ones such as threat intelligence and cloud services security. The transition window for the older 2013 version has closed, so any certificate you're shown should reference 27001:2022.

Certification is where the three really split

If a customer or regulator wants an independently audited certificate, only ISO 27001 qualifies. That single fact decides more buying situations than anything else here.

ISO 27001 certification runs on a three-year cycle: a two-stage initial audit (documentation review, then an operational audit), annual surveillance audits, and a recertification audit at the end. The certificate lists a defined scope, so buyers should always read it. A certificate covering only "the IT department at headquarters" says very little about a SaaS product run out of another region.

NIST CSF has no certification. Consultancies will assess you against it and issue maturity scores or attestation letters, but those don't carry the weight of an accredited certificate. Anyone selling "NIST CSF certification" is selling their own branded assessment.

The CIS Controls have no formal certification either. You can self-assess against them, but the result is a scorecard, not a credential procurement teams recognize. That's not a flaw. CIS was never meant to be a credential. It's a to-do list, and a good one.

How customers and regulators in different regions read each one

Acceptance varies by geography and sector, and companies that sell across borders get caught out here.

Europe and the UK

ISO 27001 is the default language of B2B assurance. Under NIS2, essential and important entities and their suppliers often use ISO 27001 to show appropriate measures are in place, though it isn't a legal safe harbor. Financial firms under DORA still have to meet its specific ICT risk requirements, but an ISO-based management system gives them a structure to hang those on. In the UK, Cyber Essentials is often requested alongside ISO for public-sector work. NIST CSF is understood but rarely requested.

Asia-Pacific

ISO 27001 is widely held and expected across Japan, China, India, Singapore and much of Southeast Asia. Sector regulators issue their own rules, such as the MAS technology risk guidelines in Singapore and SEBI and RBI requirements in India. These generally don't mandate a single framework, but an ISO-certified ISMS maps well to them. Australia's Essential Eight sits closer to CIS in spirit.

Middle East

National frameworks dominate. Saudi Arabia's NCA Essential Cybersecurity Controls and the UAE's information assurance standards draw on both ISO and NIST concepts. Government-linked customers will audit against the national controls, but ISO 27001 is widely recognized and shrinks the gap work.

The Americas

In the US and Canada, NIST CSF is the common vocabulary for boards, regulators and federal-adjacent buyers, while SOC 2 tends to beat ISO as the commercial assurance report. In Latin America, including Brazil, Mexico, Colombia and Chile, ISO 27001 is the more commonly requested credential, especially from multinationals and banks.

Africa

In South Africa, Kenya and Nigeria, ISO 27001 is a common reference point for banks, telecoms and their suppliers, often alongside data-protection obligations such as POPIA or Nigeria's data protection law. Check your sector regulator's guidance rather than assuming.

The pattern is plain: ISO 27001 is the closest thing to a global passport, and NIST CSF is a respected reference that is rarely requested by name outside North America.

Implementation effort and cost ranges

Costs depend on scope, how much of the program already exists, and whether you use consultants, a compliance automation platform, or both. The ranges below are typical 2026 market ranges for a company of roughly 50–500 staff. They vary by region, contract and vendor, so confirm them with providers.

Cost elementNIST CSF 2.0ISO 27001CIS Controls (IG1–IG2)
Initial gap assessment$10,000–$40,000$10,000–$35,000$5,000–$25,000
Consulting / program build$20,000–$100,000$25,000–$120,000Mostly internal effort plus targeted help
Compliance automation platform (e.g., Vanta, Drata, Secureframe)Optional, roughly $8,000–$35,000/yrCommon, roughly $10,000–$45,000/yrRarely needed
Certification auditNot applicableRoughly $12,000–$45,000 initial; $6,000–$25,000 per surveillance yearNot applicable
Tooling to close gaps (MFA, EDR, backups, logging)Varies widelyVaries widelyUsually the main cost; depends on what you already own
Typical time to a defensible baseline4–9 months6–12 months to certificate3–6 months for IG1

Two notes on NIST CSF cost. The framework is free, but turning it into a target profile and a measurable roadmap is consulting-heavy unless you have an experienced security lead. And it doesn't tell you which technical gaps to fix first. That's why many CSF programs end up using CIS safeguards as the implementation layer.

Hypothetical example: say a 150-person software company in Poland selling to German manufacturers needs ISO 27001 within a year. With a part-time consultant ($40,000), an automation platform ($20,000), an initial audit ($20,000) and about half an FTE of internal time, year one lands somewhere around $80,000–$130,000 before tooling. Surveillance years then drop to roughly $35,000–$60,000.

How well each one maps to underwriting questionnaires

Cyber insurance applications have converged on a short list of controls that drive claims: MFA on email, remote access and privileged accounts; endpoint detection and response; offline or immutable backups that have been tested; patching cadence; privileged access management; email filtering; and a tested incident response plan. Underwriters in Lloyd's, the major global carriers and regional markets ask about these in one form or another.

Here CIS beats ISO 27001 clearly. Its IG1 safeguards read almost like an underwriting questionnaire: asset inventory, secure configuration, account management, access control, data recovery, malware defenses and audit logging. A company with IG1 evidence can answer most application questions with a confident "yes" and supporting detail.

ISO 27001 helps less directly than people expect. A certificate shows you run a managed program, and some underwriters accept it as supporting evidence, but Annex A is risk-based. You can be certified while having excluded or only partly implemented a control an insurer treats as mandatory. It rarely removes the need to answer the technical questions, and it doesn't reliably earn a premium credit on its own.

NIST CSF sits in between. Its Govern, Respond and Recover functions line up with the governance and incident-readiness sections of longer mid-market and large-account applications, and brokers find a CSF maturity summary useful in submissions. But the subcategories are too high-level to answer "is MFA enforced for all remote access?" without evidence underneath.

Whichever you choose, keep a one-page evidence pack mapped to the questions your carrier actually asks. Talk to your broker about how your controls will be represented on the application, because a misstatement can affect coverage.

Red flags when scoping a framework program

  • A narrow ISO scope built to pass, not to reassure. If the scope leaves out the product customers actually buy, sophisticated buyers will notice and the certificate loses most of its value.
  • "NIST CSF certified" in a proposal. No accredited certification exists. Ask exactly what the deliverable is.
  • Policies without operating evidence. Automation platforms generate policies fast. Auditors and underwriters want logs, tickets, access reviews and restore tests.
  • Skipping the risk assessment. ISO 27001 depends on a credible risk assessment and Statement of Applicability. Templates copied wholesale tend to fail stage two or produce a program nobody follows.
  • Jumping straight to CIS IG3. Lean teams that attempt every safeguard stall. Do IG1 first, then the IG2 safeguards your risk profile justifies.
  • One framework per stakeholder. Separate ISO, NIST and insurer workstreams multiply evidence collection. Pick one control set as the system of record and map the others to it.

Verdicts for exporters, regulated firms and lean teams

Exporters and companies selling to multinationals: build on ISO 27001

If growth depends on passing supplier due diligence in Europe, Asia, the Middle East or Latin America, ISO 27001 shortens sales cycles. It's the clear answer in most NIST CSF vs ISO 27001 decisions for exporters, because a framework with no certificate can't be uploaded to a procurement portal. Use CIS IG1 as the technical floor inside your ISMS so the certificate is backed by controls insurers care about. If you also sell into North America, plan for SOC 2 using the same evidence.

Regulated firms: build on what your regulator maps to, usually ISO with NIST CSF on top

Banks, insurers, healthcare providers, energy firms and NIS2-scoped entities answer to sector rules first. Map those rules to your controls directly. Outside North America, an ISO 27001 management system is usually the best backbone because auditors and supervisors already understand it. Add NIST CSF 2.0 as the board and risk-committee reporting layer; the Govern function fits board accountability requirements well. In the US, the order often flips: NIST CSF as the backbone, ISO only if international customers demand it.

Lean mid-size teams (roughly 30–300 staff, small or no security function): build on CIS Controls IG1

If nobody is asking for a certificate yet, the fastest risk reduction and best insurance outcome come from CIS IG1. It's concrete, it can be sequenced, and it maps closely to underwriting questions. Use NIST CSF 2.0's functions as a one-page way to report progress to leadership. Move to ISO 27001 when a contract, tender or regulator requires it. By then a good share of the technical work will already be done.

A decision rule and the next 30 days

If a customer, tender or regulator has asked for a certificate in the past 12 months, or likely will within 18, build on ISO 27001. If not, build on CIS IG1 and report through NIST CSF 2.0. Either way, keep one control set as the system of record and map everything else to it.

For the next 30 days:

  1. Pull your last 10 customer security questionnaires and your latest cyber insurance application. Count how many ask for ISO, NIST, SOC 2, or specific technical controls.
  2. Run a CIS IG1 self-assessment. It takes days, not months, and shows your underwriting exposure.
  3. Ask two or three ISO consultancies or certification bodies for scoped quotes based on your actual product boundary.
  4. Brief your broker on which controls you can evidence today, before your next renewal.
  5. Have your legal or compliance advisor confirm which sector regulations apply in each country you operate in before you commit budget.

Frequently asked questions

Can we be certified against NIST CSF 2.0?

No. NIST CSF has no accredited certification scheme. Third parties can assess you against it and issue maturity reports, but those aren't equivalent to an ISO 27001 certificate from an accredited certification body.

Does ISO 27001 certification lower cyber insurance premiums?

Sometimes it helps, but rarely on its own. Underwriters price mostly on specific controls such as MFA, EDR, tested backups and privileged access management, so you'll still need to evidence those. Ask your broker how your carrier treats certification.

How long does ISO 27001 take for a mid-size company?

Six to twelve months from kickoff to certificate is typical when basic security is already in place. A low starting baseline or a broad multi-site scope can push it past a year.

Is the CIS Controls framework enough for regulated companies?

Usually not by itself. CIS covers technical safeguards well but leaves out the governance, risk management and supplier oversight that regulators such as NIS2 authorities or financial supervisors expect. Use it as the technical layer under ISO 27001 or your sector framework, and confirm requirements with a qualified compliance advisor.

Can one program satisfy ISO 27001, NIST CSF and CIS at the same time?

Yes, and that's the efficient approach. Pick one control set as the system of record, then use published crosswalks to show coverage of the others. Compliance automation platforms can handle much of the mapping.

Written by the Breach Risk Direct editorial team. Prices, features and rules change often - confirm details with the vendor or a licensed professional before you decide.