A Survey on Developer-Centred Security
Open accessThe DOI matches its Crossref record; 7 of the 7 references it cites were found in a registry or an index.
Abstract
Software developers are key players in the security ecosystem as they produce code that runs on millions of devices. Yet we continue to see insecure code being developed and deployed on a regular basis despite the existence of support infrastructures, tools, and research into common errors. This work provides a systematised overview of the relatively new field of Developer-Centred Security which aims to understand the context in which developers produce security-relevant code as well as provide tools and processes that that better support both developers and secure code production. We report here on a systematic literature review of 49 publications on security studies with software developer participants. We provide an overview of both the types of methodologies currently being used as well as the current research in the area. Finally, we also provide recommendations for future work in Developer-Centred Security.
Overview
The claims and statistics of this paper haven’t been checked yet.
Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.
Integrity signals
Registry
Cites
Statistics
Verification
Claims the paper makes
The claims and statistics of this paper haven’t been checked yet.
Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.
Self-check
Percentages, sums and reported differences re-computed from the paper’s own numbers.
The self-check needs the paper’s full text.
Citations
Cites
A Guide to Conducting a Standalone Systematic Literature Review
Okoli, C. (2015) · Communications of the Association for Information Systems · doi:10.17705/1cais.03743 · Cited by 1,413 · cited 3×
“We used a Systematic Literature Review [20] approach in order to identify all relevant literature.”
BackgroundMethodInfluentialThe 2015 Ukraine Blackout: Implications for False Data Injection Attacks
Liang, G., Weller, S. R., Zhao, J., Luo, F., & Dong, Z. Y. (2017) · IEEE Transactions on Power Systems · doi:10.1109/tpwrs.2016.2631891 · Cited by 1,248
Dubé, L., & Paré, G. (2003) · MIS Quarterly · doi:10.2307/30036550 · Cited by 976
The state of the art in end-user software engineering
Ko, A. J., Abraham, R., Beckwith, L., Blackwell, A., Burnett, M., Erwig, M., Scaffidi, C., Lawrance, J., Lieberman, H., Myers, B., et al. (2011) · ACM Computing Surveys · doi:10.1145/1922649.1922658 · Cited by 633
(2015) · doi:10.1007/s10664-013-9279-3 · Cited by 273 · cited 3×
“In software engineering experiments it is recommend to report experience with programming languages, technologies related to the tool, industry, and natural language [26].”
BackgroundProgrammers Are Users Too: Human-Centered Methods for Improving Programming Tools
Myers, B. A., Ko, A. J., LaToza, T. D., & Yoon, Y. (2016) · Computer · doi:10.1109/mc.2016.200 · Cited by 144
Software security in DevOps: synthesizing practitioners' perceptions and practices
Ur Rahman, A. A., & Williams, L. (2016) · Proceedings of the International Workshop on Continuous Software Evolution and Delivery · doi:10.1145/2896941.2896946 · Cited by 86 · cited 1×
“The fast nature of testing can also lead to prioritisation of automated tests over more manual tests such as penetration testing [43].”
Method
Cited by
Challenges and solutions when adopting DevSecOps: A systematic review
Rajapakse, R. N., Zahedi, M., Babar, M. A., & Shen, H. (2022) · Information and Software Technology · doi:10.1016/j.infsof.2021.106700 · Cited by 235
“Developers, similar to end-users in security tasks, need support to create applications that are secure [57].”
Background(2022) · doi:10.1145/3491102.3501957 · Cited by 47
Self-citationAn Empirical Study of the Use of Integrity Verification Mechanisms for Web Subresources
Chapuis, B., Omolola, O., Cherubini, M., Humbert, M., & Huguenin, K. (2020) · Proceedings of The Web Conference 2020 · doi:10.1145/3366423.3380092 · Cited by 14
Metadata
- Authors
- Tahaei, M., & Vaniea, K.
- Venue
- 2019 IEEE European Symposium on Security and Privacy Workshops (EuroS&PW)
- Publisher
- IEEE
- Published
- 2019-06
- Pages
- 129-138
- OpenAlex
- W2966008409
- Cited by
- 85
- References
- 7
- FWCI
- 8.70
- Type
- conference paper
- Language
- en
- Open access
- green
About these checks
Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.
Statistics and arithmetic are recomputed, not judged.
Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.
What counts as a claim ›How we measure confidence ›How we check this ›
Are you an author, or do you see a problem with this page? Request a review
How to cite
Cite CoChat for the checks on this page, and the paper for its own findings.
- This page
- CoChat. (2026). Citation check: A Survey on Developer-Centred Security. https://app.cochat.ai/papers/10.1109/eurospw.2019.00021
- The paper
- Tahaei, M., & Vaniea, K. (2019). A Survey on Developer-Centred Security. 2019 IEEE European Symposium on Security and Privacy Workshops (EuroS&PW). https://doi.org/10.1109/eurospw.2019.00021
Data sources
Bibliographic data: Semantic Scholar, OpenAlex, Crossref.
Contains information from the Semantic Scholar Academic Graph Datasets, made available under the ODC Attribution License (ODC-BY 1.0).
Semantic Scholar’s data is described in: Kinney, R., et al. (2023). The Semantic Scholar Open Data Platform. arXiv:2301.10140.