Edit add-on settings for Engines

Engine Editor > Add-Ons

Use this branch to view a summary of the add-on features and the status of each feature.

Activate TLS inspection on Engines

Depending on the elements you select in the engine properties, you can activate client protection alone, server protection alone, or client and server protection together.

CAUTION:

Uploading TLS Credentials or a Client Protection Certificate Authority elements to the engine might enable decryption of TLS traffic that is not excluded from TLS inspection. The following configurations might enable decryption of TLS traffic:

Adding a Network Application that allows or requires the use of TLS to an Access rule
Selecting the Enforced option for Log Application Information in the Access rules
Enabling Deep Inspection in an Access rule if the Service cell contains a Network Application or a Service that does not include a Protocol Agent

For more details about the product and how to configure features, click Help or press F1.

Steps

Select Configuration.
Click Engines.
Right-click an engine element, then select Edit <element type>.
From the navigation pane on the left, select Add-Ons > TLS Inspection.
(For client protection) From the Client Protection Certificate Authority drop-down list, select a Client Protection Certificate Authority element.
- To select an existing element, click Select and select the element.
- To create an element, click New.
(For server protection) Click Add, then select one or more TLS Credentials elements and click Select.
Click Save and Refresh to transfer the configuration changes and upload the certificates.

Engine Editor > Add-Ons > Endpoint Integration

Use this branch to enable endpoint integration on the engine and change the settings for the endpoint client communication.

Option	Definition
When Endpoint Service is Forcepoint Endpoint Context Agent
ECA Listener Certificate	The internal certificate for the Engine that listens for Forcepoint F1E traffic. The certificate is generated automatically when you save the Forcepoint F1E configuration.
Signing CA	The internal CA that signed the certificate.
ECA Configuration	The selected ECA Configuration element. Click Select to select an element.
Source Networks	Add the networks or zones that contain the Forcepoint F1E clients. The Forcepoint F1E clients located in these networks or zones send endpoint information to this Firewall. Click Add to add an element to the table, or Remove to remove the selected element.
Destination Networks	Add the networks or zones where outbound connections are going. The Forcepoint F1E clients send endpoint information only if the destination address is located in these networks or zones. If filtering based on both source address and destination address, both conditions must be met. Click Add to add an element to the table, or Remove to remove the selected element.
Listening Interfaces	The interfaces or zones the Engine uses to listen for Forcepoint F1E traffic. Click Add to add an element to the table, or Remove to remove the selected element.
Listening Port	The port on which the Engine listens for Forcepoint F1E traffic.
Export Configuration for Endpoint Clients	Opens the Export ECA Configuration dialog box, where you can export an XML file that contains the Forcepoint F1E configuration and details of all the Engines that use the same ECA Configuration element. You must first save the Engine configuration.

Engine Editor > Add-Ons > User Authentication

Use this branch to enable user authentication. You can configure authentication using HTTP connections or encrypted HTTPS connections.

Option	Definition
Authentication Time-Out	Defines the length of time after which authentication expires and users must re-authenticate.
Authentication Idle Time-Out	Defines an idle timeout for user authentication. If there have been no new connections within the specified time limit after the closing of a user's previous connection, the user is removed from the list of authenticated users.
HTTP	When selected, allows authentication using plain HTTP connections. Change the Port number if you want to use a different port for the authentication interface. The default port is 80.
HTTPS	When selected, allows authentication using encrypted HTTPS connections. Change the Port number if you want to use a different port for the authentication interface. The default port is 443. This option is required for client certificate authentication.
HTTPS Settings	Opens the Browser-Based User Authentication HTTPS Configuration dialog box.
TLS Profile	The TLS Profile element that defines TLS settings for HTTPS connections for authentication, and the trusted certificate authority for client certificate authentication. Click Select to select an element. This option is required for client certificate authentication.
Use Client Certificates for Authentication	When selected, the Engine allows users to authenticate using X.509 certificates. Client certificate authentication is supported for browser-based user authentication.
Always Use HTTPS	When selected, redirects connections to the HTTPS port and enforces the use of HTTPS if the Engine also listens on other ports.
Listen on Interfaces	Restricts the interfaces that users can authenticate through. All — Users can authenticate through all interfaces. Selected — Users can only authenticate through the selected interfaces.
User Authentication Page	Select the User Authentication Page element that defines the look of the logon, challenge, re-authentication, and status page shown to end users when they authenticate.
Enable Session Handling (Optional)	When selected, enables cookie-based strict session handling. Note: When Enable Session Handling is selected, the Authentication Idle Time-Out option is not available. The Refresh Status Page Every option defines the authentication timeout.
Refresh Status Page Every (Optional)	Defines how often the status page is automatically refreshed. When Enable Session Handling is selected, defines the authentication timeout.

Engine Editor > Add-Ons > User Identification

Use this branch to select a User Identification Service element.

Note: These settings are not supported for Master Engines or Virtual Engines.

Option	Definition
User Identification Service	The Forcepoint User ID Service, McAfee Logon Collector, and Integrated User ID Service provide user, group, and IP address information that can be used in transparent user identification. The Integrated User ID Service is primarily meant for demonstration purposes and proof-of-concept testing of user identification services. Select — Allows you to select an existing Forcepoint User ID Service, McAfee Logon Collector, or Integrated User ID Service element. None — Disables transparent user identification. Note: For Engine version 6.4 or higher, we recommend that you use the Forcepoint User ID Service.
Network Filters section (When a Forcepoint User ID Service element is selected)
IP Ranges (Optional)	To prevent the Engine from receiving too many logon events, specify the IP address ranges of networks from which to receive logon events. Click Add to add an element to the list, or Remove to remove the selected element. We recommend adding the IP address ranges of networks for which the Engine routes traffic. Note: Network filters do not exclude other IP addresses outside of the specified IP address range if a user has at least one logon in the specified IP address range. The Engine might still receive logon events from other IP address ranges.

Option

Definition

User Identification Service

The Forcepoint User ID Service, McAfee Logon Collector, and Integrated User ID Service provide user, group, and IP address information that can be used in transparent user identification.

The Integrated User ID Service is primarily meant for demonstration purposes and proof-of-concept testing of user identification services.

Select — Allows you to select an existing Forcepoint User ID Service, McAfee Logon Collector, or Integrated User ID Service element.
None — Disables transparent user identification.

Note: For Engine version 6.4 or higher, we recommend that you use the Forcepoint User ID Service.

Network Filters section (When a Forcepoint User ID Service element is selected)

IP Ranges

(Optional)

To prevent the Engine from receiving too many logon events, specify the IP address ranges of networks from which to receive logon events.

Click Add to add an element to the list, or Remove to remove the selected element.

We recommend adding the IP address ranges of networks for which the Engine routes traffic.

Note: Network filters do not exclude other IP addresses outside of the specified IP address range if a user has at least one logon in the specified IP address range. The Engine might still receive logon events from other IP address ranges.

Engine Editor > Add-Ons > Anti-Malware

Use this branch to enable and change settings for anti-malware checks on the Engine.

Option	Definition
Enable	Enables anti-malware checks.
Malware Log Level	The log level for anti-malware events. None — Does not create any log entry. Transient — Creates a log entry that is displayed in the Current Events mode in the Logs view, but is not stored. Stored — Creates a log entry that is stored on the Log Server. Essential — Creates a log entry that is shown in the Logs view and saved for further use. Alert — Triggers the alert you select.
Alert	When the Log Level is set to Alert, specifies the Alert that is sent.

Option	Definition
Malware Signature Update Settings section
Update Frequency	Defines how often the Engine checks for updates to the anti-malware database. Never — The Engine does not check for updates. You must update the anti-malware database manually. When Anti-Malware Daemon Starts — Checks when the anti-malware daemon starts. The daemon starts, for example, when the anti-malware feature is enabled or when the Engine restarts. Every Hour — Checks for updates once an hour. Daily — Checks for updates once a day. Set the time of day. Weekly — Checks for updates once a week. Set the day and time of day.

Option

Definition

Malware Signature Update Settings section

Update Frequency

Defines how often the Engine checks for updates to the anti-malware database.

Never — The Engine does not check for updates. You must update the anti-malware database manually.
When Anti-Malware Daemon Starts — Checks when the anti-malware daemon starts. The daemon starts, for example, when the anti-malware feature is enabled or when the Engine restarts.
Every Hour — Checks for updates once an hour.
Daily — Checks for updates once a day. Set the time of day.
Weekly — Checks for updates once a week. Set the day and time of day.

Option	Definition
Malware Signature Mirror Settings section
Mirror(s)	Enter the URL of the anti-malware database mirror that the Engine contacts to update the anti-malware database. Separate multiple addresses with commas.
Use HTTP Proxy (Optional)	Specifies that the Engine uses an HTTP proxy to connect to the anti-malware database mirrors.
Host	The IP address or DNS name of the HTTP proxy.
Port	The listening port of the HTTP proxy.
Username	The user name for authenticating to the HTTP proxy.
Password	The password for authenticating to the HTTP proxy. By default, passwords and keys are not shown in plain text. To show the password or key, deselect the Hide option.

Engine Editor > Add-Ons > Data Protection

Use this branch to enable ICAP for data protection on the Engine.

Option	Definition
Enable ICAP for data protection	When selected, the Engine sends files to the specified ICAP servers for DLP scanning.
ICAP Servers list Click Add to add an element to the list, or Remove to remove the selected element. If you add multiple ICAP servers, traffic is balanced between the ICAP servers.

Option

Definition

Enable ICAP for data protection

When selected, the Engine sends files to the specified ICAP servers for DLP scanning.

ICAP Servers list

Click Add to add an element to the list, or Remove to remove the selected element.

If you add multiple ICAP servers, traffic is balanced between the ICAP servers.

Engine Editor > Add-Ons > Sandbox

Use this branch to select and configure sandbox servers for Engines.

Option	Definition
Sandbox Type	Specifies which type of sandbox the Engine uses for sandbox file reputation scans. None — The Engine does not use a sandbox. Cloud Sandbox - Forcepoint Advanced Malware Detection — The engine uses the cloud sandbox for Forcepoint Advanced Malware Detection. Local Sandbox - Forcepoint Advanced Malware Detection — The engine uses the local sandbox for Forcepoint Advanced Malware Detection. Note: To use the local sandbox for Forcepoint Advanced Malware Detection, you must have a Forcepoint Advanced Malware Detection appliance. Local Sandbox - McAfee Advanced Threat Defense (ATD) — The engine uses McAfee Advanced Threat Defense. Note: McAfee Advanced Threat Defense is no longer supported in Engine version 6.4.0 and higher. We recommend that you use Forcepoint Advanced Malware Detection instead.

Option

Definition

Sandbox Type

Specifies which type of sandbox the Engine uses for sandbox file reputation scans.

None — The Engine does not use a sandbox.
Cloud Sandbox - Forcepoint Advanced Malware Detection — The engine uses the cloud sandbox for Forcepoint Advanced Malware Detection.
Local Sandbox - Forcepoint Advanced Malware Detection — The engine uses the local sandbox for Forcepoint Advanced Malware Detection.
Note: To use the local sandbox for Forcepoint Advanced Malware Detection, you must have a Forcepoint Advanced Malware Detection appliance.
Local Sandbox - McAfee Advanced Threat Defense (ATD) — The engine uses McAfee Advanced Threat Defense.
Note: McAfee Advanced Threat Defense is no longer supported in Engine version 6.4.0 and higher. We recommend that you use Forcepoint Advanced Malware Detection instead.

Option	Definition
When Sandbox Type is Cloud Sandbox - Forcepoint Advanced Malware Detection
License Key (Optional)	The license key for the connection to the sandbox server. If you have not entered a license key in the properties of the Sandbox Service element, you must enter a license key here. If you have entered a license key in the properties of the Sandbox Service element, you can optionally enter a license key here to override the global setting. Note: The license defines the home data center where files are analyzed. Enter the key and license token for the data center that you want to use as the home data center. CAUTION: The license keys and license tokens allow access to confidential analysis reports. Handle the license key and license token securely.
License Token (Optional)	The license token for the connection to the sandbox server. If you have not entered a license token in the properties of the Sandbox Service element, you must enter a license key here. If you have entered a license token in the properties of the Sandbox Service element, you can optionally enter a license token here to override the global setting.
Sandbox Service	Specifies the sandbox service that the firewall contacts to request file reputation scans. Click Select to select an element.
HTTP Proxies (Optional)	When specified, requests are sent through an HTTP proxy instead of the engine accessing the external network directly. Add — Allows you to add an HTTP Proxy to the list. Remove — Removes the selected HTTP Proxy from the list.

Option	Definition
When Sandbox Type is Local Sandbox - Forcepoint Advanced Malware Detection
License Key (Optional)	The license key for the connection to the sandbox server. If you have not entered a license key in the properties of the Sandbox Service element, you must enter a license key here. If you have entered a license key in the properties of the Sandbox Service element, you can optionally enter a license key here to override the global setting.
License Token (Optional)	The license token for the connection to the sandbox server. If you have not entered a license token in the properties of the Sandbox Service element, you must enter a license key here. If you have entered a license token in the properties of the Sandbox Service element, you can optionally enter a license token here to override the global setting.
Sandbox Service	Specifies the sandbox service that the firewall contacts to request file reputation scans. Click Select to select an element.
HTTP Proxies (Optional)	When specified, requests are sent through an HTTP proxy instead of the engine accessing the external network directly. Add — Allows you to add an HTTP Proxy to the list. Remove — Removes the selected HTTP Proxy from the list.

Engine Editor > Add-Ons > File Reputation

Use this branch to enable file reputation services for file filtering.

Option	Definition
File Reputation Service	Select the file reputation service to use. None — Disables file reputation services. Threat Intelligence Exchange (TIE) — This option is included for backward compatibility with legacy software versions. McAfee Threat Intelligence Exchange (TIE) is no longer supported in Engine 6.10 and higher. Global Threat Intelligence (GTI) — Enables the use of McAfee GTI file reputation services for file filtering.

Option

Definition

File Reputation Service

Select the file reputation service to use.

None — Disables file reputation services.
Threat Intelligence Exchange (TIE) — This option is included for backward compatibility with legacy software versions. McAfee Threat Intelligence Exchange (TIE) is no longer supported in Engine 6.10 and higher.
Global Threat Intelligence (GTI) — Enables the use of McAfee GTI file reputation services for file filtering.

Option	Definition
When File Reputation Service is Global Threat Intelligence (GTI)
HTTP Proxies (Optional)	When specified, requests are sent through an HTTP proxy instead of the engine accessing the external network directly. Click Add to add an element to the list, or Remove to remove the selected element. Note: You can only use one HTTP proxy for the connection to the McAfee Global Threat Intelligence file reputation service. If you select more than one HTTP proxy, the additional HTTP proxies are ignored.

Option

Definition

When File Reputation Service is Global Threat Intelligence (GTI)

HTTP Proxies

(Optional)

When specified, requests are sent through an HTTP proxy instead of the engine accessing the external network directly. Click Add to add an element to the list, or Remove to remove the selected element.

Note: You can only use one HTTP proxy for the connection to the McAfee Global Threat Intelligence file reputation service. If you select more than one HTTP proxy, the additional HTTP proxies are ignored.

Engine Editor > Add-Ons > Anti-Spam

The Anti-Spam feature is no longer supported in Engine version 6.2.0 and higher..

Engine Editor > Add-Ons > Sidewinder Proxy

Use this branch to enable and configure Sidewinder Proxies.

Option	Definition
Enable	When selected, enables Sidewinder Proxy.
Sidewinder Logging Profile	The selected Sidewinder Logging Profile element for the engine. Click Select to open the Select Element dialog box, where you can select a Sidewinder Logging Profile.
SSH Proxy	Settings specific to the SSM SSH Proxy.
SSH Known Hosts Lists	The selected SSH Known Hosts List elements for the engine. Click Add to add an element to the list, or Remove to remove the selected element.
Host Keys	The SSH host keys used by the firewall when it acts as the SSH server in a connection that uses the SSM SSH Proxy. Click Add to add a row to the table, or Remove to remove the selected row. To import an existing host key, click Import.
Key Type	Shows the signature algorithm used for the host key.
Key Length	Shows the length of the host key.
SHA256 Fingerprint	Shows the SHA256 fingerprint of the host key.
SSH Proxy Services	The SSH Proxy Service element with which the host key is used. Double-click the field to open the Select Element dialog box, where you can select a Service element.
Comment (Optional)	A comment for your own reference.
Advanced Settings	Opens the Advanced Sidewinder Proxy Settings dialog box.

Engine Editor > Add-Ons > Snort

Use this branch to override settings in the global Snort configuration for specific Engines.

Note: These settings are not supported for Master Engines or Virtual Engines.

Option	Definition
Enable	When selected, enables Snort inspection for the Engine. Note: To apply Snort inspection to traffic, you must also create Access rules to select traffic for Snort inspection.
Snort Configuration (Optional)	The externally created Snort configuration .zip file that contains the Snort configuration files and rules for Snort inspection. Click Browse to select a file. Click None to remove a previously imported file. Click Export to export the Snort configuration file. All Engines for which Snort inspection is enabled use the global Snort configuration by default. If you do not want to override settings in the global Snort configuration, it is not necessary to import a Snort configuration file for an individual Engine. Settings in the Snort configuration .zip file for an individual Engine are combined with the settings in the global Snort configuration .zip file. If any configuration files in a Snort configuration .zip file for an individual Engine have the same files name and paths as configuration files in the global Snort configuration .zip file, the overlapping files in the global Snort configuration .zip file are ignored.

Option

Definition

Enable

When selected, enables Snort inspection for the Engine.

Note: To apply Snort inspection to traffic, you must also create Access rules to select traffic for Snort inspection.

Snort Configuration

(Optional)

The externally created Snort configuration .zip file that contains the Snort configuration files and rules for Snort inspection.

Click Browse to select a file.
Click None to remove a previously imported file.
Click Export to export the Snort configuration file.

All Engines for which Snort inspection is enabled use the global Snort configuration by default. If you do not want to override settings in the global Snort configuration, it is not necessary to import a Snort configuration file for an individual Engine.

Settings in the Snort configuration .zip file for an individual Engine are combined with the settings in the global Snort configuration .zip file. If any configuration files in a Snort configuration .zip file for an individual Engine have the same files name and paths as configuration files in the global Snort configuration .zip file, the overlapping files in the global Snort configuration .zip file are ignored.

Engine Editor > Add-Ons > ThreatSeeker

Use this branch to select HTTP Proxy elements for the connection to the ThreatSeeker Intelligence Cloud.

Option	Definition
Enable	When selected, enables ThreatSeeker URL filtering for the engine.
HTTP Proxies (Optional)	When specified, requests are sent through an HTTP proxy instead of the engine accessing the external network directly. Add — Allows you to add an HTTP Proxy to the list. Remove — Removes the selected HTTP Proxy from the list.

Option

Definition

Enable

When selected, enables ThreatSeeker URL filtering for the engine.

HTTP Proxies

(Optional)

When specified, requests are sent through an HTTP proxy instead of the engine accessing the external network directly.

Add — Allows you to add an HTTP Proxy to the list.

Remove — Removes the selected HTTP Proxy from the list.

Engine Editor > Add-Ons > OPC UA Inspection

Use this branch to change inspection settings for open platform communications unified architecture (OPC UA). For information about OPC UA, see Knowledge Base article 12491.