Abuse Cases and Misuse Cases
What you'll learn: How to model attacker behavior through abuse cases to proactively identify security weaknesses before implementation.
Understanding the Concept
While traditional use cases describe how legitimate users interact with your system, abuse cases (also called misuse cases) flip the script: they describe how an attacker might exploit your system's features. This approach helps you think like an adversary during the design phase, not after deployment.
Think of it like this: when designing a bank vault, you don't just plan how tellers will access it—you imagine how thieves might break in, so you can add the right defenses upfront.
How Abuse Cases Work
An abuse case documents:
- The threat actor (insider, external attacker, automated bot)
- Their goal (steal data, disrupt service, escalate privileges)
- The functionality they exploit (login system, file upload, API endpoint)
- The attack technique (credential stuffing, path traversal, excessive API calls)
For example, if you're building a file upload feature (legitimate use case: "User uploads profile photo"), your abuse case might be: "Attacker uploads malicious executable disguised as image to gain remote code execution."
From Abuse Cases to Security Requirements
Each abuse case directly informs security requirements:
- Abuse case: "User floods API with requests" → Requirement: Rate limiting per user/IP
- Abuse case: "Admin credentials stolen via phishing" → Requirement: Multi-factor authentication mandatory for admin accounts
- Abuse case: "Attacker modifies IaC templates in CI/CD" → Requirement: Code review and approval gates for infrastructure changes
This connects perfectly to the Security Requirements Elicitation process you've already learned—abuse cases are a structured way to discover non-obvious security needs.
Key Takeaway: Abuse cases transform "what could go wrong" into actionable security requirements by systematically modeling attacker perspectives against every system feature before you build.