Today Red Hat announced a definitive agreement to acquire StackRox. This is an exciting milestone for StackRox and a tremendous validation of our innovative approach to container and Kubernetes security. It combines the industry’s first Kubernetes-native security platform with Red Hat’s leading enterprise Kubernetes platform, OpenShift – helping businesses further accelerate their digital transformation initiatives by more securely building, deploying and running their cloud-native applications anywhere. StackRox will continue to support multiple Kubernetes offerings such as Amazon EKS, Azure AKS, and Google GKE. You can gain additional insights from Ashesh Badani, Senior Vice President of Cloud Platforms at Red Hat, in this blog post.

StackRox was founded over six years ago with an initial focus on runtime security for containers. Over time, based on customer feedback and industry trends around DevSecOps and shift-left security, we expanded the product footprint to cover use cases across the build and deploy phases of the container lifecycle.

Over two and half years ago, we made a strategic decision to focus exclusively on Kubernetes and pivoted our entire product to be Kubernetes-native. While this seems obvious today; it wasn’t so then. Fast forward to 2020 and Kubernetes has emerged as the de facto operating system for cloud-native applications and hybrid cloud environments. According to CNCF, Kubernetes is now used by 91% of its annual survey respondents, with 83% of them using it in production compared to 58% just two years ago.

Today, DevOps and Security teams at cloud-native companies, Fortune 500 companies and government agencies, rely on StackRox to implement security and compliance policies across the entire container lifecycle.

Why Is Red Hat Acquiring StackRox?

2020 was a watershed year for StackRox. Despite the challenges presented by the global pandemic, we grew over 2.5x while staying true to our core value of exceeding customer expectations as shown by our customer satisfaction, retention and expansion

View Entire Article on