Signed, Not Secured: What the Johnson Controls Settlement Means for CMMC Compliance

On November 13, 2026, Johnson Controls and two subsidiaries agreed to pay $5 million to settle allegations that they ignored cybersecurity requirements in federal contracts. That agreement came three days after the date CMMC Phase II was set to begin.

For defense contractors, the message is clear: you don’t need a CMMC deadline to be held accountable for CMMC compliance. The cybersecurity clauses in your contracts are enforceable today, and the Justice Department is enforcing them.

Here’s what the government alleged, why the timing matters, and what your company should review this month.

What the Justice Department alleged

According to the DOJ, the case covers contracts and subcontracts from January 2018 to August 2025. Those agreements involved the Department of Defense, NASA, the Department of Energy, and the Department of Justice.

The contracts required Johnson Controls to use security controls to protect government information.

The government alleges two types of failures:

  1. Johnson Controls allegedly lacked enough information about, or control over, its information systems to limit who could access protected data.
  2. Some contracts required NIST SP 800-171. On those contracts, the company allegedly failed to maintain a System Security Plan that met contract requirements. The government also alleges that Johnson Controls did not fully develop and carry out a plan of action and milestones to address known gaps.

In addition, seven federal investigative agencies worked with DOJ attorneys on the case. They included the Defense Criminal Investigative Service, NCIS, NASA’s Office of Inspector General, and the GSA Office of Inspector General.

These remain allegations. No one has determined liability.

CMMC Phase II is paused. Enforcement is not.

The Department of War suspended CMMC Phase II on July 13, 2026. As a result, the third-party assessment rule scheduled for November 10 never took effect.

Since then, a reform task force has sent recommendations to the DoW CIO. Those recommendations include restarting Phase II for a narrower group of contracts. However, officials had not approved any recommendations as of late October.

Some contractors heard “paused” and moved CMMC compliance to next year’s to-do list. This case shows why that could be risky.

CMMC verifies security requirements; it didn’t create them. DFARS 252.204-7012 and NIST SP 800-171 have appeared in defense contracts for years. They remain binding on every contract that includes them. That includes the 72-hour incident reporting rule.

The Johnson Controls case relied on those existing clauses. The government did not need a CMMC assessment to bring it.

Why paperwork can cost $5 million

Nobody hacked Johnson Controls. Instead, the allegations focus on documents. That should get every compliance lead’s attention.

Your System Security Plan (SSP) describes how your company protects Controlled Unclassified Information. It should cover the systems you use today, including your network, users, cloud services, and security boundaries.

If your environment has changed since you wrote the SSP, the document may no longer describe your company accurately.

Your plan of action and milestones (POA&M) tracks how you plan to address known gaps. Each item needs an owner, a target date, and visible progress. Without those details, it’s just a list of weaknesses your company already knows about.

Your SPRS score relies on these documents. When they don’t match your actual environment, that mismatch can raise False Claims Act concerns. For example, the government may have paid for security that the company said it provided but did not.

The risk can come from inside

The settlement resolves two whistleblower lawsuits. A former Johnson Controls employee filed one of them and will receive $850,000 from the recovery.

Under the False Claims Act, a private citizen can sue on the government’s behalf. That person may also share in the money the government recovers.

In practice, your exposure may go beyond what an auditor finds. Someone who knows what your contracts require—and what your environment actually looks like—could raise the issue.

That changes who should pay attention. Companies often treat CMMC compliance as an IT project. However, the company that signed the contract holds the obligation. Leadership decides how to fund, staff, and prioritize that work.

What to do before Phase II restarts

You don’t need to wait for a new deadline to reduce your risk. Start by asking these questions:

  1. Does your SSP describe your current environment? Compare it with your network, users, cloud services, and CUI boundary. Update anything that has changed.
  2. Is every open POA&M item moving forward? Give each item an owner and target date. Track progress, close what you can, and document why other items remain open.
  3. Does your SPRS score match your evidence? Could you show the proof behind your score if someone asked you to defend it tomorrow?
  4. Do you control access to CUI? Identify which systems hold it and who can access them. This was the first type of failure the DOJ alleged.
  5. Does leadership know the current status? The executive who signs off on your SPRS score should see the same picture as your IT team.

There’s also a practical reason to act now. When Phase II returns, contractors may compete for a limited number of certified assessors. Companies with current documentation will be better prepared.

Signed means binding

The CMMC deadline moved. The clauses in your contract didn’t.

If you signed a defense contract that includes DFARS 7012, you already have obligations to meet. This case shows the government may enforce those clauses with or without Phase II.

The least expensive time to find a gap is before anyone else does.

Schedule your complimentary consultation with Cyber Security Solutions. We’ll look at where your SSP, POA&M and SPRS score stand and help you decide what to fix first. Book a Free Expert Call

Be smart. Be secure. Be free.


The Johnson Controls settlement involves allegations only; there has been no determination of liability. This article is for general information and is not legal advice. CSS does not grant CMMC certification.

Sources: U.S. Department of Justice, Office of Public Affairs, press release, Nov. 13, 2026; Jenner & Block on the CMMC Phase II suspension; Federal News Network on the CMMC task force recommendations.

 

Enough Talks, Let’s find the solutions

Recent Posts:

(Sign up)

Ready to
close your gaps?

From your first scan to full remediation, we guide you through every step before the CMMC clock runs out.