Emergency playbooks
Pick the situation that matches. Each playbook tells you what to do right now, what not to do, who to tell, and what to save.
Start here
Act in the first 10 minutes
HIGHMy password leaked
One leaked password becomes ten hacked accounts if you reuse it.Short version: Make a brand-new password, change it everywhere you reused it (email first), add a second lock, then check the account for leftovers.
Act in the first 5 minutes
CRITICALMy API key leaked
A leaked key lets a stranger spend your money. Cancel it first, investigate second.Short version: Cancel the key now, even if it breaks something. Then find out what it did, hunt for backdoors the attacker made, and replace it with a smaller, safer key.
Act in the first 10 minutes
CRITICALSomeone got into my account
Take the account back, sign the intruder out everywhere, then look for what they left behind.Short version: Reset from a clean device, sign out of everything, then check the sneaky stuff: extra MFA devices, forwarding rules and connected apps.
Act in the first 5 minutes
CRITICALMy AI agent is wrecking my database
Tables vanishing, rows changing, an agent insisting everything is fine. Stop it, take its keys, then restore carefully.Short version: Stop the agent, take away its database keys, pause writes, snapshot what is left, then restore into a NEW database. Do not let it "fix" itself.
More situations
Act in the first 15 minutes
CRITICALMy database or storage might be open to the public
Close the door first, then work out who walked in.
Act in the first 10 minutes
WATCHI clicked a suspicious link or opened a strange file
Say so quickly. Speed matters more than embarrassment.
Act in the first 15 minutes
HIGHMy cloud or AI bill suddenly spiked
Treat an unexplained bill as a stolen key until proven otherwise.
Act in the first 5 minutes
HIGHMy AI agent did something I did not ask for
Stop it, take its keys away, then read what it actually did.
Act in the first 30 minutes
HIGHA package or extension I installed looks malicious
Remove it, then replace every secret it could have read.
Act in the first 15 minutes
HIGHMy site is under attack or behaving strangely
Slow the attack, protect what matters, and keep the logs.
Pause before you act
WATCHI got an urgent request to approve or pay something
Urgency is the tactic. Verify before you approve.
Act in the first 30 minutes
HIGHA laptop or phone with work access was lost or stolen
Lock the device and cut its access to your accounts.
Reply within the hour
WATCHA customer says something looks wrong with their account
Take it seriously, check quickly, and reply with facts.
Decide in 15 minutes
HIGHA change broke something. Should we roll back?
Compare the cost of the bad change with the cost of undoing it.
Within hours of confirming it
WATCHI need to tell customers what happened
Say what you know, what you do not, and what people should do.
Within a few days
INFOIt is over. Now we need to learn from it
Blameless, factual, and ending in a few real changes.
Need the exact steps for a specific platform?
The Platform help page (for tech people) links straight to the official guides for replacing keys and handling a break-in on AWS, Google, Microsoft, Supabase, Vercel, GitHub, Stripe, OpenAI, Anthropic and more.