CMMC outlook 2027: paused certification and the assessor bottleneck

CMMC's rules are final but its third-party phase is suspended, so contractors self-assess against NIST SP 800-171 while the Department reviews a program it says lacked assessment capacity.

The question and the short answer

The Cybersecurity Maturity Model Certification (CMMC) program decides how a defense contractor proves that it protects federal contract information (FCI) and controlled unclassified information (CUI) on its own systems. Its rules are final and unchanged, but the step that was meant to matter most in 2026, third-party certification as a condition of award, is suspended [1] [3]. Through 2027 the duty stays where it was before CMMC: implement NIST SP 800-171 Rev 2 under DFARS 252.204-7012, self-assess, post the results in the Supplier Performance Risk System (SPRS) and have a senior official affirm them [2] [4]. The Department's own memo names a shortage of third-party assessment capacity as one reason for the pause [1].

All statuses below are as checked on November 16, 2026. The Department of War's CIO site refused our automated requests, so its memos and program page are cited from Internet Archive copies, with the capture dates given in the sources. This piece describes rules and official documents; it is not legal advice, and the terms that bind a given contract are the ones in its solicitation.

What the rules still say

The program rule at 32 CFR part 170 was published on October 15, 2024 and took effect on December 16, 2024 [7]. The eCFR version history lists no amendment to part 170 since that date [6]. The DFARS acquisition rule, DFARS Case 2019-D041, was published on September 10, 2025 and took effect on November 10, 2025 [8], which is when Phase 1 began [5]. We found no CMMC rule or proposed rule in the Federal Register after it [9].

Part 170 sets four phases, each beginning one calendar year after the one before: Phase 1 with Level 1 (Self) or Level 2 (Self), Phase 2 in which the Department intends to add Level 2 (C3PAO) as a condition of award, Phase 3 in which it intends to require it for all applicable contracts and adding Level 3 (DIBCAC), and Phase 4 reaching option periods on older contracts [5]. The levels rest on 15 Level 1 requirements from FAR 52.204-21, the 110 Level 2 requirements of NIST SP 800-171 Rev 2 and 24 Level 3 requirements from NIST SP 800-172 [5].

A contractor may hold a conditional Level 2 status only if its score is at least 0.8 of the total and the open items meet the plan of action rules; the plan must be closed within 180 days or the status expires [5]. Final Level 1 (Self) is current for one year, and Final Level 2 and Level 3 for three years, each with an affirmation of continuous compliance no older than one year [4].

The suspension and what it removed

On July 13, 2026 the Department of War CIO suspended the November 2026 Phase 2 transition, held "all pending and future CMMC implementation milestones" in abeyance until further notice, and limited program managers to Level 1 or Level 2 self-assessments in procurement requests [1]. The same memo set up a CMMC Reform Task Force for a 60-day review, charged with recommending a framework that "replaces prohibitive, third-party compliance models with scalable, realistic security measures" [1]. The program page, as captured on November 10, 2026, still described the suspension and the review and named Phase 2's original date as November 10, 2026 [3].

The implementing memo from the Under Secretary of War for Acquisition and Sustainment, also of July 13, 2026, says program managers may not designate Level 2 (C3PAO) or Level 3 (DIBCAC) during the suspension, must amend active solicitations that carry them, and must have them removed from existing contracts before the next option or at the next administrative modification [2]. It also says no CMMC waivers will be granted during the review and that further guidance will follow at the end of the 60-day review [2]. Class Deviation 2026-O0025, Revision 3, signed on September 3, 2026, carries those instructions into contracting rules [4].

The deviation leaves two dates in the clause prescription. Until November 9, 2028, the CMMC clause goes into a contract only when the program office decides a specific level is needed; on or after November 10, 2028, it goes in whenever the contractor will process, store or transmit FCI or CUI [4]. We could not find a public report from the Task Force, so this piece gives no account of its recommendations.

What a contractor owes through 2027

  • NIST SP 800-171 Rev 2 on every covered contractor information system, under DFARS 252.204-7012, which both July memos say remains in effect [1] [2].
  • Cyber incident reports to DoD within 72 hours of discovery, a DoD-approved medium assurance certificate to file them, and images of affected systems kept for at least 90 days [4].
  • Cloud providers that hold covered defense information must meet requirements equivalent to the FedRAMP Moderate baseline [4] [5].
  • Where a contract carries the CMMC clause: a current status in SPRS for each system, a CMMC unique identifier for each, an annual affirmation by the affirming official, and the right level flowed down to subcontractors before award [4].
  • Access for a Medium or High NIST SP 800-171 DoD Assessment by government assessors, whose results, when the Defense Contract Management Agency conducts the assessment, take precedence over any other assessment [4].

Moraph's view

Moraph's view: the suspension changes who checks the work, not the work. A Level 2 self-assessment score is a representation to the government, signed by a senior official, and the July memo promises "select government-led assessments" during the pause. Contractors that cut their 800-171 budgets for 2027 are betting on the outcome of a review nobody outside the Department has seen.

Where assessment capacity runs short

The CIO's memo gives the Department's own reason for the pause: prohibitive compliance costs, severe shortages in third-party assessment capacity and complex regulatory timelines [1]. The record shows four places where capacity is set.

Assessor organizations. In the 2024 rule the Department estimated that 8,350 medium and large entities would need Level 2 certification assessments, and planned on 135 C3PAO-led assessments in the first year, 673 in the second, 2,252 in the third and 4,452 in the fourth [7]. GAO reported that as of December 2025 The Cyber AB had authorized 92 C3PAOs, 14 more had passed a DIBCAC assessment without yet being authorized and 14 were waiting for one [10]. On July 15, 2026 The Cyber AB put the count at 110 authorized C3PAOs and said nearly 2,000 contractors held a Final Level 2 certification [11].

Certified assessors. GAO reported 633 CMMC Certified Assessors as of December 2025, 290 of them Lead assessors [10]; The Cyber AB reported more than 1,000 in July 2026 [11]. Part 170 requires every assessment team to include a Lead assessor and at least one other certified assessor, with quality assurance done by a further certified assessor who is not on the team [5]. A Lead assessor needs at least 5 years of cybersecurity experience, 5 of management and 3 of assessment or audit [5].

Government gates. Each C3PAO must pass its own Level 2 assessment by DIBCAC and a foreign ownership review, and every person in its assessment process must complete a Tier 3 background investigation [5] [10]. C3PAOs must also reach ISO/IEC 17020 compliance within 27 months of authorization [5]. In its response to the Department's request for information, The Cyber AB asked for the minimum of three certified assessors on each assessment to be cut to two, and for the Tier 3 background investigation requirement for assessors to be dropped [12].

Standards in motion. GAO noted that NIST issued Revision 3 of SP 800-171 in May 2024 while CMMC still rests on Revision 2, and that The Cyber AB and its training arm said updating training and exams could take up to a year after the rules change [10]. The revised 7012 clause in the September 2026 deviation still names Revision 2 [4].

Moraph's view

Moraph's view: at 110 C3PAOs, the Department's estimate of 8,350 entities works out to about 76 Level 2 certifications per organization, before renewals every three years. The tighter limit is people rather than firms: assessors who clear a Tier 3 investigation and meet the Lead qualifications, and DIBCAC's queue for new C3PAOs. The pause relieves that pressure for now but does not add capacity, and certifications had already run well ahead of the Department's first-year estimate of 135 before the pause. When third-party assessment returns, expect it to start with a narrower population than Phase 2 planned, and expect the first months to be a scramble for assessor time.

What to watch in 2027

  • The guidance the implementing memo promised at the end of the 60-day review, and any revision of the class deviation that follows it [2] [4].
  • A proposed or interim rule amending 32 CFR part 170, which would be the first change to the text since December 16, 2024 [6].
  • Whether DoD moves the 7012 clause from Revision 2 to Revision 3 of NIST SP 800-171 [4] [10].
  • Whether the November 10, 2028 date in the clause prescription survives the review [4].

For the levels and how they fit together, see the CMMC levels explainer; for the procurement side, the federal cloud and cyber procurement outlook.

What this means for you

  • Prime contractors: Keep NIST SP 800-171 Rev 2 implementation, SPRS scores and affirmations current, and check every amended solicitation: CMMC third-party requirements are to be removed, but the 7012 clause and its 72-hour reporting stay [2] [4]. Primes still flow the required level down to subcontractors before award where the CMMC clause applies [4].
  • Small subcontractors: A Level 2 (Self) assessment posted in SPRS is the instrument most contracts can ask for during the suspension [2]. A conditional status needs a score of at least 0.8 of the total and a plan of action closed within 180 days [5].
  • C3PAOs and assessors: Third-party Level 2 assessments remain available to contractors that want them, according to The Cyber AB [11], but DoD solicitations may not require them while the suspension lasts [2]. The part 170 rules on teams, Tier 3 investigations and ISO/IEC 17020 still apply [5].
  • Cloud and managed service providers: Contractors must still require FedRAMP Moderate or equivalent security of any cloud provider holding covered defense information [4], so providers serving the defense industrial base should expect those questions to continue.

Moraph predictions

Every prediction is Moraph's view, not a fact. Each has a date, a confidence level (70% means we expect to be wrong about three times in ten) and a test anyone can apply. We score them on this page when the date comes and never remove one. How we make and score predictions.

  1. P1 By Confidence 70% Open

    Through June 30, 2027, DoD solicitations still may not require CMMC Level 2 (C3PAO) as a condition of award: no memo, class deviation or rule published before that date lifts the July 13, 2026 restriction.

    How we will check: On June 30, 2027, the Department of War CIO's CMMC page and the DFARS class deviations list show no document dated before that day that again permits program offices to designate Level 2 (C3PAO) in solicitations, and no Federal Register rule does so.

    Basis: The suspension holds all milestones in abeyance until further notice [1], no waivers are granted during the review [2], the September 2026 deviation restated the restriction [4], and the program page as captured on November 10, 2026 still described the suspension [3].

  2. P2 By Confidence 55% Open

    DoD publishes in the Federal Register a proposed, interim or final rule amending 32 CFR part 170.

    How we will check: A Federal Register document published on or before December 31, 2027 amends or proposes to amend 32 CFR part 170.

    Basis: Part 170 has not been amended since December 16, 2024 [6], while the July 2026 memo directs a redesign that replaces third-party compliance models [1] and contracting changes have so far been made by class deviation [4]; no CMMC rulemaking had appeared by November 16, 2026 [9].

  3. P3 By Confidence 80% Open

    DFARS 252.204-7012, as written in the DFARS or the latest class deviation, still names NIST SP 800-171 Revision 2 as the required standard.

    How we will check: On December 31, 2027, the text of DFARS 252.204-7012 in the eCFR, or in the latest DFARS class deviation that revises it, cites Revision 2 of NIST SP 800-171 in paragraph (b)(2)(i).

    Basis: The clause revised in June 2026 names Revision 2 [4], the July 2026 memo sets Revision 2 as the baseline during the suspension [1], and GAO reported that DoD had not yet updated CMMC for Revision 3 and that training updates could take up to a year after rules change [10].

  4. P4 By Confidence 70% Open

    The number of authorized or accredited C3PAOs stays below 150.

    How we will check: On December 31, 2027, the C3PAO listing in The Cyber AB's CMMC Marketplace, or the latest count The Cyber AB or DoD publishes, shows fewer than 150 authorized or accredited C3PAOs.

    Basis: GAO reported 92 authorized C3PAOs with 28 more in the pipeline in December 2025 [10]; The Cyber AB reported 110 in July 2026 [11], and with Level 2 (C3PAO) requirements suspended DoD solicitations cannot create new demand [2].

Facts on this page link to their sources. Text marked "Moraph's view", and every prediction, is our own analysis, not a fact or advice. Methodology.

Spotted an error? Tell us and we will check it and correct the piece where needed.

  • CMMC
  • 32 CFR part 170
  • DFARS 252.204-7012
  • DFARS 252.204-7021
  • NIST SP 800-171
  • C3PAO
  • SPRS
  • Defense industrial base