How eisler/automated-scanner works
Based on an analysis of both the file tree and the README, this project is a penetration testing and reconnaissance tool that orchestrates a collection of open-source scanning and enumeration utilities. Its primary purpose is to take a target domain (as provided via command-line arguments to scanner.sh) and then call out to various external tools (using bash scripting) for subdomain enumeration, port scanning, endpoint discovery, and vulnerability assessments such as potential subdomain takeover or XSS scanning. The project is essentially a “glue” script that leverages many well-known tools (like Amass, subfinder, assetfinder, nmap, ffuf, etc.) and some configuration files (in the tools directory) to simplify the pentester’s workflow.
• Tools/Modules: Illustrate each group of scanning tools. Group related functionalities such as:
• Subdomain Enumeration (e.g., Amass, subfinder, assetfinder, goaltdns, massdns)
• HTTP/Host Probing (e.g., httprobe, DNSProbe)
• Subdomain Takeover (e.g., tko-subs, subjack)
• Endpoint and Secret Discovery (e.g., Linkfinder, github-endpoints, github-secrets)
• Port and Service Scanning (nmap, masscan)
• Web Fingerprinting (aquatone, webanalyze)
• File/Directory Discovery (gau, getching)
• Vulnerability Scanning (kxss, dalfox, ffuf)
Underlying configuration data
• Tools Directory: Represent the “tools” folder as a shared resource that contains configuration files, credentials (.creds, .tokens) and datasets (apps.json, fingerprints.json, nameservers.txt, providers-data.csv) used by the scanning tools.
Out the relationships and interactions
• That scanner.sh (entry point) initiates the orchestration flow upon receiving a target domain.
• Moreover, emphasize data pipelines where the output of one tool (e.g., discovered subdomains) feeds into subsequent tools (like HTTP probing, port scanning, or endpoint discovery).
With architectural patterns and design principles
• Modular “plug-and-play” style: each tool represents an independent module that the main scanner script orchestrates in a pipeline.
• Loose coupling between the orchestrator and the third-party tools; any additions or modifications can be made relatively independently, which is ideal for extensibility.
• Point out that configuration and credentials stored in the tools folder further decouple tool-specific settings from the orchestration script—an important design choice facilitating easy updates and modularity.
Final elements
• A clearly marked entry point labeled “scanner.sh: Orchestration Script.”
• Separate blocks for each category of scanning tools (with subsidiary labels listing actual tool names).
• A central or shared “Tools Configuration/Data” block showing where credentials, tokens, and configuration files are kept.
• Optional notes about external dependencies (e.g., the installation of various tools via apt-get, GoLang, PIP, or Git).