Home Content News Sysdig Announces Intent to Acquire Apolicy

Sysdig Announces Intent to Acquire Apolicy

0
Image Credit: Linux Insider
  • The Apolicy team, including the founders Maor Goldberg, CEO, Eran Leib, VP Product Management, and Shlomi Wexler, VP R&D will join the Sysdig team.
  • The Apolicy product offering will be incorporated as part of the Sysdig Secure DevOps Platform

Sysdig, Inc. has announced intent to acquire Apolicy to shift security further left and expand the Sysdig offering to include Infrastructure as code (IaC) security. Sysdig customers secure the DevOps cycle from build through production. It said that Apolicy complements these capabilities by strengthening cloud and Kubernetes security with compliance and governance enforcement via policy as code, auto-remediation of drift to close the loop from production to source, and faster issue resolution with risk-based prioritization.

The Apolicy team, including the founders Maor Goldberg, CEO, Eran Leib, VP Product Management, and Shlomi Wexler, VP R&D will join the Sysdig team. The Apolicy product offering will be incorporated as part of the Sysdig Secure DevOps Platform.

Modern apps are built as containerized microservices using a DevOps approach to accelerate delivery. Teams are adopting secure DevOps as they transform security processes to adapt. This includes cloud configuration risk management, scanning images at build time, detecting and responding to threats at runtime, and continuously validating compliance with regulatory standards.The trend of Infrastructure-as-Code (IaC) and GitOps continues to gain broad mindshare with cloud platform teams as a way to achieve complete operational control of infrastructure.

It added, “As teams codify infrastructure using IaC tools like Terraform, CloudFormation, etc., it can be easy to overlook security. Misconfigurations in the cloud are common, evident by many high profile cloud breaches. Adopting IaC principles for building infrastructure can improve reliability by improving consistency and reducing human error. Checking for security as configurations are defined ‘shifts security further left,’ allowing teams to identify and resolve issues before infrastructure is deployed.”

With IaC security, teams can consistently enforce compliance and governance by applying policies as code to validate both configuration files and production environments and ensure they are identical. When runtime deviations occur, they can be discovered and automatically remediated directly at the source to ensure they don’t happen again.

It said, “Enforce compliance and governance via policy as code from source to production: Apolicy provides the ability to apply consistent policies and best practices across multiple IaC, cloud and Kubernetes environments. Customers can now bridge the gap between developers, DevOps and security teams with a unified view of security requirements using policy as code. Automating compliance by enforcing OPA-based policies via Kubernetes admission controller puts the control back in the hands of the user.”

With the addition of Apolicy, customers can now detect runtime drift and instantly map it back to the IaC configuration (source) file. This increases developer productivity by auto-remediating the IaC configuration source with a simple pull-request and allows for enforcing policy consistently across teams.

It said that it can also fix issues faster with risk-based prioritization by onsolidating alerts by identifying the production instances that are affected by the IaC error and prioritizing IaC fixes based on application context, allows users to prioritize remediation efforts. Rich application context makes it easy to identify owners who can fix misconfigurations.

“Most breaches are caused by configuration errors. Our customers want a single platform that detects configuration errors pre-deployment and identifies drift in production,” said Suresh Vasudevan, Chief Executive Officer, Sysdig. “With Apolicy, only Sysdig delivers a secure DevOps workflow for infrastructure and workloads and automatically closes the loop from production to source by fixing issues identified at runtime.”

NO COMMENTS

LEAVE A REPLY

Please enter your comment!
Please enter your name here

Exit mobile version