In non decrypted tls 1.3 traffic, how is the firewall in 10.0 seeing the URL that a user requests and how is it enforcing that category? I've read that tls1.3 encrypts the SNI field, which from my understanding, is the primary way the palo firewalls read and implement URL categories on non-decrypted traffic.
If we don't decrypt on certain traffic (ex. financial), and that traffic is tls1.3, how is the firewall seeing a destination, other than an IP address, and how is it trying to utilize what it sees to a URL category?
I've read below, but still a bit foggy on this, as would this break URL categories period for non-decrypted traffic?
TLSv1.3 supports encrypting the SNI field, but there's additional work that needs to be done to do so and a lot of sites aren't doing so at this time. For sites that choose to encrypt the SNI field, I imagine that the traffic is simply decrypted until the firewall can see what the site actually is and then it stops for the remainder of the established session. I could be wrong on that, but that's about as far as you could handle that situation as far as TLSv1.3 with encrypted SNI is concerned. I might have to lab this up this weekend to see exactly how that functions.
Thank you for the reply! Always good to hear from you.
I'm wondering about the effectiveness of URL categories that are not decrypted on the firewall in a TLS1.3 world. Do they become worthless?
Found the below link, but it still doesn't give a lot of info on the tls1.3 encrypted SNI.
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!