We recently came across a fun book. A book that basically tells us why most Agile software development projects do not include security in their processes and that most software built in an Agile-fashion are not secure.
Wake up call anyone?
Below is some of the abstract from the book:
“In this article, the authors contrast the results of a series of interviews with agile software development organizations with a case study of a distributed agile development effort, focusing on how information security is taken care of in an agile context. The interviews indicate that small and medium-sized agile software development organizations do not use any particular methodology to achieve security goals, even when their software is web-facing and potential targets of attack. This case study confirms that even in cases where security is an articulated requirement, and where security design is fed as input to the implementation team, there is no guarantee that the end result meets the security objectives.”
The authors contend that security must be built as an intrinsic software property and emphasize the need for security awareness throughout the whole software development lifecycle. This paper suggests two extensions to agile methodologies that may contribute to ensuring focus on security during the complete lifecycle.
Worth a read for $30? Yep. I bought a copy. I’ll update this post as I finish it and let y’all know.