Continuous Security Testing: A Case Study on Integrating Dynamic Security Testing Tools in CI/CD Pipelines
Open accessThe DOI matches its Crossref record; 4 of the 4 references it cites were found in a registry or an index.
Abstract
Continuous Integration (CI) and Continuous Delivery (CD) have become a well-known practice in DevOps to ensure fast delivery of new features. This is achieved by automatically testing and releasing new software versions, e.g. multiple times per day. However, classical security management techniques cannot keep up with this quick Software Development Life Cycle (SDLC). Nonetheless, guaranteeing high security quality of software systems has become increasingly important. The new trend of DevSecOps aims to integrate security techniques into existing DevOps practices. Especially, the automation of security testing is an important area of research in this trend. Although plenty of literature discusses security testing and CI/CD practices, only a few deal with both topics together. Additionally, most of the existing works cover only static code analysis and neglect dynamic testing methods. In this paper, we present an approach to integrate three automated dynamic testing techniques into a CI/CD pipeline and provide an empirical analysis of the introduced overhead. We then go on to identify unique research/technology challenges the DevSecOps communities will face and propose preliminary solutions to these challenges. Our findings will enable informed decisions when employing DevSecOps practices in agile enterprise applications engineering processes and enterprise security.
Overview
The claims and statistics of this paper haven’t been checked yet.
Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.
Integrity signals
Registry
Cites
Statistics
Verification
Claims the paper makes
The claims and statistics of this paper haven’t been checked yet.
Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.
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
DevSecOps: A Multivocal Literature Review
Myrbakken, H., & Colomo-Palacios, R. (2017) · Communications in Computer and Information Science · doi:10.1007/978-3-319-67383-7_2 · Cited by 205 · cited 7×
“DevSecOps establishes a proactive approach to limit the attack surface of the application [6] and entails considering security from the very beginning of the project [2].”
BackgroundInfluentialArachchi, S. A. I. B. S., & Perera, I. (2018) · 2018 Moratuwa Engineering Research Conference (MERCon) · doi:10.1109/mercon.2018.8421965 · Cited by 97 · cited 1×
“Continuous Integration (CI) and Continuous Delivery (CD) are software engineering processes used in DevOps in order to improve the efficiency of projects [16].”
An Empirical Study on Culture, Automation, Measurement, and Sharing of DevSecOps
Tomas, N., Li, J., & Huang, H. (2019) · 2019 International Conference on Cyber Security and Protection of Digital Services (Cyber Security) · doi:10.1109/cybersecpods.2019.8884935 · Cited by 66 · cited 5×
“Traditionally, security experts were organized into separate silos and security concerns were addressed after the actual design and development stages [8].”
InfluentialWhere to Integrate Security Practices on DevOps Platform
Yasar, H., & Kontostathis, K. (2016) · International Journal of Secure Software Engineering · doi:10.4018/ijsse.2016100103 · Cited by 25 · cited 3×
“Yasar and Kontostathis provide the 8 best practices on how to ensure sufficient security in DevOps [6].”
Cited by
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
“Various tools and technologies are available to support automated security checks in DevSecOps pipelines (Rangnau et al ., 2020).”
MethodPrates, L., & Pereira, R. (2025) · International Journal of Information Security · doi:10.1007/s10207-024-00914-z · Cited by 49
“Integrating SAST into the development pipeline, security issues can be iden-tified early in the development process, allowing for timely resolution [56].”
InfluentialA Unified Framework for Automating Software Security Analysis in DevSecOps
Aljohani, M. A., & Alqahtani, S. S. (2023) · 2023 International Conference on Smart Computing and Application (ICSCA) · doi:10.1109/icsca57840.2023.10087568 · Cited by 17
“[14] studied and explained how to conduct Dynamic Application Security Testing (DAST) in a CI/CD pipeline.”
BackgroundSecuring Infrastructure as Code (IaC) through DevSecOps:A Comprehensive Risk Management Framework
Zeini, A., Lennon, R. G., & Lennon, P. (2023) · 2023 Cyber Research Conference - Ireland (Cyber-RCI) · doi:10.1109/cyber-rci59474.2023.10671452 · Cited by 4
DevSecOps in Finance: Strengthening the Security Model of Applications
David, P., Kushwaha, M. K., & Suseela, G. (2024) · 2024 4th International Conference on Data Engineering and Communication Systems (ICDECS) · doi:10.1109/icdecs59733.2023.10502917 · Cited by 2
Metadata
- Authors
- Rangnau, T., Buijtenen, R. V., Fransen, F., & Turkmen, F.
- Venue
- 2020 IEEE 24th International Enterprise Distributed Object Computing Conference (EDOC)
- Publisher
- IEEE
- Published
- 2020-10
- Pages
- 145-154
- ISSN
- 1541-7719 (ISSN-L)
- OpenAlex
- W3093836561
- Cited by
- 97
- References
- 4
- FWCI
- 6.55
- Type
- conference paper
- Language
- en
- Open access
- green
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
How to cite
Cite CoChat for the checks on this page, and the paper for its own findings.
- This page
- CoChat. (2026). Citation check: Continuous Security Testing: A Case Study on Integrating Dynamic Security Testing Tools in CI/CD Pipelines. https://app.cochat.ai/papers/10.1109/edoc49727.2020.00026
- The paper
- Rangnau, T., Buijtenen, R. V., Fransen, F., & Turkmen, F. (2020). Continuous Security Testing: A Case Study on Integrating Dynamic Security Testing Tools in CI/CD Pipelines. 2020 IEEE 24th International Enterprise Distributed Object Computing Conference (EDOC). https://doi.org/10.1109/edoc49727.2020.00026
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.