STIGQter STIGQter: STIG Summary: F5 BIG-IP Local Traffic Manager 11.x Security Technical Implementation Guide Version: 2 Release: 1 Benchmark Date: 23 Oct 2020:

The BIG-IP Core implementation must be configured to initiate a session lock after a 15-minute period of inactivity when users are connected to virtual servers.

DISA Rule

SV-230213r561158_rule

Vulnerability Number

V-230213

Group Title

SRG-NET-000514-ALG-000514

Rule Version

F5BI-LT-000141

Severity

CAT II

CCI(s)

Weight

10

Fix Recommendation

If user access control intermediary services are provided, configure the BIG-IP Core to initiate a session lock after a 15-minute period of inactivity.

Check Contents

If the BIG-IP Core does not provide user access control intermediary services virtual servers, this is not applicable.

When user access control intermediary services are provided, verify the BIG-IP Core initiates a session lock after a 15-minute period of inactivity.

Select a profile for user sessions.

Verify "Keep Alive Interval" under "Settings" section is set to "Specify" 900.

Verify the BIG-IP LTM is configured to use the Protocol Profile.

Navigate to the BIG-IP System manager >> Local Traffic >> Virtual Servers >> Virtual Servers List tab.

Select appropriate virtual server.

Verify "Protocol Profile (Client)" is set to a profile that limits session timeout.

If the BIG-IP Core does not initiate a session lock after a 15-minute period of inactivity, this is a finding.

Vulnerability Number

V-230213

Documentable

False

Rule Version

F5BI-LT-000141

Severity Override Guidance

If the BIG-IP Core does not provide user access control intermediary services virtual servers, this is not applicable.

When user access control intermediary services are provided, verify the BIG-IP Core initiates a session lock after a 15-minute period of inactivity.

Select a profile for user sessions.

Verify "Keep Alive Interval" under "Settings" section is set to "Specify" 900.

Verify the BIG-IP LTM is configured to use the Protocol Profile.

Navigate to the BIG-IP System manager >> Local Traffic >> Virtual Servers >> Virtual Servers List tab.

Select appropriate virtual server.

Verify "Protocol Profile (Client)" is set to a profile that limits session timeout.

If the BIG-IP Core does not initiate a session lock after a 15-minute period of inactivity, this is a finding.

Check Content Reference

M

Target Key

4019

Comments