The Seven Sins: Security Smells in Infrastructure as Code Scripts
The DOI matches its Crossref record; 5 of the 5 references it cites were found in a registry or an index.
Abstract
Practitioners use infrastructure as code (IaC) scripts to provision servers and development environments. While developing IaC scripts, practitioners may inadvertently introduce security smells. Security smells are recurring coding patterns that are indicative of security weakness and can potentially lead to security breaches. The goal of this paper is to help practitioners avoid insecure coding practices while developing infrastructure as code (IaC) scripts through an empirical study of security smells in IaC scripts. We apply qualitative analysis on 1,726 IaC scripts to identify seven security smells. Next, we implement and validate a static analysis tool called Security Linter for Infrastructure as Code scripts (SLIC) to identify the occurrence of each smell in 15,232 IaC scripts collected from 293 open source repositories. We identify 21,201 occurrences of security smells that include 1,326 occurrences of hard-coded passwords. We submitted bug reports for 1,000 randomly-selected security smell occurrences. We obtain 212 responses to these bug reports, of which 148 occurrences were accepted by the development teams to be fixed. We observe security smells can have a long lifetime, e.g., a hard-coded secret can persist for as long as 98 months, with a median lifetime of 20 months.
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
Experimentation in Software Engineering
Wohlin, C., Runeson, P., Höst, M., Ohlsson, M. C., Regnell, B., & Wesslén, A. (2012) · doi:10.1007/978-3-642-29044-2 · Cited by 4,460
The protection of information in computer systems
Saltzer, J. H., & Schroeder, M. D. (1975) · Proceedings of the IEEE · doi:10.1109/proc.1975.9939 · Cited by 2,126 · cited 1×
“Recommendations from Saltzer and Schroeder [52] may be helpful in this regard.”
BackgroundCurating GitHub for engineered software projects
Munaiah, N., Kroh, S., Cabrey, C., & Nagappan, M. (2017) · Empirical Software Engineering · doi:10.1007/s10664-017-9512-6 · Cited by 365 · cited 2×
“Munaiah et al. [42] used the threshold of at least two commits per month to determine which repositories have enough software development activity.”
BackgroundSubjective evaluation of software evolvability using code smells: An empirical study
Mäntylä, M. V., & Lassenius, C. (2007) · Empirical Software Engineering · doi:10.1007/s10664-006-9002-8 · Cited by 171 · cited 1×
“Possible explanations for disagreements can also be attributed to perception of practitioners: smells in code have subjective interpretation [48], and programmers do not uniformly agree with all smell occurrences [49], [50].”
BackgroundCrySL: An Extensible Approach to Validating the Correct Usage of Cryptographic APIs
Kruger, S., Spath, J., Ali, K., Bodden, E., & Mezini, M. (2021) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2019.2948910 · Cited by 112
Cited by
Ullah, S., Han, M., Pujar, S., Pearce, H., Coskun, A., & Stringhini, G. (2023) · arXiv · doi:10.48550/arxiv.2312.12575 · Cited by 132
Security Smells in Ansible and Chef Scripts: A Replication Study
Rahman, A., Rahman, M. R., Parnin, C., & Williams, L. (2021) · ACM Transactions on Software Engineering and Methodology · doi:10.1145/3408897 · Cited by 80
Self-citationAn Empirical Study of Code Smells in Transformer-based Code Generation Techniques
Siddiq, M. L., Majumder, S. H., Mim, M. R., Jajodia, S., & Santos, J. C. S. (2022) · 2022 IEEE 22nd International Working Conference on Source Code Analysis and Manipulation (SCAM) · doi:10.1109/scam55253.2022.00014 · Cited by 70
“They are code patterns frequently that may lead to security flaws [17], [18].”
BackgroundIntegrating Security with DevSecOps: Techniques and Challenges
Ahmed, Z., & Francis, S. C. (2019) · 2019 International Conference on Digitization (ICD) · doi:10.1109/icd47981.2019.9105789 · Cited by 44
“The authors in [6] applied the concept of DevSecOps methodology to develop infrastructure as code (IaC) when writing insecure scripts to create development environments.”
MethodAutomated infrastructure as code program testing
Sokolowski, D., Spielmann, D., & Salvaneschi, G. (2024) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2024.3393070 · Cited by 20
An empirical study of policy as code: adoption, purpose, and maintenance
Opdebeeck, R., Alfadel, M., Rahman, A., Kashiwa, Y., Ferreira, J. F., Kula, R. G., & De Roover, C. (2026) · Proceedings of the 23rd International Conference on Mining Software Repositories · doi:10.1145/3793302.3793355 · Cited by 5
“Numerous studies have also investigated security in IaC scripts, from taxonomies of security weaknesses for various IaC tools [55–57] to the identification of new types of weaknesses [31, 33, 64] and improvements to weakness detection techniques [43, 45, 66, 67].”
Self-citationSecuring 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
Metadata
- Authors
- Rahman, A., Parnin, C., & Williams, L.
- Venue
- 2019 IEEE/ACM 41st International Conference on Software Engineering (ICSE)
- Publisher
- IEEE
- Published
- 2019-05
- Pages
- 164-175
- OpenAlex
- W2955656327
- Cited by
- 228
- References
- 5
- FWCI
- 19.68
- Type
- conference paper
- Language
- en
- Open access
- closed
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
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.