Re: Audit trail tools or ideas

From: H C (keydet89@yahoo.com)
Date: 09/26/01 

Message-ID: <20010926214811.17227.qmail@web20508.mail.yahoo.com>
Date: Wed, 26 Sep 2001 14:48:11 -0700 (PDT)
From: H C <keydet89@yahoo.com>
Subject: Re: Audit trail tools or ideas
To: shewitt@cdw.com, focus-ms@securityfocus.com

Most organizations I've seen that track such things
take a slightly different approach, in that they plan
for such things. For example, when upgrading to SP6a,
they had a plan in place for updating and verifying
all of their machines, and they did just that.

Of course, you can use Perl scripts to retrieve the
necessary information for you. SP and hotfixes can be
pulled from the Registry and DLL, EXE, and SYS file
versions can be retrieved easily, as with finfo.pl on
http://patriot.net/~carvdawg/perl.html.

--- shewitt@cdw.com wrote:
> I'm curious to find out what people are using for an
> audit trail when making
> changes on servers.
>
> I have a server farm with several servers and I find
> it difficult to keep
> track of what patches I've applied on what machines
> and when I applied them.
> I've been using a spread*** to keep track of it,
> but I'm curious to find
> out what other people use and how well it works for
> them.
>
> Does anybody know of any programs that help with
> this problem? This would
> be helpful for managing all machines, not just web
> servers.
>
>
>
> --------------------------
> Scott Hewitt
> WEB/WAN Administrator
> CDW Computer Centers, Inc.
> shewitt@cdw.com

__________________________________________________
Do You Yahoo!?
Get email alerts & NEW webcam video instant messaging with Yahoo! Messenger. http://im.yahoo.com

Quantcast