Subscribe to Windows IT Pro

 

Get Newsletters

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

Subscribe Now!

May 22, 2008 12:00 AM

Controlling Access to the Windows Security Event Log

Windows IT Pro
InstantDoc ID #98526
Rating: (6)

Q: How can I control who has access to a system’s Security event log? Does Microsoft provide a way to give a user (e.g., a member of our Help desk team) access to a system’s Security event log? I want to avoid giving all the users that require Security event log access an administrator-level account.

A: Microsoft included a mechanism to control Security event log access in Windows Server 2003 without giving users administrator-level access. This mechanism leverages a Reg_SZ value called CustomSD that must be added to the HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Eventlog\Security registry location. The CustomSD value contains a security descriptor that controls who gets what level of access (i.e., read, write, or clear access) to the Security event log. The security descriptor in CustomSD must be specified in the Security Descriptor Definition Language (SDDL) format. SDDL is a special (and complex) language that describes object permissions. The following is an example of an SDDL string that you can embed in CustomSD:

O:BAG:SYD:(D;; 0xf0007;;;AN) 
(A;; 0x7;;;SO)(A;; 0x3;;;IU)

This string denies anonymous users read, write, and clear access to the Security event log (D;; 0xf0007;;;AN); grants server operators read, write, and clear access (A;; 0x7;;;SO); and grants interactive users read and write access (A;; 0x3;;;IU). For a complete description of the SDDL syntax, see the Microsoft article “Security Descriptor Definition Language” at http://go.microsoft.com/fwlink/?LinkId=100970.

To centrally enforce the customer security descriptor contained in CustomSD on Windows 2003 machines that are part of a Windows Active Directory (AD) domain environment, you can use Group Policy Object (GPO) settings. To find out how to leverage GPO settings for this purpose, go to http://support.microsoft.com/kb/323076.

If you edit CustomSD, its new value will take effect only after a system restart. CustomSD is available only in Windows 2003. You can also use CustomSD to fine-tune access to any of the other Windows event logs (e.g., Application, System).

Related Content:

ARTICLE TOOLS

Comments
  • Alexandre
    4 years ago
    May 23, 2008

    Ok, eu gostei.

  • Alexandre
    4 years ago
    May 23, 2008

    ok

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.