Aqua News

Enterprise Times caught up with Liz Rice, Technology Evangelist, Aqua Security and Sugu Sougoumarane, CTO, PlanetScale Data at the Cloud Native Computing Conference and KubeCon in Copenhagen. We talked about Vitess, the open source database clustering system which is now a CNCF project. At the same time we talked about the challenge of container security…

May 2018 can be titled “The Month of Kubernetes”, starting at KubeCon Europe, with triple the attendance just last year, followed by many exciting announcements from the cloud-native ecosystem. Will DockerCon next month bring the same level of excitement? We hope so.

Supports Red Hat OpenShift workloads that use CRI-O as the runtime engine Red Hat Summit, San Francisco, and Boston, MA – May 7, 2018 – Aqua Security, the market-leading platform provider for securing container-based and cloud-native applications, today announced early availability of its runtime security controls for workloads using the CRI-O runtime engine, including those …

Aqua Security rolled out initial runtime security control support for container workloads running across the CRI-O Kubernetes runtime platform. A container runtime provides an API and tools that abstract low-level technical details in the container.

Aqua’s expertise in full lifecycle container security helps Google Cloud customers secure applications running on Google Kubernetes Engine KubeCon, Copenhagen, Denmark — May 3, 2018 — Aqua Security, a platform provider for full lifecycle container and cloud-native security, today announced its partnership with Google Cloud to bring container runtime security capabilities to Cloud Security Command …

A cloud-native deployment could look like a nightmare to a security professional: thousands of containers, each with their own versions of different operating system files, packages and executables. Doesn’t this multiply the patching problem by orders of magnitude? Fortunately, some of the main tenets of today’s best practices in DevOps can really help. Let’s see how …

The monitoring and security challenges associated with microservices architectures arises from how microservices were created to be highly scalable — which means they may replicate themselves across nodes rapidly, run for minutes, and then shut down. Security tools geared for static locations, even virtual ones, will thus not work.

There are a lot of options to avoid having your Kubernetes environment hacked. But I’m often asked: What are the main Kubernetes security best practices that you absolutely must get right, assuming you don’t have the time to do a CISSP certification and also become a full-time Kubernetes expert? Here are the five things you need to know.