Embracing IaC Through the DevSecOps Philosophy: Concepts, Challenges, and a Reference Framework
Open accessThe DOI matches its Crossref record; 9 of the 9 references it cites were found in a registry or an index.
Abstract
We introduce the challenges of DevSecOps philosophy and its applicability to the development and operation of trustworthy infrastructure-as-code, and we combine the solutions into a single framework covering all crucial steps. Finally, we discuss how the proposed framework addresses the challenges and introduce an initial design for it.
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.
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 source backs part of the claim, not all of it — or backs it for a different population, condition or comparison.
In the citing paper
“The framework is primarily conceptual and lacks empirical validation through real-world case studies or quantitative assessments, which limits its proven applicability in diverse operational contexts.”
From Evolution of DevSecOps and Its Influence on Application Security: A Systematic Literature Review (2025) · cites this paper as [30]
Experimental — accuracy not yet measuredThe cited source says what the claim attributes to it.
In the citing paper
“The literature notes that while IaC enables greater consistency and operational efficiency, it also poses potential systemic risks if security is not inherently built into provisioning scripts and configurations.”
From Evolution of DevSecOps and Its Influence on Application Security: A Systematic Literature Review (2025) · cites this paper as [30]
The cited source says what the claim attributes to it.
In the citing paper
“However, the inherent complexity of IaC can introduce errors that compromise reliability.”
From Evolution of DevSecOps and Its Influence on Application Security: A Systematic Literature Review (2025) · cites this paper as [30]
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
Devops: A Software Architect's Perspective
Bass, L., Weber, I. M., & Zhu, L. (2015) · CERN Document Server (European Organization for Nuclear Research) · Cited by 561
A systematic mapping study of infrastructure as code research
Rahman, A., Mahdavi-Hezaveh, R., & Williams, L. (2019) · Information and Software Technology · doi:10.1016/j.infsof.2018.12.004 · Cited by 174
A survey of AIOps methods for failure management
Notaro, P., Cardoso, J., & Gerndt, M. (2021) · ACM Transactions on Intelligent Systems and Technology · doi:10.1145/3483424 · Cited by 142
Adoption, Support, and Challenges of Infrastructure-as-Code: Insights from Industry
Guerriero, M., Garriga, M., Tamburri, D. A., & Palomba, F. (2019) · 2019 IEEE International Conference on Software Maintenance and Evolution (ICSME) · doi:10.1109/icsme.2019.00092 · Cited by 140
The do’s and don’ts of infrastructure code: A systematic gray literature review
Kumara, I., Garriga, M., Romeu, A. U., Nucci, D. D., Palomba, F., Tamburri, D. A., & van den Heuvel, W. (2021) · Information and Software Technology · doi:10.1016/j.infsof.2021.106593 · Cited by 115
The essential deployment metamodel: a systematic review of deployment automation technologies
Wurster, M., Breitenbücher, U., Falkenthal, M., Krieger, C., Leymann, F., Saatkamp, K., & Soldani, J. (2019) · SICS Software-Intensive Cyber-Physical Systems · doi:10.1007/s00450-019-00412-x · Cited by 88
Quattrocchi, G., & Tamburri, D. A. (2022) · IEEE Software · doi:10.1109/ms.2022.3212034 · Cited by 19
On Unifying the Compliance Management of Applications Based on IaC Automation
Falazi, G., Breitenbücher, U., Leymann, F., Stötzner, M., Ntentos, E., Zdun, U., Becker, M., & Heldwein, E. (2022) · IEEE International Conference on Software Architecture Companion (ICSA-C) · doi:10.1109/icsa-c54293.2022.00050 · Cited by 4
From Theory to Practice: The Challenges of a DevOps Infrastructure as Code Implementation
Siebra, C., Lacerda, R., Cerqueira, I., Quintino, J. P., Florentin, F., da Silva, F. Q. B., & Santos, A. L. M. (2018) · International Conference on Software Technologies (ICSOFT) · doi:10.5220/0006826104610470 · Cited by 2
Research works printed but not linked: 1
- 0, How We Build Code at Netflix
Cited by
Security in DevSecOps: Applying Tools and Machine Learning to Verification and Monitoring Steps
Cankar, M., Petrovic, N., Pita Costa, J., Cernivec, A., Antic, J., Martincic, T., & Stepec, D. (2023) · Companion of the 2023 ACM/SPEC International Conference on Performance Engineering · doi:10.1145/3578245.3584943 · Cited by 24
“In this paper, we adopt an approach which tackles the previously mentioned issues related to security and trustworthiness within the scope of DevOps workflows in both the design and run-time phase, based on DevSecOps philosophy [2].”
BackgroundMethodInfluentialSelf-citationMachine Learning-Based Run-Time DevSecOps: ChatGPT Against Traditional Approach
Petrović, N. (2023) · 2023 10th International Conference on Electrical, Electronic and Computing Engineering (IcETRAN) · doi:10.1109/icetran59631.2023.10192161 · Cited by 17
“1 depicts the complete DevSecOps workflow based on practice-approved insights from [2, 3].”
BackgroundInfluentialChat GPT-Based Design-Time DevSecOps
Petrović, N. (2023) · International Scientific Conference on Information, Communication and Energy Systems and Technologies (ICEST) · doi:10.1109/icest58410.2023.10187247 · Cited by 17
“In general, we can distinguish between design phase – which covers planning, creation, verification and packaging on one side and runtime phase – that includes release, configuration and monitoring activities [1, 2].”
BackgroundAutomated Approach to IaC Code Inspection Using Python-Based DevSecOps Tool
Petrović, N., Cankar, M., & Luzar, A. (2022) · Telecommunications Forum (TELFOR) · doi:10.1109/telfor56187.2022.9983681 · Cited by 17
“Therefore, integration of security-oriented aspects in DevOps workflows has emerged into related field, referred to as DevSecOps [6, 7].”
BackgroundSelf-citationReview of Techniques for Integrating Security in Software Development Lifecycle
Saeed, H., Shafi, I., Ahmad, J., Khan, A. A., Khurshaid, T., & Ashraf, I. (2024) · Computers, materials & continua/Computers, materials & continua (Print) · doi:10.32604/cmc.2024.057587 · Cited by 23
“Another challenge is how different organizations will start DevSecOps practices by adopting the change in skills, tools, standards, and processes to successfully implement security into their culture [12].”
Metadata
- Authors
- Alonso, J., Piliszek, R., & Cankar, M.
- Affiliations
- Tecnalia (ES)
- 7bulls. com, Warsaw, Poland
- XLAB (Slovenia) (SI)
- Venue
- IEEE Software
- Published
- 2023-01
- Volume
- 40
- Issue
- 1
- Pages
- 56-62
- ISSN
- 0740-7459 (ISSN-L)
- 1937-4194
- OpenAlex
- W4312191397
- Cited by
- 30
- References
- 9
- Citations by year
- 2026: 4 · 2025: 8 · 2024: 9 · 2023: 8
- FWCI
- 6.44
- Type
- journal article
- Language
- en
- Open access
- hybrid
- doi.org
- Locations
- IEEE Software (publishedVersion, cc-by)
- TECNALIA Publications (Fundación TECNALIA Research & Innovation) (submittedVersion, public-domain)
- Zenodo (CERN European Organization for Nuclear Research) (cc-by)
- Funders
- Horizon 2020 research and innovation Program (101000162)
- Topics
- Physical Sciences › Computer Science › Information Systems › Software Engineering Techniques and Practices
- Physical Sciences › Computer Science › Computer Networks and Communications › Software System Performance and Reliability
- Physical Sciences › Computer Science › Hardware and Architecture › Security and Verification in Computing
- Keywords
- infrastructure as code, DevSecOps, reference framework
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: Embracing IaC Through the DevSecOps Philosophy: Concepts, Challenges, and a Reference Framework. https://app.cochat.ai/papers/10.1109/ms.2022.3212194
- The paper
- Alonso, J., Piliszek, R., & Cankar, M. (2023). Embracing IaC Through the DevSecOps Philosophy: Concepts, Challenges, and a Reference Framework. IEEE Software. https://doi.org/10.1109/ms.2022.3212194
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.