|
|||||||||||
|
RE: Distributed Vulnerability Scanners
From: Rapaille Max <Max.Rapaille(at)nbb.be>
Date: Fri Mar 07 2003 - 02:29:58 EST
Regards, Max
-----Original Message-----
I've heard a couple people mention scanning services that offer appliances that you can bring in house, but do those actually run in a distributed fashion? For this case, here's the definition I'd use for distributed: from a single console, I am able to set up a scan across a block of IP addresses, those addresses are then automatically split up according to some rules (by subnet or whatever) and sent out to scanning systems that are responsible for scanning those groups of IPs. They run the scans and send the results back to the central server. The central server should also be able to push test updates down to the scanning systems. Maybe in an ideal world the scan jobs would have an approval path that would check with the owner of the network/environment about to be scanned before executing it. Or at least give them a day or two to object before running the scan. It's easy to set up a single box that is remotely managed and does all the scanning for an environment, but that doesn't work so well when some of your networks are at the other end of slow or expensive links. toby Are your vulnerability scans producing just another report? Manage the entire remediation process with StillSecure VAM's Vulnerability Repair Workflow. Download a free 15-day trial: http://www2.stillsecure.com/download/sf_vuln_list.html
Are your vulnerability scans producing just another report?
Manage the entire remediation process with StillSecure VAM's
Vulnerability Repair Workflow.
This archive was generated by hypermail 2.1.8 : Wed Aug 23 2006 - 14:02:33 EDT |
||||||||||
|
|||||||||||