Software security in DevOps: synthesizing practitioners' perceptions and practices
The DOI matches its Crossref record; 15 of the 17 references it cites were found in a registry or an index.
Abstract
In organizations that use DevOps practices, software changes can be deployed as fast as 500 times or more per day. Without adequate involvement of the security team, rapidly deployed software changes are more likely to contain vulnerabilities due to lack of adequate reviews. The goal of this paper is to aid software practitioners in integrating security and DevOps by summarizing experiences in utilizing security practices in a DevOps environment. We analyzed a selected set of Internet artifacts and surveyed representatives of nine organizations that are using DevOps to systematically explore experiences in utilizing security practices. We observe that the majority of the software practitioners have expressed the potential of common DevOps activities, such as automated monitoring, to improve the security of a system. Furthermore, organizations that integrate DevOps and security utilize additional security activities, such as security requirements analysis and performing security configurations. Additionally, these teams also have established collaboration between the security team and the development and operations teams.
Overview
Integrity signals
Registry
Cites
Statistics
Verification
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?
In the citing paper
“findings show that Sec teams actively collaborate with Dev and Ops teams in established DevOps organizations”
From Identifying the primary dimensions of DevSecOps: A multi-vocal literature review (2024) · cites this paper as Rahman and Williams, 2016
In the citing paper
“and a supervised collaboration among teams might help to improve the automated deployment for system's security.”
From Identifying the primary dimensions of DevSecOps: A multi-vocal literature review (2024) · cites this paper as Rahman and Williams, 2016
Citations
Cites
Threat Modeling: Designing for Security
Shostack, A. (2014) · Cited by 1,587
Software Security: Building Security In
McGraw, G. (2006) · 2006 17th International Symposium on Software Reliability Engineering · doi:10.1109/issre.2006.43 · Cited by 785
Crossing the chasm : marketing and selling technology products to mainstream customers
Moore, G. A. (1991) · HarperBusiness eBooks · Cited by 462
Development and Deployment at Facebook
Feitelson, D. G., Frachtenberg, E., & Beck, K. L. (2013) · IEEE Internet Computing · doi:10.1109/mic.2013.25 · Cited by 243
Potter, B., & McGraw, G. (2004) · IEEE Security & Privacy Magazine · doi:10.1109/msp.2004.84 · Cited by 233 · cited 1×
“• Performing Manual Security Tests : Performing manual security tests is the activity that aims to reduce software risk by applying two tasks: ensuring that the software’s functionality is properly implemented, and executing risk-based security testing via simulating an attacker [17].”
MethodDevOps: A Definition and Perceived Adoption Impediments
Smeds, J., Nybom, K., & Porres, I. (2015) · Lecture Notes in Business Information Processing · doi:10.1007/978-3-319-18612-2_14 · Cited by 158 · cited 3×
“Smeds et al. [21] defined DevOps as a collection of software engineering activities such as, continuous planning, and continuous deployment that are supported by cultural facilitators such as sharing of responsibility and goals, and technical facilitators such as automated build process, and…”
BackgroundInfluentialTowards Definitions for Release Engineering and DevOps
Dyck, A., Penners, R., & Lichter, H. (2015) · 2015 IEEE/ACM 3rd International Workshop on Release Engineering · doi:10.1109/releng.2015.10 · Cited by 154 · cited 2×
“According to Dyck et al. [2], DevOps is the software process that emphasizes collaboration within and between different teams involved in software development.”
MethodSystems and Software Engineering
Möller, D. P. F. (2016) · Computer communications and networks · doi:10.1007/978-3-319-25178-3_6 · Cited by 137
Practitioners' Perspectives on Security in Agile Development
Bartsch, S. (2011) · International Conference on Availability, Reliability and Security (ARES) · doi:10.1109/ares.2011.82 · Cited by 92 · cited 1×
“Bartsch [1] explored the perceptions of software security amongst Agile practitioners and observed the importance of appropriate involvement of customers, and continuous improvement, to implement software security amongst Agile practitioners.”
BackgroundSynthesizing Continuous Deployment Practices Used in Software Development
Rahman, A. A. U., Helms, E., Williams, L., & Parnin, C. (2015) · 2015 Agile Conference · doi:10.1109/agile.2015.12 · Cited by 75 · cited 2×
“[18] investigated the usage frequency of 11 software practices used amongst software companies that implement continuous deployment.”
MethodSelf-citation
Research works printed but not linked: 10
- Humble , J. , and Farley , D . 2011. Continuous Delivery , 1st Ed. Addison-Wesley , Boston, MA , 2011 Humble, J., and Farley, D. 2011. Continuous Delivery, 1st Ed. Addison-Wesley, Boston, MA, 2011
- Innovation . S. Regulatory Compliance Demystified: An Introduction to Compliance for Developers : 2006 . Available: https://msdn.microsoft.com/en-us/library/aa480484.aspx. Accessed: 2016-01-24 Innovation. S. Regulatory Compliance Demystified: An Introduction to Compliance for Developers: 2006. Available: https://msdn.microsoft.com/en-us/library/aa480484.aspx. Accessed: 2016-01-24
- Labs , P. , and Revolution , IT . 2015 State of DevOps Report | Puppet Labs : 2015 . Available: https://puppetlabs.com/sites/default/files/2015-state-of-devops-report.pdf. Accessed: 2016-01-24 Labs, P., and Revolution, IT. 2015 State of DevOps Report | Puppet Labs: 2015. Available: https://puppetlabs.com/sites/default/files/2015-state-of-devops-report.pdf. Accessed: 2016-01-24
- Likert , R. 1932 . A Technique for the Measurement of Attitudes , in Archives of Psychology , vol. 22 , no. 140, pages 5--55, June, 1932 Likert, R. 1932. A Technique for the Measurement of Attitudes, in Archives of Psychology, vol. 22, no. 140, pages 5--55, June, 1932
- 10.1109/mc.2008.478 · doi:10.1109/mc.2008.478
- McGraw , G. , Migues , S. , and West J . BSIMM 6: Building Security in Maturity Model : 2015 . https://www.bsimm.com/download/. Accessed : 2016-01-24 McGraw, G., Migues, S., and West J. BSIMM 6: Building Security in Maturity Model: 2015. https://www.bsimm.com/download/. Accessed: 2016-01-24
- Microsoft . Microsoft Secure Development Lifecycle Guidance : 2012 . https://www.microsoft.com/en-us/download/details.aspx?id=29884. Accessed : 2016-01-24 Microsoft. Microsoft Secure Development Lifecycle Guidance: 2012. https://www.microsoft.com/en-us/download/details.aspx?id=29884. Accessed: 2016-01-24
- Technologies , CA. DevOps: The Worst Kept Secret to Winning in the Application Economy : 2014 . http://www.ca.com/us/~/media/Files/whitepapers/devops-the-worst-kept-secret-to-winning-in-the-application-economy.pdf. Accessed : 2016-01-24 Technologies, CA. DevOps: The Worst Kept Secret to Winning in the Application Economy: 2014. http://www.ca.com/us/~/media/Files/whitepapers/devops-the-worst-kept-secret-to-winning-in-the-application-economy.pdf. Accessed: 2016-01-24
- Turnbull , J. DevOps & Security : 2012 . http://www.slideshare.net/jamtur01/security-loves-devops-devops-days-austin-2012. Accessed: 2016-01-24 Turnbull, J. DevOps & Security: 2012. http://www.slideshare.net/jamtur01/security-loves-devops-devops-days-austin-2012. Accessed: 2016-01-24
- Velasquez , N. , Kim , G. , Kersten , N. , and Humble , J . 2014 State of DevOps Report : 2014 . https://puppetlabs.com/sites/default/files/2014-state-of-devops-report.pdf. Accessed : 2016-01-24 Velasquez, N., Kim, G., Kersten, N., and Humble, J. 2014 State of DevOps Report: 2014. https://puppetlabs.com/sites/default/files/2014-state-of-devops-report.pdf. Accessed: 2016-01-24
Cited by
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
DevOps in practice: A multiple case study of five companies
Lwakatare, L. E., Kilamo, T., Karvonen, T., Sauvola, T., Heikkilä, V., Itkonen, J., Kuvaja, P., Mikkonen, T., Oivo, M., & Lassenius, C. (2019) · Information and Software Technology · doi:10.1016/j.infsof.2019.06.010 · Cited by 195
“, continuous monitoring through log aggregation and monitoring tools has become an integral part of the deployment pipeline, and are made accessible to developers [23] [16] [37] [44] [28].”
BackgroundA 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
Self-citationShamim, S. I., Bhuiyan, F. A., & Rahman, A. (2020) · IEEE Secure Development Conference (SecDev) · doi:10.1109/secdev45635.2020.00025 · Cited by 114
“Previously, researchers have systematically studied Internet artifacts to identify challenges in microservices development, identify practices used in continuous deployment [9], identify security practices used in organization who have adopted DevOps [8], and software testing [14].”
MethodInfluentialSecDevOps: Is It a Marketing Buzzword? - Mapping Research on Security in DevOps
Mohan, V., & Othmane, L. B. (2016) · 2016 11th International Conference on Availability, Reliability and Security (ARES) · doi:10.1109/ares.2016.92 · Cited by 112
“In fact, CA Technologies expects that 1254 out of 1425 organizations will adopt DevOps in the next five years [2].”
BackgroundInfluential
Metadata
- Authors
- Ur Rahman, A. A., & Williams, L.
- Affiliations
- North Carolina State University, Raleigh, NC
- North Carolina State University (US)
- ORCID
- Williams, Laurie
- Venue
- Proceedings of the International Workshop on Continuous Software Evolution and Delivery
- Publisher
- ACM
- Published
- 2016-05-14
- Pages
- 70-76
- OpenAlex
- W2503060256
- Cited by
- 86
- References
- 17
- Citations by year
- 2026: 8 · 2025: 6 · 2024: 3 · 2023: 7 · 2022: 8 · 2021: 19 · 2020: 18 · 2019: 7 · 2018: 6 · 2017: 2 · 2016: 2
- FWCI
- 4.81
- Type
- conference paper
- Language
- en
- Open access
- closed
- Funders
- National Security Agency (2014-1267)
- 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
- software security, DevOps, security practices, security integration, automated monitoring, security requirements analysis, security configuration, software vulnerabilities, continuous deployment
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: Software security in DevOps: synthesizing practitioners' perceptions and practices. https://app.cochat.ai/papers/10.1145/2896941.2896946
- The paper
- Ur Rahman, A. A., & Williams, L. (2016). Software security in DevOps: synthesizing practitioners' perceptions and practices. Proceedings of the International Workshop on Continuous Software Evolution and Delivery. https://doi.org/10.1145/2896941.2896946
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.