On November 3, the Justice Department (DOJ) announced that two defense and space suppliers, ILC Dover and ILC Astrospace of Delaware, agreed to pay $13 million. The government said they asked the Army, the Missile Defense Agency and NASA to pay them while knowing they weren’t meeting their contracts’ cybersecurity rules. The case started with their own former director of cybersecurity. It lands while Phase 2 of the Defense Department’s Cybersecurity Maturity Model Certification (CMMC) is paused. The pause didn’t remove the rules the case was about, so it’s worth checking your business against them.
What the government alleged
DOJ said the problems ran from January 2018 to October 2024. Most involve controlled unclassified information (CUI). That’s sensitive information that isn’t classified, such as technical drawings. The rules for it come from a National Institute of Standards and Technology (NIST) standard, Special Publication (SP) 800-171. Cloud services are held to the Federal Risk and Authorization Management Program (FedRAMP). DOJ listed five problems:
| What DOJ alleged | What the rule asks for |
|---|---|
| CUI stored with a cloud company that wasn’t held to the required security level | A cloud provider that meets the FedRAMP Moderate baseline, or the same level, plus the Defense Department’s incident rules |
| No system security plan for each covered system | A written plan that shows each system’s limits and how you meet each requirement |
| Not all NIST SP 800-171 controls in place | All the controls, or a plan to finish the missing ones |
| No plans to fix known gaps | A plan of action with dates for each gap |
| No current self-assessment sent to the Defense Department | A current NIST SP 800-171 assessment score in the Supplier Performance Risk System (SPRS) |
These are allegations. The companies settled without admitting they broke the law, according to news reports. Their former director of cybersecurity, who filed the case as a whistleblower, gets $2.35 million of the settlement.
A second case followed on November 13: Johnson Controls, a building-services company, agreed to pay $5 million. What it means for trades contractors.
Why a security gap became a fraud case
The False Claims Act makes it illegal to knowingly ask the government to pay a false claim. DOJ didn’t say the companies were hacked. It said they billed the government while knowing they hadn’t done what their contracts required. That’s the risk: saying you meet a requirement when you don’t, or billing while you know about a gap.
Anyone who sees the gap can file this kind of case, including your own staff. The law gives them a share of what the government recovers.
What the CMMC pause did and didn’t change
In July, the Defense Department suspended CMMC Phase 2, which would have added checks by outside assessors. Our note on the pause explains it. Every rule in DOJ’s list still applies:
- Clause 252.204-7012 of the Defense Federal Acquisition Regulation Supplement (DFARS), if it’s in your contract or your subcontract.
- NIST SP 800-171, with a system security plan and a plan to fix gaps.
- Your current score in the Supplier Performance Risk System (SPRS), where your contract asks for one.
- The 15 basic cybersecurity rules in almost every federal contract, even if you don’t handle CUI.
Five things to check this week
- Where your CUI lives. List every place drawings, specs or other CUI are stored or shared, including cloud drives and email. Ask each provider for proof it meets FedRAMP Moderate or the same level.
- Your system security plan. Make sure you have one and that it matches how your systems work today.
- Your gaps. Compare your controls with NIST SP 800-171. Write down each one that isn’t done.
- Your plan to fix them. Put a date and an owner next to each gap. That list is your plan of action.
- Your SPRS score. Check that the score on file is current and honest. If it’s higher than your real state, fix it.
If you’re a subcontractor, also look at what you told your prime. Primes must flow this clause down to you, and they rely on what you tell them.
Common questions
Does the CMMC pause mean I can skip cybersecurity rules?
No. The pause stopped new requirements for outside assessments. If your contract has DFARS clause 252.204-7012, you still have to protect covered defense information, follow NIST SP 800-171 and report cyber incidents.
Why is a cybersecurity gap a False Claims Act case?
The government alleged the companies asked to be paid while knowing they weren’t meeting the contracts’ cybersecurity requirements. Billing while knowingly out of compliance can make a claim for payment false under the law.
What is a plan of action and milestones?
It’s a written list of the security controls you haven’t finished, with dates and steps to finish them. NIST SP 800-171 expects one for every gap you know about.