Replies: 1 comment 3 replies
-
|
Hi @macpak ! Is this a private repo? |
Beta Was this translation helpful? Give feedback.
3 replies
-
|
Yes, sorry, cannot share it. |
Beta Was this translation helpful? Give feedback.
-
|
Please note that the output of tfsec and Trivy may differ, as some fixes and enhancements have been made to Trivy. More context is needed to understand what the problem is.
|
Beta Was this translation helpful? Give feedback.
-
|
Can you create a minimally reproducible example while preserving the project structure? |
Beta Was this translation helpful? Give feedback.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Description
I am in the process of migrating from tfsec to Trivy. Here is the structure of my Terraform repository:
I run tfsec recursively as a validation step in a PR, starting from
project/src, and it correctly identifies all issues. I've transitioned to Trivy and initiated scanning with the following command:trivy config .However, I've noticed that when I start the recursive scan at the
project/srclevel, it doesn't find all issues, particularly in theproject/src/modulesdirectory. But when I start the scan deeper, for instance atproject/src/modules, it works correctly. It appears that the recursive scan might be skipping some folders.Desired Behavior
Trivy accurately detects all issues in the repository.
Actual Behavior
Trivy misses some issues when run from a top-level folders.
Reproduction Steps
Target
None
Scanner
Vulnerability
Output Format
None
Mode
Standalone
Debug Output
Operating System
Windows 11
Version
Checklist
trivy clean --allBeta Was this translation helpful? Give feedback.
All reactions