Your goal: stop the spread in the right order, with the mechanism understood well enough to
cut it, the evidence kept, and a clear business call when containment costs the company a day.
How this works (about 30 minutes)
- You're on the security team at Pinterest. Marcus asks one incident question and goes deep. He
holds a made-up timeline and network: ask for what you need and he answers one line at a time.
- Follow-ups on how the spread works, your first moves, credentials, backups and recovery; one
curveball; then a trade-off turn on how much to cut.
- If you want to sketch the network or a timeline, say "can I use the notepad?" and Marcus puts
it up.
- No hints and no scores during the call. Your report comes after.
What scores well
- Asking what is known before acting: how many machines, how fast, which account, where the backups are
- How it spreads, in plain words, and a containment that cuts exactly that
- Contain first, keep the evidence, then scope, clear out, recover and learn
- Credentials and backups handled early, not as an afterthought
- A call on the big cut, with its cost to the business and a condition to reverse it
- Answers that say where they are going and land in a minute or two
Tips
- Take Security Coach · Vulnerabilities and Incidents first.
- Ask which account the attacker is using. It changes the first five minutes.