TO UNSUBSCRIBE: email "unsubscribe issforum" in the body of your message to [EMAIL PROTECTED] Contact [EMAIL PROTECTED] for help with any problems! ---------------------------------------------------------------------------- I am working on a large implementation of RealSecure, System Scanner, Internet Scanner and SafeSuite Decision(SSD) and I wanted to throw an idea out to be picked apart. My goal is to limit the number of consoles necessary to manage RealSecure and System Scanner. Currently we are looking at over 10 consoles which, IMHO, is to many. I understand that the limitations in console to agent/sensor ratios are primarily due to database size (current implementations use Access and have a 1GB size limitation), human factor (monitoring a RealSecure console with 100+ sensors may be overwhelming), and logistic issues with managing a high number of devices (system scanner communicating with a large number simultaneously would cause an overload). If there are more I would love to hear about them. The basic design would be to use the consoles as management tools and temporary data storage. Meaning that SSD will pull in the data from each console on a periodic basis and then each console will purge the database (procedures are being looked into). With other limitations like system scanner will run scans on a staggered basis and all RealSecure sensors will use SNMP to send realtime alerts (so no consoles in NOC) it would seem like it could work. I would especially like to hear from those groups currently using SafeSuite Decision. Thanks for any help that might be given and I will post an update as the project goes forward along with a consolidated piece from this thread. Danny ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Danny Walker, CISSP, CISA, SSCP <[EMAIL PROTECTED]> Senior Network Security Engineer Icons, Inc. <http://www.iconsinc.com>
