An Empirical Study on Culture, Automation, Measurement, and Sharing of DevSecOps
The DOI matches its Crossref record; 9 of the 9 references it cites were found in a registry or an index.
Abstract
Programmers are central agents in creating secure applications. However, software engineering and software security have historically worked in separate silos. DevSecOps is the practice of breaking down silos between development, operations, and quality assurance of security. To understand the state of art and challenges of DevSecOps, we interviewed six developers about their DevSecOps practices. We asked interview subjects about their security practices rooted in the four pillars of DevOps, namely culture, automation, sharing, and measurement. Results were analyzed by using qualitative methods. The results of the study show that it is necessary first to create a security culture. Several interviewees identified the importance of caring about security and issues in existing culture, such as how developers feel attacked by security engineers if they create vulnerable code. After establishing a security culture in the organization, development and operations need the necessary training and knowledge so that security automation tools can be utilized effectively. Measurements need to be applied continuously to keep track of identified vulnerabilities, the amount of training staff has received, and staffs general opinions regarding security.
Overview
Integrity signals
Registry
Cites
Statistics
Verification
Claims the paper makes
Claims other papers make about this one
Each is checked against this paper’s own text: does it say what the citing paper says it does?
In the citing paper
“DevSecOps uses the same CAMS principles as DevOps [10] [29].”
From DevSecOps practices and tools (2025) · cites this paper as [29]
In the citing paper
“Without addressing this issue at the beginning, projects may not start off well (Rafi et al., 2020; Tomas et al., 2019).”
From Identifying the primary dimensions of DevSecOps: A multi-vocal literature review (2024) · cites this paper as Tomas et al., 2019
In the citing paper
“that stresses the necessity of training security knowledge and skills, especially for developers (Tomas et al., 2019).”
From Identifying the primary dimensions of DevSecOps: A multi-vocal literature review (2024) · cites this paper as Tomas et al., 2019
Citations
Cites
National Institute of Standards and Technology
(1990) · Analytical Chemistry · doi:10.1021/ac00210a736 · Cited by 1,314
Continuous software engineering: A roadmap and agenda
Fitzgerald, B., & Stol, K.-J. (2017) · Journal of Systems and Software · doi:10.1016/j.jss.2015.06.063 · Cited by 723
Shahin, M., Ali Babar, M., & Zhu, L. (2017) · IEEE Access · doi:10.1109/access.2017.2685629 · Cited by 680 · cited 1×
“However, fixing issues later in the process is more costly than making sure defects do not happen in the beginning [18].”
BackgroundHuman and organizational factors in computer and information security: Pathways to vulnerabilities
Kraemer, S., Carayon, P., & Clem, J. (2009) · Computers & Security · doi:10.1016/j.cose.2009.04.006 · Cited by 215 · cited 1×
“Studies show that external factors such as time pressure and high workload can cause programmers to neglect security [3].”
BackgroundKim, G. H., Debois, P., Willis, J., & Humble, J. (2016) · Cited by 205
DevSecOps: A Multivocal Literature Review
Myrbakken, H., & Colomo-Palacios, R. (2017) · Communications in Computer and Information Science · doi:10.1007/978-3-319-67383-7_2 · Cited by 205 · cited 4×
“Myrbakken and Colomo-Palacios introduce DevSecOps by saying that traditional security methods have struggled to keep up with DevOps agility and speed [16].”
BackgroundInfluentialDevOps: A Definition and Perceived Adoption Impediments
Smeds, J., Nybom, K., & Porres, I. (2015) · Lecture Notes in Business Information Processing · doi:10.1007/978-3-319-18612-2_14 · Cited by 158
Closing the IT Development-operations Gap: The DevOps Knowledge Sharing Framework
Nielsen, P. A., Winkler, T. J., & Nørbjerg, J. (2017) · Business Informatics Research · Cited by 16
An integrated approach to security in software development methodologies
Raman, A., & Muegge, S. M. (2008) · Conference proceedings - Canadian Conference on Electrical and Computer Engineering · doi:10.1109/ccece.2008.4564898 · Cited by 2
Research works printed but not linked: 11
- 2018, 2018 State of DevOps Report
- 2018, Measuring DevOps
- mendes, 2017, DevOps Maturity Model Report Trends and Best Practices in 2017
- boyer, 2018, Security as Code Why a Mental Shift Is Necessary for Secure DevOps
- 2018, DevSecOps Global Skills Survey
- willis, 2012, DevOps Culture (Part 1)
- mugrage, 2018, You only have to change one thing to do the DevOps
- klijnsma, 2018, Inside the Magecart Breach of British Airways How 22 Lines of Code Claimed 380 000 Victims
- mezak, 2018, Data Breaches Compromised 4 5 Billion Records in First Half of 2018
- wilsenach, 2015, DevOps Culture
- sheridan, 2018, The Best and Worst Tasks for Security Automation
Cited by
Toward successful DevSecOps in software development organizations: A decision-making framework
Akbar, M. A., Smolander, K., Mahmood, S., & Alsanad, A. (2022) · Information and Software Technology · doi:10.1016/j.infsof.2022.106894 · Cited by 128
Rangnau, T., Buijtenen, R. V., Fransen, F., & Turkmen, F. (2020) · 2020 IEEE 24th International Enterprise Distributed Object Computing Conference (EDOC) · doi:10.1109/edoc49727.2020.00026 · Cited by 97
“Traditionally, security experts were organized into separate silos and security concerns were addressed after the actual design and development stages [8].”
InfluentialKumar, R., & Goyal, R. (2020) · Computers & Security · doi:10.1016/j.cose.2020.101967 · Cited by 97
Security as Culture: A Systematic Literature Review of DevSecOps
Sánchez-Gordón, M., & Colomo-Palacios, R. (2020) · Proceedings of the IEEE/ACM 42nd International Conference on Software Engineering Workshops · doi:10.1145/3387940.3392233 · Cited by 58
“It does not seem to be an easy task that likely differs in nature from organization to organization [20].”
InfluentialKhan, A. A., & Shameem, M. (2020) · Journal of Software Evolution and Process · doi:10.1002/smr.2263 · Cited by 67
Metadata
- Authors
- Tomas, N., Li, J., & Huang, H.
- Affiliations
- Norwegian University of Science and Technology (NO)
- Nanjing University (CN)
- ORCID
- Li, Jingyue
- Venue
- 2019 International Conference on Cyber Security and Protection of Digital Services (Cyber Security)
- Publisher
- IEEE
- Published
- 2019-06
- Pages
- 1-8
- OpenAlex
- W2982485630
- Cited by
- 66
- References
- 9
- Citations by year
- 2026: 3 · 2025: 9 · 2024: 14 · 2023: 11 · 2022: 8 · 2021: 12 · 2020: 9
- FWCI
- 5.77
- Type
- conference paper
- Language
- en
- Open access
- closed
- Licence
- Locations
- International Conference on Cyber Security and Protection of Digital Services (Cyber Security) (publishedVersion)
- Topics
- Physical Sciences › Computer Science › Information Systems › Software Engineering Techniques and Practices
- Physical Sciences › Computer Science › Information Systems › Web Application Security Vulnerabilities
- Physical Sciences › Computer Science › Information Systems › Information and Cyber Security
- Keywords
- DevSecOps, security culture, security automation, vulnerability measurement, knowledge sharing, developer interviews, software security, developer training
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: An Empirical Study on Culture, Automation, Measurement, and Sharing of DevSecOps. https://app.cochat.ai/papers/10.1109/cybersecpods.2019.8884935
- The paper
- Tomas, N., Li, J., & Huang, H. (2019). An Empirical Study on Culture, Automation, Measurement, and Sharing of DevSecOps. 2019 International Conference on Cyber Security and Protection of Digital Services (Cyber Security). https://doi.org/10.1109/cybersecpods.2019.8884935
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.