| 1.1.1.2 Set 'Account lockout duration' to '15 or more minute(s)' | CIS Windows 8 L1 v1.0.0 | Windows | ACCESS CONTROL |
| 1.1.1.3 Set 'Reset account lockout counter after' to '15 minute(s)' | CIS Windows 8 L1 v1.0.0 | Windows | ACCESS CONTROL |
| 1.2.2 Ensure 'Account lockout threshold' is set to '10 or fewer invalid logon attempt(s), but not 0' | CIS Windows 7 Workstation Level 1 v3.2.0 | Windows | ACCESS CONTROL |
| 1.2.3 Ensure 'Reset account lockout counter after' is set to '15 or more minute(s)' | CIS Windows 7 Workstation Level 1 + Bitlocker v3.2.0 | Windows | ACCESS CONTROL |
| 1.4.2 Ensure 'Failed Attempts' and 'Lockout Time' for Authentication Profile are properly configured - Failed Attempts | CIS Palo Alto Firewall 7 Benchmark L1 v1.0.0 | Palo_Alto | ACCESS CONTROL |
| 1.4.2 Ensure 'Failed Attempts' and 'Lockout Time' for Authentication Profile are properly configured - Failed Attempts | CIS Palo Alto Firewall 6 Benchmark L1 v1.0.0 | Palo_Alto | ACCESS CONTROL |
| 5.3.1 Ensure password creation requirements are configured - 'retry=3' | CIS Ubuntu Linux 14.04 LTS Server L1 v2.1.0 | Unix | ACCESS CONTROL |
| 5.3.2 Ensure lockout for failed password attempts is configured - password-auth 'auth required pam_faillock.so preauth audit silent deny=5 unlock_time=900' | CIS Amazon Linux v2.1.0 L1 | Unix | ACCESS CONTROL |
| 5.3.2 Ensure lockout for failed password attempts is configured - system-auth 'auth sufficient pam_faillock.so authsucc audit deny=5 unlock_time=900' | CIS Amazon Linux v2.1.0 L1 | Unix | ACCESS CONTROL |
| 6.4 Limit Consecutive Login Attempts for SSH | CIS Solaris 11.2 L1 v1.1.0 | Unix | ACCESS CONTROL |
| 6.6 Set Delay between Failed Login Attempts to 4. | CIS Solaris 10 L1 v5.2 | Unix | ACCESS CONTROL |
| 6.10 Set Delay between Failed Login Attempts to 4 | CIS Solaris 11.2 L1 v1.1.0 | Unix | ACCESS CONTROL |
| 6.10 Set Delay between Failed Login Attempts to 4 - SLEEPTIME = 4 | CIS Solaris 11 L1 v1.1.0 | Unix | ACCESS CONTROL |
| 6.11 Set Retry Limit for Account Lockout - Check if 'RETRIES' in /etc/default/login is set to 3. | CIS Solaris 10 L1 v5.2 | Unix | ACCESS CONTROL |
| 6.15 Set Retry Limit for Account Lockout - LOCK_AFTER_RETRIES = yes | CIS Solaris 11.2 L1 v1.1.0 | Unix | ACCESS CONTROL |
| 6.15 Set Retry Limit for Account Lockout - RETRIES = 3 | CIS Solaris 11.2 L1 v1.1.0 | Unix | ACCESS CONTROL |
| 6.15 Set Retry Limit for Account Lockout - LOCK_AFTER_RETRIES = yes | CIS Solaris 11.1 L1 v1.0.0 | Unix | ACCESS CONTROL |
| 6.15 Set Retry Limit for Account Lockout - LOCK_AFTER_RETRIES = yes | CIS Solaris 11 L1 v1.1.0 | Unix | ACCESS CONTROL |
| 9.2.2 Set Lockout for Failed Password Attempts | CIS Debian Linux 7 L1 v1.0.0 | Unix | ACCESS CONTROL |
| 9.3.5 Set SSH MaxAuthTries to 4 or Less | CIS Ubuntu 12.04 LTS Benchmark L1 v1.1.0 | Unix | ACCESS CONTROL |
| Account lockout duration | MSCT Windows 10 v2004 v1.0.0 | Windows | ACCESS CONTROL |
| Account lockout duration | MSCT Windows 10 v21H2 v1.0.0 | Windows | ACCESS CONTROL |
| Account lockout duration | MSCT Windows Server 1903 DC v1.19.9 | Windows | ACCESS CONTROL |
| Account lockout duration | MSCT Windows Server 1903 MS v1.19.9 | Windows | ACCESS CONTROL |
| Account lockout duration | MSCT Windows Server v2004 MS v1.0.0 | Windows | ACCESS CONTROL |
| Account lockout duration | MSCT Windows Server v20H2 MS v1.0.0 | Windows | ACCESS CONTROL |
| Account lockout threshold | MSCT Windows Server 2012 R2 MS v1.0.0 | Windows | ACCESS CONTROL |
| Account lockout threshold | MSCT Windows 10 1803 v1.0.0 | Windows | ACCESS CONTROL |
| Ensure SSH MaxAuthTries is set to 4 or less | Tenable Cisco Firepower Management Center OS Best Practices Audit | Unix | ACCESS CONTROL |
| Extreme : Configure max-failed-logins <= 3 | TNS Extreme ExtremeXOS Best Practice Audit | Extreme_ExtremeXOS | ACCESS CONTROL |
| FireEye - AAA lockouts delay further attempts for at least 30 seconds | TNS FireEye | FireEye | ACCESS CONTROL |
| Fortigate - Admin password lockout >= 300 seconds | TNS Fortigate FortiOS Best Practices v2.0.0 | FortiGate | ACCESS CONTROL |
| IBM i : Maximum Sign-On Attempts (QMAXSIGN) - '<=3' | IBM System i Security Reference for V7R2 | AS/400 | ACCESS CONTROL |
| Interactive logon: Machine account lockout threshold | MSCT Windows 10 1909 v1.0.0 | Windows | ACCESS CONTROL |
| Interactive logon: Machine account lockout threshold | MSCT Windows Server v1909 DC v1.0.0 | Windows | ACCESS CONTROL |
| Interactive logon: Machine account lockout threshold | MSCT Windows Server 2016 MS v1.0.0 | Windows | ACCESS CONTROL |
| Interactive logon: Machine account lockout threshold | MSCT Windows 10 v1507 v1.0.0 | Windows | ACCESS CONTROL |
| Interactive logon: Machine account lockout threshold | MSCT Windows Server 1903 MS v1.19.9 | Windows | ACCESS CONTROL |
| Interactive logon: Machine account lockout threshold | MSCT Windows Server v20H2 DC v1.0.0 | Windows | ACCESS CONTROL |
| Reset account lockout counter after | MSCT Windows 10 1803 v1.0.0 | Windows | ACCESS CONTROL |
| Reset account lockout counter after | MSCT Windows 10 1809 v1.0.0 | Windows | ACCESS CONTROL |
| Reset account lockout counter after | MSCT Windows 10 1909 v1.0.0 | Windows | ACCESS CONTROL |
| Reset account lockout counter after | MSCT Windows 10 v20H2 v1.0.0 | Windows | ACCESS CONTROL |
| Reset account lockout counter after | MSCT Windows Server 1903 MS v1.19.9 | Windows | ACCESS CONTROL |
| Reset account lockout counter after | MSCT Windows Server v2004 MS v1.0.0 | Windows | ACCESS CONTROL |
| Reset account lockout counter after | MSCT Windows Server 2019 DC v1.0.0 | Windows | ACCESS CONTROL |
| Reset account lockout counter after | MSCT Windows 10 v21H2 v1.0.0 | Windows | ACCESS CONTROL |
| Reset account lockout counter after | MSCT Windows Server v1909 MS v1.0.0 | Windows | ACCESS CONTROL |
| Reset lockout counter after | MSCT Windows Server 2012 R2 MS v1.0.0 | Windows | ACCESS CONTROL |
| Reset lockout counter after | MSCT Windows Server 2016 DC v1.0.0 | Windows | ACCESS CONTROL |
