Isora GRC
Day 8 after signup
FAA Halts Departures Nationwide, Microsoft Outage Disrupts Security Tools, and FedRAMP Clarifies Migration Reporting
Plus: Fireworks AI exposes Uber and Notion data, 5 more states join the Hims & Hers lawsuit, and United Airlines restricts AI agents.
Why it works
- Group related stories under a clear topic heading so readers can scan a broad roundup.
- Explain the timeline and practical implications of each incident, rather than stopping at the headline.
How it is built
- Edition heading
- Newsletter introduction
- Incident news section
- Detailed story breakdowns
- Security implications
Email copy
November 2026 Edition Howdy there! Welcome back to the InfoSec GRC Brief from SaltyCloud, your go-to source for the latest insights on governance, risk, and compliance (GRC) in information security. Let’s get into it. Cyber Incidents & Risk Implications FAA Halts Departures Nationwide After Communication Problems On November 13, the Federal Aviation Administration (FAA) halted departures at airports nationwide after communication problems affected multiple Air Route Traffic Control Centers. The ground stop held aircraft at their departure airports. Airlines said flights already in the air would continue, while the FAA said inbound international flights would be handled individually. The FAA also said departures were halted until further notice while its technicians investigated. In a separate statement, the agency described a temporary telecommunications outage, said the ground stop was precautionary, and reported that every flight had been accounted for. An internal Alaska Airlines message similarly described communication and radar problems. The disruption affected hundreds of flights, with 11,000 flights scheduled to depart U.S. airports after 4 p.m. Eastern that day. Meanwhile, as crews reach their daily duty-hour limits, prolonged stops can also compound delays. The last nationwide ground stop occurred in January 2023, when a failure in the system used to distribute notices to pilots interrupted departures. Microsoft 365 Outage Disrupts Security Tools Microsoft’s November 12 outage continued into November 13, disrupting email and the security and compliance services connected to it. In an earlier update, Microsoft attributed the disruption to an issue introduced during a network capacity upgrade that surfaced after a subsequent network change. The company described the incident as technical and unrelated to cyberattacks or AI agents. But the affected services extended beyond Outlook and Exchange Online: Defender XDR portal pages could fail to load, while some Defender for Office 365 policy evaluation and enforcement experienced delays or failures. Intune device enrollment, check-ins, and compliance policies were intermittently affected. Purview disruptions included data loss prevention, auto-labeling, audit searches, eDiscovery searches and exports, and access to protected content. Most core Teams calls, meetings, and chats stayed functional, while Exchange-dependent calendar features were affected. Direct access to files stored in SharePoint also remained available. In its November 13 update at 2 p.m. Pacific, Microsoft reported sustained recovery and said most affected scenarios had been addressed. However, the company is still monitoring the backlog of email messages and dependent services before declaring the incident resolved. Fireworks AI Breach Exposes Uber and Notion Data Uber confirmed that a breach at AI provider Fireworks AI exposed driver information, including driver’s license details. In its November 10 notification letter, Uber said a service provider reported compromised internal credentials on October 9. Uber then disconnected the provider and confirmed unauthorized access to Uber data on October 13. Notion also disclosed that the incident exposed AI chat transcripts used by its Insights feature, which analyzes customers’ AI usage. Its November 12 advisory says fewer than 1% of workspaces were affected. But the assessed scope changed over several days: November 2: Fireworks alerted Notion to a dataset initially identified as synthetic testing data. November 3–4: Notion disconnected from Fireworks and deleted its data from the provider. November 6–9: Fireworks reported potential customer-data exposure, confirmed the affected dataset, and Notion notified customers. Most affected transcripts lacked user or workspace labels and contained no tool-call results, but the conversations themselves could include identifying information. On November 11, Notion subsequently found exposed cr