For descriptions of all log fields, see Knowledge Base article 38581.
This online help was created for Forcepoint Network Security Platform, version 7.3.0.
Before setting up Forcepoint Network Security Platform, 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 SMC 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 SMC Client or on the engine command line. You can also stop traffic manually.
SMC Manager configuration allows you to customize how the SMC components work.
You can create and modify Engines, IPS engines, Layer 2 Engines, Master Engines and Virtual Security Engines. You can configure the Security Engine properties, activate optional features, and configure advanced Security Engine settings.
Use the SMC 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 Network Security Platform in the Engine/VPN role or external authentication servers to authenticate users.
Forcepoint Network Security Platform supports both policy-based and Route-based Tunnels between VPN gateways. For full remote access, Forcepoint Network Security Platform supports both IPsec and SSL VPN tunnels for VPN clients.
Maintenance includes procedures that you do not typically need to do frequently.
Troubleshooting helps you resolve common problems in the Forcepoint Network Security Platform and SMC.
There are command line tools for the SMC and the Security Engines.
There are default ports used in connections between SMC components and default ports that SMC components use with external components.
Expressions are elements that allow you to create simple definitions for representing complex sets of IP addresses by using logical operands.
Predefined Aliases are used in the default policies. Some of them might be useful when you create your own rules.
There are parameters you can define for Situation Contexts.
The SMC has its own regular expression syntax. Regular expressions are used in Situations for matching network traffic. Situations are used in the Inspection rules on Security Engines.
There are SMC-specific LDAP classes and attributes that you add to the schema of external LDAP servers.
For a list of available shortcut keys in the SMC Client, see Knowledge Base article 38538.
The multicasting reference describes the general principles of multicasting and how it can be used with CVIs (cluster virtual IP addresses) in Engine Clusters.