SV-29638r1: Time before bad-logon counter is reset does not meet minimum requirements. | Windows Vista Security Technical Implementation Guide

Loading benchmark…

Assessment Title

Rule Text

Time before bad-logon counter is reset does not meet minimum requirements.

Description

Discussion Text

This parameter specifies the amount of time that must pass between two successive login attempts to ensure that a lockout will occur. The smaller this value is, the less effective the account lockout feature will be in protecting the local system.

How this relates to the STIG checklist: STIG vs SCAP benchmark.

IA Controls

NIST SP 800-53

Not mappedCCI-000044Not mappedCCI-002238CCE-2715-1

Additional Details

Third-Party Tools

Responsibility

System Administrator

References

DPMS Target Windows Vista DISA DPMS Target Windows Vista 1029

SCC Automation Reference

The reconstructed evaluation script behind this rule's OVAL check(s) — every module a compound check combines, with this rule's own concrete values and DISA's SCC tool's real per-module mechanism curated from static teardown of SCC releases.

# Windows PowerShell
# Reconstructed from oval:mil.disa.fso.windows:def:105
# Time before bad-logon counter is reset does not meet minimum requirements.
# Per-module read mechanism curated from static teardown of DISA's SCC tool
# (SCAP Compliance Checker) -- see the SCC Automation Reference above.

# Ensure lockout counter is greater than or equal to 60 minutes
# lockoutpolicy_object (lockoutpolicy_test)
function test_1 {
  return (((net accounts | Select-String 'Lockout observation window') -replace '[^0-9]','') -ge 3600)
}
# checks account lockout threshold policy setting is not equal to 0
# lockoutpolicy_object (lockoutpolicy_test)
function test_2 {
  return (((net accounts | Select-String 'Lockout threshold') -replace '[^0-9]','') -ne 0)
}

if (-not ((test_1 -and test_2))) {
  Write-Output "PASS"
} else {
  Write-Output "FAIL"
}

Assessment Script Powered by AISyntax-verified

A standalone PowerShell script to assess this control automatically. Review before running it in your environment.

Syntax-checked as valid PowerShell. Not executed here — running it for real needs the actual windows_vista target this check assesses.

# OVAL Definition: oval:mil.disa.fso.windows:def:105
$lockoutPolicy = Get-CimInstance -ClassName Win32_LocalSystemGroupPolicyElement -Filter "SettingName = 'LockoutObservationWindow'"
if ($lockoutPolicy -and $lockoutPolicy.SettingValue -ge 3600 -and (Get-CimInstance -ClassName Win32_LocalSystemGroupPolicyElement -Filter "SettingName = 'LockoutThreshold'").SettingValue -ne 0) { Write-Output "PASS"; Exit 0 } else { Write-Output "FAIL"; Exit 1 }

Remediation

Configure the system to have the lockout counter reset itself after a minimum of 60 minutes.