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.
Evolution of DevSecOps and Its Influence on Application Security: A Systematic Literature Review
Open accessAbstract
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
Cites
Statistics
Verification
Claims the paper makes
31 Valid · 28 Not valid · 52 Not checked · 108 Own results and interpretations
The cited sources support only part of this claim — read each source’s verdict below.
In the paper
“Highly regulated sectors such as healthcare, finance, and government face additional hurdles due to stringent compliance requirements, further complicating DevSecOps implementation.”
§ Evolution of DevSecOps and Its Influence on Application Security: A Systematic Literature Review > 1. Introduction
What the sources say
- Partly supportedcites [17] Cankar, M., Petrovic, N., Pita Costa, J., Cernivec, A., Antic, J., Martincic, T., and Stepec, D. (2023, January 15–19). Security in DevSecOps: Applying Tools and Machine Learning to Verification and Monitoring Steps. Proceedings of the ICPE 2023—Companion of the 2023 ACM/SPEC International Conference on Performance Engineering, Coimbra, Portugal. sourceExperimental — accuracy not yet measured
Section 5 (page unavailable) describes checking application compliance with standards as a complex task for auditors, and the Abstract identifies healthcare as a sensitive domain. The paper does not say that stringent compliance requirements create additional DevSecOps implementation hurdles in healthcare, finance, and government. (LLM, conf=0.76)
- Not checked — no full text of the sourcecites [18] Chen, T., and Suo, H. (2022). Design and Practice of Security Architecture via DevSecOps Technology. Proceedings of the IEEE International Conference on Software Engineering and Service Sciences, Beijing, China, 21–23 October 2022, IEEE Computer Society. ICSESS. source
- Not checked — no full text of the sourcecites [19] David, P., Kushwaha, M.K., and Suseela, G. (2024, January 22–23). DevSecOps in Finance: Strengthening the Security Model of Applications. Proceedings of the IEEE International Conference on Data Engineering and Communication Systems, ICDECS, Bengaluru, India. source
plainstates a cause- 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.
- Partly supported
The sources with a verdict support this claim; the rest weren’t checked yet, have no full text we could read, or their verdicts aren’t rated yet.
In the paper
“Ramaj et al. [25] and Rajapakse et al. [28] document the technical, cultural, and compliance-related barriers organisations face when adopting DevSecOps, while other works provide prescriptive strategies for change management and migration.”
§ Evolution of DevSecOps and Its Influence on Application Security: A Systematic Literature Review > 1.5. Comparison of Existing Survey Papers
What the sources say
- Supportedcites [25] Ramaj, X., Sánchez-Gordón, M., Gkioulos, V., Chockalingam, S., and Colomo-Palacios, R. (2022). Holding on to Compliance While Adopting DevSecOps: An SLR. Electronics, 11. source
The Discussion and Future Work section identifies resistance to new ways of working as a cultural barrier. Sections 5.1.2 (Management) and 5.1.3 (Technicalities) discuss obstacles involving compliance-tool awareness and processes that cannot be automated. Together, these passages support the claim that Ramaj et al. document cultural, technical, and compliance-related barriers to DevSecOps adoption; the separate attribution to Rajapakse et al. is not assessed here. (LLM, conf=0.90)
- Not checked — no full text of the sourcecites [28] Rajapakse, 2022, Challenges and solutions when adopting DevSecOps: A systematic review, Inf. Softw. Technol. source
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.
- Supported
The cited sources support only part of this claim — read each source’s verdict below.
In the paper
“Compliance and risk management appear as additional focal points, with compliance automation recognised as underexplored in both research and industry practice [25].”
§ Evolution of DevSecOps and Its Influence on Application Security: A Systematic Literature Review > 1.1. Context & Motivation
What the sources say
- Partly supportedcites [25] Ramaj, X., Sánchez-Gordón, M., Gkioulos, V., Chockalingam, S., and Colomo-Palacios, R. (2022). Holding on to Compliance While Adopting DevSecOps: An SLR. Electronics, 11. sourceExperimental — accuracy not yet measured
The Discussion and Future Work section (page unavailable) reports a low number of studies on integrating compliance into DevSecOps, supporting the research-gap portion of the claim. It also notes challenges automating compliance validation, but does not establish that compliance automation is underexplored across industry practice. (LLM, conf=0.82)
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.
- Partly supported
Every source the paper cites for this claim was checked and supports it.
In the paper
“Akbar et al. [29] provide a comprehensive analysis of the barriers to DevSecOps implementation by systematically identifying 18 distinct challenges, which are organised into 10 core categories.”
§ Evolution of DevSecOps and Its Influence on Application Security: A Systematic Literature Review > 3.1. DevSecOps Evolution
What the sources say
- Supportedcites [29] Akbar, 2022, Toward successful DevSecOps in software development organizations: A decision-making framework, Inf. Softw. Technol. source
The Summary of study findings (Section 5) says the authors used a multivocal literature review to identify 18 DevSecOps challenging factors related to 10 key categories, then surveyed practitioners about their significance. The Conclusion (Section 8) likewise describes 18 factors across ten key areas of software security. (LLM, conf=0.94)
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.
- Supported
Every source the paper cites for this claim was checked and supports it.
In the paper
“showing that automation significantly boosts cybersecurity by enabling rapid vulnerability detection and more efficient compliance processes”
§ Evolution of DevSecOps and Its Influence on Application Security: A Systematic Literature Review > 3.1. DevSecOps Evolution
What the sources say
- Supportedcites [36] Pranav, M., Madhesh, I., Lenin, J., and Sasikumar, R. (2025). Advances in Devsecops and the Future of Cybersecurity Using Automation, EAI Endorsed Transactions. source
The Results and Evaluation section reports increased vulnerability detection with automation and higher compliance scores from real-time automated checks. The Discussion adds that continuous compliance scans and reports reduced manual compliance work, supporting the claim about more efficient compliance processes. (LLM, conf=0.93)
- Supportedcites [38] Zhou, 2023, Revisit security in the era of DevOps: An evidence-based inquiry into DevSecOps industry, IET Softw. source
Section 5.3.3 says automated security checks substantially reduce the time needed to discover errors. Section 5.4.3 says automation speeds security work and that compliance as code helps identify and fix deviations early. Together, these support the paraphrase in the DevSecOps context. (LLM, conf=0.88)
boostedstates a cause- 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.
- Supported
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.
- Probably not a substantial claim. 129
- It may state two separate claims as one. 97
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
“The first level of screening included a review of the titles and abstracts of the 347 studies.From this, 75 studies were excluded because they did not meet the inclusion criteria.Of the remaining 134 studies, full texts were reviewed to assess their eligibility.”
§ Evolution of DevSecOps and Its Influence on Application Security: A Systematic Literature Review > 2.4. Analysis Method
Reported 134 · recomputed 272
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
§ Evolution of DevSecOps and Its Influence on Application Security: A Systematic Literature Review > 2.1. Search Strategy
“Inclusion criteria required that sources be peer-reviewed and published in English.”
§ Evolution of DevSecOps and Its Influence on Application Security: A Systematic Literature Review > 1.3. Scope
“The review draws upon academic literature sourced from Scopus and relevant grey literature identified via Google Search.”
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
§ Evolution of DevSecOps and Its Influence on Application Security: A Systematic Literature Review > 2.4. Analysis Method
“This study employs the PRISMA framework [42] to systematically guide the screening and organisation of selected literature.”
§ Evolution of DevSecOps and Its Influence on Application Security: A Systematic Literature Review > References
“42. Lombardi, F.; Fanton, A. From DevOps to DevSecOps is not enough. CyberDevOps: An extreme shifting-left architecture to bring cybersecurity within software security lifecycle pipeline. Softw. Qual. J. 2023, 31, 619-654. [CrossRef]”
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
§ Evolution of DevSecOps and Its Influence on Application Security: A Systematic Literature Review > 2.4. Analysis Method
“Of the remaining 134 studies, full texts were reviewed to assess their eligibility.”
§ Evolution of DevSecOps and Its Influence on Application Security: A Systematic Literature Review > 2.4. Analysis Method
“59 studies were assessed in the full-text assessment stage.”
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
§ Evolution of DevSecOps and Its Influence on Application Security: A Systematic Literature Review > 3.3. Frameworks
“While the findings offer valuable insights into organisational resilience, the study is industry-specific and does not directly address DevSecOps or application security, limiting its relevance to the core focus of this review.”
§ Evolution of DevSecOps and Its Influence on Application Security: A Systematic Literature Review > 6. Conclusions
“| Frameworks | [55] | Adaptive Governance Framework | Resilience and governance in GVCs through DevSecOps, managing external shocks | Governance frameworks for resilience | Resource reconfiguration, disruption orientation, sustainability of supply chain performance |”
Citations
Cites
The PRISMA 2020 statement: An updated guideline for reporting systematic reviews
Page, M. J., McKenzie, J. E., Bossuyt, P. M., Boutron, I., Hoffmann, T. C., Mulrow, C. D., Shamseer, L., Tetzlaff, J. M., Akl, E. A., Brennan, S. E., et al. (2021) · BMJ · doi:10.1136/bmj.n71 · Cited by 108,283
The PRISMA 2020 statement: an updated guideline for reporting systematic reviews
Page, M. J., McKenzie, J., Bossuyt, P., Boutron, I., Hoffmann, T., mulrow, C., Shamseer, L., Tetzlaff, J., Akl, E., Brennan, S. E., et al. (2020) · doi:10.31222/osf.io/v7gm2 · Cited by 5,177
A Survey of Machine and Deep Learning Methods for Internet of Things (IoT) Security
Al-Garadi, M. A., Mohamed, A., Al-Ali, A. K., Du, X., Ali, I., & Guizani, M. (2020) · IEEE Communications Surveys & Tutorials · doi:10.1109/comst.2020.2988293 · Cited by 1,392
A Survey of DevOps Concepts and Challenges
Leite, L., Rocha, C., Kon, F., Milojicic, D., & Meirelles, P. (2020) · ACM Computing Surveys · doi:10.1145/3359981 · Cited by 484
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
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
Kumar, R., & Goyal, R. (2020) · Computers & Security · doi:10.1016/j.cose.2020.101967 · Cited by 97
Lombardi, F., & Fanton, A. (2023) · Software Quality Journal · doi:10.1007/s11219-023-09619-3 · Cited by 54
Bahaa, A., Abdelaziz, A., Sayed, A., Elfangary, L., & Fahmy, H. (2021) · Information · doi:10.3390/info12040154 · Cited by 48
Abiona, O. O., Oladapo, O. J., Modupe, O. T., Oyeniran, O. C., Adewusi, A. O., & Komolafe, A. M. (2024) · World Journal of Advanced Engineering Technology and Sciences · doi:10.30574/wjaets.2024.11.2.0093 · Cited by 48
Research works printed but not linked: 7
- Succi, 2021, AI Empowered DevSecOps Security for Next Generation Development, Communications in Computer and Information Science, Volume 1523 CCIS, 32
- Rangaraju, 2023, Incorporating AI-driven strategies in DevSecOps for robust cloud security, Int. J. Innov. Sci. Res. Technol., 8, 7
- 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.
- Sandu, 2021, DevSecOps: Integrating Security into the DevOps Lifecycle for Enhanced Resilience, Technol. Manag. Rev., 6, 1
- Lee, 2023, Microservices-based DevSecOps Platform using Pipeline and Open Source Software, J. Inf. Sci. Eng., 39, 1117
- Yilmaz, 2023, Towards a DevSecOps-Enabled Framework for Risk Management of Critical Infrastructures, Communications in Computer and Information Science, Volume 1890 CCIS, 47
- Jose, 2024, Harnessing the Power of AI: Transforming DevSecOps for Enhanced Cloud Security, Int. J. Comput. Inf. Eng., 18, 335
Cited by
A Secure and Scalable Cloud-Based Banking Service Model Leveraging AI and Advanced Cyber Security
Gajula, S., & Margam, M. (2026) · IEEE International Conference on AI in Cybersecurity (ICAIC) · doi:10.1109/icaic67076.2026.11395704 · Cited by 23
“The necessity of the single device that can guarantee security, the intelligence, and scalability is the topical issue, so the creation of the model of the offered safe and scalable cloud-based banking service is encouraged [7].”
Security Risks in Responsive Web Design Frameworks
Almeida, F., & Sousa, C. (2026) · Digital · doi:10.3390/digital6010026 · Cited by 1
From prototype to deployment: An EU-centric lifecycle framework for law enforcement AI
Aramburu, M., García, J., Gaines, S., Touleimat, N., Mattina, E. L., Akhgar, B., & Kavallieros, D. (2026) · Open Research Europe · doi:10.12688/openreseurope.21859.1
“21,22 Moreover, robustness is commonly operationalised as technical stability (e.g., resilience to drift), which does not fully capture the procedural accountability and transparency expectations associated with high-stakes security deployments.”
Implementation of Secure DevOps (DevSecOps) in System Administration Workflows
Quijano, J., & Rey, W. P. (2026) · International Conference on Computer Communication and Artificial Intelligence (CCAI) · doi:10.1109/ccai69603.2026.11641976
Security Challenges and Solutions in Cloud Computing Environments
Abo-Torkhoma, A. A.-L. H., Abo-torkhoma, A. A.-L. H., & Ali, G. S. H. (2026) · Emirates International University Journal · doi:10.64059/eiu.v3i1.227
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
- gold
- doi.org
- Licence
- 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
How to cite
Cite CoChat for the checks on this page, and the paper for its own findings.
- This page
- CoChat. (2026). Citation check: Evolution of DevSecOps and Its Influence on Application Security: A Systematic Literature Review. https://app.cochat.ai/papers/10.3390/technologies13120548
- The paper
- Mohammed, K., Shanmugam, B., & El-Den, J. (2025). Evolution of DevSecOps and Its Influence on Application Security: A Systematic Literature Review. Technologies. https://doi.org/10.3390/technologies13120548
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.