Security in agile software development: A practitioner survey

Rindell, Kalle; Ruohonen, Jukka; Holvitie, Johannes; Hyrynsalmi, Sami; Leppänen, Ville

doi:10.1016/j.infsof.2020.106488

Cited by 34 publications

(28 citation statements)

References 29 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…It has been discovered that addressing security concerns during the initial phase costs up to 100x times less than addressing flaws in the released software. e article also defines each person's role, from the top of management down the hierarchy, in promoting the model and establishing a sustainable application [27][28][29][30]. Mathematical Problems in Engineering…”

Section: Discussionmentioning

confidence: 99%

Cost Benefit Analysis of Incorporating Security and Evaluation of Its Effects on Various Phases of Agile Software Development

Kumar¹,

Kaur²,

Jolly³

et al. 2021

Mathematical Problems in Engineering

View full text Add to dashboard Cite

This article addresses the costs and benefits of integrating security into the development of applications and gives formulas for calculating security costs and benefits. The lack of safe application might lead to safety issues. Increasingly, there are accidents recorded that expose security flaws in many major software systems. It results in significant losses for consumer companies. While software businesses are working to produce secure software, the utility of secure software is quite limited. In contrast to the traditional manufacturers of commodities, for example, automakers, software developers have no legal responsibility if their products include flaws. The market reacts adversely to software manufacturers with serious vulnerabilities in their products. This is because of the loss of credibility, cost of patches, and so on. The study shows that the market is ready to penalize the supplier for insecurity and therefore offers the chance to deliver safer technologies. To improve cost/efficiency, the vulnerabilities are connected by accessible fixes. Significant savings are gained when security shortcomings are corrected during designing requirements instead of fixing security failures after deploying software. For suppliers, updates are more expensive to produce and publish. In addition, development costs can be reduced by plugging security issues in the early stages of development.

show abstract

Section: Discussionmentioning

confidence: 99%

Cost Benefit Analysis of Incorporating Security and Evaluation of Its Effects on Various Phases of Agile Software Development

Kumar¹,

Kaur²,

Jolly³

et al. 2021

Mathematical Problems in Engineering

View full text Add to dashboard Cite

show abstract

“…Various researchers [10,26,52] and the relevance of including SRE in the SSD process have stressed GSD industry practitioners. These operations yield outcomes that are inextricably tied to the software's economic value [53].…”

Section: Findings Of Empirical Studymentioning

confidence: 99%

Evaluation of Requirement Engineering Best Practices for Secure Software Development in GSD: An ISM Analysis

Khan

Akbar

Rafi

et al. 2023

Preprint

View full text Add to dashboard Cite

Technological advancement makes the world a global village. The immense use of software systems has modernized human society in every aspect. Thus, the security parameter is an important element that needs to be considered while developing software systems. Considering the significance of software security, it is important to consider the security practices from the early phase of the software development life cycle (SDLC), i.e., requirements engineering (RE). Hence, this study aims to identify and categorize RE practices important to apply for secure software development (SSD) in a geographically distributed development environment. To study the RE practices concerning SSD, we conducted a questionnaire survey with industrial experts in the global software development (GSD) context. Furthermore, the interpretive structure modeling (ISM) approach was applied to evaluate the relationship between the RE security practice core categories. This paper identifies 70 practices and classifies them into 11 fundamental dimensions (categories) to assist GSD organizations in specifying the requirements for SSD. The ISM results show the “Awareness of Secure Requirement Engineering (SRE)” category has the most decisive influence on the other ten core categories of the identified RE security practices. With the help of empirical evidence and the ISM approach, this work attempts to identify potential security practices and to give a set of secure RE practices that can be used to improve the security of the software development process.

show abstract

“…For software security problems, Software Security Specifications and Design: How Software Engineers and Practitioners Are Mixing Things up [1]. Understanding Software Security from Design to Deployment [2].…”

Section: Related Workmentioning

confidence: 99%

“…The strong inexpensive business situation grades in small-medium sized industry pointing for plans to initiative rate decrease and rise the security for the product [1]. Though the goals of the establishments struggle for, small-medium sized industry necessity is to achieve these constant development aims with restricted incomes.…”

Section: Introductionmentioning

confidence: 99%

Critical Success Factor Estimation for Software Security in Small and Medium Scale Industry Using AHP and TOPSIS Approach

Kavyashree¹,

Chandramouli²,

Lokesh³

2021

Atlantis Highlights in Computer Sciences

View full text Add to dashboard Cite

In small and medium scale software industry, software security success factor is trivial process. Six-sigma and fuzzy logic methodology address software security problems effectively in the state of work. The research work chosen Fuzzy Technique for Order of Preference by Similarity to Ideal Solution (TOPSIS) and Analytical Hierarchical Process (AHP) method to identify critical success factor estimation. The experimental case study, shows the Euclidean distance amongst the nine components of IOS mobile application. The results discuss on the goal alternate and the best/worst alternate Ranking of the factors to verify mobile IOS application software security. For attaining supportable software security, it is authoritative to safeguard that best practices are conscripted in considering the security valuation at the actual commencement of the software development life cycle.

show abstract

Security in agile software development: A practitioner survey

Cited by 34 publications

References 29 publications

Cost Benefit Analysis of Incorporating Security and Evaluation of Its Effects on Various Phases of Agile Software Development

Cost Benefit Analysis of Incorporating Security and Evaluation of Its Effects on Various Phases of Agile Software Development

Evaluation of Requirement Engineering Best Practices for Secure Software Development in GSD: An ISM Analysis

Critical Success Factor Estimation for Software Security in Small and Medium Scale Industry Using AHP and TOPSIS Approach

Contact Info

Product

Resources

About