Auditing: Windows must be configured to audit Logon/Logoff - Account Lockout Failures

bdab6cee-183b-4d5c-a916-853606d1a192

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.Satisfies: SRG-OS-000240-GPOS-00090, SRG-OS-000470-GPOS-00214

Remediation

To fix this 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.

STIG: Server
2022: https://system32.eventsentry.com/stig/viewer/V-254309
2019: https://system32.eventsentry.com/stig/viewer/V-205730
2016: https://system32.eventsentry.com/stig/viewer/V-224890

Desktop
W11: https://system32.eventsentry.com/stig/viewer/V-253313
W10: https://system32.eventsentry.com/stig/viewer/V-220755

NIST 800-53 : AU-2, AU-3, AU-12, AC-7, SI-4
NIST 800-171: 3.3.1, 3.3.2, 3.1.8
CMMC v2.0 L2: AU.L2-3.3.1, AU.L2-3.3.2, AC.L2-3.1.8
PCI-DSS v4.0: 10.2.1, 10.2.1.3
HIPAA SR : §164.312(b), §164.312(d)
HIPAA HICP : Practice 3 (Identity and Access Management), Practice 8 (Incident Response)