Trivy Reviews

We are using Trivy for vulnerability scans and identifying open secrets, if there are any, in our Kubernetes clusters. We are visualizing the results on Grafana dashboards, which helps restrict the exposure of secrets and makes our system more precise with image scanners.

What I find valuable is the ease of setup with Trivy, including pre-defined operators that require minimal configuration. The reports generated are easy to read, even for non-technical individuals. Good documentation for installation and troubleshooting is provided. Additionally, it differentiates vulnerabilities based on severity, which aids in addressing vulnerabilities in the correct order.

The main area for improvement is in differentiating between OS and application-based vulnerabilities. Additionally, the customization of reports is limited; we can only add a few parameters. Custom application details in reports would make it easier to identify the use case of each pod.

I have been using Trivy for around six to seven months.

We faced challenges with setting up Trivy on Windows, but the process on Linux was smooth. The complexity is attributed to Windows setups rather than Trivy itself. For implementation, we downloaded the repository, ran a few commands, and used Helm charts to deploy Trivy operators on Kubernetes.

There are no performance or stability issues with Trivy.

Trivy is quite easy to scale, especially on Kubernetes. We have replicated it across multiple clusters, and it scales easily both vertically and horizontally, depending on CPU usage and the number of pods.

We haven't tried reaching out to Trivy's technical support, and I'm unsure if they provide any.

Before Trivy, we did not have any solution in place for scanning.

The initial setup was straightforward for Linux but not for Windows. We followed the documentation provided, ran the necessary commands, and used Helm charts for Kubernetes. It took more than one day for the Kubernetes setup and around five to six hours for the local setup.

We implemented Trivy following the documentation available. The setup for both Trivy itself and the Trivy operator required downloading the repositories and configuring them using Helm charts on Kubernetes.

Trivy is open source, making it cost-effective. There are customization options available at the cluster level, allowing us to modify schedules, scaling, and which pods or images to scan.

We did not evaluate any other solutions. Trivy was the first option that came up during our search.

One piece of advice is to start with the image-based version locally to understand how Trivy works before setting it up on Kubernetes. This local setup will enhance understanding, which helps when customizing the Kubernetes setup. Overall, I rate Trivy as an eight out of ten as a solution.

I use Trivy for CICD and container scanning.

Trivy is easy to integrate with CI/CD and can be installed on desktops to scan images. It helps with all configurations, including scanning of images and file systems, and even detecting secrets, not just vulnerabilities. It is very lightweight, requiring minimal effort to get it working. Trivy catches most vulnerabilities quickly because it does not take time to scan anything.

The only problem is that Trivy does not support reporting features such as generating reports in CSV, which is useful for auditing and reporting. 

Additionally, Trivy should work as a Software Composition Analysis tool. If Trivy could do this, it would be great.

I have been working with Trivy for more than four years.

I find Trivy to be stable.

I do not have to scale Trivy itself. I have to scale the part or the tool that is scanning the images. Each instance is a complete system that can scan as many images as are passed through that scanning stage.

We are using the open source community, so we do not need customer service support. If anything happens, we go on GitHub to find a solution.

Positive

We have been using Trivy from the beginning. We also have another scanner, New Vector, but our primary scanner is Trivy.

The initial setup is straightforward, not just for me, but also for other developers who find it easy to set up and run. We installed Trivy in the container and used it for scanning other images. The setup process is quick and takes approximately five minutes.

We tried QEscape and some other new solutions, however, we settled with Trivy. I am not sure about money savings. I have not explored any other commercial software.

Trivy is a Swiss knife. I recommend it because it is easy to integrate and provides quick results.

On a scale of one to ten, I rate it nine out of ten for vulnerability scanning.

On-premises