How to audit Windows events by ID in the Active Directory Real Time Audits?
I want to be alerted when certain events appear in the logs of my domain controllers: locked-out accounts, security log cleared, members added to a sensitive group...
Can I monitor one or more Windows event IDs with IDEAL Administration?
Starting with version 27.0, the Real Time Audits include a Windows events category: each audit counts the events of one or more IDs over a time window and can raise an alert (on screen, by email, in the event log).
Create an event audit
- In the Active Directory Network tab, open the Real Time Audits sub-tab.
- Click Action > Configure.
- In the Configure Audits window, choose Action > Add a Windows event audit...
- Choose a Template (optional) or fill in the fields:
- Audit name;
- Log: Security, System, Application, Directory Service, DNS Server...;
- Time window (minutes): the period over which events are counted (from 1 minute to 7 days);
- Event IDs: one or more IDs separated by commas, for example 4625, 4771;
- Source (optional), for example Microsoft-Windows-Security-Auditing;
- Counting: total events, per account (most targeted account), per origin (most active computer or IP address), or number of different accounts targeted from the same origin;
- Excluded accounts: separated by semicolons, with the * wildcard, for example svc_*;*$ to ignore service accounts and computer accounts;
- Computers queried: all domain controllers, or a list of computers.
- Click Test: the number of events found on each computer is displayed, along with any access errors.
- Confirm. The audit is created and added to the favorites.
- To be alerted, select the audit, then Action > Alert: check Alert, choose Value, the >= operator and the threshold, then the alert level and notifications.
Ready-to-use templates
A template fills in the name, log, IDs, source, counting mode and time window. A tip is shown below the list (recommended threshold and alert level).
| Template | Log: IDs | Recommended threshold |
|---|---|---|
| Logon failures per account | Security: 4625, 4771, 4776 | 5 in 10 min |
| Attack on several accounts from the same origin | Security: 4625, 4771, 4776 | 10 accounts in 10 min |
| Logon failures from the same origin | Security: 4625, 4771, 4776 | 20 in 10 min |
| Locked-out accounts | Security: 4740 | 1 in 60 min |
| Security log cleared | Security: 1102 | 1 in 24 h |
| Audit policy changed | Security: 4719 | 1 in 24 h |
| Members added to a security group | Security: 4728, 4732, 4756 | 1 in 60 min |
| User accounts created or deleted | Security: 4720, 4726 | 1 in 24 h |
| Passwords reset | Security: 4724 | 1 in 60 min |
| New services installed | System: 7045 | 1 in 24 h |
| Unexpected shutdowns | System: 6008 | 1 in 24 h |
| System log cleared | System: 104 | 1 in 24 h |
Prerequisites
- The audit policy must be enabled on the computers queried for the chosen IDs (the System log templates do not need it).
- The account used by IDEAL Administration to connect to the domain must be able to read the log: member of the Event Log Readers group, or administrator.
- Logs are read remotely over RPC: if Test reports an unreachable computer, check the Remote Event Log Management firewall rule on that computer.
Good to know: filtering is done by the queried computer, and only the 2,000 most recent events of each computer are analyzed for per-account or per-origin counting. If no computer answers, the last known value is kept.

