The point is valid. I would not try to harden 10K machines let alone 100 by hand, however, if there is a mandate to fix this many systems one can build a hardened system use COTS tools to check the system vulnerabilities and then build an image file of the system partition and use this as a basis for a reasonably secure underlying OS that has been hardened. You can use this as the blueprint and use Ghost or another tool to roll out the underlying image file for the boot partition. [EMAIL PROTECTED] wrote: > TO UNSUBSCRIBE: email "unsubscribe issforum" in the body of your message to > [EMAIL PROTECTED] Contact [EMAIL PROTECTED] for help with any problems! > ---------------------------------------------------------------------------- > > Missing the point, most IT people don't want to cobble things together by > hand anymore.. They want an automated to do their job for them. If one > were to download the SANS NT Hardening Guide.. OK, that is fine and dandy > for one or two machines that someone can do by hand, but try like deploying > 10,000 machines at once. The SANS guide was designed for scaleability. > > /mark -- Paul Osterwald Sr. Security Engineer Intrusion.com 3940 Ruffin Road San Diego, CA 92123 (858) 268-1236 x2232 (Office) (619) 865-2775 (Cell) (858) 268-7755 (Fax) http://www.intrusion.com mailto:[EMAIL PROTECTED]
begin:vcard n:Osterwald;Paul tel;cell:619-865-2775 tel;fax:858-268-7755 tel;home:760-724-0446 tel;work:858-268-1236 x2232 x-mozilla-html:TRUE url:http://www.intrusion.com org:Intrusion.com;Security Engineering adr:;;3940 Ruffin Road;San Diego;California;92123;USA version:2.1 email;internet:[EMAIL PROTECTED] title:Sr. Security Engineer fn:Paul Osterwald end:vcard
