{"id":4424,"date":"2021-09-29T06:44:00","date_gmt":"2021-09-29T06:44:00","guid":{"rendered":"https:\/\/wibmo.com\/devsecops-a-necessity-in-the-current-landscape\/"},"modified":"2024-08-07T09:30:05","modified_gmt":"2024-08-07T09:30:05","slug":"devsecops-a-necessity-in-the-current-landscape","status":"publish","type":"post","link":"https:\/\/wibmo.com\/blogs\/devsecops-a-necessity-in-the-current-landscape\/","title":{"rendered":"DevSecOps \u2014 A necessity in the current landscape"},"content":{"rendered":"\t\t
\n\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

Let\u2019s start with the basics here. Traditionally, we followed Software Development Life Cycle, in short SDLC, a structured approach to develop quality software that meets customer requirements. With a rapid evolution in lifestyle, we moved to the Agile method which is one of the variants of SDLC to develop software in an iterative and fast way. While the agile methodology aims to develop a software or a component of software quicker, there is a need to deploy that component at equal speed in production set up to make it available to the user community. This development process along with the deployment process is together referred to as DevOps. Essentially, DevOps refers to the continuous integration of a software component and its continuous deployment. Now, thinking of security from the early stage of the development cycle instead of retrospectively fitting at the end of the cycle, transcends DevOps to DevSecOps. Here, we are shifting Security at the early stage of the cycle, i.e., shifting to the left of the cycle, which is referred to as Shift Left.<\/p>\n

To establish an analogy, may not be exact but a crude analogy to understand better, let\u2019s look at some of the household work like cooking. I cook in my free time at home. After cooking, I request my wife to serve the food to family members. Here, the cooking process is Development, serving process is Operations, together with cooking and serving process is DevOps. Now, it\u2019s important to understand in this example what is DevSecOps. While cooking, I am concerned about the hygiene of the food from the beginning, else, retrospectively fitting hygiene is very difficult. Therefore, the cooking and serving process along with maintaining hygiene in the entire process is DevSecOps.<\/p>\n

In a rapidly moving world where technology is easing the way we do business and lead life, there is a rapid increase in threats to the technology landscape by fraudsters or individuals with malicious intent. Therefore, it\u2019s imperative that security is looked at from the very early stage of the development cycle and all possible threat vectors are identified and appropriate controls or safeguards are built into the software to protect the software and therefore protect its user community and ultimately customers. Let\u2019s look at some of the benefits of DevSecOps.<\/p>\n

Continuous integration (CI)<\/strong> \u2014 merges code changes to ensure the most recent version is available to developers.<\/p>\n

Continuous delivery and continuous deployment (CD)<\/strong> \u2014 automate the process of releasing updates to increase efficiency.<\/p>\n

Microservices \u2014 <\/strong>builds an application as a set of smaller services.<\/p>\n

Infrastructure as code (IaC) \u2014 <\/strong>designing, implementing, and managing app infrastructure needs through code.<\/strong><\/p>\n

Common weaknesses enumeration (CWE)<\/strong> \u2014 improves the quality of code and increases the level of security during the CI and CD phases.<\/p>\n

Threat modeling <\/strong>\u2014 implements security testing during the development pipeline to save time and cost in the future.<\/p>\n

Automated security testing<\/strong> \u2014 test for vulnerabilities in new builds on regular basis.<\/p>\n

Incident management<\/strong> \u2014 creates a standard framework for responding to security incidents.<\/p>\n

Fast delivery <\/strong>\u2014 achieve ensure fast delivery of application by embedding automated security controls and tests early in the development cycle.<\/p>\n

Enriched efficiency<\/strong> \u2014 higher efficiency by scanning code for vulnerabilities as it’s written.<\/p>\n

Automotive<\/strong>: reduce lengthy cycle times while still meeting software compliance standards.<\/p>\n

Digital Transformation<\/strong>: enable digital transformation efforts while maintaining the privacy and security of sensitive data per regulations such as GDPR.<\/p>\n

Code analysis<\/strong> \u2014 deliver code in small chunks so vulnerabilities can be identified quickly.<\/p>\n

Compliance monitoring<\/strong> \u2014 be ready for an audit at any time that means being in a constant state of compliance, including gathering evidence of GDPR compliance<\/a>, PCI compliance<\/a>, etc.<\/p>\n

Threat investigation<\/strong> \u2014 identify potential emerging threats with each code update and be able to respond quickly.<\/p>\n

Vulnerability assessment<\/strong> \u2014 identify new vulnerabilities with code analysis and accordingly analyze how quickly they are being responded to and patched.<\/p>\n

Security training<\/strong> \u2014 train software and IT engineers with guidelines for set routines.<\/p>\n

\n
\n
\"\"<\/picture><\/div>\n<\/div>\n
Source: https:\/\/accelera.com.au\/<\/a><\/figcaption>\n<\/figure>\n

To conclude, DevSecOps is a cultural shift which means security is a shared responsibility, and everyone participating in SDLC has to a play very vital role in building security into the DevOps workflow.<\/p>\n

Author:<\/strong><\/p>\n

Ravi Bhushan<\/a>, Head- GRC and Ritesh Prasad<\/a>, Manager DevOps+SRE<\/p>\n

Wibmo<\/a> A PayU\/Naspers FinTech Company<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t

\n\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t