Your Cyber Lead Could Be the False Claims Act Whistleblower
The person who knows your security gaps best may be on your payroll. If you sign DoD contracts that require NIST SP 800-171, fix those gaps before someone files a False Claims Act whistleblower suit.
CMMC Ready Now, in Leesburg, Virginia, provides CMMC compliance consulting for defense contractors: gap assessments, remediation and C3PAO preparation.
In This Article
What happened in November 2026?
Two federal contractors settled cyber fraud claims with the Department of Justice in two weeks. In each case, a former employee helped bring the suit.
On November 3, ILC Dover and ILC Astrospace agreed to pay $13 million. Their contracts were with the Army, the Missile Defense Agency and NASA.
The whistleblower was Philip Root, ILC's former Director of Cybersecurity. He will receive $2.35 million.
On November 13, Johnson Controls and two of its subsidiaries agreed to pay $5 million. Their contracts were with NASA and the Departments of Defense, Energy and Justice.
A former employee, Kelly Vance, will receive $850,000. A second suit was filed by David Thomas.
Neither company admitted liability. DOJ says the claims are allegations only, with no finding of liability.
What can a False Claims Act whistleblower do?
The False Claims Act lets a private person file suit on behalf of the government. It is the law behind both November cases.
DOJ calls this a unique whistleblower provision. It lets private parties help the government find fraud and share in any recovery.
In 2021, DOJ launched its Civil Cyber-Fraud Initiative. It said it would use the False Claims Act to pursue cyber fraud by contractors.
So the risk is not only an outside audit. It is anyone inside who sees the gap between your paperwork and your systems.
What did DOJ say went wrong?
The two cases share a pattern. Both named the System Security Plan (SSP) and the Plan of Action and Milestones (POA&M).
At ILC, DOJ alleged:
- The SSP was not developed, documented or kept up to date.
- POA&Ms were not developed or put in place.
- NIST SP 800-171 controls were not fully in place.
- One company never sent DoD a current NIST SP 800-171 assessment. The other sent one that was not current.
- A cloud provider storing CUI did not meet FedRAMP Moderate equivalent security.
At Johnson Controls, DOJ alleged the company did not keep an SSP that met its contract terms. It also said the POA&M was not properly built or used.
DOJ also said the company did not control access to protected data. It lacked enough insight into, and control over, its own systems.
What should be on my readiness checklist?
Start with the items DOJ named. Each one is a document or a setting someone can check.
- Review and update your System Security Plan on a set schedule (CA.L2-3.12.4).
- Turn every open gap into a real POA&M item with an owner and a date (CA.L2-3.12.2).
- Confirm the NIST SP 800-171 assessment you sent DoD is current. That is the self-assessment score DoD contractors post in SPRS.
- Check that any cloud service storing CUI meets FedRAMP Moderate equivalent security, and keep the proof.
- Keep an inventory of the systems that touch CUI, so you know what you control.
- Give staff a clear internal path to raise a gap, and answer them in writing.
Why does an internal path matter?
Your security team sees the gaps first. They know when the SSP is stale or a POA&M item has slipped.
Give them a direct line to leadership. Track each concern until it is fixed or formally accepted.
This is not about stopping anyone from reporting. The law lets private parties go to the government, and that stays their choice.
The point is simple. When your people raise a gap, fix it. A company that listens and acts has fewer gaps to report.
What is the first step?
Pull your SSP, your POA&M and the date of your last NIST SP 800-171 assessment. Ask your cyber lead which one is out of date, and start there.
Check Your Readiness
CMMC Ready Now can walk through each item with you. Book a call to check your readiness.
Book a Call with RickFrequently Asked Questions
What is a False Claims Act whistleblower?
A False Claims Act whistleblower is a private person who files suit on behalf of the government. DOJ says the law lets them help find fraud and share in any recovery.
Can a former employee file a False Claims Act case about cybersecurity?
Yes. In both November 2026 DOJ cyber settlements, a former employee filed suit and was paid. At ILC Dover, it was the former Director of Cybersecurity.
What does this mean for my business?
It means your SSP, POA&M and NIST SP 800-171 assessment must match reality. The people who can see a mismatch already work for you. Fix gaps now and give staff a clear way to raise them.
Did ILC Dover or Johnson Controls admit they broke the law?
No. DOJ says the claims are allegations only and there has been no determination of liability. ILC agreed to pay $13 million and Johnson Controls agreed to pay $5 million.
Should we discourage staff from reporting outside the company?
No. The False Claims Act lets private parties help the government find fraud. Your goal is to fix gaps fast and listen when your people raise them.
Sources
- DOJ: ILC Dover and ILC Astrospace agree to pay $13M (November 3, 2026) (justice.gov)
- DOJ: Johnson Controls and two subsidiaries agree to pay $5 million (November 13, 2026) (justice.gov)
- DOJ: Civil Cyber-Fraud Initiative announced (October 6, 2021) (justice.gov)
- NIST SP 800-171 Rev 2 (csrc.nist.gov)
