Rights statement: © ACM, 2020. This is the author's version of the work. It is posted here by permission of ACM for your personal use. Not for redistribution. The definitive version was published in ICSE '20: Proceedings of the ACM/IEEE 42nd International Conference on Software Engineering, 2020 https://dl.acm.org/doi/abs/10.1145/3377811.3380394
Accepted author manuscript, 915 KB, PDF document
Available under license: CC BY-NC: Creative Commons Attribution-NonCommercial 4.0 International License
Final published version
Research output: Contribution in Book/Report/Proceedings - With ISBN/ISSN › Conference contribution/Paper › peer-review
Research output: Contribution in Book/Report/Proceedings - With ISBN/ISSN › Conference contribution/Paper › peer-review
}
TY - GEN
T1 - Schrödinger’s Security
T2 - Opening the Box on App Developers’ Security Rationale
AU - van der Linden, Dirk
AU - Anthonysamy, Pauline
AU - Nuseibeh, Bashar
AU - Tun, Thein T.
AU - Petre, Marian
AU - Levine, Mark
AU - Towse, John
AU - Rashid, Awais
N1 - © ACM, 2020. This is the author's version of the work. It is posted here by permission of ACM for your personal use. Not for redistribution. The definitive version was published in ICSE '20: Proceedings of the ACM/IEEE 42nd International Conference on Software Engineering, 2020 https://dl.acm.org/doi/abs/10.1145/3377811.3380394
PY - 2020/5/23
Y1 - 2020/5/23
N2 - Research has established the wide variety of security failures in mobile apps, their consequences, and how app developers introduce or exacerbate them. What is not well known is why developers do so—what is the rationale underpinning the decisions they make which eventually strengthen or weaken app security? This is all the more complicated in modern app development’s increasingly di- verse demographic: growing numbers of independent, solo, or small team developers who do not have the organizational structures and support that larger software development houses enjoy.Through two studies, we open the box on developer rationale, by performing a holistic analysis of the rationale underpinning various activities in which app developers engage when developing an app.The first study does so through a task-based study with app developers (N=44) incorporating six distinct tasks for which this developer demographic must take responsibility: setting up a devel- opment environment, reviewing code, seeking help, seeking testers, selecting an advertisement SDK, and software licensing. We found that, while on first glance in several activities participants seemed to prioritize security, only in the code task such prioritization was underpinned by a security rationale–indicating that development behavior perceived to be secure may only be an illusion until the box is opened on their rationale.The second study confirms these findings through a wider sur- vey of app developers (N=274) investigating to what extent they find the activities of the task-based study to affect their app’s se- curity. In line with the task-based study, we found that developers perceived actively writing code and actively using external SDKs as the only security-relevant, while similarly disregarding other activities having an impact on app security.Our results suggest the need for a stronger focus on the tasks and activities surrounding the coding task – all of which need to be underpinned by a security rationale. Without such a holistic focus, developers may write “secure code" but not produce “secure apps”.
AB - Research has established the wide variety of security failures in mobile apps, their consequences, and how app developers introduce or exacerbate them. What is not well known is why developers do so—what is the rationale underpinning the decisions they make which eventually strengthen or weaken app security? This is all the more complicated in modern app development’s increasingly di- verse demographic: growing numbers of independent, solo, or small team developers who do not have the organizational structures and support that larger software development houses enjoy.Through two studies, we open the box on developer rationale, by performing a holistic analysis of the rationale underpinning various activities in which app developers engage when developing an app.The first study does so through a task-based study with app developers (N=44) incorporating six distinct tasks for which this developer demographic must take responsibility: setting up a devel- opment environment, reviewing code, seeking help, seeking testers, selecting an advertisement SDK, and software licensing. We found that, while on first glance in several activities participants seemed to prioritize security, only in the code task such prioritization was underpinned by a security rationale–indicating that development behavior perceived to be secure may only be an illusion until the box is opened on their rationale.The second study confirms these findings through a wider sur- vey of app developers (N=274) investigating to what extent they find the activities of the task-based study to affect their app’s se- curity. In line with the task-based study, we found that developers perceived actively writing code and actively using external SDKs as the only security-relevant, while similarly disregarding other activities having an impact on app security.Our results suggest the need for a stronger focus on the tasks and activities surrounding the coding task – all of which need to be underpinned by a security rationale. Without such a holistic focus, developers may write “secure code" but not produce “secure apps”.
U2 - 10.1145/3377811.3380394
DO - 10.1145/3377811.3380394
M3 - Conference contribution/Paper
SP - 149
EP - 160
BT - ICSE '20
PB - Association for Computing Machinery (ACM)
CY - New York
ER -