Vis enkel innførsel

dc.contributor.authorRamaj, Xhesika
dc.contributor.authorSanchez Gordon, Mary Luz
dc.contributor.authorGkioulos, Vasileios
dc.contributor.authorChockalingam, Sabarathinam
dc.contributor.authorColomo-Palacios, Ricardo
dc.date.accessioned2022-12-05T09:28:55Z
dc.date.available2022-12-05T09:28:55Z
dc.date.created2022-11-14T21:12:10Z
dc.date.issued2022
dc.identifier.citationElectronics. 2022, 11 (22), 1-19.en_US
dc.identifier.issn2079-9292
dc.identifier.urihttps://hdl.handle.net/11250/3035797
dc.description.abstractThe software industry has witnessed a growing interest in DevSecOps due to the premises of integrating security in the software development lifecycle. However, security compliance cannot be disregarded, given the importance of adherence to regulations, laws, industry standards, and frameworks. This study aims to provide an overview of compliance aspects in the context of DevSecOps and explore how compliance is ensured. Furthermore, this study reveals the trends of compliance according to the extant literature and identifies potential directions for further research in this context. Therefore, we carried out a systematic literature review on the integration of compliance aspects in DevSecOps, which rigorously followed the guidelines proposed by Kitchenham and Charters. We found 934 articles related to the topic by searching five bibliographic databases (163) and Google Scholar (771). Through a rigorous selection process, we selected 15 papers as primary studies. Then, we identified the compliance aspects of DevSecOps and grouped them into three main categories: compliance initiation, compliance management, and compliance technicalities. We observed a low number of studies; therefore, we encourage further efforts into the exploration of compliance aspects, their automated integration, and the development of metrics to evaluate such a process in the context of DevSecOps.en_US
dc.description.abstractHolding on to Compliance While Adopting DevSecOps: An SLRen_US
dc.language.isoengen_US
dc.rightsNavngivelse 4.0 Internasjonal*
dc.rights.urihttp://creativecommons.org/licenses/by/4.0/deed.no*
dc.subjectComplianceen_US
dc.subjectComplianceen_US
dc.subjectDatasikkerheten_US
dc.subjectSecurityen_US
dc.subjectDevOpsen_US
dc.subjectDevOpsen_US
dc.titleHolding on to Compliance While Adopting DevSecOps: An SLRen_US
dc.title.alternativeHolding on to Compliance While Adopting DevSecOps: An SLRen_US
dc.typePeer revieweden_US
dc.typeJournal articleen_US
dc.description.versionpublishedVersionen_US
dc.rights.holder© 2022 by the authors. Licensee MDPI, Basel, Switzerland.en_US
dc.subject.nsiVDP::Sikkerhet og sårbarhet: 424en_US
dc.subject.nsiVDP::Security and vulnerability: 424en_US
dc.source.pagenumber1-19en_US
dc.source.volume11en_US
dc.source.journalElectronicsen_US
dc.source.issue22en_US
dc.identifier.doi10.3390/electronics11223707
dc.identifier.cristin2073853
dc.relation.projectNorges forskningsråd: 309911en_US
cristin.ispublishedtrue
cristin.fulltextoriginal
cristin.qualitycode1


Tilhørende fil(er)

Thumbnail

Denne innførselen finnes i følgende samling(er)

Vis enkel innførsel

Navngivelse 4.0 Internasjonal
Med mindre annet er angitt, så er denne innførselen lisensiert som Navngivelse 4.0 Internasjonal