Course contentsShow
← Security
Lesson 71 of 3,0522. Threat Modeling FundamentalsFree lesson

Misuse and Abuse Cases

Document negative scenarios where actors deliberately misuse system features to identify vulnerabilities in requirements.

Misuse and Abuse Cases

What you'll learn: How to discover security vulnerabilities by imagining how attackers might deliberately misuse legitimate system features.

What Are Misuse and Abuse Cases?

While normal use cases describe how legitimate users should interact with your system, misuse cases and abuse cases flip the script. They document how malicious actors might deliberately twist, exploit, or abuse your system's features to cause harm—even when those features work exactly as designed.

Think of a fire extinguisher: its use case is putting out fires. A misuse case might be someone using it as a weapon to assault others. The extinguisher works perfectly, but its legitimate function gets weaponized.

Why This Matters for Threat Modeling

When building threat models (using frameworks like STRIDE or LINDDUN that you've learned), misuse cases help you think like an attacker. They force you to ask: "What could go wrong if someone intentionally abuses this feature?"

For example:

  • Legitimate feature: Password reset via email
  • Misuse case: Attacker floods a victim's inbox with password reset requests, causing denial of service or hiding a real attack notification

By documenting these negative scenarios during requirements gathering, you identify vulnerabilities before they're coded into your system. This aligns with treating security as a non-functional requirement throughout the SDLC.

Creating Misuse Cases

Start with your normal use cases, then brainstorm:

  • How could an insider with legitimate access abuse this?
  • Could an external attacker twist this feature for reconnaissance or attack?
  • What happens if someone uses this feature at massive scale or with malicious inputs?

Key Takeaway: Misuse and abuse cases reveal how legitimate system features can become attack vectors, allowing you to build defenses into requirements before vulnerabilities become exploits.