- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
03-18-2020 01:59 AM
On my PA 9.1.0 firewall, Ive created a custom URL category 'Akamai' with a url list comprising *.deploy.static.akamaitechnologies.com
In my security policy i have a rule allowing any source (trust zone) to reach any destination (untrust zone) via any protocol and any application. The rule specifies 'Akamai' under the Services/URL category. log and allow is set. Any ideas why my rule is not matching? I see likely traffic falling through to a later rule.
03-20-2020 02:59 AM - edited 03-20-2020 03:02 AM
Hi @JimMcGrady ,
If you don't decrypt then the firewall can't see the url ... it will be encrypted.
In that case the firewall will rely on the certificate information or the SNI to identify the category.
URL CATEGORIZATION IN SSL AND POLICY LOOKUP WORK-FLOW
Cheers,
-Kiwi.
03-18-2020 02:10 AM
Hi @JimMcGrady ,
Can you add some more details ?
Is it SSL traffic ? If so are you decrypting it correctly ? How is the traffic identified by the firewall ?
Cheers,
-Kiwi.
03-20-2020 01:45 AM
It is https (ssl) traffic. I am not decrypting. However i would have thought the rule would match on URL rather than on content.
This is the procedure i have followed
https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000ClJKCA0
03-20-2020 02:59 AM - edited 03-20-2020 03:02 AM
Hi @JimMcGrady ,
If you don't decrypt then the firewall can't see the url ... it will be encrypted.
In that case the firewall will rely on the certificate information or the SNI to identify the category.
URL CATEGORIZATION IN SSL AND POLICY LOOKUP WORK-FLOW
Cheers,
-Kiwi.
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!