NGFW Online Help

Home
Virtual private networks
Forcepoint NGFW supports both policy-based and route-based VPNs (virtual private networks).
Managing VPN certificates
A digital certificate is a proof of identity. Forcepoint NGFW in the Firewall/VPN role supports using certificates for authenticating gateways and the Stonesoft VPN Client.

About this Help
Introduction to the Forcepoint Next Generation Firewall solution
Before setting up Forcepoint Next Generation Firewall (Forcepoint NGFW), 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 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
Security Management Center (SMC) configuration allows you to customize how the SMC components work.
Engine element configuration
You can create and modify Firewalls, IPS engines, Layer 2 Firewalls, Master NGFW Engines and Virtual NGFW 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.
Users and authentication
User accounts are stored in internal databases or external directory servers. You can use Forcepoint NGFW in the Firewall/VPN role or external authentication servers to authenticate users.
Virtual private networks
Forcepoint NGFW supports both policy-based and route-based VPNs (virtual private networks).
- Getting started with VPNs
  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.
- Basic policy-based VPN configurations
  The following configurations outline specific examples for common policy-based VPN configuration scenarios.
- Managing VPN certificates
  A digital certificate is a proof of identity. Forcepoint NGFW in the Firewall/VPN role supports using certificates for authenticating gateways and the Stonesoft VPN Client.
  - VPN certificates and how they work
    Certificates can be used for authenticating VPN gateways and the Stonesoft VPN Client.
  - Define additional VPN certificate authorities
    You can define several certificate authorities.
  - Create an internal ECDSA certificate authority for VPN gateways
    You can create one 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).
  - 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.
  - Replace expired VPN certificates
    For security reasons, VPN certificates have an expiration date, after which the certificates must be replaced with new ones.
  - 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.
  - 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.
  - 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
  Stonesoft VPN Client does not have controls for many settings that are needed for establishing a VPN. These settings are defined in the SMC. Stonesoft VPN Client downloads the settings from the gateways it connects to. VPN clients are only supported in policy-based VPNs.
Maintenance and upgrades
Maintenance includes procedures that you do not typically need to do frequently.
Troubleshooting
Troubleshooting helps you resolve common problems in the Forcepoint NGFW and SMC.
Appendices

Managing VPN certificates

A digital certificate is a proof of identity. Forcepoint NGFW in the Firewall/VPN role supports using certificates for authenticating gateways and the Stonesoft VPN Client.

VPN certificates and how they work
Certificates can be used for authenticating VPN gateways and the Stonesoft VPN Client.
Define additional VPN certificate authorities
You can define several certificate authorities.
Create an internal ECDSA certificate authority for VPN gateways
You can create one 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).
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.
Replace expired VPN certificates
For security reasons, VPN certificates have an expiration date, after which the certificates must be replaced with new ones.
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.
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.
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.

Copyright © 2018 Forcepoint LLC