Account for special identity groups in every Windows ACL review

Use this document to connect an official requirement or behavior to observable evidence: Account for special identity groups in every Windows ACL review. Only the official source and traced locations below supply facts. Confirm applicability before acting.

Source fact:

The official Special Identity Groups from Microsoft supports the following bounded statements:

• Special identity groups provide a Windows mechanism for assigning access based on authentication or operating context. The research record locates this support at Opening overview.
• The reference distinguishes identities such as Anonymous Logon, Authenticated Users, and authentication-authority asserted identities. The research record locates this support at Section: Default special identity groups.

These statements are the factual basis for this document. Do not extend them into a broader assurance. Review forests, domains, controllers, directory partitions, trusts, sites, replication links, service accounts, and delegated roles only where the source and recorded environment align.

What the source does not establish

Do not treat special identities as ordinary AD groups with manually managed membership. Do not read the source as proof of implementation or permission to change production. Its guidance remains conditional on Windows DNS, time synchronization, network reachability, PKI, backups, virtualization safeguards, and privileged identity and the environment’s recorded constraints.

Applicability questions

• For source statement 1 at Opening overview, which observable configuration, record, or test can confirm applicability here?
• For source statement 2 at Section: Default special identity groups, which observable configuration, record, or test can confirm applicability here?
• What inventory proves which parts of forests, domains, controllers, directory partitions, trusts, sites, replication links, service accounts, and delegated roles are in and out of scope?
• Which condition in Windows DNS, time synchronization, network reachability, PKI, backups, virtualization safeguards, and privileged identity must be healthy before evidence is trustworthy?
• What result would disprove the working assumption and return the issue to the owner?

DSE recommendation:

DSE recommends using the cited source as the evidence anchor for this decision. Start with applicability, then compare the observed state with the cited source. Record the source location, examined part of forests, domains, controllers, directory partitions, trusts, sites, replication links, service accounts, and delegated roles, observed and expected states, owner, and reason for deviation.

If the review warrants change, use a bounded implementation with prerequisites, test population, monitoring, abort criteria, and a rehearsed reversal. Sequence checks for Windows DNS, time synchronization, network reachability, PKI, backups, virtualization safeguards, and privileged identity and sanitize protected material before retention.

Verification and evidence

Build a reproducible chain from Opening overview; Section: Default special identity groups to the observed environment. Useful domain evidence includes directory and policy exports, replication and locator tests, event logs, trust state, role ownership, and controlled authentication tests; label every item with scope, timestamp, collector, and stable identifier.

Preserve both successful and failed observations, along with approval and rollback evidence. Avoid uncontrolled production experiments. Assign an expiry or event-driven recheck so the conclusion is not treated as permanent.

Official references

• Special Identity Groups — Microsoft