STIGs Search Compare

STIGhub

A free tool to search and browse the entire DISA STIG library. Saves up to 75% in security compliance research time.

Navigation

Browse STIGs
Search
Compare Versions

Resources

About
Release Notes
VPAT
DISA STIG Library

STIGs updated 6 hours ago

Powered by Pylon

© 2026 Beacon Cloud Solutions, Inc. All rights reserved.

← Back to STIGs

F5 BIG-IP Local Traffic Manager Security Technical Implementation Guide

Version

V2R4

Release Date

Dec 19, 2024

SCAP Benchmark ID

F5_BIG-IP_Local_Traffic_Manager_11-x_STIG

Total Checks

61

Tags

other

CAT I: 7CAT II: 51CAT III: 3

This Security Technical Implementation Guide is published as a tool to improve the security of Department of Defense (DOD) information systems. The requirements are derived from the National Institute of Standards and Technology (NIST) 800-53 and related documents. Comments or proposed revisions to this document should be sent via email to the following address: disa.stig_spt@mail.mil.

Export CKL Export CSV Export JSON Download STIG ZIP

Checks (61)

V-215738MEDIUMThe BIG-IP Core implementation must be configured to enforce approved authorizations for logical access to information and system resources by employing identity-based, role-based, and/or attribute-based security policies.V-215739MEDIUMThe BIG-IP Core implementation must be configured to enforce approved authorizations for controlling the flow of information within the network based on attribute- and content-based inspection of the source, destination, headers, and/or content of the communications traffic.V-215740HIGHThe BIG-IP Core implementation must be configured to restrict or block harmful or suspicious communications traffic by controlling the flow of information between interconnected networks based on attribute- and content-based inspection of the source, destination, headers, and/or content of the communications traffic.V-215741LOWThe BIG-IP Core implementation must be configured to display the Standard Mandatory DoD-approved Notice and Consent Banner before granting access to virtual servers.V-215742LOWThe BIG-IP Core implementation must be configured to retain the Standard Mandatory DoD-approved Notice and Consent Banner on the screen until users accessing virtual servers acknowledge the usage conditions and take explicit actions to log on for further access.V-215743LOWThe BIG-IP Core implementation must be configured to display the Standard Mandatory DoD-approved Notice and Consent Banner before granting access to publicly accessible applications.V-215744HIGHThe BIG-IP Core implementation must be configured to limit the number of concurrent sessions to an organization-defined number for virtual servers.V-215745MEDIUMThe BIG-IP Core implementation must be configured to monitor inbound traffic for remote access policy compliance when accepting connections to virtual servers.V-215746MEDIUMThe BIG-IP Core implementation must be configured to use encryption services that implement NIST SP 800-52 Revision 2 compliant cryptography to protect the confidentiality of connections to virtual servers.V-215747MEDIUMThe BIG-IP Core implementation must be configured to comply with the required TLS settings in NIST SP 800-52 Revision 1 for TLS services to virtual servers.V-215748MEDIUMThe BIG-IP Core implementation must be configured to use NIST SP 800-52 Revision 1 compliant cryptography to protect the integrity of remote access sessions to virtual servers.V-215749MEDIUMThe BIG-IP Core implementation must be configured to protect audit information from unauthorized read access.V-215750MEDIUMThe BIG-IP Core implementation must be configured to protect audit information from unauthorized modification.V-215751MEDIUMThe BIG-IP Core implementation must be configured to protect audit information from unauthorized deletion.V-215752MEDIUMThe BIG-IP Core implementation must be configured to protect audit tools from unauthorized access.V-215753MEDIUMThe BIG-IP Core implementation must be configured to protect audit tools from unauthorized modification.V-215754MEDIUMThe BIG-IP Core implementation must be configured to protect audit tools from unauthorized deletion.V-215755MEDIUMThe BIG-IP Core implementation must be configured so that only functions, ports, protocols, and/or services that are documented for the server/application for which the virtual servers are providing connectivity.V-215756MEDIUMThe BIG-IP Core implementation must be configured to remove or disable any functions, ports, protocols, and/or services that are not documented as required.V-215757MEDIUMThe BIG-IP Core implementation must be configured to prohibit or restrict the use of functions, ports, protocols, and/or services, as defined in the Ports, Protocol, and Service Management (PPSM) Category Assurance List (CAL) and vulnerability assessments.V-215758MEDIUMThe BIG-IP Core implementation must be configured to uniquely identify and authenticate organizational users (or processes acting on behalf of organizational users) when connecting to virtual servers.V-215759MEDIUMThe BIG-IP Core implementation must be configured with a pre-established trust relationship and mechanisms with appropriate authorities (e.g., Active Directory or authentication, authorization, and accounting (AAA) server) that validate user account access authorizations and privileges when providing access control to virtual servers.V-215760MEDIUMThe BIG-IP Core implementation providing user authentication intermediary services must restrict user authentication traffic to specific authentication server(s) when providing access control to virtual servers.V-215761MEDIUMThe BIG-IP Core implementation providing user authentication intermediary services must use multifactor authentication for network access to non-privileged accounts when granting access to virtual servers.V-215762MEDIUMThe BIG-IP Core implementation must be configured to validate certificates used for TLS functions for connections to virtual servers by constructing a certification path (which includes status information) to an accepted trust anchor.V-215763MEDIUMThe BIG-IP Core implementation providing PKI-based, user authentication intermediary services must be configured to map the authenticated identity to the user account for PKI-based authentication to virtual servers.V-215764MEDIUMThe BIG-IP Core implementation must be configured to uniquely identify and authenticate non-organizational users (or processes acting on behalf of non-organizational users) when connecting to virtual servers.V-215765MEDIUMThe BIG-IP Core implementation must terminate all communications sessions at the end of the session or as follows: for in-band management sessions (privileged sessions), the session must be terminated after 10 minutes of inactivity, and for user sessions (nonprivileged sessions), the session must be terminated after 15 minutes of inactivity.V-215766MEDIUMThe BIG-IP Core implementation must be configured to protect the authenticity of communications sessions.V-215772MEDIUMThe BIG-IP Core implementation providing intermediary services for remote access communications traffic must control remote access methods to virtual servers.V-215773MEDIUMTo protect against data mining, the BIG-IP Core implementation must be configured to prevent code injection attacks from being launched against data storage objects, including, at a minimum, databases, database records, queries, and fields when providing content filtering to virtual servers.V-215774MEDIUMTo protect against data mining, the BIG-IP Core implementation providing content filtering must be configured to prevent code injection attacks from being launched against application objects, including, at a minimum, application URLs and application code.V-215775MEDIUMTo protect against data mining, the BIG-IP Core implementation providing content filtering must be configured to prevent SQL injection attacks from being launched against data storage objects, including, at a minimum, databases, database records, and database fields.V-215776MEDIUMTo protect against data mining, the BIG-IP Core implementation providing content filtering must be configured to detect code injection attacks being launched against data storage objects.V-215777MEDIUMTo protect against data mining, the BIG-IP Core implementation providing content filtering must be configured to detect SQL injection attacks being launched against data storage objects, including, at a minimum, databases, database records, and database fields.V-215778MEDIUMThe BIG-IP Core implementation must be configured to detect code injection attacks being launched against application objects, including, at a minimum, application URLs and application code, when providing content filtering to virtual servers.V-215779MEDIUMThe BIG-IP Core implementation must require users to reauthenticate when the user's role, the information authorizations, and/or the maximum session timeout is exceeded for the virtual server(s).V-215780MEDIUMA BIG-IP Core implementation providing user authentication intermediary services must be configured to require multifactor authentication for remote access to non-privileged accounts in such a way that one of the factors is provided by a device separate from the system gaining access.V-215781MEDIUMThe BIG-IP Core implementation providing user authentication intermediary services must be configured to require multifactor authentication for remote access with privileged accounts to virtual servers in such a way that one of the factors is provided by a device separate from the system gaining access.V-215784MEDIUMThe BIG-IP Core implementation must be configured to deny-by-default all PKI-based authentication to virtual servers supporting path discovery and validation if unable to access revocation information via the network.V-215788MEDIUMThe BIG-IP Core implementation must be able to conform to FICAM-issued profiles when providing authentication to virtual servers.V-215789MEDIUMThe F5 BIG-IP appliance providing user authentication intermediary services must only accept end entity certificates issued by DOD PKI or DOD-approved PKI Certification Authorities (CAs) for the establishment of protected sessions.V-215790HIGHThe BIG-IP Core implementation must be configured to protect against known and unknown types of Denial of Service (DoS) attacks by employing rate-based attack prevention behavior analysis when providing content filtering to virtual servers.V-215791HIGHThe BIG-IP Core implementation must be configured to implement load balancing to limit the effects of known and unknown types of Denial of Service (DoS) attacks to virtual servers.V-215792HIGHThe BIG-IP Core implementation must be configured to protect against known types of Denial of Service (DoS) attacks by employing signatures when providing content filtering to virtual servers.V-215793HIGHThe BIG-IP Core implementation must be configured to protect against or limit the effects of known and unknown types of Denial of Service (DoS) attacks by employing pattern recognition pre-processors when providing content filtering to virtual servers.V-215794MEDIUMThe BIG-IP Core implementation must be configured to only allow incoming communications from authorized sources routed to authorized destinations.V-215795MEDIUMThe BIG-IP Core implementation must be configured to handle invalid inputs in a predictable and documented manner that reflects organizational and system objectives.V-215796MEDIUMThe BIG-IP Core implementation must continuously monitor inbound communications traffic crossing internal security boundaries for unusual or unauthorized activities or conditions.V-215797MEDIUMThe BIG-IP Core implementation must be configured to check the validity of all data inputs except those specifically identified by the organization.V-215798MEDIUMThe BIG-IP Core implementation must be configured to implement NIST FIPS-validated cryptography to generate cryptographic hashes when providing encryption traffic to virtual servers.V-215799MEDIUMThe BIG-IP Core implementation must be configured to implement NIST FIPS-validated cryptography for digital signatures when providing encrypted traffic to virtual servers.V-215800MEDIUMThe BIG-IP Core implementation must be configured to use NIST FIPS-validated cryptography to implement encryption services when providing encrypted traffic to virtual servers.V-215801MEDIUMThe BIG-IP Core implementation must be configured to inspect for protocol compliance and protocol anomalies in inbound SMTP and Extended SMTP communications traffic to virtual servers.V-215802MEDIUMThe BIG-IP Core implementation must be configured to inspect for protocol compliance and protocol anomalies in inbound FTP and FTPS communications traffic to virtual servers.V-215803MEDIUMThe BIG-IP Core implementation must be configured to inspect for protocol compliance and protocol anomalies in inbound HTTP and HTTPS traffic to virtual servers.V-230214MEDIUMThe BIG-IP Core implementation must automatically terminate a user session for a user connected to virtual servers when organization-defined conditions or trigger events occur that require a session disconnect.V-230215MEDIUMThe BIG-IP Core must display an explicit logoff message to users indicating the reliable termination of authenticated communications sessions when providing access to virtual servers.V-230216MEDIUMThe BIG-IP Core implementation must be configured to activate a session lock to conceal information previously visible on the display for connections to virtual servers.V-260048MEDIUMThe F5 BIG-IP appliance must configure OCSP to ensure revoked credentials are prohibited from establishing an allowed session.V-270899HIGHThe version of F5 BIG-IP must be a supported version.