A Novel Security-Enhanced Agile Software Development Process Applied in an Industrial Setting

被引:25
作者
Baca, Dejan [1 ]
Boldt, Martin [2 ]
Carlsson, Bengt [2 ]
Jacobsson, Andreas [3 ,4 ]
机构
[1] Ericsson AB, Karlskrona, Sweden
[2] Blekinge Inst Technol, Dept Comp Sci & Engn, Karlskrona, Sweden
[3] Malmo Univ, Dept Comp Sci, Malmo, Sweden
[4] Malmo Univ, Internet Things & People Res Ctr, Malmo, Sweden
来源
PROCEEDINGS 10TH INTERNATIONAL CONFERENCE ON AVAILABILITY, RELIABILITY AND SECURITY ARES 2015 | 2015年
关键词
Security; risk analysis; software development; agile method; industrial setting;
D O I
10.1109/ARES.2015.45
中图分类号
TP [自动化技术、计算机技术];
学科分类号
0812 ;
摘要
A security-enhanced agile software development process, SEAP, is introduced in the development of a mobile money transfer system at Ericsson Corp. A specific characteristic of SEAP is that it includes a security group consisting of four different competences, i.e., security manager, security architect, security master and penetration tester. Another significant feature of SEAP is an integrated risk analysis process. In analyzing risks in the development of the mobile money transfer system, a general finding was that SEAP either solves risks that were previously postponed or solves a larger proportion of the risks in a timely manner. The previous software development process, i.e., the baseline process of the comparison outlined in this paper, required 2.7 employee hours spent for every risk identified in the analysis process compared to, on the average, 1.5 hours for the SEAP. The baseline development process left 50% of the risks unattended in the software version being developed, while SEAP reduced that figure to 22%. Furthermore, SEAP increased the proportion of risks that were corrected from 12.5% to 67.1%, i.e., more than a five times increment. This is important, since an early correction may avoid severe attacks in the future. The security competence in SEAP accounts for 5% of the personnel cost in the mobile money transfer system project. As a comparison, the corresponding figure, i.e., for security, was 1% in the previous development process.
引用
收藏
页码:11 / 19
页数:9
相关论文
共 18 条
[1]  
Anderson P., 2012, SECURITY PRIVACY IEE, V10, P40
[2]  
[Anonymous], 2011, INT ENCY STAT SCI
[3]  
[Anonymous], P 2004 WORKSH NEW SE
[4]  
Baca D., 2011, P INT C SOFTW SYST P
[5]   Improving software security with static automated code analysis in an industry setting [J].
Baca, Dejan ;
Carlsson, Bengt ;
Petersen, Kai ;
Lundberg, Lars .
SOFTWARE-PRACTICE & EXPERIENCE, 2013, 43 (03) :259-279
[6]  
Black P.E., 2012, SECURITY PRIVACY, V10, P48
[7]   Fault Injection for Software Certification [J].
Cotroneo, Domenico ;
Natella, Roberto .
IEEE SECURITY & PRIVACY, 2013, 11 (04) :38-45
[8]  
Davis Noopur, 2005, CMUSEI2005TN024
[9]  
Keramati H., 2008, P IEEE ACS INT C COM
[10]  
McGraw, 2006, SOFTWARE SECURITY BU