Secure SD-WAN 7.1 Online Help

Home
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.
Managing VPN certificates
A digital certificate is a proof of identity. Secure SD-WAN in the Engine/VPN role supports using certificates for authenticating gateways and the Forcepoint VPN Client.
Replacing expired VPN certificates
For security reasons, VPN certificates have an expiration date, after which the certificates must be replaced with new ones.
Renew an externally signed certificate for a VPN Gateway element

Latest online help
Link to the latest FlexEdge Secure SD-WAN online documentation.
About this Help
This online help was created for Forcepoint FlexEdge Secure SD-WAN, version 7.1.0.
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.
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.
- VPNs in Secure SD-WAN
  A VPN extends a secured private network over public networks by encrypting connections so that they can be transported over insecure links without compromising confidential data.
- Configuring VPNs
  VPNs allow creating secure, private connections through networks that are not otherwise secure.
- Example VPN configurations
  The following example configurations outline common VPN use cases.
- Managing VPN certificates
  A digital certificate is a proof of identity. Secure SD-WAN in the Engine/VPN role supports using certificates for authenticating gateways and the Forcepoint VPN Client.
  - VPN certificates and how they work
    Certificates can be used for authenticating VPN gateways and the Forcepoint VPN Client.
  - Define additional VPN certificate authorities
    If you want to use certificates that are signed by an external CA, define an additional VPN CA.
  - Create an internal ECDSA certificate authority for VPN gateways
    The Elliptic Curve Digital Signature Algorithm (ECDSA) is a digital signature algorithm that uses elliptic curve cryptography. If you want to use the ECDSA signature algorithm for signing VPN certificates, create an Internal ECDSA CA for Gateways.
  - Select the default internal certificate authority
    If you have both an Internal RSA CA for Gateways and an Internal ECDSA CA for Gateways, only one certificate authority can be selected as the default certificate authority.
  - Create a VPN certificate or certificate request for a VPN Gateway element
    You can create a certificate request and sign it either using an Internal CA for Gateways or an external certificate authority (CA).
  - Import an externally signed VPN gateway certificate
    You can import a certificate signed by an external certificate issuer for a VPN Gateway element when the certificate request has been created in the SMC.
  - Sign external VPN certificate requests with an internal certificate authority
    You can use an internal certificate authority to sign VPN certificate requests for VPN clients and internal VPN gateways.
  - Select which internal certificate authority signs each certificate
    When there is more than one valid CA, you can select which CA signs each certificate.
  - Replacing expired VPN certificates
    For security reasons, VPN certificates have an expiration date, after which the certificates must be replaced with new ones.
    - Renew an externally signed certificate for a VPN Gateway element
    - Renew an internally signed certificate for an external component
    - Renew an internally signed certificate for a VPN Gateway element
      New certificates signed by the new default certificate authority are automatically created for VPN Gateway elements. You must manually create and renew any certificates that are not signed by the default certificate authority.
    - Renew an external certificate authority used in VPN configurations
  - Export signed VPN gateway certificates or VPN certificate authority certificates
    You can export signed gateway certificates, the certificates of the Internal RSA CA for Gateways, and the certificates of the Internal ECDSA CA for Gateways.
  - Check when VPN gateway certificates expire
    Certificates expire according to the information written in the certificate when it was generated
  - Check when VPN certificate authorities expire
    The Internal RSA CA for Gateways and the Internal ECDSA CA for Gateways are valid for 10 years.
- Reconfiguring existing VPNs
  You can reconfigure and tune existing VPNs.
- VPN client settings
  Forcepoint VPN Client does not have controls for many settings that are needed for establishing a SD-WAN. These settings are defined in the SMC. Forcepoint VPN Client downloads the settings from the gateways it connects to. VPN clients are only supported in policy-based VPNs.
- Configuring the SSL VPN Portal
  The SSL VPN Portal uses secure sockets layer (SSL) encryption to allow authenticated users to establish secure connections to internal HTTP and HTTPS services through a standard web browser or through a client application that allows direct network access.
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

Renew an externally signed certificate for a VPN Gateway element

Steps

Create a certificate request.
Sign the certificate with the external CA.
Import the signed certificate.

Copyright © 2024 Forcepoint LLC