17.5.1 Ensure 'Audit Account Lockout' is set to include 'Failure'

Warning! Audit Deprecated

This audit has been deprecated and will be removed in a future update.

View Next Audit Version

Information

This subcategory reports when a user's account is locked out as a result of too many failed logon attempts. Events for this subcategory include:

4625: An account failed to log on.

The recommended state for this setting is to include: Failure.

Rationale:

Auditing these events may be useful when investigating a security incident.

Solution

To establish the recommended configuration via GP, set the following UI path to include Failure:

Computer Configuration\Policies\Windows Settings\Security Settings\Advanced Audit Policy Configuration\Audit Policies\Logon/Logoff\Audit Account Lockout

Impact:

If no audit settings are configured, or if audit settings are too lax on the computers in your organization, security incidents might not be detected or not enough evidence will be available for network forensic analysis after security incidents occur. However, if audit settings are too severe, critically important entries in the Security log may be obscured by all of the meaningless entries and computer performance and the available amount of data storage may be seriously affected. Companies that operate in certain regulated industries may have legal obligations to log certain events or activities.

Default Value:

Success.

See Also

https://workbench.cisecurity.org/files/2646