<?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: Subordinate CA creation for SSL Decryption in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/subordinate-ca-creation-for-ssl-decryption/m-p/156930#M51516</link>
    <description>&lt;P&gt;Functionally, the CN won't really matter. The user is presented a server certificate that matches the CN and SAN fields of the destination server, but it's signed by the CA you're creating. Some admins choose something descriptive like "SSL-TLS Inspection", while others will simply use something like "MyCompany Security Team".&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;It won't actually matter, it's really just a matter of preference. It shows up as the signer, so most users won't even see it unless they have a habit of checking the certificate chain.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Edit: You'll want to include the "Host Name" option as well. Chrome 57 (I think) has deprecated the CN field. If your CA doesn't have a SAN (using the Host Name field) it may complain. I haven't tested it, but it's worth considering.&lt;/P&gt;</description>
    <pubDate>Tue, 16 May 2017 18:24:47 GMT</pubDate>
    <dc:creator>gwesson</dc:creator>
    <dc:date>2017-05-16T18:24:47Z</dc:date>
    <item>
      <title>Subordinate CA creation for SSL Decryption</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/subordinate-ca-creation-for-ssl-decryption/m-p/156912#M51509</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; I am attempting&amp;nbsp;to set up SSL Decryption on a new firewall&amp;nbsp;and trying to create a Subordinate CA with our internal Microsoft Certificate Services.&amp;nbsp; I am in the process of generating the CSR on the PA, but I am a little confused on what the Common Name should be.&lt;/P&gt;&lt;P&gt;&amp;nbsp; Should it be the Inside interface IP, Outside interface IP, the AD domain controller name?&amp;nbsp; I am stumped.&amp;nbsp; If someone could give me a pointer, I would apprecaite it.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;&amp;nbsp; Steve&lt;/P&gt;</description>
      <pubDate>Tue, 16 May 2017 14:49:40 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/subordinate-ca-creation-for-ssl-decryption/m-p/156912#M51509</guid>
      <dc:creator>Steve27596</dc:creator>
      <dc:date>2017-05-16T14:49:40Z</dc:date>
    </item>
    <item>
      <title>Re: Subordinate CA creation for SSL Decryption</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/subordinate-ca-creation-for-ssl-decryption/m-p/156917#M51511</link>
      <description>&lt;P&gt;&lt;SPAN&gt;In the &lt;/SPAN&gt;Common Name&lt;SPAN&gt; field, enter the FQDN (recommended) or IP address of the interface where you will configure the service that will use this certificate. So FQDN of the inside interface (client&amp;nbsp;facing interface) is the way to go. But for sure other members will&amp;nbsp;give you a better advice as I am not a great fan of the&amp;nbsp;SSL decryption &lt;span class="lia-unicode-emoji" title=":grinning_face_with_smiling_eyes:"&gt;😄&lt;/span&gt;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 16 May 2017 15:50:07 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/subordinate-ca-creation-for-ssl-decryption/m-p/156917#M51511</guid>
      <dc:creator>TranceforLife</dc:creator>
      <dc:date>2017-05-16T15:50:07Z</dc:date>
    </item>
    <item>
      <title>Re: Subordinate CA creation for SSL Decryption</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/subordinate-ca-creation-for-ssl-decryption/m-p/156930#M51516</link>
      <description>&lt;P&gt;Functionally, the CN won't really matter. The user is presented a server certificate that matches the CN and SAN fields of the destination server, but it's signed by the CA you're creating. Some admins choose something descriptive like "SSL-TLS Inspection", while others will simply use something like "MyCompany Security Team".&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;It won't actually matter, it's really just a matter of preference. It shows up as the signer, so most users won't even see it unless they have a habit of checking the certificate chain.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Edit: You'll want to include the "Host Name" option as well. Chrome 57 (I think) has deprecated the CN field. If your CA doesn't have a SAN (using the Host Name field) it may complain. I haven't tested it, but it's worth considering.&lt;/P&gt;</description>
      <pubDate>Tue, 16 May 2017 18:24:47 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/subordinate-ca-creation-for-ssl-decryption/m-p/156930#M51516</guid>
      <dc:creator>gwesson</dc:creator>
      <dc:date>2017-05-16T18:24:47Z</dc:date>
    </item>
    <item>
      <title>Re: Subordinate CA creation for SSL Decryption</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/subordinate-ca-creation-for-ssl-decryption/m-p/157001#M51537</link>
      <description>&lt;P&gt;SSL Certs are always being an interesting subject. Doesn't look complex but easy&amp;nbsp;to get confused (at least for me :D)&lt;/P&gt;&lt;P&gt;Thanks for the explanation&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 17 May 2017 06:50:16 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/subordinate-ca-creation-for-ssl-decryption/m-p/157001#M51537</guid>
      <dc:creator>TranceforLife</dc:creator>
      <dc:date>2017-05-17T06:50:16Z</dc:date>
    </item>
  </channel>
</rss>

