After Configuring SSL Decryption, Web Browsing Sessions Do Not Match the Configured Policy

After Configuring SSL Decryption, Web Browsing Sessions Do Not Match the Configured Policy

Created On 09/25/18 17:19 PM - Last Modified 02/07/19 23:55 PM



An SSL decryption policy has been put in place but now websites that start as HTTP and switch to HTTPS aren't loading properly anymore.


Security rule originally was set to allow application SSL and web-browsing and service application-default.


Service Application-default forces the App-ID match only on the ports that are defined as default ports under the applications.

The default service for application web-browsing is TCP/80.


However, once SSL Decryption is configured, the firewall can decrypt SSL sessions and identify the underlying application as web-browsing.

This session is still over TCP/443, but the configured security rule (containing application web-browsing, service application-default) does not match due to TCP/443 not being included in the default port range for application web-browsing, which means the session is denied due to implicit deny.

4350    web-browsing   DISCARD FLOW *NS[2514]/L3Trust/6  ([7301]) vsys1                           [443]/L3Untrust  ([443])


There are two ways to resolve this issue:

  1. Either change the current rule to permit service any and allowing web-browsing signature to scan over TCP/443 allowing the session to match the decrypted session.
  2. Clone existing rule, leaving only application web-browsing and allow service service-http and service-https.

Once the above changes are made, the sessions will match desired rule and show up as Active:

4373    web-browsing   ACTIVE  FLOW *NS[2528]/L3Trust/6  ([4471]) vsys1                           [443]/L3Untrust  ([443])

owner: achitwadgi

  • Print
  • Copy Link

Choose Language