Abstract: We all know that User Stories capture goals from the user perspective along with their business value. On the flip side, how can we ensure we've thoroughly examined the ways in which hackers, criminals and adversaries can exploit those stories to get access to our most valuable resources: Our Data!
Abuser stories is a way to capture potential vulnerabilities in software systems, using the standard user story format. While user stories are written from a user perspective, abuser stories are written from an enemy or attacker’s perspective and describe the enemy’s mal-intent and motivation.
The session will look at the concept of Abuser Stories more in-depth. We will examine:
- How seemingly benign functional user stories can create vulnerabilities in our software, leaving lots of opportunity for our enemies to take advantage of our weaknesses.
- How to use the concept of abuser stories to shed some light on where these vulnerabilities can be introduced.
- How to craft a good abuser story.
- How to craft refutation criteria so that we can determine that the attack depicted by the abuser story is not possible.
- How to estimate and rank abuser stories.
Learning Outcomes: - The participants will take away:
- * An appreciation for how functional stories can introduce vulnerabilities we may not have thought of before
- * An understanding between a threat and a vulnerability
- * A way to capture predictable vulnerabilities that may be introduced into a system while coding features
- * How to estimate and rank abuser stories in the overall product backlog
