<?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 Known limitations of External Discovery and Virtually hosted certificates (SNI) in Network Security Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/network-security-discussions/known-limitations-of-external-discovery-and-virtually-hosted/m-p/1419283#M445</link>
    <description>&lt;P&gt;Hi all, Zach here again from the VaaS team. I wanted to discuss a recent issue that we had that could be effecting your environment if External Discovery is not configured properly and if you have certificates being virtually hosted via SNI.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;SNI virtual hosting allows multiple sites and certificates to be hosted on the same IP address. When an External Discovery is performed, the scanner is scanning the public IP address for TLS certificates and will match the results against the registered domains. However, this discovery is only able to discover the default certificates installed at a given IP address. If a certificate is installed using SNI and it is not the default certificate, it might not be found during this discovery.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;To address this, you can add the FQDN explicitly as a target for External Discovery and VaaS should pick up the correct certificate then.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;As always you can post below if you have any additional questions or open a ticket with support if needed. Thanks!&lt;/P&gt;</description>
    <pubDate>Thu, 25 Aug 2022 00:40:25 GMT</pubDate>
    <dc:creator>CyberArkAlumni</dc:creator>
    <dc:date>2022-08-25T00:40:25Z</dc:date>
    <item>
      <title>Known limitations of External Discovery and Virtually hosted certificates (SNI)</title>
      <link>https://live.paloaltonetworks.com/t5/network-security-discussions/known-limitations-of-external-discovery-and-virtually-hosted/m-p/1419283#M445</link>
      <description>&lt;P&gt;Hi all, Zach here again from the VaaS team. I wanted to discuss a recent issue that we had that could be effecting your environment if External Discovery is not configured properly and if you have certificates being virtually hosted via SNI.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;SNI virtual hosting allows multiple sites and certificates to be hosted on the same IP address. When an External Discovery is performed, the scanner is scanning the public IP address for TLS certificates and will match the results against the registered domains. However, this discovery is only able to discover the default certificates installed at a given IP address. If a certificate is installed using SNI and it is not the default certificate, it might not be found during this discovery.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;To address this, you can add the FQDN explicitly as a target for External Discovery and VaaS should pick up the correct certificate then.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;As always you can post below if you have any additional questions or open a ticket with support if needed. Thanks!&lt;/P&gt;</description>
      <pubDate>Thu, 25 Aug 2022 00:40:25 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/network-security-discussions/known-limitations-of-external-discovery-and-virtually-hosted/m-p/1419283#M445</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2022-08-25T00:40:25Z</dc:date>
    </item>
  </channel>
</rss>

