CoChat

Evolution of DevSecOps and Its Influence on Application Security: A Systematic Literature Review

Open access
Mohammed, Khwaja, Shanmugam, Bharanidharan, El-Den, Jamal · 2025 · Technologies

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

Abstract

This systematic literature review (SLR) investigates the current landscape of DevSecOps by analysing peer-reviewed studies published between 2012 and 2025. The review identifies key themes including automation, continuous security integration, toolchain orchestration, and cultural transformation. At the same time, it underscores the persistent challenges of embedding security within fast-paced development cycles, such as the absence of standardised practices, difficulties in achieving tool interoperability, and resistance at the organisational level. By synthesising findings across 36 selected studies, this paper rightly identified the gaps including seamless integration of security tools, lack of comprehensive frameworks for effective deployment, scalability in cloud-native technologies for effective DevSecOps adoption. In response, the study outlines future research directions aimed at bridging these gaps, particularly in areas of empirical validation and scalability.

Overview

CoChat Summary

TL;DR

This systematic literature review synthesises 36 studies published between 2012 and 2025 to map DevSecOps evolution and its influence on application security. It finds strong support for shift-left security, automation, IaC, and AI/ML, but persistent gaps in standardisation, tool integration, empirical validation, and scalability.

Key findings

  • Across 36 included studies, the review identifies automation, continuous security integration, toolchain orchestration, and cultural transformation as key themes; persistent challenges include the absence of standardised practices, difficulties in tool interoperability, and organisational resistance.
  • Shift-left security and automated tools such as SAST, DAST, vulnerability scanning, and threat modelling in CI/CD pipelines are widely advocated to detect risks early, reduce rework and cost, support compliance, and strengthen security posture; however, few studies provide quantitative or longitudinal evidence.
  • AI/ML integration is emerging for automated threat detection, predictive analytics, and intelligent CI/CD automation, but research is largely conceptual or case-study based, with concerns about data privacy, algorithm transparency, ethics, false positives, and scalability.
  • Research gaps include seamless integration of security tools into CI/CD, lack of comprehensive frameworks for AI/ML deployment, organisational and cultural barriers, scalability in IoT and cloud-native technologies, and absence of standardised metrics for assessing DevSecOps effectiveness.

Methods

  • Systematic literature review using the PRISMA framework; academic sources from Scopus and grey literature via Google Search; inclusion criteria required studies published 2012–2025, peer-reviewed, and in English, with keywords including “DevSecOps”, “SecDevOps”, “Continuous Security”, “Application Security”, “Shift-Left”, “Infrastructure as Code (IaC)”, and “Security as Code”.
  • Screening: 368 references were imported; 1 duplicate was manually removed and 20 additional duplicates were identified by Covidence, leaving 347 unique studies; 75 studies were excluded at title/abstract screening; 59 full texts were assessed; 23 were excluded (12 inappropriate study designs, 8 irrelevant settings, 2 non-related outcomes, 1 intervention not included); 36 studies were included.
  • Data extraction used predefined coding schemes in Covidence, followed by thematic analysis to identify recurring trends, patterns, gaps, and implementation frameworks.

Limitations

  • The paper states that heavy reliance on expert opinion introduces subjectivity and potential bias, limiting generalisability; many frameworks are validated only through narrow case studies; there is a lack of large-scale, cross-industry, or longitudinal empirical validation; and heterogeneity, variable study quality, potential publication bias, and rapid technological change may render some insights outdated.
  • The paper states that over-specialisation on cloud-native or mature DevSecOps contexts may not translate to hybrid, on-premises, or earlier-stage organisations, and that AI/ML research is largely conceptual or small-scale with limited evidence of scalability or cross-industry applicability.
  • Evident from the text: the reported screening counts are internally inconsistent (347 unique after deduplication, 75 excluded, then “remaining 134” and “59 full-text assessed”), and at least one included framework study (Islam & Chadee on global value chain apparel suppliers) is noted as not directly addressing DevSecOps or application security.

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

Integrity signals

Registry

Crossref · 10.3390/technologies13120548

Cites

48 of 48 references verified0 citation errors · 0 not checkable

Statistics

Nothing to recompute.

Verification

Claims the paper makes

31 Valid · 28 Not valid · 52 Not checked · 108 Own results and interpretations

40 more claims · 2 with their cited sources checked

Create a free account to see all 219 claims and to verify the 6 references still open.

See all claims — free account
  • Probably not a substantial claim. 129
  • It may state two separate claims as one. 97

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.

5 of 5

Citations

Cites

Research works printed but not linked: 7

  1. Succi, 2021, AI Empowered DevSecOps Security for Next Generation Development, Communications in Computer and Information Science, Volume 1523 CCIS, 32
  2. Rangaraju, 2023, Incorporating AI-driven strategies in DevSecOps for robust cloud security, Int. J. Innov. Sci. Res. Technol., 8, 7
  3. Kahan, N. (2025, June 10). DevSecOps in Action: Shifting Left and Securing Right for Next-Gen Cloud-Native Security. ResearchGate. Available online: https://www.researchgate.net/publication/386076256.
  4. Sandu, 2021, DevSecOps: Integrating Security into the DevOps Lifecycle for Enhanced Resilience, Technol. Manag. Rev., 6, 1
  5. Lee, 2023, Microservices-based DevSecOps Platform using Pipeline and Open Source Software, J. Inf. Sci. Eng., 39, 1117
  6. Yilmaz, 2023, Towards a DevSecOps-Enabled Framework for Risk Management of Critical Infrastructures, Communications in Computer and Information Science, Volume 1890 CCIS, 47
  7. Jose, 2024, Harnessing the Power of AI: Transforming DevSecOps for Enhanced Cloud Security, Int. J. Comput. Inf. Eng., 18, 335

Cited by

See all 8

Metadata

Authors
Mohammed, K., Shanmugam, B., & El-Den, J.
Affiliations
  • Charles Darwin University (AU)
  • Faculty of Science and Technology, Charles Darwin University, Sydney, NSW 2000, Australia
Corresponding author
  • Mohammed, Khwaja
  • Shanmugam, Bharanidharan
Venue
Technologies
Publisher
MDPI AG
Published
2025-11-25
Volume
13
Issue
12
Pages
548
ISSN
2227-7080 (ISSN-L)
OpenAlex
W4416764585
Cited by
8
References
38
Citations by year
2026: 8
FWCI
1.24
Type
journal article
Language
en
Open access
Locations
  • Technologies (publishedVersion, cc-by)
  • DOAJ (DOAJ: Directory of Open Access Journals) (submittedVersion, cc-by-sa)
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, software security, security automation, cloud-native security, security framework, DevOps culture

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).

Cited sources are checked with a language model’s help (gpt-6-sol).

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

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.