Integrate Intruder with Vulnetix. Export vulnerability findings via the Intruder REST API for centralised tracking and prioritisation.
Run Intruder in CI
Scan on every push and upload the report as a workflow artifact:
- name: Export Intruder findings
env:
INTRUDER_TOKEN: ${{ secrets.INTRUDER_API_KEY }}
run: |
curl -X GET "https://api.intruder.io/v1/issues?status=open" -H "Authorization: Bearer $INTRUDER_TOKEN" -H "Accept: application/json" > intruder-issues.json
- name: Upload to Vulnetix
run: vulnetix upload --file intruder-issues.json
How Vulnetix compares: better together
Vulnetix does not replace Intruder. Keep running it. Vulnetix sits on top of Intruder (and every other scanner you already own) turning disconnected tool outputs into one prioritised, fixable queue.
Intruder is strongest at its core category and also carries features in DAST, Cloud Security & CSPM, Secret Scanning, just as Vulnetix spans categories.
| Capability | Vulnetix | Intruder |
|---|---|---|
| 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 | ~ Authenticated/unauthenticated web app and API scanning for 75+ application vulns (XSS, SQLi) incl SPAs, secondary to infra scanning |
| Container & image | ✓ Image CVEs, base image, Dockerfile | ✗ |
| IaC / misconfiguration | ✓ Terraform, k8s, CloudFormation | ✗ |
| Secret scanning | ✓ 1,000+ rules, source + binary + git history | ~ Cloud/config scans surface exposed credentials among misconfigurations; not a dedicated secrets scanner |
| Cloud / CSPM | ✓ Cloud-posture findings, compliance tab | ~ Agentless cloud scanning for AWS/Azure/GCP/Cloudflare surfaces misconfigurations and exposure |
| 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 | ✓ Core: emulates a remote attacker to find missing patches, misconfigs, exposed systems and encryption weaknesses across 140k+ checks |
| 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 | ~ Rapid-response scanning proactively checks for emerging/critical threats being exploited in the wild to focus remediation |
| 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 Intruder does well
- Continuous, API-first attack-surface monitoring that automatically adds newly exposed cloud IPs/hostnames as scan targets (cloud sync)
- Broad network scanning against 140,000+ infrastructure weaknesses (missing patches, RCE, misconfigs, exposed systems, weak encryption)
- Authenticated and unauthenticated web app and API scanning for 75+ application vulnerabilities (XSS, SQLi), including single-page apps
- Emerging-threat / rapid-response scanning and a genuinely easy workflow tuned for lean security teams, with AWS/Azure/GCP/Cloudflare integrations
Where Vulnetix adds to it: Vulnetix ingests Intruder scan results via its REST API and merges the infra, web-app and cloud findings into the single deduplicated queue with SAST/SCA/IaC/secrets/SBOM, layering EPSS/KEV/ESS/LEV prioritisation, reachability, versioned VEX, EOL and SSVC. Vulnetix runs no network or DAST engine of its own, so Intruder stays the continuous attack-surface scanner and Vulnetix is the ASPM orchestration and prioritisation layer above it.
No migration, no rip-and-replace. Intruder keeps doing what it does best; Vulnetix adds the orchestration, exploit-intelligence prioritisation and remediation layer built for the way AppSec works today.
Centralise Intruder results in Vulnetix
Upload Intruder JSON 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.