Originally MyNmap wasn’t intended to act as a tool to automate scans. The real goal was to get the grid display with highlighting of what is new. Looking at tons of Nmap scans makes my head spin, and digesting that information to determine what is new is best left to a computer.
Because of this, you don’t necessarily need to use the scheduling interface to get your nmap scans into MyNmap, furthermore if you have two scans and want to compare differences between the two–you can load them in succession and be able to analyze the differences.
It is quite easy, when you run your scans use the “nmap -oX” flag. Then copy the XML file into the “/usr/local/mynmap/scans” directory with the file extension “new.xml“. If you don’t have the “new.xml” at the end of the filename MyNmap will ignore the file (this is to stop it from trying to process files that haven’t been completely written while a scan is in process, sure I could have used another directory for that, but I didn’t.)
I use this at work so that I can visualize scan data from external networks, using cron, a shell script, and SSH allows me to use an external machine to keep an ongoing view of what is in our public accessible network space.
I also use a script that allows me to alert on when new things appear in the DMZ based upon scan results–I will post how that works here soon.
Sorry, the comment form is closed at this time.