Yes, it is a Windows XP SP2 machine. I thought that it was weird too but i dont have much experience with the root-kit proctection module either.

Thanks,

I have seen this quite often and seems legit. Here is the details on the service.

http://www.microsoft.com/downloads/details.aspx?FamilyId=1B286E6D-8912-4E18-B570-42470E2F3582&displaylang=en

Just add it to your Kernel Protection Set-Rootkit-Trusted rule with the hash **\*\uphcleanhlp.sys at the simplest level.

what is the best way to add this to the Kernal Protection Set Root-Kit-Trusted rule?

I do not like to modify the rules that cisco provides because it makes upgrading challenging.

I originally created a new Rule Module for this root-kit exception but it does not show up for me to use. I can only use previous rule modules or the default one "Operating System - Base Protection - Windows V 5.2.r203'

You should just be able to add a new kernel protection rule to the module you have then.

It is just a kernel protetion rule you need to add. Options are SET, ROOTKIT, TRUSTED and in the Modules modify Kernel Functionality" add the hash to the "Included module hashes:" section.

Do this manually and do not use the wizard.

within the kernel protection rule I do not see Options SET, ROOKIT or Trusted, but I do see Kernel Functionality and such.

Any additional help would be appreciated.

Thanks

It's the drop down for Take Action.

Bradley thanks for the screen shot. I will monitor this rule and see where it gets me but I appreciate your efforts.

when I click on the "system state" caption under the rule in my event logs i get the message pop up. What does this mean and how do I fix?

The rule that generated this event only triggers under the system state "rootkit=untrusted".

It is just saying that you need to look at the system states as that rule is only enforced for a certain system state. With the rootkit module a system is placed in that state after it fires the rootkit rule. By using the rule I put up previously it will not be tagged as a rootkit untrusted and therefore the rule module for rootkit detected will not be enforced.

After you put the rule in you will want to reset the agent on the system that had the rootkit. And you can log the new rule to make sure it is working correctly.