Page 241 of the DSE Security Knowledge Hub, with source-backed guidance, checklists, explainers, and playbooks.
The stale-account recommendation lists Active Directory user accounts that have not logged in during the previous 90 days. The page says impacted entities can update within minutes after remediation while assessment scores and statuses update every 24 hours.
Read the explainer
Defender for Identity provides cloud-identity assessments for Okta, CyberArk Identity, and SailPoint Identity Security Cloud. Microsoft requires the relevant provider instance to be connected in the Defender portal before its assessments are used.
Read the guide
Defender for Identity alerts describe suspicious activities and identify involved actors and computers with direct evidence links.
Read the playbook
Classic and Defender-format alerts use detections from Defender for Identity sensors but differ as part of the transition to a unified alerting experience.
Read the briefing
Classic and Defender formats use the same underlying Defender for Identity sensor detections but differ in structure, naming, and categorization. Alert names differ in the XDR structure while alert IDs remain consistent between the two formats.
Read the checklist
By default, the alerts queue shows alerts seen in the previous seven days in a grouped view with the newest alerts first. The documented workflow covers viewing, filtering, investigating, classifying, and managing Defender for Identity security alerts.
Read the explainer
Defender for Identity monitors information from Active Directory, network activities, and event activities to detect suspicious activity. For a validated threat, the monitored information can help determine incident scope, involved entities, and remediation.
Read the guide
Defender for Identity activities derived from network traffic, Windows events, and ETW commonly contain IP data. Network Name Resolution correlates raw IP activities with computers so Defender for Identity can profile entities and generate alerts for suspicious activity.
Read the playbook
The alert story presents a chronological view of what happened, when it happened, and which entities appeared before and after the triggering event. The alert graph maps users, devices, and domain controllers and shows their interactions for relationship and pattern analysis.
Read the briefing
Available remediation actions depend on the connector managing the account and can span Active Directory, Entra ID, non-Microsoft identity providers, and connected SaaS applications.
Read the checklist