Security event 4719
System audit policy was changed
Channel: Security. Category: Audit Policy Change.
What it records
Generated whenever the local computer's audit policy changes, identifying which audit category and subcategory (e.g., Logon/Logoff, Object Access) was modified and whether Success and/or Failure auditing was added or removed for it. Per Microsoft's documentation, this event is always logged regardless of whether the 'Audit Policy Change' subcategory is itself set to be audited.
Why it matters
Audit policy determines what gets logged in the first place, so a change here (especially one that disables auditing on a sensitive subcategory) is a direct defense-evasion move: an attacker who quietly turns off logging before acting leaves far less evidence than one who clears the log afterward, making 4719 a key 'is my visibility being tampered with' signal.
What triggers it
Legitimately: an administrator tuning audit policy via `auditpol.exe` or Group Policy (Advanced Audit Policy Configuration) as part of security baselining. Maliciously: an attacker running `auditpol /set /subcategory:"..." /success:disable /failure:disable` (or `auditpol /clear /y`) to blind specific auditing categories before performing follow-on actions.
Fields that carry the answer
| Field | What it tells you |
|---|---|
| Category / Subcategory | Which audit category and subcategory (e.g. Object Access > File System, Logon/Logoff > Logon) had its policy changed, which identifies exactly what kind of logging was affected. |
| Changes | Whether Success and/or Failure auditing was added or removed for that subcategory: a 'removed' value is the direct signal of an attacker blinding a specific audit category before acting. |
In practice
Category Logon/Logoff, Subcategory Logon, Changes: Success removed, made by CORP\svcadmin as part of a documented GPO audit-baseline rollout. Routine. The same event showing Failure removed for Object Access > File System, made by CORP\jdoe (not an administrator) minutes before a burst of file-share access from that same account, points to an attacker blinding a specific audit category before acting.
Sample record
System audit policy was changed.
Subject:
Security ID: S-1-5-21-3457937927-2839227994-823803824-1104
Account Name: jsmith
Account Domain: CORP
Logon ID: 0x2A9F31
Audit Policy Change:
Category: Logon/Logoff
Subcategory: Logon
Subcategory GUID: {0CCE9215-69AE-11D9-BED3-505054503030}
Changes: Success removedATT&CK techniques
- T1562.002: T1562.002
Sources
Paste a record into Event XML or open a log in EVTX Reader.