Playbook: denial-of-service and traffic overload
Separate malicious traffic, flash demand, dependency failure, and capacity exhaustion while keeping communication and evidence intact.
Scope
For network, platform, application, provider, communications, and business teams handling severe service degradation.
Start with the situation, not the slogan
A playbook is a decision aid for tired people working with incomplete information. Playbook: denial-of-service and traffic overload therefore names owners, evidence, containment and exit criteria instead of pretending every incident follows a flowchart. Read it before the incident, tailor the contacts and systems, and exercise the awkward branches.
The first objective is shared situational awareness: what is known, who owns the incident, what business process is at risk, and which decision is due next. A chat channel full of competent people is not the same as command. Assign a coordinator and a note taker, even when the organisation is small enough for both to use the same kettle.
Not every overload is a DDoS attack, and aggressive blocking can harm legitimate users. The playbook prioritises observability, provider coordination, service protection, and reversible mitigation.
Composite scenario
How this usually reaches the desk
The playbook should activate when the team can establish its entry conditions, including: Baseline and current request rate, connection state, endpoints, sources, protocols, errors, latency, and resource saturation are visible. If the report remains ambiguous, open a low-severity record and time-box validation rather than ignoring it or declaring the end of civilisation. Escalate as evidence, privilege, spread or business impact increases.
This scenario combines common operational patterns; it is not presented as a report of one named incident.
What to look for
Begin with preserved, comparable evidence. One signal is rarely proof; use independent observations and a reliable timeline before declaring scope or intent.
Baseline and current request rate, connection state, endpoints, sources, protocols, errors, latency, and resource saturation are visible.
Confirm this condition from an authoritative source and note who supplied it. Mark assumptions as assumptions; they have an unfortunate habit of becoming facts in copied status updates.
Provider, CDN, DNS, network, hosting, and application contacts and escalation paths are current.
Identify the decision that depends on the information and the deadline for obtaining it. Evidence is most useful when it changes action rather than merely decorating the timeline.
Critical functions and acceptable degradation modes are defined.
Check coverage and retention before containment. If a source is unavailable, record the gap and use independent evidence rather than silently treating absence as innocence.
Working examples
Run it, read it, decide what changes
These examples use documentation addresses, test identities and bounded targets. Replace placeholders only inside systems you own or are explicitly authorised to operate. Read the expected result and next action before running the command; a successful command is evidence, not yet a conclusion.
Record live listeners without changing them
- Prerequisites
- Local administrator access; collect before rebooting if incident policy allows.
# Linux
sudo ss -lntup
# Windows PowerShell
Get-NetTCPConnection -State Listen |
Sort-Object LocalPort |
Select-Object LocalAddress,LocalPort,OwningProcessA list of listening addresses, ports and process identifiers appears.
`0.0.0.0` or `::` means all local interfaces; `127.0.0.1` is local-only. A PID is a lead that must be mapped to a signed binary or package.
Save the output, map unexpected PIDs to processes, then compare with firewall, container and port-forward configuration.
Verify end-to-end collection
- Prerequisites
- A host whose syslog is meant to reach the central platform.
marker="NMF_LOG_TEST_$(date -u +%Y%m%dT%H%M%SZ)"
logger -p auth.notice -t nmf-test "$marker"
printf '%s
' "$marker"A unique marker is emitted locally and printed for pasting into the central search.
Local command success proves only submission to the local logging path.
Search centrally, record arrival delay and parsed host/source fields, then alert when this scheduled canary stops arriving.
Add an upstream timeout
- Prerequisites
- An owned service calling a dependency.
const response = await fetch('https://dependency.internal/health', {
signal: AbortSignal.timeout(3000),
headers: {'X-Request-ID': req.id}
});The request either completes or aborts after about three seconds instead of waiting indefinitely.
A timeout without error handling may still produce a 500 storm. Three seconds is an example, not a universal value.
Handle timeout separately, return a safe degraded response, emit a metric and test dependency slowness in staging.
Response sequence
Read the whole sequence before starting. Several workstreams may run in parallel, but their evidence, authority and expected outcomes still need to be explicit. Every step below points back to a concrete example; use the example as implementation evidence, not as permission to operate outside the stated scope.
Operational judgement
Run the playbook as a checklist with judgement, not as a spell. For DDoS, Playbook and Availability, localise tenant names, log locations, provider contacts, legal thresholds, emergency credentials and business priorities. A generic document becomes operational only when the people on duty can find the required access without consulting the person currently on holiday.
Use a decision log separate from the task list. For each consequential action, note time, owner, evidence, choice, expected effect and observed result. This gives later reviewers something better than a reconstructed story and helps the next shift understand why a seemingly obvious action was delayed or rejected.
Handover
Make the result useful to the next person
Prepare the playbook package before an incident: primary and deputy owners, current contact routes, system inventory, evidence locations, delegated authority, provider escalation, legal and privacy triggers, secure communication, and emergency credentials. Keep a printable or otherwise independent copy where an identity or collaboration outage cannot hide it. Review contact details during exercises; telephone numbers appear to age faster than almost any cryptographic primitive.
For this playbook, the incident record should open with “Declare severity and compare current traffic and resources with baseline and recent changes.” and drive deliberately towards “Communicate status and recovery, then tune limits, autoscaling, architecture, and provider runbooks from observed evidence.” A shift handover must state confirmed facts, open hypotheses, business impact, containment already applied, evidence at risk, approvals pending and the next scheduled update. After closure, turn lessons into owned changes to controls, documentation and exercises. A lesson without an owner and a date is simply a well-written regret.
Validate before you close
Exit when service objectives are stable, temporary controls and customer impact are reviewed, evidence is retained, and recurrence thresholds and owners are updated.
Capture the test, the expected result and the observed result. Where a person or business owner must accept restored service, name them in the record. A green dashboard can confirm that a component is answering; it cannot confirm that invoices, identities or restored data are trustworthy.
Finish with a compact closure note: the original trigger, confirmed scope, evidence retained, controls changed, tests passed, known gaps, residual risk, and the people responsible for the remaining work. Schedule a review while the timeline is still fresh enough to challenge. The purpose is not to find a person to blame; computers already perform blame with admirable efficiency. The purpose is to make the next response faster, safer and less dependent on one person remembering where the useful log was hidden.
Common mistakes
- Running the playbook without assigning a decision owner and note taker.
- Containing too early or too late because evidence and business impact were not compared.
- Closing the incident without documenting recovery checks and follow-up owners.
These errors usually come from haste, unclear ownership or misplaced confidence. Build the safeguard into the runbook: a required evidence field, a second-person review, a rollback test or a specific exit criterion.
Questions people ask when the clock is running
Who may activate the playbook?
Define that locally before an incident. Help desk or monitoring staff should be able to open a record and escalate; containment authority may sit with incident command, service ownership or an executive depending on impact.
Must every step be completed in order?
No. Evidence, containment, communication and recovery often run in parallel. Keep dependencies explicit and do not let a later checkbox imply that an earlier decision was actually verified.
What is the exit condition?
Exit when service objectives are stable, temporary controls and customer impact are reviewed, evidence is retained, and recurrence thresholds and owners are updated. Residual risk, communication and improvement actions still need named owners even after service is restored.
Safety boundary
Use these steps only on systems you own or are explicitly authorised to assess. Preserve evidence, follow your organisation’s legal and regulatory obligations, and prefer reversible actions when the situation is not yet understood.
Primary references
- SP 800-61 Rev. 3: Incident Response Recommendations and ConsiderationsNIST
- Cybersecurity Framework 2.0NIST
Editorial status: first edition. Review the linked vendor documentation for product- and version-specific changes before acting.