V-266095

Discussion

Terminating an idle session within a short time period reduces the window of opportunity for unauthorized personnel to take control of a management session enabled on the console or console port that has been left unattended. In addition, quickly terminating an idle session will also free up resources committed by the managed network element. Terminating network connections associated with communications sessions includes, for example, deallocating associated TCP/IP address/port pairs at the operating system level, or deallocating networking assignments at the application level if multiple application sessions are using a single, operating system-level network connection. This does not mean that the device terminates all sessions or network access; it only ends the inactive session and releases the resources associated with that session. Satisfies: SRG-APP-000190-NDM-000267, SRG-APP-000003-NDM-000202

Check Content

If a documented and validated reason for not implementing the five-minute idle timeout exists, this is not a finding.

From the BIG-IP GUI:
HTTPD/TMSH:
1. System.
2. Preferences.
3. Under Security Settings, verify "Idle Time Before Automatic Logout" is configured for 300 seconds or less.

SSHD:
1. System.
2. Configuration.
3. Device.
4. SSHD.
5. Verify "Idle Time Before Automatic Logout" is configured for 300 seconds or less.

From the BIG-IP Console, issue the following commands:
HTTPD/TMSH:

tmsh list sys httpd auth-pam-idle-timeout
Note: This must return a value of 300 or less.

tmsh list sys httpd auth-pam-dashboard-timeout
Note: This must return a value of "on".

tmsh list sys global-settings console-inactivity-timeout
Note: This must return a value of 300 or less.

tmsh list cli global-settings idle-timeout
Note: This must return a value of 5.

SSHD:
tmsh list sys sshd inactivity-timeout
Note: This must return a value of 300 or less.

If the BIG-IP appliance is not configured to terminate inactive sessions after five minutes of inactivity, this is a finding.