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.
You can set permissions to control the administration of the engines.
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.
Before you can set up the system and start configuring elements, you must consider how the different SMC components should be positioned and deployed.
After deploying the SMC components, you are ready to start using the Management Client and carrying out some of the first configuration tasks.
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.
You can command and set options for engines through the Management Client or on the engine command line. You can also stop traffic manually.
Security Management Center (SMC) configuration allows you to customize how the SMC components work.
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.
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.
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.
To maintain the security of your system, the engines establish an authenticated and encrypted connection with Log Servers and Management Servers.
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.
The tester runs various checks on the engines and initiates responses based on the success or failure of these tests.
You can define the permissions that enable or restrict administrators to edit and view an engine's properties.
Define the administrator permissions that permit users to access and view engine options.
Assign Policy or Template Policy permissions for engines.
DNS relay allows the firewall to provide DNS services for clients in internal networks.
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 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.
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 settings cover various system parameters related to different features.
Use the Management Client to configure static or dynamic routing, and use a Multi-Link configuration to manage and distribute inbound and outbound connections.
Policies are key elements that contain rules for allowing or blocking network traffic and inspecting the content of traffic.
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.
Forcepoint NGFW supports both policy-based and route-based VPNs (virtual private networks).
Maintenance includes procedures that you do not typically need to do frequently.
Troubleshooting helps you resolve common problems in the Forcepoint NGFW and SMC.