CMMC influencers: how primes will drive the security agenda for subcontractors

Gettyimages.com/Parradee Kietsirikul

Find opportunities — and win them.

Most prime contractors are holding subcontractors to third-party certification standards despite last July's pause, writes Dr. Thomas Graham of Redspin.

When the Department of Defense paused requirements for Cybersecurity Maturity Model Certification (CMMC) Phase 2 implementation last July, much of the industry and media conversation centered on how individual contractor organizations would respond. Phase 2 of the CMMC implementation rollout, which was originally scheduled to go into effect on Nov. 10, 2026, requires third-party certification of a defense contractor’s CMMC compliance.

The department’s 60-day review period has come and gone with no conclusion as of yet. Some defense industrial base members, especially smaller companies, have taken this as a reason to slow or stop their CMMC efforts. But recent research points to another factor they should keep in mind: the cybersecurity expectations that prime contractors running the defense supply chain have for their subcontractors.

The survey data shows that only 23.3% of primes are relaxing CMMC requirements for their subs amid the pause period. This highlights an opportunity for primes to proactively differentiate themselves within the DIB by staying ahead of security requirements. That involves guiding and communicating with their subs about meeting CMMC requirements ahead of changing government mandates and new National Institute of Standards and Technology (NIST) 800-171 Revision 3 requirements that will soon be imposed across federal agencies.

Accountability Sets the Line on Security

Most primes are sticking to the position they have held since the 48 Code of Federal Regulations (CFR) acquisition rule took effect in November 2025. That milestone allowed the Defense Department to start putting CMMC requirements into contracts. As of now, a majority of primes are still obliging third-party certification of their sub’s or vendor’s implementation of NIST SP 800-171 Revision 2.

Their position is rooted in the level of accountability a prime bears to ensure its full team follows the regulation, codified in Defense Federal Acquisition Regulations (DFARS) 7021. If something harmful happens to the government’s controlled unclassified information associated with a given contract, the prime can be held responsible for its subs’ involvement in that breach. In some cases, primes have hundreds if not thousands of subcontractor organizations, so the scope of potential liability is enormous.

Without third party certification, a prime does not have visibility or any real assurance that their subs or vendors have correctly and completely implemented the NIST standard. While DOD can check for a sub’s supplier performance risk system (SPRS) score in the CMMC Enterprise Mission Assurance Support Service (eMASS) database, where official third-party CMMC assessment results are recorded, primes do not have access to that system. The issue is somewhat moot, since in the majority of cases, the scores reported to SPRS are from self-assessments that have consistently been shown to provide inaccurate compliance metrics, and which the DoD itself rates as low-confidence.

The Buck Stops with Primes

The research also showed that 39.5% of primes have not yet made a decision about whether or not to change their CMMC expectations for their subs because of the DOD pause. As those undecideds move forward with making their decision, there are important issues to keep in mind.

As already noted, it is their responsibility to ensure NIST 800-171 compliance by their entire team. That implementation requirement has not been paused or terminated. In fact, the requirement to protect government controlled unclassified information (CUI) is about to be enforced beyond the DoD and across all federal agencies, given an impending federal CUI rule that would mandate compliance for the executive branch.

While to date the DIB has been focusing on NIST SP 800-171 Revision 2 which CMMC requires, the proposed federal CUI rule will require Revision 3. That later version has prescriptive minimum requirements, known as organizationally defined parameters (ODPs), that must be in place in order to meet implementation. It is inevitable that at some point the DoD will need to comply with Rev 3 as well, so meeting Rev 2 requirements first will position DIB members well for Rev 3 when it is required.

A Team Commitment

As primes evolve communications to their subs about security requirements, a few key practices will help. First, have requirements clearly included in teaming agreements and monitor team compliance. Explain how compliance and certification benefit, rather than hinder, subs. Note any additional opportunities that may require certification by a third party.

Be vocal about the CMMC decision. Explain the areas where having a third-party certification mitigates the prime’s liability and risk. Be sure to mention ancillary benefits to subs such as being able to negotiate lower insurance rates for themselves.

Finally, reinforce that NIST 800-171 implementation has been a requirement for almost a decade. It should have already been addressed by any sub that has been a part of a prime’s contract team throughout that time. If that implementation has not been done, it could open up litigation not only with the sub but also the prime as the one ultimately accountable. 

Together, primes and subs are providing the Defense Department with a team solution; that requires all team members to fulfill their roles to enable mutual opportunity and responsibility.