CoChat

An Empirical Study on Culture, Automation, Measurement, and Sharing of DevSecOps

Tomas, Nora, Li, Jingyue, Huang, Huang · 2019 · 2019 International Conference on Cyber Security and Protection of Digital Services (Cyber Security)

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

Crossref · 10.1109/cybersecpods.2019.8884935

Cites

9 of 9 references verified0 citation errors · 0 not checkable

Statistics

Recomputing p-values needs the paper’s full text.

Verification

Claims the paper makes

This paper’s full text isn’t openly available, so its claims and self-check weren’t run. The registry and citation checks still apply.

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?

Citations

Cites

Show all 9 references

Research works printed but not linked: 11

  1. 2018, 2018 State of DevOps Report
  2. 2018, Measuring DevOps
  3. mendes, 2017, DevOps Maturity Model Report Trends and Best Practices in 2017
  4. boyer, 2018, Security as Code Why a Mental Shift Is Necessary for Secure DevOps
  5. 2018, DevSecOps Global Skills Survey
  6. willis, 2012, DevOps Culture (Part 1)
  7. mugrage, 2018, You only have to change one thing to do the DevOps
  8. klijnsma, 2018, Inside the Magecart Breach of British Airways How 22 Lines of Code Claimed 380 000 Victims
  9. mezak, 2018, Data Breaches Compromised 4 5 Billion Records in First Half of 2018
  10. wilsenach, 2015, DevOps Culture
  11. sheridan, 2018, The Best and Worst Tasks for Security Automation

Cited by

See all 66

Metadata

Authors
Tomas, N., Li, J., & Huang, H.
Affiliations
  • Norwegian University of Science and Technology (NO)
  • Nanjing University (CN)
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
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.