Faraday Integration
Faraday is a collaborative vulnerability management platform. reconFTW integrates with Faraday to automatically import scan results.
What is Faraday?
Faraday provides:
Centralized vulnerability database
Team collaboration features
Report generation
Integration with 80+ security tools
Workspace management
Prerequisites
Faraday Installation
# Docker installation (recommended)
docker pull faradaysec/faraday:latest
docker run -d --name faraday -p 5985:5985 faradaysec/faraday
# Or native installation
pip install faradaysecFaraday Setup
Access Faraday web interface:
http://localhost:5985Create admin account
Create workspace for your project
Generate API token
Configuration in reconFTW
Enable Faraday Integration
secrets.cfg Setup
Data Imported to Faraday
reconFTW automatically sends:
Hosts
Subdomain resolution
Host
Services
Port scan (nmap)
Service
Vulnerabilities
Nuclei results
Vulnerability
CVEs
Nmap vulners script
Vulnerability
Integration Flow
Workspace Management
Create Workspace
Workspace Strategy
Per-target
One workspace per domain
Isolated scans
Per-program
One workspace per bug bounty
Program tracking
Unified
Single workspace
Overview of all targets
Viewing Results
Faraday Web Interface
Open
http://localhost:5985Select workspace (
reconftw)Navigate to:
Hosts: All discovered hosts with IPs
Services: Ports and services per host
Vulns: All vulnerabilities by severity
Faraday CLI
Report Generation
Built-in Reports
Faraday generates reports in multiple formats:
PDF
HTML
Markdown
CSV
Custom Templates
Advanced Configuration
Severity Mapping
reconFTW maps nuclei severities to Faraday:
critical
Critical
high
High
medium
Medium
low
Low
info
Informational
Custom Fields
Bulk Import
For large scans, results are batched:
Troubleshooting
Connection Issues
Authentication Errors
Missing Data
Check workspace exists
Verify scan completed successfully
Review Faraday logs:
docker logs faraday
Duplicate Entries
Faraday deduplicates by:
Host: IP address
Service: IP + port + protocol
Vulnerability: Name + host + service
Best Practices
Workspace naming: Use consistent naming convention
Token security: Keep API token in secrets.cfg
Regular cleanup: Archive old workspaces
Backup: Export workspaces regularly
Access control: Use Faraday roles for team access
Alternative: Manual Import
If automatic integration fails, import manually:
Next Steps
Deployment Guide - Full setup
Output Interpretation - Understanding results
Last updated