Projects per year
Abstract
Background: Recent studies show that secure coding is about not only technical requirements but also developers' behaviour.
Objective: To understand the influence of socio-technical contexts on how developers attend to and engage with security in code, software engineering researchers collaborated with social psychologists on a psychologically-informed study.
Method: In a preregistered, between-group, controlled experiment, 124 developers from multiple freelance communities, were primed toward one of three identities, following which they completed code review tasks with open-ended responses. Qualitative analysis of the rich data focused on the attitudes and reasoning that shaped their identification of security issues within code.
Results: Overall, attention to code security was intermittent and heterogeneous in focus. Although social identity priming did not significantly change the code review, qualitative analysis revealed that developers varied in how they noticed issues in code, how they addressed them, and how they justified their choices.
Conclusion: We found that many developers do think about security - but differently from one another. Hence, effective interventions to promote secure coding must be appropriate to the individual development context.
Objective: To understand the influence of socio-technical contexts on how developers attend to and engage with security in code, software engineering researchers collaborated with social psychologists on a psychologically-informed study.
Method: In a preregistered, between-group, controlled experiment, 124 developers from multiple freelance communities, were primed toward one of three identities, following which they completed code review tasks with open-ended responses. Qualitative analysis of the rich data focused on the attitudes and reasoning that shaped their identification of security issues within code.
Results: Overall, attention to code security was intermittent and heterogeneous in focus. Although social identity priming did not significantly change the code review, qualitative analysis revealed that developers varied in how they noticed issues in code, how they addressed them, and how they justified their choices.
Conclusion: We found that many developers do think about security - but differently from one another. Hence, effective interventions to promote secure coding must be appropriate to the individual development context.
| Original language | English |
|---|---|
| Title of host publication | Proceedings of the 15th International Conference on Cooperative and Human Aspects of Software Engineering (CHASE '22) |
| Publisher | Association for Computing Machinery (ACM) |
| Pages | 86-95 |
| DOIs | |
| Publication status | Published - 19 Jul 2022 |
Fingerprint
Dive into the research topics of 'Influences of developers' perspectives on their engagement with security in code'. Together they form a unique fingerprint.Projects
- 1 Finished
-
Why Johnny doesn't write secure software? Secure software development by the masses
Rashid, A. (Principal Investigator) & Hallett, J. (Researcher)
1/10/18 → 31/12/21
Project: Research