Create private application policy rules
Create private application policy rules to define the remote access requirements for your applications, as well as the threat inspection settings you will apply to remote application traffic.
Private application policy rules identify and authenticate the users that are permitted to access your private applications, define traffic decryption settings, and filter incoming traffic based on its source IP address. When private application traffic is decrypted, threat inspection can be used to identify potential threat signatures in private application traffic.
Private applications policies consist of two stages: application rules and threat inspection.
Private application policy rules
- Which private applications can be accessed remotely.
- Which users and groups are permitted to access your applications.
- Whether SAML-based authentication is required for accessing your applications.
- The source IP addresses or geographic IP address ranges that are permitted to access your applications.
For each rule you must configure an Action: the action determines whether the rule will allow and bypass threat inspection, allow and continue inspection, or block access for the configured users and sources. Enable TLS inspection in order to perform threat inspection for HTTPS traffic.
TLS inspection
The TLS inspection setting applies traffic decryption in order to inspect the traffic for threat signatures. In order to perform TLS decryption, you must install the Forcepoint root certificate on end user machines.
Threat inspection for private application traffic
The threat inspection stage for private applications policy applies deep packet inspection to identify potentially malicious private access traffic. If required, you can adjust the default settings for each threat category. The default threat inspection settings are recommended by Forcepoint, and provide a high level of security.