The following example configurations outline common VPN use cases.
This guide provides the information you need to work with your Forcepoint product.
The SMC as a Service provides centralized access for configuring, managing, logging, and monitoring NGFWs that secure network connectivity and control business operations.
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.
VPNs allow creating secure, private connections through networks that are not otherwise secure.
You can follow these examples when you set up your own VPNs and add other features after the basic scenario is configured and working.
This scenario shows an example of how to create a policy-based VPN between two or more Engines managed through the same SMCaaS Application.
This scenario walks you through creating a site-to-site VPN between one Engine and one external VPN gateway that is not managed through the same SMCaaS Application.
This configuration scenario walks you through creating a mobile VPN between an Engine and more than one Forcepoint VPN Client.
In a VPN hub configuration, a gateway is configured to forward VPN traffic between different VPN tunnels.
The Site element defines the internal IP addresses that can send or receive traffic through the VPN.
Site elements allow you to adjust how the Site is used in each VPN.
If the default VPN Profile elements do not meet your needs, create a custom VPN Profile element.
A digital certificate is a proof of identity. SMCaaS supports using certificates for authenticating gateways and the Forcepoint VPN Client.
You can reconfigure and tune existing VPNs.