Post

Microsoft Events Log Analysis:Windows Account & Group Management Events

Microsoft Events Log Analysis:Windows Account & Group Management Events

User Account Management


User account management events track changes to user accounts in Active Directory (AD) or local systems, such as creation, modification, enabling/disabling, password changes, and deletions. These are vital for monitoring insider threats, unauthorized access attempts, or compliance with policies like least privilege.

Common Event IDs

Here are the most relevant Event IDs for user account management (from the Security log):

Event IDDescriptionWhen It OccursAuditing Category
4720A user account was createdNew user account added (e.g., via Active Directory Users and Computers)User Account Management (Success)
4722A user account was enabledDisabled account reactivatedUser Account Management (Success)
4723An attempt was made to change an account's passwordPassword change by the user or adminUser Account Management (Success/Failure)
4724An attempt was made to reset an account's passwordAdmin resets a user's passwordUser Account Management (Success/Failure)
4725A user account was disabledAccount deactivated (e.g., for security reasons)User Account Management (Success)
4726A user account was deletedUser account removedUser Account Management (Success)
4738A user account was changedModifications to account properties (e.g., name, expiration)User Account Management (Success)
4740A user account was locked outAccount locked due to failed logonsUser Account Management (Success)
4767A user account was unlockedLocked account unlockedUser Account Management (Success)

Key Fields in User Account Events


Most user account events include sections like Subject (who performed the action), Target Account (the affected account), and Attributes (details of changes). These fields help trace accountability and assess impact. Below is a breakdown, with explanations:

  • Subject Section: Identifies the actor (e.g., the administrator or service account that initiated the change).
    • Security ID: A unique SID (Security Identifier) for the subject account. SIDs are used internally by Windows for authentication and authorization.
    • Account Name: The username of the subject (e.g., “administrator”).
    • Account Domain: The domain or machine name (e.g., “ACME-FR” for a domain-joined system).
    • Logon ID: A hexadecimal value (e.g., “0x20f9d”) representing the session ID of the logon session. This links related events from the same session for correlation.
  • Target Account / New Account Section: Details the affected user account.
    • Security ID: The SID of the new or changed account.
    • Account Name: The username (e.g., “John.Locke”).
    • Account Domain: The domain of the target account.
  • Attributes Section: Properties of the account, which vary by event but often include changes or new values. These are key for auditing compliance (e.g., password policies).
    • SAM Account Name: The logon name in the Security Accounts Manager (SAM) database (e.g., “John.Locke”). This is the pre-Windows 2000 logon name.
    • Display Name: A user-friendly name (e.g., “John Locke”) shown in tools like ADUC.
    • User Principal Name (UPN): The full email-like name for logon (e.g., “John.Locke@acme-fr.local”). It’s the modern equivalent of “Full Name” in your notes and is used for Kerberos authentication.
    • Home Directory: Path to the user’s network home folder (e.g., “\server\users\John.Locke”). Often set to “-“ if not configured.
    • Home Drive: Mapped drive letter for the home directory (e.g., “H:”).
    • Script Path: Path to a logon script (e.g., batch file run at login).
    • Profile Path: Roaming profile location (e.g., “\server\profiles\John.Locke”).
    • User Workstations: Allowed workstations for logon (comma-separated list); “*” means all.
    • Password Last Set: Timestamp of the last password change (e.g., “never” for new accounts). Critical for detecting stale passwords.
    • Account Expires: Expiration date (e.g., “never”). Helps enforce temporary accounts.
    • Primary Group ID: Default group (e.g., 513 for Domain Users).
    • Allowed To Delegate To: Services the account can delegate to (rarely used).
    • Old UAC Value / New UAC Value: User Account Control flags (hexadecimal, e.g., “0x0” to “0x15”). Flags include “Account Disabled,” “Password Not Required,” “Normal Account,” etc. Changes here indicate policy shifts.
    • User Account Control: Human-readable breakdown of UAC flags (e.g., “‘Password Not Required’ - Enabled” flags weak security).
    • User Parameters: Custom parameters (usually “-“).
    • SID History: List of previous SIDs (for migrations; usually “-“).
    • Logon Hours: Allowed logon times (bitmask; “value not set” means unrestricted).

Microsoft Events Log

Security Group Management


Security groups manage permissions in Windows (e.g., assigning rights to folders or resources). Events track creation, deletion, and membership changes for security-enabled groups (local, global, or universal). These are essential for monitoring privilege escalations, like adding users to admin groups.

Common Event IDs

Focus on security-enabled groups (not distribution groups for email). Events are similar for local/global/universal scopes.

Event IDDescriptionWhen It OccursAuditing CategoryGroup Type
4727A security-enabled global group was createdNew global group addedSecurity Group Management (Success)Global
4728A member was added to a security-enabled global groupUser/computer added to groupSecurity Group Management (Success)Global
4729A member was removed from a security-enabled global groupMember removedSecurity Group Management (Success)Global
4730A security-enabled global group was deletedGroup removedSecurity Group Management (Success)Global
4731A security-enabled local group was createdNew local group (similar for universal: 4737)Security Group Management (Success)Local/Universal
4732A member was added to a security-enabled local groupMember added (universal: 4737 variant)Security Group Management (Success)Local/Universal
4733A member was removed from a security-enabled local groupMember removedSecurity Group Management (Success)Local/Universal
4734A security-enabled local group was deletedGroup removed (universal: 4741)Security Group Management (Success)Local/Universal
4735A security-enabled local group was changedGroup attributes modifiedSecurity Group Management (Success)Local/Universal

Key Fields in Security Group Events


Similar structure to user events, but focused on groups:

  • Subject Section: Same as user events (who made the change).
  • Group Section: Details the affected group.
    • Security ID: SID of the group.
    • Group Name: Name (e.g., “Domain Admins”).
    • Group Domain: Domain or local machine.
    • Attributes: Group SAM name, description, etc. (e.g., “Group Scope: Global and security”).
  • Member Section (for add/remove events): SID, name, and domain of the added/removed member (user or group).
  • Additional Attributes: Similar to user events, but group-specific (e.g., no password fields; instead, group type like “Security” vs. “Distribution”).

Analysis Tips: Watch for additions to privileged groups (e.g., Event 4728 for “Administrators”). The “Target Group” and “Member” sections help trace who gained elevated rights. Correlate with user events for full context.

This post is licensed under CC BY 4.0 by the author.