Skip to content

F5 BIG-IP TMOS Firewall Security Technical Implementation Guide

Rules, Groups, and Values defined within the XCCDF Benchmark

  • SRG-NET-000364-FW-000032

    Group
  • The F5 BIG-IP appliance must generate traffic log entries containing information to establish the details of the event, including success or failure of the application of the firewall rule.

    Without establishing what type of event occurred, it would be difficult to establish, correlate, and investigate the events leading up to an outage or attack. Audit event content that may be neces...
    Rule Medium Severity
  • The F5 BIG-IP appliance must be configured to restrict itself from accepting outbound packets that contain an illegitimate address in the source address field via an egress filter or by enabling Unicast Reverse Path Forwarding (uRPF).

    A compromised host in an enclave can be used by a malicious platform to launch cyber attacks on third parties. This is a common practice in "botnets", which are a collection of compromised computer...
    Rule Medium Severity
  • The F5 BIG-IP appliance must employ filters that prevent or limit the effects of all types of commonly known denial-of-service (DoS) attacks, including flooding, packet sweeps, and unauthorized port scanning.

    Not configuring a key boundary security protection device such as the firewall against commonly known attacks is an immediate threat to the protected enclave because they are easily implemented by ...
    Rule High Severity
  • The F5 BIG-IP appliance must be configured to filter inbound traffic on all external interfaces.

    Unrestricted traffic to the trusted networks may contain malicious traffic that poses a threat to an enclave or to other connected networks. Additionally, unrestricted traffic may transit a network...
    Rule Medium Severity
  • The F5 BIG-IP appliance must be configured to filter outbound traffic on all internal interfaces.

    If outbound communications traffic is not filtered, hostile activity intended to harm other networks or packets from networks destined to unauthorized networks may not be detected and prevented. A...
    Rule Medium Severity
  • The BIG-IP appliance perimeter firewall must be configured to filter traffic destined to the enclave in accordance with the specific traffic that is approved and registered in the Ports, Protocols, and Services Management (PPSM) Category Assurance List (CAL) and vulnerability assessments.

    The enclave's internal network contains the servers where mission-critical data and applications reside. Malicious traffic can enter from an external boundary or originate from a compromised host i...
    Rule Medium Severity
  • SRG-NET-000061-FW-000001

    Group
  • The F5 BIG-IP appliance that filters traffic from the VPN access points must be configured with organization-defined filtering rules that apply to the monitoring of remote access traffic.

    Remote access devices (such as those providing remote access to network devices and information systems) that lack automated capabilities increase risk and make remote user access management diffic...
    Rule Medium Severity
  • SRG-NET-000019-FW-000003

    Group
  • The F5 BIG-IP appliance must be configured to use filters that use packet headers and packet attributes, including source and destination IP addresses and ports, to prevent the flow of unauthorized or suspicious traffic between interconnected networks with different security policies, including perimeter firewalls and server VLANs.

    Blocking or restricting detected harmful or suspicious communications between interconnected networks enforces approved authorizations for controlling the flow of traffic. The firewall that filter...
    Rule High Severity
  • F5BI-FW-300005

    Group
  • SRG-NET-000089-FW-000019

    Group
  • In the event that communication with the central audit server is lost, the F5 BIG-IP appliance must continue to queue traffic log records locally.

    It is critical that when the network element is at risk of failing to process traffic logs as required, it takes action to mitigate the failure. Audit processing failures include software/hardware ...
    Rule Low Severity
  • SRG-NET-000098-FW-000021

    Group
  • The F5 BIG-IP appliance must be configured to use TCP when sending log records to the central audit server.

    If the default UDP protocol is used for communication between the hosts and devices to the central log server, then log records that do not reach the log server are not detected as a data loss. The...
    Rule Medium Severity
  • SRG-NET-000364-FW-000042

    Group
  • SRG-NET-000362-FW-000028

    Group
  • SRG-NET-000202-FW-000039

    Group
  • The F5 BIG-IP appliance must deny network communications traffic by default and allow network communications traffic by exception (i.e., deny all, permit by exception).

    To prevent malicious or accidental leakage of traffic, organizations must implement a deny-by-default security posture at the network perimeter. Such rulesets prevent many malicious exploits or acc...
    Rule High Severity
  • SRG-NET-000392-FW-000042

    Group
  • The F5 BIG-IP appliance must generate an alert that can be forwarded to, at a minimum, the information system security officer (ISSO) and information system security manager (ISSM) when denial-of-service (DoS) incidents are detected.

    Without an alert, security personnel may be unaware of major detection incidents that require immediate action, and this delay may result in the loss or compromise of information. The firewall gen...
    Rule Low Severity
  • SRG-NET-000364-FW-000040

    Group
  • The F5 BIG-IP appliance must be configured to inspect all inbound and outbound traffic at the application layer.

    Application inspection enables the firewall to control traffic based on different parameters that exist within the packets such as enforcing application-specific message and field length. Inspectio...
    Rule Medium Severity
  • SRG-NET-000364-FW-000031

    Group
  • SRG-NET-000364-FW-000035

    Group
  • The F5 BIG-IP appliance must be configured to block all outbound management traffic.

    The management network must still have its own subnet to enforce control and access boundaries provided by Layer 3 network nodes such as routers and firewalls. Management traffic between the manage...
    Rule Medium Severity
  • SRG-NET-000205-FW-000040

    Group

The content of the drawer really is up to you. It could have form fields, definition lists, text lists, labels, charts, progress bars, etc. Spacing recommendation is 24px margins. You can put tabs in here, and can also make the drawer scrollable.

Capacity
Modules