DSE security knowledge hub

Security knowledge,
without the noise.

Page 239 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

Validate new identity sensors through status, device timeline, and identity data

A first sensor activation can take up to an hour to show as Running, while subsequent activations can appear within five minutes. Microsoft directs administrators to confirm Defender for Identity events on the device timeline and user data for the newly onboarded domain.

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

Connect CyberArk Identity only with the required API roles and permissions

The connection uses connector APIs to provide Defender for Identity visibility into and control over CyberArk identities. Microsoft requires the documented CyberArk role plus Microsoft Entra or Defender role-based access permissions before connection.

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

Correlate Okta activity with Active Directory and Entra identity context

Defender for Identity ingests Okta user and activity data and correlates it with identity data from Active Directory and Microsoft Entra ID. The integration provides a centralized view of user activity, posture risks, and suspicious behavior and supports remediation actions.

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