This is a composite, anonymised case from Book 5 of our IAM Architecture Series. The details are changed, but the pattern isn't rare.
The timeline
Day 0. A mid-sized insurer runs one shared domain admin account across 40 servers. The password sits in a team wiki because "the vault is slow." It has no owner, isn't in the vault, and hasn't been reviewed in 14 months. A contractor gets phished at 14:02, and the attacker finds the wiki page within an hour. Then they log in from a device the company has never seen. No alert fires, because a domain admin logging in is normal.
Day 1. A new service account appears with domain-wide rights: svc-backup-audit. No ticket. No approval. It isn't in the inventory, because discovery last ran as a one-time project nine months earlier.
Day 2. Audit logging is switched off on three servers. The shared account bypasses the session broker, so nothing records the change.
Day 4. Credentials are dumped from memory, and a reused hash (pass-the-hash) opens two more servers. Every hop is a valid login, and every move looks like administration.
Day 11. An unusual outbound transfer trips a network alert. Not a single privileged-access alert fired in 11 days.
The 11-second problem
After the incident, someone finally timed the "slow" vault. The brokered path was 11 seconds slower than the direct one.
Eleven seconds bought eleven days of undetected access.
On paper, this company was compliant. It had a vault and a PAM policy, and the board had been told privileged access was vaulted. That was true for every onboarded account. It was false for the one that mattered.
What would have changed the ending
| Day | What happened | The control that breaks it |
|---|---|---|
| 0 | A standing admin password is stolen from a wiki | Vaulting + just-in-time elevation: no standing credential to steal |
| 0 | A login from a first-seen device | First-seen-device alerting for Tier 1 accounts |
| 1 | A shadow admin is created | Continuous discovery + alerting on new privileged accounts |
| 2 | Logging is disabled | Brokered sessions with recording, kept off the server |
| 4 | Pass-the-hash | Individual identities, brokered sessions, rotation after check-out |
PAM isn't a product you deploy. It's an architecture you finish.
Try this on your team
Can you name the human behind every privileged login from yesterday?
Tell me in the comments: on which day would your SOC have caught this? 0, 1, 2, 4 or 11?
The full case file and the 12-module PAM playbook:
Privileged Access Management, IAM Architecture Series Book 5









Top comments (1)
Some comments may only be visible to logged-in visitors. Sign in to view all comments.