As at Open-AudIT 2.3.2 and later, we have introduced some easy to use but extremely powerful options for discovering devices.
These options centre around directing Nmap on how to discover devices.
We have grouped these options into what we're calling Discovery Scan Options. We ship seven different groups of options (items) by default that should cover the common use-cases.
This benefits Community, Professional and Enterprise customers.
Feature use is dependent on license type, and is detailed below.
|Match Rules - set default for all discoveries||y||y||y|
|Discovery Scan Options - set default for all discoveries||y||y||y|
|Discovery Scan Options - read||y||y|
|Discovery Scan Options - set per discovery||y||y|
|Discovery Scan Options - create, read, update, delete||y|
|Discovery Scan Options - Custom per Discovery||y|
|Discovery Scan Options - Exclude IP, range, subnet per discovery||y|
|Discovery Scan Options - Exclude ports per discovery||y|
|Discovery Scan Options - Set device timeout, per discovery||y|
|Discovery Scan Options - Custom SSH port per discovery||y|
|Match Rules - set per discovery||y|
The Discovery Scan Options we ship are detailed below. As above, Enterprise users can create more of these or edit the shipped items.
|Approximate time in seconds for remote IP scan||1||5||40||90||100||240||1200|
|Must Respond to Ping||y||y||y||n||y||y||n|
|Use Service Version Detection||n||n||n||n||n||y||y|
|Consider Filtered Ports as Open||n||n||n||y||n||y||y|
|Top Nmap TCP Ports||10||100||1000||1000||1000||1000|
|Top Nmap UDP Ports||10||100||100||100||1000|
|Custom TCP Ports||22,135,62078||62078||62078||62078||62078||62078||62078|
|Custom UDP Ports||161||161|
|Exclude TCP Ports|
|Exclude UDP Ports|
|Timeout per Host|
|Exclude IP (address, range, subnet)|
|Custom SSH Port|
The item for Medium (Classic) is as close as we can make these options to how (prior to 2.3.2) Open-AudIT used Nmap for Discovery.
We have a customer who is running discovery on a /22. The scan time to complete when using the original (hard set) options, prior to 2,3.2 was 29 hours. Using 2.3.2's UltraFast option, that scan now takes less than 10 minutes. Obviously they are sacrificing some detail regarding Nmap ports, but as that is not an issue in this case, to say they are impressed would be an understatement! And don't forget, if the audited device is a computer, you will have a list of open ports derived from Netstat, anyway.
Recently we had cause to scan a subnet that was made up of virtual Cisco networking devices. These devices all happened to have identical serial numbers. Using the Match Rules per Discovery (available to Enterprise users) we were able to tweak the ruleset for this discovery only, without affecting other discoveries that rely upon matching a serial number. This ability solved a long standing issue of working around a less than ideal setup on a network. A serial number, by definition, should be unique.
Networks respond differently depending on how they're configured. Some routers and/or firewalls can respond "on behalf" of IPs on the other side of their interfaces to the Open-AudIT Server. It is quite common to see Nmap report a probe for SNMP (UDP port 161) to respond as open|filtered for devices the do and do not exist. This has cause Open-AudIT users some confusion in the past. They know there is no device at that IP, yet they end up with a device entry in the database. 99.9% of the time, it is not Open-AudIT, nor even Nmap, but the network causing this issue. Now that we have the options to treat open|filtered ports as either open or closed, we can eliminate a lot of this confusion. Enterprise users even have the option to change this on a per discovery basis (more than just using the Medium (Classic) item, as above).
This new functionality, I believe, makes Open-AudIT one of the easiest to use Nmap Frontends available while at the same time provides a great amount of flexibility for advanced users.
I hope you find it as useful as I do.