Regulations & frameworks

NIST Cybersecurity Framework 2.0 assessment

Your board wants to know how secure the company really is, your cyber insurer wants answers you can stand behind, and a customer or regulator has asked you to align to the NIST Cybersecurity Framework. A CSF 2.0 assessment turns that question into a current profile, a target profile and a prioritized plan to close the distance, in language your executives and your engineers both understand.

Formal outcome from
No one — the NIST CSF has no certification
Who asks for it
Boards and audit committees · Cyber insurance underwriters
Our role
Readiness — we help you build it and prove it
Your organization — readiness viewEvery requirement, an owner and its evidence
Readiness
  • SCOPE
    Scope and system boundary
    Ready
  • RISK
    Risk assessment and register
    Ready
  • ACCESS
    Access reviews, with evidence
    Gap · owner set
  • CHANGE
    Change management
    Closing
  • VENDOR
    Vendor management
    Gap · owner set
  • TEST
    Penetration test evidence
    Report in hand
Handed to the assessor you choose — the opinion is theirs
Gaps found before the audit
Who it’s for

Why NIST CSF lands on your desk.

The NIST Cybersecurity Framework is the most widely used common language for managing cybersecurity risk in the United States. Version 2.0, published by NIST in 2024, broadened its reach from critical infrastructure to organizations of every size and sector and added a sixth function, Govern, to the original five: Identify, Protect, Detect, Respond and Recover. Under those six functions sit 22 categories and 106 subcategories that describe outcomes — what good looks like — without prescribing how you get there.

That outcome focus is why the CSF travels so well. Boards use it to see the whole security program on one page. Cyber insurers and enterprise customers frame their questionnaires around it. Sector regulators and state agencies reference it, and several states, Ohio and Utah among them, offer legal protection in data-breach litigation to organizations whose security programs reasonably conform to a recognized framework such as the CSF. It also maps cleanly to more prescriptive standards, so the same profile can support SOC 2, ISO 27001, HIPAA or CMMC work later.

The CSF is voluntary, and there is no CSF certification: nobody can certify you against it, and nobody needs to. What it gives you is structure. Organizational Profiles describe your current and target outcomes; Tiers characterize how rigorous your cyber risk governance and management practices are; and NIST’s informative references and implementation examples link each outcome to concrete controls. Teams come to a CSF assessment for an honest baseline, a defensible target and a roadmap they can fund and report against.

Who asks for it
Boards and audit committeesCyber insurance underwritersEnterprise and public-sector customersSector regulators and state agenciesInvestors and lenders running due diligence

CISOs and security leaders

You need a defensible baseline and a target your board will fund, plus a way to show progress that doesn’t depend on whoever built last year’s slide deck.

Boards and executive teams

You are accountable for overseeing cyber risk and want one framework that shows where the company stands, where it is heading, and what the remaining gap means in business risk.

Growing companies without a framework

You have outgrown ad hoc security, a customer or insurer is asking which framework you follow, and you want a starting point that won’t box you in when a certification comes later.

Critical-infrastructure and public-sector suppliers

Utilities, manufacturers, healthcare organizations and government contractors whose regulators, state agencies or customers expect alignment to the CSF and ask to see it.

Who certifies

No certificate exists. The proof is yours to build.

Formal outcome from

No one — the NIST CSF has no certification

What they produce

Your own documented Current and Target Profiles, reported to your board, insurers, customers and regulators

Where readiness fits

NIST publishes the framework and does not assess, certify or endorse organizations against it, so treat any “CSF certificate” with suspicion. Readiness gives you a profile and roadmap built on evidence, mapped forward to the certifications and attestations — ISO 27001, SOC 2, CMMC — that an authorized assessor of your choice can grant.

NIST Cybersecurity Framework (CSF) 2.0, NIST CSWP 29 NIST CSF 2.0 Implementation Examples, Quick Start Guides and Community Profiles NIST CSF 2.0 Informative References (Cybersecurity and Privacy Reference Tool) NIST IR 8286, Integrating Cybersecurity and Enterprise Risk Management NIST SP 800-53 Rev. 5, Security and Privacy Controls for Information Systems and Organizations NIST SP 800-30 Rev. 1, Guide for Conducting Risk Assessments CIS Critical Security Controls v8.1 ISO/IEC 27001:2022
What it covers

What NIST CSF readiness covers.

  • Govern: organizational context, risk management strategy, roles and authorities, policy, oversight, and cybersecurity supply chain risk management
  • Identify: asset management, risk assessment and the improvement loop that feeds lessons back into the program
  • Protect: identity management, authentication and access control; awareness and training; data security; platform security; and technology infrastructure resilience
  • Detect: continuous monitoring and adverse event analysis
  • Respond: incident management, incident analysis, reporting and communication, and mitigation
  • Recover: recovery plan execution and recovery communication
  • A Current Profile rated subcategory by subcategory against evidence, not interviews alone
  • A Target Profile set by your risk appetite, legal and contractual obligations, and business priorities
  • Tier characterization of your governance and risk management practices, from Partial through Risk Informed and Repeatable to Adaptive
  • Supplier and third-party risk as CSF 2.0 now frames it under Govern
  • Mapping to the informative references you already answer to, such as NIST SP 800-53, ISO/IEC 27001 or the CIS Controls
  • Use of a NIST or sector Community Profile where one exists for your industry
  • Board-level reporting that ties cybersecurity risk into enterprise risk management
  • Answers for CSF-framed insurance, customer and regulator questionnaires
What you receive

What you have in hand when readiness is done.

1

Current Profile

Every CSF 2.0 subcategory rated against the evidence for how you operate today, with the reasoning written down so each rating survives scrutiny.

2

Target Profile

The outcomes you should reach and why, set by your risk appetite, contracts, regulators and insurers rather than a generic maturity ladder.

3

Gap analysis and prioritized roadmap

The distance between current and target, ranked by risk reduction and effort, with owners assigned — a plan you can budget for and track.

4

Tier assessment

An honest view of how rigorous your cyber risk governance and management are today, and what would move you to the Tier you actually need.

5

Board report

A plain-language summary of posture, top risks and progress for directors and executives, organized around the six functions.

6

Control crosswalk

Your profile mapped to SP 800-53, ISO/IEC 27001, the CIS Controls or the framework your customers use, so one body of work answers many questionnaires.

7

Governance and policy set

Cybersecurity strategy, policy, and roles and responsibilities drafted or updated to cover what the new Govern function expects.

8

Evidence-backed questionnaire answers

Clear, accurate answers for the CSF-framed questions insurers, customers and regulators send, tied to the evidence behind them.

Common gaps

What a NIST CSF readiness review tends to surface.

Better found now, by people on your side, than by your assessor.

No written risk appetite or risk management strategy, so priorities shift with whoever is asking

Cybersecurity risk managed apart from enterprise risk management and rarely reported to the board in business terms

Incomplete inventories of hardware, software, cloud services, data and suppliers

Supply chain risk management that ends with a questionnaire at vendor onboarding

Logs collected without anyone analyzing adverse events or tuning detection

Incident response and recovery plans that have never been exercised

Lessons from incidents, tests and exercises that never feed back into improvement

Profiles self-scored from interviews, with no evidence behind the ratings

Questions

What buyers ask about NIST CSF.

Can we get certified against the NIST CSF?

No. The CSF is a voluntary framework, and NIST does not certify, accredit or endorse organizations against it, so no legitimate CSF certificate exists. What you can have is a documented Current and Target Profile backed by evidence, which is what boards, insurers and customers actually ask for. If you need a certificate or attestation, CSF work maps directly into ISO 27001, SOC 2 or CMMC, each granted by an authorized assessor you choose.

What changed from CSF 1.1 to 2.0?

CSF 2.0 adds the Govern function, gathering risk strategy, roles, policy, oversight and supply chain risk management into one place instead of scattering them across Identify. It widens the intended audience from critical infrastructure to every organization, restructures several categories, and adds implementation examples, Quick Start Guides, Community Profiles and online informative references. If your last assessment used 1.1, the ratings don’t carry over cleanly; the governance and supply chain outcomes in particular need fresh evidence.

What is the difference between a Profile and a Tier?

A Profile describes outcomes: your Current Profile records which CSF outcomes you achieve today and how well, and your Target Profile records which you intend to achieve. Tiers describe the rigor of your approach — Partial, Risk Informed, Repeatable or Adaptive — across cyber risk governance and management. Tiers are not a maturity score to chase for its own sake; the right Tier depends on your risk and resources, and aiming for Adaptive everywhere is rarely sensible.

How does the CSF relate to NIST SP 800-53 and SP 800-171?

The CSF says what outcomes to achieve. SP 800-53 is a catalog of specific security and privacy controls, and SP 800-171 is the requirement set for protecting Controlled Unclassified Information in nonfederal systems. NIST’s informative references link CSF subcategories to those controls. Many organizations use the CSF to set direction and report to leadership, then use a control catalog to implement and test. If you handle CUI or sell to the Department of Defense, a CSF profile is a useful first view, but SP 800-171 and CMMC set the bar you are measured against.

Will a CSF assessment help with our cyber insurance renewal?

Underwriters increasingly ask about specific controls — multi-factor authentication, endpoint detection and response, backups, privileged access, incident response — and many organize their questions around the CSF functions. A current, evidence-backed profile lets you answer accurately, which matters because inaccurate answers can lead to coverage disputes after a claim. It also shows which gaps are most likely to affect your terms, so you can address those first.

Our board wants a cyber scorecard. Is the CSF the right basis?

It is the most common one, because six functions are simple enough for directors to follow while still mapping to detailed controls underneath. A CSF-based report can show the current and target position for each function, the highest risks, and progress against the roadmap over time. Pairing the profile with penetration testing and exercise results keeps the scorecard grounded in evidence instead of self-assessment.

Is NIST CSF on your desk?

One conversation with someone who does this work. You leave knowing where you likely stand and what readiness would involve for you.

Free attack-surface snapshot

Give us a domain. See what an attacker sees.

Not sure where to start? One of our testers reviews your internet-facing footprint and sends you a short summary of what an attacker would see — free. Nothing you don’t own is ever touched, and there’s no sales sequence.

  • Internet-facing hosts
  • Exposed services
  • Leaked credentials
  • TLS certificate hygiene

Request your snapshot

Free. No obligation.

We only ever test assets you own, with your written authorization. How we handle your details