Software secure building aspects in Computer Engineering

Abstract

Anapplication includes software and communications infrastructure. As for the latter there own solutions to focus on security, there to build secure software solutions. However, the construction of secure software remains a problem due to a strategy that proposes to incorporate security as an aspect to consider when it has implemented most or all of the functional requirements. The equal treatment of functional and security requirements is the starting point to ensure an improvement in software security. Incorporate security into every stage of Software Development Life Cycle (SDLC) is another criterion that contributes and leads to a conceptually Secure SDLC. To this we must add a special emphasis on including security from the elicitation of requirements. In all cases the security treatment should be approached with criteria to allow evidence to be used best practices for its construction and the best solutions to meet security requirements. This paper presents criteria used to build secure software, incorporating Security Patterns, since requirements elicitation phase.

A Preventive Secure Software Development Model for a Software Factory: A Case Study

“…According to Solinas et al [12], security for software should be no longer optional, but mandatory. In this regard, most studies focused on secure development aim to introduce checks and measurements in Software Development Life Cycle (SDLC).…”