I was recently doing an external penetration test that involved very stealthy and progressive enumeration scans on a block of 24 IP addresses. I disabled the scheduler scans on this engagement in favor of manually launching a series of custom nmap scans of increasing speed and scope. The issue that I ran into is I had to launch the scans individually for each host as opposed to firing off each scan on the entire range. Some suggestions to combat this could be:
Allow selection and scanning of multiple hosts in the main hosts tab
Ability to launch scans on a custom range outside of the hosts tab (a-la Zenmap)
Once the scans were completed and all the host enumeration was done, using Sparta on the detected services was very nice. Great tool, guys!
Hi Matthew! Thanks for the suggestion. We are brainstorming this internally and figuring out the best way to solve this common problem. It IS a pain to launch scans individually on each host.
I was recently doing an external penetration test that involved very stealthy and progressive enumeration scans on a block of 24 IP addresses. I disabled the scheduler scans on this engagement in favor of manually launching a series of custom nmap scans of increasing speed and scope. The issue that I ran into is I had to launch the scans individually for each host as opposed to firing off each scan on the entire range. Some suggestions to combat this could be:
Once the scans were completed and all the host enumeration was done, using Sparta on the detected services was very nice. Great tool, guys!