Analyzing confidentiality and privacy concerns: insights from Android issue logs
| aut.relation.startpage | Article no 18 | |
| aut.researcher | Clear, Anthony George | |
| dc.contributor.author | Licorish, S | |
| dc.contributor.author | MacDonell, SG | |
| dc.contributor.author | Clear, T | |
| dc.contributor.editor | Zhang, J | |
| dc.contributor.editor | Ali Babar, M | |
| dc.date.accessioned | 2015-05-12T04:22:40Z | |
| dc.date.available | 2015-05-12T04:22:40Z | |
| dc.date.copyright | 2015-04-27 | |
| dc.date.issued | 2015-04-27 | |
| dc.description.abstract | Context: Post-release user feedback plays an integral role in improving software quality and informing new features. Given its growing importance, feedback concerning security enhancements is particularly noteworthy. In considering the rapid uptake of Android we have examined the scale and severity of Android security threats as reported by its stakeholders. Objective: We systematically mine Android issue logs to derive insights into stakeholder perceptions and experiences in relation to certain Android security issues. Method: We employed contextual analysis techniques to study issues raised regarding confidentiality and privacy in the last three major Android releases, considering covariance of stakeholder comments, and the level of consistency in user preferences and priorities. Results: Confidentiality and privacy concerns varied in severity, and were most prevalent over Jelly Bean releases. Issues raised in regard to confidentiality related mostly to access, user credentials and permission management, while privacy concerns were mainly expressed about phone locking. Community users also expressed divergent preferences for new security features, ranging from more relaxed to very strict. Conclusions: Strategies that support continuous corrective measures for both old and new Android releases would likely maintain stakeholder confidence. An approach that provides users with basic default security settings, but with the power to configure additional security features if desired, would provide the best balance for Android's wide cohort of stakeholders. | |
| dc.identifier.citation | The 19th International Conference on Evaluation and Assessment in Software Engineering (EASE '15:) , Nanjing, China, 2015-04-27to 2015-04-29, published in: EASE '15: Proceedings of the 19th International Conference on Evaluation and Assessment in Software Engineering, pp.Article no 18 - ? | |
| dc.identifier.doi | 10.1145/2745802.2745819 | |
| dc.identifier.uri | https://hdl.handle.net/10292/8677 | |
| dc.publisher | ACM | |
| dc.relation.uri | http://dx.doi.org/10.1145/2745802.2745819 | |
| dc.rights | Permission to make digital or hard copies of all or part of this work for personal or classroom use is granted without fee provided that copies are not made or distributed for profit or commercial advantage and that copies bear this notice and the full citation on the first page. Copyrights for components of this work owned by others than ACM must be honored. Abstracting with credit is permitted. To copy otherwise, or republish, to post on servers or to redistribute to lists, requires prior specific permission and/or a fee. Request permissions from Permissions@acm.org. | |
| dc.rights.accessrights | OpenAccess | |
| dc.subject | Android | |
| dc.subject | Security | |
| dc.subject | Confidentiality | |
| dc.subject | Privacy | |
| dc.subject | Content analysis | |
| dc.subject | Empirical analysis | |
| dc.title | Analyzing confidentiality and privacy concerns: insights from Android issue logs | |
| dc.type | Conference Contribution | |
| pubs.elements-id | 183004 | |
| pubs.organisational-data | /AUT | |
| pubs.organisational-data | /AUT/Design & Creative Technologies |