Prepare for v0.38.0 #3709
knqyf263
started this conversation in
Development
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Draft to collaborate on v0.38.0 release announcement
🚀 What's new? 🚀
🐳 Complete Docker CIS Benchmark 📝
In the previous release we have introduced Docker CIS Benchmark scanning to Trivy (
trivy image --compliance docker-cis
). With this release Trivy now completes the report by detecting vulnerabilities of installed packages (section 4.4) and secrets in the Dockerfile (section 4.10).⎈ Kubernetes resources for deprecated and removal APIs 💀
When Trivy scans Kubernetes resources it can now alert when the resource is using a deprecated (or about to be) API, and will also suggest the recommended newer version. now can easily check resources against specific k8s version
🐭 Dependency tree and license support for Go 🌲
When scanning a Go project, Trivy now identifies dependency relationships and licenses. This works by finding package sources in
$GOPATH
so in order to work, make sure modules were downloaded to local cache beforehand (go mod download
/go mod tidy
).See here for detail.
📃 Dependency tree for Poetry (Python) 🌲
When scanning a Poetry project, Trivy now identifies dependency relationships and shows the tree with
--dependency-tree
. It also requirespyproject.toml
alongsidepoetry.lock
to identify dependency relationships.See here for detail.
💎 Dependency tree for Bundler (Ruby) 🌲
Trivy now shows a dependency origin tree on Gemfile.lock. The following example describes the vulnerable
actionpack
is introduced byactioncable
, which is a direct dependency of the Ruby project.🧭 Command completion
See the documentation for detail.
Thanks, @didiermichel and @congbang-le
🕐 Fail on EOSL OS 🚫
You may surprisingly get no vulnerabilities in old images. OS vendors don't provide security advisories for OSes at the end of service (EOL), then newly disclosed vulnerabilities may not be detected. The
--exit-on-eol
flag enables you to be aware of this situation.It fails scanning on EOL OSes with the specified exit code.
Thanks, @blueskyson
🫖 Configure the Java DB repository
In the previous release we introduced new Java scanning architecture that does not rely on external API calls during scan and thus is much more reliable. The new Java scanner uses a dedicated "Trivy Java DB" that is added to the regular "Trivy DB" for Java scanning. This release makes is possible override the default Java DB location using a new flag:
--java-db-repository
.Thanks, @nobbs
🎨 Ability to supply custom schemas for Rego policies
It's now possible to supply your custom schemas (or use from a collection of built-in ones) in your Rego policies while doing misconfiguration scanning.
You can read more on this here for more details.
🔮Add optional selectors for Policies
In this release we've introduced the support for subtypes on selectors. With such granular selectors, you can specifically target certain rego policies to be only evaluated if the resources under scan are applicable.
See here for more details on how to use this feature.
Beta Was this translation helpful? Give feedback.
All reactions