|
In the last few days, major systems have gone down or been hit, one after another. Some were outages. Some were breaches. And your business runs on the same kind of platforms.
On Thursday, Nov. 12, Microsoft 365 went down. Outlook, Teams, Word, Excel, SharePoint, OneDrive, and Copilot were among the services affected, The Guardian reported the next day. The disruption began Thursday and stretched into Friday. Microsoft’s preliminary report, covered by Ars Technica, puts the incident at just under 24 hours. It ran from Nov. 12 at 16:20 UTC to Nov. 13 at 16:10 UTC, with extra monitoring through Nov. 14. Microsoft said this was a technical issue and was unrelated to a cyberattack. Three things combined: a months-old bug in its cloud gateway, a shift of Teams traffic onto the same gateway that handles Exchange Online, and reduced server capacity. Together they froze more than 80 percent of the affected gateway servers. CNBC reported that Microsoft said it did not suspect malicious activity.
The next afternoon, the FAA issued a nationwide ground stop. The agency’s questions and answers page, dated Nov. 15, says a technical problem at about 3:30 p.m. ET on Friday, Nov. 13, led to the stop. Air traffic resumed at 8:15 p.m. the same day. Legacy equipment became unstable after data flooded the network, at a rate of about 1,000 connection attempts every four to five seconds. That disrupted aircraft communications and radar feeds. The FAA points to work by its network provider, L3Harris, including a new router at a radio site in El Dorado, Arkansas, and a radar site in Amarillo, Texas. Instability showed up at 17 of 22 Air Route Traffic Control Centers. The FAA said that, based on all available evidence, it had no indication this was a cyberattack or an outside actor. Transportation Secretary Sean Duffy said the same, as Reuters reported on Nov. 14.
And it kept going. On Friday, Nov. 13, Workday took its production systems into maintenance after disaster-recovery services unexpectedly connected to live production databases. That comes from a company notice university IT teams posted the same evening. WUSA9 reported on Saturday that Workday said the outage was unrelated to a cybersecurity incident, and that service had been restored by 11 a.m. ET.
Then on Monday, Nov. 16, United Airlines had a system outage that delayed some departing flights. The airline told CNN and the Associated Press there was no indication it was a cybersecurity-related issue. The same day, JPMorgan Chase told the Associated Press that a temporary software bug in an on-premise hardware system was causing trouble with some transactions, and that it was not cyber-related. The BBC reported that customers at several other U.S. banks also saw problems. Chase said other banks may have been affected where they were party to a transaction, though it said this was not a systemic issue.
So the outages were technical failures. The attacks were happening too.
On Nov. 16, researchers at Report URI, led by Scott Helme, found malicious code in files belonging to 178 organizations that use Optimizely, a website testing tool. Optimizely confirmed to BleepingComputer that an unauthorized party exploited a vulnerability in its Experimentation signup flow and injected JavaScript into some customer projects. The affected sites included CNN, the BBC, Fox News, Zoom, Salesforce, and GitLab. BleepingComputer independently confirmed the malicious script loaded, or tried to load, on a number of those sites. The way in was a third-party script running on those websites. That script was used to reach visitors, and the companies’ own servers were never broken into. The injected code was built to swap cryptocurrency wallet addresses, skim payment card details, and load exploit kits aimed at some iPhones and iPads. Optimizely says it has fixed the vulnerability, removed the injected code, and notified affected customers.
In late October and early November, Japan Airlines, Cathay Pacific, Thai Airways, Singapore Airlines, Korean Air, Asiana, and Malaysia Airlines all disclosed a booking-data incident at Amadeus, the travel-technology firm that runs reservation systems for airlines. The Record reported the airline notices on November 4. Cathay Pacific’s own notice, dated October 30, said unauthorized access to reservation data in Amadeus systems took place between August 2023 and September 2026. Around 53,000 Cathay bookings were affected. Thai Airways, in a November 9 notice, put its figure at about 60,529 passenger records. The airlines said payment data was not accessed and their own systems were not affected. The opening sat with a vendor they relied on.
On November 2, GitBook, a documentation platform many teams use for internal and public docs, said an attacker used a flaw in its sign-in flow to create staff sessions, then reached internal code and a cloud API key. GitBook’s official postmortem, published November 4, says customer API tokens and integration secrets were accessible. The app was taken offline for about 16 hours while every secret was rotated. GitBook said billing information and passwords were not compromised.
Different causes, same lesson
None of this was one event. But the run of it is hard to ignore. Email. Cloud tools. Vendors. Hosting. The accounts that hold your pages and your payouts all sit on systems like these. You cannot stop a provider from going down. You can close the doors you hold.
You hold more doors than you think
If you run pages and sites, you hold a lot of access. Facebook pages and Business Manager. Ad accounts. Hosting and domain registrars. Email. Payout and bank accounts. The AI tools you draft with. One weak login can open the rest.
Do this tonight
Work through every place you have access, one group at a time.
Facebook and Meta: start here
Turn on two-factor authentication with an authenticator app or a security key. A text message is easier to intercept. Open Business Manager and review every admin and partner. Remove people who no longer need access. Turn on login alerts.
Google and Gmail: go past the password
Set up a passkey. Turn on 2-Step Verification. Run Google’s Security Checkup. Review third-party apps that have access to your account, and revoke anything you do not recognize. If you are a high-risk target, look at Google’s Advanced Protection Program.
Other email: make sure recovery is still yours
Turn on two-factor authentication. Check the recovery phone and recovery email, and make sure you still control both.
Hosting and domains: lock the front door
This covers hosting, servers, your CDN, and your domain registrar. Turn on two-factor authentication on every panel. Lock the domain at the registrar. Use SSH keys instead of passwords where you can. Rotate API tokens. Confirm you have backups that live somewhere other than the same server.
AI tools like Grok and ChatGPT count too
Turn on two-factor authentication. Review connected apps and revoke anything you do not use.
Banks and payouts: watch the money
This covers banks, payment processors, and ad payouts. Turn on two-factor authentication. Turn on transaction alerts. Set limits where the account allows it.
Your phone number is a login too
Use a password manager, with a unique password for every account. Treat your recovery phone and recovery email as assets, and lock those down too. Call your mobile carrier and ask for SIM-swap protection, so someone cannot steal your number and reset your logins.
Block out time tonight and work down the list. Every group, before you close the laptop. If you run a bigger operation, book a call with the founders and we’ll walk through it with you.
|