Trivy Operator
aquasecurity.github.io
- Free plan
- Open source
- Linux
- API
- Self-hosted
What Trivy Operator is
Trivy Operator is a free, self-hosted Kubernetes operator that scans clusters for security issues and stores its findings as Kubernetes resources accessible through the Kubernetes API. It watches Kubernetes state changes and can start scans when resources such as Pods are created. Automatic checks cover workload vulnerabilities, configuration audits, exposed secrets, RBAC assessments, Kubernetes infrastructure, and deprecated API use. Configuration audits use predefined rules or custom Open Policy Agent policies. The operator also creates compliance reports for Kubernetes hardening guidance, the CIS Kubernetes Benchmark, and Pod Security Standards profiles, plus Software Bill of Materials reports for workloads. Stale reports are removed through Kubernetes garbage collection, and deleting an owned vulnerability report can trigger another scan. A /metrics endpoint is exposed by default for Prometheus. Installation supports Helm, kubectl manifests, and Operator Lifecycle Manager. The documentation says there is no user interface and describes the project as incubating, so APIs and custom resource definitions may change.
Who it suits
It suits Kubernetes administrators and security teams managing self-hosted clusters through APIs and Kubernetes resources. It is also useful for teams that need vulnerability, posture, compliance, and SBOM reports.
Good to know, and what to watch
- Automatic scans follow Kubernetes state changes
- Audits configurations with custom OPA policies
- Produces compliance and SBOM reports
- Prometheus metrics endpoint enabled by default
- Helm, kubectl, and OLM installation
- No user interface
- Project is described as incubating
- APIs and custom resources may change
Plans
Every plan and priceTrivy Operator
Free plan
The verdict
Trivy Operator concentrates security scanning and reporting inside Kubernetes itself. Its broad report types and deployment choices fit technical teams, while the lack of a UI and incubating status matter during adoption planning.
What the maker publishes
- Automatic scans
- It watches Kubernetes state changes and triggers scans when resources change, such as when a Pod is created. source
- Company ownership status
- Crunchbase describes Aqua Security as a private Series E company headquartered in Ramat Gan, Tel Aviv, Israel, with a 251–500 employee range. source
- Compliance
- It produces compliance reports for Kubernetes hardening guidance, the CIS Kubernetes Benchmark, and Pod Security Standards profiles. source
- Compliance reports
- Built-in compliance outputs cover NSA/CISA Kubernetes hardening guidance, CIS Kubernetes Benchmark 1.23, and Kubernetes Pod Security Standards baseline and restricted profiles. source
- Configuration auditing
- It audits Kubernetes resources with predefined rules or custom Open Policy Agent policies. source
- Configuration audits
- It audits Kubernetes resource configuration using predefined rules or custom Open Policy Agent policies. source
- Configuration limits
- Documented defaults include a five-minute scan-job timeout, a maximum of 10 concurrent scan jobs, one concurrent node-collector job, and 30-second retry delay. source
- Custom resources
- The project defines namespaced VulnerabilityReport, ConfigAuditReport, ExposedSecretReport, RbacAssessmentReport, InfraAssessmentReport and SbomReport resource types plus cluster-level report types. source
- Documentation depth
- Official documentation includes installation, configuration, troubleshooting, quick starts, tutorials, integrations, scanner settings, private registries, compliance, CRD schemas, and FAQ material. source
- Exposed secrets
- It creates reports identifying exposed secrets and their locations in cluster workloads. source
- Helm installation
- The Helm instructions add Aqua's chart repository and install into a trivy-system namespace. source
- Independent field benchmark
- Safeguard reported a 31-minute first full-coverage time for 1,400 pods and a 14-second median scan for an 800 MB image in its v0.30/v0.70 test. source
- Infrastructure assessment
- It assesses configuration of Kubernetes core components such as etcd, the API server, scheduler, and controller manager. source
- Installation
- It can be installed through Helm, kubectl manifests, or Operator Lifecycle Manager; Helm is recommended for tracking custom configuration. source
- Installation methods
- Installation is documented through static YAML manifests, Helm, and Operator Lifecycle Manager. source
- Integrations
- Official documentation describes metrics, Lens extension, webhook, and Policy Reporter integrations. source
- Kubernetes API
- Security reports are Kubernetes Custom Resource Definitions and are readable through normal Kubernetes API mechanisms. source
- KubeVela integration
- KubeVela documents a Trivy Operator add-on with a metrics service reachable on port 9115. source
- Lens extension
- A separate Aqua Lens extension displays vulnerability, misconfiguration, exposed-secret, RBAC, and Kubernetes infrastructure reports; its documented prerequisite is Lens 4.0 or newer. source
- License
- The repository is licensed under Apache-2.0. source
- Limit: multi-cluster operations
- Safeguard's comparison says Trivy Operator has no built-in multi-cluster console and requires external aggregation for large estates. source
- Limit: native UI
- Safeguard says the operator produces CRDs but has no native dashboard, so users commonly add DefectDojo, Dependency-Track, or vendor consoles. source
- Limit: reporting and UI
- PeerSpot reviewers repeatedly request better report interpretation, PDF/CSV outputs, and built-in report analysis or a user-friendly interface. source
- Limit: runtime and malware coverage
- PeerSpot reviewers say Trivy lacks dynamic runtime scanning and that malware or anomaly detection may require a separate tool such as ClamAV. source
Checked against the maker's pages on 15 Oct 2026.