A cloud-native SIEM solution that provides intelligent security analytics and threat detection across systems
Yes. The out-of-the-box ASIM unifying parser for this use case is the User Management schema parser:
_Im_UserManagement
This parser is designed to normalize user management events (such as user enable/disable, create/delete, password changes, group changes) from multiple sources into a single schema. It already supports filtering parameters like eventtype_in and time filters:
_Im_UserManagement(
eventtype_in = dynamic(["UserEnabled"]),
starttime = ago(1d),
endtime = now()
)
For Windows/local account events (for example, Security Event ID 4772) the unifying parser will route to the appropriate source-specific parser, such as:
-
_Im_UserManagement_MicrosoftSecurityEventVxxfor Windows SecurityEvent -
_Im_UserManagement_MicrosoftWindowsEventVxxfor WindowsEvent
For other platforms (AWS, Linux, Cisco ISE, SentinelOne, etc.), the same _Im_UserManagement unifying parser will route to the relevant source-specific _Im_UserManagement_*Vxx parser listed under the User Management parsers.
To cover Entra account management events (like Enable account in AuditLogs) with ASIM, those events must first be normalized into the User Management schema (for example, into the ASimUserManagementLogs table) or another supported source table that has a corresponding _Im_UserManagement_* parser. Once normalized, they are automatically included in _Im_UserManagement queries alongside the Windows/local account events.
If Entra AuditLogs are not yet normalized to the User Management schema in the workspace, they will not appear via _Im_UserManagement and must still be queried directly from AuditLogs as in the sample:
AuditLogs
| where OperationName =~ "Enable account"
In summary:
- There is an out-of-the-box unifying parser for user management events:
_Im_UserManagement. - It already supports Windows/local account events and any other sources listed in the User Management parsers table.
- Entra
AuditLogsmust be onboarded/normalized into the User Management schema (or a supported source) to be surfaced via_Im_UserManagement; otherwise, they remain accessible only via directAuditLogsqueries.
References: