Home > Research > Publications & Outputs > The Case for Adaptive Security Interventions

Electronic data

Text available via DOI:

View graph of relations

The Case for Adaptive Security Interventions

Research output: Contribution to journalJournal articlepeer-review

Forthcoming
  • Irum Rauf
  • Marian Petre
  • Thein T. Tun
  • Tamara Lopez
  • Paul Lunn
  • Dirk van der Linden
  • John Towse
  • Helen Sharp
  • Mark Levine
  • Awais Rashid
  • Bashar Nuseibeh
Close
<mark>Journal publication date</mark>19/06/2021
<mark>Journal</mark>ACM Transactions on Software Engineering and Methodology
Publication StatusAccepted/In press
<mark>Original language</mark>English

Abstract

Despite the availability of various methods and tools to facilitate secure coding, developers continue to write code that contains common vulnerabilities. It is important to understand why technological advances do not sufficiently facilitate developers in writing secure code. In order to widen our understanding of developers’ behaviour, we considered the complexity of the security decision space of developers using theory from cognitive and social psychology. Our interdisciplinary study reported in this paper (1) draws on the psychology literature to provide conceptual underpinnings for three categories of impediments to achieving security goals, (2) reports on an in-depth meta-analysis of existing software security literature which identified a catalogue of factors that influence developers’ security decisions, and (3) characterises the landscape of existing security interventions that are available to the developer during coding and identifies gaps. Collectively, these show that different forms of impediments to achieving security goals arise from different contributing factors. Interventions will be more effective where they reflect psychological factors more sensitively and marry technical sophistication, psychological frameworks, and usability. Our analysis suggests ‘adaptive security interventions’ as a solution that responds to the changing security needs of individual developers and a present a proof-of-concept tool to substantiate our suggestion.