Existing methods for providing developers security guidance don’t work well with agile project workflows, leading to security requirements being overlooked. Instead, convert the requirements to security user stories and embed them in developers' backlogs to make security guidance more developer and agile friendly.
Before You Start
Common Pitfalls and Keys to Success
Step 1 of 3: Identify Security Requirements Suited for Translation to User Stories
Step 2 of 3: Write Security User Stories and Acceptance Criteria
Step 3 of 3: Review and Update the Security User Stories
Review Your Performance
Recommended by the Authors
©2020 Gartner, Inc. and/or its affiliates.
All rights reserved.
Gartner is a registered trademark of Gartner, Inc. and its affiliates.
This publication may not be reproduced or distributed in any form without Gartner’s prior written permission.
It consists of the opinions of Gartner’s research organization, which should not be construed as statements of fact.
While the information contained in this publication has been obtained from sources believed to be reliable, Gartner disclaims all warranties as to the accuracy, completeness or adequacy of such information.
Although Gartner research may address legal and financial issues, Gartner does not provide legal or investment advice and its research should not be construed or used as such.
Your access and use of this publication are governed by Gartner’s Usage Policy.
Gartner prides itself on its reputation for independence and objectivity.
Its research is produced independently by its research organization without input or influence from any third party.
For further information, see
Guiding Principles on Independence and Objectivity.