The DOI matches its Crossref record.
Advances in DevSecOps and the Future of Cybersecurity using Automation
Open accessAbstract
DevSecOps (“Development” + “Security” + “Operations”) combines security practices into the DevOps lifecycle, for a holistic, unified, and continuous approach to software development and delivery. DevSecOps closes the divide between the dev and infrastructure teams, and solves the problems that occur
Overview
The claims and statistics of this paper haven’t been checked yet.
Run the check — free, no account needed. It reads the open-access text and checks the sources it cites.
Integrity signals
Registry
Cites
Statistics
Verification
Claims the paper makes
The claims and statistics of this paper haven’t been checked yet.
Run the check — free, no account needed. It reads the open-access text and checks the sources it cites.
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?
The literature identifies persistent limitations including tool incompatibility, challenges with legacy systems, fragmented security policies, and resistance to change within organisations.
“yet the literature identifies persistent limitations including tool incompatibility, challenges with legacy systems, fragmented security policies, and resistance to change within organisations.”
From Evolution of DevSecOps and Its Influence on Application Security: A Systematic Literature Review (2025) · cites this paper as [36]
Section 8.1, “Tool Overload and Compatibility,” explicitly identifies tool compatibility problems. Section 5, “Discussion,” describes difficulty integrating tools into existing development environments and a steep learning curve, but does not specifically identify legacy systems or organisational resistance to change. Section 11.4 refers to administering security policies as a unified fabric rather than separate silos, but does not establish fragmented policies as a persistent limitation. Page numbers were not available in our copy. (LLM, conf=0.85)
Experimental — accuracy not yet measuredAutomation significantly boosts cybersecurity by enabling rapid vulnerability detection and more efficient compliance processes.
“showing that automation significantly boosts cybersecurity by enabling rapid vulnerability detection and more efficient compliance processes”
From Evolution of DevSecOps and Its Influence on Application Security: A Systematic Literature Review (2025) · cites this paper as [36]
Self-check
Percentages, sums and reported differences re-computed from the paper’s own numbers.
The self-check needs the paper’s full text.
Citations
Cites
The publisher hasn’t deposited this paper’s reference list.
Research works printed but not linked: 12
- Wichers, D. (2021). OWASP Top 10: 2021 Edition. OWASP Foundation.
- Chatterjee, R., & Sen, S. (2022). "Integrating Security in DevOps: A Systematic Literature Review." Journal of Systems and Software, 189, 111329.
- Liu, X., Li, X., & Chen, Y. (2022). "Automated Software Composition Analysis and Open- Source Dependency Management." IEEE Transactions on Software Engineering, 48(6), 2285- 2300.
- Gkortzis, A., et al. (2022). "Security Compliance in Infrastructure-as-Code: An Empirical Study." ACM Transactions on Software Engineering and Methodology (TOSEM), 31(4), 1-36.
- Sharma, V., & Coyne, E. (2021). "A Practical Approach to DevOps Using Jenkins." International Journal of Computer Applications, 183(35), 12-17.
- Luis Prates, Ruben Pereira (2024). "DevSecOps Practices and Tools." International Journal of Information Security.
- M. A. Aljohani and S. S. Alqahtani. 2023. A Unified Framework for Automating Software Security Analysis in DevSecOps," in International Conference on Smart Computing and Application (ICSCA), Hail, Saudi Arabia.
- L. Verderame, L. Caviglione, R. Carbone and A. Merlo. 2023. SecCo: Automated Services to Secure Containers in the DevOps Paradigm," in Proceedings of the 2023 International Conference on Research in Adaptive and Convergent Systems (RACS '23), New York, NY, USA.
- N. Bernardino, B. Sequeira, E. Piza, F. Henriques, F. Neves and C. I. Reis. 2024. Enhancing DevSecOps: Three Custom Tools for Continuous Security," in IEEE 11th International Conference on Cyber Security and Cloud Computing (CSCloud). Shanghai. China.
- R. N. Rajapakse, M. M. Zahedi, A. Babar and H. Shen. 2022. Challenges and solutions when adopting DevSecOps: A systematic review," Information and Software Technology" vol. 141
- Woody, C., Chick, T., Reffett, A., Pavetti, S., Laughlin, R., Frye, B., Bandor, M.: DevSecOps Pipeline for Complex SoftwareIntensive Systems: Addressing Cybersecurity Challenges. J Syst, Cybern Inf: JSCI 18(5), 31-36 (2020)
- H. Yasar and S. E. Teplov, "DevSecOps In Embedded Systems: An Empirical Study Of Past Literature," in Proceedings of the 17th International Conference on Availability, Reliability and Security, Vienna, Austria, 2022.
Cited by
Sorted by citations
Evolution of DevSecOps and Its Influence on Application Security: A Systematic Literature Review
Mohammed, K., Shanmugam, B., & El-Den, J. (2025) · Technologies · doi:10.3390/technologies13120548 · Cited by 8
Metadata
- Authors
- Pranav, M., Madhesh, I., Lenin, J., & Sasikumar, R.
- Corresponding author
- Pranav, M.
- Venue
- Proceedings of the 4th International Conference on Information Technology, Civil Innovation, Science, and Management, ICITSM 2025, 28-29 April 2025, Tiruchengode, Tamil Nadu, India, Part I
- Publisher
- EAI
- Published
- 2025
- OpenAlex
- W4415438127
- Cited by
- 1
- References
- 0
- Citations by year
- 2025: 1
- FWCI
- 1.20
- Type
- conference paper
- Language
- en
- Open access
- bronze
- doi.org
- Locations
- International Conference on Information Technology, Civil Innovation, Science, and Management (ICITSM) (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, DevOps, cybersecurity, software development lifecycle, security automation, software delivery
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