Forcepoint Network Security Platform 7.3 Installation Guide

Home
Forcepoint Security Engine deployment
Forcepoint Security Engine deployment consists of adding and configuring engine elements in the SMC, and configuring the Security Engine software on the engine.
Configuring Security Engine for the Layer 2 Engine role
Configuring engine elements in the SMC prepares the SMC to manage Security Enginew with the Layer 2 Engine role.

Introduction to the Forcepoint Network Security Platform solution
Before setting up Forcepoint Network Security Platform, it is useful to know what the different components do and what Security Engine roles are available. There are also tasks that you must complete to prepare for installation.
Forcepoint Security Management Center deployment
SMC is the management component of the Security Engine system. SMC must be installed and running before you can deploy the Security Engines.
Forcepoint Security Engine deployment
Forcepoint Security Engine deployment consists of adding and configuring engine elements in the SMC, and configuring the Security Engine software on the engine.
- Configuring Forcepoint Security Engines with Layer 3 Interfaces
  Configuring engine elements in the SMC prepares the SMC to manage Security Engine with Layer 3 Interfaces.
- Configuring Security Engine for the IPS role
  Configuring engine elements in the SMC prepares the SMC to manage Security Engine in the IPS role.
- Configuring Security Engine for the Layer 2 Engine role
  Configuring engine elements in the SMC prepares the SMC to manage Security Enginew with the Layer 2 Engine role.
  - Types of interfaces for Security Engines in the IPS and Layer 2 Engine roles
    Interface definitions are an important part of IPS and Layer 2 Engine elements.
  - Install licenses for Security Engines
    Install the Security Engine licenses that you downloaded while preparing for installation.
  - Defining Layer 2 engines
    Layer 2 Engine elements are a tool for configuring nearly all aspects of your Layer 2 Engines.
  - Bind engine licenses to Layer 2 Engine elements
    After you have configured the Layer 2 Engine elements, you must manually bind Management Server POL-bound licenses to specific Layer 2 Engine elements.
- Configuring Security Engines as Master Engines and Virtual Engines
  Configuring engine elements in the SMC prepares the SMC to manage Master Security Engines and Virtual Security Engines.
- Configuring routing
  After creating the Security Engine elements and defining the interfaces, you can configure the basic routing.
- Initial configuration of Security Engine software
  After configuring the Security Engines in the SMC Client, apply the initial configuration of the Security Engine and contact the Management Server.
- Creating and installing policies
  After successfully applying the initial configuration and establishing contact between the Security Engines and the Management Server, the Security 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 Security Engine, upgrade the SMC and Security Engine regularly.
Appendices

Configuring Security Engine for the Layer 2 Engine role

Configuring engine elements in the SMC prepares the SMC to manage Security Enginew with the Layer 2 Engine role.

Types of interfaces for Security Engines in the IPS and Layer 2 Engine roles
Interface definitions are an important part of IPS and Layer 2 Engine elements.
Install licenses for Security Engines
Install the Security Engine licenses that you downloaded while preparing for installation.
Configuring Layer 2 Engines
Layer 2 Engine elements are a tool for configuring nearly all aspects of your Layer 2 Engines.
Bind engine licenses to Layer 2 Engine elements
After you have configured the Layer 2 Engine elements, you must manually bind Management Server POL-bound licenses to specific Layer 2 Engine elements.

Copyright © 2025 Forcepoint LLC