November 10th, 2026 was the day CMMC Phase 2 was scheduled to take effect. Third-party C3PAO certification would have become a condition of award for most Department of War contracts involving Controlled Unclassified Information. The suspension announced on July 13th, 2026 and carried into Class Deviation 2026-O0025 Revision 3 on September 3rd made that transition into a non-event. The date passed. Nothing changed at the Department.

For an 8(a) small disadvantaged business that is itself a Prime contractor, that non-event raises a different question than it does for a standard defense Prime. The Department's rationale for the suspension cited the specific burden of CMMC compliance on small and 8(a) businesses. In that sense, the 8(a) Prime is the beneficiary of the pause. At the same time, the 8(a) Prime is a Prime, which means it carries Prime-level flow-down obligations the Department's action did not touch, and it carries the Affirming Official exposure that every other Prime carries on its own SPRS score.

Both sides of the position are live at the same time. The 8(a) Prime that treats the non-event as pure relief is missing a specific decision that is now worth making. The 8(a) Prime that ignores the small-business commercial angle is leaving leverage on the table. This article addresses what the reader should actually do with the day that did not arrive.

The One-Sentence Frame

November 10th arrived as a non-event for the Department. For an 8(a) Prime, the day exposed three obligations that still bind, one asymmetry that still cuts, and one strategic decision that is now worth making deliberately.

Three Obligations the Non-Event Did Not Touch

The Department's suspension changed one specific thing: the C3PAO certification mandate scheduled for November 10th is paused. The suspension did not modify three obligations that 8(a) Primes already carried.

Obligation Source Status after November 10th
Adequate security and 72-hour cyber incident reporting DFARS 252.204-7012 Fully in force. Unchanged by the pause.
Implementation of 110 security requirements NIST SP 800-171 Revision 2 Fully in force. Unchanged by the pause.
Flow-down of cybersecurity requirements to subcontractors handling FCI or CUI DFARS 252.204-7012 (c) and (m), subcontract terms Fully in force. The Prime's responsibility to verify subcontractor compliance is unchanged.

Three features of the obligation set deserve specific attention for 8(a) Primes.

  1. The SPRS score is still required for the Prime's own award eligibility. A current self-assessment score and an annual affirmation signed by a senior official remain conditions of award. The 8(a) Prime's sole-source contract eligibility under the 8(a) Program depends on the Prime being award-eligible in the first place, which includes the SPRS score status.
  2. The Affirming Official exposure is identical to any other Prime. The False Claims Act reaches statements made in reckless disregard for the truth, which the pause does not relax. An 8(a) Prime's Affirming Official carries the same personal exposure as the Affirming Official at any larger Prime.
  3. Flow-down to subcontractors was never under the Department's control. The suspension addressed what the Department requires in solicitations. It did not address what a Prime has flowed down to its own subcontractors, because the Department was not a party to those subcontracts. This is the asymmetry the next section covers.

The Flow-Down Asymmetry Nobody Is Talking About

This is the specific point most 8(a) Primes have not thought through, and it is the one with the clearest action implication.

When a Prime contractor signed a subcontract in 2025 or early 2026 that flowed down CMMC Level 2* requirements to its subcontractors, that flow-down became a term of the subcontract. The Prime took on the verification obligation; the subcontractor took on the compliance obligation. Both obligations sit inside the subcontract, between the two private parties.

The Department's suspension of Phase 2 did not modify that subcontract. The Department was not a party to it. The Department cannot unilaterally change the terms of a private subcontract any more than it can unilaterally change the terms of a vendor agreement between two commercial companies. What changed is the government-side mandate; the subcontract-side flow-down remained exactly as the Prime wrote it.

That leaves the 8(a) Prime holding a specific decision: whether to modify its own subcontracts to relieve subcontractors of a flow-down requirement the government is no longer enforcing.

The Decision Structure

  • Keep the flow-down as written: the subcontract remains enforceable, the subcontractor continues to invest in readiness, and the Prime's supply chain is positioned for whatever the Department does next: a narrower-population restart, a different structure, or a continued pause.
  • Modify the subcontract to remove the flow-down: the subcontractor is relieved of the obligation, the Prime surfaces that decision formally, and the subcontract is realigned to the current government position.
  • Doing nothing: the flow-down remains enforceable because it is written into the subcontract. The subcontractor may or may not know that, which produces its own set of problems.

For an 8(a) Prime, the second option is often attractive because it reduces cost pressure on the Prime's own subcontractor base, many of whom are themselves small businesses. It is also the option that carries the most strategic consideration, because the Prime has to decide whether to give up the verification posture that the flow-down produced.

The specific clause-level mechanics of modification under the deviation are covered in our article on what Contracting Officers are actually doing with Rev 3. The Prime-to-subcontractor relationship is procedurally simpler than the government-to-Prime relationship, but the strategic decision is harder because the Prime is choosing it voluntarily rather than executing a government directive.

The Commercial Angle 8(a) Primes Are Underusing

The Department's suspension rationale specifically cited cost burden on small and 8(a) businesses. CIO statements to that effect are public record. That rationale has a specific commercial implication for 8(a) Primes that most are not using.

Three commercial positions become more valuable during the pause for an 8(a) Prime with real readiness investment behind it.

  1. Teaming with larger Primes seeking 8(a) subcontracting goals. Larger Primes continue to need subcontracting relationships that meet their small business and 8(a) goals. An 8(a) Prime that can credibly describe its NIST SP 800-171 Revision 2 implementation, documented SPRS score, and current CUI handling posture is more valuable as a teaming partner than one whose compliance story is “the Department paused so we paused.” The suspension did not change what larger Primes expect from their 8(a) teaming partners.
  2. Sole-source opportunities that were sitting in the pipeline. The 8(a) program allows federal agencies to award sole-source contracts to 8(a) firms up to $4.5 million for services. That procurement mechanism did not pause. An 8(a) Prime with documented readiness is positioned to execute sole-source awards faster than competitors still trying to decide whether to invest. The compliance posture is a differentiator in the sole-source conversation, not a barrier.
  3. Growing the pipeline while competitors wait. Industry commentary across the pause has described a specific pattern: contractors that paused their readiness work in July are now behind the ones that continued. For an 8(a) Prime weighing resource allocation, the readiness track is the more defensible investment because every plausible outcome of the Reform Task Force process preserves NIST SP 800-171 Revision 2 as the baseline.

What to Do in the Next 90 Days

Four actions align the 8(a) Prime's posture with the position the day actually produced. None depend on a Task Force report or a restart announcement.

  1. Make the flow-down decision deliberately. Pull every active subcontract that contains CMMC flow-down language. For each, decide whether to keep the flow-down, modify it, or coordinate the subcontractor's investment pace with the government's current position. Document the reasoning. A subcontract that was flowed down in 2025 and has not been revisited since July 2026 is being managed by default rather than by decision.
  2. Verify the SPRS score matches the actual environment. The Affirming Official exposure continues during the pause. An 8(a) Prime relying on the suspension to justify slower reconciliation of its posted score and its actual control implementation is accepting the self-assessment liability the pause concentrates on the signature. Verifying accuracy now is substantially cheaper than defending a gap later.
  3. Document readiness as a teaming and sole-source asset. Produce a one-page readiness summary for teaming conversations with larger Primes and for sole-source award discussions. The summary should describe environment scope, SPRS score status, NIST SP 800-171 Revision 2 implementation evidence, and any Joint Surveillance Voluntary Assessment status. This becomes a commercial document, not just a compliance artifact.
  4. Confirm each contract's clause set. Legacy and renumbered DFARS citations are both in circulation because the deviation did not amend the codified text. Which numbers appear in a given contract determines the specific obligations and the appropriate internal references. For an 8(a) Prime with contracts awarded at different times, the portfolio may carry multiple clause sets simultaneously.

The underlying work that supports each of these is covered across our CMMC Level 2* readiness practice. An 8(a) Prime working on these items in the next 90 days is preparing for whatever outcome the Department produces, while maintaining the commercial position the pause specifically rewards.

How KSG Approaches This Period

Kaizen Solutions Group has secured federal and state government systems since 2016. We are an SBA 8(a)-certified small disadvantaged business, ISO 27001:2022, ISO 9001:2015 and ISO 20000-1:2018 certified, and we hold GSA HACS designations across all five categories: Risk and Vulnerability Assessment, High Value Asset assessment, Penetration Testing, Incident Response, and Cyber Hunt.

As an 8(a) small disadvantaged business, we operate in the same classification as the readers of this article. The decisions described here are decisions we have thought about from both sides: as a Prime that carries flow-down obligations to its own subcontractors, and as an 8(a) firm that is subject to flow-down from larger Primes. Our position is that the Department's pause created options rather than relief, and that the 8(a) Primes who treat the next 90 days deliberately are positioned better than those who treat the pause as the end of the question.

Where We Typically Begin

  • Subcontract flow-down review: We catalog every active subcontract containing CMMC flow-down language, assess the strategic implications of keeping or modifying the flow-down, and document the resulting decision with the reasoning behind it.
  • SPRS score reconciliation and gap assessment: We assess the environment against all 110 NIST SP 800-171 controls and reconcile the result against the posted score, so the Affirming Official has a defensible basis for the signature.
  • CUI identification and boundary scoping: We map where FCI and CUI are processed, stored and transmitted, including information generated during performance, so the level determination reflects actual information flow rather than marking alone.
  • System Security Plan and POA&M development: We produce documentation that describes the environment, the boundary and the deficiencies accurately enough to hold up under government-led review, and reusable enough to support teaming and sole-source conversations.
  • Risk Management and POA&M analytics: We deliver continuous monitoring, vulnerability and patch management, and Key Risk Indicator and Key Performance Indicator dashboards.
  • Security operations and remediation delivery: We support Security Operations Center monitoring, SIEM and SOAR, Identity and Access Management, endpoint detection and response, and DevSecOps.

A Useful Place to Begin

One question clarifies most of the strategic decision facing an 8(a) Prime today. If a larger teaming partner asked for the 8(a) Prime's current compliance posture tomorrow, with specific reference to NIST SP 800-171 Revision 2 implementation and SPRS score status, could the response be produced in writing within 48 hours?

Where the answer is no, the 8(a) Prime is carrying a teaming and sole-source disadvantage that the Department's suspension does not relieve.

Talk to our team · Download our capability statement · Explore CMMC Level 2* readiness

Frequently Asked Questions

Did November 10th 2026 matter for 8(a) Primes?

Not on the Department's side, because the July 13th suspension and the September 3rd Class Deviation 2026-O0025 Revision 3 removed the mandatory C3PAO certification that would have taken effect that day. For 8(a) Primes specifically, the date exposed three obligations that still bind, one asymmetry in flow-down to subcontractors that still cuts, and one strategic decision about subcontract modification that is now worth making deliberately.

Do 8(a) Primes still have to flow CMMC requirements down to subcontractors?

The Department's suspension did not require Primes to remove CMMC flow-downs from existing subcontracts. Where a Prime has already flowed CMMC requirements to a subcontractor, that flow-down is a term of the subcontract, which is a private agreement between the Prime and the subcontractor. The Department can direct what appears in government solicitations; it does not direct what appears in private subcontracts. The 8(a) Prime decides whether to keep the flow-down, modify it, or coordinate the subcontractor's investment pace with the current government position.

Can an 8(a) Prime remove CMMC requirements from its own subcontracts now?

Yes, through a bilateral subcontract modification between the Prime and the subcontractor. The 8(a) Prime is the party that controls that decision. Removing the flow-down relieves the subcontractor of the readiness requirement but also removes the verification posture the flow-down produced. The decision should be made deliberately, with the reasoning documented, and consistent across similar subcontracts to avoid downstream inconsistency in the supply chain.

Is the SPRS score still required for 8(a) sole-source awards?

Yes. A current self-assessment score posted in SPRS and the annual senior-official affirmation remain conditions of award eligibility. The 8(a) program's sole-source procurement mechanism requires the awardee to be award-eligible in the first place, which includes the SPRS score status. An 8(a) Prime assuming the sole-source path bypasses the SPRS requirement is misreading the award mechanics.

What should an 8(a) Prime do in the next 90 days?

Four actions align the 8(a) Prime's posture with the position November 10th actually produced. Make the subcontract flow-down decision deliberately, with each active subcontract reviewed and the decision documented. Verify the SPRS score matches the actual environment to limit Affirming Official exposure. Produce a one-page readiness summary that supports teaming and sole-source conversations. Confirm which DFARS clause set appears in each active contract, because legacy and renumbered citations are both in circulation.

Does the CMMC pause relieve DFARS 252.204-7012 obligations?

No. DFARS 252.204-7012 continues to require adequate security on covered contractor information systems, implementation of NIST SP 800-171 Revision 2, and cyber incident reporting within 72 hours. The clause includes flow-down terms that continue to apply to subcontracts involving covered defense information. The pause addressed the CMMC assessment mandate, not the underlying security obligation.

How does November 10th affect existing teaming agreements?

Existing teaming agreements that include CMMC-related commitments continue to operate under their original terms until the parties modify them. A teaming agreement signed in early 2026 that assumed Phase 2 would take effect in November is still enforceable between the parties according to its written terms. Whether the parties should modify it depends on the specific language and the commercial relationship. The suspension gave the parties a reason to revisit the agreement; it did not modify the agreement itself.

Is readiness still worth investing in for an 8(a) Prime?

Yes, for three reasons. The commercial case is that larger Primes continue to value 8(a) teaming partners with credible compliance postures, and documented readiness remains a differentiator in sole-source award conversations. The regulatory case is that every plausible outcome of the Reform Task Force process preserves NIST SP 800-171 Revision 2 as the baseline, so readiness work applies under whatever structure emerges. The exposure case is that the Affirming Official liability runs through the self-assessment attestation regardless of what the Department does next.