Aqua Cloud Native Blog › Categories: CONTAINER SECURITY

Today at re:Invent, Amazon is announcing AWS Fargate, a container service that allows you to provision containers in AWS without having to worry about the VM instances for them to run on. We had an early preview, and the opportunity to see how Aqua’s Container Security Platform works to protect containers running in it.

Amazon Web Services announced today at re:Invent an to a recent feature PrivateLink, that enables AWS Virtual Private Cloud customers to consume apps outside their VPCs through service endpoints, using their own private IP addresses and security groups. This is a non-trivial task since VPCs are made to be isolated, so normally, making an external SaaS application …

Aqua CNAPP is focused on making the platform more scalable for our customer deployments, which include some of the world’s largest container setups.

Since 1996, the HIPAA act has mandated how personal health information (PHI) should be secured and protected from prying eyes. HIPAA requirements changed how companies in the healthcare industry treat patient data, as well as the processes governing it, the applications that handle it, and the infrastructure that runs those applications. In the U.S, following HIPAA …

In our many conversations with customers, Docker secrets management has come up as a particularly thorny issue that seemed to lack an elegant, cross-platform solution for container environments. Not a new issue in the enterprise space, especially as pertains to large-scale DevOps environments, the challenges of managing secrets become amplified in container environments.

Last month at VMWorld we had the pleasure of being part of a next-generation security session given by VMWare’s SVP of Security Products, Tom Corn. 

There’s nothing wrong with seeking help, and that’s especially true for container processes. Third-party Docker tools that help with testing, images, backups and other important procedures are invaluable, even more so when they’re free.

Like many of you working in Docker-space, over time I’ve come across a ton of third-party tools that improve management, cleanup, orchestration, development and other container processes.

In the last 2 posts about the main security features in Docker 1.10 we tackled the Authorization plug-in and the Secomp profiles. In this final post we’ll focus on the new support for Linux User Namespace. Before the release of Docker 1.10, a container running under user=root in Docker would have run as root also on the host …

The new Docker 1.10 release has a host of new features, among them several security improvements that merit the attention of anyone using Docker to develop and run applications. I’d like to focus on three of these features in a short series of blogs: Seccomp profiles, Authorization Plug-in, and User Namespace Support.

Welcome to Scalock’s new blog.