Zscaler 블로그

Zscaler 블로그의 최신 업데이트를 이메일로 받아보세요

Products & Solutions

The Role of Security in DevOps Architecture

image
>The Role of Security in DevOps Architecture

With the increase of digital business powered by cloud, DevOps has become an infinite backbone behind the software delivery ecosystem. DevOps empowers development teams to deliver applications faster by reducing the time to deploy functionalities and features. The core of DevOps, “automation” for agility and “integration” of various sets of tools for visibility, have reduced the complexity and gaps between traditional development and operations teams. The outcome? Substantial productivity boosts in every development ecosystem. 

As DevOps enables speed, agility, and cross-functional collaboration, many organizations run the risk out outpacing “security”, creating a huge remediation backlog for engineering and Infrastructure teams. Fortunately, modern (CI/CD) tooling capabilities allow security checks to be baked into the DevOps process at almost any stage of the development lifecycle (Code|Check-in|Build|Test|Deploy|Monitor).

Cloud-Native Application Security platforms (CNAPP) allows security teams to implement gates and guardrails that can be integrated into any DevOps pipeline, enabling visibility for every software, DevOps, and security engineer. Such a security-integrated DevOps pipeline is called a DevSecOps pipeline.

 

The DevSecOps pipeline 

The security team can integrate security gates at various stages of the CI and CD process, as described below: 

Source Code & Integrated Development Environment (IDE): Code is born in a developer's IDE. Integrating IaC scanning abilities with an IDE could enable visibility for developers and guide them to follow security coding standards before even the code is checked into a source code system.

The second check can be enabled during the source code check-in process, where every PR and MR raised by the developers is scanned for vulnerabilities and sensitive information leakage using SAST and OSS tools, which gives the approvers ability to sign off on clean and compliant code into the pipeline.

Build and Test - CI Pipeline:  Once the code is approved and merged, the CI workflow is initiated. In this process, security teams can scan the software for OSS (Open Source Software) vulnerabilities and their licenses, along with functional and unit testing. These security gates help to protect the intellectual property rights of the product and prevent zero-day vulnerabilities. This process reduces the review and approval cycles for engineering teams. 

Artifacts:  The CI process ends with clean and compliant code being pushed into the central registry. Security teams can enable vulnerability scanning, audit, and access scanning on this central registry to continuously monitor zero-day and unauthorized access and for rogue or unsigned packages being introduced. 

Deployment: Certified and signed images from the registry are deployed into various environments for functional, regression, and stress testing. In this cycle, security teams can simulate real-world attacker scenarios on the application “Grey-box testing” and project the exploitable risks present in the application.

Monitor: Tested, scanned, hardened network, infrastructure, and applications are now deployed. As SRE teams monitor and scale the application, infrastructure, and network security teams continuously monitor and protect the runtime behavior of the application, API, containers, cloud, network and infrastructure using tools like CNAPP. Security teams continuously collect, process, and correlate runtime signals across various building blocks (Network, Infrastructure, and cloud) of an application. They develop and deploy the right set of security guardrails to prevent any security events thus guarding the customer-centric application and data.

Conclusion

Security integrated CI/CD workflows enable and guide developers with organization-defined security best practices, thus reducing security backlog. DevSecOps workflows improve proactive security without compromising on agility. Ensuring that cloud applications are “born secure” is a must-have for growing digital businesses and enterprises. 

DevOps poses a variety of organizational and technical security challenges for security teams. Security teams must find ways to safeguard DevOps environments without impairing the pace of development. CNAPP solutions such as Zscaler’s Posture Control empower security and DevOps teams to enforce consistent best practices for securing DevOps environments. Learn more about Posture Control and its capabilities.

form submtited
읽어주셔서 감사합니다

면책 조항: 이 블로그 게시물은 정보 제공만을 목적으로 Zscaler에서 작성하였으며, 정확성, 완전성 또는 신뢰성에 대한 어떠한 보증도 없이 "있는 그대로" 제공됩니다. Zscaler는 제공된 정보를 기반으로 수행된 조치나 오류 또는 누락에 대해 어떠한 책임도 지지 않습니다. 이 블로그 게시물에 링크된 제3자 웹사이트나 리소스는 편의를 위해서만 제공되며, Zscaler는 해당 웹사이트의 콘텐츠나 관행에 대해 책임을 지지 않습니다. 모든 콘텐츠는 예고 없이 변경될 수 있습니다. 이 블로그에 접속함으로써 귀하는 본 약관에 동의하며 귀하의 필요에 따라 정보를 확인하고 사용할 전적인 책임이 귀하에게 있음을 인정합니다.

Zscaler 블로그의 최신 업데이트를 이메일로 받아보세요

양식을 제출함으로써 귀하는 당사의 개인정보 보호정책에 동의하는 것입니다.