Self-Service Cybersecurity Monitoring as Enabler for DevSecOps
Open accessThe DOI matches its Crossref record; 7 of the 7 references it cites were found in a registry or an index.
Abstract
Current IoT systems are highly distributed systems that integrate cloud, edge, and fog computing approaches depending on where intelligence and processing capabilities are allocated. This distribution and heterogeneity make development and deployment pipelines very complex and fragmented with multiple delivery endpoints above hardware. This fact prevents rapid development and makes the operation and monitoring of production systems a difficult and tedious task, including cybersecurity event monitoring. The DevSecOps can be defined as a cultural approach to improve and accelerate the delivery of business value by making dev/sec/ops teams' collaboration effective. This paper focuses on self-service cybersecurity monitoring as an enabler to introduce security practices in a DevOps environment. To that end, we have defined and formalized an activity that supports `Fast and Continuous Feedback from Ops to Dev' by providing a flexible monitoring infrastructure so that teams can configure their monitoring and alerting services according to their criteria (you build, you run, and now you monitor) to obtain fast and continuous feedback from the operation and thus, better anticipate problems when a production deployment is performed. This activity has been formalized using the Software & Systems Process Engineering Metamodel by OMG and its instantiation is described through a case study that shows the versioned and repeatable configuration of a cybersecurity monitoring infrastructure (Monitoring as Code) through virtualization and containerization technology. This self-service monitoring/alerting allows breaking silos between dev, ops, and sec teams by opening access to key security metrics, which enables a sharing culture and continuous improvement.
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
Edge computing: Vision and challenges
Shi, W., Cao, J., Zhang, Q., Li, Y., & Xu, L. (2016) · IEEE Internet of Things Journal · doi:10.1109/jiot.2016.2579198 · Cited by 8,733
Guidelines for conducting and reporting case study research in software engineering
Runeson, P., & Höst, M. (2009) · Empirical Software Engineering · doi:10.1007/s10664-008-9102-8 · Cited by 3,862 · cited 1×
“That is, they are, in general terms, very difficult to be objectively judged [36].”
BackgroundFog Computing: Platform and Applications
Yi, S., Hao, Z., Qin, Z., & Li, Q. (2015) · 2015 Third IEEE Workshop on Hot Topics in Web Systems and Technologies (HotWeb) · doi:10.1109/hotweb.2015.22 · Cited by 829 · cited 1×
“Nowadays most authors accept that fog/edge computing features should also be included in the definition of the new IoT architectures and integrated with cloud-native architecture [20][21][22].”
BackgroundIFCIoT: Integrated Fog Cloud IoT: A novel architectural paradigm for the future Internet of Things
Munir, A., Kansakar, P., & Khan, S. U. (2017) · IEEE Consumer Electronics Magazine · doi:10.1109/mce.2017.2684981 · Cited by 252
What 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
Carter, K. (2017) · IEEE Software · doi:10.1109/ms.2017.3571578 · Cited by 42
Cited by
Preliminary Findings about DevSecOps from Grey Literature
Mao, R., Zhang, H., Dai, Q., Huang, H., Rong, G., Shen, H., Chen, L., & Lu, K. (2020) · 2020 IEEE 20th International Conference on Software Quality, Reliability and Security (QRS) · doi:10.1109/qrs51102.2020.00064 · Cited by 49
“Although DevSecOps has gained increasing attention in academia [12]–[14], like many other new topics (e.g., mi-croservices [15]) in SE, industry is actually leading the way.”
BackgroundBahaa, A., Abdelaziz, A., Sayed, A., Elfangary, L., & Fahmy, H. (2021) · Information · doi:10.3390/info12040154 · Cited by 48
“Jessica et al. [33] addressed the formalization of feedback processes from operations to IoT system development.”
BackgroundRevisit security in the era of DevOps: An evidence-based inquiry into DevSecOps industry
Zhou, X., Mao, R., Zhang, H., Dai, Q., Huang, H., Shen, H., Li, J., & Rong, G. (2023) · IET Software · doi:10.1049/sfw2.12132 · Cited by 23
Alghawli, A. S. A., & Radivilova, T. (2024) · Alexandria Engineering Journal · doi:10.1016/j.aej.2024.07.036 · Cited by 23
“These issues were partially resolved by the authors of [18], who developed a self-service approach to cybersecurity monitoring during software deployment and testing.”
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
- Diaz, J., Perez, J. E., Lopez-Pena, M. A., Mena, G. A., & Yague, A.
- Venue
- IEEE Access
- Published
- 2019
- Volume
- 7
- Pages
- 100283-100295
- ISSN
- 2169-3536 (ISSN-L)
- OpenAlex
- W2963834817
- Cited by
- 63
- References
- 7
- FWCI
- 9.68
- Type
- journal article
- Language
- en
- Open access
- gold
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: Self-Service Cybersecurity Monitoring as Enabler for DevSecOps. https://app.cochat.ai/papers/10.1109/access.2019.2930000
- The paper
- Diaz, J., Perez, J. E., Lopez-Pena, M. A., Mena, G. A., & Yague, A. (2019). Self-Service Cybersecurity Monitoring as Enabler for DevSecOps. IEEE Access. https://doi.org/10.1109/access.2019.2930000
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.