NGFW Online Help

Home
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.
Network interface configuration
The network interface configuration for NGFW Engines is stored on the Management Server in the properties of Single Firewall, Firewall Cluster, Single IPS, IPS Cluster, Single Layer 2 Firewall, Layer 2 Firewall Cluster, Master NGFW Engine, and Virtual NGFW Engine elements.
Examples of IPS engine interface configuration
These examples illustrate some common uses for IPS engines and general steps for how each example is configured.

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.
- Creating and modifying engine elements
  Engine elements contain the configuration information that is directly related to the Firewalls, IPS engines, and Layer 2 Firewalls. The configuration information includes interface definitions, cluster mode selection, tester settings, and other engine-specific options.
- Creating and modifying Master NGFW Engine and Virtual NGFW Engine elements
  Virtual NGFW Engines are logically separate engines that run as virtual instances on a physical engine device. A Master NGFW Engine is a physical engine device that provides resources for Virtual NGFW Engines.
- Network interface configuration
  The network interface configuration for NGFW Engines is stored on the Management Server in the properties of Single Firewall, Firewall Cluster, Single IPS, IPS Cluster, Single Layer 2 Firewall, Layer 2 Firewall Cluster, Master NGFW Engine, and Virtual NGFW Engine elements.
  - Network interfaces for engines
    The network interface configuration stored on the Management Server contains most of the settings for network interfaces.
  - Configuring interfaces for Firewalls
    The interface configuration process consists of several general steps.
  - Configuring interfaces for IPS engines
    The interface configuration for Single IPS engines and IPS Clusters consists of several main steps.
  - Configuring interfaces for Layer 2 Firewalls
    The interface configuration for Single Layer 2 Firewalls and Layer 2 Firewall Clusters consists of several main steps.
  - Configuring interfaces for Master NGFW Engines
    Master NGFW Engines can have two types of interfaces: interfaces for the Master NGFW Engine's own traffic, and interfaces that are used by the Virtual NGFW Engines hosted on the Master NGFW Engine.
  - Configuring interfaces for Virtual NGFW Engines
    Physical interfaces in the properties of a Virtual NGFW Engine represent interfaces allocated to the Virtual NGFW Engine in the Master NGFW Engine.
  - Add manual ARP entries to NGFW Engines
    You can add manual ARP entries for IPv4 and neighbor discover entries for IPv6 in the Engine Editor.
  - Examples of Single Firewall interface configuration
    These examples illustrate common configurations for a Single Firewall and general overviews of the steps for how each example is configured.
  - Examples of Firewall Cluster interface configuration
    These examples illustrate the configuration of a Firewall Cluster with general steps for how each example is configured.
  - Examples of IPS engine interface configuration
    These examples illustrate some common uses for IPS engines and general steps for how each example is configured.
    - Example: IPS Capture Interface configuration with SPAN
      An example of using SPAN ports on switches to duplicate packets for inspection.
    - Example: IPS Capture Interface configuration with TAP
      An example of using a network TAP device to forward packets for inspection.
    - Example: IPS Inline Interface configuration
      An example of deploying a Single IPS in the traffic path.
    - Example: IPS Cluster serial inline deployment
      This scenario shows an example of an IPS Cluster in a serial inline deployment.
  - Examples of Layer 2 Firewall interface configuration
    These examples illustrate some common uses for Layer 2 Firewalls and general steps for how each example is configured.
- Connecting engines to the SMC
  To maintain the security of your system, the engines establish an authenticated and encrypted connection with Log Servers and Management Servers.
- Element-based network address translation (NAT)
  Element-based NAT allows you to define NAT addresses in the properties of an element. The NAT definitions define how firewalls translate network IP addresses.
- Configuring the engine tester
  The tester runs various checks on the engines and initiates responses based on the success or failure of these tests.
- Engine permissions
  You can set permissions to control the administration of the engines.
- DNS Relay
  DNS relay allows the firewall to provide DNS services for clients in internal networks.
- Setting up SNMP for NGFW Engines
  SNMP is a standard protocol that different equipment can use to send network management-related information to each other. You can configure NGFW Engines to send SNMP traps to external equipment.
- Alias element translations for engines
  Alias elements can be used to represent other network elements in configurations. The value an Alias takes in a configuration can be different on each engine where the Alias is used.
- Add-on features for engines
  There are several engine element add-on features that you can use on Firewalls, IPS engines, Layer 2 Firewalls, Virtual Firewalls, Virtual IPS engines, and Virtual Layer 2 Firewalls.
- Advanced engine settings
  Advanced settings cover various system parameters related to different features.
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).
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

Examples of IPS engine interface configuration

These examples illustrate some common uses for IPS engines and general steps for how each example is configured.

Example: IPS Capture Interface configuration with SPAN
An example of using SPAN ports on switches to duplicate packets for inspection.
Example: IPS Capture Interface configuration with TAP
An example of using a network TAP device to forward packets for inspection.
Example: IPS Inline Interface configuration
An example of deploying a Single IPS in the traffic path.
Example: IPS Cluster serial inline deployment
This scenario shows an example of an IPS Cluster in a serial inline deployment.

Copyright © 2018 Forcepoint LLC