A virtual forwarding server is listening for traffic with a destination of any on all VLANs-f5-all

A virtual forwarding server is listening for traffic with a destination of any on all VLANs-f5-all

Vendor: f5

OS: all

Description:
Using a virtual forwarding server in a large network in combination with All VLANs would short circuit networks behind the load balancer and this is not ideal in terms of security. indeni will alert if this configuration is used.

Remediation Steps:
Verify that the configuration is intentional. If not, create forwarding servers for each VLAN listening on the egress VLAN, and one forwarding server listening on all VLANs except the egress VLANs. This way you allow traffic to pass through the load balancer without short circuiting the VLANs behind it.\n\nNote: A change window is highly recommended as there may be impact to the environment. More information about virtual forwarding servers can be found here: https://support.f5.com/csp/article/K7595\n\nThis alert was added per the request of <a target="_blank" href=“https://se.linkedin.com/in/patrik-jonsson-6527932”>Patrik Jonsson.

How does this work?
This alert uses the iControl REST interface to extract any virtual forwarding servers listening to all destinations and on all VLANs.

Why is this important?
It is generally not recommended to have a virtual server listening on all VLANs with a destination of any. This can short circuit any VLANs behind the load balancer and is not ideal in terms of security.

Without Indeni how would you find this?
Login to the device’s web interface and click on “Local Traffic” and then “Virtual servers”. For each of the Virtual Servers, verify if it is listening to any destination and on all VLANs.

f5-rest-mgmt-tm-ltm-virtual

name: f5-rest-mgmt-tm-ltm-virtual
description: Determine use of automap, and if any wildcard forwarding servers listening
    on all VLANs exists.
type: monitoring
monitoring_interval: 60 minute
requires:
    vendor: f5
    product: load-balancer
    rest-api: 'true'
comments:
    f5-automap-used:
        why: |
            Using automap is a great way to troubleshoot assymetric routing, but is considered not ideal in a busy live environment because of a risk of port exhaustion. In case of high amount of traffic it is better to create a "SNAT Pool" with multiple IP addresses on the member networks.
        how: |
            This alert uses the iControl REST interface to extract the use of automap on virtual servers.
        can-with-snmp: true
        can-with-syslog: false
    f5-wildcard-forwarding-servers:
        why: |
            It is generally not recommended to have a virtual server listening on all VLANs with a destination of any. This can short circuit any VLANs behind the load balancer and is not ideal in terms of security.
        how: |
            This alert uses the iControl REST interface to extract any virtual forwarding servers listening to all destinations and on all VLANs.
        can-with-snmp: true
        can-with-syslog: false
steps:
-   run:
        type: HTTP
        command: /mgmt/tm/ltm/virtual?$select=fullPath,sourceAddressTranslation,ipForward,destination,source,vlans
    parse:
        type: JSON
        file: rest-mgmt-tm-ltm-virtual.parser.1.json.yaml

f5_wildcard_forwarding_servers_used

Failed to fetch the data: https://bitbucket.org/indeni/indeni-knowledge/src/master/rules/templatebased/f5/f5_wildcard_forwarding_servers_used.scala