DSE security knowledge hub

Security knowledge,
without the noise.

Page 243 of the DSE Security Knowledge Hub, with source-backed guidance, checklists, explainers, and playbooks.

DSE-authoredOfficial sourcesReviewed guidance
Search the library
DSE post stream

Guidance and analysis from DSE

3,000 articles
DSE visual briefIdentity & cloud

Apply sensitive, Exchange, and honeytoken identity tags for their documented detections

Defender for Identity supports tagging accounts as sensitive or honeytokens and tagging devices as Exchange servers. Some detections depend on the sensitive tag, while any sign-in from a tagged honeytoken account triggers an alert.

Published Reviewed 3 min readBy DSE Security Editorial Team
Read the explainer
DSE visual briefIdentity & cloud

Trace gMSA password-read failures to the domain controller's retrieval rights

The known-issues page documents a sensor warning when an LDAP connection cannot retrieve a group managed service account password. For that documented issue, Microsoft identifies the cause as the domain controller lacking rights to access the gMSA password.

Published Reviewed 3 min readBy DSE Security Editorial Team
Read the checklist
DSE visual briefIdentity & cloud

Use Defender for Identity sensor logs to reconstruct chronological sensor state

Defender for Identity logs provide point-in-time insight into sensor activity and status. The Microsoft.Tri.Sensor.log records sensor operations, resolution, and errors in chronological order and is used for an overall operational view.

Published Reviewed 3 min readBy DSE Security Editorial Team
Read the explainer
DSE visual briefIdentity & cloud

Run a daily identity-defense cycle across dashboards, incidents, hunting, tuning, and health

Microsoft’s daily guide covers identity dashboard review, incident triage, alert tuning, proactive hunting, and deployment-health monitoring. The stated operating personas include SOC analysts, security administrators, and identity and access management teams.

Published Reviewed 3 min readBy DSE Security Editorial Team
Read the guide
DSE visual briefPhysical security

Validate exit-route capacity and permanence before occupancy changes

Under 29 CFR 1910, the rule requires that more than two exit routes be available in a workplace if the number of employees, the size of the building, its occupancy, or the arrangement of the workplace is such that all employees would not be able to evacuate safely during an emergency.

Published Reviewed 3 min readBy DSE Security Editorial Team
Read the checklist