- Products
- Learn
- Local User Groups
- Partners
- More
Simplify Admin Operations with R82.20
Wed, 19 August @ 5pm CET/11am EDT
The industry's first AI Network Firewall
Securing AI traffic, everywhere
The State of Ransomware Q2 2026:
This Quarter's Trends, and Their Impact on Your Defenses
READY OR NOT: Securing the AI Enterprise
AI Research & Threat Landscape
CheckMates Go:
No Attack Required
🔍 Suggests trimming options for broad rules, based on log data
💬 Comment to help improve this extension
SmartConsole Extension to add RuleTrim to the right global pane.
RuleTrim samples an overly permissive rule's actual traffic from the logs and proposes a tightened ruleset, reconciled against your existing objects, with a before/after risk diff.
Extension URL: https://dannyjung.de/ruletrim.json
Installation: SmartConsole > Manage & Settings > Preferences > SmartConsole Extensions
🔍 Suggests trimming options for broad rules, based on log data
💬 Comment to help improve this extension
SmartConsole Extension to add RuleTrim to the right global pane.
RuleTrim samples an overly permissive rule's actual traffic from the logs and proposes a tightened ruleset, reconciled against your existing objects, with a before/after risk diff.
Extension URL: https://dannyjung.de/ruletrim.json
Installation: SmartConsole > Manage & Settings > Preferences > SmartConsole Extensio
Works great, thank you!
How does one stage only parts of a command with a suggested change?
Sometimes, the staging also results in an error " 6 commands failed - see SmartConsole. Nothing was published."
Where exactly can we find the cause of such error?
Works great, thank you!
How does one stage only parts of a command with a suggested change?
Sometimes, the staging also results in an error " 6 commands failed - see SmartConsole. Nothing was published."
Where exactly can we find the cause of such error?
;
Thanks for testing and for the great feedback, I'm glad it's proving useful!
Those failures were probably just "object already exists" (re-staging / leftover objects).
I implemented two fixes: staging now shows the actual API message per command, and "already exists" is treated as reused, not a failure, that should clear most of what you saw.
I also added selective staging. Hit reload and give it another go.
Thanks for testing and for the great feedback, I'm glad it's proving useful!
Those failures were probably just "object already exists" (re-staging / leftover objects).
I implemented two fixes: staging now shows the actual API message per command, and "already exists" is treated as reused, not a failure, that should clear most of what you saw.
I also added selective staging. Hit reload and give it another go.
;Hello Danny, thank you very much for the tool that I would really love to use!
Unfortunately, it doesn't seem to detect anything for a rule that is regularly used and has many logs.
The layer is the right one.
Thank you very much for all your tools!
Andy
Hello Danny, thank you very much for the tool that I would really love to use!
Unfortunately, it doesn't seem to detect anything for a rule that is regularly used and has many logs.
The layer is the right one.
Thank you very much for all your tools!
Andy
;
About CheckMates
Learn Check Point
Advanced Learning
YOU DESERVE THE BEST SECURITY