Details

Anytime an authentication method is exposed so as to allow for the login to an application, there is a risk that attempts will be made to obtain unauthorized access.

By limiting the number of failed login attempts that occur within a particular time period, the risk of unauthorized system access via user password guessing, otherwise known as brute-forcing, is reduced. Limits are imposed by locking the account once the number of failed attempts has been exceeded.

Solution

1. Access AC
2. From ‘Domain Structure’, select ‘Security Realms’
3. Select realm to configure (default is ‘myrealm’)
4. Select ‘Configuration’ tab -> ‘User Lockout’ tab
5. Utilize ‘Change Center’ to create a new change session
6. Set the following values in the fields as shown:
‘Lockout Threshold’ = 3
‘Lockout Duration’ = 15
‘Lockout Reset Duration’ = 15
7. Click ‘Save’, and from ‘Change Center’ click ‘Activate Changes’ to enable configuration changes

Supportive Information

The following resource is also helpful.

• https://dl.dod.cyber.mil/wp-content/uploads/stigs/zip/U_Oracle_WebLogic_Server_12c_V2R1_STIG.zip

This security hardening control applies to the following category of controls within NIST 800-53: Access Control.This control applies to the following type of system Windows.

References

• 800-53|AC-7a.
• CAT|II
• CCI|CCI-000044
• Rule-ID|SV-235936r628586_rule
• STIG-ID|WBLC-01-000032
• STIG-Legacy|SV-70475
• STIG-Legacy|V-56221
• Vuln-ID|V-235936

Source

• Tenable.com/audits