CoChat

Software security in DevOps: synthesizing practitioners' perceptions and practices

Ur Rahman, Akond Ashfaque, Williams, Laurie · 2016 · Proceedings of the International Workshop on Continuous Software Evolution and Delivery

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

Crossref · 10.1145/2896941.2896946

Cites

15 of 15 references verified0 citation errors · 0 not checkable

Statistics

Recomputing p-values needs the paper’s full text.

Verification

Claims the paper makes

This paper’s full text isn’t openly available, so its claims and self-check weren’t run. The registry and citation checks still apply.

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?

Citations

Cites

Show all 15 references

Research works printed but not linked: 10

  1. 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
  2. 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
  3. 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
  4. 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
  5. 10.1109/mc.2008.478 · doi:10.1109/mc.2008.478
  6. 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
  7. 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
  8. 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
  9. 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
  10. 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

See all 97

Metadata

Authors
Ur Rahman, A. A., & Williams, L.
Affiliations
  • North Carolina State University, Raleigh, NC
  • North Carolina State University (US)
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.