Integrate Trivy IaC scanning with Vulnesis. Use trivy config to detect misconfigurations across Terraform, CloudFormation, Kubernetes manifests, Helm charts, ARM, and Dockerfiles.
Install & scan
$ # Homebrew (macOS/Linux) brew install trivy # Install script (Linux) curl -sfL https://raw.githubusercontent.com/aquasecurity/trivy/main/contrib/install.sh | sudo sh -s -- -b /usr/local/bin # Debian/Ubuntu sudo apt-get install wget gnupg wget -qO - https://aquasecurity.github.io/trivy-repo/deb/public.key | gpg --dearmor | sudo tee /usr/share/keyrings/trivy.gpg > /dev/null echo "deb [signed-by=/usr/share/keyrings/trivy.gpg] https://aquasecurity.github.io/trivy-repo/deb generic main" | sudo tee /etc/apt/sources.list.d/trivy.list sudo apt-get update && sudo apt-get install trivy $ trivy config . --format sarif --output trivy-iac.sarif
Run Trivy IaC in CI
Scan on every push and upload the report as a workflow artifact:
- name: Trivy IaC scan
uses: aquasecurity/trivy-action@0.33.1
with:
scan-type: 'config'
scan-ref: '.'
format: 'sarif'
output: 'trivy-iac.sarif'
severity: 'CRITICAL,HIGH,MEDIUM'
- name: Upload report
uses: actions/upload-artifact@v6
with:
name: trivy-iac
path: trivy-iac.sarif
if-no-files-found: warnThen one publish job hands every artifact in the run to Vulnesis, recorded under Trivy IaC's own name and version. Written once per workflow, however many scanners you run:
publish:
name: Publish to Vulnesis
runs-on: ubuntu-latest
needs: [scan] # every scanner job, or its report is never published
if: always() # or one failing scanner suppresses all the others
permissions:
contents: read
actions: read # required to list the run's artifacts
env:
VULNETIX_ORG_ID: ${{ secrets.VULNETIX_ORG_ID }}
VULNETIX_API_KEY: ${{ secrets.VULNETIX_API_KEY }}
steps:
- uses: actions/checkout@v5
- name: Install Vulnesis CLI
run: |
curl -fsSL https://cli.vulnes.is/install.sh | sh -s -- --install-dir "$HOME/.local/bin"
echo "$HOME/.local/bin" >> "$GITHUB_PATH"
- name: Publish scanner reports
env:
GITHUB_TOKEN: ${{ github.token }}
run: vulnetix gha upload --org-id "$VULNETIX_ORG_ID" --jsonAfter the run, vulnetix gha status reports what was actually recorded.
How Vulnesis compares: better together
Vulnesis does not replace Trivy IaC. Keep running it. Vulnesis sits on top of Trivy IaC (and every other scanner you already own) turning disconnected tool outputs into one prioritised, fixable queue.
Trivy IaC is strongest at its core category and also carries features in SCA, Secret Scanning, SBOM Generation, Container & Image Scanning, License Compliance, just as Vulnesis spans categories.
| Capability | Vulnesis | Trivy IaC |
|---|---|---|
| Security coverage | ||
| SAST (static code analysis) | ✓ Built-in rules + Semgrep augmentation | ✗ |
| SCA / dependencies | ✓ 40+ ecosystems, transitive graph | ~ Same binary does dependency/OS vulnerability scanning via --scanners vuln |
| DAST (dynamic testing) | ~ Ingests DAST results; no native dynamic engine | ✗ |
| Container & image | ✓ Image CVEs, base image, Dockerfile | ~ Container image scanning is a primary Trivy use case (this profile scopes the IaC/config scanner) |
| IaC / misconfiguration | ✓ Terraform, k8s, CloudFormation | ✓ Core: trivy config scans Terraform/CFN/K8s/Helm/Dockerfile/ARM with Rego-powered built-in and custom checks |
| Secret scanning | ✓ 1,000+ rules, source + binary + git history | ~ Built-in secret detection via --scanners secret |
| Cloud / CSPM | ✓ Cloud-posture findings, compliance tab | ✗ |
| Mobile (MAST) | ~ Ingests mobile scanner output; no native mobile engine | ✗ |
| License compliance | ✓ SPDX, copyleft/AGPL/SSPL policy | ~ License scanning supported alongside vuln/misconfig |
| SBOM generation | ✓ CycloneDX 1.7 + SPDX 2.3, cosign-signable | ~ Generates CycloneDX and SPDX SBOMs |
| Malware / supply-chain | ✓ De-duplicated corpus + install-time firewall (25 registries) | ✗ |
| Network / infra vuln | ~ Ingests network scanner output; no native network scanner | ✗ |
| Fuzzing | ✗ Ingests fuzzing crashes; no native fuzzer | ✗ |
| Pentest / bug bounty | ✗ Ingests pentest/bug-bounty findings; not a testing service | ✗ |
| The Vulnesis orchestration layer | ||
| Cross-scanner dedup & one queue (ASPM) | ✓ Correlates every scanner into one prioritised queue with ownership routing | ✗ |
| Exploit-intel prioritisation | ✓ EPSS, CISA KEV, Coalition ESS, CWSS, Vulnesis LEV | ✗ |
| Reachability analysis | ✓ Tree-sitter + CVEAffected; direct/transitive/semantic | ✗ |
| Versioned VEX + audit trail | ✓ Immutable OpenVEX/CycloneDX, cosign-signable | ✗ |
| Safe Harbour autofix | ✓ Resolves + applies the nearest safe version | ✗ |
| End-of-life policy | ✓ Flags/blocks past-EOL runtimes & packages | ✗ |
| SSVC / risk-based policy | ✓ SSVC v2 + CISA/FedRAMP/Essential-8 presets | ✗ |
✓ full · ~ partial · ✗ not covered
What Trivy IaC does well
- All-in-one single Go binary: one tool covers IaC misconfig, dependency vulnerabilities, secrets, SBOM and license scanning via --scanners flags
- Broad IaC format support with auto-detection: Terraform, CloudFormation, Kubernetes, Helm, Dockerfile and Azure ARM
- Hundreds of built-in checks powered by OPA/Rego, extensible with custom Rego policies
- Fast, open-source (Aqua Security), widely adopted in CI and Kubernetes admission workflows
Where Vulnesis adds to it: Vulnesis ingests Trivy's misconfig, SCA, secret, SBOM and license output and deduplicates it against other scanners into one prioritised ASPM queue, adding EPSS/KEV/ESS exploit-intel, reachability, SSVC, immutable versioned VEX, EOL policy and Safe Harbour autofix. Better together: Trivy remains the multi-purpose scanning engine; Vulnesis is the correlation, prioritisation and remediation layer above it.
No migration, no rip-and-replace. Trivy IaC keeps doing what it does best; Vulnesis adds the orchestration, exploit-intelligence prioritisation and remediation layer built for the way AppSec works today. Software Factory agents on a Pix Sandbox can then turn the findings from any scanner into pull requests that a person approves. How Software Factory works.
Centralise Trivy IaC results in Vulnesis
Upload Trivy IaC SARIF, JSON, CycloneDX output to the Vulnesis platform to deduplicate findings, prioritise them with EPSS, CISA KEV and Coalition ESS exploit intelligence, and track remediation across every scanner in a single queue.