Multi-factor stopped the password. It did nothing about the cookie that came after it. Once a person has signed in, the browser holds a session token, and whoever holds that token is that person until it expires.
Most of the cases on our desk this year started this way. Nobody cracked anything. A proxy page sat between the user and the real sign-in, passed the code along, and kept the token that came back.
What the token opens
It depends on how long your sessions last and what they can reach. In a sample week of testing on our own lab tenant, one token gave us the following, with no further prompt.
- The mailbox, including rules and delegates.
- Shared files the user could already open.
- The admin portal, if the user was an administrator.
- A way to register a new device, which outlives the token.
The password was never the prize. The session was.
What changes the answer
Shorter sessions for administrators help. So does binding sessions to a managed device. Hardware keys help most, because the key checks the address of the page and a proxy page fails that check.
When we respond, we revoke sessions before we reset passwords. Resetting a password does not end a session on every platform, and that gap is often where an attacker stays.




