Spark 1900 URL & APP filtering issue

[AmitS]

Hi Team,

We have a 1900 spark appliance in Cluster version R81.10.10.

Requirement is to have APP & URL Blocking based on the predefined categories (e.g Shopping, FTP, Social, Media etc) with out HTTPS inspection as customer cannot install the certificates on endpoint and/or mobile devices.

We have tested to use HTTPS categorization but its not working as expected, few sites are getting blocked and some are working, hence not achieving the desired solution.

but when HTTPS inspection is configured all is working properly, the categories which are blocked in rule are not working which is desired.

Is there any other way to achieve this???

[G_W_Albrecht]

I would first install the current version R81.10.15 Build 996003913 and after testing, open SR# with CP TAC to get this resolved.

[PhoneBoy]

Do you have an explicit rule blocking QUIC in your rulebase?
QUIC traffic will not be categorized by HTTPS Categorization.
By blocking QUIC, the client web browsers should fall back to HTTP/1.1, for which traffic can be categorized correctly.

[G_W_Albrecht]

Yes, QUIC - but recently with 1600, blocking QUIC on GW did not help, so customer had to disable it for browsers using GPO.

[AmitS]

Yes, we have explicit rule to block QUIC. Still categorisation is not working.

Any alternate solution?

[PhoneBoy]

HTTPS Categorization uses one two things to categorize websites for HTTP/HTTPS connections (QUIC connections aren't supported for HTTPS Categorization):

• The DN of the site certificate (which is always unencrypted, but may not reflect the actual site being accessed)
• The unencrypted SNI of the HTTPS connection. If the SNI is encrypted, there is no way to see the SNI short of full HTTPS Inspection, thus not possible to categorize the connection.

Specific examples of websites that should be being blocked but aren't might be helpful.

[AmitS]

Categories example such as gambling, Shopping, Media, Youtube.

Amazon.in

flipkart.com

888.com

velonyx.live

and many more

[PhoneBoy]

To see if the problem is Encrypted SNI, you will have to take a packet capture when the client initiates a connection to this site.
If it's Encrypted SNI, the only solution to that is HTTPS Inspection.
If the SNI is not encrypted and it's not working, then I suggest a TAC case.

[AmitS]

Hi Team,

Customer is having other Firewall as well such as Palo alto & sonicwall & same thing is working there without SSL/HTTPS inspections..

So here in Checkpoint its not working without Https inspections...