Replies: 1 comment 11 replies
-
|
Hello @micsinyei Regards, Dmitriy |
Beta Was this translation helpful? Give feedback.
11 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment



Uh oh!
There was an error while loading. Please reload this page.
-
Description
Backgroud:
I use trivy and standalone OPA in Jenkins Pipeline. I wanted to switch to Trivy only so I can simplify the pipeline.
Our use-case like, extending checks for security groups and allowed AMI (in aws) requires to use the terraform plan(json) option.
Jenkins accepts Sarif format, so the check on terraform works perfectly, but when I use the custom checks then the first rule (how the directory and files are listed, I assume) becomes a descriptor for every other rule. I believe this is on trivy's side and how the data is exported
I can show the jenkins output, but I am not sure how should the sarif file looklike.
The console output also can be checked with the trivy-checks examples
Desired Behavior
Jenkins:
Artifact: iac.json Type: json Vulnerability N/A Severity: HIGH Message: Do not use inline egress rule for security group:sg_inline .
Artifact: iac.json Type: json Vulnerability N/A Severity: HIGH Message: Opening this ingress port to the internet is prohibited:82. Resource: example
Actual Behavior
Jenkins
N/A: Misconfiguration Necessary metadata for EC2 For additional help see: Misconfiguration N/A | Type | Severity | Check | Message | Link | | --- | --- | --- | --- | --- | |JSON Security Check|HIGH|Necessary metadata for EC2|Instance metadata tags in metadata options are not defined for: example Metadata tag should be enabled in order to use ansibale. **Artifact: iac.json Type: json Vulnerability N/A Severity: HIGH Message: Do not use inline egress rule for security group:sg_inline .**N/A: Misconfiguration Necessary metadata for EC2 For additional help see: Misconfiguration N/A | Type | Severity | Check | Message | Link | | --- | --- | --- | --- | --- | |JSON Security Check|HIGH|Necessary metadata for EC2|Instance metadata tags in metadata options are not defined for: example.Metadata tag should be enabled in order to use ansibale. **Artifact: iac.json Type: json Vulnerability N/A Severity: HIGH Message: Opening this ingress port to the internet is prohibited:82. Resource: example**Console output of trivy-checks:
Also shows duplication
Reproduction Steps
Target
Filesystem
Scanner
Misconfiguration
Output Format
SARIF
Mode
Standalone
Debug Output
Operating System
Ubuntu 24 LTS (WSL)
Version
Checklist
trivy clean --allBeta Was this translation helpful? Give feedback.
All reactions