Most Trivy pain is self-inflicted and predictable. Here are the mistakes we see most, and the fix for each.
Mistake 1: Failing on unfixed CVEs and drowning in noise
Fix: Gate on HIGH/CRITICAL with ignore-unfixed, then tighten over time. Make it the default in your templates and enforce it in review or CI so the mistake cannot come back.
Mistake 2: Scanning only images and ignoring IaC and secrets
Fix: Scan images, IaC and filesystems - not just one surface. Make it the default in your templates and enforce it in review or CI so the mistake cannot come back.
Mistake 3: Never updating the vulnerability DB in air-gapped runners
Fix: Cache and periodically refresh the DB in CI. Make it the default in your templates and enforce it in review or CI so the mistake cannot come back.
A safer baseline
Config file to fail only on HIGH/CRITICAL and ignore unfixed CVEs.
# trivy.yaml
severity:
- HIGH
- CRITICAL
vulnerability:
ignore-unfixed: true
exit-code: 1Want senior help putting Trivy to work - or a team bootcamp on it? CodeWizard runs Israel's largest DevOps community and embeds named senior engineers with a transparent hours log. Book a free consult or explore the Academy.