ResourcesBlog

CMMC 2.0: What You Need to Know

The CMMC program is officially active with assessments underway. Here’s a practical guide for organizations navigating the requirements.

PolicyCortex TeamPublished 2025-11-20Reading time 2 min

Filed underCMMC compliance NIST 800-171

Summary

CMMC 2.0 is officially active — the 32 CFR Part 170 final rule took effect in December 2024, and assessments are underway through authorized C3PAOs.
Level 2 certification (110 NIST 800-171 controls) is required for most organizations handling CUI, with mandatory third-party assessment.
Reducing scope through CUI environment segmentation is the single most effective way to lower assessment cost and complexity.
CMMC requires continuous monitoring, not one-time audits — automated compliance platforms dramatically reduce the operational burden of maintaining certification.
Common mistakes include treating CMMC as a checkbox exercise, waiting too long to start, and ignoring cloud environment configurations.

CMMC 2.0 Overview

The Cybersecurity Maturity Model Certification (CMMC) 2.0 framework establishes cybersecurity requirements for organizations that handle FCI or CUI under DoD contracts. It streamlines the original five-level model down to three levels and codifies the requirement for third-party assessments at Level 2 and above.

If you handle Controlled Unclassified Information (CUI) for the Department of Defense, CMMC affects you.

The Three Levels

Level 1 — Foundational covers 15 basic cybersecurity practices from FAR 52.204-21. This level requires annual self-assessment and applies to organizations handling Federal Contract Information (FCI).

Level 2 — Advanced maps directly to the 110 security requirements in NIST SP 800-171. Most organizations handling CUI will need Level 2 certification, which requires assessment by an authorized C3PAO (Certified Third-Party Assessor Organization).

Level 3 — Expert adds requirements from NIST SP 800-172 for enhanced security against advanced persistent threats. This level requires government-led assessment and applies to a smaller set of critical programs.

Timeline and Enforcement

The CMMC program is now officially active. The 32 CFR Part 170 final rule took effect in December 2024, and CMMC requirements are being phased into DoD contracts through the 48 CFR DFARS rulemaking process.

This is no longer a future requirement. Organizations that haven’t started preparation are already behind.

Practical Steps for Preparation

1. Scope Your CUI Environment

Identify exactly where CUI flows and is stored in your organization. The scope of your assessment — and the cost — depends entirely on this boundary.

2. Conduct a Gap Assessment

Map your current security posture against all 110 NIST 800-171 practices. Common problem areas include access control, audit log management, configuration management, incident response, and system communications protection.

3. Build Your System Security Plan (SSP)

Your SSP documents how you implement each security requirement.

4. Address Gaps with a POA&M

A Plan of Action and Milestones (POA&M) documents known gaps and your plan to close them.

5. Establish Continuous Monitoring

CMMC is not a one-time audit. Organizations must maintain their security posture continuously between assessments.

Common Mistakes

Treating CMMC as a checkbox exercise. The assessors are looking at actual security posture, not just documentation.

Waiting too long to start. Achieving compliance takes most organizations months, not weeks. C3PAO availability is limited.

Ignoring the cloud. Many organizations use AWS, Azure, or GCP without properly configuring these environments for CUI handling.

Cloud misconfigurations are among the top findings in CMMC assessments. If your CUI touches cloud infrastructure, your cloud environment is in scope.

Related records

Guides and articles describe the work. The evidence that work produces is described in three proof pages, the architecture page, and the two pages on authorization.

proof.state: Proof of State. What the environment was, as of a date someone else picks: point-in-time records, content hashed and chained.
proof.change: Proof of Change. Who or what altered the environment, under what authority, with before and after state hashes.
proof.agency: Proof of Agency. What a machine was permitted to do before it acted, what it did, and what would have stopped it.
architecture: Architecture. How the chain is built and where the evidence is stored in each delivery mode.
authorization: Continuous ATO. How an authorizing official's decision is recorded with its package, and how the authorized system is checked against it every hour.
baseline: NIST SP 800-53. The Low, Moderate and High baselines as evidence, with the SSP, SAR and POA&M generated from one record.