← All rangesThe Range · Application Security · Analyst level

Somebody Else’s Invoice

Not every time, and never the same stranger

You are the application security engineer on call. It is 11:10. Support has three tickets that sound like a bug, engineering has already said it is not them, and one customer has posted a screenshot.

SEC-2291 · priority highSupport escalations · 11:10

"Three customers this morning say the Billing page showed somebody else’s name, address and last invoice. For two of them it went away on its own a few minutes later. Engineering cannot reproduce it and say nothing in yesterday’s release touches billing. One customer has posted a screenshot on social media."

Before you start: how this works

01One objective at a timeYou are always told, in one sentence, what you are trying to establish right now. Only the actions that serve it are shown, and you can open the full list whenever you like.

02Time passesEvery action costs minutes in the story. Nothing is on a real-world timer, so think as long as you like, but the minutes inside the incident have consequences in it.

03Some things cannot be undoneWrong moves make the incident bigger, not just lower-scoring. This one can reach CRITICAL, where the run ends and somebody more senior takes it off you.

04Mistakes are the lessonEvery wrong turn is written up at the end with what it cost and what the better move was. Finish the range (any outcome) and its interview pack unlocks.

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.

Somebody Else’s Invoice · SEC-2291 · priority high

Wall clock: 11:10
Time spent: 0m
Situation: ·
Severity: ·

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.