Next Generation Firewall 7.0 Installation Guide

Home
Forcepoint NGFW deployment
Forcepoint NGFW deployment consists of adding and configuring engine elements in the SMC, and configuring the Forcepoint NGFW software on the engine.
Configuring Forcepoint NGFW for the Firewall/VPN role
Configuring engine elements in the SMC prepares the SMC to manage NGFW Engines in the Firewall/VPN role.
Configuring Firewall Clusters
After you have the SMC installed and running, you can configure the Firewall Cluster elements.
Add layer 3 interfaces to Firewall Clusters
Layer 3 interfaces are used in system communications and in traffic inspection on Firewall Clusters.

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. There are also tasks that you must complete to prepare for installation.
Security Management Center deployment
SMC is the management component of the Forcepoint NGFW system. SMC must be installed and running before you can deploy the Forcepoint NGFW engines.
Forcepoint NGFW deployment
Forcepoint NGFW deployment consists of adding and configuring engine elements in the SMC, and configuring the Forcepoint NGFW software on the engine.
- Configuring Forcepoint NGFW for the Firewall/VPN role
  Configuring engine elements in the SMC prepares the SMC to manage NGFW Engines in the Firewall/VPN role.
  - Types of interfaces for NGFW Engines in the Firewall/VPN role
    You can configure several types of interfaces for NGFW Engines in the Firewall/VPN role.
  - Interface numbering
    The interfaces have their own numbering in the SMC called the interface ID. The interface IDs are mapped to the corresponding network interfaces on the NGFW Engine when you configure the Forcepoint NGFW software.
  - Install licenses for NGFW engines
    Install the NGFW Engine licenses that you downloaded while preparing for installation.
  - Configuring single firewalls
    After you have the SMC installed and running, you can configure the Single Firewall elements.
  - Configuring Firewall Clusters
    After you have the SMC installed and running, you can configure the Firewall Cluster elements.
    - Considerations for Firewall Clusters
      There are several operating modes for the physical interfaces of a Firewall Cluster. Packet dispatch mode is recommended for new installations.
    - Create a Firewall Cluster element
      To introduce a new Firewall Cluster to the SMC, you must define a Firewall Cluster element that stores the configuration information related to the Firewalls.
    - Add a node to a Firewall Cluster
      The Firewall Cluster element has two nodes when the element is created.
    - Add layer 3 interfaces to Firewall Clusters
      Layer 3 interfaces are used in system communications and in traffic inspection on Firewall Clusters.
      - Add a physical interface
        To route traffic through the Firewall Cluster, you must define at least two layer 3 physical interfaces.
      - Add VLAN Interfaces to Firewall Clusters
        VLANs divide a single physical network link into several virtual links.
    - Add IP addresses for Firewall Cluster interfaces
      To route traffic through the firewall, each Firewall Cluster interface must have at least two IP addresses.
    - Add layer 2 interfaces to Firewall Clusters
      Layer 2 interfaces are used in traffic inspection on Firewall Clusters.
    - Set global interface options for a cluster
      Select which IP addresses are used for particular roles in system communications.
    - Add manual ARP entries for Firewall Clusters
      ARP entries are normally managed automatically based on the Firewall’s routing configuration. However, you can also add manual ARP entries for the nodes.
    - Bind engine licenses to correct elements
      After you have configured the Firewall Cluster elements, you must manually bind Management Server POL-bound licenses to specific nodes in Firewall Cluster elements.
- Configuring Forcepoint NGFW for the IPS role
  Configuring engine elements in the SMC prepares the SMC to manage Forcepoint NGFW in the IPS role.
- Configuring Forcepoint NGFW for the Layer 2 Firewall role
  Configuring engine elements in the SMC prepares the SMC to manage NGFW Engines in the Layer 2 Firewall role.
- Configuring NGFW Engines as Master NGFW Engines and Virtual NGFW Engines
  Configuring engine elements in the SMC prepares the SMC to manage Master NGFW Engines and Virtual NGFW Engines.
- Configuring routing
  After creating the NGFW Engine elements and defining the interfaces, you can configure the basic routing.
- Initial configuration of Forcepoint NGFW software
  After configuring the NGFW Engines in the Management Client, apply the initial configuration of the NGFW Engine and contact the Management Server.
- Creating and installing policies
  After successfully applying the initial configuration and establishing contact between the NGFW Engines and the Management Server, the NGFW Engine is in the initial configuration state. Now you can create and install policies for access control or inspecting traffic.
Maintenance
To maximize the benefit of Forcepoint NGFW, upgrade the SMC and Forcepoint NGFW regularly.
Appendices

Add layer 3 interfaces to Firewall Clusters

Layer 3 interfaces are used in system communications and in traffic inspection on Firewall Clusters.

Add layer 3 physical interfaces to Firewall Clusters
To route traffic through the Firewall Cluster, you must define at least two layer 3 physical interfaces.
Add VLAN interfaces to layer 3 interfaces of Firewall Clusters
VLANs divide a single physical network link into several virtual links.

© 2023 Forcepoint
Published 25 August 2023