Applications and app types
Gateway allows you to build DNS, Network, and HTTP policies based on applications and app types. This feature gives you more granular control over how web applications are used on your network.
Creating policies with applications and app types
Navigate to the DNS, Network, or HTTP tab, depending on what kind of policy you want to create.
In the Selector drop-down menu, select the Application option.
In the Operator drop-down menu, select in or not in, depending on whether you want to include or exclude applications or app types from your policy.
In the Value drop-down menu, check the applications or app types you would like to control with your policy.
Click Create policy to finalize your changes.
Supported applications and app types
Do Not Inspect applications
Some applications are incompatible with TLS decryption for a variety of reasons, one of which is certificate pinning. This is a process used by applications to verify that the TLS certificate presented from the origin server matches a known, specified list of certificates hardcoded in the application.
This is a countermeasure to man-in-the-middle attacks where an attacker presents a trusted, but false, certificate on behalf of the origin in order to decrypt the traffic. This is exactly what TLS interception in a Secure Web Gateway does, although for the purposes of securing a user’s web traffic.
Gateway automatically groups applications incompatible with TLS decryption into the Do Not Inspect app type. To ensure that traffic gets through to these applications, you can , select Application as a Selector, in as an Operator, and check the Do Not Inspect app type in the Value field. Then, set the HTTP policy Action to Do Not Inspect.
Gateway periodically updates the Do Not Inspect app type to include new applications. By creating this Do Not Inspect HTTP policy and selecting all applications within the Do Not Inspect app type, you will ensure that your Do Not Inspect policy will apply to any new applications added to the app type.