Impossible Travel
A service account does not go on vacationYou are on the identity and access team, on call. It is 03:55. The alert has been open for fifteen minutes, and the treasury export the account runs fires again at 06:00.
"Impossible travel: svc-treasury@corp.example. Successful sign-in 02:00 from 192.0.2.20 (head office region). Successful sign-in 03:12 from 203.0.113.77 (country not in operating list). Note: service account, may be cloud egress."
You are judged on three things. Accuracy: did you work out what was really wrong and deal with it. Economy: how directly you got there, in the incident’s own minutes. Integrity: what you preserved, who you told, and whether you claimed anything you had not established. The third is the one people fail.
Finish it, with any outcome, and its interview pack unlocks: 4 questions with weak, good and strong answers, the follow-up, and the trap.
Choose one
Incident log
Everything you do, in order. This is what a real handover is written from.
Nothing has happened yet.
How bad is it
Wrong moves push this up. Containing the problem pushes it back down.
What you have established
Facts you have actually observed, not guesses.
Nothing yet.