Maturity

NIST CSF 2.0 Tiers vs Cybersecurity Maturity Levels

XR
Xcigence Research
Cyber Risk Intelligence Team
9 min read

"We are CSF Tier 3, so we are Level 3 mature" is a sentence heard in many assessment readouts. NIST itself disagrees with the equivalence. Understanding why is the key to reporting framework results honestly — and to building a maturity model that can sit above several frameworks without misrepresenting any of them.

What the CSF Tiers are

NIST CSF 2.0 defines four Tiers that characterize the rigor of an organization's cybersecurity risk governance and management practices.[1]

TierNameCharacterization
1PartialRisk management is ad hoc and reactive; limited organizational awareness of cyber risk.
2Risk InformedPractices are approved by management but may not be established organization-wide.
3RepeatablePractices are formally approved, expressed as policy and consistently applied.
4AdaptivePractices adapt from lessons learned and predictive indicators; risk management is part of culture.
NIST CSF 2.0 Tiers, paraphrased from NIST CSWP 29.

Why NIST says Tiers are not maturity levels

NIST is explicit that Tiers "do not necessarily represent maturity levels."[1] They describe the rigor of governance and risk-management practice, and organizations are encouraged to choose a target Tier that fits their risk, regulatory obligations and resources — a Tier 2 organization is not failing if Tier 2 is the appropriate target for its profile. Nor do Tiers grade the implementation of individual CSF outcomes; an organization can be Tier 3 in governance while a specific Detect outcome is barely implemented.

Key point
Reporting "NIST CSF Tier 3 — Repeatable" is correct and useful. Reporting "NIST maturity Level 3" is putting words in NIST's mouth. Keep the framework's own vocabulary.

Frameworks that do define maturity

  • C2M2 — The Department of Energy's model grades each domain by Maturity Indicator Level (MIL 0–3), with explicit practice requirements per level.[2] This is a true maturity model.
  • CMMC — Defines assessment levels for defence contractors. Because certification is external, an internal result should be expressed as estimated readiness ("Level 2 readiness 84%"), never as "certified."[3]
  • CIS Controls v8.1 — Implementation Groups IG1–IG3 prioritize safeguards by organizational profile and resources.[4] They are a prioritization scheme, not maturity levels — "IG2 82%" is a coverage statement.
  • COBIT 2019 — Provides capability levels for governance and management objectives[5] — a maturity-style concept, but with its own methodology and terminology.

The application-level rule that follows: differentiate maturity models, control frameworks, compliance standards, regulatory requirements and certification schemes, and never present one type's categories as another type's levels unless the standard itself defines them that way.

A normalized model that keeps each in its own words

The practical solution is a normalized internal model — Xcigence uses Levels 0–5 with a continuous 0–100 score — computed from evidence against a crosswalk of controls, with each framework's native result reported alongside. One verified piece of evidence (say, MFA telemetry) can support several mapped requirements. Mapping strength is graded — equivalent, substantially equivalent, partial, supporting, related — and cross-referencing two controls never automatically implies equivalent compliance.

FrameworkResult reportedResult type
Xcigence Maturity72 / 100 — Level 4, ManagedNormalized maturity model
NIST CSF 2.0Tier 3 — RepeatableFramework tier
C2M2Domain-specific MIL resultsMaturity model
CIS Controls v8.1IG1 100% · IG2 82% · IG3 49%Implementation coverage
ISO/IEC 27001:2022Control coverage 87%Coverage — not certification
CMMCEstimated Level 2 readiness 84%Readiness estimate — not certification
Illustrative Framework Maturity Alignment view. Framework results reflect an evidence-based assessment and do not constitute certification unless explicitly indicated.

What this means in practice

  • Pick a target Tier deliberately — Tier 4 is not automatically the goal; NIST expects the target to match risk and resources.
  • Assess outcomes separately from Tiers — Implementation of individual CSF outcomes is a control-coverage question with its own evidence.
  • Version everything — Mappings should reference NIST-CSF-2.0 and CIS-8.1 specifically, so historical results remain interpretable when standards change.
  • Label result types — Tier, MIL, coverage, readiness estimate and certification are different claims. Say which one you are making.

For the broader concept, start with What Is a Cybersecurity Maturity Score?; for how Xcigence reports alignment across frameworks, see Cybersecurity Maturity Intelligence.

Part of our guide to
Cybersecurity Maturity Intelligence

Evidence-driven 0–100 maturity scoring, framework alignment and next-best-action planning.

References

  1. [1]NIST. The NIST Cybersecurity Framework (CSF) 2.0 — NIST CSWP 29 (Section 3, Tiers)
  2. [2]U.S. Department of Energy. Cybersecurity Capability Maturity Model (C2M2)
  3. [3]U.S. Department of Defense. Cybersecurity Maturity Model Certification (CMMC)
  4. [4]Center for Internet Security. CIS Critical Security Controls v8.1 — Implementation Groups
  5. [5]ISACA. COBIT 2019 Framework

See your own cyber risk score

Xcigence computes a standardized 300–850 cyber risk score for your organization and every vendor in your ecosystem — no agents, no questionnaires.

We use cookies to improve your experience, analyze traffic, and support our marketing. See our Privacy Policy.