Subscribe to Windows IT Pro

 

Get Newsletters

  • Get the Latest News
  • Product Updates
  • Helpful Tricks
  • Productivity Tips

Subscribe Now!

June 21, 2004 12:00 AM

Access Denied: Letting Users View Security Logs

Windows IT Pro
InstantDoc ID #42811
Rating: (2)

I want to let a group of users who aren't members of Enterprise Admins or Domain Admins view the Security logs of all domain controllers (DCs) in a forest. What user rights do I need to apply?

To view the Security log, users must have the Manage auditing and security log user right on each computer whose log they want to view. To grant this right on all your DCs, open the Microsoft Management Console (MMC) Active Directory Users and Computers snap-in. Create a global group, give it an appropriate name, such as DCSecurityLogViewers, and populate the group with the users who need access to the Security log. Then, simply edit the Default Domain Controllers Policy Group Policy Object (GPO), which is linked to the Domain Controllers organizational unit (OU). To edit this GPO, go to Computer Configuration\Windows Settings\Security Settings\Local Policies\ User rights assignment and assign the Manage auditing and security log right to the DCSecurityLogViewers group. Everyone in the DCSecurityLogViewers group will be able to view the Security log of each DC in the current domain. To grant DCSecurityLogViewers the same access on the DCs in other domains, make the same change to the Default Domain Controllers Policy GPO in each domain.

Be aware that this user right also lets users clear the Security log. You can't give someone the ability to view the Security log without giving them the authority to clear it as well. And you can't restrict administrators from viewing or clearing the Security log—although you can deny administrators the Manage auditing and security log user right, they can grant the right to themselves. If you don't want your users to be able to clear the Security log or to be able to grant the Manage auditing and security log user right to themselves, you must set up a process that frequently exports each computer's Security log to a central database, to which you can then control access as you see fit.

Related Content:

ARTICLE TOOLS

Comments
  • jpmillerx77
    10 months ago
    Apr 28, 2011

    this article is obsolete as of windows 2003 server. if your still running windows 2000 its correct, otherwise its just misleading and should be removed or updated

You must log on before posting a comment.

Are you a new visitor? Register Here

advertisement

advertisement

White Papers

Get your Windows 7 deployment off to the right start by implementing PC lockdown. A locked-down environment is easier and cheaper to support since users are less likely to make unnecessary changes to the core system configuration - read more here!

Essential Guides

Is your iSCSI "lossy"? The reality is that most off-the-shelf Ethernet hardware deployed for iSCSI can lose packets, resulting in slow performance or application downtime. Learn how to assess your current iSCSI infrastructure and engineer an advanced iSCSI SAN infrastructure.

Web Seminars

What's the best way to keep your network safe from malware? In this web seminar, security expert Greg Shields suggests an alternative method to the traditional blacklisting approach that is common with anti-virus and anti-malware solutions.

eLearning Series

We bring the experts direct to you to share their real-world perspective and expertise. During each event, three sessions stream in real time, so you can learn, ask questions, and get solutions.
Upcoming event: Getting the Most with Exchange 2010 with Paul Robichaux

Subscribe to Windows IT Pro!

Windows is a trademark of the Microsoft group of companies. Windows IT Pro is used by Penton Media Inc. under license from owner.