<?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: Multiple outbound HTTPS inspection certificates in Firewall and Security Management</title>
    <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Multiple-outbound-HTTPS-inspection-certificates/m-p/158201#M27584</link>
    <description>&lt;P&gt;What we allow for outbound HTTPS inspection is a single CA to be used per management domain.&lt;BR /&gt;That ultimately signs all the outbound certificates generated for user connections.&lt;/P&gt;
&lt;P&gt;That implies MDM is a potential workaround for this.&lt;BR /&gt;Like you point out, these operations in can potentially be automated in R81.20.&lt;BR /&gt;Otherwise having different Outbound CA certs for different gateways managed by the same management domain is an RFE.&lt;/P&gt;</description>
    <pubDate>Tue, 27 Sep 2022 16:48:38 GMT</pubDate>
    <dc:creator>PhoneBoy</dc:creator>
    <dc:date>2022-09-27T16:48:38Z</dc:date>
    <item>
      <title>Multiple outbound HTTPS inspection certificates</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Multiple-outbound-HTTPS-inspection-certificates/m-p/158198#M27583</link>
      <description>&lt;P&gt;I believe this was &lt;A href="https://community.checkpoint.com/t5/General-Topics/Multiple-Gateways-with-different-outbound-certificate-for-https/m-p/61261#" target="_self"&gt;asked 3 years ago&lt;/A&gt;, but not properly answered (if at all).&amp;nbsp; I've asked a few folks as well, but nothing yet.&lt;/P&gt;&lt;P&gt;The desire is to have different certificates/CA's used on/by different gateways.&amp;nbsp; One example would be different locations with separate Active Directory domains.&amp;nbsp; Users at each location already have different trusted CA's and would ideally be presented with different trusted root CA's upon outbound inspection.&lt;/P&gt;&lt;P&gt;AFAIK there is only a single outbound inspection certificate (whether internal or imported) - installed on the SMS and deployed to GW's during access policy installation.&lt;/P&gt;&lt;P&gt;One [rather impractical] workaround could be to install policy to site A, re-import site B's certificate (scriptable in R81.20?), install policy to site B.&amp;nbsp; If R81.20's certificate scripting permits (as I've read), this could become fairly automated if we script all policy installation operations.&amp;nbsp; Somewhat ugly, but it may at least help better covey the goal.&lt;/P&gt;&lt;P&gt;Even more ideally (but likely more of an RFE), what about allowing multiple &lt;EM&gt;outbound&lt;/EM&gt; certificates in the inspection policy?&amp;nbsp; The policy already allows for certificate selection - but only for inbound.&amp;nbsp; Allowing certificate selection in outbound inspection rules would allow for even greater flexibility, like using roles and dynamic objects in source - allowing members of different AD domains (and even non-member machines) to use different certs.&amp;nbsp; We can always dream &lt;span class="lia-unicode-emoji" title=":winking_face:"&gt;😉&lt;/span&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;-E&lt;/P&gt;</description>
      <pubDate>Tue, 27 Sep 2022 16:43:06 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Multiple-outbound-HTTPS-inspection-certificates/m-p/158198#M27583</guid>
      <dc:creator>EricAnderson</dc:creator>
      <dc:date>2022-09-27T16:43:06Z</dc:date>
    </item>
    <item>
      <title>Re: Multiple outbound HTTPS inspection certificates</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Multiple-outbound-HTTPS-inspection-certificates/m-p/158201#M27584</link>
      <description>&lt;P&gt;What we allow for outbound HTTPS inspection is a single CA to be used per management domain.&lt;BR /&gt;That ultimately signs all the outbound certificates generated for user connections.&lt;/P&gt;
&lt;P&gt;That implies MDM is a potential workaround for this.&lt;BR /&gt;Like you point out, these operations in can potentially be automated in R81.20.&lt;BR /&gt;Otherwise having different Outbound CA certs for different gateways managed by the same management domain is an RFE.&lt;/P&gt;</description>
      <pubDate>Tue, 27 Sep 2022 16:48:38 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Multiple-outbound-HTTPS-inspection-certificates/m-p/158201#M27584</guid>
      <dc:creator>PhoneBoy</dc:creator>
      <dc:date>2022-09-27T16:48:38Z</dc:date>
    </item>
    <item>
      <title>Re: Multiple outbound HTTPS inspection certificates</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Multiple-outbound-HTTPS-inspection-certificates/m-p/158213#M27585</link>
      <description>&lt;P&gt;Thanks for confirming, bud.&lt;/P&gt;&lt;P&gt;Makes sense that MDM would work, but even more impractical than scripting in this case.&lt;/P&gt;&lt;P&gt;Thinking about the scripting more, it makes me wish "&lt;EM&gt;Before&lt;/EM&gt; install Policy" was a SmartTask trigger &lt;span class="lia-unicode-emoji" title=":winking_face:"&gt;😉&lt;/span&gt;&lt;/P&gt;&lt;P&gt;Still curious if anyone else has any creative ideas, or even just has the same need/desire.&lt;/P&gt;&lt;P&gt;-E&lt;/P&gt;</description>
      <pubDate>Tue, 27 Sep 2022 17:37:11 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Multiple-outbound-HTTPS-inspection-certificates/m-p/158213#M27585</guid>
      <dc:creator>EricAnderson</dc:creator>
      <dc:date>2022-09-27T17:37:11Z</dc:date>
    </item>
  </channel>
</rss>

