Ethical Hacking

Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package.
Computer Forensics Training at InfoSec Institute

Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors.




Network Security Focus-Microsoft
[Top] [All Lists]

patching servers...

Subject: patching servers...
Date: Tue, 10 Jan 2006 15:06:22 +1000
Hi all,
I wanted to get a few ideas of what people do to test their systems once
they have applied a patch/hotfix.

Currently I pull one of the hotswap drives that has the OS mirrored on it
and then let it run with the patch applied for a few days/week before
letting it rebuild.
In that time I will check things like event logs/performance and do some
general 'listening' for any issues. 
Does anyone have a more scientific method? What do you keep an eye on? Also,
Do you actually ever check whether the vulnerability(for example) that the
patch was designed to thwart has actually been plugged? 
In the last two years I've only had one instance of a patch causing an OS to
fail--and then just removing and then reapplying the patch seemed to work
just fine. However, I don't want to get complacent.

Kind Regards
Murad Talukdar


 



---------------------------------------------------------------------------
---------------------------------------------------------------------------

<Prev in Thread] Current Thread [Next in Thread>