- Prompt injection attacks manipulate AI guardrails using natural language, exploiting the semantic gap to get models to ignore developer instructions.
- AI social engineering scales faster and lowers attacker skill barriers, enabling automated, targeted campaigns like deepfakes and credential theft.
- Primary harms include data exfiltration, unauthorized transactions, and malicious or biased outputs that damage reputation and operations.
- Defenses are immature; require layered controls: human in the loop, prompt firewalls, input sanitization, least privilege, fuzz testing, patching, and user training.
Last Updated on November 16, 2026
On July 13, 2026, the US Department of War (DoW) suspended CMMC Level 2 third-party assessments pending a 60-day review. A lot of contractors read that as relief. I read it differently.
The CMMC 2.0 program will enable the DoW to verify that a defense supplier has implemented all contractually mandated security requirements and is maintaining compliance throughout the contract period. CMMC’s focus is on protecting controlled unclassified information (CUI) and federal contract information (FCI).
Let’s be clear on what was actually suspended, because the distinction is critical. The pause hit the assessment. It did not touch the requirement, nor did it touch enforcement.
DFARS 252.204-7012 still obligates you to implement NIST SP 800-171 and to report cyber incidents within 72 hours. DFARS 252.204-7019 and 7020 still require a current NIST SP 800-171 self-assessment score posted in the Supplier Performance Risk System (SPRS), refreshed at least every three years, as a condition of award. Contracting officers still check SPRS. The Civil Division of the US Department of Justice (DoJ) is still running the Civil Cyber-Fraud Initiative it announced in October 2021. What went away is the third party who was going to corroborate your number.
The 110 controls have not moved since 2017
This is the part that gets lost around CMMC, especially with each pause. The substantive security requirement for CUI in the defense industrial base (DIB) has been the same 110 controls across 14 families since December 31, 2017. That was the compliance date set under DFARS 7012 for NIST SP 800-171. Rev 2 renumbered and clarified the standard and Rev 3 restructured it. The obligation itself has been sitting there for nearly nine years.
CMMC is not a new requirement. CMMC is a new verification mechanism the DoW bolted on after concluding that self-attestation alone was not producing implementation. Pausing the verification mechanism does not unwind the underlying control set any more than turning off a smoke detector makes a kitchen fire less likely. If you were non-conformant on July 12, you are non-conformant today. The only thing that changed is who was scheduled to notice.
If your company has been handling CUI but isn’t in compliance with NIST 800-171, you need to move quickly to close that gap or face significant repercussions.
During the pause, these baseline requirements remain in place for defense contractors:
- Implementing the controls in NIST 800-171 Rev. 2
- Documenting your NIST 800-171 Rev. 2 compliance status, including plans of action and milestones (POA&Ms) to address any compliance gaps, in a System Security Plan (SSP)
- Recording your self-attested compliance score in the Supplier Performance Risk System (SPRS), along with signed authorization by a senior leader
Your exposure lives in the attestation, not the audit
Contractors talk about CMMC risk as audit risk: the Certified Third-Party Assessment Organization (C3PAO) shows up, finds gaps, you fail, you lose the award. That is a commercial risk. It is limited and recoverable, as you can remediate and re-test.
False Claims Act (FCA) exposure is different. It attaches to the actions you have already taken. When you posted a score to SPRS and then invoiced against a contract containing a DFARS 7012 clause, you made a representation of your security posture to the government. Per section 31 U.S.C. 3729, liability turns on “knowing,” which the statute defines to include actual knowledge, deliberate ignorance, and reckless disregard. Submitting a score without evidence to validate its accuracy is arguably reckless disregard.
The penalty is harsh: triple damages plus per-claim penalties. Perhaps scarier is that a whistleblower gets 15 to 30 percent. Consider:
- Aerojet Rocketdyne settled with DoJ for $9 million in 2022. The relator, a former senior director of cybersecurity, took $2.61 million of it.
- LOGZONE, in June of this year, agreed to pay $507,144 over its self-assessed SPRS score.
Neither case involved a failed C3PAO assessment. They involved a company’s own representation about its implementation of the required NIST SP 800-171 controls.
I understand that the cost of a C3PAO assessment can be challenging for a small DIB supplier. However, it’s a five-figure number, and FCA settlements are six- and seven-figure numbers before defense costs, before suspension and debarment referral, and before the reputational hit with your primes.
Another way DIB orgs can end up in a review process leading to a false claims action is following a data breach. Per DFARS guidance, defense suppliers are required to report security incidents. So, how did that bad stuff happen if you were in compliance with NIST 800-171? Compliance doesn’t equal security, but it certainly makes a breach far less likely.
What else a C3PAO was buying you (beyond the certificate)
Set the CMMC Level 2 certificate aside for a second. The assessment produced something arguably more useful than a logo: a documented, independent record of what a qualified outside party observed about your environment on a specific date.
It’s a 3rd-party attestation. It is the difference between “our score is 105” (self-attestation) and “our score is 105, and here is evidence that a third party agrees with the score” (third party attestation).
Should the government knock on your door; a contractor who can produce independent validation is a contractor arguing about a good-faith disagreement over control interpretation. A contractor who cannot produce independent validation is a contractor arguing that they believed their own unverified number, and the only witness is the executive who attested to it. The pause removed the C3PAO’s corroboration, i.e., your protection. It did not remove the statement you are responsible to uphold.
Two things worth doing now
- Keep going. If you were mid-stream toward Level 2 certification with a C3PAO, the case for continuing is stronger now, not weaker. The legal/contractual requirement has not changed. Programs that stopped and restarted during the 2021 CMMC 1.0 to 2.0 transition lost far more than 60 days of momentum, because SSPs go stale, POA&M owners move on, and evidence collection must start over. The controls you implement during the pause are controls that are implemented when the pause lifts, and they make your current SPRS score defensible in the meantime. The certification schedule moved. The security value did not.
- Consider getting independent validation anyway. If you were not midstream, engage an appropriate qualified entity (e.g., a CMMC Registered Practitioner Organization (RPO)) to conduct an independent assessment against the 110 controls, document the evidence reviewed, and produce a written record of the basis for your score. That record provides FCA protection because:
- It creates evidence of due diligence, dated, from someone other than you.
- Reckless disregard is a much harder charge for the government to prove against a contractor who commissioned an outside review, acted on the findings, and adjusted its score accordingly.
- It gives you a defensible methodology for the score rather than a spreadsheet nobody outside your IT team has looked at.
- It surfaces the gaps while you can still fix them and update SPRS, which is a materially better posture than surfacing them in response to a subpoena.
Conducting a NIST 800-171 Rev. 2 gap assessment or CMMC 2.0 internal audit now offers several benefits to DIB orgs, including:
- Empowering you to share bona fide status and progress with your senior management and other stakeholders
- Supporting executive sign-off on your NIST 800-171 Rev. 2 compliance in SPRS
- Building a relationship with a registered practitioner organization (RPO) to help streamline your CMMC compliance process
To reduce legal risk, many companies will look to RPOs and other cybersecurity consultants to provide attestation of compliance through a CMMC internal audit or NIST 800-171 Rev. 2 gap assessment process.
What is flowdown of CMMC compliance requirements?
CMMC not only requires DoW contractors to demonstrate robust cybersecurity, but also mandates them to ensure their own suppliers comply with DoW guidelines.
Contractors that handle CUI must comply with CMMC Level 2, while contractors that handle only FCI need to achieve CMMC Level 1.
CMMC itself now mandates requirements flowdown based on the type of information shared with subcontractors and vendors.
This means that prime contractors must flow down CMMC requirements to all their subcontractors based on the type of information the subcontractors will receive from the prime:
- Subcontractors that only handle FCI need only meet CMMC Level 1 requirements.
- Subcontractors that handle CUI must meet the stringent CMMC Level 2 requirements. At CMMC Level 2, subcontractors will be held to the same assessment regime as the prime contractor (self-assessment or third-party assessment).
- Subcontractors that handle highly sensitive CUI on a contract where the prime contractor needs to meet CMMC Level 3 must meet CMMC Level 2 at a minimum.
CMMC 2.0 now also states that primes will be responsible for ensuring that subcontractors maintain up-to-date CMMC certificates or self-assessments at the appropriate level before awarding contracts. Further, contracts must clearly state CMMC requirements.
These new requirements go a long way toward improving security across the US defense industrial base (DIB). But they add significant new responsibilities and complexities to a contractor’s cybersecurity compliance program.
Who must comply with CMMC flowdown requirements?
The flowdown requirements will apply to all DoW contracts and subcontracts where the contractor will store, process, and/or transmit FCI and/or CUI on its own systems in performance of the contract or subcontract.
If contractors and their subcontractors are handling the same type of FCI and/or CUI, the same CMMC requirements will apply to both. When the contractor shares only certain less sensitive information, a lower CMMC level may apply.
For example, if your business receives both FCI and CUI but some of your vendors only receive FCI, you must flow down the CMMC Level 1 certification requirement to those vendors. But for your vendors that you share CUI with, you must flow down the CMMC Level 2 certification requirement, along with applicable DFARS requirements (e.g., DFARS 7012 or DFARS 7020).
Suppliers of commercial off-the-shelf (COTS) items are an exception to the above. These organizations are exempt from CMMC compliance.
Why is a supply chain approach to safeguarding CUI so critical?
By charging DIB companies with ensuring that their vendors also meet CMMC requirements, the DoW has added significant compliance steps for thousands of organizations. Contractors that fail to achieve compliance risk losing contracts, being rendered ineligible for future contracts, and/or facing False Claims Act litigation.
Why is CMMC flowdown across the DIB so important to cybersecurity? Because failure to protect CUI can compromise national security, personal privacy, and the US economy.
The DoW’s worldwide supply chain is becoming increasingly complex, with more and more sensitive data flowing down to suppliers. Further, much of this data ends up in the cloud, which compounds cybersecurity risk.
Safeguarding CUI thus requires every organization that handles it to uphold an adequate cybersecurity posture. By taking a supply chain approach to cybersecurity, CMMC aims to ensure that CUI remains secure wherever it flows across the DIB.
The DoW’s supply chain approach to cyber compliance makes it imperative for DIB leaders to read contracts carefully and make sure that all requirements are understood, agreed, and reflected in your CUI protection program. Assessing vendors’ cybersecurity requirements often requires significant resources and could shift the balance between pursuing a contract or not.
What is CMMC Level 3?
CMMC 2.0 Level 3 (Expert) defines controls and practices that enable a contractor to protect the most sensitive controlled unclassified information (CUI) from advanced persistent threats (APTs) and nation state level attacks.
The DoW likely plans to apply CMMC Level 3 requirements on a contract-by-contract basis depending on the sensitivity of the CUI involved. These contracts are likely to include the most sensitive defense programs, such as missile system or nuclear weapons development.
What are the CMMC Level 3 control requirements?
CMMC Level 3 starts with the 110 controls defined in NIST 800-171. Then it adds the 24 additional requirements in NIST 800-172, Enhanced Security Requirements for Protecting CUI.
As the NIST 800-172 standard explains, its enhanced controls support a multidimensional, defense-in-depth strategy for protecting highly sensitive CUI based on three primary components:
- A penetration-resistant architecture;
- Damage-limiting operations; and
- Designing for cyber resiliency and survivability while under sustained attack.
This defense-in-depth approach acknowledges that determined adversaries can eventually breach perimeter defenses and embed malicious code on a defender’s systems. Organizations must therefore have protections in place to detect, obstruct, and outflank attackers while protecting the highest value assets.
Critical components of the NIST 800-172 control strategy include:
- Logical and physical isolation and segmentation within networks, storage, etc.
- Dual or multifactor authorization controls
- Extended configuration management requirements
- Continuous 24×7 monitoring via a SOC and advanced analytics
- Using deception techniques to confuse and mislead adversaries
In addition to the NIST 800-172 requirements, the CMMC final rule specifies a number of Organization-Defined Parameters (ODPs) to be applied in specific situations.
What are the CMMC Level 3 assessment requirements?
The CMMC Level 3 assessment process includes multiple steps:
- First, an Organization Seeking Certification (OSC) needs to complete a CMMC Level 2 certification assessment with a Certified Third-Party Assessment Organization (C3PAO) and achieve a perfect 110 score.
- In addition to successfully implementing the CMMC Level 2 control set, the OSC also needs to implement the 24 controls in NIST 800-172.
- After achieving CMMC Level 2 certification, the OSC must arrange with the Defense Contract Management Agency Defense Industrial Base Cybersecurity Assessment Center (DCMA DIBCAC) to verify the NIST 800-172 control implementation.
The CMMC final rule defines a scoring methodology for the DIBCAC to use when assessing CMMC Level 3 compliance, which allows Plans of Action & Milestones (POA&Ms) for some incomplete requirements. POA&Ms must be closed within 180 days of the assessment.
Once achieved, a CMMC Level 3 certification is valid for three years. A senior official must affirm on an annual basis that the compliance is being maintained.
DIB orgs that support or plan to support “critical programs and technologies” should conduct a gap assessment soon to gauge their CMMC Level 3 compliance effort and develop a roadmap.
How to prepare now for CMMC compliance?
Defense contractors that handle CUI should be doing all they can to reduce information security risk in line with NIST 800-171 Rev. 2. Key steps include:
- Initiate or strengthen your third-party risk management (TPRM) program and identify your critical vendors.
- Chart the flow of your federal contract information (FCI) and CUI through your systems as a foundation for CMMC scoping.
- Ascertain what people, roles, and systems have access to CUI in your environment so you can begin limiting access.
- Start training staff on CUI management.
- Start researching/acquiring appropriate technology to protect CUI.
- Perform a NIST 800-171 Rev. 2 gap assessment to identify weak areas and plan remediations.
- Check your compliance with DFARS 7012, which is currently in effect.
- Initiate or strengthen your compliance monitoring program as you move toward “continuous compliance” and continuous monitoring.
- Establish or bolster your internal CMMC team, including appointing a “CMMC point person” or compliance lead.
The bottom line
The DoW paused the CMMC audit program. It did not pause the obligation, and DoJ has given no indication that it is pausing anything. Prior to July 13, your NIST SP 800-171 compliance score was slated to be checked by a third party. Today it stands on one in-house signature. If you are comfortable with that, the pause is (temporary) relief. If you are not, make sure somebody independent can vouch for the number you already posted in SPRS.
To connect with an expert about CMMC requirements flowdown and other defense cybersecurity issues, contact CBIZ Pivot Point Security.