ISS Server Sensor and System Scanner are really one install, the System Scanner binaries are included in the Server Sensor install. The difference is that to get all of the functionality of System Scanner a license key to enable all of the functionality must be purchased.
Case A: You get ease of use, one management console and possibly a reduced price for a volume purchase and more fuctionality than Case B. Case B: Your console management is a little more problematic but you get vendor distributed protection, your not relying solely on one vendor or its products possible vulnerabilities to protect your network as you would be in Case A. There are good and bad points with both, I would determine the clients specific criteria (ease of use, price, whatever it may be)and wants and offer the solution that offers the best security based on the criteria they provide. >>>>>>>> >>>>Hello list, this is my first question to the list, so please be gentle. One of my customers want's to improve security in his DMZ. He needs vulnerability scanning, integritiy checking and intrusion detection. For network based vulnerability scanning he uses a combination of free software (nessus) and a comercial solution. But he's looking for hostbased vulnerability scanning too. Environement: Mix of Windows and Unix servers I've found the following combinations: Case A: ISS System Scanner (Does scanning and integrity checking as far as I know) ISS Real Secure Server Sensor (for intrusion detection) could be handled from a single console Case B: Tripwire (integrity checking) ISS Real Secure Server Sensor (for intrusion detection, and, as for informations from ISS, does vulnerability scanning in a future version) needs 2 consoles >>>>>>>>>> _________________________________________________________________ Chat with friends online, try MSN Messenger: http://messenger.msn.com
