scantron v1.31 releases: A distributed nmap scanning framework
Scantron is a distributed nmap scanner comprised of two components. The first is a master node that consists of a web front end used for scheduling scans and storing nmap scan targets and results. The second component is an agent that pulls scan jobs from the master and conducts the actual nmap scanning. A majority of the application’s logic is purposely placed on the master to make the agent(s) as “dumb” as possible. All nmap target files and nmap results reside on master and are shared through a network file share (NFS) leveraging SSH tunnels. The agents call back to master periodically using a REST API to check for scan tasks and provide scan status updates.
Scantron is coded for Python3.6+ exclusively and leverages Django for the web front-end, Django REST Framework as the API endpoint, PostgreSQL as the database, and comes complete with Ubuntu-focused Ansible playbooks for smooth deployments. Scantron has been tested on Ubuntu 18.04 and may be compatible with other operating systems. Scantron’s inspiration comes from:
Scantron relies heavily on utilizing SSH port forwards (-R / -L) as an umbilical cord to the agents. Either an SSH connection from master –> agent or agent –> master is acceptable and may be required depending on different firewall rules, but tweaking the port forwards and autossh commands will be necessary.
Massive overhaul of
agent.py. Consolidated all agent-related Python files into a single
agent.py file to:
- Utilize native Python libraries and not depend on third party or custom libraries (like
- Be a single file so it can be easily moved, downloaded, or transferred between systems.
number_of_threadsfrom 1 to 8.
agent_config.jsonto allow agent’s to advertise what scan capabilities they have. This is an inert functionality right now, but will hopefully allow Master to provide dynamic scanning templates based on what scan binaries an agent can support.
- Added version to
agent.pyto start tracking when
- Added capability to cancel and pause
masscanscans from Master. No need to kill the process manually on the agents. Currently, the scan status state must be updated in the
/scantron-admin/django_scantron/scheduledscan/endpoint, which is not ideal, because that endpoint should not be interfaced with.
master/scan_results/cancelleddirectory to hold cancelled scan files in the event they are needed at a future time
- Started tracking process ID of
- Added some updates to processing logic in
Copyright 2012-2013 Rackspace, Inc.