Secure Software Engineering in the Financial Services: A Practitioners' Perspective

Abstract

Secure software engineering is a fundamental activity in modern software development. However, while the field of security research has been advancing quite fast, in practice, there is still a vast knowledge gap between the security experts and the software development teams. After all, we cannot expect developers and other software practitioners to be security experts. Understanding how software development teams incorporate security in their processes and the challenges they face is a step towards reducing this gap. In this paper, we study how financial services companies ensure the security of their software systems. To that aim, we performed a qualitative study based on semi-structured interviews with 16 software practitioners from 11 different financial companies in three continents. Our results shed light on the security considerations that practitioners take during the different phases of their software development processes, the different security practices that software teams make use of to ensure the security of their software systems, the improvements that practitioners perceive as important in existing state-of-the-practice security tools, the different knowledge-sharing and learning practices that developers use to learn more about software security, and the challenges that software practitioners currently face when it comes to secure their systems.

Human-centred cyber secure software engineering

“… 2020 ; Kanniah and Mahrin 2016 ; Arora et al. 2021 ; Stamat and Humphries 2009 ; Hein and Saiedian 2009 ). The need for security to be part of the software engineering process from design through to implementation is highlighted (Mouratidis et al.…”

“…Importance of collaboration and team dynamics highlighted: (Arora et al. 2021 ), and of the need for communication between stakeholders during the development process (Kanniah and Mahrin 2016 ). End Users : Need to consider the impact of security measures on end users (Flechais et al.…”

“… 2020 ; Kanniah and Mahrin 2016 ; Arora et al. 2021 ; Stamat and Humphries 2009 ; Hein and Saiedian 2009 ).…”