A Firewall is a network security device that monitors incoming and outgoing network traffic and decides whether to allow or block specific traffic based on a defined set of security rules. SASE Orchestrator supports configuration of stateless and stateful Firewalls for Profiles and Edges.

For more information on Firewall, see Firewall Overview.

Configure Profile Firewall

To configure Profile Firewall:
  1. In the SD-WAN service of the Enterprise portal, go to Configure > Profiles. The Profiles page displays the existing Profiles.
  2. To configure a Profile Firewall, click the link to the Profile and click the Firewall tab. Alternatively, you can click the View link in the Firewall column of the Profile.
  3. The Firewall page appears.
  4. From the Firewall tab, you can configure the following Edge Security and Firewall capabilities:
    Field Description
    Edge Access Allows you to configure a Profile for Edge access. You must make sure to select the appropriate option for Support access, Console access, USB port access, SNMP access, and Local Web UI access under Firewall settings to make the Edge more secure. This will prevent any malicious user from accessing the Edge. By default, Support access, Console access, SNMP access, and Local Web UI access are deactivated for security reasons. For more information, see Configure Edge Access.
    Firewall Status Allows you to turn ON or OFF the Firewall rules, configure Firewall settings, and in-bound ACLs for all Edges associated with the Profile.
    Note: By default, this feature is activated. You can deactivate the Firewall function for Profiles by turning the Firewall Status to OFF.
    Attention: At the Edge level, once you override the inherited Firewall Status settings, the Edge will stop inheriting any further Firewall Status setting changes from the associated Profile even when the setting is changed at the associated Profile level or when assigned to a different Profile. However, if the Firewall Status setting is turned off in the Profile, this setting will be inherited by the Edge, and it will be deactivated even if the Firewall Status is enabled on the Edge.
    Enhanced Security Allows you to turn ON or OFF the following security services for all Edges associated with the Profile:
    • Intrusion Detection/Prevention
    • URL Filtering
    • Malicious IP Filtering

    By default, the Enhanced Security functionality is not activated. If you activate this feature, ensure to activate at least one of the supported security services.

    Note: Enhanced Security services are not supported for routed LAN interfaces with dynamic addressing (DHCP Client, DHCPv6 Client, DHCPv6 PD, and SLAAC).

    For more information, see Configure Enhanced Security Services.
    Hosted Firewall Logging Allows you to turn ON or OFF the Firewall Logging feature at the Enterprise Edge level to send Firewall logs to the Orchestrator.
    Note: Starting with the 5.4.0 release, for Hosted Orchestrators, the Enable Firewall Logging to Orchestrator capability is activated by default for new and existing Enterprises. At the Edge level, customers must activate Hosted Firewall Logging to send Firewall logs from the Edge to Orchestrator.

    You can view the Edge Firewall logs in Orchestrator from the Monitor > Firewall Logs page. For more information, see Monitor Firewall Logs.
    Syslog Forwarding By default, the Syslog Forwarding feature is deactivated for an Enterprise. To collect SASE Orchestrator bound events and Firewall logs originating from Enterprise SD-WAN Edge to one or more centralized remote Syslog collectors (Servers), an Enterprise user must activate this feature at the Edge/Profile level. To configure Syslog collector details per segment in the SASE Orchestrator, see Configure Syslog Settings for Profiles.
    Note: You can view both IPv4 and IPv6 Firewall logging details in a IPv4-based Syslog Server.
    Firewall Rules The existing pre-defined Firewall rules are displayed. You can click + NEW RULE to create a new Firewall rule. For more information, see Configure Firewall Rule.

    To delete an existing Firewall rule, select the rule and click DELETE.

    To duplicate a Firewall rule, select the rule and click CLONE.

    To view all comments added while creating or updating a rule, select the rule and click COMMENT HISTORY.

    Click Search for Rule if you want to search for a specific rule. You can search the rule by Rule name, IP address, Port/Port range, and Address group and Service group names.
    Stateful Firewall By default, the Stateful Firewall feature is deactivated for an Enterprise. SASE Orchestrator allows you to set session timeout for established and non-established TCP flows, UDP flows, and other flows at the Profile level. Optionally, you can also override the Stateful firewall settings at the Edge level. For more information, see Configure Stateful Firewall Settings.
    Network & Flood Protection To secure all connection attempts in an Enterprise network, VMware SASE Orchestrator allows you to configure Network and Flood Protection settings at the Profile and Edge levels, to protect against the various types of attacks. For more information, see Configure Network & Flood Protection Settings.

Configure Edge Access

To configure Edge access for Profiles, perform the following steps:
  1. In the SD-WAN service of the Enterprise portal, go to Configure > Profiles > Firewall.
  2. Under Edge Security, click the Edge Access expand icon.
  3. You can configure one or more of the following Edge Access options, and click Save Changes:
    Field Description
    Log Edge Access When activated, all access to the Edge is logged, including successful and failed attempts.
    Support Access

    Select Allow the following IPs if you want to explicitly specify the IP addresses from where you can SSH into this Edge. You can enter both IPv4 and IPv6 addresses separated by comma (,).

    By default, Deny All is selected.
    Console Access Select Allow to activate Edge access through Physical Console (Serial Port or Video Graphics Array (VGA) Port). By default, Deny is selected and Console login is deactivated after Edge activation.
    Note: Whenever the console access setting is changed from Allow to Deny or vice-versa, the Edge must be rebooted manually.
    Enforce Power-on Self Test When activated, a failed Power-on Self Test will deactivate the Edge. You can recover the Edge by running factory reset and then reactivate the Edge.
    USB Port Access

    Select Allow to activate and select Deny to deactivate the USB port access on Edges.

    This option is available only for Edge models 510 and 6x0.

    Note: Whenever the USB port access setting is changed from Allow to Deny or vice-versa, you must reboot the Edge manually if you have access to the Edge and if the Edge is in a remote site, restart the Edge using SASE Orchestrator. For instructions, refer to Remote Actions.
    SNMP Access Allows Edge access from routed interfaces/WAN through SNMP. Select one of the following options:
    • Deny All - By default, SNMP access is deactivated for all devices connected to an Edge.
    • Allow All LAN - Allows SNMP access for all devices connected to the Edge through a LAN network.
    • Allow the following IPs - Allows you to explicitly specify the IP addresses from where you can access the Edge through SNMP. Separate each IPv4 or IPv6 address with a comma (,).
    Local Web UI Access Allows Edge access from routed interfaces/WAN through a Local Web UI. Select one of the following options:
    • Deny All - By default, Local Web UI access is deactivated for all devices connected to an Edge.
    • Allow All LAN - Allows Local Web UI access for all devices connected to the Edge through a LAN network.
    • Allow the following IPs - Allows you to explicitly specify the IP addresses from where you can access the Edge through Local Web UI. Separate each IPv4 or IPv6 address with a comma (,).
    Local Web UI Port Number Enter the port number of the local Web UI from where you can access the Edge. The default value is 80.
If you want to override the Edge access settings for a specific Edge, use the Enable Edge Override option available on the Edge Firewall page.

Configure Stateful Firewall Settings

To configure Stateful Firewall Settings for Profiles, perform the following steps:
  1. In the SD-WAN service of the Enterprise portal, go to Configure > Profiles > Firewall.
  2. Under Configure Firewall, turn on the Stateful Firewall toggle button and then click the expand icon. By default, the timeout sessions are applied for IPv4 addresses.
  3. You can configure the following Stateful Firewall settings, and click Save Changes:
    Field Description
    Established TCP Flow Timeout (seconds) Sets the inactivity timeout period (in seconds) for established TCP flows, after which they are no longer valid. The allowable value ranges from 60 seconds to 15999999 seconds. The default value is 7440 seconds.
    Non Established TCP Flow Timeout (seconds) Sets the inactivity timeout period (in seconds) for non-established TCP flows, after which they are no longer valid. The allowable value ranges from 60 seconds to 604800 seconds. The default value is 240 seconds.
    UDP Flow Timeout (seconds) Sets the inactivity timeout period (in seconds) for UDP flows, after which they are no longer valid. The allowable value ranges from 60 seconds to 15999999 seconds. The default value is 300 seconds.
    Other Flow Timeout (seconds) Sets the inactivity timeout period (in seconds) for other flows such as ICMP, after which they are no longer valid. The allowable value ranges from 60 seconds to 15999999 seconds. The default value is 60 seconds.
    Note:

    The configured timeout values apply only when the memory usage is below the soft limit. Soft limit corresponds to anything below 60 percent of the concurrent flows supported by the platform in terms of memory usage.

Configure Network & Flood Protection Settings

VMware SD-WAN provides detection and protection against the following types of attacks to combat exploits at all stages of their execution:
  • Denial-of-Service (DoS) attack
  • TCP-based attacks - Invalid TCP Flags, TCP Land, and TCP SYN Fragment
  • ICMP-based attacks - ICMP Ping of Death and ICMP Fragment
  • IP-based attacks - IP Unknown Protocol, IP Options, IPv6 Unknown Protocol, and IPv6 Extension Header.
Attack Type Description
Denial-of-Service (DoS) attack

A denial-of-service (DoS) attack is a type of network security attack that overwhelms the targeted device with a tremendous amount of bogus traffic so that the target becomes so preoccupied with processing the bogus traffic that legitimate traffic cannot be processed. The target can be a firewall, the network resources to which the firewall controls access, or a specific hardware platform or operating system of an individual host. The DoS attack attempts to exhaust the target device's resources, making the target device unavailable to legitimate users.

There are two general methods of DoS attacks: flooding services or crashing services. Flood attacks occur when the system receives too much traffic for the server to buffer, causing them to slow down and eventually stop. Other DoS attacks simply exploit vulnerabilities that cause the target system or service to crash. In these attacks, input is sent that takes advantage of bugs in the target that subsequently crash or severely destabilize the system.
Invalid TCP Flags
Invalid TCP flags attack occurs when a TCP packet has a bad or invalid flag combination. A vulnerable target device will crash due to invalid TCP flag combinations and therefore it is recommended to filter them out. Invalid TCP flags guards against:
  • A packet that has no flags set in its TCP header such as SYN, FIN, ACK, and so on.
  • TCP header that has SYN and FIN flags combined, which are mutually exclusive in reality
TCP Land

A Land attack is a Layer 4 DoS attack in which a TCP SYN packet is created such that the source IP address and port are set to be the same as the destination IP address and port, which in turn is set to point to an open port on a target device. A vulnerable target device would receive such a message and reply to the destination address effectively sending the packet for reprocessing in an infinite loop. Thus, the device CPU is consumed indefinitely causing the vulnerable target device to crash or freeze.

TCP SYN Fragment

The Internet Protocol (IP) encapsulates a Transmission Control Protocol (TCP) SYN segment in the IP packet to initiate a TCP connection and invoke a SYN/ACK segment in response. Because the IP packet is small, there is no legitimate reason for it to be fragmented. A fragmented SYN packet is anomalous and as such suspect. In a TCP SYN fragment attack, a target server or host is flooded with TCP SYN packet fragments. The host catches the fragments and waits for the remaining packets to arrive so it can reassemble them. By flooding a server or host with connections that cannot be completed, the host's memory buffer overflows, and therefore no further legitimate connections are possible, causing damage to the target host's operating system.
ICMP Ping of Death

An Internet Control Message Protocol (ICMP) Ping of Death attack involves the attacker sending multiple malformed or malicious pings to a target device. While ping packets are small and used for checking the reachability of network hosts, they could be crafted larger than the maximum size of 65535 bytes by attackers.

When a maliciously large packet is transmitted from the malicious host, the packet gets fragmented in transit and when the target device attempts to reassemble the IP fragments into the complete packet, the total exceeds the maximum size limit. This could overflow memory buffers initially allocated for the packet, causing a system crash, or freeze, or reboot, as they cannot manage such huge packets.
ICMP Fragment

An ICMP Fragmentation attack is a common DoS attack that involves the flooding of fraudulent ICMP fragments that cannot be defragmented on the target server. As defragmentation can only take place when all fragments are received, temporary storage of such fake fragments takes up memory and may exhaust the available memory resources of the vulnerable target server, resulting in server unavailability.
IP Unknown Protocol

IP Unknown Protocols refers to any protocol not listed in IANA: https://www.iana.org/assignments/protocol-numbers/protocol-numbers.xhtml.

Enabling IP Unknown Protocol protection blocks IP packets with the protocol field containing a protocol ID number of 143 or greater, as it could lead to a crash if not managed properly on the end device. A cautious stance would be to block such IP packets from entering the protected network.
IP Options

Attackers sometimes configure IP option fields within an IP packet incorrectly, producing either incomplete or malformed fields. Attackers use these malformed packets to compromise vulnerable hosts on the network. Exploitation of the vulnerability may potentially allow for arbitrary code execution. The vulnerability may be exploited after processing a packet containing a specific crafted IP option in the packet's IP header. Enabling IP Insecure Options protection blocks transit IP packets with incorrectly formatted IP option fields in the IP packet header.
IPv6 Unknown Protocol

Enabling IPv6 Unknown Protocol protection blocks IPv6 packets with the protocol field containing a protocol ID number of 143 or greater, as it could lead to a crash if not managed properly on the end device. A cautious stance would be to block such IPv6 packets from entering the protected network.
IPv6 Extension Header An IPv6 Extension Header attack is a DoS attack that occurs due to mishandling of extension headers in an IPv6 packet. The mishandling of IPv6 extension headers creates new attack vectors that could lead to DoS, and which can be exploited for different purposes, such as creating covert channels and routing header 0 attacks. Enabling this option would drop an IPv6 packet with any extension header except fragmentation headers.
To configure Network and Flood Protection Settings for Profiles, perform the following steps:
  1. In the SD-WAN service of the Enterprise portal, go to Configure > Profiles > Firewall.
  2. Under Configure Firewall, ensure to turn on the Stateful Firewall feature.
  3. Click the Network & Flood Protection expand icon.
  4. You can configure the following Network and Flood Protection settings, and click Save Changes:
    Note: By default, the network and flood protection settings are applied for IPv4 addresses.
    Field Description
    New Connection Threshold (connections per second) The maximum number of new connections that is allowed from a single source IP per second. The allowable value ranges from 10 percent to 100 percent. The default value is 25 percent.
    Denylist Select the checkbox to block a source IP address, which is violating the new connection threshold by sending flood traffic either due to misconfiguration of the network or malicious user attacks.
    Note: The New Connection Threshold (connections per second) settings will not work unless Denylist is selected.
    Detect Duration (seconds) Before blocking a Source IP address, it is the grace time duration for which the violating source IP is allowed to send traffic flows.

    If a host sends flood traffic of new connection requests (port scan, TCP SYN flood, and so on) exceeding the maximum allowed connection per second (CPS) for this duration, it will be considered as eligible for denylisting instead of immediately denylisting it as soon as it exceeds the CPS per source once. For example, consider that the maximum allowed CPS is 10 with detect duration of 10 seconds, if the host floods new connection requests greater than 100 requests for 10 seconds, then the host will be denylisted.

    The allowable value ranges from 10 seconds to 100 seconds. The default value is 10 seconds.
    Denylist Duration (seconds) The time duration for which the violated source IP is blocked from sending any packets. The allowable value ranges from 10 seconds to 86400 seconds. The default value is 10 seconds.
    TCP Half-Open Threshold Per Destination The maximum number of half-open TCP connections that is allowed per destination. The allowable value ranges from 1 percent to 100 percent.
    TCP Based Attacks Supports protection from the following TCP-based attacks by enabling the respective checkboxes:
    • Invalid TCP Flags
    • TCP Land
    • TCP SYN Fragment
    ICMP Based Attacks Supports protection from the following ICMP-based attacks by enabling the respective checkboxes:
    • ICMP Ping of Death
    • ICMP Fragment
    IP Based Attacks Supports protection from the following IP-based attacks by enabling the respective checkboxes:
    • IP Unknown Protocol
    • IP Options
    • IPv6 Unknown Protocol
    • IPv6 Extension Header