Implement a Filesystem Watcher or Database to look at (configurable), so the Scans can kick off independently from the current running processes.
This could help to decouple the static calls of "StartPortScanner" and "StartServiceScanner" in the main method. Further it could help to decouple the Docker Containers into specific workload defined containers like
NMap Containers
Nikito Containers
Whatweb Containers
Dirbuster Containers
...
A short workflow example:
User creates a new target config file (/results/targets/10.10.10.10.yaml)
Port Scanners pickup the new target and start spinning up independently
Port Scanners write a service report (/results/10.10.10.10/services.txt)
Service scanners picking up the report and individually check if they have any todos
Further Enumeration happens....
This could be switched up with database adapters too.
Implement a Filesystem Watcher or Database to look at (configurable), so the Scans can kick off independently from the current running processes.
This could help to decouple the static calls of "StartPortScanner" and "StartServiceScanner" in the main method. Further it could help to decouple the Docker Containers into specific workload defined containers like
A short workflow example:
This could be switched up with database adapters too.