Join our Newsletter — 33% off our NHI Course
Home› Guides› CMMC Level 1 vs Level 2 vs Level…
Guide Regulations & Frameworks

CMMC Level 1 vs Level 2 vs Level 3: Which Level Applies to Your Contract

PDF for newsletter subscribers · free to read online

← All guides
By NHI Mgmt Group, edited by Lalit Choda Updated 14 November 2026 16 min read
On this page

Most defence suppliers who ask "which CMMC level do I need" are really asking three separate questions: what information will I hold, what does the contract clause say, and who is allowed to assess me. Getting any one of them wrong leads to the same two outcomes: money spent on an assessment the contract never needed, or an affirmation signed for a level the company cannot defend. This guide is a decision tool. It explains the trigger for each level (FCI or CUI), the control set behind it, the assessment route (self, C3PAO or DCMA DIBCAC), the POA&M rules, what drives cost and timeline, and how to read a solicitation to find your answer. It is for compliance leads, contracts teams, IT managers and the managed service providers who support them. Requirement-by-requirement detail lives in the level-specific guides linked throughout.

Status note: programme status, dates and rules below were checked against the DoD CIO "About CMMC" page, 32 CFR Part 170 and DFARS subpart 204.75 on 14 November 2026. CMMC is under review and details may change, so confirm against the official text before relying on it.

Key takeaways

  • The information decides the floor. FCI alone points to Level 1 (Self); CUI points to Level 2; Level 3 applies only where the program office says the CUI supports a critical programme or high value asset.
  • The contract decides the level, not you. Under DFARS 204.7503 the contracting officer writes in the level the program office or requiring activity has set, and DFARS 252.204-7021 makes it binding for every system that handles the FCI or CUI.
  • Level 2 has two routes. Level 2 (Self) and Level 2 (C3PAO) use the same 110 requirements; the solicitation decides which one counts, and since 13 July 2026 the DoD CIO says the programme "may only require self-assessments at two levels".
  • POA&M rules tighten, then change shape. Level 1 allows none; Level 2 needs 80 per cent and allows only 1-point items (plus one encryption exception); Level 3 needs 80 per cent and bars seven named requirements.
  • Level 3 is built on Level 2. A Level 3 (DIBCAC) assessment cannot start without a Final Level 2 (C3PAO) status on the same or a larger scope, so a Level 3 plan is always a two-assessment plan.

The short answer

If your contract only gives you, or has you generate, non-public information under the contract that is not marked or designated as CUI, you are looking at Level 1 (Self): 15 requirements, an annual self-assessment and an annual affirmation. If you will process, store or transmit CUI, you are at Level 2, and the solicitation will say whether a self-assessment or a C3PAO certification assessment is required. Level 3 is rare: it sits on top of Level 2 (C3PAO) and is only required where DoD has decided the information needs protection against advanced persistent threats. The rest of this page explains how to confirm each step and what each answer costs you in effort.

Side-by-side comparison

DimensionLevel 1 (Self)Level 2 (Self or C3PAO)Level 3 (DIBCAC)
TriggerFederal contract information (FCI)Controlled unclassified information (CUI)CUI the program office designates for Level 3
Control set (32 CFR 170.14)15 requirements, FAR 52.204-21(b)(1)(i) to (xv)Identical to NIST SP 800-171 Rev. 2 (110 requirements)24 requirements selected from NIST SP 800-172 (Feb 2021), with DoD-set parameters, on top of Level 2
Assessed byThe contractorThe contractor (Self) or an authorised C3PAODCMA DIBCAC
PrerequisiteNoneNone (Level 2 Self also satisfies Level 1 for the same scope, 170.16)Final Level 2 (C3PAO) on the Level 3 scope (170.18)
FrequencyAnnual assessment and affirmationEvery three years, affirmation annuallyEvery three years, with a new Level 2 (C3PAO), affirmation annually
POA&M (170.21)Not permitted at any timeScore at least 0.8 of maximum; only 1-point items, plus SC.L2-3.13.11 where encryption is not FIPS-validated; six requirements excludedScore at least 0.8 of maximum; seven requirements excluded
Status at award (204.7502)FinalConditional (up to 180 days) or FinalConditional (up to 180 days) or Final
Results recordedSPRSSPRS (Self) or CMMC eMASS then SPRS (C3PAO)CMMC eMASS then SPRS
Evidence retentionSix years from the CMMC Status Date

Step 1: identify the information (FCI or CUI)

FCI, as DFARS 252.204-7021 defines it, is information not intended for public release that is provided by or generated for the Government under a contract. It excludes information the Government makes public and simple transactional information such as that needed to process payments. CUI is information the Government creates or possesses, or that an entity creates for the Government, that a law, regulation or Government-wide policy requires to be safeguarded or disseminated under controls (32 CFR 2002.4(h)). In defence contracts CUI usually arrives as covered defense information under DFARS 252.204-7012, which already requires NIST SP 800-171 and 72-hour incident reporting regardless of CMMC.

  • Look for markings: CUI banners, controlled technical information, export-controlled drawings and contract data requirements that call for marking. Unmarked information you believe is CUI is a question for the contracting officer, in writing. The CUI Guide explains categories and marking.
  • Look at what you generate, not only what you receive: test reports, derived drawings and engineering change data created under the contract can be CUI even when the starting package was not.
  • Check the 7012 clause: if DFARS 252.204-7012 is in the contract and covered defense information flows, Level 2 obligations exist in substance whatever the CMMC phase.

Step 2: read the clause and the level in the solicitation

Under DFARS 204.7503(a) the contracting officer includes the CMMC level required by the program office or requiring activity, and DFARS 252.204-7021 lists the four possible statuses: Level 1 (Self), Level 2 (Self), Level 2 (C3PAO) and Level 3 (DIBCAC). Provision 252.204-7025 accompanies the clause in solicitations. The clause is not used in solicitations solely for commercially available off-the-shelf (COTS) items.

What you find in the solicitationWhat it meansNext action
252.204-7021 with Level 1 (Self)FCI only; Final status needed before awardComplete all 15 requirements, post in SPRS, affirm
252.204-7021 with Level 2 (Self)CUI; self-assessment against 110 requirementsSelf-assess with SP 800-171A, post score and affirmation; a qualifying POA&M gives Conditional status
252.204-7021 with Level 2 (C3PAO)CUI; third-party certificationBook a C3PAO early; prepare SSP and evidence to the rule
252.204-7021 with Level 3 (DIBCAC)CUI on a designated programmeConfirm Final Level 2 (C3PAO) on the scope first, then contact DIBCAC
7012 but no 7021No CMMC status required by this contract, but SP 800-171 and 7019/7020 SPRS duties applyKeep a current SPRS score; the clause may appear in later contracts

Phase-in matters. DFARS 204.7504 says that through 9 November 2028 the clause is used when the program office determines a specific level is required, and from 10 November 2028 whenever the contractor must use its systems to process, store or transmit FCI or CUI. The DoD CIO page states that Phase II, scheduled for 10 November 2026, was suspended on 13 July 2026 and a reform task force set up; it says the programme "is paused in Phase 1 and may only require self-assessments at two levels". The C3PAO and DIBCAC provisions remain in 32 CFR 170.17 and 170.18, so the rule text still defines them.

Step 3: confirm the assessment route and who signs

Each route has a different threat model behind it, which explains the jump in rigour.

Level 1 (Self)

  • Threat model: opportunistic compromise of small-business systems holding contract data: phishing, default credentials, unpatched internet-facing services.
  • Architecture in words: the systems, people and facilities that touch FCI, often a business email tenant, a file share and a few laptops.
  • Controls: identification and authentication, access limits, media sanitisation, physical access, boundary protection and malicious code protection, from FAR 52.204-21.
  • Failure mode: scoring any requirement NOT MET; with no POA&M permitted, a single gap means no Final status and no award. The CMMC Level 1 Self-Assessment Guide walks the 15 requirements.

Level 2 (Self or C3PAO)

  • Threat model: targeted theft of CUI by capable actors, including credential theft and lateral movement through managed service providers.
  • Architecture in words: the CUI enclave or whole environment, plus Security Protection Assets such as the identity provider, SIEM and endpoint tooling, and any cloud offering, which must be FedRAMP Moderate or equivalent (32 CFR 170.16).
  • Controls: the 110 SP 800-171 Rev. 2 requirements, scored 5, 3 or 1 points each; MFA (IA.L2-3.5.3) and FIPS-validated encryption (SC.L2-3.13.11) carry partial credit rules.
  • Failure mode: no current SSP (CA.L2-3.12.4), which cannot go on a POA&M; or a POA&M not closed within 180 days, after which the Conditional status expires. See the CMMC 2.0 Level 2 Assessment Guide.

Level 3 (DIBCAC)

  • Threat model: advanced persistent threats with time and resources to dwell in a network and reach programme data.
  • Architecture in words: the Level 2 scope or a subset of it, with Level 3 requirements applying to every asset that handles CUI in that scope. 32 CFR 170.18 requires the Level 3 scope to be "equal to, or a subset of" the Final Level 2 (C3PAO) scope.
  • Controls: 24 enhanced requirements with DoD parameters, for example IR.L3-3.6.1e a security operations centre that "operates 24/7, with allowance for remote/on-call staff", IR.L3-3.6.2e an incident response team deployable "within 24 hours", CA.L3-3.12.1e penetration testing "at least annually or when significant security changes are made", CM.L3-3.4.3e an automated, current component inventory and RA.L3-3.11.2e ongoing threat hunting. The NIST SP 800-172 Rev 3 Guide covers the source catalogue.
  • Failure mode: assuming a POA&M will absorb the hard items. The seven excluded requirements are the SOC, the incident response team, threat-informed risk assessment, supply chain risk response and plan, security solution rationale and specialised asset security.

POA&M rules compared

Rule (32 CFR 170.21)Level 1Level 2Level 3
POA&M allowedNo, at any timeYes, for Conditional Level 2 (Self) or (C3PAO)Yes, for Conditional Level 3 (DIBCAC)
Minimum scoreAll requirements METScore divided by total requirements at least 0.8 (88 of 110)Score divided by total Level 3 requirements at least 0.8
Point-value limitNot applicableNo item above 1 point, except SC.L2-3.13.11 where encryption is used but not FIPS-validatedNo point limit stated; exclusion list applies
Never on a POA&MNot applicableAC.L2-3.1.20, AC.L2-3.1.22, CA.L2-3.12.4, PE.L2-3.10.3, PE.L2-3.10.4, PE.L2-3.10.5IR.L3-3.6.1e, IR.L3-3.6.2e, RA.L3-3.11.1e, RA.L3-3.11.4e, RA.L3-3.11.6e, RA.L3-3.11.7e, SI.L3-3.14.3e
CloseoutNot applicableWithin 180 days, by the contractor (Self) or a C3PAOWithin 180 days, by DCMA DIBCAC

Cost and timeline drivers

DoD's final rule (effective 16 December 2024) estimated cost for assessment, preparation and affirmation, not for implementing the requirements, at Levels 1 and 2, because those requirements already existed under FAR 52.204-21 and DFARS 252.204-7012. For Level 3 the estimates do include implementation, because the requirements are new, and the rule notes that Level 3 assessments by DoD assessors are performed free of cost. C3PAO prices are set by the market. In practice the cost drivers are the same at every level, but they scale differently.

DriverLevel 1Level 2Level 3
Scope sizeSmall: FCI assets onlyLargest lever: an enclave versus the whole company; see the CMMC Scoping GuideEqual to or smaller than Level 2
DocumentationEvidence per requirement, affirmationSSP, policies, operational plans of action, customer responsibility matricesAll of Level 2 plus Level 3 parameter evidence
AssessorInternal effortInternal effort (Self) or C3PAO fees and scheduling (C3PAO)C3PAO for Level 2 plus DIBCAC scheduling
Standing operationsAnnual reassessmentAnnual affirmation, triennial reassessment, POA&M closeout24/7 SOC, 24-hour response team, annual penetration testing
Lead timeWeeks for most small suppliersMonths, driven by remediation and assessor availabilitySequential: Final Level 2 (C3PAO) first, then DIBCAC

Lead times above are planning guidance from programme structure, not DoD figures. Every route carries the same six-year evidence retention, so build an evidence pack you can produce years later.

Subcontractors and flow-down

32 CFR 170.23 sets the minimum level a prime flows down. If only FCI flows to the subcontractor, Level 1 (Self) is required. If CUI flows and the prime needs Level 2 (C3PAO), the subcontractor needs at least Level 2 (C3PAO). If the prime needs Level 3 (DIBCAC) and CUI flows, the subcontractor minimum is Level 2 (C3PAO), not Level 3. DFARS 252.204-7021(f) requires the clause in subcontracts, including commercial products and services, whenever FCI or CUI will be processed, except for COTS items, and the prime must confirm the subcontractor's current status before award.

  • For primes: decide what information each supplier truly needs. Sending CUI where FCI would do raises the supplier to Level 2.
  • For subcontractors: ask the prime in writing what will flow to you and at which level, and keep the answer with your assessment evidence.
  • For service providers: an MSP that manages in-scope assets is assessed inside the customer's scope at Level 2 and above; choosing one is covered in the CMMC C3PAO and RPO Selection guide.

Decision checklist and worked scenarios

  1. List contracts and bids and record for each whether 52.204-21, 252.204-7012, 252.204-7021 and 252.204-7025 appear, with the level stated.
  2. Map information types per contract: FCI only, CUI received, CUI generated.
  3. Take the highest level required across contracts for each environment, because one system can only hold one status per scope.
  4. Decide scope: one environment for everything, or a CUI enclave with the rest of the business at Level 1.
  5. Check the route: Self or C3PAO at Level 2; for Level 3, schedule Level 2 (C3PAO) first.
  6. Name the Affirming Official and set the annual affirmation date for each CMMC UID.
  • Scenario A, machine shop: 40 staff, builds parts to a drawing marked as controlled technical information. The drawing is CUI, so the floor is Level 2 even though the shop sees itself as small. A contained enclave (a dedicated workstation group and a FedRAMP Moderate file service) keeps the Level 2 scope small; the office network stays at Level 1 for FCI such as delivery schedules.
  • Scenario B, facilities services: receives work orders and site access lists, no markings, no 7012 clause, solicitation states Level 1 (Self). Level 1 applies; the work is getting all 15 requirements to MET before award, since no POA&M is allowed.
  • Scenario C, systems integrator on a designated programme: solicitation states Level 3 (DIBCAC). The plan is Level 2 (C3PAO) on the programme enclave, then Level 3 on that enclave or a subset, with the SOC and incident response team running before DIBCAC arrives, because neither can sit on a POA&M. Its subcontractors receiving CUI need Level 2 (C3PAO), not Level 3.

Where identity fits

Every level starts with identifying and authenticating users, the processes acting for them and devices, and at Level 2 the identity provider and privileged access tooling are Security Protection Assets inside scope. Service accounts, API keys and automation identities that touch FCI or CUI need an owner, an authentication method and logs that attribute their actions, or they fail objectives human accounts pass. The NIST SP 800-171 and CMMC 2.0 Guide covers how this maps across the families.

Framework mapping and metrics

Activity on this pageNIST CSF 2.0NIST SP 800-53 Rev. 5
Read clauses and record the required level per contractGV.OC-03CA-2 (control assessments)
Identify FCI and CUI held and generatedID.AM-07Not mapped
Flow requirements down and verify supplier statusGV.SC-05, GV.SC-07SR-6 (supplier assessments and reviews)

Metrics that show the decision process is working:

  • Percentage of active contracts with the required CMMC level recorded and matched to an assessed scope.
  • Days to the next affirmation for each CMMC UID (alert at 60 days).
  • Open POA&M items and days remaining in each 180-day window.
  • Percentage of subcontractors receiving FCI or CUI with a verified current status before award.
  • Number of information flows to suppliers that were reduced from CUI to FCI after review.

Common failure patterns

  • Choosing a level from company size: CMMC has no small-business level; a 10-person firm holding CUI is at Level 2.
  • Planning a Level 1 POA&M: none is permitted, so Level 1 gaps must be fixed before the self-assessment is posted.
  • Treating the pause as a holiday: DFARS 252.204-7012 and the SPRS duties in 7019 and 7020 continue, and the DoD CIO says enforcement continues through self-assessments and select government-led assessments. DIBCAC findings override an existing status (170.16).
  • Over-scoping CUI to suppliers: primes that push CUI to every subcontractor force Level 2 across the supply chain.
  • Starting Level 3 before Level 2 is Final: DIBCAC validates the Final Level 2 (C3PAO) status before scheduling.
  • Signing the affirmation without evidence: the affirmation is a statement to the Government, and the evidence behind it must be kept for six years.

Practitioner checklist

  • Build a contract register showing clauses present and the CMMC level stated in each.
  • Classify information per contract as FCI, CUI received or CUI generated, and confirm doubtful cases with the contracting officer in writing.
  • Pick the highest required level per environment and decide on enclave or whole-company scope.
  • For Level 2, confirm from the solicitation whether Self or C3PAO is required before booking an assessor.
  • For Level 3, plan Level 2 (C3PAO) first and stand up the SOC and response team before DIBCAC.
  • Track POA&M items against the 0.8 score floor, the excluded lists and the 180-day closeout.
  • Record CMMC UIDs, SPRS entries and affirmation dates; name the Affirming Official.
  • Verify subcontractor status against 170.23 before every award that flows FCI or CUI.
  • Recheck the DoD CIO page each quarter while the review is open.

Standards and references

This guide summarises the CMMC programme rules and DFARS clauses as published on 14 November 2026 and is not legal advice. Related NHI Mgmt Group resources: NIST SP 800-171 and CMMC 2.0 Guide · CMMC Level 1 Self-Assessment Guide · CMMC 2.0 Level 2 Assessment Guide · CMMC Scoping Guide · DFARS 252.204-7012 Guide

PDF for subscribers

Take this guide with you

Every section, table and checklist in one PDF, with links to the sources and related guides. Subscribe to our weekly NHI & AI Identity Journal and we’ll email you a download link.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Researched and written by the NHI Mgmt Group editorial team using AI tools, under the editorial direction of Lalit Choda. Facts are drawn from the sources listed on this page and checked by our automated quality process. Last updated 14 November 2026. Spotted an error? Use our contact page.
NHI Mgmt Group, the independent authority on Non-Human Identity, IAM and Agentic AI security. nhimg.org

PDF Downloads for Newsletter Subscribers

Get the guide

Enter your details and we’ll email you a download link.

The full guide is free to read online. The PDF is a thank you for subscribing.

Fill in all fields marked * and tick the PDF box to continue.