Event ID 4719 — System audit policy was changed.
Description
System audit policy was changed.
Message #
Fields #
| Name | Description |
|---|---|
SubjectUserSid SID | [Subject] Security ID. |
SubjectUserName UnicodeString | [Subject] Account Name. |
SubjectDomainName UnicodeString | [Subject] Account Domain. |
SubjectLogonId HexInt64 | [Subject] Logon ID. |
CategoryId UnicodeString | [Audit Policy Change] Category. Known values
|
SubcategoryId UnicodeString | [Audit Policy Change] Subcategory. Known values
|
SubcategoryGuid GUID | [Audit Policy Change] Subcategory GUID. Known values
|
AuditPolicyChanges UnicodeString | [Audit Policy Change] Changes. Known values
|
ClientProcessId UInt32 | — |
ClientProcessStartKey UInt64 | — |
Example Event #
{
"system": {
"provider": "Microsoft-Windows-Security-Auditing",
"guid": "54849625-5478-4994-A5BA-3E3B0328C30D",
"event_source_name": "",
"event_id": 4719,
"version": 1,
"level": 0,
"task": 13568,
"opcode": 0,
"keywords": 9232379236109516800,
"time_created": "2023-11-05T23:49:58.098445+00:00",
"event_record_id": 112372,
"correlation": {
"ActivityID": "E4DB489E-1037-0001-0C49-DBE43710DA01"
},
"execution": {
"process_id": 808,
"thread_id": 8228
},
"channel": "Security",
"computer": "WinDev2310Eval",
"security": {
"user_id": ""
}
},
"event_data": {
"SubjectUserSid": "S-1-5-18",
"SubjectUserName": "WINDEV2310EVAL$",
"SubjectDomainName": "WORKGROUP",
"SubjectLogonId": "0x3e7",
"CategoryId": "%%8279",
"SubcategoryId": "%%14080",
"SubcategoryGuid": "0CCE923B-69AE-11D9-BED3-505054503030",
"AuditPolicyChanges": "%%8449, %%8451",
"ClientProcessId": 8540,
"ClientProcessStartKey": 3659174697239635
},
"message": ""
}
Community Notes #
System audit policy changed. Attackers often disable auditing to reduce detection.
Detection Rules #
View all rules referencing this event →
Sigma # view in reference
- Windows Event Auditing Disabled source low: Detects scenarios where system auditing (i.e.: Windows event log auditing) is disabled. This may be used in a scenario where an entity would want to bypass local logging to evade detection when Windows event logging is enabled and reviewed. Also, it is recommended to turn off "Local Group Policy Object Processing" via GPO, which will make sure that Active Directory GPOs take precedence over local/edited computer policies via something such as "gpedit.msc". Please note, that disabling "Local Group Policy Object Processing" may cause an issue in scenarios of one off specific GPO modifications - however, it is recommended to perform these modifications in Active Directory anyways.
- Important Windows Event Auditing Disabled source high: Detects scenarios where system auditing for important events such as "Process Creation" or "Logon" events is disabled.
Elastic # view in reference
- Sensitive Audit Policy Sub-Category Disabled source medium: Identifies attempts to disable auditing for some security sensitive audit policy sub-categories. This is often done by attackers in an attempt to evade detection and forensics on a system.
Splunk # view in reference
- Windows AD Domain Controller Audit Policy Disabled source: The following analytic detects the disabling of audit policies on a domain controller. It leverages EventCode 4719 from Windows Security Event Logs to identify changes where success or failure auditing is removed. This activity is significant as it suggests an attacker may have gained access to the domain controller and is attempting to evade detection by tampering with audit policies. If confirmed malicious, this could lead to severe consequences, including data theft, privilege escalation, and full network compromise. Immediate investigation is required to determine the source and intent of the change.
- Windows Important Audit Policy Disabled source: The following analytic detects the disabling of important audit policies. It leverages EventCode 4719 from Windows Security Event Logs to identify changes where success or failure auditing is removed. This activity is significant as it suggests an attacker may have gained access to the domain controller and is attempting to evade detection by tampering with audit policies. If confirmed malicious, this could lead to severe consequences, including data theft, privilege escalation, and full network compromise. Immediate investigation is required to determine the source and intent of the change.
References #
- Microsoft Learn https://learn.microsoft.com/en-us/windows/security/threat-protection/auditing/event-4719
- Microsoft Learn Audit Policy https://learn.microsoft.com/en-us/windows/security/threat-protection/auditing/audit-audit-policy-change
- Ultimate Windows Security https://www.ultimatewindowssecurity.com/securitylog/encyclopedia/event.aspx?eventid=4719
- Example event sourced from https://github.com/NextronSystems/evtx-baseline