CCI-000044
Enforce the organization-defined limit of consecutive invalid logon attempts by a user during the organization-defined time period.
9 rules found Severity: Medium
9 rules found Severity: Medium
9 rules found Severity: Medium
2 rules found Severity: Medium
1 rule found Severity: Medium
1 rule found Severity: Medium
Apple iOS/iPadOS 15 must be configured to not allow more than 10 consecutive failed authentication attempts.
1 rule found Severity: Medium
The DBN-6300 must enforce the limit of three consecutive invalid logon attempts by a user during a 15-minute time period.
1 rule found Severity: Medium
The FortiGate device must enforce the limit of three consecutive invalid logon attempts, after which time it must lock out the user account from accessing the device for 15 minutes.
1 rule found Severity: Medium
For the local account, CounterACT must enforce the limit of three consecutive invalid logon attempts by a user during a 15-minute time period.
1 rule found Severity: Medium
Google Android 12 must be configured to not allow more than 10 consecutive failed authentication attempts.
2 rules found Severity: Medium
The HP FlexFabric Switch must enforce the limit of three consecutive invalid logon attempts by a user during a 15-minute time period.
1 rule found Severity: Medium
The HYCU VM console must be configured to enforce the limit of three consecutive invalid logon attempts, after which time it must block any logon attempt for 15 minutes.
1 rule found Severity: Medium
IBM Aspera Console must lock accounts after three unsuccessful login attempts within a 15-minute timeframe.
1 rule found Severity: Medium
IBM Aspera Faspex must lock accounts after three unsuccessful login attempts within a 15-minute timeframe.
1 rule found Severity: Medium
IBM Aspera Shares must lock accounts after three unsuccessful login attempts within a 15-minute timeframe.
1 rule found Severity: Medium
The MQ Appliance network device must enforce the limit of three consecutive invalid logon attempts by a user during a 15-minute time period.
1 rule found Severity: Medium
1 rule found Severity: Medium
1 rule found Severity: Medium
The Ivanti MobileIron Core server must enforce the limit of three consecutive invalid logon attempts by a user during a 15-minute time period.
1 rule found Severity: Medium
MobileIron Sentry must be configured to enforce the limit of three consecutive invalid logon attempts, after which time it must block any login attempt for 15 minutes.
1 rule found Severity: Low
Microsoft Android 11 must be configured to not allow more than 10 consecutive failed authentication attempts.
2 rules found Severity: Medium
Motorola Solutions Android 11 must be configured to not allow more than ten consecutive failed authentication attempts.
1 rule found Severity: Low
Nutanix AOS must enforce the limit of three consecutive invalid logon attempts by a user during a 15-minute time period.
1 rule found Severity: Medium
Oracle WebLogic must limit the number of failed login attempts to an organization-defined number of consecutive invalid attempts that occur within an organization-defined time period.
1 rule found Severity: Medium
Riverbed Optimization System (RiOS) must enforce the limit of three (3) consecutive invalid logon attempts by a user during a 15-minute time period for device console access.
1 rule found Severity: Medium
Riverbed Optimization System (RiOS) must enforce the limit of three (3) consecutive invalid logon attempts by a user during a 15-minute time period for web-based management access.
1 rule found Severity: Medium
Samsung Android must be configured to not allow more than 10 consecutive failed authentication attempts.
11 rules found Severity: Medium
1 rule found Severity: Medium
Symantec ProxySG must be configured to enforce the limit of three consecutive invalid logon attempts by a user during a 15-minute time period.
1 rule found Severity: Medium
The NSX-T Manager must be configured to enforce the limit of three consecutive invalid logon attempts, after which time it must block any login attempt for 15 minutes.
1 rule found Severity: Medium
1 rule found Severity: High
Apple iOS/iPadOS 16 must be configured to not allow more than 10 consecutive failed authentication attempts.
2 rules found Severity: Medium
The Ubuntu operating system must be configured so that three consecutive invalid logon attempts by a user automatically locks the account until released by an administrator.
1 rule found Severity: Medium
The network device must be configured to enforce the limit of three consecutive invalid logon attempts, after which time it must block any login attempt for 15 minutes.
5 rules found Severity: Medium
The Red Hat Enterprise Linux operating system must be configured to lock accounts for a minimum of 15 minutes after three unsuccessful logon attempts within a 15-minute timeframe.
1 rule found Severity: Medium
Zebra Android 11 must be configured to not allow more than 10 consecutive failed authentication attempts.
1 rule found Severity: Low
The BIG-IP appliance must be configured to enforce the limit of three consecutive invalid logon attempts by a user during a 15-minute time period.
1 rule found Severity: Medium
Apple iOS/iPadOS 17 must be configured to not allow more than 10 consecutive failed authentication attempts.
2 rules found Severity: Medium
The Arista network device must be configured to enforce the limit of three consecutive invalid logon attempts, after which time it must block any login attempt for 15 minutes.
1 rule found Severity: Medium
The Ubuntu operating system must automatically lock an account until the locked account is released by an administrator when three unsuccessful logon attempts have been made.
1 rule found Severity: Low
The Cisco router must be configured to enforce the limit of three consecutive invalid logon attempts after which time lock out the user account from accessing the device for 15 minutes.
1 rule found Severity: Medium
The Cisco switch must be configured to enforce the limit of three consecutive invalid logon attempts, after which time it must lock out the user account from accessing the device for 15 minutes.
2 rules found Severity: Medium
The Cisco ISE must be configured to enforce the limit of three consecutive invalid logon attempts, after which time it must lock out the user account from accessing the device for 15 minutes.
1 rule found Severity: Medium
The F5 BIG-IP appliance must be configured to enforce the limit of three consecutive invalid logon attempts, after which time it must block any login attempt for at least 15 minutes.
1 rule found Severity: Medium
Google Android 14 must be configured to not allow more than 10 consecutive failed authentication attempts.
3 rules found Severity: Medium
Google Android 13 must be configured to not allow more than 10 consecutive failed authentication attempts.
3 rules found Severity: Medium
SSMC must enforce the limit of three consecutive invalid logon attempts by a nonadministrative user.
1 rule found Severity: Low
The HPE Nimble must be configured to enforce the limit of three consecutive invalid logon attempts, after which time it must block any login attempt for 15 minutes.
1 rule found Severity: Medium
AIX must enforce the limit of three consecutive invalid login attempts by a user before the user account is locked and released by an administrator.
1 rule found Severity: Medium
1 rule found Severity: Medium
The ICS must be configured to enforce the limit of three consecutive invalid logon attempts, after which time it must block any login attempt for 15 minutes.
1 rule found Severity: Medium
The Ivanti EPMM server must enforce the limit of three consecutive invalid logon attempts by a user during a 15-minute time period.
1 rule found Severity: Medium
Sentry must be configured to enforce the limit of three consecutive invalid logon attempts, after which time it must block any login attempt for 15 minutes.
1 rule found Severity: Low
The Juniper EX switch must be configured to enforce the limit of three consecutive invalid logon attempts for any given user, after which time it must block any login attempt for that user for 15 minutes.
1 rule found Severity: Medium
1 rule found Severity: Medium
1 rule found Severity: Medium
Microsoft Intune service must enforce the limit of three consecutive invalid login attempts by a user during a 15-minute time period.
1 rule found Severity: Medium
1 rule found Severity: Medium
2 rules found Severity: Medium
1 rule found Severity: Medium
1 rule found Severity: Medium
Windows Server 2016 must have the period of time before the bad logon counter is reset configured to 15 minutes or greater.
1 rule found Severity: Medium
1 rule found Severity: Medium
The Oracle Linux operating system must be configured to lock accounts for a minimum of 15 minutes after three unsuccessful logon attempts within a 15-minute timeframe.
1 rule found Severity: Medium
The Riverbed NetProfiler must enforce the limit of three consecutive invalid logon attempts, after which time it must block any login attempt for 30 minutes, at a minimum.
1 rule found Severity: Medium
1 rule found Severity: Medium
Splunk Enterprise must enforce the limit of 3 consecutive invalid logon attempts by a user during a 15 minute time period.
1 rule found Severity: Medium
Splunk Enterprise must enforce the limit of three consecutive invalid logon attempts by a user during a 15-minute time period.
1 rule found Severity: Medium
The TippingPoint SMS must be configured to enforce the limit of three consecutive invalid logon attempts, after which time it must lock out the user account from accessing the device for 15 minutes.
1 rule found Severity: Medium
TOSS must enforce the limit of five consecutive invalid logon attempts by a user during a 15-minute time period.
1 rule found Severity: Medium
1 rule found Severity: Medium
NixOS must enforce the limit of three consecutive invalid login attempts by a user during a 15-minute time period.
1 rule found Severity: Medium
AAA Services must be configured to automatically lock user accounts after three consecutive invalid logon attempts within a 15-minute time period.
1 rule found Severity: Medium
Apple iOS/iPadOS 18 must be configured to not allow more than 10 consecutive failed authentication attempts.
1 rule found Severity: Medium
1 rule found Severity: Medium
1 rule found Severity: Medium
The application must enforce the limit of three consecutive invalid logon attempts by a user during a 15 minute time period.
1 rule found Severity: High
Ubuntu 22.04 LTS must automatically lock an account until the locked account is released by an administrator when three unsuccessful logon attempts have been made.
1 rule found Severity: Low
The Cisco router must be configured to enforce the limit of three consecutive invalid logon attempts, after which time it must lock out the user account from accessing the device for 15 minutes.
2 rules found Severity: Medium
The Central Log Server must enforce the limit of three consecutive invalid logon attempts by a user during a 15 minute time period.
1 rule found Severity: Medium
The Cisco switch must be configured to enforce the limit of three consecutive invalid logon attempts, after which time it must disconnect the session.
1 rule found Severity: Medium
1 rule found Severity: Medium
AlmaLinux OS 9 must automatically lock the root account until the root account is released by an administrator when three unsuccessful logon attempts occur during a 15-minute time period.
1 rule found Severity: Medium
AlmaLinux OS 9 must automatically lock an account when three unsuccessful logon attempts occur during a 15-minute time period.
1 rule found Severity: Medium
AlmaLinux OS 9 must configure the use of the pam_faillock.so module in the /etc/pam.d/system-auth file.
1 rule found Severity: Medium
AlmaLinux OS 9 must configure the use of the pam_faillock.so module in the /etc/pam.d/password-auth file.
1 rule found Severity: Medium
1 rule found Severity: Medium
The container platform must enforce the limit of three consecutive invalid logon attempts by a user during a 15-minute time period.
1 rule found Severity: Medium
The Dell OS10 Switch must be configured to enforce the limit of three consecutive invalid logon attempts, after which time it must block any login attempt for 15 minutes.
1 rule found Severity: Medium
1 rule found Severity: Medium
Forescout must be configured to enforce the limit of three consecutive invalid logon attempts, after which time it must lock out the user account from accessing the device for 15 minutes.
1 rule found Severity: Medium
Google Android 15 must be configured to not allow more than 10 consecutive failed authentication attempts.
2 rules found Severity: Medium
The operating system must enforce the limit of three consecutive invalid logon attempts by a user during a 15-minute time period.
1 rule found Severity: Medium
AOS must be configured to enforce the limit of three consecutive invalid login attempts, after which time it must block any login attempt for 15 minutes.
1 rule found Severity: Medium
The HYCU virtual appliance must be configured to enforce the limit of three consecutive invalid login attempts, after which time it must block any login attempt for 15 minutes.
1 rule found Severity: Medium
The IBM RACF PASSWORD(REVOKE) SETROPTS value must be specified to revoke the userid after three invalid logon attempts.
1 rule found Severity: Medium
The Juniper router must be configured to enforce the limit of three consecutive invalid logon attempts after which time lock out the user account from accessing the device for 15 minutes.
1 rule found Severity: Medium
For local accounts created on the device, the Juniper SRX Services Gateway must enforce the limit of three consecutive invalid logon attempts by a user during a 15-minute time period.
1 rule found Severity: Low
The Mainframe Product must enforce the limit of three consecutive invalid logon attempts by a user during a 15 minute time period.
1 rule found Severity: Medium
1 rule found Severity: Medium
1 rule found Severity: Medium
Windows Server 2019 must have the period of time before the bad logon counter is reset configured to 15 minutes or greater.
1 rule found Severity: Medium
1 rule found Severity: Medium
Windows Server 2022 must have the period of time before the bad logon counter is reset configured to 15 minutes or greater.
1 rule found Severity: Medium
Access to Prisma Cloud Compute must be managed based on user need and least privileged using external identity providers for authentication and grouping to role-based assignments when possible.
1 rule found Severity: Medium
OL 8 systems below version 8.2 must automatically lock an account when three unsuccessful logon attempts occur.
1 rule found Severity: Medium
OL 8 systems, versions 8.2 and above, must automatically lock an account when three unsuccessful logon attempts occur.
1 rule found Severity: Medium
OL 8 systems below version 8.2 must automatically lock an account when three unsuccessful logon attempts occur during a 15-minute time period.
1 rule found Severity: Medium
OL 8 systems, versions 8.2 and above, must automatically lock an account when three unsuccessful logon attempts occur during a 15-minute time period.
1 rule found Severity: Medium
OL 8 systems below version 8.2 must automatically lock an account until the locked account is released by an administrator when three unsuccessful logon attempts occur during a 15-minute time period.
1 rule found Severity: Medium
OL 8 systems, versions 8.2 and above, must automatically lock an account until the locked account is released by an administrator when three unsuccessful logon attempts occur during a 15-minute time period.
1 rule found Severity: Medium
1 rule found Severity: Medium
OL 8 systems below version 8.2 must prevent system messages from being presented when three unsuccessful logon attempts occur.
1 rule found Severity: Medium
OL 8 systems, versions 8.2 and above, must prevent system messages from being presented when three unsuccessful logon attempts occur.
1 rule found Severity: Medium
OL 8 systems below version 8.2 must log user name information when unsuccessful logon attempts occur.
1 rule found Severity: Medium
OL 8 systems, versions 8.2 and above, must log user name information when unsuccessful logon attempts occur.
1 rule found Severity: Medium
OL 8 systems below version 8.2 must include root when automatically locking an account until the locked account is released by an administrator when three unsuccessful logon attempts occur during a 15-minute time period.
1 rule found Severity: Medium
OL 8 systems, versions 8.2 and above, must include root when automatically locking an account until the locked account is released by an administrator when three unsuccessful logon attempts occur during a 15-minute time period.
1 rule found Severity: Medium
1 rule found Severity: Medium
1 rule found Severity: Medium
OL 8 systems, versions 8.2 and above, must configure SELinux context type to allow the use of a non-default faillock tally directory.
1 rule found Severity: Medium
OL 8 systems below version 8.2 must configure SELinux context type to allow the use of a non-default faillock tally directory.
1 rule found Severity: Medium
The Palo Alto Networks security platform must enforce the limit of three consecutive invalid logon attempts.
1 rule found Severity: Medium
2 rules found Severity: Medium
RHEL 8 must automatically lock an account when three unsuccessful logon attempts occur during a 15-minute time period.
2 rules found Severity: Medium
RHEL 8 must automatically lock an account until the locked account is released by an administrator when three unsuccessful logon attempts occur during a 15-minute time period.
2 rules found Severity: Medium
RHEL 8 must prevent system messages from being presented when three unsuccessful logon attempts occur.
2 rules found Severity: Medium
2 rules found Severity: Medium
RHEL 8 must include root when automatically locking an account until the locked account is released by an administrator when three unsuccessful logon attempts occur during a 15-minute time period.
2 rules found Severity: Medium
1 rule found Severity: Medium
1 rule found Severity: Medium
RHEL 8 systems, versions 8.2 and above, must configure SELinux context type to allow the use of a non-default faillock tally directory.
1 rule found Severity: Medium
RHEL 8 systems below version 8.2 must configure SELinux context type to allow the use of a non-default faillock tally directory.
1 rule found Severity: Medium
1 rule found Severity: Medium
RHEL 9 must automatically lock the root account until the root account is released by an administrator when three unsuccessful logon attempts occur during a 15-minute time period.
1 rule found Severity: Medium
RHEL 9 must automatically lock an account when three unsuccessful logon attempts occur during a 15-minute time period.
1 rule found Severity: Medium
1 rule found Severity: Medium
1 rule found Severity: Medium
RHEL 9 must configure SELinux context type to allow the use of a nondefault faillock tally directory.
1 rule found Severity: Medium
1 rule found Severity: Medium
1 rule found Severity: Medium
2 rules found Severity: Medium
2 rules found Severity: Medium
The VMM must enforce the limit of three consecutive invalid logon attempts by a user during a 15-minute time period.
1 rule found Severity: Medium
The UEM server must enforce the limit of three consecutive invalid logon attempts by a user during a 15-minute time period.
1 rule found Severity: Medium
The NSX Manager must be configured to enforce the limit of three consecutive invalid logon attempts, after which time it must block any login attempt for 15 minutes.
1 rule found Severity: Medium
3 rules found Severity: Medium
The Photon operating system must automatically lock an account when three unsuccessful logon attempts occur.
1 rule found Severity: Medium
3 rules found Severity: Medium
The Photon operating system must enforce the limit of three consecutive invalid logon attempts by a user during a 15-minute time period.
2 rules found Severity: Medium
2 rules found Severity: Medium
2 rules found Severity: Medium
2 rules found Severity: Medium
The Photon operating system must include root when automatically locking an account until the locked account is released by an administrator when three unsuccessful logon attempts occur during a 15-minute time period.
2 rules found Severity: Medium
2 rules found Severity: Medium
Zebra Android 13 must be configured to not allow more than 10 consecutive failed authentication attempts.
2 rules found Severity: Medium
The Tanium Operating System (TanOS) must enforce the limit of three consecutive invalid logon attempts by a user during a 15 minute time period.
2 rules found Severity: Medium
Rancher MCM must use a centralized user management solution to support account management functions. For accounts using password authentication, the container platform must use FIPS-validated SHA-2 or later protocol to protect the integrity of the password authentication process.
1 rule found Severity: High