Skip to content

Document strong identifier requirements for XDR mapping #486

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
PremMS-MDE wants to merge 1 commit into
base: public
Choose a base branch
from
+11 −0
Open

Document strong identifier requirements for XDR mapping #486

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 11 additions & 0 deletions defender-xdr/entity-page-device.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -146,6 +146,17 @@ You can elect not to show events from Microsoft Sentinel in the main timeline, a

For more information about these activity events, see [Entity pages in Microsoft Sentinel](/azure/sentinel/entity-pages?tabs=defender-portal#entity-pages).

### Strong Identifier Requirements for Unified Timeline (Sentinel → XDR Mapping)

To ensure that custom activity data (e.g., Sophos alerts) is correctly mapped and visible in **Microsoft Defender XDR** (`security.microsoft.com`) under the **Device Timeline**, the ingested data must include multiple strong identifiers for the host/device.

#### ✅ Required Strong Identifiers

At minimum, one of the following valid combinations must be present:

- **Hostname + NTDomain**
- **Hostname + DNS Domain**

> [!NOTE]
>
> For firewall events to be displayed, you'll need to enable the audit policy. For instructions, see [Audit Filtering Platform connection](/windows/security/threat-protection/auditing/audit-filtering-platform-connection).
Expand Down