mythsthe appsMicrosoft Midnight Blizzard2024technology

everyone assumed:

a retired test tenant is harmless

what was actually true:

A retired environment is only harmless if its access retired with it.

how it happened

  1. whoAPT29password spraying
  2. the gaptest account, no MFAforgotten
  3. thenelevated grantinto corporate email
  4. the resultleadership mailboxesread for weeks
the gap that let it happen the result

what everyone assumed

Test and legacy tenants feel disposable, walled off from anything that matters, exempt from the controls that guard production. The assumption is that a non-production account is a non-consequential account.

what happened

From the legacy tenant the attackers found a legacy OAuth application that, against expectation, held elevated access into the corporate environment. That standing grant let them read email across senior leadership, security, and legal, slowly and quietly, for weeks.

step by step

  1. a legacy test account has no MFAThe attackers get in there.
  2. a forgotten OAuth app holds elevated accessIt reaches into the corporate environment.the assumption breaks here
  3. weeks of reading emailSenior leadership, security and legal mailboxes.
  4. January 2024Microsoft disclosesAttributed to APT29.

how it surfaced

In January 2024 Microsoft disclosed that the nation-state group APT29 had read corporate email from a small percentage of mailboxes, including senior staff, after entering through a no-MFA legacy test account and a forgotten OAuth app.

A retired environment is only harmless if its access retired with it.

A test tenant with a live OAuth grant into production is a production risk wearing a test label.

picture it at a company like yours

The company here is made up. The other two paths are not: they happened, and each links to the story.

your company
a normal dayYears ago someone set up a test account and a test app, then moved on.
the gap nobody seesThe test account has no two-step login, and the app has powerful access.access that outlives the job
  1. in this story
    the day it mattersAn attacker guesses the test account's password and finds the app.
    what it costs youThey read your leadership's email for weeks through a setup everyone forgot.
  2. or it goes like this
    howThe person logs back in from home, weeks after leaving.
    what leavescustomer lists and reportswho ends up with itthe former employee and whoever they work for next
    it happenedCash App / Block, 2022
  3. or it goes like this
    howThe forgotten account's password turns up in a breach dump.
    what leavesa working way into the networkwho ends up with ita ransomware crew
    it happenedColonial Pipeline, 2021

sources

  1. Microsoft Security Blog, 2024

← all myths

your turn

what you can do about it

  1. this week

    List old test tenants, legacy apps and OAuth grants, and what each can reach.

    You have test tenants, legacy apps, and old OAuth grants nobody has looked at since they were created. Some of them quietly reach into systems that matter. The inventory of forgotten grants and their scopes is exactly the surface Midnight Blizzard used, and it is yours to read.

  2. go deeper

  3. if you're not sure where to start

    Run the offboarding checklist on one leaver. It covers every account and token to close when someone leaves.

    open the checklist →

the letter · every two weeks

one access gap in your inbox, with the fix.

Every issue takes one way access creeps in, shows a real incident where it went wrong, and ends with one thing to check that week. Written for the people who run the tools, without a security team behind them.

  • 1one mechanism, explained plainly
  • 2one real incident, taken apart
  • 3one step you can take on Monday

get the next issue

One email every two weeks. Your address stays here and is never passed to vendors. One click to unsubscribe. Privacy.