Skip to content
Post Mortem

Playbook ยท Act in the first 15 minutes

My site is under attack or behaving strangely

Slow the attack, protect what matters, and keep the logs.

HIGHTake a breath. Do these in order.

How you might know

  • Sudden traffic spike or the site is very slow or down.
  • Pages changed that you did not change.
  • Unknown admin accounts or files.
  • A security advisory says software you run is being exploited.

Do this now

  1. Work out what you are seeing

    Is it a traffic flood (the site is overwhelmed), a defacement (pages changed) or a break-in (unknown accounts, files, or logins)? The response differs.

  2. Turn on your protection layer

    If you use a service like Cloudflare, turn on its stronger protection mode and rate limiting. Many hosts have a similar option.

  3. Restrict who can reach sensitive areas

    Put admin pages behind a login or limit them to known addresses. Disable features you do not need right now.

  4. Check what changed recently, and for signs of a break-in

    Look at recent changes, updates and new users. If you find admin users or files you did not add, treat it as a break-in, not a traffic problem: take the server out of public view, do not just clean it, restore from a backup you know is clean, and replace every secret key the server could read.

  5. Apply the fix or workaround

    If a known flaw is involved, update the software or follow the vendor's temporary workaround.

  6. Tell your host and your people

    Hosting support can often see attack traffic and help block it. Tell your team and, if customers are affected, post a short status update.

Do not do this

  • Do not reboot everything before saving logs.
  • Do not publish guesses about the cause.
  • Do not restore from backup without checking the backup is clean.

Who to tell

  • Hosting provider support
  • Whoever is in charge
  • Customers if service or data is affected

What to save before you clean up

  • Web server and application logs
  • CDN or firewall logs
  • A snapshot of the affected server

In the next 24 hours

  • Patch the root cause.
  • Change passwords and keys for admin access.
  • Write a short factual update for customers.

Official help for the platforms involved

Links open each provider's own documentation, so you do not have to search for it.

What to write in the post mortem afterwards

  • Entry point
  • Time to detect
  • What reduced the impact
  • What would have shortened the response

Finished this one?

Add it to What I learned and earn 30 Trust. You can open your list from the badge at the bottom of the page.