- Products
- Learn
- Local User Groups
- Partners
- More
Policy Insights and Policy Auditor in Action
19 November @ 5pm CET / 11am ET
Access Control and Threat Prevention Best Practices
Watch HereOverlap in Security Validation
Help us to understand your needs better
CheckMates Go:
Maestro Madness
Hi,
We need to allow users to reach a certain site but avoid tracking the connection.
We created a rule setting logging to "none" but the console displays the error Connection terminated before the Security Gateway was able to make a decision: Insufficient data passed. To learn more see sk113479.
Connection starts in http and then switches to https. Only http traffic (with the error) is logged. Https is correctly not tracked
Has anyone found themselves in the same situation and managed to resolve it?
Release is 81.10, blade are firewall and application control
Thx for your support
F
If the rule that is matched in the other layer is set to log, the connection will be logged.
This is expected behavior.
If this isn't the case, I recommend a TAC case: https://help.checkpoint.com
What does the rule that permits the traffic look like?
Unless it contains http explicitly (the service), this is expected behavior.
To resolve the issue, add http to the the Services for the relevant rule (or create a new one).
Hi @PhoneBoy , thx for your response.
Rule number 1 (above all) looks like this:
Source = Any
Destination = IP Address Object
Services = http,https
Log = None
Install On = Target Cluster
Still logging
Can you provide a full log card (with sensitive details redacted)?
I suspect this may be a bug of some sort and will require TAC to assist: https://help.checkpoint.com
Hi @Daphne_Reese , what is exactly needed (when you say 'full log card')
When you double-click on an individual log entry, you will see a screen pop up with more details; This is the log card.
Hi, today we splitted the rule.
Rule 1 for service HTTP, Drop, No-Log
Rule 2 switched Services to ANY, Accept, No-Log (Any protocol: ping, https, ntp, etc)
Rule Number 1 is matched and no log is present for HTTP - that's ok
For HTTPS, as you can see, matched rule is exactly number 2 but still logging
What is the precise destination here?
Is it the gateway or something else?
What about using the explicit https service in Rule 2?
Are there other ordered Access Policy layers in use or just the one?
What is the precise destination here? Destination is an IP Address (in rule we put IP Address Object)
Is it the gateway or something else? External WebSite
What about using the explicit https service in Rule 2? Tried without success
Are there other ordered Access Policy layers in use or just the one? URL/App filtering with allow policy but no log about AppControl blade
If the rule that is matched in the other layer is set to log, the connection will be logged.
This is expected behavior.
If this isn't the case, I recommend a TAC case: https://help.checkpoint.com
Hi @PhoneBoy we will set no-log on all layers and try again.
Otherwise we will open the TAC case.
Thx
F
Leaderboard
Epsum factorial non deposit quid pro quo hic escorol.
| User | Count |
|---|---|
| 25 | |
| 14 | |
| 13 | |
| 8 | |
| 5 | |
| 4 | |
| 3 | |
| 3 | |
| 3 | |
| 2 |
Wed 19 Nov 2025 @ 11:00 AM (EST)
TechTalk: Improve Your Security Posture with Threat Prevention and Policy InsightsThu 20 Nov 2025 @ 05:00 PM (CET)
Hacking LLM Applications: latest research and insights from our LLM pen testing projects - AMERThu 20 Nov 2025 @ 10:00 AM (CST)
Hacking LLM Applications: latest research and insights from our LLM pen testing projects - EMEAWed 26 Nov 2025 @ 12:00 PM (COT)
Panama City: Risk Management a la Parrilla: ERM, TEM & Meat LunchWed 19 Nov 2025 @ 11:00 AM (EST)
TechTalk: Improve Your Security Posture with Threat Prevention and Policy InsightsThu 20 Nov 2025 @ 05:00 PM (CET)
Hacking LLM Applications: latest research and insights from our LLM pen testing projects - AMERThu 20 Nov 2025 @ 10:00 AM (CST)
Hacking LLM Applications: latest research and insights from our LLM pen testing projects - EMEAThu 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 - EMEAWed 26 Nov 2025 @ 12:00 PM (COT)
Panama City: Risk Management a la Parrilla: ERM, TEM & Meat LunchAbout CheckMates
Learn Check Point
Advanced Learning
YOU DESERVE THE BEST SECURITY