CoChat

DevSecOps practices and tools

Open access
Prates, Luís, Pereira, Rúben · 2025 · International Journal of Information Security

The DOI matches its Crossref record; 79 of the 79 references it cites were found in a registry or an index; 7 of the 42 sources its claims cite were checked for support.

Abstract

Nowadays, software development happens at a fast pace. At the same time, Information Technology organizations face higher demands and competition while struggling with external threats such as cyberattacks. Therefore, many organizations adopt DevOps as a working culture to improve their Software Development Lifecycle (SDL). However, the success of DevOps adoption remains inconsistent, and recently, IEEE introduced a DevOps standard that might help improve DevOps adoption. The standard mentions DevSecOps as the security aspect of DevOps, adding security practices to the SDL from inception, but what are these practices or capabilities? Which tools can be used to implement these practices? Therefore, a Multivocal Literature Review was performed to identify DevSecOps practices and their definitions, and which tools can be used to implement them.

Overview

CoChat Summary

TL;DR

This paper uses a multivocal literature review to map DevSecOps practices and the tools used to implement them across white and grey literature. It identifies 39 practices from 103 primary studies and 114 tools for 27 practices, with strong overlap between academic and industry sources.

Key findings

  • The review screened 895 initial records and ended with 103 primary studies eligible for data extraction.
  • Across those studies, the authors identified 39 DevSecOps practices; WL contributed 38 practices and GL contributed 39, with average contribution per practice of 49.13% WL and 50.87% GL.
  • The most frequently mentioned practices were SAST (65 publications), DAST (58), Automated Security Testing (56), Vulnerability Scanning (44), Continuous Monitoring (41), Continuous Integration (41), and Threat Modelling (40).
  • For tooling, the paper reports 114 pertinent tools tailored to 27 of the 39 practices; 63% of the identified tools were community-supported on GitHub.
  • The paper ranks practices into tiers: Tier 1 core practices include SAST, DAST, Automated Security Testing, Vulnerability Scanning, Continuous Monitoring, Continuous Integration, Threat Modelling, Shift Left Security, Collaboration, Continuous Deployment, and Code Review.

Methods

  • The study used a Multivocal Literature Review (MLR), combining white literature and grey literature to answer two research questions: which DevSecOps practices are mentioned, and which tools implement them.
  • Search began in December 2022 across IEEE, Scopus, ACM Digital Library, Google Search, and EBSCO, using two search-string sets: ("DevSecOps OR SecDevOps") AND ("Practices" OR "Capabilities") and ("DevSecOps OR SecDevOps") AND ("Tools").
  • The selection pipeline applied filtering, inclusion/exclusion criteria, snowballing, abstract screening, and full-text screening, yielding 103 publications for extraction; tools were then compiled and refined using mention frequency and GitHub popularity.

Limitations

  • The paper states two major MLR limitations: source quality/credibility and selection bias.
  • It also notes temporal bias as a minor limitation: some included sources may be outdated in a fast-evolving field.
  • Evident from the text: the review relies on grey literature, which the paper says may be biased, less rigorous, or less transparent; it also acknowledges that relevant primary studies may have been inadvertently overlooked despite the protocol.

Model-written summary. Check it against the paper before relying on it.

Integrity signals

Registry

Crossref · 10.1007/s10207-024-00914-z

Cites

79 of 79 references verified0 citation errors · 0 not checkable

Statistics

Nothing to recompute.

Verification

Claims the paper makes

7 Valid · 7 Not valid · 20 Not checked · 166 Own results and interpretations

13 more claims

Create a free account to see all 200 claims and every source verdict.

See all claims — free account
  • Probably not a substantial claim. 168
  • It may state two separate claims as one. 30
  • The quote only partly states this claim. 1
  • Borderline: one of the tests for a substantial claim is unclear. 1

Create a free account to see these claims.

Self-check

Percentages, sums and reported differences re-computed from the paper’s own numbers.

Each contradiction between two passages listed here was confirmed by an independent check.

4 of 4

Citations

Cites

Show all 79 references

Research works printed but not linked: 14

  1. J. Humble and D. Farley, Continuous Delivery: Reliable Software Releases Through Build, Test, and Deployment Automation, Addison-Wesley Professional, 2010.
  2. Smeds, J., Nyborn, K., Pores, I.: DevOps: A Definition and Perceived Adoption Impediments. Agile Proce. Softw. Eng. Extreme Program. 212, 166–177 (2015)
  3. Kim, G., Humble, J., Debois, P., Willis, J.: The DevOps Handbook, Portland, OR. IT Revolution Press, USA (2016)
  4. Floris, E.: DevOps is Simply Interaction Between Development and Operations," in First International Workshop DevOps 2018. Chateau de Villebrumier, France (2019)
  5. Humble, J., Molesky, J.: Why enterprises must adopt devops to enable continuous delivery. Cutter IT Journal 24, 6–12 (2011)
  6. Davis, J., Daniels, K.: Effective DevOps. O’Reilly Media, USA (2016)
  7. Wilson, G.: DevSecOps. Rethink Press, UK (2020)
  8. Bird, J.: DevOpsSec, Sebastopol, CA. O’Reilly, USA (2016)
  9. Candel, J.: Implementing DevSecOps with Docker and Kubernetes. BPB Publications, India (2022)
  10. Kitchenham, B.: Procedures for performing systematic reviews." Keele. UK, Keele Univ. 33, 1–26 (2004)
  11. Zaydi, M., Nassereddine, B.: DevSecOps practices for an agile and secure IT service management. Int. J. Inf. Decis. Sci. 23, 134–149 (2020)
  12. Woody, C., Chick, T., Reffett, A., Pavetti, S., Laughlin, R., Frye, B., Bandor, M.: DevSecOps Pipeline for Complex Software-Intensive Systems: Addressing Cybersecurity Challenges. J Syst, Cybern Inf: JSCI 18(5), 31–36 (2020)
  13. W.-T. Lee and Z.-W. Liu. 2023. Microservices-based DevSecOps Platform using Pipeline and Open Source Software," Journal of Information Science and Engineering, vol. 39, pp. 1117–1128
  14. Flora, J., Gonçalves, P., Antunes, N.: Intrusion Detection for Scalable and Elastic Microservice Applications," in IEEE 28th Pacific Rim International Symposium on Dependable Computing (PRDC). Singapore, Singapore (2023)

Cited by

See all 49

Metadata

Authors
Prates, L., & Pereira, R.
Affiliations
Iscte – Instituto Universitário de Lisboa (PT)
Corresponding author
Prates, Luís
Venue
International Journal of Information Security
Published
2024-11-05
Volume
24
Issue
1
ISSN
  • 1615-5262 (ISSN-L)
  • 1615-5270
OpenAlex
W4404029152
Cited by
49
References
72
Citations by year
2026: 27 · 2025: 22
FWCI
18.34
Type
journal article
Language
en
Open access
Licence
Locations
  • International Journal of Information Security (publishedVersion, cc-by)
  • Repositório do ISCTE-IUL (submittedVersion, other-oa)
Funders
ISCTE – Instituto Universitário
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, DevOps, software development lifecycle, security practices, DevOps tools, DevOps adoption, software security

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.

The claim verdicts this report counts are experimental: their accuracy is not yet measured.

A language model drew the claims from the paper on 2026-10-10, under version 3 of the claim definition (model deepseek-v4.1-flash, prompt extract-v3).

A second model labelled each claim on 2026-10-10 (model jev-1.13-20260917, definition revision gold-guideline-v0.2).

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: DevSecOps practices and tools. https://app.cochat.ai/papers/10.1007/s10207-024-00914-z
The paper
Prates, L., & Pereira, R. (2025). DevSecOps practices and tools. International Journal of Information Security. https://doi.org/10.1007/s10207-024-00914-z

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.