Tool integration

Terrascan integration guide

IaC security scanner from Tenable

Get a Free API Key

Integrate Terrascan with Vulnesis. Scan Terraform, CloudFormation, Kubernetes, Helm, and Dockerfiles.

CLI toolSARIF

Install & scan

$ # Download from https://github.com/tenable/terrascan/releases
$ terrascan scan -d . -i terraform -o sarif

Run Terrascan in CI

Scan on every push and upload the report as a workflow artifact:

- name: Install Terrascan
  run: |
    curl -L $(curl -s https://api.github.com/repos/tenable/terrascan/releases/latest | grep -o 'https://.*Linux_x86_64.tar.gz') | tar xz terrascan
    sudo mv terrascan /usr/local/bin/
- name: Run Terrascan
  run: terrascan scan -d . -i terraform -o sarif > terrascan.sarif
- name: Upload report
  uses: actions/upload-artifact@v6
  with:
    name: terrascan
    path: terrascan.sarif
    if-no-files-found: warn

Then one publish job hands every artifact in the run to Vulnesis, recorded under Terrascan'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" --json

After the run, vulnetix gha status reports what was actually recorded.

How Vulnesis compares: better together

Vulnesis does not replace Terrascan. Keep running it. Vulnesis sits on top of Terrascan (and every other scanner you already own) turning disconnected tool outputs into one prioritised, fixable queue.

Terrascan is strongest at its core category and also carries features in Container & Image Scanning, just as Vulnesis spans categories.

CapabilityVulnesisTerrascan
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~ Dockerfile scanning plus K8s admission-controller enforcement
IaC / misconfiguration✓ Terraform, k8s, CloudFormation✓ Core: 500+ Rego policies (Terraform, CFN, K8s, Helm, Kustomize); CIS/NIST/PCI mapped
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 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 Terrascan does well

Where Vulnesis adds to it: Terrascan was archived read-only by Tenable on 20 Nov 2025, so it no longer picks up new policies or provider changes. Vulnesis ingests its SARIF for teams still running it, dedupes into the one queue, and provides the actively-maintained IaC engine plus exploit-intel, VEX, EOL and SSVC layers on top. Better together while it lives; Vulnesis is the forward path.

No migration, no rip-and-replace. Terrascan 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 Terrascan results in Vulnesis

Upload Terrascan SARIF 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.

Terrascan documentation ↗  ·  Source repository ↗

Wire Terrascan into your CI/CD pipeline →