Why do People Adopt, or Reject, Smartphone Security Tools?

Alkaldi, N. and Renaud, K. (2016) Why do People Adopt, or Reject, Smartphone Security Tools? In: International Symposium on Human Aspects of Information Security and Assurance (HAISA 2016), Frankfurt, Germany, 19 - 21 July 2016, pp. 135-144. ISBN 9781841024134

120716.pdf - Accepted Version


Publisher's URL: http://cscan.org/default.asp?page=openaccess&eid=17&id=283


A large variety of security tools exist for Smartphones, to help their owners to secure the phones and prevent unauthorised others from accessing their data and services. These range from screen locks to antivirus software to password managers. Yet many Smartphone owners do not use these tools despite their being free and easy to use. We were interested in exploring this apparent anomaly. A number of researchers have applied existing models of behaviour from other disciplines to try to understand these kinds of behaviours in a security context, and a great deal of research has examined adoption of screen locking mechanisms. We review the proposed models and consider how they might fail to describe adoption behaviours. We then present the Integrated Model of Behaviour Prediction (IMBP), a richer model than the ones tested thus far. We consider the kinds of factors that could be incorporated into this model in order to understand Smartphone owner adoption, or rejection, of security tools. The model seems promising, based on existing literature, and we plan to test its efficacy in future studies.

Item Type:Conference Proceedings
Glasgow Author(s) Enlighten ID:Renaud, Professor Karen
Authors: Alkaldi, N., and Renaud, K.
College/School:College of Science and Engineering > School of Computing Science
Copyright Holders:Copyright © 2016 The Authors
First Published:First published in Tenth International Symposium on Human Aspects of Information Security & Assurance (HAISA 2016): 135-144
Publisher Policy:Reproduced in accordance with the publisher copyright policy
Related URLs:

University Staff: Request a correction | Enlighten Editors: Update this record