Thanks for the updated rule idea. I tried it with the syntax you provided, but could not get it to work that way. It would fail to compile. I used an Include -processor_mode "kernel", and that seemed to compile, but would not fire on an admin account. Even though when you use an admin account to launch iexplore.exe, it is still considered user mode and not kernel. I switched it from "kernel" to "user" and it fired off on it as it was indeed in usermode.
Perhaps there is another way.
This is the correct usage. Here is some example Expert Rule (modified from the ENS Product Guide PD27227, page 32) that I had previously tested successfully.
Rule { Process { Include OBJECT_NAME { -v cmd.exe } Exclude EXP_USER_NAME { -v {domain\administrator} } } Target { Match FILE { Include OBJECT_NAME { -v "c:\\temp\\*test.txt" } Include -access "CREATE" } } }
For other usernames (with spaces for example), I tested using quotes vs brackets for usernames with spaces, and the brackets worked for me.
Didn't work:
Include EXP_USER_NAME { -v "NT AUTHORITY\SYSTEM"
Worked:
Include EXP_USER_NAME { -v {NT AUTHORITY\SYSTEM}
New to the forums or need help finding your way around the forums? There's a whole hub of community resources to help you.
Thousands of customers use our Community for peer-to-peer and expert product support. Enjoy these benefits with a free membership: