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

Merged
Chris Davis (chrisda) merged 3 commits into from
Sep 2, 2026
+11 −0
Merged

Document strong identifier requirements for XDR mapping #486

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
bb39b73
Document strong identifier requirements for XDR mapping
PremMS-MDE Apr 21, 2026
2f2d0b2
Merge branch 'public' into patch-6
PremMS-MDE May 5, 2026
8589f58
Apply batched suggestions from code review
TimShererWithAquent Sep 2, 2026
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 @@ -145,6 +145,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 to XDR mapping)

To ensure that custom activity data (for example, Sophos alerts) is correctly mapped and visible in **Microsoft Defender XDR** (`security.microsoft.com`) under the **Device Timeline**, the ingested data must include a strong identifier combination for the host.

#### Required strong identifiers

At a minimum, include one of the following strong identifier combinations:

- `HostName` + `NTDomain`
- `HostName` + `DnsDomain`

> [!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