ItemBox

4912(S) Per User Audit Policy was changed.

4912(S): Per User Audit Policy was changed.

Subcategory: Audit Policy Change

Event Description:

This event generates every time Per User Audit Policy was changed.

This event is always logged regardless of the “Audit Policy Change” sub-category setting.

Note  For recommendations, see Security Monitoring Recommendations for this event.

Event XML:

- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
 <Provider Name="Microsoft-Windows-Security-Auditing" Guid="{54849625-5478-4994-A5BA-3E3B0328C30D}" /> 
 <EventID>4912</EventID> 
 <Version>0</Version> 
 <Level>0</Level> 
 <Task>13568</Task> 
 <Opcode>0</Opcode> 
 <Keywords>0x8020000000000000</Keywords> 
 <TimeCreated SystemTime="2015-09-30T23:43:07.363195100Z" /> 
 <EventRecordID>1049452</EventRecordID> 
 <Correlation /> 
 <Execution ProcessID="516" ThreadID="1660" /> 
 <Channel>Security</Channel> 
 <Computer>DC01.contoso.local</Computer> 
 <Security /> 
 </System>
- <EventData>
 <Data Name="SubjectUserSid">S-1-5-21-3457937927-2839227994-823803824-1104</Data> 
 <Data Name="SubjectUserName">dadmin</Data> 
 <Data Name="SubjectDomainName">CONTOSO</Data> 
 <Data Name="SubjectLogonId">0x11ae30</Data> 
 <Data Name="TargetUserSid">S-1-5-21-3457937927-2839227994-823803824-2104</Data> 
 <Data Name="CategoryId">%%8276</Data> 
 <Data Name="SubcategoryId">%%13312</Data> 
 <Data Name="SubcategoryGuid">{0CCE922B-69AE-11D9-BED3-505054503030}</Data> 
 <Data Name="AuditPolicyChanges">%%8452</Data> 
 </EventData>
 </Event>

Required Server Roles: None.

Minimum OS Version: Windows Server 2008, Windows Vista.

Event Versions: 0.

Field Descriptions:

Subject:

  • Security ID [Type = SID]: SID of account that made a change to per-user audit policy. Event Viewer automatically tries to resolve SIDs and show the account name. If the SID cannot be resolved, you will see the source data in the event.

Note  A security identifier (SID) is a unique value of variable length used to identify a trustee (security principal). Each account has a unique SID that is issued by an authority, such as an Active Directory domain controller, and stored in a security database. Each time a user logs on, the system retrieves the SID for that user from the database and places it in the access token for that user. The system uses the SID in the access token to identify the user in all subsequent interactions with Windows security. When a SID has been used as the unique identifier for a user or group, it cannot ever be used again to identify another user or group. For more information about SIDs, see Security identifiers.

  • Account Name [Type = UnicodeString]: the name of the account that made a change to per-user audit policy.

  • Account Domain [Type = UnicodeString]: subject’s domain or computer name. Formats vary, and include the following:

    • Domain NETBIOS name example: CONTOSO

    • Lowercase full domain name: contoso.local

    • Uppercase full domain name: CONTOSO.LOCAL

    • For some well-known security principals, such as LOCAL SERVICE or ANONYMOUS LOGON, the value of this field is “NT AUTHORITY”.

    • For local user accounts, this field will contain the name of the computer or device that this account belongs to, for example: “Win81”.

  • Logon ID [Type = HexInt64]: hexadecimal value that can help you correlate this event with recent events that might contain the same Logon ID, for example, “4624: An account was successfully logged on.”

Policy For Account:

  • Security ID [Type = SID]: SID of account for which the Per User Audit Policy was changed. Event Viewer automatically tries to resolve SIDs and show the account name. If the SID cannot be resolved, you will see the source data in the event.

Policy Change Details:

  • Category [Type = UnicodeString]: the name of auditing category which subcategory state was changed. Possible values are:

    • Account Logon

    • Account Management

    • Detailed Tracking

    • DS Access

    • Logon/Logoff

    • Object Access

    • Policy Change

    • Privilege Use

    • System

  • Subcategory [Type = UnicodeString]: the name of auditing subcategory which state was changed. Possible values:

ValueValueValue
Audit Credential ValidationAudit Process TerminationAudit Other Logon/Logoff Events
Audit Kerberos Authentication ServiceAudit RPC EventsAudit Special Logon
Audit Kerberos Service Ticket OperationsAudit Detailed Directory Service ReplicationAudit Application Generated
Audit Other Logon/Logoff EventsAudit Directory Service AccessAudit Certification Services
Audit Application Group ManagementAudit Directory Service ChangesAudit Detailed File Share
Audit Computer Account ManagementAudit Directory Service ReplicationAudit File Share
Audit Distribution Group ManagementAudit Account LockoutAudit File System
Audit Other Account Management EventsAudit IPsec Extended ModeAudit Filtering Platform Connection
Audit Security Group ManagementAudit IPsec Main ModeAudit Filtering Platform Packet Drop
Audit User Account ManagementAudit IPsec Quick ModeAudit Handle Manipulation
Audit DPAPI ActivityAudit LogoffAudit Kernel Object
Audit Process CreationAudit LogonAudit IPsec Driver
Audit Other Object Access EventsAudit Filtering Platform Policy ChangeAudit Other System Events
Audit RegistryAudit MPSSVC Rule-Level Policy ChangeAudit Security State Change
Audit SAMAudit Other Policy Change EventsAudit Security System Extension
Audit Policy ChangeAudit Non-Sensitive Privilege UseAudit System Integrity
Audit Authentication Policy ChangeAudit Sensitive Privilege UseAudit PNP Activity
Audit Authorization Policy ChangeAudit Other Privilege Use Events
Audit Group MembershipAudit Network Policy Server
  • Subcategory GUID [Type = GUID]: the unique GUID of changed subcategory.

Note  GUID is an acronym for ‘Globally Unique Identifier’. It is a 128-bit integer number used to identify resources, activities or instances.

To see subcategory GUID you can use the following command: “auditpol /list /subcategory:* /v”:

  • Changes [Type = UnicodeString]: changes which were made for the subcategory. Possible values are:

    • Success include removed

    • Success include added

    • Failure include removed

    • Failure include added

    • Success exclude removed

    • Success exclude added

    • Failure exclude removed

    • Failure exclude added

Security Monitoring Recommendations

For 4912(S): Per User Audit Policy was changed.

  • If you use the Per-user audit feature, then this event should be always monitored, especially on high value assets or computers. If this change was not planned, investigate the reason for the change.

  • If you don’t use the Per-user audit feature, then this event should be always monitored because it indicates use of the Per-user audit feature outside of your standard procedures.