Hello guys, Recently I had a situation where Cisco Webex traffic was decrypted by policy - let's call them "URL_policy" 'URL_policy" was set to decrypt traffic based on the categorization of URL likes: drugs, extremism, gambling, adult, malware, nudity, etc - nothing business-related for sure. Just after this policy was my "webex_do_not_decrypt" policy, based of destination IP https://help.webex.com/en-us/article/WBX264/How-Do-I-Allow-Webex-Meetings-Traffic-on-My-Network?#id_135011 For an unknown reason, Webex traffic hit the first rule, why? Here you have examples of destination IP which belongs for Cisco Webex services: ( addr.dst in 170.72.131.16 ) 170.72.0.0/16 170.72.0.1 - 170.72.255.254 ( addr.dst in 209.197.208.182 ) and ( addr.dst in 209.197.208.148 ) 209.197.192.0/19 209.197.192.1 - 209.197.223.254 NSLOOKUP shows: Name: m09txmcs182.webex.com Address: 170.72.131.16 while two others don't have DNS records assigned, but belong to Organization: Cisco Webex LLC (WEX) I asked PA TAC and got the explanation that due to technical limitations on PANOS 9.1 there is no way to check why - really??!? I know how to check reputation of URL (https://urlfiltering.paloaltonetworks.com/query/) Help me please to understand why the traffic hit first policy With regards SLawek
... View more