Integrating Security with DevSecOps: Techniques and Challenges
Abstract
The delivery of software applications is key to the success of many development organizations. The software development process over the period increased its scope and included other areas like operations with core Information Technology. Software project practices with DevOps have demonstrated how to streamline these processes, improve the quality of products with present technologies and speed up the processes. In the project cell, a university students' organization which undertake software development projects and services implemented the DevOps methodology for student projects. This model showed results with effective completion of projects. However, what was missing was robust and secure applications, increasing concern and risk involved with insecure products that brought our attention to the implementation and integration of security model into our present development process. The goal of this article is to describe the integration of DevSecOps practice to our ongoing projects that will avoid insecure practices during development.
Integrity signals
Registry
Cites
Statistics
Claims the paper makes
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?
Another benefit of DevSecOps is that manual security tests and support activities are reduced by automation, allowing teams to focus more on policies.
“Another benefit is that manual security tests and support activities are reduced by the automation, so that teams can focus more on policies (Ahmed and Francis, 2019).”
From Identifying the primary dimensions of DevSecOps: A multi-vocal literature review (2024) · cites this paper as Ahmed and Francis, 2019
Cites
Continuously integrating security
Williams, L. (2018) · Proceedings of the 1st International Workshop on Security Awareness from Design to Deployment · doi:10.1145/3194707.3194717 · Cited by 10 · see citing works
Flagged first, then by citations
Cited by
Sorted by citations
Prates, L., & Pereira, R. (2025) · International Journal of Information Security · doi:10.1007/s10207-024-00914-z · Cited by 49 · see citing works
“DevSecOps term is a combination of the DevOps term merged with Security (Sec) [27] and represents the integration of security practices into DevOps [10].”
InfluentialIdentifying the primary dimensions of DevSecOps: A multi-vocal literature review
Zhao, X., Clear, T., & Lal, R. (2024) · Journal of Systems and Software · doi:10.1016/j.jss.2024.112063 · Cited by 40 · see citing works
Navigating the DevOps landscape
Zhang, X., Zhao, P., & Jaskolka, J. (2025) · Journal of Systems and Software · doi:10.1016/j.jss.2024.112331 · Cited by 21 · see citing works
Integrating security controls in DevSecOps: Challenges, solutions, and future research directions
Sinan, M., Shahin, M., & Gondal, I. (2025) · Journal of Software: Evolution and Process · doi:10.1002/smr.70029 · Cited by 13 · see citing works
- Authors
- Ahmed, Z., & Francis, S. C.
- Affiliations
- Manipal Academy of Higher Education, Dubai (AE)
- Venue
- 2019 International Conference on Digitization (ICD)
- Publisher
- IEEE
- Published
- 2019-11
- Pages
- 178-182
- OpenAlex
- W3034173343
- Cited by
- 44
- References
- 1
- Citations by year
- 2026: 6 · 2025: 9 · 2024: 9 · 2023: 9 · 2022: 5 · 2021: 5 · 2020: 1
- FWCI
- 2.19
- Type
- conference paper
- Language
- en
- Open access
- closed
- Locations
- International Conference on Digitization (ICD) (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, software security, secure software development, student software projects, software development process
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
