RE: Scanning - anyone got ball park timings?

Rule of thumb for security testing enumeration-- straight out of OSSTMM 2.5 RED-- (warning - this is a RULE OF THUMB which means your mileage may vary but it's pretty accurate to start planning or baseline)

Based on blackbox enumeration and port scanning (ICMP all request types, TCP/UDP 64k ports, various protocol application and network level types based on ICMP response ACLs, and various enumeration techniques as outlined in the OSSTMM). This should be about equivalent with running a vuln scanner like ISS with "Scan if Ping Fails" option running.

48 hours for each /24 at 12 hops of 64Kb bandwidth. Add 1 hour per /24 for every hop greater than 12. For less than 12 hops consider flood control timing to balance rule or else calculations are unreliable. Divide by (digital and upstream/downstream balance) bandwidth because increasing bandwidth decreases time proportionally where smallest bandwidth is maximum calculated size.

Example:

Scanning 3 /24 networks at 18 hops with a 256Kb line

Now assuming my math isn't hindered by lack of sleep: 48 hours per /24 = 144 hours
add 1 hour per hop per /24 over 12 hops = 144 + 6 * 3 = 162 divide for bandwidth = /(256 / 64) = /4
total = 162 / 4 = 40.5 hours

Less than 2 days for enumerating 3 /24s is about right. Anyways, it works pretty well for me.

Do you need help?

In addition to our free technical library, Pantek provides professional IT services to companies who utilize Open Source software: Learn more about Pantek's Technical Support offerings Place an order for 24/7/365 Technical Support here Learn more about Pantek, who we are, and what we do Chat with a Live Operator Related securityfocus.com Links bugtraq certification focus-bsd focus-ids focus-ih focus-linux focus-ms focus-sun focus-unix-other focus-virus forensics incidents libnet linux-secnews ms-secnews pen-test secpapers secprog sectools secureshell security-basics securityjobs sf-news vuln-dev webappsec Request more information about Pantek

If 16 hours for vuln scans seems long for you then I recommend you take shortcuts and enumerate once and make an IP list of systems and commonly found ports to feed into the scanner. Actually, it sounds more like an internal scan - or just a router or three away from you. Even then, a good firewall will slow a scan down considerably.

You just need to feed me more info for more accuracy.

Sincerely,
-pete.

> -----Original Message-----