I have thought about creating my own rule set based solely on the fact that
from the latest release of updates, over half of the students on campus were
placed in the temporary role from not being up-to-date when in fact they
were (according to windowsupdate.com).  

Anyone interested in sharing their windows xp and windows 2000 rule set or
the way they go about determining the appropriate hotfixes to include in
their rule set for future updates?  I would assume a little research on
Microsoft's website and a comparison to Cisco's rule set is a start.  

-----Original Message-----
From: Perfigo SecureSmart and CleanMachines Discussion List
[mailto:[log in to unmask]] On Behalf Of King, Michael
Sent: Wednesday, October 19, 2005 9:10 AM
To: [log in to unmask]
Subject: Re: Non Cisco Rule Sets

Thanks, I missed that one.

My SOP is to compare my current rule set (which is a copy of Cisco's
rule set) to one that Cisco publishes about a day after Patch Tuesday.)
to see if any thing has disappeared. I also check when I get someone
that can't seem to pass the windows update rule.  I'm under a mandate
from upper management to not have an outside company dictate our policy.
Personally, I'd rather just have then "Live".  But this policy came from
last year when Microsoft Re-issued 5 patches, completely changing the
Reg location, but not the KB id.  It took several hours, and a few calls
to TAC to straighten that out.

> -----Original Message-----
> From: Perfigo SecureSmart and CleanMachines Discussion List 
> [mailto:[log in to unmask]] On Behalf Of Pender, Anne
> 
> 899588 has been replaced by 905749.  But the MS KB article for the
> 899588 doesn't mention that it has been superseded, so it's a 
> little tricky to track down.  (I was searching the KB, but 
> the details for security patches aren't kept in the KB, 
> they're just linked out to the technet security site...)