The short answer
No. The Johnson Controls agreement announced by DOJ on November 13, 2026 resolves specified historical allegations; it is not a current NIST SP 800-171 assessment or certification. The three corporate defendants agreed to a $5 million settlement plus interest without admitting liability. A present compliance conclusion requires evidence tied to the relevant contractor, contract requirements, information system and assessment period.
Prepared by Dossier Editorial with AI assistance from public records. This educational document review does not claim a live Dossier investigation, technical security assessment, human approval or legal review. It is not a legal opinion or a certification of any contractor’s present compliance.
Executive summary: resolution is not assurance
A settlement answers a defined legal question. A security assessment answers whether specified safeguards are implemented and effective within a defined system. Those questions require different evidence. This case shows how to preserve that distinction when a vendor questionnaire asks whether an enforcement matter has been resolved.
- Established: a signed agreement addresses alleged cybersecurity failures during January 1, 2018-August 1, 2025, associated with 25 listed contract and subcontract entries.
- Qualified outcome: the agreement contains no admission of liability. Its government monetary release for covered conduct is conditional on receipt of the settlement amount and subject to reservations.
- Open here: current contract-specific compliance, payment receipt and later filed dismissals were not independently verified.
- [S1]
The parent company’s latest annual report describes security monitoring and external assessments. That is relevant company context, but it does not supply the assessment results for the contract and system a reader may be evaluating.[S5]
Identify the entity, contract and system
The agreement defines JCI as Johnson Controls, Inc., Johnson Controls Fire Protection LP and Johnson Controls Security Solutions LLC. Keep these parties distinct from the SEC reporting parent, Johnson Controls International plc. A shared brand does not make every subsidiary, contract or system interchangeable.[S1][S5]
| Identity field | Verified example | Review consequence |
|---|---|---|
| Civil actions | 1:24-cv-2500, Northern District of Georgia; 1:26-cv-448, District of Columbia | Use court plus docket number; avoid a company-name-only match.[S1] |
| Exhibit scope | Exhibit A contains 25 numbered entries. | Entries can contain multiple instruments; this is not a count of 25 distinct systems.[S1] |
| Worked contract identifier | Entry 16: subcontract KSCFL24008 under prime 80KSC024FA049. | Record both identifiers. The exhibit alone does not define the system boundary or prove present performance.[S1] |
| Applicable requirements | The actual contract, incorporated clauses and amendments. | Verify the required standard and revision for the period being assessed; these instruments were not reviewed here. |
| Current system and evidence period | Named system boundary, assessment date and scope. | A parent-level program statement cannot supply these missing details. |
For the worked example, the defensible starting record is “listed subcontract; current system assurance unresolved.” Do not expand it to “all Johnson Controls systems failed” or “all systems are now compliant.” Neither conclusion follows from this agreement.
Chronology: conduct, signatures, filing and announcement
| Date | Documented development | What the date means |
|---|---|---|
| January 1, 2018-August 1, 2025 | The government alleges failures within this period. | Alleged historical conduct, not a finding about today’s systems.[S1] |
| June 7, 2024; February 11, 2026 | The agreement recites the filing dates of the Georgia and D.C. actions, respectively. | Case history described in the agreement; underlying complaints were not reviewed.[S1] |
| October 19, 2026 | Latest signature date visible in the signed counterparts. | Paragraph 23 defines effectiveness by the last signatory’s date. This is separate from the later announcement.[S1] |
| November 12, 2026 | Johnson Controls International plc files its FY2026 Form 10-K. | Current company disclosure, including Item 1C on cybersecurity.[S5] |
| November 13, 2026 | DOJ announces the $5 million settlement. | Announcement of the agreement; not a payment receipt.[S2] |
| November 14, 2026 | This review checks the agreement, announcement, NIST guidance and annual report. | Evidence-check and article publication day; no technical testing performed. |
Some signature pages are scans with little extractable text. We visually checked the counterparts and Exhibit A rather than assigning the press-release date to every event. Keeping these dates separate prevents an announcement from becoming an invented execution or payment date.
Findings: the supported outcome and the material gaps
The government’s allegations include inadequate knowledge and control of relevant systems, access restrictions, system security plans and plans of action. These are allegations in Recital I, not technical findings made by this article. Recital J provides both that JCI does not admit liability and that the United States does not concede its claims lacked foundation.[S1]
The $5 million obligation includes interest under paragraph 1. Paragraph 4 conditions the government’s covered-conduct monetary release on receipt; paragraph 13 connects receipt to filing dismissal stipulations. Paragraph 6 preserves specified claims and authorities. None of those provisions is a remittance record, a filed dismissal or evidence of an actual suspension or debarment.[S1]
Free docket searches did not yield the later filings for these two matters. We did not review a payment receipt or filed dismissal stipulation, and this is not a complete docket certification. The bounded result is an agreed settlement with those completion steps unverified in this review—not a claim that payment or dismissal has failed to occur.
The November 12 parent filing describes round-the-clock monitoring, vulnerability assessments, and third-party penetration testing and maturity assessments. These are the company’s descriptions of its program. Item 1C does not provide the underlying results needed to assess the worked subcontract’s particular system. The disclosure is useful contrary context to any assumption that the historical allegations describe every current control.[S5]
NIST’s assessment guidance distinguishes the system security plan’s description of the environment and safeguards from assessment of their implementation and effectiveness. A plan can identify what should be in place; it does not, by itself, demonstrate that each safeguard works. For a current review, seek the relevant assessment scope, results, exceptions and subsequent closure evidence.[S3]
There is also a version trap. NIST’s catalog marks SP 800-171 Revision 2 withdrawn and superseded by Revision 3 on May 14, 2024. That catalog status does not show that a particular contract was amended. Match the obligation to the actual contract and relevant period before using either revision as the review benchmark.[S4]
These five source items serve different roles: an agreement, an agency announcement, two NIST reference pages and an issuer filing. They are not five independent audits. No current system security plan, assessment report, contract amendment or remediation closure record was obtained.
Decision tree: can the present compliance question be answered?
01Have you matched the exact contractor, contract and system?
If establishedRecord legal entity, prime and subcontract identifiers, system boundary and assessment period before interpreting evidence.
If unresolvedKeep scope unresolved. A brand name, settlement headline or parent filing cannot fill those identity fields.
02Do you have the applicable clauses and standard revision?
If establishedMap each requirement to the instrument that imposes it, including amendments and relevant dates.
If unresolvedObtain the contract requirements through an authorized channel. Do not substitute the newest standard for an unverified contractual obligation.
03Is there a scoped assessment with results and treatment of open findings?
If establishedCheck who performed it, when, which systems and requirements it covers, its limitations, and evidence supporting any claimed closure.
If unresolvedRecord current compliance as unverified. A policy, security plan or statement that testing occurs is insufficient for the missing result.
04Are you also being asked whether the litigation and payment steps are complete?
If establishedReview the agreement’s conditions, actual payment evidence and filed dispositions separately from the technical assessment.
If unresolvedKeep the legal settlement as context. Do not treat it as a technical pass or a current failure finding.
05Does new evidence alter the scope or outcome?
If establishedAdd a dated finding, retain the earlier version and explain exactly which conclusion changed.
If unresolvedState the review date and coverage. Missing evidence supports an open question, not an assumed answer.
The tree is an evidence-review method. Contract interpretation and technical assurance may require qualified review; this public walkthrough performs neither on the reader’s behalf.
Reproduce the review in Dossier
- Frame one testable question: “What evidence supports current compliance for subcontract KSCFL24008’s relevant system and period?” Track settlement completion as a separate question.
- Preserve the five public originals with their URLs, retrieval dates and file hashes. Note that scanned signatures need visual review and that the SEC filing is a parent-company statement.
- Record the three agreement parties, two court/docket identifiers and the exhibit’s prime/subcontract pair in case notes or an attached inventory. Leave unknown system and contract-version fields explicitly unresolved.
- Build the dated chronology above. Distinguish alleged conduct, signature dates, issuer disclosure, public announcement and this review’s evidence date.
- Link each finding to a precise source location: Recital I for allegations, paragraphs 4 and 13 for conditional completion steps, Exhibit A for the contract entry, and Item 1C for the company’s account.
- Create separate open evidence tasks for contract scope, current assessment results, remediation closure, payment receipt and filed disposition. Do not mark one task complete merely because another is supported.
- Before exporting, reconcile the executive summary with the evidence table and unanswered questions. Keep any later nonpublic security material in its authorized workspace; a public article needs no sensitive configuration details.
This describes a reproducible authoring workflow. No live Dossier matter was created or investigated, no assessment was commissioned and no provider was contacted. The downloadable report uses the same public-source content as this article.
What evidence would change the conclusion?
- A matched contract and amendments would establish which requirements apply to the specific legal entity, system and period.
- A scoped assessment, its limitations and evidence supporting closure of relevant findings would support a more precise present assurance conclusion. A list of planned actions alone would not establish completion.
- A receipt or other authoritative payment record, plus the actual filed dispositions, would resolve the settlement-completion questions within their documented scope.
- A later original government action or company filing could justify a follow-up. Retain the previous record and explain the change instead of silently replacing the historical finding.
The related CISA KEV walkthrough asks a complementary question: whether a public vulnerability entry establishes exposure in a particular vendor deployment. Both reviews require a precise match between a public record and the system about which a decision is being made.
Questions readers ask
Does the Johnson Controls settlement certify current NIST SP 800-171 compliance?
No. It addresses defined historical allegations. Current assurance requires evidence matched to the contractor, contract, system, applicable requirements and assessment period; the settlement does not supply that assessment.[S1][S3]
Did Johnson Controls admit liability?
No. Recital J contains no admission of liability by JCI and no concession by the United States that its claims lacked foundation. DOJ says the resolved claims are allegations and there has been no determination of liability. Neither qualification is a current technical compliance finding.[S1][S2]
Has the $5 million been paid?
This review did not obtain payment evidence. The agreement requires $5 million plus interest, and the announcement says the companies agreed to pay. Those documents alone do not verify receipt or the later filing of dismissal stipulations.[S1][S2]
Is a system security plan the same as an assessment?
No. NIST describes a plan as documenting the system environment, requirements and their implementation. Assessment examines implementation and effectiveness. A current assurance review needs results and scope, not merely evidence that a plan exists.[S3]
Does Revision 2’s withdrawal automatically change an existing contract?
The NIST catalog records withdrawal and supersession, not the terms of a particular contract. Check incorporated clauses and amendments before selecting the applicable revision. No contract amendment was reviewed in this case walkthrough.[S4]
What remains unresolved as of November 14, 2026?
Contract-specific current compliance, the worked example’s system boundary and assessment results, payment receipt and filed dismissals remain unverified here. The company’s annual report supplies program context but not the missing contract-specific assessment.[S5]
Source register
Original records and agency pages. Each reference identifies its role and limits.
S1Signed Johnson Controls cybersecurity settlement agreement
U.S. Department of Justice · Original signed settlement agreement · Checked November 14, 2026
Anchor: Recitals A-C and I-J; paragraphs 1, 4, 6, 13 and 23; signature counterparts; Exhibit A entry 16
17-page original. Latest visible signature October 19, 2026. Allegations, defined release and reserved matters; not payment, dismissal or current security-assessment proof.
S2Johnson Controls and subsidiaries agree to pay $5 million
U.S. Department of Justice · Original agency announcement · Checked November 14, 2026
Anchor: November 13, 2026 release 26-1360; settlement summary; final liability qualification
Agency announcement links the agreement. Same publisher as S1; announcement date is not an execution or receipt date.
S3NIST SP 800-171A assessment: purpose and scope
National Institute of Standards and Technology · Original standards guidance · Checked November 14, 2026
Anchor: Purpose; Scope; system security plan and assessment of implementation and effectiveness
General assessment methodology. Not a Johnson Controls assessment or a determination of a specific contract’s requirements.
S4NIST SP 800-171 Revision 2 publication record
National Institute of Standards and Technology · Original publication and version record · Checked November 14, 2026
Anchor: Withdrawn May 14, 2024; superseded by SP 800-171 Revision 3
Catalog history, not evidence that a particular government contract was amended.
S5Johnson Controls International plc FY2026 Form 10-K
Johnson Controls International plc / SEC EDGAR · Original issuer annual filing · Checked November 14, 2026
Anchor: Filed November 12, 2026; year ended September 30, 2026; Item 1C Cybersecurity, printed pages 25-26
Parent CIK 833444; company-described security program. Underlying contract-specific assessment reports were not supplied by this disclosure.