You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: defender-xdr/advanced-hunting-identityinfo-table.md
+38-3Lines changed: 38 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -19,7 +19,7 @@ ms.custom:
19
19
- cx-ti
20
20
- cx-ah
21
21
ms.topic: reference
22
-
ms.date: 04/22/2024
22
+
ms.date: 05/13/2025
23
23
appliesto:
24
24
- Microsoft Defender XDR
25
25
- Microsoft Sentinel in the Microsoft Defender portal
@@ -35,6 +35,10 @@ Microsoft Sentinel uses a slightly expanded version of this table in Log Analyti
35
35
36
36
For information on other tables in the advanced hunting schema, [see the advanced hunting reference](advanced-hunting-schema-tables.md).
37
37
38
+
The following schema is the unified `IdentityInfo` schema that streamlines a similar table in Microsoft Sentinel's log analytics and in Microsoft Defender XDR advanced hunting. The complete set of columns below is available for Defender portal users who have onboarded Sentinel and turned on the User and Entity Behavior Analytics (UEBA) service.
39
+
40
+
Defender portal users who have not onboarded a Sentinel workspace that has the UEBA service turned on cannot view UEBA-specific columns. Read [UEBA-specific columns](#ueba-specific-columns).
41
+
38
42
| Column name | Data type | Description |
39
43
|-------------|-----------|-------------|
40
44
|`Timestamp`[*](#mdi-only)|`datetime`| The date and time that the line was written to the database. <br><br>This is used when there are multiple lines for each identity, such as when a change is detected, or if 24 hours have passed since the last database line was added. |
@@ -45,7 +49,8 @@ For information on other tables in the advanced hunting schema, [see the advance
45
49
|`AccountDisplayName`|`string`| Name of the account user displayed in the address book. Typically a combination of a given or first name, a middle initial, and a last name or surname. |
46
50
|`AccountName`|`string`| User name of the account |
47
51
|`AccountDomain`[*](#mdi-only)|`string`| Domain of the account |
48
-
|`Type`[*](#mdi-only)|`string`| Type of record |
52
+
|`CriticalityLevel`|`int`| The criticality score of the account |
53
+
|`Type`[*](#mdi-only)|`string`| Type of identity; possible values: User, ServiceAccount |
49
54
|`DistinguishedName`[*](#mdi-only)| string | The user's [distinguished name](/previous-versions/windows/desktop/ldap/distinguished-names)|
50
55
|`CloudSid`|`string`| Cloud security identifier of the account |
51
56
|`GivenName`|`string`| Given name or first name of the account user |
@@ -61,17 +66,47 @@ For information on other tables in the advanced hunting schema, [see the advance
61
66
|`Manager`[*](#mdi-only)|`string`| The listed manager of the account user |
62
67
|`Phone`[*](#mdi-only)|`string`| The listed phone number of the account user|
63
68
|`CreatedDateTime`[*](#mdi-only)|`datetime`| Date and time when the account user was created |
64
-
|`SourceProvider`[*](#mdi-only)|`string`|The identity's source, such as Microsoft Entra ID, Active Directory, or a [hybrid identity](/azure/active-directory/hybrid/what-is-provisioning) synchronized from Active Directory to Azure Active Directory |
65
69
|`ChangeSource`[*](#mdi-only)|`string`|Identifies which identity provider or process triggered the addition of the new row. For example, the `System-UserPersistence` value is used for any rows added by an automated process.|
70
+
|`BlastRadius`|`string`| A calculation based on the position of the user in the org tree and the user's Microsoft Entra roles and permissions; possible values: Low, Medium, High|
71
+
|`CompanyName`|`string`| Name of the company for which the user works |
72
+
|`DeletedDateTime`|`datetime`| Date and time when the user account was deleted |
73
+
|`EmployeeId`|`string`| Employee identifier assigned to the user by the organization |
74
+
|`OtherMailAddresses`|`dynamic`| Additional email addresses of the user account |
75
+
|`RiskLevel`|`string`| Microsoft Entra ID risk level of the user account; possible values: Low, Medium, High |
76
+
|`RiskLevelDetails`|`string`| Details regarding the Microsoft Entra ID risk level |
77
+
|`State`|`string`| State where the sign-in occured, if available |
66
78
|`Tags`[*](#mdi-only)|`dynamic`| Tags assigned to the account user by Defender for Identity |
67
79
|`AssignedRoles`[*](#mdi-only)|`dynamic`| For identities from Microsoft Entra-only, the roles assigned to the account user|
68
80
|`PrivilegedEntraPimRoles` (Preview) [**](#mdi)|`dynamic`| A snapshot of privileged role assignment schedules and eligibility schedules for the account as maintained by Microsoft Entra Privileged Identity Management (excluding activated assignments) |
69
81
|`TenantId`|`string`| Unique identifier representing your organization's instance of Microsoft Entra ID |
70
82
|`SourceSystem`[*](#mdi-only)|`string`| The source system for the record|
83
+
|`OnPremObjectId`|`string`| Active Directory object ID of the user |
84
+
|`TenantMembershipType`|`string`| User type in Microsoft Entra ID; possible values: Guest, Member|
85
+
|`RiskStatus`|`string`| Status of the user's risk; possible values: None, ConfirmedSafe, Remediated, Dismissed, AtRisk, ConfirmedCompromised, UnknownFutureValue|
86
+
|`UserAccountControl`|`string`| Security attributes of the user account in the Active Directory domain |
87
+
|`IdentityEnvironment`|`string`| Environment where the identity is used; possible values: CloudOnly, Hybrid, On-premises |
88
+
|`SourceProviders`|`dynamic`| Source providers of the accounts for the identity; possible values: ActiveDirectory, EntraID, Okta |
89
+
|`GroupMembership`|`dynamic`| Microsoft Entra ID groups where the user account is a member |
90
+
71
91
72
92
<aname="mdi-only"></a>* Available only for tenants with Microsoft Defender for Identity, Microsoft Defender for Cloud Apps or Microsoft Defender for Endpoint P2 licensing.<br>
73
93
<aname="mdi"></a>** Available only for tenants with Microsoft Defender for Identity.
74
94
95
+
## UEBA-specific columns
96
+
If you are using the Microsoft Defender portal but have not onboarded a Microsoft Sentinel workspace with the UEBA service turned on, the following columns are not available in your `IdentityInfo` table:
97
+
98
+
-`BlastRadius`
99
+
-`CompanyName`
100
+
-`DeletedDateTime`
101
+
-`EmployeeId`
102
+
-`OtherMailAddresses`
103
+
-`RiskLevel`
104
+
-`RiskLevelDetails`
105
+
-`State`
106
+
-`Tags`
107
+
108
+
For more information about UEBA, read [Advanced threat detection with User and Entity Behavior Analytics (UEBA) in Microsoft Sentinel](/azure/sentinel/identify-threats-with-entity-behavior-analytics). For more information about the different data sources in UEBA, read [Microsoft Sentinel UEBA reference](/azure/sentinel/ueba-reference).
Copy file name to clipboardExpand all lines: defender-xdr/whats-new.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -35,6 +35,7 @@ You can also get product updates and important notifications through the [messag
35
35
## May 2025
36
36
37
37
- (Preview) You can now highlight your security operations achievements and the impact of Microsoft Defender using the **unified security summary**. The unified security summary is available in the Microsoft Defender portal and streamlines the process for SOC teams to generate security reports, saving time usually spent on collecting data from various sources and creating reports. For more information, see [Visualize security impact with the unified security summary](security-summary-report.md).
38
+
- Defender portal users who have onboarded Microsoft Sentinel and have enabled the [User and Entity Behavior Analytics (UEBA)](/azure/sentinel/ueba-reference) can now take advantage of the new unified [`IdentityInfo` table](advanced-hunting-identityinfo-table.md) in advanced hunting. This latest version now includes the largest possible set of fields common to both Defender and Azure portals.
0 commit comments