There are command line tools for the SMC and the Security Engines.
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.
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 consists of adding and configuring engine elements in the SMC, and configuring the Security Engine software on the engine.
To maximize the benefit of Security Engine, upgrade the SMC and Security Engine regularly.
There are default ports used in connections between SMC components and default ports that SMC components use with external components.
SMC commands include commands for the Management Server, Log Server, and Web Access Server.
There are commands that can be run on the command line on Engine, Layer 2 Engine, IPS engines, or Master Engines.
You can test and monitor the Server Pool Monitoring Agents on the command line.
You can install the SMC Appliance software as a virtual machine on virtualization platforms such as VMware ESX.
You can install the Security Engine software as a virtual machine on virtualization platforms such as VMware ESX or KVM.
You can install the Security Engine software on third-party hardware that meets the hardware requirements.
When you install the SMC, you can use certificates issued by an external CA for internal TLS communication between system components.
This example gives you a better understanding of how Security Engines with Layer 3 Interfaces fits into a network.
To give you a better understanding of how Security Engine in the IPS role fits into a network, this example outlines a network with IPS engines.
For planning the configuration of network interfaces for the engine nodes, use the worksheet.