000000087 001__ 87
000000087 005__ 20130522141942.0
000000087 037__ $$aLERSSE-RefConfPaper-2005-015
000000087 041__ $$aeng
000000087 100__ $$aKonstantin Beznosov
000000087 100__ $$aPhilippe Kruchten
000000087 245__ $$aTowards Agile Security Assurance
000000087 260__ $$c2005-10-16
000000087 520__ $$aAgile development methods are promising to become the next generation replacing water-fall development. They could eventually replace the plan-driven methodologies not only in pure software solutions in such benign domains as word processing and office automation but also in security-critical projects with both software and hardware parts developed or integrated together. At the same time, the accepted practices for security assurance appear to go totally contrary to agile approaches. Can and how security assurance be adopted by agile developers? What needs to be done for the adoption to happen? This paper makes a first step toward answering these questions in a pursuit for agile security assurance. It re-examines the conventional practices of security assurance to find out how well they suite agile development methodologies. It classifies security assurance methods and techniques with regards to their clash with agile development. For those in conflict, ways of alleviating it are suggested.
000000087 6531_ $$aagile methods
000000087 6531_ $$aeXtreme Programming
000000087 6531_ $$aXP
000000087 6531_ $$asecurity assurance
000000087 6531_ $$aengineering secure software
000000087 8560_ $$fqiangw@ece.ubc.ca
000000087 8564_ $$uhttp://lersse-dl.ece.ubc.ca/record/87/files/87.pdf$$yTransfer from CDS 0.99.7
000000087 909C4 $$c47-54$$pProceedings of the workshop on New										security paradigms, Nova Scotia, Canada$$y2004
000000087 980__ $$aRefConfPaper