tfsec is deprecated and incorporated into Trivy. Migrate to trivy config for continued support.
Install & scan
$ go install github.com/aquasecurity/tfsec/cmd/tfsec@latest $ tfsec . --format sarif --out tfsec.sarif
How Vulnetix compares: better together
Vulnetix does not replace tfsec. Keep running it. Vulnetix sits on top of tfsec (and every other scanner you already own) turning disconnected tool outputs into one prioritised, fixable queue.
tfsec is strongest at its core category and also carries features in Container & Image Scanning, just as Vulnetix spans categories.
| Capability | Vulnetix | tfsec |
|---|---|---|
| Security coverage | ||
| SAST (static code analysis) | ✓ Built-in rules + Semgrep augmentation | ✗ |
| SCA / dependencies | ✓ 40+ ecosystems, transitive graph | ✗ |
| DAST (dynamic testing) | ~ Ingests DAST results; no native dynamic engine | ✗ |
| Container & image | ✓ Image CVEs, base image, Dockerfile | ~ Kubernetes provider rules via Terraform HCL; deep container scanning only in successor Trivy |
| IaC / misconfiguration | ✓ Terraform, k8s, CloudFormation | ✓ Core: hundreds of Terraform HCL rules, multi-cloud (github.com/aquasecurity/tfsec) |
| Secret scanning | ✓ 1,000+ rules, source + binary + git history | ✗ |
| Cloud / CSPM | ✓ Cloud-posture findings, compliance tab | ✗ |
| Mobile (MAST) | ~ Ingests mobile scanner output; no native mobile engine | ✗ |
| License compliance | ✓ SPDX, copyleft/AGPL/SSPL policy | ✗ |
| SBOM generation | ✓ CycloneDX 1.7 + SPDX 2.3, cosign-signable | ✗ |
| 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 Vulnetix 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, Vulnetix 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 tfsec does well
- Fast, focused Terraform/HCL static analysis with hundreds of built-in rules for insecure defaults, permissive IAM, unencrypted resources and public exposure
- Evaluates HCL expressions, Terraform functions and module relationships (local and remote) rather than raw text matching
- Multi-cloud rule coverage: AWS, Azure, GCP plus DigitalOcean, GitHub, Kubernetes, OpenStack and Oracle providers
- Wide output support (JSON, SARIF, CSV, CheckStyle, JUnit) and a documented migration path into Trivy
Where Vulnetix adds to it: tfsec is deprecated: Aqua folded its rules into Trivy (trivy config). Vulnetix ingests tfsec (or Trivy config) SARIF and dedupes it into the cross-scanner queue, then adds the exploit-intel, versioned VEX, EOL, SSVC and Safe Harbour autofix layers neither tool runs. Better together: keep the Terraform rule engine, let Vulnetix orchestrate and prioritise above it.
No migration, no rip-and-replace. tfsec keeps doing what it does best; Vulnetix adds the orchestration, exploit-intelligence prioritisation and remediation layer built for the way AppSec works today.
Centralise tfsec results in Vulnetix
Upload tfsec SARIF output to the Vulnetix 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.