- Products
- Learn
- Local User Groups
- Partners
- More
CheckMates Fifth Birthday
Celebrate with Us!
days
hours
minutes
seconds
Join the CHECKMATES Everywhere Competition
Submit your picture to win!
Check Point Proactive support
Free trial available for 90 Days!
As YOU DESERVE THE BEST SECURITY
Upgrade to our latest GA Jumbo
The 2022 MITRE Engenuity ATT&CK®
Evaluations Results Are In!
Now Available: SmartAwareness Security Training
Training Built to Educate and Engage
MITRE ATT&CK
Inside Check Point products!
CheckFlix!
All Videos In One Space
Hi Damon,
SmartConsole version 105
Gateway and Mgmt HotFix 169 on R80.10.
Tom
It's definitely not allowed in R80.20 either.
@Dima_M any ideas on this one?
You're right, this behavior is by design, motivation is to prevent collisions.
Could you please share more details about your use case?
Access Role can represent Any User@Specific Network - do you think it will be useful in your case?
Hi Dima,
Okay, that's something we also thought about internally as well and I can see the reasoning behind it.
All I wanted to avoid was including both an access role and networks in a single rule to avoid having two identical rules apart from the source column; not a huge deal just wondered if this was a fault I'd done or was by design.
Let me know though if you have any suggestions though?
Tom
Hey Tom,
How about {Any/Any Identified Users/Machines} + {Specific Network} in access role - can it substitute the network object in your case?
Hi Dima,
That could potentially work, would take a slight redesign from our current standard, but seems like a viable option.
Thanks for the tip.
Tom.
About CheckMates
Learn Check Point
Advanced Learning
YOU DESERVE THE BEST SECURITY