Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 640
  • Last Modified:

Can registry exceptions be made within Forefront Client Security?

Greetings -

I use Group Policy Preferences extensively in my environment and Forefront Client Security is noticing when I write values to the "Run" keys in the registry and logging entries for these changes in the System Event Log.  This is flooding the logs given that Group Policy is updating every 60 minutes in my environment.

Is anyone aware of a way to authorize certain registry values to be written and ignored?  I can't find any way to do this in policy.  I can exclude files and folders but not registry keys.

Ideas?
0
amendala
Asked:
amendala
  • 2
1 Solution
 
ForrorCommented:
*.reg  does not work?  Just curious myself, or possibly filter by REG_SZ or REG_DWORD to exclude those?

Just throwing suggestions.
0
 
ForrorCommented:
Do not log events for files marked "Unknown"
 AM\Reporting\

DisableLoggingForUnknown
 On (1)

Off (0)
 R, S, C
 
Might help if the log events are being marked Unknown, not sure what errors or log message you were getting.
0
 
amendalaAuthor Commented:
This is the solution I implemented, though I found that there's a check box in the policy for this as well.  Thanks!  It works.
0

Featured Post

The Lifecycle Approach to Managing Security Policy

Managing application connectivity and security policies can be achieved more effectively when following a framework that automates repeatable processes and ensures that the right activities are performed in the right order.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now