Active Directory change auditing Who changed what, when, and from where. With the change itself ready to undo.
Identity CORE collects every object in Active Directory, Entra ID and Okta and joins it to the directory's own audit trail. Pick a change in the Auditor, read the full story, and roll it back from there. Put rules on the objects that matter most and have unwanted changes reverted for you.
- Active Directory, Entra ID and Okta audit trails in one console
- Every change joined to the object and its saved copy, so it can be undone from the event
- Monitored objects with Notify or Revert rules, evaluated within seconds of a change
From "something happened last night" to putting it right
The Auditor lists the individual changes made in a directory: what was changed, by whom, and when. Pick Active Directory, Entra ID or Okta at the top and the screen follows. Sort by time, filter by event type, and click a row to see the full details laid out for that kind of change.
Because you start from the change rather than the object, you do not have to work out which account or group was affected. Tick one change or several, choose Rollback, and the wizard takes you through exactly what will be put back.
| Column | What it tells you |
|---|---|
| Event | What sort of change it was: create, modify, delete, move or restore |
| Object | Which object was changed, with its full location in the directory |
| Account Name | Who made the change |
| Domain Controller | Which server recorded it (the tenant, for Entra ID and Okta) |
| Event Time | When it happened |
One audit trail, fed by each directory's own log
Events are collected incrementally from a bookmark, de-duplicated, and kept for the retention period you set. Nothing leaves your network.
Active Directory
Directory service change events from the domain controllers, matched to the objects they name.
- Read from each domain controller's Security log
- Or from a Splunk® index you already keep
- Or pushed by the agent on each domain controller
Entra ID
The tenant's directory audit log, read through Microsoft Graph from where the last run stopped.
- Role, group, application and policy changes with the actor
- Failed operations with the reason
- Administrative activity by address, with new addresses flagged
Okta
The organization's System Log, paged from a bookmark and de-duplicated.
- User, group, application and policy events with the actor
- Administrator privileges granted and revoked
- Activity by address and location
Three ways to collect Active Directory events
Identity CORE can read the Security log of each domain controller itself, take the events from a Splunk® index you already maintain, or let the lightweight agent on each domain controller push them. With the agents, nothing has to reach into a domain controller from outside, and a change to a watched object is judged within seconds of the event arriving.
Not just the event. The object as it was.
Each collection run picks up only what changed since the last one and keeps a copy of every changed object. The Identity browser shows the directory as a tree, and every object's Backup Time says when its last copy was taken.
That is what makes an audit event actionable: the event says what happened, the saved copy says what the object looked like before, and the rollback wizard uses both. Deleted objects are gathered under their own container, arranged by where they used to live.
The home dashboard counts users, groups, computers and the rest for each domain and tenant, with a click through to the objects behind each number and an activity chart of when changes happened.
Watch the objects that matter most, and revert what should not change
Some objects matter more than others: the group that grants administrator rights, the account a critical service runs as, a Conditional Access policy, an Entra directory role. A monitored object is a named list of those, with rules about which changes you care about.
A rule names an attribute and what should happen when it changes: Notify, or Revert. A Revert puts the attribute back to its previous value through a rollback job, and the entry records who made the original change and how the revert went.
- 1
Name it "Domain Admins and service accounts", with a note for whoever reads it next.
- 2
Pick the objects Browse a domain, or pick from a tenant's collected objects. Objects from several domains can share one list.
- 3
Set the rules An attribute and an action for each. A new list starts with Any attribute → Notify; add member → Revert for a group, or a specific attribute for an account.
- 4
Say who to tell One email per evaluation listing every change found, who made it and whether a rollback was queued.
After every collection and every audit run, every quarter hour besides, and within seconds when the domain controller agents send an event about a watched object.
A change is found in the audit events, usually first and with the actor, and in the object's next saved copy. Both sightings are kept as one entry, so nothing is reported twice.
A deleted or restored object is reported, not undone, so a deliberate cleanup is never fought by a rule. Restore it from the Identity browser when it was a mistake.
What was done inside Identity CORE is audited too
The Auditor covers changes made in your directories, wherever they came from. System Activity covers what was done in the console: every rollback and restore, every guided fix and its undo, every recovery started, retried or cancelled, every configuration change and every sign-in, with the request and the result attached.
Each operator sees their own history under My Activity. Administrators see everyone's, and the Operator Actions report hands it over with success or failure per action.
Roles separate administrators, managers, operators and read-only users, and the back end enforces them, not just the menus. Sign in with your own accounts or Entra ID single sign-on.
The questions an auditor asks, already answered
Activity reports run over the audit trail for a period you choose, and each exists for Active Directory, Entra ID and Okta.
Saved, scheduled and exported like every other report. See Reporting →
Common Questions
Do I need to install anything on my domain controllers?
Not for auditing. Identity CORE can read the domain controllers' Security logs remotely or take the events from Splunk. The agent is optional: it adds backups for forest recovery and pushes audit events so nothing has to connect into a domain controller.
How far back does the audit trail go?
As far as your retention setting. Audit events and object copies are kept for the retention period you choose per directory, and the first run of a tenant reaches back 30 days by default.
Can a monitored object rule revert a change in Entra ID or Okta?
Yes. An Entra ID change is reverted from the object's previous saved copy. An Okta event does not carry attribute values, so a Revert waits for the next collection to show the change and then puts it back.
Is Identity CORE a SIEM?
No. It is the identity-specific layer: it understands directory objects, keeps their history and can undo a change. It happily takes Active Directory events from Splunk if that is where you already keep them.
See a change found, explained and undone
Book a demo and watch a change land in the Auditor, trip a rule, and roll back.