NEW350+ rooms now have a live terminal, so you can learn by typing the commands, right in your browser.Learn in a live terminal. 350+ rooms.Try a lab♥ Codelivly is 100% free, no paywall. If it helped you, chip in to keep it running.100% free. Help keep it so.Support us
[>_] ROOM · Cybersecurity
Security Requirements and Abuse Cases
Master the art of defining security requirements and modeling abuse cases to proactively design resilient, secure software architectures.
Room tasks
1What Are Security Requirements and Why Do They Matter
2Writing Abuse Cases and Misuse Stories
3OWASP ASVS Requirement Levels
4Turning Requirements into Testable Acceptance Criteria
5Guided Lab: Writing Security Requirements for a User Story
Security Requirements and Abuse Cases | Codelivly
Frequently Asked Questions
What is an abuse case?
An abuse case describes how an attacker could misuse a feature, just as a use case describes legitimate behavior. Modelling them early reveals threats so you can add requirements that block them.
How do you write good security requirements?
State them clearly, make them testable and tie them to a risk, for example requiring multi-factor authentication for admin actions. Standards such as OWASP ASVS provide useful starting points.
How do abuse cases fit into agile teams?
Add them to user stories as negative scenarios and acceptance criteria during refinement. The Codelivly room on abuse cases is free and shows hands-on how to do this in practice.