ANAVEM
Languagefr
Windows security monitoring dashboard showing Event Viewer Security logs and audit policy management interface
Event ID 4692InformationMicrosoft-Windows-Security-AuditingWindows

Windows Event ID 4692 – Microsoft-Windows-Security-Auditing: An attempt was made to backup the security audit policy

Event ID 4692 fires when Windows attempts to backup the security audit policy configuration. This security audit event tracks policy backup operations for compliance and forensic purposes.

Emanuel DE ALMEIDAEmanuel DE ALMEIDA
18 March 202612 min read 0
Event ID 4692Microsoft-Windows-Security-Auditing 5 methods 12 min
Event Reference

What This Event Means

Windows Event ID 4692 represents a critical component of the Windows security auditing framework, specifically designed to track attempts to backup security audit policy configurations. This event is generated by the Microsoft-Windows-Security-Auditing provider and appears exclusively in the Security event log.

The event captures comprehensive information about the backup operation, including the user account that initiated the backup, the process responsible for the operation, and timestamps for forensic analysis. The audit policy backup functionality is essential for maintaining consistent security configurations across enterprise environments and ensuring compliance with regulatory requirements.

When this event fires, it indicates that either a manual backup operation was initiated through administrative tools, or an automated process attempted to preserve the current audit policy settings. The event provides visibility into policy management activities, which is crucial for security teams monitoring configuration changes and maintaining audit trails.

In modern Windows environments, this event often correlates with Group Policy deployments, PowerShell-based automation scripts, or third-party security management tools that interact with Windows audit policies. The event structure includes detailed information about the backup operation's success or failure status, enabling administrators to quickly identify and resolve policy management issues.

Applies to

Windows 10Windows 11Windows Server 2019/2022/2025
Analysis

Possible Causes

  • Manual execution of auditpol /backup command by administrators
  • PowerShell scripts using Backup-AuditPolicy cmdlet or equivalent functions
  • Group Policy management operations that backup existing audit configurations
  • Third-party security management tools performing policy backup operations
  • Automated backup scripts scheduled through Task Scheduler
  • System restore operations that include audit policy configurations
  • Enterprise security compliance tools backing up audit settings
  • Windows Update processes that preserve audit policy during system updates
Resolution Methods

Troubleshooting Steps

01

Review Event Details in Event Viewer

Start by examining the specific details of Event ID 4692 to understand the context of the backup attempt.

  1. Open Event Viewer by pressing Win + R, typing eventvwr.msc, and pressing Enter
  2. Navigate to Windows LogsSecurity
  3. Filter the log for Event ID 4692 by right-clicking the Security log and selecting Filter Current Log
  4. Enter 4692 in the Event IDs field and click OK
  5. Double-click on the most recent Event ID 4692 entry to view detailed information
  6. Review the General tab for basic event information including timestamp and user account
  7. Check the Details tab for XML data containing process information and backup parameters
  8. Note the Subject section showing the security identifier and account name of the user who initiated the backup
Pro tip: The Task Category field will show "Audit Policy Change" which helps categorize this as a policy management operation rather than a security breach.
02

Query Events Using PowerShell

Use PowerShell to programmatically retrieve and analyze Event ID 4692 occurrences for pattern analysis.

  1. Open PowerShell as Administrator
  2. Run the following command to retrieve recent Event ID 4692 entries:
Get-WinEvent -FilterHashtable @{LogName='Security'; Id=4692} -MaxEvents 50 | Format-Table TimeCreated, Id, LevelDisplayName, Message -Wrap
  1. For more detailed analysis, extract specific properties:
Get-WinEvent -FilterHashtable @{LogName='Security'; Id=4692} -MaxEvents 10 | ForEach-Object {
    $xml = [xml]$_.ToXml()
    [PSCustomObject]@{
        TimeCreated = $_.TimeCreated
        UserName = $xml.Event.EventData.Data | Where-Object {$_.Name -eq 'SubjectUserName'} | Select-Object -ExpandProperty '#text'
        ProcessName = $xml.Event.EventData.Data | Where-Object {$_.Name -eq 'ProcessName'} | Select-Object -ExpandProperty '#text'
        BackupFile = $xml.Event.EventData.Data | Where-Object {$_.Name -eq 'BackupFile'} | Select-Object -ExpandProperty '#text'
    }
}
  1. To check for failed backup attempts, correlate with other audit policy events:
Get-WinEvent -FilterHashtable @{LogName='Security'; Id=4719,4692} -MaxEvents 20 | Sort-Object TimeCreated
Warning: Running these commands on domain controllers or high-traffic systems may return large result sets. Use -MaxEvents parameter to limit output.
03

Verify Audit Policy Configuration

Check the current audit policy settings to understand what configuration is being backed up and ensure proper policy application.

  1. Open Command Prompt as Administrator
  2. Display current audit policy settings:
auditpol /get /category:*
  1. Check for recent policy changes that might trigger backup operations:
auditpol /get /category:"Policy Change"
  1. Review the backup file location if specified in the event details:
Get-ChildItem -Path "C:\Windows\System32\config" -Filter "*.csv" | Where-Object {$_.Name -like "*audit*"} | Sort-Object LastWriteTime -Descending
  1. Verify Group Policy audit settings using PowerShell:
Get-GPO -All | Where-Object {$_.DisplayName -like "*audit*"} | ForEach-Object {
    Write-Host "GPO: $($_.DisplayName)"
    Get-GPOReport -Guid $_.Id -ReportType Xml | Select-String -Pattern "audit"
}
  1. Check if the backup operation completed successfully by examining the backup file:
$BackupPath = "C:\temp\audit_backup.csv"
if (Test-Path $BackupPath) {
    Import-Csv $BackupPath | Select-Object -First 10
} else {
    Write-Host "Backup file not found at expected location"
}
04

Investigate Process and User Context

Analyze the process and user context that initiated the audit policy backup to determine if the operation was legitimate or requires further investigation.

  1. Extract detailed process information from the event XML:
$Events = Get-WinEvent -FilterHashtable @{LogName='Security'; Id=4692} -MaxEvents 5
foreach ($Event in $Events) {
    $xml = [xml]$Event.ToXml()
    $ProcessId = ($xml.Event.EventData.Data | Where-Object {$_.Name -eq 'ProcessId'}).'#text'
    $ProcessName = ($xml.Event.EventData.Data | Where-Object {$_.Name -eq 'ProcessName'}).'#text'
    $SubjectUserName = ($xml.Event.EventData.Data | Where-Object {$_.Name -eq 'SubjectUserName'}).'#text'
    
    Write-Host "Event Time: $($Event.TimeCreated)"
    Write-Host "Process: $ProcessName (PID: $ProcessId)"
    Write-Host "User: $SubjectUserName"
    Write-Host "---"
}
  1. Check if the process is still running and gather additional context:
Get-Process | Where-Object {$_.ProcessName -like "*audit*" -or $_.ProcessName -eq "powershell" -or $_.ProcessName -eq "cmd"} | Select-Object ProcessName, Id, StartTime, CPU
  1. Review recent logon events for the user account that initiated the backup:
Get-WinEvent -FilterHashtable @{LogName='Security'; Id=4624,4625} -MaxEvents 20 | Where-Object {$_.Message -like "*username_from_event*"} | Format-Table TimeCreated, Id, Message -Wrap
  1. Check scheduled tasks that might be performing automated backups:
Get-ScheduledTask | Where-Object {$_.TaskName -like "*audit*" -or $_.TaskName -like "*backup*"} | ForEach-Object {
    $TaskInfo = Get-ScheduledTaskInfo -TaskName $_.TaskName
    [PSCustomObject]@{
        TaskName = $_.TaskName
        State = $_.State
        LastRunTime = $TaskInfo.LastRunTime
        NextRunTime = $TaskInfo.NextRunTime
        Author = $_.Author
    }
}
Pro tip: Cross-reference the process name and user account with your organization's approved automation tools and service accounts to quickly identify legitimate operations.
05

Configure Advanced Monitoring and Alerting

Implement comprehensive monitoring for audit policy backup operations to ensure proper oversight and rapid response to unauthorized changes.

  1. Create a custom Windows Event Forwarding subscription for centralized monitoring:
<Subscription xmlns="http://schemas.microsoft.com/2006/03/windows/events/subscription">
    <SubscriptionId>AuditPolicyBackup</SubscriptionId>
    <SubscriptionType>SourceInitiated</SubscriptionType>
    <Description>Monitor audit policy backup operations</Description>
    <Enabled>true</Enabled>
    <Uri>http://schemas.microsoft.com/wbem/wsman/1/windows/EventLog</Uri>
    <Query>
        <![CDATA[
        <QueryList>
            <Query Id="0">
                <Select Path="Security">*[System[EventID=4692]]</Select>
            </Query>
        </QueryList>
        ]]>
    </Query>
</Subscription>
  1. Set up PowerShell-based alerting using Windows Event Log monitoring:
# Create monitoring script
$ScriptBlock = {
    Register-WmiEvent -Query "SELECT * FROM Win32_NTLogEvent WHERE LogFile='Security' AND EventCode=4692" -Action {
        $Event = $Event.SourceEventArgs.NewEvent
        $Message = "Audit Policy Backup Detected: User=$($Event.User), Time=$($Event.TimeGenerated)"
        Write-EventLog -LogName Application -Source "Custom Monitor" -EventId 1001 -Message $Message
        # Add email notification or SIEM integration here
    }
}

# Register the event monitoring job
Start-Job -ScriptBlock $ScriptBlock -Name "AuditPolicyMonitor"
  1. Configure Group Policy to audit policy change events:

Navigate to Computer ConfigurationWindows SettingsSecurity SettingsAdvanced Audit Policy ConfigurationPolicy Change and enable:

  • Audit Policy Change - Success and Failure
  • Audit Authentication Policy Change - Success and Failure
  1. Create a custom PowerShell function for regular audit policy backup monitoring:
function Monitor-AuditPolicyBackups {
    param(
        [int]$Hours = 24,
        [string]$OutputPath = "C:\temp\audit_policy_report.csv"
    )
    
    $StartTime = (Get-Date).AddHours(-$Hours)
    $Events = Get-WinEvent -FilterHashtable @{
        LogName = 'Security'
        Id = 4692
        StartTime = $StartTime
    } -ErrorAction SilentlyContinue
    
    $Results = foreach ($Event in $Events) {
        $xml = [xml]$Event.ToXml()
        [PSCustomObject]@{
            TimeCreated = $Event.TimeCreated
            UserName = ($xml.Event.EventData.Data | Where-Object {$_.Name -eq 'SubjectUserName'}).'#text'
            ProcessName = ($xml.Event.EventData.Data | Where-Object {$_.Name -eq 'ProcessName'}).'#text'
            BackupFile = ($xml.Event.EventData.Data | Where-Object {$_.Name -eq 'BackupFile'}).'#text'
        }
    }
    
    $Results | Export-Csv -Path $OutputPath -NoTypeInformation
    Write-Host "Report saved to: $OutputPath"
    return $Results
}

# Usage example
Monitor-AuditPolicyBackups -Hours 168 # Last 7 days
Warning: Ensure proper permissions are configured for event forwarding and monitoring scripts to prevent unauthorized access to security event data.

Overview

Event ID 4692 is a security audit event that fires whenever Windows attempts to backup the security audit policy configuration. This event appears in the Security log and is part of Windows' comprehensive audit policy tracking system. The event captures details about who initiated the backup, when it occurred, and whether the operation succeeded or failed.

This event is particularly relevant in enterprise environments where audit policy configurations need to be preserved for compliance requirements or disaster recovery scenarios. The backup operation can be triggered through Group Policy management tools, PowerShell cmdlets, or administrative utilities like auditpol.exe. Security administrators rely on this event to track changes to audit configurations and ensure proper governance of security logging policies.

The event fires regardless of whether the backup operation completes successfully, making it valuable for troubleshooting failed policy backup attempts. In Windows Server 2025 and the latest Windows 11 builds, enhanced logging provides additional context about the backup destination and policy scope.

Frequently Asked Questions

What does Event ID 4692 mean and when does it occur?+
Event ID 4692 indicates that Windows attempted to backup the security audit policy configuration. This event fires whenever the audit policy backup operation is initiated, whether through manual commands like 'auditpol /backup', PowerShell cmdlets, Group Policy operations, or automated scripts. The event appears in the Security log and provides details about who initiated the backup, when it occurred, and the process responsible for the operation. This is a normal administrative operation used for compliance, disaster recovery, or configuration management purposes.
How can I determine if an Event ID 4692 represents a legitimate backup operation?+
To verify legitimacy, examine the event details including the user account, process name, and timing. Legitimate backups typically originate from known administrative accounts, recognized processes like auditpol.exe or PowerShell, and occur during scheduled maintenance windows. Cross-reference the event timestamp with your organization's backup schedules, change management records, and approved automation tools. Check if the backup file was created successfully and review recent Group Policy deployments that might trigger policy backups. Unusual timing, unknown user accounts, or suspicious process names warrant further investigation.
Can Event ID 4692 indicate a security threat or malicious activity?+
While Event ID 4692 typically represents legitimate administrative activity, it could potentially indicate malicious behavior if an attacker is attempting to backup audit policies before making unauthorized changes. Red flags include backups initiated by unexpected user accounts, unusual timing (outside business hours), or correlation with other suspicious events like privilege escalation or policy modifications. However, the backup operation itself is not inherently malicious - it's the context and subsequent actions that determine threat level. Monitor for patterns of policy backup followed by policy changes or system compromise indicators.
What information is captured in Event ID 4692 and how can I extract it?+
Event ID 4692 captures comprehensive information including the subject user's security identifier and account name, the process ID and name that initiated the backup, timestamp details, and potentially the backup file location. To extract this information, use PowerShell with Get-WinEvent and XML parsing to access the EventData fields. Key fields include SubjectUserName, ProcessName, ProcessId, and BackupFile. The event also includes logon session information and may contain additional context about the backup operation's scope and destination. Use the event's XML structure to programmatically extract and analyze these details for reporting or investigation purposes.
How should I configure monitoring and alerting for Event ID 4692 in an enterprise environment?+
For enterprise monitoring, implement Windows Event Forwarding to centralize Event ID 4692 collection from all domain systems to a dedicated collector server. Configure SIEM integration to correlate these events with other security activities and establish baseline patterns for legitimate backup operations. Set up automated alerting for backups occurring outside approved maintenance windows or initiated by unauthorized accounts. Use PowerShell-based monitoring scripts with scheduled tasks to generate regular reports on audit policy backup activities. Consider implementing approval workflows for policy changes and ensure all backup operations are logged in your change management system for compliance and audit trail purposes.
Documentation

References (2)

Emanuel DE ALMEIDA
Written by

Emanuel DE ALMEIDA

Senior IT Journalist & Cloud Architect

Microsoft MCSA-certified Cloud Architect | Fortinet-focused. I modernize cloud, hybrid & on-prem infrastructure for reliability, security, performance and cost control - sharing field-tested ops & troubleshooting.

Discussion

Share your thoughts and insights

You must be logged in to comment.

Loading comments...