Demos and production are different sports. This checklist covers what changes when Trivy has to be reliable, secure and observable under real load.
Security and reliability defaults
- Add Trivy as a required check on pull requests
- Generate SBOMs (CycloneDX/SPDX) for supply-chain visibility
A production-minded config
Config file to fail only on HIGH/CRITICAL and ignore unfixed CVEs.
# trivy.yaml
severity:
- HIGH
- CRITICAL
vulnerability:
ignore-unfixed: true
exit-code: 1Operational best practices
- Gate on HIGH/CRITICAL with ignore-unfixed, then tighten over time
- Scan images, IaC and filesystems - not just one surface
- Cache and periodically refresh the DB in CI
In production, boring and reproducible beats clever every time.
Want 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.