DevSecOps practices and tools
Open accessThe 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
Cites
Statistics
Verification
Claims the paper makes
7 Valid · 7 Not valid · 20 Not checked · 166 Own results and interpretations
A result the paper states — it cites no source for it, so there is none to check. The quote shows it is in the paper.
In the paper
“Security Training is mentioned in 27 publications.”
§ DevSecOps practices and tools > Shift Left Security (SLS)
plain- Asserted: passes — The authors put it forward as true.
- Checkable: passes — It can be checked against evidence.
- Load-bearing: unclear — It is unclear whether the paper’s conclusions depend on it.
- Based: passes — The paper gives a reason why it holds.
A result the paper reports from its own data — it cites no other source for it, so there is none to check. The quote shows it is in the paper.
In the paper
“Through a comprehensive literature review encompassing 103 publications, this study identified 39 specific practices commonly implemented by organizations adopting DevSecOps methodologies.”
§ DevSecOps practices and tools > 7.1 RQ1 which devSecOps practices are mentioned in the literature?
plain- Asserted: passes — The authors put it forward as true.
- Checkable: passes — It can be checked against evidence.
- Load-bearing: passes — The paper’s conclusions depend on it.
- Based: passes — The paper gives a reason why it holds.
A result the paper reports from its own data — it cites no other source for it, so there is none to check. The quote shows it is in the paper.
In the paper
“The conclusion of the primary studies selection resulted in 103 publications eligible for data extraction.”
§ DevSecOps practices and tools > 6.2 Data extraction analysis
plain- Asserted: passes — The authors put it forward as true.
- Checkable: passes — It can be checked against evidence.
- Load-bearing: passes — The paper’s conclusions depend on it.
- Based: passes — The paper gives a reason why it holds.
A result the paper reports from its own data — it cites no other source for it, so there is none to check. The quote shows it is in the paper.
In the paper
“In Fig. 8 it is observable that from 2018 to 2023 there was an increase in the number of studies published referring DevSecOps practices and tools.”
§ DevSecOps practices and tools > 6.4 Studies distribution over the years
plainstates an association- Asserted: passes — The authors put it forward as true.
- Checkable: passes — It can be checked against evidence.
- Load-bearing: passes — The paper’s conclusions depend on it.
- Based: passes — The paper gives a reason why it holds.
A result the paper reports from its own data — it cites no other source for it, so there is none to check. The quote shows it is in the paper.
In the paper
“The white literature contribution of 50,48% of the studies was distributed in the following manner Scopus (12,62%), EBSCO (8,73%), IEEE (11,65%), and ACM (16,50%).”
§ DevSecOps practices and tools > 6.2 Data extraction analysis
plain- Asserted: passes — The authors put it forward as true.
- Checkable: passes — It can be checked against evidence.
- Load-bearing: unclear — It is unclear whether the paper’s conclusions depend on it.
- Based: passes — The paper gives a reason why it holds.
13 more claims
Create a free account to see all 200 claims and every source verdict.
- 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
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.
Rated major: it would touch a result — a value a result rests on, reported and recomputed p-values on opposite sides of the significance level, two passages that conflict with no sign which is right, or a cited work retracted before this paper was published.
In the paper
“| | Total | 895 | 209 | 201 | 215 | 154 | 75 | 103 |”
§ DevSecOps practices and tools > 9 Limitations & threats to validity
Reported 103 · recomputed 98
Rated major: it would touch a result — a value a result rests on, reported and recomputed p-values on opposite sides of the significance level, two passages that conflict with no sign which is right, or a cited work retracted before this paper was published.
In the paper
“| | Total | 895 | 209 | 201 | 215 | 154 | 75 | 103 |”
§ DevSecOps practices and tools > 9 Limitations & threats to validity
Reported 895 · recomputed 839
Rated minor: it would not touch a result — a value no result rests on, a p-value that stays on the same side of the significance level, or a conflict that is clerical, resolved elsewhere in the paper, or outside its own findings.
In the paper
§ 7.2 RQ2 - Which tools can be used to implement the identified DevSecOps practices?
“Out of the 39 DevSecOps practices examined, tools were successfully identified for 27 practices.”
§ 7.2 RQ2 - Which tools can be used to implement the identified DevSecOps practices?
“Within the subset of 25 practices with identified tools, at least three tools were identified for each practice, except for seven practices namely Dynamic Application Security Testing (DAST), Code Review, Interactive Application Security Testing (IAST), Policy as Code, Infrastructure as Code (IaC),”
Rated minor: it would not touch a result — a value no result rests on, a p-value that stays on the same side of the significance level, or a conflict that is clerical, resolved elsewhere in the paper, or outside its own findings.
In the paper
§ 6.3 Contribution per literature type
“The white literature contribution of 50,48% of the studies was distributed in the following manner Scopus (12,62%), EBSCO (8,73%), IEEE (11,65%), and ACM (16,50%).”
§ 8 Conclusion & future work
“Within the pool of studies, White Literature (WL) contributed 49% while Grey Literature (GL) contributed 51%.”
Citations
Cites
Adams, R. J., Smart, P., & Huff, A. S. (2017) · International Journal of Management Reviews · doi:10.1111/ijmr.12102 · Cited by 995 · cited 1×
“It is also recognized that GL sources have many different formats and levels of credibility, defined as shades of GL [50]. the sources of GL in terms of credibility.”
Garousi, V., Felderer, M., & Mäntylä, M. V. (2019) · Information and Software Technology · doi:10.1016/j.infsof.2018.09.006 · Cited by 831
Grey literature in meta-analyses of randomized trials of health care interventions
Hopewell, S., McDonald, S., Clarke, M. J., & Egger, M. (2007) · Cochrane Database of Systematic Reviews · doi:10.1002/14651858.mr000010.pub3 · Cited by 598 · cited 1×
“Since the early nineties, researchers have conducted MLRs in fields such as education [44] and Medicine [45].”
Adams, J., Hillier-Brown, F. C., Moore, H. J., Lake, A. A., Araujo-Soares, V., White, M., & Summerbell, C. (2016) · Systematic Reviews · doi:10.1186/s13643-016-0337-y · Cited by 486
An exploration of technical debt
Tom, E., Aurum, A., & Vidgen, R. (2013) · Journal of Systems and Software · doi:10.1016/j.jss.2012.12.052 · Cited by 438 · cited 1×
“Within Software Engineering (SE), MLRs are being undertaken as exploratory studies [46] [47] and are seen as beneficial due to the practical nature of the field [43].”
Towards Rigor in Reviews of Multivocal Literatures: Applying the Exploratory Case Study Method
Ogawa, R. T., & Malen, B. (1991) · Review of Educational Research · doi:10.3102/00346543061003265 · Cited by 247 · cited 1×
“Some of the challenges for researchers while selecting GL sources are accessibility, dis-coverability, bias, low quality, and lack of standardization [49] [41].”
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 · cited 7×
“There is available literature that identi-fies and details activities within DevSecOps [51] [10] [52].”
InfluentialWhat is DevOps?: A Systematic Mapping Study on Definitions and Practices
Jabbari, R., bin Ali, N., Petersen, K., & Tanveer, B. (2016) · Proceedings of the Scientific Workshop Proceedings of XP2016 · doi:10.1145/2962695.2962707 · Cited by 230 · cited 2×
“The perceived most common DevOps practices in literature are Continuous Integration, Continuous Delivery, Continuous Monitoring, and Continuous Testing [14] [16] [17] [18] [19] [20].”
Continuous software engineering and beyond: trends and challenges
Fitzgerald, B., & Stol, K.-J. (2014) · Proceedings of the 1st International Workshop on Rapid Continuous Software Engineering · doi:10.1145/2593812.2593813 · Cited by 212 · cited 2×
“Through approaches such as DevOps the speed at which Software Development is released has increased [7] increasing the pressure for the inclusion of security and compliance requirements [2].”
Garousi, V., Felderer, M., & Mäntylä, M. V. (2016) · Proceedings of the 20th International Conference on Evaluation and Assessment in Software Engineering · doi:10.1145/2915970.2916008 · Cited by 210 · cited 3×
“Therefore, to mitigate the challenges of working with GL sources, this research will adopt systematic guidelines for performing MLR in SE [43] that provide the research with a structured process to search, collect, and extract data from GL. Figure 3 represents the adopted process for the MLR in…”
Research works printed but not linked: 14
- J. Humble and D. Farley, Continuous Delivery: Reliable Software Releases Through Build, Test, and Deployment Automation, Addison-Wesley Professional, 2010.
- Smeds, J., Nyborn, K., Pores, I.: DevOps: A Definition and Perceived Adoption Impediments. Agile Proce. Softw. Eng. Extreme Program. 212, 166–177 (2015)
- Kim, G., Humble, J., Debois, P., Willis, J.: The DevOps Handbook, Portland, OR. IT Revolution Press, USA (2016)
- Floris, E.: DevOps is Simply Interaction Between Development and Operations," in First International Workshop DevOps 2018. Chateau de Villebrumier, France (2019)
- Humble, J., Molesky, J.: Why enterprises must adopt devops to enable continuous delivery. Cutter IT Journal 24, 6–12 (2011)
- Davis, J., Daniels, K.: Effective DevOps. O’Reilly Media, USA (2016)
- Wilson, G.: DevSecOps. Rethink Press, UK (2020)
- Bird, J.: DevOpsSec, Sebastopol, CA. O’Reilly, USA (2016)
- Candel, J.: Implementing DevSecOps with Docker and Kubernetes. BPB Publications, India (2022)
- Kitchenham, B.: Procedures for performing systematic reviews." Keele. UK, Keele Univ. 33, 1–26 (2004)
- Zaydi, M., Nassereddine, B.: DevSecOps practices for an agile and secure IT service management. Int. J. Inf. Decis. Sci. 23, 134–149 (2020)
- 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)
- 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
- 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
Cybersecurity in DevOps Environments: A Systematic Literature Review
Ramos, R. C. B., & Yoo, S. G. (2025) · IEEE Access · doi:10.1109/access.2025.3582892 · Cited by 17
“In [71], a comprehensive review of existing solutions is presented, categorizing tools by purpose: static analysis (SAST), dynamic analysis (DAST), secure secret management, compliance-as-code, and operational monitoring.”
Khadem, E. A., & Movaghar, A. (2025) · Array · doi:10.1016/j.array.2025.100547 · Cited by 10
Unified AI and ML Framework in DevSecOps Practices, Solving Real-World Problems
Muthukrishnan, H., Viradia, V., & Yadav, D. (2025) · IEEE SoutheastCon · doi:10.1109/southeastcon56624.2025.10971458 · Cited by 7
“DevOps merges Development (Dev) and Operations (Ops)[1], while DevSecOps, an evolution of the DevOps methodology, prioritizes integrating security practices throughout the entire software development lifecycle [2].”
Toward a Robust and Enhanced DevSecOps Framework
Ramos, R. C. B., & Yoo, S. G. (2025) · Communications in computer and information science · doi:10.1007/978-3-032-08366-1_28 · Cited by 3
Property-Based Testing for Cybersecurity: Towards Automated Validation of Security Protocols
Reis, M. J. C. S. (2025) · Computers · doi:10.3390/computers14050179 · Cited by 6
Metadata
- Authors
- Prates, L., & Pereira, R.
- Affiliations
- Iscte – Instituto Universitário de Lisboa (PT)
- Corresponding author
- Prates, Luís
- ORCID
- Pereira, Rúben
- 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
- hybrid
- doi.org
- Licence
- cc-by
- creativecommons.org/licenses/by/4.0 (tdm)
- creativecommons.org/licenses/by/4.0 (vor)
- 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.