NIST Cybersecurity Framework (CSF) 2.0 for Small Businesses: A Practical Starting Point

Short answer: The NIST Cybersecurity Framework (CSF) 2.0 is free, voluntary guidance from NIST, released in February 2024. It describes the cybersecurity outcomes an organization should aim for, grouped into six Functions: Govern, Identify, Protect, Detect, Respond, and Recover. It doesn’t tell you which products to buy or how to achieve each outcome. For a small business, the practical path is to start with NIST’s Small Business Quick-Start Guide, record where you stand today (a Current Profile), decide where you need to be (a Target Profile), and work the gap in priority order.

What is NIST CSF 2.0?

The CSF is a common language for managing cybersecurity risk. NIST first released it in 2014, and CSF 2.0 (NIST CSWP 29, February 26, 2024) is its first major update. NIST designed it for organizations of all sizes and sectors, regardless of how mature their security program is. Version 2.0 widened the scope beyond critical infrastructure and added a new focus on governance and supply chain risk.

Three things make the CSF useful for a small company:

  • It’s outcome-based. NIST states that the CSF “does not prescribe how outcomes should be achieved.” You choose the controls that fit your size and budget.
  • It isn’t a checklist. The outcomes are not a list of actions to perform in order. You prioritize them based on your own risks.
  • It’s easy to explain. The six Functions give you a simple way to show customers, insurers, and leadership where you stand.

The CSF Core is organized as 6 Functions, 22 Categories, and 106 Subcategories. You don’t need to tackle all 106 at once. Most small businesses start with the handful that address their biggest risks.

What are the six CSF 2.0 Functions?

Function NIST’s definition (abridged) In plain English
Govern (GV) — new in 2.0 Cybersecurity risk management strategy, expectations, and policy are established, communicated, and monitored Who owns security, what rules you follow, what you must comply with, and how leadership oversees it
Identify (ID) Current cybersecurity risks are understood Know what you have (devices, software, data, vendors) and what could go wrong
Protect (PR) Safeguards to manage cybersecurity risks are used MFA, access control, training, patching, backups, encryption
Detect (DE) Possible attacks and compromises are found and analyzed Notice when something is wrong, through monitoring, alerts, and staff reporting
Respond (RS) Actions regarding a detected incident are taken Contain the incident, communicate, and report as required
Recover (RC) Assets and operations affected by an incident are restored Get back to business and learn from what happened

Govern is the biggest change from CSF 1.1. It treats cybersecurity as a business risk that leadership weighs alongside finance and reputation, not as a purely IT topic. It covers organizational context, risk management strategy, roles and responsibilities, policy, oversight, and cybersecurity supply chain risk management.

What are CSF Profiles and Tiers?

Profiles are how you apply the CSF to your business:

  • A Current Profile describes the outcomes you’re achieving today and how well.
  • A Target Profile describes the outcomes you’ve chosen and prioritized for where you need to be, considering new requirements, technology changes, and threats.
  • A Community Profile is a published baseline for a sector or use case. You can use one as the starting point for your Target Profile.

The gap between Current and Target becomes your action plan. NIST suggests documenting it as a prioritized plan, such as a risk register or a POA&M.

Tiers are optional. They describe how rigorous your risk management practices are, on four levels: Partial (Tier 1), Risk Informed (Tier 2), Repeatable (Tier 3), and Adaptive (Tier 4). NIST encourages moving to a higher Tier when risks or mandates are greater, or when the cost-benefit case supports it. Tier 4 is not a goal every small business needs to reach.

What is the NIST Small Business Quick-Start Guide?

NIST publishes short Quick-Start Guides that distill parts of the CSF into practical first steps. The CSF 2.0 Small Business Quick-Start Guide (NIST SP 1300) is written for small and mid-sized businesses with modest or no cybersecurity plans in place. For each Function, it lists actions to consider. Examples include:

  • Govern: Understand your legal, regulatory, and contractual cybersecurity requirements, and assess whether cybersecurity insurance is appropriate.
  • Identify: Keep an inventory of hardware, software, systems, and services, and document threats in a risk register.
  • Protect: Require multi-factor authentication wherever it’s offered, change default passwords, patch regularly, back up data and test the backups, and enable full-disk encryption on laptops.
  • Detect: Install and maintain anti-malware on all business devices, and consider a service provider for monitoring if you can’t do it in-house.
  • Respond: Know your incident response plan and who has authority to act on it.
  • Recover: Know who has recovery responsibilities, and check the integrity of backups before restoring from them.

Other CSF 2.0 Quick-Start Guides cover Organizational Profiles, Tiers, Enterprise Risk Management, and Cybersecurity Supply Chain Risk Management. NIST also publishes Implementation Examples for each outcome, and the CSF 2.0 Reference Tool lets you browse the Core and export it.

How can a small business get started with CSF 2.0 in 90 days?

A realistic first quarter for a company of 10 to 150 people:

Phase Focus Outputs
Days 1–30: Govern and Identify Name an accountable security owner. List legal, contractual, and customer requirements. Inventory devices, software, cloud services, data, and key vendors. Owner named, requirements list, asset and vendor inventory
Days 31–60: Current Profile and quick wins Score where you stand against the Subcategories that matter most to you. Close the obvious gaps: MFA, default passwords, patching, tested backups. Current Profile, risk register, quick wins done
Days 61–90: Target Profile and plan Choose your Target Profile, prioritize the gaps, assign owners and dates. Write the core policies and an incident response plan. Target Profile, prioritized roadmap, policy set, incident response plan

After 90 days, the CSF becomes a rhythm: review the risk register monthly, update the Profiles when the business changes, and report progress to leadership on a set schedule.

How does CSF 2.0 relate to CMMC, ISO 27001, and CIS Controls?

The CSF works well as an organizing umbrella, but it doesn’t replace a framework you’re contractually required to meet.

  • NIST SP 800-171 and CMMC. If you handle Controlled Unclassified Information for the Department of Defense, NIST SP 800-171 and CMMC are the requirements that apply. CSF alignment alone won’t satisfy them. NIST publishes an informative reference mapping CSF 2.0 to SP 800-171 Rev. 3. See CMMC readiness.
  • ISO/IEC 27001. ISO 27001 is a management system standard that organizations can be certified against. A mapping between ISO/IEC 27001:2022 and CSF 2.0 is listed in NIST’s informative reference catalog. If customers ask for a certificate or audit report, see ISO 27001 vs. SOC 2.
  • CIS Controls. The CIS Critical Security Controls are a prioritized set of specific safeguards. A CIS Controls v8.1 to CSF 2.0 mapping is also listed in NIST’s catalog. Many small businesses use CIS Controls for the “how” and the CSF for the “what” and “why”.

What are the most common CSF mistakes?

  • Treating it as a checklist. NIST is explicit that the Core is not a checklist. Trying to “complete” all 106 Subcategories wastes effort on low-risk items.
  • Skipping Govern. Without a named owner, defined requirements, and leadership oversight, technical controls drift.
  • Claiming “CSF compliance.” The CSF is voluntary guidance you align to. Describe your Current and Target Profiles honestly rather than claiming a status that isn’t defined.
  • Aiming for Tier 4 by default. Pick the Tier that matches your risk and obligations.
  • Building a Profile once and never updating it. Profiles should change when your systems, vendors, contracts, or threats change.

Frequently Asked Questions

Is NIST CSF 2.0 mandatory for small businesses?

No. The CSF is voluntary guidance. It can become required when a government policy, regulator, or contract calls for it, so check your contracts and customer requirements.

Is CSF 2.0 too big for a small company?

No, if you scope it. NIST’s Small Business Quick-Start Guide was written for companies with modest or no cybersecurity plans. Start with its suggested actions and the Subcategories tied to your biggest risks.

What is the difference between CSF 1.1 and CSF 2.0?

CSF 2.0 added the Govern Function, expanded coverage of supply chain risk, broadened the intended audience to all organizations, and added online resources such as Quick-Start Guides, Implementation Examples, and the CSF 2.0 Reference Tool.

Does following CSF 2.0 make us CMMC compliant?

No. CMMC Level 2 assesses the security requirements of NIST SP 800-171. The CSF can help organize your overall program, but defense contractors handling CUI must meet those specific requirements.

How USCIBER can help

USCIBER’s Security & Risk Assessment (starting at $6,500) maps your current state against CSF 2.0, produces your Current Profile and risk register, and delivers a prioritized roadmap toward a realistic Target Profile. For ongoing program work, our vCISO service turns that roadmap into a steady governance rhythm. Engagements are led by security leadership holding CISSP, CISA, and CISM credentials. Book a free consultation.

Sources

This article is general information, not legal advice.

Need help applying this?

Tell us what you're facing — a CMMC requirement, a customer questionnaire, an audit, or no security program at all. We'll reply within one business day with a recommended next step.