BP: Security Concerns and Best Practices for Automation of Software Deployment Processes: An Industrial Case Study
The DOI matches its Crossref record; 6 of the 6 references it cites were found in a registry or an index.
Abstract
SecDevOps is a paradigm for integrating the software development and operation processes considering security and compliance requirements. Organizations are reluctant to transform their development and operation processes to SecDevOps because of the expectation of incompatibility between security and DevOps. This paper reports about a study performed at IBM on transformation of five Business Intelligence (BI) projects to SecDevOps. The study revealed that main security concerns for the automation of the deployment process are: separation of roles, enforcement of access controls, manual security tests, audit, security guidelines, management of security issues, and participation of the security team. The major recommended best practices for a transformation of current processes to SecDevOps are: good documentation and logging, strong collaboration and communication, automation of the processes, and enforcement of separation of roles. Based on the empirical results, we conclude that separation of roles is the main aspect to be considered when planning to automate deployment processes. The results of the study are being used by IBM BI Unit and may be used by other organizations when planning to migrate to SecDevOps, especially for BI projects.
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
Microservices Architecture Enables DevOps: Migration to a Cloud-Native Architecture
Balalaie, A., Heydarnoori, A., & Jamshidi, P. (2016) · IEEE Software · doi:10.1109/ms.2016.64 · Cited by 735 · cited 2×
“[6] reported on their experiences and lessons learned from adopting DevOps and how this facilitated a smooth migration of security issues.”
BackgroundWhat is DevOps?: A Systematic Mapping Study on Definitions and Practices
Jabbari, R., bin Ali, N., Petersen, K., & Tanveer, B. (2016) · Proceedings of the Scientific Workshop Proceedings of XP2016 · doi:10.1145/2962695.2962707 · Cited by 230
SecDevOps: 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
Self-citationSoftware security in DevOps: synthesizing practitioners' perceptions and practices
Ur Rahman, A. A., & Williams, L. (2016) · Proceedings of the International Workshop on Continuous Software Evolution and Delivery · doi:10.1145/2896941.2896946 · Cited by 86 · cited 3×
“Rahman and Williams [3] analyzed a selected set of Internet artifacts and surveyed representatives of nine organizations that are using DevOps.”
BackgroundMethodInfluentialCarter, K. (2017) · IEEE Software · doi:10.1109/ms.2017.3571578 · Cited by 42
Cited by
Kumar, R., & Goyal, R. (2020) · Computers & Security · doi:10.1016/j.cose.2020.101967 · Cited by 97
Prioritization based taxonomy of DevOps security challenges using PROMETHEE
Rafi, S., Yu, W., Akbar, M. A., Alsanad, A., & Gumaei, A. (2020) · IEEE Access · doi:10.1109/access.2020.2998819 · Cited by 50
Prates, L., & Pereira, R. (2025) · International Journal of Information Security · doi:10.1007/s10207-024-00914-z · Cited by 49
“Integrating security checks into the pipeline results in rapid and reliable software releases while also ensuring that security measures are consistently applied, helping to identify and mitigate security vulnerabilities at every stage of development and deployment [33] [71].”
Holding on to Compliance While Adopting DevSecOps: An SLR
Ramaj, X., Sánchez-Gordón, M., Gkioulos, V., Chockalingam, S., & Colomo-Palacios, R. (2022) · Electronics · doi:10.3390/electronics11223707 · Cited by 33
Caniglia, A., Dentamaro, V., Galantucci, S., & Impedovo, D. (2025) · Information and Software Technology · doi:10.1016/j.infsof.2024.107605 · Cited by 18
Metadata
- Authors
- Mohan, V., ben Othmane, L., & Kres, A.
- Venue
- 2018 IEEE Cybersecurity Development (SecDev)
- Publisher
- IEEE
- Published
- 2018-09
- Pages
- 21-28
- OpenAlex
- W2901946639
- Cited by
- 33
- References
- 6
- FWCI
- 2.99
- 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
How to cite
Cite CoChat for the checks on this page, and the paper for its own findings.
- This page
- CoChat. (2026). Citation check: BP: Security Concerns and Best Practices for Automation of Software Deployment Processes: An Industrial Case Study. https://app.cochat.ai/papers/10.1109/secdev.2018.00011
- The paper
- Mohan, V., ben Othmane, L., & Kres, A. (2018). BP: Security Concerns and Best Practices for Automation of Software Deployment Processes: An Industrial Case Study. 2018 IEEE Cybersecurity Development (SecDev). https://doi.org/10.1109/secdev.2018.00011
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.