Incident · 8-K Item 8.01
Johnson Controls reports disruption to internal IT infrastructure from a cybersecurity incident
Compiled from public records. Updated 2026-11-14. By the cisonews.net Desk.
Johnson Controls International plc told the SEC in a Form 8-K filed under Item 8.01 on September 27, 2023 that a cybersecurity incident had disrupted portions of its internal information technology infrastructure and applications. The filing does not say what information was involved or how many people were affected, and states that the company is still assessing what information was impacted.
Entries like this one, in Wednesday’s docket
Wednesdays
Unsubscribe any time.
What happened at Johnson Controls, and when?
The filing describes disruptions in parts of the company's internal systems and applications that resulted from the incident. This first filing gives no date for when the incident began or was detected, and it does not describe how the incident occurred. The company says it began an investigation promptly after detecting the issue, with help from outside cybersecurity experts. It also says the investigation and remediation work were still under way when it filed.
Did the attack disrupt Johnson Controls' operations?
The company says many of its applications were largely unaffected and stayed operational. For some operations it put workarounds in place so that it could keep serving customers. It also states plainly that parts of the business have been disrupted and that more disruption is expected.
On finances, the company says it was still working out whether the incident would affect the timing of its fourth quarter and full fiscal year results. It also says it was assessing the effect on those results. The filing gives no cost figure.
What did the November 13, 2023 update say?
On November 13, 2023, Johnson Controls filed a second 8-K under Item 8.01 with more detail. It says it first detected the incident during the weekend of September 23, 2023, after outages to some of its systems. The incident consisted of unauthorized access by a third party and the deployment of ransomware on part of the company's internal IT infrastructure. By then the company had largely restored the affected applications and systems, and it believed the unauthorized activity was contained. Its analysis of the data accessed, exfiltrated or otherwise affected was still under way. It had seen no evidence of an impact on its digital products, services and solutions, including OpenBlue and Metasys.
The incident also disrupted systems that support or provide data used in financial reporting. The company said it would be late reporting its fiscal 2023 fourth quarter and year-end results, and expected to report them by December 14, 2023.
What risks did Johnson Controls list?
The forward-looking statements section names several open questions. These include what more the investigation may uncover, the length and scope of business disruption, added expenses, and whether insurance coverage will be available. The same section mentions possible compromise of sensitive, confidential, financial or personal data as a general risk factor. That wording is not a statement that such data was taken.
What did the Johnson Controls cyberattack cost?
Johnson Controls' annual report for its fiscal year ended September 30, 2023, filed on December 14, 2023, gives one figure.
Lost and deferred revenue and expenses from the incident cut fiscal 2023 net income by about $30 million, or about $0.04 per diluted share.
How many Delaware residents were affected?
Delaware's attorney general lists a report from Johnson Controls dated June 30, 2025, for a breach it dates from February 1, 2023 to September 30, 2023, with 3,722 Delaware residents potentially affected. That count covers Delaware residents only.
How many Washington residents were affected?
Washington's attorney general lists a report from Johnson Controls on June 30, 2025, for a breach dated February 1, 2023, with 4,903 Washingtonians affected. The information it records as compromised is: name, Social Security number, driver's license or Washington ID card number, financial and banking information, full date of birth, passport number, health insurance policy or ID number, medical information, biometric data and username and password or security question answers. That count covers Washington residents only.
How many Indiana residents were affected?
Indiana's attorney general lists a notice from Johnson Controls sent on June 30, 2025, for a breach dated February 1, 2023, with 16,729 Indiana residents affected. The report prints the same number, 16,729, in its total-affected column, so it gives no count beyond Indiana. That is the largest of the three state counts on record for this breach, ahead of Washington's 4,903 and Delaware's 3,722.
What is still unknown?
Neither filing names categories of personal information, gives a count of affected people, or describes notification letters or a credit monitoring offer. Neither identifies the third party behind the ransomware, and neither says whether customer or employee data was affected.
The rule behind an Item 8.01 filing
Item 8.01 (Other Events) is the item the SEC's Division of Corporation Finance encouraged companies to use for a cybersecurity incident they have not yet determined to be material, or have determined is not material. Its May 21, 2024 statement says a company that later determines the incident is material should file under Item 1.05 within four business days of that decision. Source: U.S. Securities and Exchange Commission, statement by the Director of the Division of Corporation Finance. The guide Item 8.01 versus Item 1.05: when a cyber incident moves between them reads the rule in full, and the glossary defines Form 8-K Item 1.05.
Other industrials & manufacturing incidents on cisonews.net
- Plant Construction Company, L.P., Breach notice, first disclosed November 13, 2026
- Southwire Company, LLC, Other public record, first disclosed November 12, 2026
- USA Waste-Management Resources, LLC, Breach notice, first disclosed November 6, 2026
- Cotton Incorporated, Breach notice, first disclosed November 2, 2026
- NCH Corporation, Breach notice, first disclosed October 30, 2026; 5,031 affected in total (Indiana Attorney General)
Sources
- 2026-11-06 · AWashington State Office of the Attorney General, data breach notifications list, published November 6, 2026
- 2023-09-27 · AJohnson Controls International plc, Form 8-K (SEC EDGAR), published September 27, 2023
- 2023-11-13 · AJohnson Controls International plc, Form 8-K, Item 8.01 (SEC EDGAR), published November 13, 2023
- 2023-12-14 · AJohnson Controls International, Form 10-K for the period ended 2023-09-30 (SEC EDGAR), published December 14, 2023
- 2026-11-06 · ADelaware Department of Justice, security breach notification database, published November 6, 2026
- 2026-11-14 · AIndiana Attorney General, data breach year-to-date report 2025, published November 14, 2026
- 2024-05-21 · AU.S. Securities and Exchange Commission, statement by the Director of the Division of Corporation Finance, published May 21, 2024
Tier A: the organization itself (including notices it filed with a state attorney general), a regulator or SEC EDGAR. Tier B: established press. Each fact on this page carries its supporting passage in the page source.
Entries like this one, in Wednesday’s docket
Wednesdays
Unsubscribe any time.