Review Privileged Access

The members of the administrative groups can change anything in the domain, so their accounts are the ones an attacker looks for first. This routine lists who holds those rights — directly, through nested groups, or left over from an old membership — and which of those accounts are exposed to Kerberoasting or delegation, or no longer used. It is written for administrators and security reviewers. The built-in ★ Security Audit audit profile runs the membership and exposure reports; the privileged-account security findings add Pass or Fail.

How Often to Review

No two sources name the same interval. Microsoft's answer is to keep the groups empty day to day and be told of every change.

Source What it asks
Microsoft No day-to-day accounts in Enterprise Admins, Domain Admins or the built-in Administrators; members are added for a task when needed, and auditing alerts on any change to the groups' membership or properties.
Active Directory Pro Review privileged group changes weekly; audit privileged group membership quarterly.
FedRAMP High, as Microsoft Learn maps it Review privileged accounts monthly.
PCI DSS 7.2.4, as Microsoft Learn quotes it Review all user accounts and their access privileges at least once every six months.
CIS Controls, Safeguard 6.8 Review access control to confirm that all privileges are authorized at least annually.
1

Run the Security Audit Profile

On the Audit page, select ★ Security Audit and run it (see Run an Audit). Its 24 reports fall into three groups:

The security findings about privileged accounts are not in this profile. They are in ★ All Security Findings; to run just them with this routine, add them to a profile of your own — steps 2 to 4 name them.

AD Reports Audit page after a Security Audit run: the profile's 24 reports by object type with their results, and the All Admin Group Members tab open

2

Review Who Is in the Admin Groups

All Admins lists the members of Administrators, Domain Admins, Enterprise Admins and Schema Admins — primary, direct and nested. Compare it with Admins (Direct Members Only): an account in the first list and not in the second gets its rights through a nested group, which is easy to miss.

AD Reports Administrator Reports folder with All Admins run: the primary, direct and nested members of Administrators, Domain Admins, Enterprise Admins and Schema Admins

For each account, ask whether a person needs these rights today. In Microsoft's model, Enterprise Admins holds no users day to day — the forest root domain's Administrator account possibly excepted — and neither Domain Admins nor the built-in Administrators holds the accounts people work with every day. Microsoft also notes that assessments commonly find these groups holding far too many accounts (Microsoft Learn).

3

Find Admin Rights Left Behind

When an account or group joins a protected group, Windows marks it with adminCount and gives it AdminSDHolder's permissions; leaving the group changes neither. Three reports find what was left:

  • Shadow Admins — every user account with adminCount=1 except the built-in ones Windows marks as critical: today's administrators, and the accounts that kept the mark after leaving. Compare it with All Admins.
  • Orphaned adminCount Accounts and Groups — the finding lists only the accounts and groups no longer in any protected group. Disable or remove an account nobody uses; otherwise turn its inheritance back on and clear adminCount, as its How to Fix says.
  • Protected Users (Disabled) — disabled accounts that still carry the mark; the Hygiene Check profile runs it.

AD Reports Audit page after a Security Audit run with the Shadow Admins (Orphaned adminCount) tab open: a user account marked with adminCount=1 that is not one of the built-in accounts

Rights can also be held outside the groups. These findings list them:

4

Check What Exposes Each Privileged Account

An administrator who should keep the rights can still hold them in an exposed account. These findings list such accounts:

Microsoft's December 2025 guidance names two of these fixes itself: remove support for unconstrained delegation, and add high-risk accounts to Protected Users (Microsoft Windows Server blog).

Between reviews, the Dashboard watches the same accounts. Its Privileged Accounts widget highlights privileged passwords older than 90 days in yellow and disabled accounts in red, and the Security Posture Score counts privileged passwords set to never expire and the age of the oldest privileged password.
5

Watch for Changes and Keep the Record

Between reviews. Schedule All Admins, or the whole profile, so that changes come to you: a scheduled report can e-mail only what changed since its last run, and the daily status e-mail can list what your scheduled reports recorded as changed, with the Administrator and AdminSDHolder reports right after the findings and readiness checks. Both compare runs: who made a change is not recorded, and a change made and undone between two runs does not show. Microsoft wants auditing configured to alert on any change to these groups; a comparison of runs does not replace it.

After each review, save the lists you reviewed as a baseline (History → Save Active Report to History); at the next review, compare: the Added sub-tab lists every account that gained rights in between (see Common Use Cases).

What to keep from each review:

  • the dated lists you reviewed — the run's workbook, whose Run Summary lists every report it ran, the empty ones included;
  • for each account kept, who decided and why; for each removal, the change and its date;
  • the comparison made after the removals.

PCI DSS 7.2.4 asks that inappropriate access is addressed and that management acknowledges the access that remains is appropriate (Microsoft Learn). ENISA's examples of evidence for privileged accounts include the list of users with privileged access and the records of access reviews and revocations (ENISA). The decisions and the sign-off are yours: AD Reports supplies the lists, and the Compliance Evidence Pack's change evidence has space for a reviewer to sign.

Questions about this routine? Please feel free to contact us.

Ready to try AD Reports?

Download the free 14-day trial and start reporting on your Active Directory today.