Security

Culture Is a Control

On 2 April the US Cyber Safety Review Board (CSRB) published its review of the summer 2023 intrusion into Microsoft Exchange Online. In that intrusion, a China-linked actor known as Storm-0558 accessed the mailboxes of senior US and UK officials. The Board found the intrusion was preventable, and described a “cascade of avoidable errors”.

I won’t repeat the whole report. A few of its findings stood out to me:

  • A cryptographic signing key that should have been retired was still able to forge authentication tokens.
  • An engineer who joined through an acquisition had a compromised device that was later linked to the intrusion. That points to gaps in how acquired environments were brought into the company’s security processes.
  • Microsoft’s public explanation of how the key was stolen turned out to be a theory, and it wasn’t corrected for months.
  • The Board’s overall conclusion was that the company’s security culture was inadequate and needed an overhaul, led from the very top.

Why I Think This Matters Beyond Microsoft

In SRE we talk a lot about blameless post-incident reviews. Blameless doesn’t mean nobody is accountable. It means we look at the system — incentives, priorities, decision-making — rather than hunting for an individual to blame. That’s exactly what this report does, at the scale of a whole company.

A few things I’d take into any organisation:

  1. Security debt is real debt. Old keys, old trust relationships and old exceptions all add up, quietly, until they don’t.
  2. M&A integration is a security event. When you acquire a company, you inherit its identities, devices and habits.
  3. Transparency builds trust; correct the record quickly. If your public explanation turns out to be wrong, update it.
  4. Culture is a control. It doesn’t show up in an audit checklist, but it decides how every other control actually gets used.

More Information