Skip to content
cisonews.net

Data breaches at security vendors

Which disclosed incidents in the log happened at companies that sell security products? 5 entries at 5 vendors, newest first, with the vendor's category from the directory.

The 5 disclosures run from 2022 to 2025. 4 of them came in an SEC 8-K under Item 1.05, the item for a material cybersecurity incident; the other one used a different 8-K item. Where the filing gives the day the company detected the incident (4 of 5), the gap to the first public disclosure runs from 7 days (Microsoft) to 84 days (AT&T), with a median of 55 days.

How long did each vendor take to disclose?

Security vendors in the log: detection date, first public disclosure, days between and the filing route
VendorDetectedDisclosedDaysRouteFollow-up in the log
F5August 9, 2025October 15, 2025678-K Item 1.05No follow-up filing in the log
AT&TApril 19, 2024July 12, 2024848-K Item 1.05Cited again in a 10-Q and two 10-Ks; no amendment
Hewlett Packard EnterpriseDecember 12, 2023January 24, 2024438-K Item 1.05Remediated, per the fiscal 2024 10-K; no amendment
MicrosoftJanuary 12, 2024January 19, 202478-K Item 1.05Ongoing at last amendment; amended once
Rackspace TechnologyNot statedDecember 6, 20228-K Item 7.01Two filings

“Detected” is the date the company’s own filing gives for learning of the incident; “Disclosed” is the first public filing in the log. Item 1.05 asks for a report within four business days of the company deciding the incident is material, not of detecting it, so a long gap here is not by itself a late filing. What SEC Item 1.05 requires explains the rule, and the Item 1.05 tracker lists every such filing.

How to read this list. An entry records what the company disclosed, sourced to its filing.

Vendor names link to the company’s one record on cisotribune.com, which lists what it sells. A company counts as a vendor when its name or ticker matches a published directory record. Directory data as of November 15, 2026.

The full log, with every sector and form item, is on the incident log.