On November 13, 2026, the Department of Justice announced that Johnson Controls, Inc. and two of its subsidiaries, Johnson Controls Fire Protection LP and Johnson Controls Security Solutions LLC, agreed to pay $5 million to resolve allegations that they violated the False Claims Act by failing to meet the cybersecurity requirements in their federal contracts and subcontracts. The companies did not admit liability, and the settlement doesn't establish that any violation occurred — but the allegations themselves are worth paying attention to, because they describe a gap we see constantly in smaller contractors' environments too.
What was alleged
The government's allegations covered 25 federal contracts and subcontracts spanning January 2018 through August 2025, touching agencies including the Department of Defense, NASA, and others. Across that work, the government alleged the companies failed to adequately control access to protected information because they lacked sufficient knowledge of, or control over, their own information systems.
For the subset of contracts carrying DFARS cybersecurity clauses (252.204-7008 and 252.204-7012) — the ones that make NIST SP 800-171 the required security baseline — the allegations got more specific: the companies' System Security Plan (SSP) allegedly didn't fully meet what the contracts required, and their plan of action and milestones (POA&M) for fixing known gaps wasn't adequately documented, developed, or implemented.
If that sounds familiar, it should. An SSP that doesn't match reality and a POA&M that exists on paper but isn't actually being worked are two of the most common findings we see in gap assessments — usually not from bad intent, but from documentation that was written once and never updated as the environment changed.
The settlement, in numbers
- $5 million total, plus interest, with no admission of liability.
- $2,428,565.80 of that is designated as restitution.
- The case originated from two whistleblower (qui tam) lawsuits — one filed by a former employee in the Northern District of Georgia in June 2024, the other by a former employee in the District of Columbia in February 2026. The first relator's share of the recovery is $850,000.
- The companies also agreed they can't bill certain investigation, defense, and settlement-related costs back to federal contracts — and have to identify and adjust any such costs already billed.
DOJ officials were direct about what this is meant to signal. The Defense Criminal Investigative Service's director, James Ives, put it plainly: "Cybersecurity requirements in federal contracts are not optional." The acting Assistant Attorney General for the Civil Division, Jonathan Guynn, said contractors "must follow required cybersecurity standards to safeguard sensitive government information." The U.S. Attorney for the Northern District of Georgia, Theodore S. Hertzberg, added that his office will pursue contractors that fail cybersecurity requirements, "particularly when those failures persist over several years."
Why this matters even with CMMC Phase 2 paused
We wrote back in July about the CMMC Phase 2 pause and what still applies while it's on hold. This case is exactly the kind of example that post was warning about. Nothing in this settlement depended on CMMC third-party certification being active — the underlying obligations came from DFARS 252.204-7012 and NIST SP 800-171, which have applied to covered contracts since December 2017 and were never part of the pause.
That's the part that gets lost whenever CMMC is in the news for being delayed, scaled back, or restructured. CMMC is the certification program. The security requirements it was built to verify — safeguarding controlled unclassified information under NIST SP 800-171, maintaining an accurate SSP, and actually working your POA&M — are separate, older, contractual obligations that a contract's DFARS clauses impose directly. Enforcement of those obligations runs through the False Claims Act, not through CMMC, and the False Claims Act was never paused.
What this means for your business
If your contracts carry DFARS 252.204-7008 or 252.204-7012, or you're a subcontractor flowing down from a prime that does, this case is a reasonable prompt to check three things:
- Does your SSP actually describe your current environment? Not the environment you had when it was written — the one you have today, including any new systems, vendors, or cloud services that touch CUI.
- Is your POA&M a working document or a filed one? Every open item should have a real owner and a real target date, and someone should be checking on it, not just storing it.
- Does your SPRS score match what you'd actually find in an assessment? Your SPRS submission is a representation to the government, and this case is a reminder that representations carry legal weight independent of certification status.
None of this requires a C3PAO assessment or waiting for CMMC Phase 2 to resume. It requires treating the documentation you already have as a living description of your environment rather than a one-time deliverable. If you're not confident yours would hold up, that's worth a direct look before it becomes someone else's finding.
