<?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 Re: ISE 2.3 Patch 5 (TLS 1.0) in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/ise-2-3-patch-5-tls-1-0/m-p/3711117#M492651</link>
    <description>No please see this post&lt;BR /&gt;&lt;BR /&gt;&lt;A href="https://community.cisco.com/t5/identity-services-engine-ise/cisco-ise-tls/td-p/3549414" target="_blank"&gt;https://community.cisco.com/t5/identity-services-engine-ise/cisco-ise-tls/td-p/3549414&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;I searched google with ise tls 1.2&lt;BR /&gt;&lt;BR /&gt;</description>
    <pubDate>Fri, 21 Sep 2018 13:18:41 GMT</pubDate>
    <dc:creator>Jason Kunst</dc:creator>
    <dc:date>2018-09-21T13:18:41Z</dc:date>
    <item>
      <title>ISE 2.3 Patch 5 (TLS 1.0)</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-2-3-patch-5-tls-1-0/m-p/3711113#M492649</link>
      <description>&lt;P&gt;Is there anyway to force TLS 1.2 in ISE 2.3 patch 5? We recently installed patch 5 to remedy a bug and I was hoping to be able to remedy a vulnerability.&amp;nbsp;Our vulnerability scans show TLS 1.0 open on both our PSN and Admin nodes. and under Admin-&amp;gt;Settings-&amp;gt;Protocols-&amp;gt;Security we do not have Allow TLS 1.0 or TLS 1.1&amp;nbsp;enabled.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 21 Sep 2018 13:06:30 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-2-3-patch-5-tls-1-0/m-p/3711113#M492649</guid>
      <dc:creator>plauzon</dc:creator>
      <dc:date>2018-09-21T13:06:30Z</dc:date>
    </item>
    <item>
      <title>Re: ISE 2.3 Patch 5 (TLS 1.0)</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-2-3-patch-5-tls-1-0/m-p/3711117#M492651</link>
      <description>No please see this post&lt;BR /&gt;&lt;BR /&gt;&lt;A href="https://community.cisco.com/t5/identity-services-engine-ise/cisco-ise-tls/td-p/3549414" target="_blank"&gt;https://community.cisco.com/t5/identity-services-engine-ise/cisco-ise-tls/td-p/3549414&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;I searched google with ise tls 1.2&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Fri, 21 Sep 2018 13:18:41 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-2-3-patch-5-tls-1-0/m-p/3711117#M492651</guid>
      <dc:creator>Jason Kunst</dc:creator>
      <dc:date>2018-09-21T13:18:41Z</dc:date>
    </item>
    <item>
      <title>Re: ISE 2.3 Patch 5 (TLS 1.0)</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-2-3-patch-5-tls-1-0/m-p/3711120#M492656</link>
      <description>&lt;P&gt;Thank you - I had hoped the option would have been built into patch 5 without the need to do a full upgrade to 2.4.&lt;/P&gt;</description>
      <pubDate>Fri, 21 Sep 2018 13:21:43 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-2-3-patch-5-tls-1-0/m-p/3711120#M492656</guid>
      <dc:creator>plauzon</dc:creator>
      <dc:date>2018-09-21T13:21:43Z</dc:date>
    </item>
  </channel>
</rss>

