Integrate Faraday with Vulnesis. Deploy Faraday via Docker Compose, collect findings from your pentest team, and export vulnerabilities via the REST API for upload to Vulnesis.
Install & scan
$ docker compose up -d
$ # Authenticate and get token
FARADAY_URL="http://localhost:5985"
TOKEN=$(curl -s -X POST "${FARADAY_URL}/_api/v3/login" -H 'Content-Type: application/json' -d '{"email":"admin@example.com","password":"changeme"}' | jq -r '.response.data.token')
# Export all vulnerabilities from a workspace
curl -s "${FARADAY_URL}/_api/v3/ws/my_engagement/vulns" -H "Authorization: Token ${TOKEN}" | jq '.vulnerabilities' > faraday-vulns.json
Run Faraday in CI
Scan on every push and upload the report as a workflow artifact:
- name: Export Faraday vulnerabilities
env:
FARADAY_URL: ${{ secrets.FARADAY_URL }}
FARADAY_EMAIL: ${{ secrets.FARADAY_EMAIL }}
FARADAY_PASS: ${{ secrets.FARADAY_PASS }}
WORKSPACE: ${{ secrets.FARADAY_WORKSPACE }}
run: |
TOKEN=$(curl -s -X POST "$FARADAY_URL/_api/v3/login" -H 'Content-Type: application/json' -d "{"email":"$FARADAY_EMAIL","password":"$FARADAY_PASS"}" | jq -r '.response.data.token')
curl -s "$FARADAY_URL/_api/v3/ws/$WORKSPACE/vulns" -H "Authorization: Token $TOKEN" | jq '.vulnerabilities' > faraday-vulns.json
- name: Upload to Vulnesis
run: vulnetix upload --file faraday-vulns.json
How Vulnesis compares: better together
Vulnesis does not replace Faraday. Keep running it. Vulnesis sits on top of Faraday (and every other scanner you already own) turning disconnected tool outputs into one prioritised, fixable queue.
Faraday is strongest at its core category and also carries features in Network & Vulnerability Scanners, DAST, SAST, SCA, just as Vulnesis spans categories.
| Capability | Vulnesis | Faraday |
|---|---|---|
| Security coverage | ||
| SAST (static code analysis) | ✓ Built-in rules + Semgrep augmentation | ~ Ingests/orchestrates Semgrep output; no first-party SAST rules |
| SCA / dependencies | ✓ 40+ ecosystems, transitive graph | ~ Consolidates dependency findings from connected scanners |
| DAST (dynamic testing) | ~ Ingests DAST results; no native dynamic engine | ~ Orchestrates ZAP/Burp scans via Agents Dispatcher; no proprietary DAST 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 | ~ Runs/imports Nmap/Masscan/Nessus/OpenVAS via agents; orchestrates external engines |
| Fuzzing | ✗ Ingests fuzzing crashes; no native fuzzer | ✗ |
| Pentest / bug bounty | ✗ Ingests pentest/bug-bounty findings; not a testing service | ✓ Multi-user pentest IDE: workspaces, findings, templates, report generation |
| The Vulnesis orchestration layer | ||
| Cross-scanner dedup & one queue (ASPM) | ✓ Correlates every scanner into one prioritised queue with ownership routing | ✓ Automatically identifies and merges duplicate issues across all imported tools |
| 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 Faraday does well
- Aggregates 80+ security tools (Nessus, OpenVAS, Qualys, Burp, ZAP, Nmap, Metasploit, Nuclei, Semgrep) into one normalized vulnerability model
- Faraday Agents Dispatcher can actually run scanners remotely on a schedule and pull results back, real orchestration, not just import
- Automatic deduplication/merging of duplicated issues plus a centralized dashboard and per-engagement workspaces with RBAC
- Open-source core with a documented REST API and Release 5.21 MCP-server support for connecting AI agents to vuln-management workflows
Where Vulnesis adds to it: Faraday is the closest of the pentest tools to an orchestrator (its Agents Dispatcher runs third-party scanners and dedups results) but it wraps other engines rather than owning them. Vulnesis ingests and orchestrates Faraday's consolidated pentest and scan output (it does not run the pentests itself) while also shipping its own native SAST (built-in + Semgrep), SCA across 40+ ecosystems, IaC, container, secrets, cloud/CSPM, license, SBOM and supply-chain malware/package-firewall. On the cross-cutting layer Vulnesis adds exploit-intel prioritisation, reachability, immutable versioned VEX + audit, EOL and SSVC policy and Safe Harbour autofix that Faraday's vuln-management workflow does not cover.
No migration, no rip-and-replace. Faraday 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 Faraday results in Vulnesis
Upload Faraday JSON 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.