What is our primary use case?
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.
What is most valuable?
The image security and image scanning were quite easy compared to Prisma. The solution was very user-friendly.
It is easy to set up.
It's stable.
The documentation was robust.
It's easy to set up.
What needs improvement?
I don't recall coming across any missing features.
It's a bit hard to use the user roles. That was a bit confusing. That was from the interface side, the application from which we logged into Aqua. That needs a bit of improving. The admin was a bit confusing.
For how long have I used the solution?
I've used the solution for a couple of months, maybe.
What do I think about the stability of the solution?
The stability is good. It is reliable. There are no bugs or glitches.
What do I think about the scalability of the solution?
I did not try to scale the solution.
We had 20 to 30 people on the solution.
In my team, we had five members using it - the DevSecOps team. We were on the integration side of it. There might have been two to three project teams, basically, who used to used the pipelines, which we created for them.
How are customer service and support?
We did not use support. We never came across any issues.
Which solution did I use previously and why did I switch?
I was working for Computer Software Corporation, CSC corporation, as a contract employee. There, we were asked to do a research on various cloud security applications. That's where we came in contact with Aqua. We were trying to do apple to apple comparison of Prisma and Aqua.
We felt Aqua is good and we even recommended Aqua to be used - rather than Prisma.
How was the initial setup?
The initial setup was pretty straightforward.
If it is deployed from scratch, the documentation is pretty straightforward. We just followed the steps and we were able to do it. There were no unexpected bugs or any other issues we faced. Everything was quite straightforward.
I'd rate the solution four out of five in terms of the initial setup.
Maintenance was taken care. Maintenance was good there. It doesn't need any more effort. What we used was the latest one, a stable version, and since we were dealing with a corporate organization, we wanted stable versions to be always tested.
What about the implementation team?
We did the implementation in-house.
What's my experience with pricing, setup cost, and licensing?
I'm not sure of the exact pricing. I cannot speak of the exact costs. The company already had a licensed version.
What other advice do I have?
We were working with the latest version of the solution.
We had a cloud dashboard to see our stuff, basically. We used it on-prem; however, once the scanning is done, the results would be posted on that platform. That's where we used to go and see the information.
It's fast to implement and straightforward. It works for all brackets. I'd recommend it to others.
I'd rate it eight out of ten.
Which deployment model are you using for this solution?
On-premises
Disclosure: My company does not have a business relationship with this vendor other than being a customer.