- Products
- Learn
- Local User Groups
- Partners
- More
Step Into the Future of
AI-Powered Cyber Security
The State of Ransomware Q1 2026
Key Trends and Their Impact
AI Security Masters E8:
Claude Mythos: New Era in Cyber Security
Blueprint Architecture for Securing
The AI Factory & AI Data Center
Call For Papers
Your Expertise. Our Stage
CheckMates Go:
CheckMates Fest
I have been sent a report listing various public facing services on our firewalls and whether they are allowing TLS1.0 and TLS1.1.
For the URL that clients use to connect to use the Remote Access vpn it has come back as allowing 1.0 and 1.1
| Risk Vector | Finding Identifier | Last Seen | Grade | Attributed To | Finding Severity |
| SSL Configurations | remoteaccess.mycompany.com:443 | 27/03/2025 | BAD | My Company Inc. | severe |
| Asset Importance | Assets | Details |
| critical | remoteaccess.mycompany.com | Allows insecure protocol: TLSv1.0; Allows insecure protocol: TLSv1.1 |
Presumably the client, when it connects initially, wouldn't be using 1.0 or 1.1. But beyond that I don't know what I can do to get rid of the vulnerability. I am not sure if the vulnerability even is to do with the RemoteAccess service, it is just that it uses the same public IP as the firewalls.
What could I do on the firewall to remove this vulnerability?
The firewalls are VSX running r81
Yes, found here: sk154532: Vulnerability scan detects that the Security Gateway supports TLS 1.0 or TLS 1.1 when one ...
See sk178505: Which TLS version do Check Point products use?
and then
That looks promising, many thanks. Looks like it will need a proper review and CAB before implementing but will feedback how I get on.
It is just an advanced Portal configuration option in SmartDashboard menue, see the screenshot @the_rock has posted.
Hi,
Just confirming that this worked, we changed the setting to 1.2 and the vulnerability scan has now succeeded. Thank you
Hey @P_Williams
I believe you can also correct this with settings I attached from global properties.
Andy
Yes, found here: sk154532: Vulnerability scan detects that the Security Gateway supports TLS 1.0 or TLS 1.1 when one ...
Sorry, my bad, it asked me to log in to view that sk when I tried yesterday, but I see it now.
Andy
You did post the shortcut 🙃
Leaderboard
Epsum factorial non deposit quid pro quo hic escorol.
| User | Count |
|---|---|
| 24 | |
| 19 | |
| 10 | |
| 9 | |
| 8 | |
| 7 | |
| 6 | |
| 4 | |
| 4 | |
| 4 |
Fri 29 May 2026 @ 09:00 AM (EDT)
Caracas: Executive Breakfast: Innovación en Ciberseguridad – IA y Threat IntelligenceTue 02 Jun 2026 @ 06:00 PM (IDT)
Under the Hood | Check Point SASE: Identity Integration & Access Policy Design Best PracticesThu 04 Jun 2026 @ 02:00 PM (CEST)
Deep Dive Webinar: New CloudGuard GWLB Deployment Without NAT Gateways - EuropeTue 02 Jun 2026 @ 06:00 PM (IDT)
Under the Hood | Check Point SASE: Identity Integration & Access Policy Design Best PracticesThu 04 Jun 2026 @ 02:00 PM (CEST)
Deep Dive Webinar: New CloudGuard GWLB Deployment Without NAT Gateways - EuropeThu 04 Jun 2026 @ 07:00 PM (IDT)
Deep Dive Webinar: New CloudGuard GWLB Deployment Without NAT Gateways - AmericaFri 12 Jun 2026 @ 10:00 AM (CEST)
CheckMates Live Netherlands - Sessie 47: Continuous Threat Exposure ManagementFri 29 May 2026 @ 09:00 AM (EDT)
Caracas: Executive Breakfast: Innovación en Ciberseguridad – IA y Threat IntelligenceAbout CheckMates
Learn Check Point
Advanced Learning
YOU DESERVE THE BEST SECURITY