Skip to content
Incident Response Plan Templates

PlaybookChecked 16 November 2026

DDoS attack incident response playbook

Download Word (.docx)Download PDF

Stages

  1. 1When to use this playbook
  2. 2Before you start: prerequisites
  3. 3Workflow
  4. 4Decision points
  5. 5Notices to check
  6. 6Exit criteria and follow-up

The template in full

1 When to use this playbook

Use this playbook when a website, application or network service becomes slow or unavailable because of a flood of traffic or requests.

2 Before you start: prerequisites

Complete these before an incident, as part of planning.

  • Normal traffic baselines are known.
  • Contacts at the internet provider, content delivery network and any DDoS mitigation service are on the contact sheet.
  • The service has redundancy, load balancing and a way to scale.
  • Communications for customers are ready, with a way to post status away from the affected service.

3 Workflow

Work in this order. Record each step and its time in the incident log.

  1. Confirm it is an attack: check for unavailability, network congestion, unusual traffic patterns, server crashes, high resource use and trouble reaching other services such as DNS.
  2. Classify the technique: volumetric, protocol or application. The response differs by type.
  3. Call the upstream provider or mitigation service and ask for filtering.
  4. Apply filtering at the edge: rate limits, blocks on known malicious sources, and a challenge for web requests where suitable.
  5. Keep customers informed through a channel that does not depend on the affected service.
  6. After the attack: assess the impact, restore services, do a post-incident analysis, fix what was found and update the plan.

4 Decision points

Stop at each of these and record the decision, the decider and the time.

Decision points
DecisionWho decidesInformation needed
Switch to a mitigation service or failover?Technical lead, executive sponsorAttack type, cost, time to switch
Is the attack covering something else?Incident leadOther alerts, access attempts during the attack
What do we tell customers?Communications leadImpact, expected recovery time

5 Notices to check

Open section 10 of the plan and confirm whether any of these start a notice clock.

  • A DDoS attack alone is an availability incident; check whether personal data was affected before treating it as a breach.
  • Check contract service levels and customer notice terms.

6 Exit criteria and follow-up

Close the playbook only when all of these are true.

  • Service restored to normal levels.
  • Traffic patterns back to baseline for [period].
  • The plan is updated with what was learned.

About this playbook

What is the incident response playbook for a DDoS attack?

CISA, the FBI and MS-ISAC's guide of 21 March 2024 sorts denial-of-service techniques into volumetric, protocol and application types. It lists symptoms including website unavailability, network congestion, unusual traffic patterns, server crashes and high resource use.

The NCSC's DoS guidance sets out four practices: understand your service, understand your defenses, create a response plan, and test your response. NIST adds that continuity planners may help plan responses to denial-of-service conditions.

Download the template

Free, no sign-up. Word (.docx, 3 KB): download. PDF (46 KB): download. Both files carry the same text as this page, edition 16 November 2026.

Sources

  1. CISA, FBI and MS-ISAC, Understanding and Responding to Distributed Denial-of-Service Attacks (21 March 2024)
  2. NCSC, Denial of Service (DoS) guidance
  3. NIST SP 800-61 Rev. 3, full text (April 2025)

Last reviewed 16 November 2026. Each source above was read that day.