Saltar al contenido

DevSecOps: how to integrate security into DevOps processes

Media Interactiva returns to teleworking by the will of its team

Software applications are complex and can be vulnerable to a wide variety of security problems. Corporate culture often places security at the final stage of the software development lifecycle.
DevSecOps It focuses on move the safety to the leftThat is, instead of adopting an incident response system, everyone is responsible for safety right from the start, even in the planning stages.

DevSecOps combining security, development and operations to work together and achieve a common goal by making improvements to processes, tools and team collaborations.

What is SDLC?

The software development life cycle, known by the acronym SDLC or Systems development life cycle, is a process of creating or maintaining software systems and represents the different phases that generally include from preliminary analysis to testing and post-development evaluation of the software.

This process incorporates the models and methodologies that development teams use to develop software, methodologies that constitute the framework for planning and controlling the entire development process.

SDLC methodologies

Currently, there are two SDLC methodologies used by most software developers, the traditional methodology and agile methodology.

In the traditional development lifecycle, developers and their teams often schedule meetings with other teams involved in the SDLC process to detail functional and design requirements before implementation begins.

The design phase is followed by the coding phase. The testing phase takes place when the entire coding process is complete and the final product is presented to interested parties only after no problems are found in these tests.

One of the drawbacks of this traditional methodology is that the teams build the system «uniquely». In the event that a problem occurs during the testing phase, the worst thing about this scenario is that the entire module / development needs to be reversed to correct that problem.

Another disadvantage of traditional SDLC is that, in most cases, stakeholders do not know a priori what they really want to implement in the systemTherefore, the requirements model designed in the previous stages may not meet the actual features that need to be implemented.

Requests for changes by users or interested parties can be established after the final product has been presented and released to the market, and this change can cause various software compatibility and integrity issues.

With all these drawbacks, the need arises to establish a file iterative process where changes can be made more agile.

This is where the agile methodology for software development processes is created the customer is present at all stages of development.

This methodology facilitates interaction between all parties involved since the focus is on people and not on processes, allowing projects to be sized more efficiently while minimizing risks.

DevOps culture

However, the Agile methodology does not solve the communication problem between the different elements that make up the development process of a software system: the development team and the operational team.

The term DevOps is made up of the combination of the words «development» and «operations» and represents a cultural shift that bridges the gap between development and operations teams.

DevOps isn’t simply a different process or approach to development, it’s a file cultural change that implies a change of mentality, better collaboration and closer integration.

DevSecOps model

This model integrates security into the DevOps process by helping to prevent and address security risks as they appear in the development cycle.

This type of security built into DevOps aims at include a security culture and practices throughout the DevOps workflow resulting in a faster and safer product launch.

Incorporating security measures early in software development is an overall cost saving for any organization and security should focus shared responsibility among all members of the IT teams: security, development and operations.

In essence, DevSecOps has changed the very nature of how application security should be implemented and refers to integrated security and not your security perimeter.


Final Master’s project (note 8.77)