Agile Application Security Enabling Security in a Continuous Delivery Pipeline Laura Bell, Michael Brunton-Spall, Rich Smith, and Jim Bird Agile Application Security by Laura Bell, Michael Brunton-Spall, Rich Smith, and Jim Bird Copyright © 2017 Laura Bell, Rich Smith, Michael Brunton-Spall, Jim Bird All rights reserved Printed in the United States of America Published by O’Reilly Media, Inc., 1005 Gravenstein Highway North, Sebastopol, CA 95472 O’Reilly books may be purchased for educational, business, or sales promotional use Online editions are also available for most titles (http://oreilly.com/safari) For more information, contact our corporate/institutional sales department: 800-998-9938 or corporate@oreilly.com Editor: Courtney Allen Production Editor: Colleen Cole Copyeditor: Amanda Kersey Proofreader: Sonia Saruba Indexer: Wendy Catalano Interior Designer: David Futato Cover Designer: Karen Montgomery Illustrator: Rebecca Demarest September 2017: First Edition Revision History for the First Edition 2017-09-08: First Release See http://oreilly.com/catalog/errata.csp?isbn=9781491938843 for release details The O’Reilly logo is a registered trademark of O’Reilly Media, Inc Agile Application Security, the cover image, and related trade dress are trademarks of O’Reilly Media, Inc While the publisher and the authors have used good faith efforts to ensure that the information and instructions contained in this work are accurate, the publisher and the authors disclaim all responsibility for errors or omissions, including without limitation responsibility for damages resulting from the use of or reliance on this work Use of the information and instructions contained in this work is at your own risk If any code samples or other technology this work contains or describes is subject to open source licenses or the intellectual property rights of others, it is your responsibility to ensure that your use thereof complies with such licenses and/or rights 978-1-491-93884-3 [LSI] Preface Software is eating the world Developers are the new kingmakers The internet of things means there will be a computer in every light bulb These statements indicate the growing dominance of software development, to the point where most people in the world will never be further than a meter away from a computer, and we will expect much of our life to interact with computer-assisted objects and environments all the time But this world comes with some dangers In the old world of computing, security was often only considered in earnest for banking and government systems But the rise of ubiquitous computing means a rise in the value that can be realized from the abuse of systems, which increases incentives for misuse, which in turn increases the risks systems face Agile software development techniques are becoming rapidly adopted in most organizations By being responsive to change and dramatically lowering the cost of development, they provide a standard that we expect will continue to grow until the majority of software is built in an Agile manner However, security and Agile have not historically been great bedfellows Security professionals have had their hands full with the aforementioned government, ecommerce, and banking systems, trying to architect, test, and secure those systems, all in the face of a constantly evolving set of threats Furthermore, what is often seen as the most fun and exciting work in security, the things that get covered on the tech blogs and the nightly news, is done by teams of professional hackers focusing on vulnerability research, exploit development, and stunt hacks You can probably name a few recent branded vulnerabilities like Heartbleed, Logjam, or Shellshock (or heaven forbid even recognize their logos), or recognize the teams of researchers who have achieved a jailbreak on the latest iPhones and Android devices But when was the last time a new defensive measure or methodology had a cool, media-friendly name, or you picked up the name of a defender and builder? Security professionals are lagging behind in their understanding and experience of Agile development, and that creates a gap that is scary for our industry Equally, Agile teams have rejected and thrown off the shackles of the past No more detailed requirements specifications, no more system modeling, no more traditional Waterfall handoffs and control gates The problem with this is that Agile teams have thrown the baby out with the bathwater Those practices, while sometimes slow and inflexible, have demonstrated value over the years They were done for a reason, and Agile teams in rejecting them can easily forget and dismiss their value This means that Agile teams rarely consider security as much as they should Some of the Agile practices make a system more secure, but that is often a beneficial side effect rather than the purpose Very few Agile teams have an understanding of the threats that face their system; they don’t understand the risks they are taking; they don’t track or anything to control those risks; and they often have a poor understanding of who it even is that is attacking their creations Who Should Read This Book We don’t know if you are an Agile team leader, or a developer who is curious or wants to know more about security Maybe you are a security practitioner who has just found an entire development team you didn’t know existed and you want to know more This book was written with three main audiences in mind The Agile Practitioner You live, breathe, and Agile You know your Scrum from your Kaizen, your test-driven-development from your feedback loop Whether you are a Scrum Master, developer, tester, Agile coach, Product Owner, or customer proxy, you understand the Agile practices and values This book should help you understand what security is about, what threats exist, and the language that security practitioners use to describe what is going on We’ll help you understand how we model threats, measure risks, build software with security in mind, install software securely, and understand the operational security issues that come with running a service The Security Practitioner Whether you are a risk manager, an information assurance specialist, or a security operations analyst, you understand security You are probably careful how you use online services, you think about threats and risks and mitigations all of the time, and you may have even found new vulnerabilities and exploited them yourself This book should help you understand how software is actually developed in Agile teams, and what on earth those teams are talking about when they talk about sprints and stories You will learn to see the patterns in the chaos, and that should help you interact with and influence the team This book should show you where you can intervene or contribute that is most valuable to an Agile team and has the best effect The Agile Security Practitioner From risk to sprints, you know it all Whether you are a tool builder who is trying to help teams security well, or a consultant who advises teams, this book is also for you The main thing to get out of this book is to understand what the authors consider to be the growing measure of good practice This book should help you be aware of others in your field, and of the ideas and thoughts and concepts that we are seeing pop up in organizations dealing with this problem It should give you a good, broad understanding of the field and an idea for what to research or learn about next .. .Agile Application Security Enabling Security in a Continuous Delivery Pipeline Laura Bell, Michael Brunton-Spall, Rich Smith, and Jim Bird Agile Application Security by Laura Bell, Michael... defender and builder? Security professionals are lagging behind in their understanding and experience of Agile development, and that creates a gap that is scary for our industry Equally, Agile teams... “The attacker exploited a vulnerability in ” as you start to read about this area in more depth In these examples, the vulnerability was a flaw in an application s construction, configuration