STIGhubSTIGhub
STIGsRMF ControlsCompare

STIGhub

A free tool to search and browse the entire DISA STIG library. Saves up to 75% in security compliance research time.

Navigation

  • Browse STIGs
  • Search
  • RMF Controls
  • Compare Versions

Resources

  • About
  • Release Notes
  • VPAT
  • DISA STIG Library
STIGs updated 3 hours ago
Powered by Pylon
© 2026 Beacon Cloud Solutions, Inc. All rights reserved.
← Back to Microsoft Windows Server 2025 Security Technical Implementation Guide

V-278035

CAT II (Medium)

Windows Server 2025 must have the period of time before the bad logon counter is reset configured to 15 minutes or greater.

Rule ID

SV-278035r1180811_rule

STIG

Microsoft Windows Server 2025 Security Technical Implementation Guide

Version

V1R1

CCIs

CCI-000044

Discussion

When enabled, the account lockout feature prevents brute-force password attacks on the system. This parameter specifies the period of time that must pass after failed logon attempts before the counter is reset to "0". The smaller this value is, the less effective the account lockout feature will be in protecting the local system.

Check Content

Verify the effective setting in Local Group Policy Editor.

Run gpedit.msc.

Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Account Policies >> Account Lockout Policy.

If the "Reset account lockout counter after" value is less than "15" minutes, this is a finding.

For server core installations, run the following command:

Secedit /Export /Areas SecurityPolicy /CFG C:\Path\FileName.Txt

If "ResetLockoutCount" is less than "15" in the file, this is a finding.

Fix Text

Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Account Policies >> Account Lockout Policy. Set "Reset account lockout counter after" to at least "15" minutes.