Frame this document as a source-led configuration and assurance check: Configure advanced Windows auditing before expecting identity detections. Only the official source and traced locations below supply facts. Confirm applicability before acting.
\nThe official Configure Windows event auditing from Microsoft supports the following bounded statements:
\nOnly the traced statements above are asserted as source facts. Apply the review to Defender for Identity workspaces, sensors, directory-service accounts, action accounts, network paths, roles, and deployment health after confirming that the source and deployed context match.
\nApply audit policy through controlled Group Policy testing; a configured setting does not prove events are generated, transported, or retained. No current deployment state or change approval follows from the source alone. Validate Active Directory, Windows DNS, time, certificates, domain-controller resources, network capture, cloud connectivity, and security operations, and treat examples or options as conditional inputs rather than defaults.
\nDSE recommends using the cited source as the evidence anchor for this decision. Begin by recording scope and current state before deciding whether a change is warranted. Record the source location, examined part of Defender for Identity workspaces, sensors, directory-service accounts, action accounts, network paths, roles, and deployment health, observed and expected states, owner, and reason for deviation.
\nAn implementation decision needs an owner, approved window, prechecks, observable outcome, stop authority, and rollback path. Validate Active Directory, Windows DNS, time, certificates, domain-controller resources, network capture, cloud connectivity, and security operations before and after the test, and store only sanitized operational evidence.
\nA reviewer should be able to retrace the decision from Opening overview; Auditing configuration guidance through sensor inventory, service and action-account permissions, health alerts, connectivity tests, portal state, and controlled detection tests. Record what was collected, where, when, by whom, and which system or role it represents.
\nRetain the starting state, authorization, execution record, outcome, deviation, and final state as one review package. Move disruptive checks to an approved test path. Reopen the decision when versions, design, dependencies, ownership, or official guidance changes.
\n