<?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: FirePower HTTPS URL Filerting in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/firepower-https-url-filerting/m-p/3372569#M961449</link>
    <description>&lt;P&gt;Thanks for clarification&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 25 Apr 2018 08:41:41 GMT</pubDate>
    <dc:creator>istewart11</dc:creator>
    <dc:date>2018-04-25T08:41:41Z</dc:date>
    <item>
      <title>FirePower HTTPS URL Filerting</title>
      <link>https://community.cisco.com/t5/network-security/firepower-https-url-filerting/m-p/3369879#M961447</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;from what I've read to do HTTPS url object filtering Cisco FirePower will check the Certificate CN name, will it also check the SAN entries?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Just wondering how it will work with a singel CN name and multiple SAN names on a cert used across multiple web sites.&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 15:39:29 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firepower-https-url-filerting/m-p/3369879#M961447</guid>
      <dc:creator>istewart11</dc:creator>
      <dc:date>2020-02-21T15:39:29Z</dc:date>
    </item>
    <item>
      <title>Re: FirePower HTTPS URL Filerting</title>
      <link>https://community.cisco.com/t5/network-security/firepower-https-url-filerting/m-p/3370083#M961448</link>
      <description>&lt;P&gt;no it does not&amp;nbsp;check the subdomains listed in the certificate, so do not use subdomains when creating the HTTPS filter.&amp;nbsp; Instead use company.com (and not &lt;A href="http://www.company.com).&amp;nbsp;" target="_blank"&gt;www.company.com).&amp;nbsp;&lt;/A&gt; In this case the filter will match the entire host name including subdomains.&lt;/P&gt;</description>
      <pubDate>Fri, 20 Apr 2018 18:59:08 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firepower-https-url-filerting/m-p/3370083#M961448</guid>
      <dc:creator>Marius Gunnerud</dc:creator>
      <dc:date>2018-04-20T18:59:08Z</dc:date>
    </item>
    <item>
      <title>Re: FirePower HTTPS URL Filerting</title>
      <link>https://community.cisco.com/t5/network-security/firepower-https-url-filerting/m-p/3372569#M961449</link>
      <description>&lt;P&gt;Thanks for clarification&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 25 Apr 2018 08:41:41 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firepower-https-url-filerting/m-p/3372569#M961449</guid>
      <dc:creator>istewart11</dc:creator>
      <dc:date>2018-04-25T08:41:41Z</dc:date>
    </item>
  </channel>
</rss>

