I have been testing various solutions to ensure which one is the best fit to protect data, applications, and infrastructure in cloud environments. We are distributors in Turkey, focusing on promoting cost-effective security solutions in the market. When engaging with enterprise clients, particularly in the financial sector such as banks, I emphasize the importance of robust security measures. During customer visits, they express a keen interest in technical support and want demonstrations of software source code management, security support for software chains, and workflow protection.

We did very little with Aqua, basically. We only used Aqua for the image scanning and document scanning and that's it. Since I was working on a DevSecOps project, I was asked to find how complicated it was comparatively, for example, which is more complicated, whether the Aqua or Prisma, and how fast these things could be churned out or integrated into an existing pipeline, or when you create a new pipeline, how fast these things work. I had to experiment with these things.

In our scenario, we were creating pipelines for Infrastructure as Code. Our pipeline would be doing the scanning for all infrastructure code. In that code, if any image is mentioned, we would pick them up, we would scan them, and that's where we'll be using Aqua or Prisma. We have created items with both of those. One of the pipelines which had Aqua would be scanning and finding the vulnerabilities inside the image.

The solution is used mainly to scan public clouds or containers.

It can be used on demand. For example, when we go through the DevOps lifecycle, containers can be brought in based on demand for some use cases. We often need application onboarding and application changes. The containers do pop up based on the user story that has been defined. Therefore, we have on-demand scanning of those, and we utilize Aqua Security scan to handle that task.

We use this product for all of our network security.

We mainly used Aqua Security for container-related Kubernetes security in the CI/CD pipelines to secure the runtime of the Kubernetes clusters. 

We're using it for the Image Vulnerability Scanning. We have an on-premise solution, so for us, vulnerability scanning is most important. Part of our platform spins up Docker containers and uses Docker internally. We're not a SaaS company, so it's not in the cloud and, therefore, it's very important for us to deploy at the customer's environment. It's very important that we deploy Docker images, that we see the vulnerabilities because we deploy in the customer's environment.

Generally, we are using the product for container security, and we have several items related to containers. For example, one-time protection and zero-day attacks.

I'm using it for workload protection. So, in most cases, for protecting containers, verifying Kubernetes configurations, cloud configurations, and identifying security misconfigurations, vulnerabilities, and risks.

We used Aqua Security to address our container security concerns since we were using Docker in production. There was a clear blind spot that needed to be addressed and Aqua Security was able to fill that gap by providing visibility into the container images and the runtime aspect of our container platform.

We use this solution to secure cloud media applications that are developed for containers and cloud-native services like ETS, AKS and GCP.

I am the only one using this product in our company.

We use Aqua Security for securing our container applications, particularly when it comes to the runtime stage.

There are about five of us from the security side of my company who directly use this solution.

We use Aqua Security for the container security features.

Our primary use case is to sequelize all of the ACD and to review the images.