Reframing Security in Contemporary Software Development Life Cycle

Frijns, Pieter; Bierwolf, Robert; Zijderhand, Tom

doi:10.1109/itmc.2018.8691277

Cited by 10 publications

(7 citation statements)

References 9 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…In contrast to existing approaches, the solution proposed in this paper uses potential vulnerabilities (gathered from automation software, such as vulnerability scanners) and utilizes neural network algorithms and the dataset processed using a Natural Language Processing (NLP) approach (where typically NNs yield the best results [23]) to classify the vulnerabilities as confirmed/unconfirmed. As an input for the introduced algorithm, any pre-compiled list of software vulnerabilities (with no limitation to a specific scanning solution) can be used.…”

Section: Discussionmentioning

confidence: 99%

“…• Continuous integration and continuous deployment: tools that store the set of created pipelines in the form of a set of instructions that will be executed (to build ready FIGURE 1. SDLC adoption in [23] to use applications) and when it should be executed (the scheduled event or triggered by a predefined action). • Testing: for bug and problem-free applications, it should only be allowed to be deployed in the production environment where the end customers are dealing with the delivered software.…”

Section: A Software Development Life Cycle In Devopsmentioning

confidence: 99%

See 1 more Smart Citation

Context-Aware Software Vulnerability Classification Using Machine Learning

Siewruk

Mazurczyk

2021

IEEE Access

View full text Add to dashboard Cite

Section: Discussionmentioning

confidence: 99%

Section: A Software Development Life Cycle In Devopsmentioning

confidence: 99%

Context-Aware Software Vulnerability Classification Using Machine Learning

Siewruk

Mazurczyk

2021

IEEE Access

View full text Add to dashboard Cite

“…Lack of automated testing tools [5], [3], [19], [26], [29] CH2 Security manual testing and performance configuration [2], [6], [14], [16], [80] CH3…”

Section: Ch1mentioning

confidence: 99%

Prioritization Based Taxonomy of DevOps Security Challenges Using PROMETHEE

Rafi

Akbar

et al. 2020

IEEE Access

View full text Add to dashboard Cite

DevOps is a combination of collaborative and multidisciplinary efforts of an organization to control continuous delivery and updates of new software while guaranteeing their reliability and correctness. In the software industry, the implementation of DevOps (development and operations units) faces many challenges that are specifically associated with the security. This study aims to develop a prioritization based taxonomy of DevOps security challenges using PROMETHEE-II approach. The total of eighteen DevOps security challenges were extracted from the literature and were further evaluated with experts using questionnaire survey study. In the third stage, multi criteria decision making PROMETHEE-II approach was used to prioritize and develop the taxonomy of identified factors and their categories. The implications of PROMETHEE-II approach are novel in this research domain as it has been used successfully in various other domains e.g. medical, banking, internet techniques and management etc. The contribution of this study is not limited to develop the taxonomy based structure of DevOps security challenges, but also the proper prioritization of these challenges by introducing PROMETHEE-II approach in the research field of DevOps. The study results will assist the practitioners to remove the uncertainty and vagueness in the opinion of DevOps experts to secure DevOps implementation for better and continuous software development process.

show abstract

“…Organizations have massively embraced DevOps principles due to current customers' demand for highly available, continuous-release, and high-value applications that are useable anytime, anywhere at any platform [20]. Leading ventures such as Google, Netflix, Amazon, LinkedIn, Spotify, Flicker, and Etsy have adopted DevOps practices to release software with a higher pace and better quality [21][22][23][24]. The main objective of the IT organization is always to bring new and superior quality applications with more features to the user, be its an internal consumer of the organization or a consumer in the market [25].…”

Section: Introductionmentioning

confidence: 99%