<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Resolving TLS1.0 and TLS1.1 Security Threats for Remote Access in Firewall and Security Management</title>
    <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Resolving-TLS1-0-and-TLS1-1-Security-Threats-for-Remote-Access/m-p/245483#M47820</link>
    <description>&lt;P&gt;I have been sent a report listing various public facing services on our firewalls and whether they are allowing TLS1.0 and TLS1.1.&lt;/P&gt;&lt;P&gt;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&lt;/P&gt;&lt;TABLE width="839px"&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD width="162.453px"&gt;Risk Vector&lt;/TD&gt;&lt;TD width="262.094px"&gt;Finding Identifier&lt;/TD&gt;&lt;TD width="89.2188px"&gt;Last Seen&lt;/TD&gt;&lt;TD width="53.5938px"&gt;Grade&lt;/TD&gt;&lt;TD width="135.391px"&gt;Attributed To&lt;/TD&gt;&lt;TD width="135.25px"&gt;Finding Severity&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD width="162.453px"&gt;SSL Configurations&lt;/TD&gt;&lt;TD width="262.094px"&gt;remoteaccess.mycompany.com:443&lt;/TD&gt;&lt;TD width="89.2188px"&gt;27/03/2025&lt;/TD&gt;&lt;TD width="53.5938px"&gt;BAD&lt;/TD&gt;&lt;TD width="135.391px"&gt;My Company Inc.&lt;/TD&gt;&lt;TD width="135.25px"&gt;severe&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;TABLE width="842px"&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD width="109.938px"&gt;Asset Importance&lt;/TD&gt;&lt;TD width="232.281px"&gt;Assets&lt;/TD&gt;&lt;TD width="498.781px"&gt;Details&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD width="109.938px"&gt;critical&lt;/TD&gt;&lt;TD width="232.281px"&gt;remoteaccess.mycompany.com&lt;/TD&gt;&lt;TD width="498.781px"&gt;Allows insecure protocol: TLSv1.0; Allows insecure protocol: TLSv1.1&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;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.&lt;/P&gt;&lt;P&gt;What could I do on the firewall to remove this vulnerability?&lt;/P&gt;&lt;P&gt;The firewalls are VSX running r81&lt;/P&gt;</description>
    <pubDate>Wed, 02 Apr 2025 14:11:21 GMT</pubDate>
    <dc:creator>P_Williams</dc:creator>
    <dc:date>2025-04-02T14:11:21Z</dc:date>
    <item>
      <title>Resolving TLS1.0 and TLS1.1 Security Threats for Remote Access</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Resolving-TLS1-0-and-TLS1-1-Security-Threats-for-Remote-Access/m-p/245483#M47820</link>
      <description>&lt;P&gt;I have been sent a report listing various public facing services on our firewalls and whether they are allowing TLS1.0 and TLS1.1.&lt;/P&gt;&lt;P&gt;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&lt;/P&gt;&lt;TABLE width="839px"&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD width="162.453px"&gt;Risk Vector&lt;/TD&gt;&lt;TD width="262.094px"&gt;Finding Identifier&lt;/TD&gt;&lt;TD width="89.2188px"&gt;Last Seen&lt;/TD&gt;&lt;TD width="53.5938px"&gt;Grade&lt;/TD&gt;&lt;TD width="135.391px"&gt;Attributed To&lt;/TD&gt;&lt;TD width="135.25px"&gt;Finding Severity&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD width="162.453px"&gt;SSL Configurations&lt;/TD&gt;&lt;TD width="262.094px"&gt;remoteaccess.mycompany.com:443&lt;/TD&gt;&lt;TD width="89.2188px"&gt;27/03/2025&lt;/TD&gt;&lt;TD width="53.5938px"&gt;BAD&lt;/TD&gt;&lt;TD width="135.391px"&gt;My Company Inc.&lt;/TD&gt;&lt;TD width="135.25px"&gt;severe&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;TABLE width="842px"&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD width="109.938px"&gt;Asset Importance&lt;/TD&gt;&lt;TD width="232.281px"&gt;Assets&lt;/TD&gt;&lt;TD width="498.781px"&gt;Details&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD width="109.938px"&gt;critical&lt;/TD&gt;&lt;TD width="232.281px"&gt;remoteaccess.mycompany.com&lt;/TD&gt;&lt;TD width="498.781px"&gt;Allows insecure protocol: TLSv1.0; Allows insecure protocol: TLSv1.1&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;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.&lt;/P&gt;&lt;P&gt;What could I do on the firewall to remove this vulnerability?&lt;/P&gt;&lt;P&gt;The firewalls are VSX running r81&lt;/P&gt;</description>
      <pubDate>Wed, 02 Apr 2025 14:11:21 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Resolving-TLS1-0-and-TLS1-1-Security-Threats-for-Remote-Access/m-p/245483#M47820</guid>
      <dc:creator>P_Williams</dc:creator>
      <dc:date>2025-04-02T14:11:21Z</dc:date>
    </item>
    <item>
      <title>Re: Resolving TLS1.0 and TLS1.1 Security Threats for Remote Access</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Resolving-TLS1-0-and-TLS1-1-Security-Threats-for-Remote-Access/m-p/245491#M47821</link>
      <description>&lt;P&gt;See &lt;A href="https://support.checkpoint.com/results/sk/sk178505" target="_blank" rel="noopener"&gt;&lt;SPAN&gt;sk178505: Which TLS version do Check Point products use?&lt;/SPAN&gt;&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;and then&lt;/P&gt;
&lt;P&gt;&lt;A href="https://support.checkpoint.com/results/sk/sk154532" target="_blank" rel="noopener"&gt;&lt;SPAN&gt;sk154532: Vulnerability scan detects that the Security Gateway supports TLS 1.0 or TLS 1.1 when one or more security blades are enabled&lt;/SPAN&gt;&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 02 Apr 2025 14:50:38 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Resolving-TLS1-0-and-TLS1-1-Security-Threats-for-Remote-Access/m-p/245491#M47821</guid>
      <dc:creator>G_W_Albrecht</dc:creator>
      <dc:date>2025-04-02T14:50:38Z</dc:date>
    </item>
    <item>
      <title>Re: Resolving TLS1.0 and TLS1.1 Security Threats for Remote Access</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Resolving-TLS1-0-and-TLS1-1-Security-Threats-for-Remote-Access/m-p/245494#M47823</link>
      <description>&lt;P&gt;That looks promising, many thanks. Looks like it will need a proper review and CAB before implementing but will feedback how I get on.&lt;/P&gt;</description>
      <pubDate>Wed, 02 Apr 2025 15:21:41 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Resolving-TLS1-0-and-TLS1-1-Security-Threats-for-Remote-Access/m-p/245494#M47823</guid>
      <dc:creator>P_Williams</dc:creator>
      <dc:date>2025-04-02T15:21:41Z</dc:date>
    </item>
    <item>
      <title>Re: Resolving TLS1.0 and TLS1.1 Security Threats for Remote Access</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Resolving-TLS1-0-and-TLS1-1-Security-Threats-for-Remote-Access/m-p/245496#M47825</link>
      <description>&lt;P&gt;Hey&amp;nbsp;&lt;a href="https://community.checkpoint.com/t5/user/viewprofilepage/user-id/80853"&gt;@P_Williams&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I believe you can also correct this with settings I attached from global properties.&lt;/P&gt;
&lt;P&gt;Andy&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 02 Apr 2025 16:29:31 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Resolving-TLS1-0-and-TLS1-1-Security-Threats-for-Remote-Access/m-p/245496#M47825</guid>
      <dc:creator>the_rock</dc:creator>
      <dc:date>2025-04-02T16:29:31Z</dc:date>
    </item>
    <item>
      <title>Re: Resolving TLS1.0 and TLS1.1 Security Threats for Remote Access</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Resolving-TLS1-0-and-TLS1-1-Security-Threats-for-Remote-Access/m-p/245547#M47849</link>
      <description>&lt;P&gt;It is just an advanced Portal configuration option in SmartDashboard menue, see the screenshot &lt;a href="https://community.checkpoint.com/t5/user/viewprofilepage/user-id/38213"&gt;@the_rock&lt;/a&gt; has posted.&lt;/P&gt;</description>
      <pubDate>Thu, 03 Apr 2025 08:22:48 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Resolving-TLS1-0-and-TLS1-1-Security-Threats-for-Remote-Access/m-p/245547#M47849</guid>
      <dc:creator>G_W_Albrecht</dc:creator>
      <dc:date>2025-04-03T08:22:48Z</dc:date>
    </item>
    <item>
      <title>Re: Resolving TLS1.0 and TLS1.1 Security Threats for Remote Access</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Resolving-TLS1-0-and-TLS1-1-Security-Threats-for-Remote-Access/m-p/245548#M47850</link>
      <description>&lt;P&gt;Yes, found here: &lt;A href="https://support.checkpoint.com/results/sk/sk154532" target="_blank" rel="noopener noreferrer"&gt;&lt;SPAN&gt;sk154532: Vulnerability scan detects that the Security Gateway supports TLS 1.0 or TLS 1.1 when one ...&lt;/SPAN&gt;&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 03 Apr 2025 08:21:46 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Resolving-TLS1-0-and-TLS1-1-Security-Threats-for-Remote-Access/m-p/245548#M47850</guid>
      <dc:creator>G_W_Albrecht</dc:creator>
      <dc:date>2025-04-03T08:21:46Z</dc:date>
    </item>
    <item>
      <title>Re: Resolving TLS1.0 and TLS1.1 Security Threats for Remote Access</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Resolving-TLS1-0-and-TLS1-1-Security-Threats-for-Remote-Access/m-p/245554#M47852</link>
      <description>&lt;P&gt;Sorry, my bad, it asked me to log in to view that sk when I tried yesterday, but I see it now.&lt;/P&gt;
&lt;P&gt;Andy&lt;/P&gt;</description>
      <pubDate>Thu, 03 Apr 2025 10:42:50 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Resolving-TLS1-0-and-TLS1-1-Security-Threats-for-Remote-Access/m-p/245554#M47852</guid>
      <dc:creator>the_rock</dc:creator>
      <dc:date>2025-04-03T10:42:50Z</dc:date>
    </item>
    <item>
      <title>Re: Resolving TLS1.0 and TLS1.1 Security Threats for Remote Access</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Resolving-TLS1-0-and-TLS1-1-Security-Threats-for-Remote-Access/m-p/245592#M47858</link>
      <description>&lt;P&gt;You did post the shortcut &lt;span class="lia-unicode-emoji" title=":upside_down_face:"&gt;🙃&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 03 Apr 2025 13:15:54 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Resolving-TLS1-0-and-TLS1-1-Security-Threats-for-Remote-Access/m-p/245592#M47858</guid>
      <dc:creator>G_W_Albrecht</dc:creator>
      <dc:date>2025-04-03T13:15:54Z</dc:date>
    </item>
    <item>
      <title>Re: Resolving TLS1.0 and TLS1.1 Security Threats for Remote Access</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Resolving-TLS1-0-and-TLS1-1-Security-Threats-for-Remote-Access/m-p/247006#M48200</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;Just confirming that this worked, we changed the setting to 1.2 and the vulnerability scan has now succeeded. Thank you&lt;/P&gt;</description>
      <pubDate>Tue, 22 Apr 2025 13:10:49 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Resolving-TLS1-0-and-TLS1-1-Security-Threats-for-Remote-Access/m-p/247006#M48200</guid>
      <dc:creator>P_Williams</dc:creator>
      <dc:date>2025-04-22T13:10:49Z</dc:date>
    </item>
  </channel>
</rss>

