Active Directory Monitoring, Reporting & Auditing
How to Audit Active Directory for CIS / NIST Cyber Security Audit

Active Directory (AD) is the backbone of identity and access in most organizations. It is also one of the biggest targets for attackers. Weak or poorly monitored AD environments often lead to breaches, privilege escalation, and compliance failures. That’s why regular AD auditing is critical for maintaining security, detecting suspicious behavior, and aligning with cyber security frameworks such as CIS Controls and NIST CSF.

In this article, we’ll explore how to audit Active Directory effectively. You’ll learn which Windows Event IDs to track, how to use Event Viewer and PowerShell automation, and how to map your monitoring strategy directly to compliance requirements.

Audit Active Directory for Security & CIS / NIST Compliance

Why Auditing Active Directory Matters

Active Directory stores user accounts, group memberships, and authentication details. When attackers compromise AD, they can escalate privileges, create backdoor accounts, and disable logging to cover their tracks. Without proper auditing, these activities can go undetected for weeks or months.

Auditing provides:

  • Visibility into authentication attempts, user and admin changes, and account lockouts.

  • Compliance alignment with CIS and NIST requirements for access control and monitoring.

  • Incident detection by correlating suspicious logons, privilege escalations, or mass account changes.

Video: How to Audit Active Directory for CIS / NIST Cyber Security Audit using Windows Event Viewer

Key Windows Event IDs to Monitor for CIS / NIST

Windows logs a huge number of events, but certain Event IDs are especially important for security auditing.

Event IDDescriptionWhy It MattersFramework Alignment
4624Successful LogonEstablishes baseline authentication activity.NIST PR.AC-1 (credential use), CIS Control 6 (log monitoring)
4625Failed Logon AttemptDetects brute force and password spraying.NIST DE.CM-3 (unauthorized access detection), CIS Control 6
4672Admin Logon with Special PrivilegesTracks privileged access usage.NIST PR.AC-4 (privilege management), CIS Control 4 (admin privileges)
4720User Account CreatedDetects unauthorized/shadow accounts.NIST PR.AC-1, CIS Control 4
4726User Account DeletedMonitors suspicious account cleanup.NIST PR.AC-1, CIS Control 4
4728 / 4729Added/Removed from Domain Admin GroupDetects privilege escalation attempts.NIST PR.AC-4, CIS Control 4
4740User Account Locked OutCorrelates with failed login attempts (possible attack).NIST DE.CM-1 (monitoring), CIS Control 6
4722 / 4725Account Enabled/DisabledTracks dormant account re-activation.NIST PR.AC-1, CIS Control 4
4732 / 4733Added/Removed from a Local Domain GroupDetects changes in access scope.NIST PR.AC-4, CIS Control 4
4738User Account ChangedTracks credential or attribute changes.NIST PR.AC-1, CIS Control 4
5136 / 5137Directory Object Modified/CreatedMonitors group, OU, or object changes.NIST CM-5 (change monitoring), CIS Control 5
1102Audit Log ClearedIndicates possible attacker tampering.NIST DE.CM-1, CIS Control 6

Monitoring these events provides early indicators of compromise and allows IT teams to respond before attackers escalate further.

Using Windows Event Viewer

Event Viewer is the built-in tool to inspect security logs. By filtering for specific Event IDs, admins can:

  • Identify failed logon storms (4625)

  • Spot privilege use (4672)

  • Detect mass account lockouts (4740)

However, Event Viewer alone is limited. Manually searching logs is time-consuming and doesn’t scale across multiple domain controllers.

Active Directory auditing using Event Viewer
Event Viewer on a Domain Controller

Automating Auditing & Alerting with PowerShell

PowerShell makes Active Directory auditing more efficient. With the InfraSOS Active Directory Auditing PowerShell script, you can:

  • Collect security logs across multiple domain controllers.

  • Export results into CSV reports for analysis.

  • Automate log parsing for specific Event IDs.

  • Add email alerts for critical AD changes.

This automation ensures you don’t miss important security events and reduces the manual burden on IT teams.

Correlating Events with CIS & NIST Frameworks

Auditing is not just about detection, it is also about compliance. Many of the Event IDs above map directly to CIS Controls and NIST Cyber Security Framework categories.

  • CIS Controls:

    • Control 4: Controlled Use of Administrative Privileges

    • Control 5: Secure Configuration

    • Control 6: Maintenance, Monitoring, and Analysis of Logs

    • Control 8: Malware Defenses

  • NIST CSF:

    • PR.AC-1: Identities and credentials are managed

    • PR.AC-4: Access permissions are managed

    • DE.CM-1: The network is monitored for events

    • DE.CM-3: Detecting unauthorized access

    • CM-5: Monitoring configuration changes

By aligning your AD log monitoring with these standards, you not only detect threats but also demonstrate compliance during audits.

Investigating Account Lockouts

Account lockouts (Event ID 4740) are common in AD environments. They can be caused by simple user errors, but they may also indicate brute force attacks or malicious activity.

With proper auditing, you can:

  • Trace the source of lockouts.

  • Correlate repeated failed logons (4625) with lockouts (4740).

  • Distinguish between accidental lockouts and targeted attacks.

Video: Find Active Directory Account Lockout Sources & Trace Event ID 4740 & Prevent Common AD Lockouts

Scaling with Windows Event Forwarding

For enterprises with multiple domain controllers, Windows Event Forwarding (WEF) simplifies log collection. It consolidates events from across the environment into a central system, reducing the risk of missing critical events. Combined with PowerShell automation, this provides a scalable AD monitoring strategy.

Conclusion

Auditing Active Directory is essential for both security and compliance. By monitoring the right Event IDs, leveraging Event Viewer, and automating with PowerShell, organizations can:

  • Detect suspicious activity early

  • Investigate incidents quickly

  • Align with CIS and NIST frameworks

At InfraSOS, we help organizations take AD security further by delivering automated reporting, alerting, and compliance mapping across hybrid environments.

👉 Start auditing your Active Directory today before attackers exploit what you can’t see. Learn more about InfraSOS Active Directory reporting platform.

Picture of Andrew Fitzgerald

Andrew Fitzgerald

Cloud Solution Architect. Helping customers transform their IT Infrastructure, Cloud deployments and Security. 20 years experience working in complex infrastructure environments and a Microsoft Certified Solutions Expert on everything Cloud and Active Directory.