Bug, insider or attack? What actually happens after ‘technical issue’
Microsoft 365, the FAA, Workday, Chase and United each said it saw no sign of a cyberattack. We checked nine past cases where a first statement changed: the public got the fuller story a median of 40 days later, and some companies paid for the gap years after.
- Across the nine cases we checked, the public got the fuller story a median of 40 days after the first statement, or after the company knew. The range ran from 8 days to almost two years.
- Enforcement can follow years later: SEC penalties for Yahoo, Flagstar and four firms that minimized SolarWinds-related intrusions, and a conviction for Uber’s former security chief.
- Write the hour-one statement so it is still true on day 30: say you are investigating, not that it was not an attack. Decide in advance who changes it, and when.
When a big company says “technical issue,” the first statement is not always the last word. In nine past cases we checked where the first word minimized or misdescribed an incident, the public got the fuller story a median of 40 days later. The range ran from 8 days to almost two years. Several companies paid for the gap, years after the fact.
This week: five “no sign of attack” statements and one confirmed attack
Five large US outages landed November 12 to 16. Microsoft says its Microsoft 365 outage was not caused by a cyberattack (SecurityWeek). The FAA has “no indication that this was a cyberattack or an outside nefarious actor.” Workday told ABC10 the disruption was not related to a cybersecurity incident (UC Today). Chase said “it is not cyber-related” (Al Jazeera). United cited “no indication that this was a cybersecurity-related issue” (AP).
Our view: nothing we have read suggests any of the five is holding anything back. The week’s confirmed attack was elsewhere: on November 16, an unauthorized party “exploited a vulnerability in Experimentation” to add code to scripts Optimizely serves, and Report URI counted 178 affected organizations (SecurityWeek).
What the record shows
Nine cases: first word to fuller story
| Case and what changed | Days |
|---|---|
| Change Healthcare · Feb 21 to 29, 2024 “Network interruption” and a nation-state suspect (filing); then a ransomware gang. Ransom paid, confirmed Apr 22. | 8 |
| FAA NOTAM · Jan 11 to 19, 2023 “A damaged database file”; then contract staff “unintentionally deleted files.” | 8 |
| Flagstar · Jan 25 to Feb 9, 2021 “No evidence of unauthorized access to customer information,” a day after learning data was taken. SEC penalty $3.5M, 2024. | 15 |
| MGM Resorts · Sep 11 to Oct 5, 2023 “Cybersecurity issue”; then an 8-K: customer data taken, about $100M hit. | 24 |
| Equifax · Jul 29 to Sep 7, 2017 Knew July 29, told the public Sept 7. A former unit CIO was charged with insider trading. | 40 |
| Okta · Jan 20 to Mar 22, 2022 Silent until Lapsus$ posted screenshots; later “we made a mistake.” | 61 |
| Microsoft key theft · Sep 6, 2023 to Mar 12, 2024 A root-cause post it called inaccurate to a federal review board in November; fixed in March. | 188 |
| Uber · Nov 14, 2016 to Nov 21, 2017 Paid the hackers to stay quiet, Bloomberg reported. Former CSO convicted, 2022. | 372 |
| Yahoo · Dec 2014 to Sep 22, 2016 Filings described breaches only as a risk. SEC penalty $35M, 2018; $350M off its sale price. | 631+ |
Days from the first statement or, if the company said nothing, the day it knew. Yahoo counts from December 31, 2014, a floor. Median of the 9 cases we checked: 40 days, not a rate for all incidents (make_outage_week.py).
The SEC put the pattern in writing in October 2024: Unisys, Avaya, Check Point and Mimecast each “negligently minimized” SolarWinds-related intrusions, and paid $4 million, $1 million, $995,000 and $990,000. “Downplaying the extent of a material cybersecurity breach is a bad strategy,” an SEC official said (The Record). All four settled without admitting or denying the findings.
First words also hold. CrowdStrike’s CEO called its July 2024 outage “not a security incident or cyberattack” (TechCrunch), and it was not. Cloudflare “initially wrongly suspected” a DDoS attack in 2025; it was a bad file. Southwest’s 2022 meltdown was in large part “outdated scheduling software” (NPR). And insiders: in April 2022 Block said a former employee had downloaded Cash App Investing reports after leaving (CNN).
What actually happens, in order
- Hour 0, the outage. Teams restore first, since an hour down costs over $300,000 for more than 90% of mid-size and large firms (ITIC). Restoring can overwrite evidence.
- Hour 1, the holding line. Said early: a “network interruption” (UnitedHealth), a “cybersecurity issue” (MGM).
- The next weeks, the quiet investigation. Outside forensics and lawyers. Okta waited on its vendor’s “third party forensic firm.” Cash App hired “a leading forensics firm.”
- Notices that never go public. Cash App “notified law enforcement.” A bank’s notice to its regulator is confidential under the 2021 rule.
- Weeks later, the story changes. Change Healthcare’s nation-state suspect became a ransomware gang in 8 days. Okta’s count fell from 366 customers to two (The Record).
- Years later, sometimes, enforcement. Yahoo, Flagstar and four SolarWinds-related firms drew SEC orders about 3 to 4 years after their incidents; Uber’s former CSO was convicted almost six years after. Not always: the SEC dropped its case against SolarWinds and its CISO in November 2025, after a judge read post-incident statements in the context of an unfolding investigation (Harvard Law School Forum).
On paper, the clocks are short
An 8-K under Item 1.05 is due four business days after a company decides an incident is material. Banks tell their regulator within 36 hours; defense contractors tell DoD within 72 hours of discovery. The Attorney General can delay an 8-K up to 120 days. In practice, every clock waits for a decision. After SEC staff said in May 2024 that Item 1.05 is for material incidents, 28 companies used the voluntary Item 8.01 in the rest of 2024, against nine under Item 1.05. Of 26 Item 1.05 filers, two named a material impact only in amendments (Debevoise).
When a nation-state is suspected
The government often hears first. Microsoft did not detect the 2023 Storm-0558 intrusion itself; it relied on “an initial notification from the State Department” (The Record). Justice Department guidelines weigh delay more when a company learned of an incident “only because a U.S. Government agency alerted” it. Cleared contractors report classified-system incidents to DoD under 32 CFR 117.8. Our read: in this lane the public hears later, if ever.
Our forecast
Our forecast: by March 31, 2027, none of this week’s five “no sign of attack” statements will be revised to an admitted cyberattack, and no Item 1.05 8-K will be filed about any of them. If one changes, our median says around December 26. We will update this piece either way.
Our question: when your team says “technical issue” in hour one, who decides when that statement changes, and how long would it take?
What we’d do first
- Run the outage and the investigation on two tracks from minute one. One team restores; another treats it as a possible incident.
- Preserve logs and images before restoring. DFARS 252.204-7012 requires keeping images at least 90 days after a report.
- Write the holding statement so it is still true on day 30. “We are investigating” holds. “This was not a cyberattack,” said before you know, may not.
- Know who decides materiality, and when. The SEC faulted Flagstar’s procedures for lacking guidance on “which disclosure decision makers were responsible” for that call.
- Log and review privileged changes. Who changed what, under which ticket, answers the insider question.
- Keep a live dependency map and change log in the ServiceNow CMDB, so a bad change and an intruder separate fast. Our Next-Gen GRC beta uses that graph to show affected systems in seconds.
A side note on where we fit: our work has supported the intelligence community, DHS, the Department of War (DOW) and Google, including cleared and restricted-network delivery, and our ServiceNow risk and efficiency assessment (instance health, technical debt, security posture, integrations) is now in implementation. That is the ground under this problem: telling a bad change from an intruder in the first hour, and keeping the record honest from hour one to day 30. Next-Gen GRC (beta), AusperRiskIQ™ and AccelSecure™ do that work. Compare notes with us.
Common questions
What usually happens after a company calls an outage a technical issue?
Does the SEC penalize companies for downplaying a cyber incident?
How fast do companies have to report a cyberattack?
Was any of this week’s outages an attack?
Who should decide when the first statement changes?
Sources
- SecurityWeek, Microsoft rules out cyberattack in outage, warns of phishing campaign (Nov 2026)Accessed Nov 17, 2026.
- BleepingComputer, Microsoft says months-old bug caused global Microsoft 365 outage (Nov 2026)Reports Microsoft's preliminary post-incident report: causes, start and end times, quotes. Accessed Nov 17, 2026.
- FAA, Nationwide Ground Stop: Questions and AnswersAccessed Nov 17, 2026.
- UC Today, Workday outage after disaster-recovery test (Nov 2026)Quotes Workday's status notice via Washington University IT, and Workday's restoration statement to ABC10. Accessed Nov 17, 2026.
- Fox Business, JPMorgan Chase systems recovering following hourslong nationwide technical outage (Nov 16, 2026)Accessed Nov 17, 2026.
- Al Jazeera, US bank outage: What caused Chase problems and Zelle payment delays? (Nov 17, 2026)Accessed Nov 17, 2026.
- HuffPost (Associated Press), United Airlines resolves tech issue after widespread system outage (Nov 16, 2026)AP text; apnews.com refused automated requests. Accessed Nov 17, 2026.
- SecurityWeek, Optimizely Vulnerability Exploited to Serve Malware on Major Websites (Nov 2026)Optimizely's status-page statement; Report URI's counts and timeline. Accessed Nov 17, 2026.
- The Hacker News, Hijacked Optimizely Scripts Served Card Skimmer and iOS Exploit Kits (Nov 2026)Crypto received by the attacker; delivering sites not necessarily compromised. Accessed Nov 17, 2026.
- ITIC, 2024 Hourly Cost of Downtime Report Part 1Accessed Nov 17, 2026.
- The Record, Four cyber companies fined for SolarWinds disclosure failures (Oct 22, 2024)SEC orders against Unisys, Avaya, Check Point and Mimecast: penalties, 'negligently minimized', SEC officials' quotes. sec.gov refused automated requests. Accessed Nov 17, 2026.
- Harvard Law School Forum on Corporate Governance, SolarWinds Dismissed: What the SEC's U-turn Signals for Cyber Enforcement (Dec 7, 2025)July 18, 2024 partial dismissal; November 20, 2025 joint stipulation to dismiss the rest. Accessed Nov 17, 2026.
- Debevoise & Plimpton, Lessons Learned: One Year of Form 8-K Material Cybersecurity Incident Reporting (Feb 11, 2025)Item 1.05 and Item 8.01 counts before and after the May 21, 2024 staff statement; Flagstar 8-K, amendment and SEC order. Accessed Nov 17, 2026.
- Holland & Hart, SEC issues first-ever enforcement action for failure to disclose a data breach, obtaining $35 million penalty (2018)Summary of the SEC's Yahoo (Altaba) order: December 2014 discovery, September 22, 2016 disclosure. Accessed Nov 17, 2026.
- Willkie Farr & Gallagher, SEC Fines Yahoo $35 Million for Failure to Disclose 2014 Data Breach (Apr 27, 2018)Order issued April 24, 2018; $350 million reduction in the Verizon price. Accessed Nov 17, 2026.
- Help Net Security, Former Uber CSO convicted for concealing data breach, theft from the authorities (Oct 6, 2022)Quotes the Justice Department: hackers emailed the CSO on November 14, 2016; disclosure in November 2017. Accessed Nov 17, 2026.
- ABC7 San Francisco, Uber's concealed data breach affects 57 million users (Nov 22, 2017)Uber 'revealed on Tuesday' (November 21, 2017); CEO's statement. Accessed Nov 17, 2026.
- TMJ4 (CNNMoney), Equifax executives sold stock before data breach was announced (Sep 2017)Equifax found out about the incident on July 29. Accessed Nov 17, 2026.
- CFO.com (Reuters), Former Equifax exec accused of insider trading (Mar 14, 2018)Public announcement September 7, 2017; SEC charge; internal 'cover story'. Accessed Nov 17, 2026.
- Insurance Journal (Bloomberg), UnitedHealth Blamed 'Nation-State' Threat in Hack That Disrupted Pharmacy Orders (Feb 23, 2024)Accessed Nov 17, 2026.
- Healthcare Dive, Change Healthcare cyberattack (Mar 1, 2024)First reported the outage February 21; confirmed AlphV/Blackcat on Thursday, February 29. Accessed Nov 17, 2026.
- The Record, 'Substantial proportion' of US had data stolen in Change Healthcare ransomware attack (Apr 23, 2024)UnitedHealth's April 22 statement and ransom payment confirmation. Accessed Nov 17, 2026.
- The Record, Okta apologizes for waiting two months to notify customers of Lapsus$ breach (Mar 28, 2022)Accessed Nov 17, 2026.
- The Record, Okta says two customers breached during January security incident (Apr 21, 2022)Accessed Nov 17, 2026.
- BleepingComputer, Okta confirms 2.5% customers impacted by hack in January (Mar 22, 2022)Accessed Nov 17, 2026.
- BleepingComputer, MGM Resorts ransomware attack led to $100 million loss, data theft (Oct 6, 2023)MGM disclosed a cybersecurity issue on September 11, 2023. Accessed Nov 17, 2026.
- FOX5 Las Vegas, MGM estimates $100 million loss due to cyberattack (Oct 5, 2023)Form 8-K filed Thursday, October 5, 2023; customer data taken. Accessed Nov 17, 2026.
- Windows Central, Microsoft's security culture was inadequate, says Cyber Safety Review Board (Apr 2024)Quotes the board: the September 6, 2023 root-cause post, acknowledged inaccurate in November 2023, updated March 12, 2024. Accessed Nov 17, 2026.
- The Record, DHS blames 'cascade of security failures at Microsoft' for China hack on US government (Apr 3, 2024)Microsoft relied on an initial notification from the State Department. Accessed Nov 17, 2026.
- FAA, FAA NOTAM Statement (Jan 11 and Jan 19, 2023)Accessed Nov 17, 2026.
- ABC17 News (CNN), More than 8 million Cash App Investing customers potentially impacted by data breach linked to former employee (Apr 7, 2022)Accessed Nov 17, 2026.
- Michael Tsai, Former Employee Downloaded Cash App Account Info (Apr 18, 2022)Quotes Block's April 4, 2022 8-K: download on December 10, 2021, 'recently determined'. Accessed Nov 17, 2026.
- TechCrunch, Faulty CrowdStrike update causes major global IT outage (Jul 19, 2024)Accessed Nov 17, 2026.
- Cloudflare, Cloudflare outage on November 18, 2025Accessed Nov 17, 2026.
- NPR, Southwest will pay a $140 million penalty for 2022 meltdown (Dec 18, 2023)Accessed Nov 17, 2026.
- SEC, Cybersecurity Risk Management, Strategy, Governance, and Incident Disclosure, final rule, 88 FR 51896 (Aug 4, 2023)GovInfo text of the Federal Register. Item 1.05, its instructions and the Attorney General delay in Item 1.05(c). Accessed Nov 17, 2026.
- US Department of Justice, Material Cybersecurity Incident Delay Determinations (Dec 12, 2023)Accessed Nov 17, 2026.
- eCFR, 12 CFR 53.3, Notification (OCC computer-security incident rule)Read through the eCFR renderer API. Accessed Nov 17, 2026.
- OCC, Federal Reserve and FDIC, Computer-Security Incident Notification Requirements, final rule, 86 FR 66424 (Nov 23, 2021)GovInfo text. 36-hour clock, May 1, 2022 compliance date, confidentiality of notices. Accessed Nov 17, 2026.
- Acquisition.gov, DFARS 252.204-7012 Safeguarding Covered Defense Information and Cyber Incident ReportingAccessed Nov 17, 2026.
- eCFR, 32 CFR 117.8, Reporting requirements (NISPOM), paragraph (f) CDC cyber incident reportsRead through the eCFR renderer API. Accessed Nov 17, 2026.
Updates
- Nov 18, 2026. Added a figure of the nine cases by days to the fuller story. No text or data changed.
- Nov 17, 2026. Reframed the same day around one question: could any of this week's outages be an attack, an insider or outdated software? Added the reporting clocks (SEC, bank, DFARS, CIRCIA, FedRAMP), the national security delay, past cases and a dated forecast. The dependency-map and cost material is shortened.
- Nov 17, 2026. Reworked the same day around what actually happens after a ‘technical issue’ statement: nine verified cases with the lag from first word to admission (median 40 days), the SEC’s October 2024 orders for minimizing, a step-by-step walkthrough and a new forecast. The reporting rules are cut to one paragraph; FedRAMP and CIRCIA detail is removed.
- Nov 17, 2026. Reworked the same day around what actually happens after a ‘technical issue’ statement: nine verified cases with the lag from first word to admission (median 40 days), the SEC’s October 2024 orders for minimizing, a step-by-step walkthrough and a new forecast. The reporting rules are cut to one paragraph; FedRAMP and CIRCIA detail is removed.
- Nov 17, 2026. Reworked the same day around what actually happens after a ‘technical issue’ statement: nine verified cases with the lag from first word to admission (median 40 days), the SEC’s October 2024 orders for minimizing, a step-by-step walkthrough and a new forecast. The reporting rules are cut to one paragraph; FedRAMP and CIRCIA detail is removed.
- Nov 17, 2026. Reworked the same day around what actually happens after a ‘technical issue’ statement: nine verified cases with the lag from first word to admission (median 40 days), the SEC’s October 2024 orders for minimizing, a step-by-step walkthrough and a new forecast. The reporting rules are cut to one paragraph; FedRAMP and CIRCIA detail is removed.
- Nov 17, 2026. Reworked the same day around what actually happens after a ‘technical issue’ statement: nine verified cases with the lag from first word to admission (median 40 days), the SEC’s October 2024 orders for minimizing, a step-by-step walkthrough and a new forecast. The reporting rules are cut to one paragraph; FedRAMP and CIRCIA detail is removed.
- Nov 17, 2026. Reworked the same day around what actually happens after a ‘technical issue’ statement: nine verified cases with the lag from first word to admission (median 40 days), the SEC’s October 2024 orders for minimizing, a step-by-step walkthrough and a new forecast. The reporting rules are cut to one paragraph; FedRAMP and CIRCIA detail is removed.
Share on LinkedInFollow AusperSubscribe by RSS
Related reading
Working on this now?
Tell us where your program stands and we'll tell you what we would do next.
Talk to Ausper