Content migration in progress, completing by midnight IST on 17 November 2026.
Home
Traffic inspection policies
Policies are key elements that contain rules for allowing or blocking network traffic
and inspecting the content of traffic.
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 Engine Policies, IPS Policies,
Layer 2 Engine Policies, and Layer 2 Interface Policies.
About this Help
This online help was created for Forcepoint FlexEdge Secure SD-WAN , version 7.1.x .
Introduction to the Forcepoint FlexEdge Secure SD-WAN solution
Before setting up Forcepoint 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 SMC components should be positioned and deployed.
Setting up
After deploying the SMC components, you are ready to start using the Management Client and carrying out
some of the first configuration tasks.
Monitoring
You can use the SMC to monitor system components and third-party devices. You can also view and filter
logs, and create Reports from them.
Controlling Secure SD-WAN 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.
SMC configuration
SD-WAN Manager configuration allows you to customize how the SMC components work.
Secure SD-WAN Engine configuration
You can create and modify Engines, IPS engines, Layer 2 Engines, Master Engines and
Virtual Secure SD-WAN Engines. You can configure the Secure SD-WAN Engine properties, activate optional features, and
configure advanced Secure SD-WAN 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 Secure SD-WAN Engines, Master Engines, and Virtual Engines examine traffic. The policy
elements for the engines include Template Policies, Policies, and Sub-Policies.
Ethernet rules
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 Secure SD-WAN Engines
The Snort open source intrusion prevention system is integrated into Forcepoint Secure SD-WAN . You can import externally created Snort configurations into Forcepoint Secure SD-WAN to use Snort rule sets for inspection.
Editing policies
The rules in Engine, IPS, Layer 2 Engine, 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 Engines, Master Secure SD-WAN Engines, and Virtual Engines.
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 Engine Policies, IPS Policies,
Layer 2 Engine Policies, and Layer 2 Interface Policies.
Getting started with Service elements
Service elements specify a network protocol, as well as source or destination ports
for TCP and UDP traffic.
Creating Service elements
There are predefined Service elements that correspond to reserved and commonly used
protocols and ports. You might also need to add your own custom Service elements for
any non-standard ports in use or if you want to define options for advanced traffic
handling (Protocol Agents).
Protocol elements and how they work
Protocol Elements identify traffic as being of a certain network protocol.
Defining Protocol parameters
Many Protocols provide options for you to set in the Service that uses them.
Defining Situation elements
Situation elements contain the context information that defines the pattern that the
Secure SD-WAN 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 Secure SD-WAN Engines. QoS features are available on Engines, IPS Secure SD-WAN Engines, Layer 2 Engines, Master Engines, Virtual Engines, Virtual IPS Secure SD-WAN Engines, and Virtual Layer 2 Engines.
Anti-malware scanning
An anti-malware scanner compares network traffic against an anti-malware database
to search for viruses and other malware. If malware is found, the traffic is stopped
or content is stripped out.
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 engine, and to apply malware detection to files.
Integrating Forcepoint One Endpoint with Secure SD-WAN
If you have installed Forcepoint One Endpoint clients on the endpoints in your network, you can collect information about endpoint
clients, and use the information for access control in the SMC .
Filtering URLs
URL filtering allows you to filter URLs based on categories of content or lists of
individual URLs.
Protocol Agents on Secure SD-WAN 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 Forcepoint FlexEdge Secure SD-WAN .
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.
Setting up QUIC inspection
QUIC is a secure general-purpose transport protocol. QUIC combines encryption and
transport layer data stream processing into one protocol, thereby, reduces latency
and improves security.
Forward traffic to a proxy service for external inspection
In addition to inspecting traffic on the Secure SD-WAN 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.
Block listing IP addresses
Block listing is a way to temporarily block unwanted network traffic either manually
or automatically with block list requests from an Secure SD-WAN Engine or Log Server. Engines, IPS engines, Layer 2 Engines, and Virtual Engines
can use a block list for blocking traffic.
Users and authentication
User accounts are stored in internal databases or external directory servers. You
can use Secure SD-WAN in the Engine/VPN role or external authentication servers to authenticate users.
Virtual private networks
Secure SD-WAN supports both policy-based and route-based VPN tunnels between VPN gateways. For
full remote access, Secure SD-WAN 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 Secure SD-WAN and SMC .
Appendices
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
Engine Policies, IPS Policies, Layer 2 Engine Policies, and Layer 2 Interface Policies.
Getting started with Service elements
Service elements specify a network protocol, as well as source or destination ports for TCP and UDP traffic.
Creating Service elements
There are predefined Service elements that correspond to reserved and commonly used protocols and ports. You might also need to add your own custom Service elements for any non-standard ports in use or if you want to define options for advanced traffic handling (Protocol Agents).
Protocol elements and how they work
Protocol Elements identify traffic as being of a certain network protocol.
Defining Protocol parameters
Many Protocols provide options for you to set in the Service that uses them.