recon-pipeline

recon-pipeline was designed to chain together multiple security tools as part of a Flow-Based Programming paradigm. Each component is part of a network of “black box” processes. These components exchange data between each other and can be reconnected in different ways to form different applications without any internal changes.

Getting Started

There are an accompanying set of blog posts detailing the development process and underpinnings of the pipeline. Feel free to check them out if you’re so inclined, but they’re in no way required reading to use the tool.

• Installation Instructions - How to install recon-pipeline and associated dependencies
• Defining Target Scope - How to define the scope of your scans (list of targets and a blacklist)
• Running Scans - Example scan of tesla.com using recon-pipeline
• Viewing Scan Results - How to view scan results
• Using a Scheduler - The Luigi schedulers and which to choose
• Visualizing Tasks - How to check on active tasks once they’re running

Personalization

• How to personalize the pipeline

API Reference

• Commands
  • tools
  • database
  • scan
  • status
  • view
• Database Manager
• Database Models
  • Target Model
  • Endpoint Model
  • Header Model
  • IP Address Model
  • Nmap Model
  • Nmap Scripting Engine Model
  • Port Model
  • Screenshot Model
  • Searchsploit Model
  • Technology Model
• Parsers
  • Amass Parser
  • Web Targets Parser
  • Masscan Parser
• Scanners
  • Amass Scanner
  • Aquatone Scanner
  • Full Scanner
  • Gobuster Scanner
  • Hackthebox Scanner
  • Masscan Scanner
  • Searchsploit Scanner
  • Subjack Scanner
  • ThreadedNmap Scanner
  • TKOSubs Scanner
  • WaybackurlsScan Scanner
  • Webanalyze Scanner

Indices and tables

• Index
• Search Page