FlexEdge Secure SD-WAN 6.10.100 Online Help

Home
Traffic inspection policies
Policies are key elements that contain rules for allowing or blocking network traffic and inspecting the content of traffic.
Ethernet rules

About this Help
This online help was created for Secure SD-WAN Manager, version 6.10.100.0.
Introduction to the FlexEdge Secure SD-WAN
Before setting up FlexEdge Secure SD-WAN, it is useful to know what the different components do and what engine roles are available.
Deployment
Before you can set up the system and start configuring elements, you must consider how the different Secure SD-WAN Manager components should be positioned and deployed.
Setting up
After deploying the Secure SD-WAN Manager components, you are ready to start using the Management Client and carrying out some of the first configuration tasks.
Monitoring
You can use the Secure SD-WAN Manager to monitor system components and third-party devices. You can also view and filter logs, and create Reports from them.
Controlling Engines
You can command and set options for engines through the Management Client or on the engine command line. You can also stop traffic manually.
Secure SD-WAN Manager configuration
Secure SD-WAN Manager configuration allows you to customize how the Secure SD-WAN Manager components work.
Engine configuration
You can create and modify Firewalls, IPS engines, Layer 2 Firewalls, Master Engines and Virtual Engines. You can configure the Engine properties, activate optional features, and configure advanced Engine settings.
Routing
Use the Management Client to configure static or dynamic routing, and use a Multi-Link configuration to manage and distribute inbound and outbound connections.
Traffic inspection policies
Policies are key elements that contain rules for allowing or blocking network traffic and inspecting the content of traffic.
- Creating and managing policy elements
  Policy elements are containers for the rules that determine how Engines, Master Engines, and Virtual Engines examine traffic. The policy elements for the engines include Template Policies, Policies, and Sub-Policies.
- Ethernet rules
  - Getting started with Ethernet rules
    Ethernet rules are lists of matching criteria and actions that define whether Ethernet protocol traffic is allowed or discarded.
  - Configuration of Ethernet rules
    You can use Ethernet rules in IPS, Layer 2 Firewall, and Layer 2 Interface Policy and Template Policy elements. Sub-Policies cannot contain Ethernet rules.
  - Examples of Ethernet rules
    These examples illustrate some common modifications to the default Ethernet rules and general steps on how each example is configured.
- Access rules
  Access rules are lists of matching criteria and actions that define how the engine treats different types of network traffic. They are your main configuration tool for defining which traffic is stopped and which traffic is allowed.
- NAT rules
- Inspection Policy elements
  Inspection Policy elements define how the engines look for patterns in traffic allowed through the Access rules and what happens when a certain type of pattern is found.
- Snort inspection on Engines
  The Snort open source intrusion prevention system is integrated into FlexEdge Secure SD-WAN. You can import externally created Snort configurations into FlexEdge Secure SD-WAN to use Snort rule sets for inspection.
- Editing policies
  The rules in Firewall, IPS, Layer 2 Firewall, and Layer 2 Interface Policies allow you to control how the engines inspect and filter network traffic, and how NAT (network address translation) is applied on Firewalls, Master Engines, and Virtual Firewalls.
- Defining IP addresses
  When you define IP addresses as elements, you can use the same definitions in multiple configurations for multiple components.
- Working with Service elements
  Service elements match traffic based on protocol or port and set options for advanced inspection of traffic. Service elements are used in Firewall Policies, IPS Policies, Layer 2 Firewall Policies, and Layer 2 Interface Policies.
- Defining Situation elements
  Situation elements contain the context information that defines the pattern that the Engine looks for in the inspected traffic. Situation elements also define the patterns that match events in the traffic.
- Using Network Application elements
  Network Application elements collect combinations of identified characteristics and detected events in traffic to dynamically identify traffic related to the use of a particular network application.
- Defining User Response elements
  With the User Response element, you can send customized replies to users, instead of just closing an HTTP or HTTPS connection.
- Quality of Service
  The Quality of Service (QoS) features allow you to manage bandwidth and prioritize connections on the Engines. QoS features are available on Firewalls, IPS Engines, Layer 2 Firewalls, Master Engines, Virtual Firewalls, Virtual IPS Engines, and Virtual Layer 2 Firewalls.
- File filtering
  Monitoring and restricting what data is sent out is an important part of data loss prevention (DLP). File filtering allows you to restrict the file types that are allowed in and out through the firewall, and to apply malware detection to files.
- Integrating Forcepoint F1E with Engine
  If you have installed Forcepoint F1E clients on the endpoints in your network, you can collect information about endpoint clients, and use the information for access control in the Secure SD-WAN Manager.
- Filtering URLs
  URL filtering allows you to filter URLs based on categories of content or lists of individual URLs.
- Anti-malware scanning
  An anti-malware scanner compares network traffic against an anti-malware database to search for malware. If malware is found, the traffic is stopped or content is stripped out.
- Protocol Agents on Engines
  Protocol elements of the Protocol Agent type are special modules for some protocols and services that require advanced processing. Protocol Agents can enforce policies on the application layer.
- Sidewinder Proxies
  Sidewinder Proxies are software modules that provide network level proxies, protocol validation, and configurable application level protocol filtering and translation on Secure SD-WAN Manager.
- Setting up TLS inspection
  The TLS inspection feature decrypts TLS connections so that they can be inspected for malicious traffic and then re-encrypts the traffic before sending it to its destination.
- Forward traffic to a proxy service for external inspection
  In addition to inspecting traffic on the Engine, you can transparently forward traffic to a proxy service in the cloud or on premises. For example, you can forward all HTTP and HTTPS traffic to the Forcepoint Web Security Cloud service.
- Blacklisting IP addresses
  Blacklisting is a way to temporarily block unwanted network traffic either manually or automatically with blacklist requests from an Engine or Log Server. Firewalls, IPS engines, Layer 2 Firewalls, and Virtual Engines can use a blacklist for blocking traffic.
Users and authentication
User accounts are stored in internal databases or external directory servers. You can use Engine in the Firewall/VPN role or external authentication servers to authenticate users.
Virtual private networks
Engine supports both policy-based and route-based VPN (virtual private network) tunnels between VPN gateways. For full remote access, Engine supports both IPsec and SSL VPN tunnels for VPN clients.
Maintenance and upgrades
Maintenance includes procedures that you do not typically need to do frequently.
Troubleshooting
Troubleshooting helps you resolve common problems in the Engine and Secure SD-WAN Manager.
Appendices

Ethernet rules

Getting started with Ethernet rules
Ethernet rules are lists of matching criteria and actions that define whether Ethernet protocol traffic is allowed or discarded.
Configuration of Ethernet rules
You can use Ethernet rules in IPS, Layer 2 Firewall, and Layer 2 Interface Policy and Template Policy elements. Sub-Policies cannot contain Ethernet rules.
Examples of Ethernet rules
These examples illustrate some common modifications to the default Ethernet rules and general steps on how each example is configured.