NGFW 6.7 Online Help

Home
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.
Managing certificates for system communications
Certificates are proof of identity that SMC components and NGFW Engines use to authenticate themselves in communications.

About this Help
This online Help was created for Forcepoint Next Generation Firewall (Forcepoint NGFW), version 6.7.0.
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.
- Using the Management Client
  The Management Client provides the user interface for setting up, managing, and monitoring all features in the SMC.
- Network address translation (NAT) and how it works
  Network address translation (NAT) means changing the IP address or port information in packets. Most often, NAT is used to allow internal hosts to communicate via networks where their actual address is not routable and to conceal the internal network structure from outsiders.
- Configuring system communications
  System communications involve traffic between SMC components, traffic between SMC components and external components that are a part of the system configuration, and external access into the system.
- Managing certificates for system communications
  Certificates are proof of identity that SMC components and NGFW Engines use to authenticate themselves in communications.
  - How certificates work
    SMC servers and NGFW Engines use certificates to identify each other in system communications, and to secure communications to external components.
  - Types of internal certificate authorities
    The SMC can have either an internal Elliptic Curve Digital Signature Algorithm (ECDSA) certificate authority or an internal RSA certificate authority.
  - Using certificates to secure communications to external components
    You can use certificates to secure communications from the SMC servers or NGFW Engines to external components.
  - Creating certificates
    You can generate certificates in the SMC, then sign the certificate request with tools in the SMC or with an external certificate authority.
  - Configure settings for certificate validation
    Certificate validation settings allow you to define the settings that the NGFW Engine uses when it connects to a Certificate Revocation List (CRL) or Online Certificate Status Protocol (OCSP) server.
  - Renewing certificates
    You must renew certificates and certificate authorities when they expire.
- Managing elements
  Certain tasks are common to most elements. Some of these tasks are not mandatory for defining an element, but are still helpful as you get your SMC up and running.
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 NGFW 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.
NGFW Engine configuration
You can create and modify Firewalls, IPS engines, Layer 2 Firewalls, Master NGFW Engines and Virtual NGFW Engines. You can configure the NGFW Engine properties, activate optional features, and configure advanced NGFW 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 VPN (virtual private network) tunnels between VPN gateways. For full remote access, Forcepoint NGFW 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 Forcepoint NGFW and SMC.
Appendices

Managing certificates for system communications

Certificates are proof of identity that SMC components and NGFW Engines use to authenticate themselves in communications.

How certificates work
SMC servers and NGFW Engines use certificates to identify each other in system communications, and to secure communications to external components.
Types of internal certificate authorities
The SMC can have either an internal Elliptic Curve Digital Signature Algorithm (ECDSA) certificate authority or an internal RSA certificate authority.
Using certificates to secure communications to external components
You can use certificates to secure communications from the SMC servers or NGFW Engines to external components.
Creating certificates
You can generate certificates in the SMC, then sign the certificate request with tools in the SMC or with an external certificate authority.
Configure settings for certificate validation
Certificate validation settings allow you to define the settings that the NGFW Engine uses when it connects to a Certificate Revocation List (CRL) or Online Certificate Status Protocol (OCSP) server.
Renewing certificates
You must renew certificates and certificate authorities when they expire.

© 2021 Forcepoint
Published 4 March 2021