How to Get CMMC Certified: Step-by-Step Guide for Defense Contractors (2026)
Getting CMMC certified is now mandatory for defense contractors handling Controlled Unclassified Information (CUI) on DoD contracts. Whether you're a small subcontractor or a mid-market prime, the path to certification follows the same process — but the complexity and cost scale with your organization's size and CUI footprint.
This step-by-step guide walks you through the entire CMMC certification process, from initial readiness assessment to final C3PAO certification, with practical timelines and cost estimates at each stage.
Before You Start: Determine Your Required CMMC Level
Not every contractor needs the same CMMC level. Your required level depends on the type of information you handle:
- Level 1 (Self-Assessment): You handle Federal Contract Information (FCI) only — basic contract data, delivery schedules, invoices. 17 practices, self-assessed annually.
- Level 2 (Third-Party Assessment): You handle Controlled Unclassified Information (CUI) — technical data, engineering drawings, export-controlled information, proposal content marked CUI. 110 practices from NIST SP 800-171, assessed by accredited C3PAO.
- Level 3 (Government Assessment): You support the most sensitive DoD programs with heightened CUI protections. 110+ practices including NIST SP 800-172 enhancements, assessed by DIBCAC.
How to check: Review your active contracts and anticipated solicitations on SAM.gov. Look for DFARS clauses 252.204-7012 (Safeguarding CUI) and 252.204-7021 (CMMC requirements). The solicitation will specify the required CMMC level.
How to Get CMMC Certified: Step-by-Step Roadmap
Step 1: Define Your CUI Boundary (Weeks 1–4)
The CUI boundary is the foundation of everything that follows. It defines which systems, networks, applications, and data flows handle CUI — and therefore which assets must meet all CMMC controls.
What to document:
- Every system that stores, processes, or transmits CUI (servers, workstations, cloud services, mobile devices)
- Network segments and firewalls separating CUI from non-CUI environments
- Data flows showing how CUI enters, moves through, and exits your environment
- Cloud services that process CUI (each must be FedRAMP authorized or equivalent)
- Third-party connections (subcontractors, vendors) that receive CUI from you
Key strategy: Minimize the boundary. The smaller your CUI boundary, the fewer systems require full CMMC controls, and the faster and cheaper your certification. Consolidating CUI workflows onto a single compliant platform — like Cabrillo Club's private AI infrastructure — dramatically reduces scope.
Deliverable: CUI Boundary Diagram + System Inventory
Step 2: Conduct a Gap Assessment (Weeks 3–8)
A gap assessment evaluates your current security posture against every applicable CMMC requirement. For Level 2, this means testing all 110 NIST 800-171 controls.
How to conduct the assessment:
- Use NIST SP 800-171A as your assessment guide — it provides specific evaluation methods for each control
- For each of the 110 requirements, document status as: Met, Partially Met, or Not Met
- Calculate your SPRS score (perfect score is 110; each unmet requirement deducts 1, 3, or 5 points based on severity)
- Identify quick wins (controls you can implement in under 2 weeks) vs. major gaps (requiring procurement or infrastructure changes)
Who should do it:
- In-house option: Your CISO or IT security lead using NIST 800-171A. Best for organizations with security expertise on staff. Cost: internal staff time.
- External option: A CMMC consultant or Registered Provider Organization (RPO). Note: the entity performing your gap assessment cannot also serve as your C3PAO assessor. Cost: $10,000–$40,000.
Deliverable: Gap Assessment Report + SPRS Score
Step 3: Develop Your System Security Plan (Weeks 5–12)
Your SSP is the most critical document in the entire CMMC process. Assessors use it as their primary guide — if the SSP doesn't accurately describe your environment, the assessment will fail before it starts.
What the SSP must include:
- System description and purpose
- System boundary and network architecture diagrams
- Hardware and software inventory
- Data flow diagrams showing CUI handling
- For each of the 110 controls: a specific description of how YOUR organization implements it (not a generic statement)
- Interconnection agreements with external systems
- User roles and access authorization policies
- Ports, protocols, and services in use
SSP writing tips:
- Be specific. "We use encryption" fails. "We use BitLocker with FIPS 140-2 validated AES-256 on all workstations within the CUI boundary, managed through Group Policy Object X" passes.
- Include evidence references for each control (screenshots, configuration exports, policy document citations)
- Update the SSP every time you change infrastructure. Stale SSPs are a top assessment failure cause.
Deliverable: System Security Plan (SSP) + Network Diagrams
Step 4: Build Your Plan of Action and Milestones (Weeks 8–12)
The POA&M tracks every gap identified in Step 2 that hasn't been remediated yet. It's not a wishlist — it's a commitment with dates and owners.
POA&M requirements:
- Specific description of the weakness (reference the NIST 800-171 requirement number)
- Remediation plan with concrete steps
- Milestone dates (assessors reject open-ended timelines)
- Responsible party (name and role, not just "IT team")
- Resources required (budget, tools, personnel)
- Status tracking (updated monthly at minimum)
Important: C3PAO assessors accept POA&Ms for some controls, but not for critical security functions. Controls related to MFA, encryption (FIPS-validated), access control, and audit logging must be fully implemented — they cannot be on a POA&M at assessment time.
Deliverable: POA&M Spreadsheet/Tracker
This is typically the longest and most expensive phase. Prioritize based on risk and assessment readiness:
Priority 1 — Assessment blockers (must be complete before C3PAO engagement):
- Deploy MFA on all CUI-boundary accounts (IA.L2-3.5.3)
- Implement FIPS-validated encryption at rest and in transit (SC.L2-3.13.8, SC.L2-3.13.11, SC.L2-3.13.16)
- Configure audit logging on all CUI-boundary systems (AU.L2-3.3.1)
- Define and enforce role-based access controls (AC.L2-3.1.1, AC.L2-3.1.5)
- Deploy endpoint protection on all workstations and servers (SI.L2-3.14.2)
Priority 2 — High-value controls: