- Products
- Learn
- Local User Groups
- Partners
- More
What's New in R82.10?
10 December @ 5pm CET / 11am ET
Improve Your Security Posture with
Threat Prevention and Policy Insights
Overlap in Security Validation
Help us to understand your needs better
CheckMates Go:
Maestro Madness
Doesn't seem to be possible from what I can tell, I poked around in the GUIdbedit objects_5_0.C settings and the $FWDIR/lib/*.def files and didn't see any kind of property setting that controls this behavior.
Can you elaborate please? What are you trying to achieve?
I am trying to enable AppCtrl on our GWs. This is done by activating the blade activating the protocol signature in the respective services, that are used in the access layer. Unfortunately the protocol signature check is disabled by default in any service and must be activated manually. I want to activate it by default, so any service has the box check automatically.
I think you misunderstand what Application Control is, and how it is intended to work.
There are services, and there are applications. You can use both in the rulebase. Maybe start with sk112249 and Admin manuals.
The R80+ Protocol Signature & Protocol settings on the service objects are the source of a lot of confusion but as Val said is mostly separate from Application Control. Understanding the ramifications of enabling the Protocol Signature setting beforehand is highly advisable. This seems to be one area that does not have a lot of documentation, so I took my best shot at trying to explain it in my unpublished "APCL/URLF Immersion" class for a private customer. Whether I did a good job or not is left as an exercise for the reader, see below. 😀
Thanks for the explanation. So is there a way to enable the protocol signature check by default on any supporting protocols/services/whatever-you-may-name-them?
Doesn't seem to be possible from what I can tell, I poked around in the GUIdbedit objects_5_0.C settings and the $FWDIR/lib/*.def files and didn't see any kind of property setting that controls this behavior.
Not all services are having those signatures in the first place.
Leaderboard
Epsum factorial non deposit quid pro quo hic escorol.
| User | Count |
|---|---|
| 15 | |
| 10 | |
| 8 | |
| 6 | |
| 5 | |
| 5 | |
| 4 | |
| 4 | |
| 4 | |
| 3 |
Wed 03 Dec 2025 @ 10:00 AM (COT)
Última Sesión del Año – CheckMates LATAM: ERM & TEM con ExpertosThu 04 Dec 2025 @ 12:30 PM (SGT)
End-of-Year Event: Securing AI Transformation in a Hyperconnected World - APACThu 04 Dec 2025 @ 03:00 PM (CET)
End-of-Year Event: Securing AI Transformation in a Hyperconnected World - EMEAThu 04 Dec 2025 @ 02:00 PM (EST)
End-of-Year Event: Securing AI Transformation in a Hyperconnected World - AmericasWed 03 Dec 2025 @ 10:00 AM (COT)
Última Sesión del Año – CheckMates LATAM: ERM & TEM con ExpertosThu 04 Dec 2025 @ 12:30 PM (SGT)
End-of-Year Event: Securing AI Transformation in a Hyperconnected World - APACThu 04 Dec 2025 @ 03:00 PM (CET)
End-of-Year Event: Securing AI Transformation in a Hyperconnected World - EMEAThu 04 Dec 2025 @ 02:00 PM (EST)
End-of-Year Event: Securing AI Transformation in a Hyperconnected World - AmericasAbout CheckMates
Learn Check Point
Advanced Learning
YOU DESERVE THE BEST SECURITY