STIGhubSTIGhub
STIGsRMF ControlsCompare
STIGhub— A free STIG search and compliance tool·STIGs updated 3 days ago
Powered by Pylon·Privacy·Terms·© 2026 Beacon Cloud Solutions, Inc.
← Back to IBM Aspera Platform 4.2 Security Technical Implementation Guide

V-252565

CAT II (Medium)

IBM Aspera Console must lock accounts after three unsuccessful login attempts within a 15-minute timeframe.

Rule ID

SV-252565r831494_rule

STIG

IBM Aspera Platform 4.2 Security Technical Implementation Guide

Version

V1R3

CCIs

CCI-000044CCI-002236CCI-002238

Discussion

By limiting the number of failed login attempts, the risk of unauthorized system access via user password guessing, otherwise known as brute-forcing, is reduced. Limits are imposed by locking the account.

Check Content

Verify IBM Aspera Console locks accounts after three unsuccessful login attempts within a 15-minute timeframe: 

- Log in to the IBM Aspera Console web page as a user with administrative privilege. 
- Select the "Configuration" tab.
- Select the "Defaults" tab.
- Scroll down to the "Security" section.
- Verify the "Deactivate Users" section is set to "3" or less failed login attempts within "15" minutes or less.

If the "Deactivate Users" section is set to more than "3" failed login attempts, this is a finding.

If the "Deactivate Users" section is set to more than "15" minutes, this is a finding.

Fix Text

Configure IBM Aspera Console to lock accounts after three unsuccessful login attempts within a 15-minute timeframe: 

- Log in to the IBM Aspera Console web page as a user with administrative privilege. 
- Select the "Configuration" tab.
- Select the "Defaults" tab.
- Scroll down to the "Security" section.
- Edit the "Deactivate Users" section failed login attempts option to "3" or less.
- Edit the "Deactivate Users" section attempts within minutes to "15" or less.
- Select "Save" at the bottom of the page.