<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Project Planning on Rietta Cybersecurity</title>
    <link>https://rietta.com/tags/project-planning/</link>
    <description>Recent content in Project Planning on Rietta Cybersecurity</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <copyright>1999-2026 Rietta Inc. All Rights Reserved.</copyright>
    <atom:link href="https://rietta.com/tags/project-planning/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>What is an Abuser Story (Software)</title>
      <link>https://rietta.com/blog/what-is-an-abuser-story-software/</link>
      <pubDate>Sun, 11 Oct 2015 22:35:36 -0400</pubDate>
      <guid>https://rietta.com/blog/what-is-an-abuser-story-software/</guid>
      <description>&lt;p&gt;I publicly speaking about how development teams and those who employ them should go about using user stories with security constraints and abuser stories as a security documentation tool. At this time there is not an entry on Wikipedia about it, so I am going to take a stab at writing it up for you here.&lt;/p&gt;&#xA;&lt;h2 id=&#34;what-is-an-abuser-story-in-software-development&#34;&gt;What is an Abuser Story in Software Development?&lt;/h2&gt;&#xA;&lt;p&gt;In software development and product management, an abuser story is a user story from the point of view of a &lt;a href=&#34;https://en.wikipedia.org/wiki/Adversary_(cryptography)&#34;&gt;malicious adversary&lt;/a&gt;. Abuser stories are used with agile software development methodologies as the basis for defining the activities that should be actively blocked or mitigated by the software and proven by automated regression testing.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
