CyberKit

Denial of Service

Also called DoS, DDoS.

Overwhelming or crashing a service to make it unavailable.

What it is

An attack on availability that floods, exhausts, or crashes a system or service so legitimate users cannot reach it. Distributed variants coordinate many sources at once to amplify the effect.

Why it matters

Denial of service directly impacts availability and is sometimes used as a distraction to mask a concurrent intrusion, so traffic anomalies deserve scrutiny beyond the outage itself. Volumetric spikes and unusual source distributions are the core signals.

In practice

A flood of junk traffic knocks a public portal offline, and investigators later find it coincided with quiet data theft on another system.

What to look for

  • Traffic spikes from many sources to one service.
  • Resource exhaustion such as full connection tables or maxed CPU.
  • Application errors and timeouts without a matching deploy or change.

Common mistake

Only planning for volume. Some attacks target one slow, expensive request rather than bandwidth.

Practice it nearby

CyberKit has no tool for this term itself. These are the closest places to practice it.

In the field

Well-known tools where this shows up on the job. They are listed to show the landscape, not as a recommendation.

  • Palo Alto Networks NGFW Commercial

    A next generation firewall that enforces policy by application and user and logs each session.

  • Cloudflare WAF Commercial

    Filters web traffic at the edge before it reaches the application.

  • Suricata Open source

    Can run inline as an IPS to block traffic that matches its rules. Our notes.

  • Snort Open source

    A long standing open source IDS and IPS with a large public rule set.

Read next

  • Data Destruction: Irreversibly deleting or corrupting data to cause harm.
  • Defacement: Altering public-facing content to send a message or signal control.
  • Cryptojacking: Hijacking a victim's compute to secretly mine cryptocurrency.

Sources