Abstract

Agile is an increasingly popular development methodology that enables faster delivery of code that meets customer requirements. Agile’s development principles encourage active user involvement through the lifecycle providing better visibility for stakeholders; enabling better quality, risk management and expectation management. All really good stuff! But what about secure code? Customers expect their products to be secure but often omit adding specific requirements for this. Agile behaviours often neglect the security angle and sometimes make it more difficult to integrate. We present a case study on how Thales incorporated security activities into an Agile project and hope that the learnings will be useful for future secure development work using the Agile methodology.