Towards the Integration of Security Practices in the Software Implementation Process of ISO/IEC 29110: A Mapping

Analysis of Strategies for the Integration of Security Practices in Agile Software Development: A Sustainable SME Approach

“…Our analysis reveals that some strategies have received more attention than others in the 14 reviewed studies. For example, a total of 7 articles address security throughout the Software Development Life Cycle (SDLC) via security practices [75], [76], [7], [73], [77], [78], [79]. This represents 10.1% of the total reviewed articles, indicating a relatively low proportion of studies focusing on addressing security comprehensively in all stages of the software development lifecycle.…”

“…Another benefit is the guarantee to reach a high level of quality and functionality of the software maximizing the added value to the software by the benefits of developing a robust software. Development Life Cycle (SDLC) through security practices [75], [76], [7], [73], [77], [78], [79]. This represents 10.1% of the total reviewed articles, indicating that there is a relatively low proportion of studies that focus on addressing security comprehensively in all stages of the software development cycle.…”

“…This methodology adopts aspects of software architecture, encourages the support of specialized tools, and can improve the ability of other SSDL methods to address cryptographic issues. 64 Towards the integration of security practices in the software implementation process of ISO/IEC 29110: A mapping [79] The objective of this study is to help raise awareness of the software security process among small business professionals and to assist in the integration of these practices with the ISO/IEC 29110 software implementation process, resulting in an extension of the latter with additional activities identified from industry best practices. 65 TrustSECO: A Distributed Infrastructure for Providing Trust in the Software Ecosystem [128] The purpose of this article is to address trust in the global software ecosystem (SECO) and its implications for society.…”

A Maturity Model for Secure Software Design: A Multivocal Study

“…We have distributed and used these practices to build our assessment framework, which is presented in the next section. [3], [15], [16], [46], [47], [48], [49], [50], [51], [52], [53], [54], [55], [56], [57], [58], [59], [60], [42], [61], [62], [63], [64], [ Use a scheme to classify applications based on data confidentiality 3 [42], [60], [65] 6 Perform design and architecture security risk analysis 15 [58], [61], [65] , [66], [67], [68], [69], [70], [50], [71], [72], [73], [74], [75] 7…”

“…[56], [54], [67], [74], [76] 8 Security specification review 2 [67], [71] 9 Minimize software attack surface or access points 8 [3], [15], [45], [49], [57], [70], [75] 10 Identify and segregate trusted entities from untrusted entities 8 [3], [46], [55], [58], [67], [70], [71], [77] 11 18 Design security features using diagrams 2 [67], [68] 19 Consider security principles in design 14 [5], [16], [45], [49], [55], [56], [57], [61], [62], [65], [70], [72], [74], [79] 20 Minimize or eliminate unnecessary functionality 3 [67], [71], [ [16], [42], [49], [56], [64], [73], [77], [80]…”