Posted in GRC
It's not always a conspiracy. It's the weekend, so I'll keep this short. In one week, Microsoft 365 went…
Daniel O. — Senior Cybersecurity Consulting Engineer | EDR/XDR · Zero Trust · Architecture & Engineering | CISSP · CCSP · GIAC
It's not always a conspiracy.
It's the weekend, so I'll keep this short.
In one week, Microsoft 365 went down, the FAA called a nationwide ground stop, Chase online banking fell over and dragged outage reports for other big banks along with it, and NSANet went wobbly. The comment sections had it figured out. Coordinated attack, obviously.
The explanations so far are a software bug at Microsoft, legacy equipment at the FAA, a software bug at Chase, and scheduled maintenance at the NSA. Four boring causes in four different places.
If you've done this long enough, you've caused one of these yourself.
Not everything is related. Occam's razor doesn't say coincidence always wins. It says the explanation needing the fewest extra assumptions wins. Four large, complicated systems each having a bad day takes far fewer assumptions than one adversary quietly owning all of them and picking the same week to show it.
If real evidence turns up, I'll change my mind. Until then, coincidence is the cheaper bet.
This is something I should repost every 3-6 months, because it's evergreen advice we all forget from time to time. I'll just have to pick new examples.
Have a great weekend.

4 reactions · 0 comments