Microsoft Windows Server 2012/2012 R2 Member Server STIG:
(in versions v3 r7 through v2 r11)
Windows Server 2012/2012 R2 must be configured to audit Logon/Logoff - Account Lockout failures. (Cat II impact)
Maintaining an audit trail of system activity logs can help identify configuration errors, troubleshoot service disruptions, and analyze compromises that have occurred, as well as detect attacks. Audit logs are necessary to provide a trail of evidence in case the system or network is compromised. Collecting this data is essential for analyzing the security of information assets and detecting signs of suspicious and unexpected behavior. Account Lockout events can be used to identify potentially malicious logon attempts.
Security Option "Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" must be set to "Enabled" (V-14230) for the detailed auditing subcategories to be effective. Use the AuditPol tool to review the current Audit Policy configuration: Open an elevated "Command Prompt" (run as administrator). Enter "AuditPol /get /category:*" Compare the AuditPol settings with the following. If the system does not audit the following, this is a finding. Logon/Logoff >> Account Lockout - Failure
Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Advanced Audit Policy Configuration >> System Audit Policies >> Logon/Logoff >> "Audit Account Lockout" with "Failure" selected.
Rule ID: SV-225283r569185_rule
Vulnerability ID: V-225283
Group Title: SRG-OS-000470-GPOS-00214
The information system generates audit records for the events defined in AU-2 d. with the content defined in AU-3.
The information system automatically audits account disabling actions.