- Products
- Learn
- Local User Groups
- Partners
- More
Check Point Jump-Start Online Training
Now Available on CheckMates for Beginners!
Why do Hackers Love IoT Devices so Much?
Join our TechTalk on Aug 17, at 5PM CET | 11AM EST
Welcome to Maestro Masters!
Talk to Masters, Engage with Masters, Be a Maestro Master!
ZTNA Buyer’s Guide
Zero Trust essentials for your most valuable assets
The SMB Cyber Master
Boost your knowledge on Quantum Spark SMB gateways!
As YOU DESERVE THE BEST SECURITY
Upgrade to our latest GA Jumbo
CheckFlix!
All Videos In One Space
A customer wanted to allow his clients access to all sites needed by whitelisting (R77.30). He uses URLF / APCL blade, but no https inspection, so all he can do is let the blade categorize https sites. But he does not want to Allow any URLF Categories!
Using Custom Categories for overriding URLF category to create exception does not work, because Custom Categories only can be used in URLF / APCL rulebase and is not available for "Overriding URLF category" that only shows the pre-defined categories. Otherwise, it would be possible to first create a new category and then overide the URLF categorization with this category for the sites to be whitelisted. Then he could allow the sites by allowing the new category (=RFE).
So he had to follow this procedure for site exceptions suggested by CP:
1. Create one custom application with all the URLs that you need allow or different custom applications for each needed URL
2. Add the created application to "allow" rule on top of rule base
3. Add "DNS protocol" and "SSL protocol" services to the same rule (we have to allow them in case a custom application is used).
4. Install policy.
This solution will work even if HTTPS inspection is disabled.
Guenther,
Can you expand on the "3 different custom applications for each URL"?
Thank you,
Vladimir
why not using a regex for those site and assign to a custom categorie and put the categorie in an allow rule at the top? probably I am missing something
Hi,
call it a typo 😉 Here, customer has two URLs that could have been whitelisted by IP address and one that had to use DNS resolving (collaboration site). That gave three...
regex is good if you are 😉 I have seen strange side effects with regex created by people without very much experience and in analysis learned that pattern matching is not really that easy. So this seems much more appropriate as the customer can add more URLs if needed without risk of bad regex .
Hello Günther,
I am searching for a solution of allowing specific youtube videos but blocking youtube and found this post.
Can you please explain in more details step 3 - "Add "DNS protocol" and "SSL protocol" apps to the same rule"?
My current situation: Mgmt & gateway in R80.20, I have a rule with:
- source: some IP addresses
- destination: any
- app & services: a list of youtube videos that I want to allow.
When I tried to go to a youtube video in the allowed list, it doesnot match with my rule but blocked by the next rule that blocks Youtube.
thanks,
Hiep.
Thank you, i have corrected that to services !
Hi Gunther,
I understood that you meant "services". I was actually asking you how the rules looked like.
(my current issue is I am not able to allow some specific youtube videos but block all others; or similarly, block a category of a site but allow other categories of the same site, for example: block https://www.bbc.com/sport but allow https://www.bbc.com as well as other categories of bbc.com)
Thanks,
Hiep.
I would suggest to create custom apps for the URLs and add them to the rulebase, but this will need to have https inspection enabled - else it will be impossible to block https://www.bbc.com/sportbut not https://www.bbc.com.
About CheckMates
Learn Check Point
Advanced Learning
YOU DESERVE THE BEST SECURITY