<?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 IPSec VPN - Multiple level chain of trust certificate in Firewall and Security Management</title>
    <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/IPSec-VPN-Multiple-level-chain-of-trust-certificate/m-p/258437#M50686</link>
    <description>&lt;P&gt;Hello,&lt;BR /&gt;I’m looking to set up a VPN tunnel using certificate-based authentication, and I have a question regarding how to implement a multi-level trust chain on an SMS (R81-20).&lt;BR /&gt;Currently, each party shares its public certificate chain for authentication. For a two-level structure (Root CA &amp;gt; Sub CA), the Root CA certificate is registered in the SMS as a Trusted CA, and the Sub CA certificate is registered as a Subordinate CA:&lt;/P&gt;&lt;P&gt;Trusted Root CA &amp;gt; Subordinate Sub CA&lt;/P&gt;&lt;P&gt;However, what is the correct process when there is a third level or more (e.g., Root CA &amp;gt; Sub CA &amp;gt; Sub-Sub CA)?&lt;BR /&gt;Registering both the Sub CA and Sub-Sub CA as subordinate CAs in the SMS leads to incorrect interpretation:&lt;/P&gt;&lt;P&gt;Trusted Root CA &amp;gt; Subordinate Sub CA&lt;BR /&gt;Trusted Root CA &amp;gt; Subordinate Sub-Sub CA&lt;/P&gt;&lt;P&gt;Alternatively, registering the Sub CA as both a Trusted CA and a Subordinate CA results in this interpretation:&lt;/P&gt;&lt;P&gt;Trusted Root CA &amp;gt; Nothing&lt;BR /&gt;Trusted Sub CA &amp;gt; Subordinate Sub CA&lt;BR /&gt;Trusted Sub CA &amp;gt; Subordinate Sub-Sub CA&lt;/P&gt;&lt;P&gt;In both cases, the SMS does not correctly interpret the full chain as:&lt;/P&gt;&lt;P&gt;Root CA certifies for Sub CA which certifies for Sub-Sub CA&lt;/P&gt;&lt;P&gt;Would you have a clue on the correct procedure for configuring a multi-level certificate trust chain in the SMS?&lt;BR /&gt;Thank you in advance.&lt;/P&gt;</description>
    <pubDate>Mon, 29 Sep 2025 09:33:23 GMT</pubDate>
    <dc:creator>Benjamin133030</dc:creator>
    <dc:date>2025-09-29T09:33:23Z</dc:date>
    <item>
      <title>IPSec VPN - Multiple level chain of trust certificate</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/IPSec-VPN-Multiple-level-chain-of-trust-certificate/m-p/258437#M50686</link>
      <description>&lt;P&gt;Hello,&lt;BR /&gt;I’m looking to set up a VPN tunnel using certificate-based authentication, and I have a question regarding how to implement a multi-level trust chain on an SMS (R81-20).&lt;BR /&gt;Currently, each party shares its public certificate chain for authentication. For a two-level structure (Root CA &amp;gt; Sub CA), the Root CA certificate is registered in the SMS as a Trusted CA, and the Sub CA certificate is registered as a Subordinate CA:&lt;/P&gt;&lt;P&gt;Trusted Root CA &amp;gt; Subordinate Sub CA&lt;/P&gt;&lt;P&gt;However, what is the correct process when there is a third level or more (e.g., Root CA &amp;gt; Sub CA &amp;gt; Sub-Sub CA)?&lt;BR /&gt;Registering both the Sub CA and Sub-Sub CA as subordinate CAs in the SMS leads to incorrect interpretation:&lt;/P&gt;&lt;P&gt;Trusted Root CA &amp;gt; Subordinate Sub CA&lt;BR /&gt;Trusted Root CA &amp;gt; Subordinate Sub-Sub CA&lt;/P&gt;&lt;P&gt;Alternatively, registering the Sub CA as both a Trusted CA and a Subordinate CA results in this interpretation:&lt;/P&gt;&lt;P&gt;Trusted Root CA &amp;gt; Nothing&lt;BR /&gt;Trusted Sub CA &amp;gt; Subordinate Sub CA&lt;BR /&gt;Trusted Sub CA &amp;gt; Subordinate Sub-Sub CA&lt;/P&gt;&lt;P&gt;In both cases, the SMS does not correctly interpret the full chain as:&lt;/P&gt;&lt;P&gt;Root CA certifies for Sub CA which certifies for Sub-Sub CA&lt;/P&gt;&lt;P&gt;Would you have a clue on the correct procedure for configuring a multi-level certificate trust chain in the SMS?&lt;BR /&gt;Thank you in advance.&lt;/P&gt;</description>
      <pubDate>Mon, 29 Sep 2025 09:33:23 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/IPSec-VPN-Multiple-level-chain-of-trust-certificate/m-p/258437#M50686</guid>
      <dc:creator>Benjamin133030</dc:creator>
      <dc:date>2025-09-29T09:33:23Z</dc:date>
    </item>
    <item>
      <title>Re: IPSec VPN - Multiple level chain of trust certificate</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/IPSec-VPN-Multiple-level-chain-of-trust-certificate/m-p/258446#M50691</link>
      <description>&lt;P&gt;Did you try setting the root CA as well?&lt;/P&gt;</description>
      <pubDate>Mon, 29 Sep 2025 11:28:41 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/IPSec-VPN-Multiple-level-chain-of-trust-certificate/m-p/258446#M50691</guid>
      <dc:creator>_Val_</dc:creator>
      <dc:date>2025-09-29T11:28:41Z</dc:date>
    </item>
    <item>
      <title>Re: IPSec VPN - Multiple level chain of trust certificate</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/IPSec-VPN-Multiple-level-chain-of-trust-certificate/m-p/258450#M50692</link>
      <description>&lt;P&gt;Yes, for both tests, the root CA was registered as Trusted CA on the SMS.&lt;/P&gt;&lt;P&gt;Test 1: We have Root CA as Trusted CA, Sub CA and Sub-Sub CA registered as Subordinate.&lt;/P&gt;&lt;P&gt;Test 2:&amp;nbsp;We have Root CA as Trusted CA, Sub CA both as Trusted CA and Subordinate CA and Sub-Sub CA only registered as Subordinate&lt;/P&gt;&lt;P&gt;Below is how the trust chain is perceived by the SMS afterward:&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Test 1:&lt;BR /&gt;Trusted Root CA &amp;gt; Subordinate Sub CA&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Trusted Root CA &amp;gt; Subordinate Sub-Sub CA&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;Test 2:&lt;BR /&gt;&lt;SPAN&gt;Trusted Root CA &amp;gt; Nothing&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Trusted Sub CA &amp;gt; Subordinate Sub CA&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Trusted Sub CA &amp;gt; Subordinate Sub-Sub CA&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&amp;gt; : is Trusted CA for (chosen automatically by the SMS)&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 29 Sep 2025 11:59:46 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/IPSec-VPN-Multiple-level-chain-of-trust-certificate/m-p/258450#M50692</guid>
      <dc:creator>Benjamin133030</dc:creator>
      <dc:date>2025-09-29T11:59:46Z</dc:date>
    </item>
    <item>
      <title>Re: IPSec VPN - Multiple level chain of trust certificate</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/IPSec-VPN-Multiple-level-chain-of-trust-certificate/m-p/258509#M50699</link>
      <description>&lt;P&gt;If it's not a Root CA you're importing, you should put the entire certificate chain in there (root and all subordinates).&lt;BR /&gt;This applies if it's a Sub Sub CA as well, as far as I know.&lt;/P&gt;</description>
      <pubDate>Tue, 30 Sep 2025 00:20:49 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/IPSec-VPN-Multiple-level-chain-of-trust-certificate/m-p/258509#M50699</guid>
      <dc:creator>PhoneBoy</dc:creator>
      <dc:date>2025-09-30T00:20:49Z</dc:date>
    </item>
  </channel>
</rss>

