{"id":2241,"date":"2018-08-07T07:51:28","date_gmt":"2018-08-07T07:51:28","guid":{"rendered":"https:\/\/lcloud.pl\/?p=2241"},"modified":"2024-12-12T11:50:33","modified_gmt":"2024-12-12T10:50:33","slug":"devsecops-as-a-security-guard","status":"publish","type":"post","link":"https:\/\/lcloud.pl\/en\/devsecops-as-a-security-guard\/","title":{"rendered":"DevSecOps as a security guard"},"content":{"rendered":"
There are many approaches to managing IT projects. One of them is DevOps, also used in working with the AWS cloud. DevOps is, in short, a technique combining the development and exploitation of resources, which aims to provide the highest quality of cooperation between IT maintenance specialists and software development specialists. This methodology is based on the iterative work model, which is based on repeatability (iteration) and the fastest possible delivery of the solution (code) in the shortest possible time. The term DevOps was first used in 2009 by Patrick Debois during DevOpsDays in Ghent.<\/span><\/h5>\n

So what the DevSecOps is? <\/span><\/strong><\/p>\n

The safety element is now included in the already known DevOps methodology. Already at the stage of creating an IT solution, a security engineer is additionally included in the operation. A person or department dealing with security who, in consultation with developers and the IT maintenance department, consults the code that they co-create and implement. This allows you to eliminate gaps in the code, which are an easy morsel for hackers. To better illustrate the operation of the mechanism, the following diagram shows how important it is to integrate the DevOps approach with the appropriate level of security.<\/span><\/p>\n

\"\"<\/p>\n

Source: “DevSecOps: How to Seamlessly Integrate Security Into DevOps”, Gartner, 2016<\/span><\/p>\n

During the implementation of individual activities such as: planning, creation or implementation; the factor connecting the work of both departments is knowledge of secure coding (secure software engineering).<\/span><\/p>\n

DevOps is undeniably a methodology that has improved the work on implementing and adapting solutions. First of all, including large companies, where tens or hundreds of deployments are carried out in a short time. On the other hand, adding a security layer in DevSecOps allows for faster verification of created codes and repairing or complete elimination of created errors \/ security gaps.<\/span><\/p>\n

The DevSecOps methodology clearly puts emphasis on the security layer. That is why it has found its application in the financial and telecommunications industries, as well as in the development of advanced applications. During the preparation of the solution, protection and security should focus, for example, on permission control or protection against malware. Threat awareness allows for more effective work of programmers and problem-free maintenance of the solution.<\/span><\/h6>\n

In the further part of the article there are a few tips that will help in the application of the DevSecOps methodology.<\/span><\/p>\n

As part of automation, the DevOps methodology helps in deploying applications<\/strong>, scaling resources, ensuring high availability of applications and the environment, creating backup copies and implementing changes in security mechanisms. The first step should be to define the goal to be achieved.<\/strong> Then, you should indicate the security checkpoints that are necessary to maintain its highest level. As a result, a targeted variant of the use of automation can be created.<\/span><\/p>\n

Another activity is to understand the possibility of using codes under an open source licence.<\/strong> Solutions based on the cloud and DevOps methodologies allow for more efficient creation of new applications using ready-made code fragments. When using the source code used to create a new application, the question becomes whether it does not create a contextual gap. Thanks to the services prepared by AWS, you can solve these problems in an easy and effective way. In this case, the Amazon Inspector service will apply, which automatically evaluates applications for weak points or deviations.<\/span><\/p>\n

Important in the DevSecOps methodology is the selection of appropriate SAST (Source Application Security Testing) tools.<\/strong> At the beginning, it is worth considering the inclusion of capture rules such as errors in SQL. At the moment when people working with the code see how the tool will allow them to catch security gaps during work – they will be more willing to use it.<\/span><\/p>\n

Hazard modeling and risk assessment are also important.<\/strong> They are not the simplest activities. That is why it is worth paying attention to them before we start using the DevSecOps methodology. Each risk assessment method includes common elements. These include: identifying threats, assessing the probability of potential threats and losses they may bring. Thanks to practice connected with risk assessment and models of threats, people involved in security can get a better idea of, among others, about attacks and their types, confidential data and their control mechanisms etc.<\/span><\/p>\n

More tips on good practices on the use of the DevSecOps methodology can be found in the presentation available on SlideShare.<\/span><\/p>\n