Integrate AttackForge with Vulnetix. Use the AttackForge Self-Service RESTful API to export vulnerability findings from projects, then upload to Vulnetix.
Run AttackForge in CI
Scan on every push and upload the report as a workflow artifact:
- name: Export AttackForge findings
env:
AF_URL: ${{ secrets.AF_URL }}
AF_APIKEY: ${{ secrets.AF_APIKEY }}
PROJECT_ID: ${{ secrets.AF_PROJECT_ID }}
run: |
curl -s "$AF_URL/api/ss/projects/$PROJECT_ID/vulnerabilities" -H "X-SSAPI-KEY: $AF_APIKEY" > attackforge-findings.json
- name: Upload to Vulnetix
run: vulnetix upload --file attackforge-findings.json
How Vulnetix compares: better together
Vulnetix does not replace AttackForge. Keep running it. Vulnetix sits on top of AttackForge (and every other scanner you already own) turning disconnected tool outputs into one prioritised, fixable queue.
AttackForge is strongest at its core category and also carries features in Network & Vulnerability Scanners, just as Vulnetix spans categories.
| Capability | Vulnetix | AttackForge |
|---|---|---|
| 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 | ✗ |
| IaC / misconfiguration | ✓ Terraform, k8s, CloudFormation | ✗ |
| 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 | ~ Ingests scanner output (Nessus, Qualys, Burp) into projects; does not run scans itself |
| Fuzzing | ✗ Ingests fuzzing crashes; no native fuzzer | ✗ |
| Pentest / bug bounty | ✗ Ingests pentest/bug-bounty findings; not a testing service | ✓ Core: manual pentest project and findings management, retest, SLA tracking |
| The Vulnetix orchestration layer | ||
| Cross-scanner dedup & one queue (ASPM) | ✓ Correlates every scanner into one prioritised queue with ownership routing | ~ Consolidates and de-dupes findings within pentest projects, not cross-scanner ASPM |
| 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 AttackForge does well
- Purpose-built pentest lifecycle management: scoping, scheduling, findings capture, retesting, and SLA/remediation tracking in one collaborative workspace
- On-demand branded report generation with CLI, templates, and AI report assistants that compress board-level reporting from days to minutes
- Attack Chain Visualization that maps individual findings to real-world attack paths (and MITRE ATT&CK) for risk prioritisation
- Deep workflow automation (Flows) and a full Self-Service RESTful API pushing findings to Jira, ServiceNow, Azure DevOps, Splunk, Slack/Teams
Where Vulnetix adds to it: Vulnetix ingests and orchestrates AttackForge pentest findings into its unified prioritised queue alongside SAST/SCA/container/IaC/secrets output; it never runs the manual pentest itself. Vulnetix adds cross-scanner dedup, EPSS/KEV/LEV exploit-intel prioritisation, reachability, versioned VEX, SSVC and Safe Harbour autofix that a pentest-management tool does not provide.
No migration, no rip-and-replace. AttackForge keeps doing what it does best; Vulnetix adds the orchestration, exploit-intelligence prioritisation and remediation layer built for the way AppSec works today.
Centralise AttackForge results in Vulnetix
Upload AttackForge JSON, CSV, XML 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.