Unfortunatley, it appears the CSA documentation is quite vague. I'd guess it'd be something similar ...

well, i'm still new to security, so I don't know how safe something is or not, but as long as you ca...

ok, my concerns are laid to rest then.I created the COM access rule, and that actually solves my pro...

To prevent Windows 2003 file system files from being erased or modified, CSA has already built in Fi...

ok, I think I may try this, but one question (this goes for all readers)...Let's just say I deny acc...

I guess I was thinking that someone could attack as IEXPLORE.EXE and gain access to read someone's p...

I've cloned the rule, but at it's base, it's a File Access Control rule in the Document Security Mod...

yes, but therein lies the problem...If I set the rule to Allow, it's opening a huge security hole (I...

Have you tried un-installing the Agent on the host computer and deleting the host in the MC? Then, y...

Actually, as I was thinking about this, I realized this probably shouldn't be done through CSA, sinc...

the problem is that I can't locate a way to isolate the behavior in CSA. I can't really set a CSA re...

Thanks for the response. We're trying to limit our end user's interaction with the Agent, so I'll ke...

I posted a message about this before, but the nature of my problem has changed a bit...Whenever a us...

well, the registry key the event refers to basically adds to the "Open With" list for that extension...

I'm not sure how much I can help, but we implemented in 5.0 so that only admins can turn the Agent "...