<?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: IPsec Site to Site Tunnel Crypto in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/ipsec-site-to-site-tunnel-crypto/m-p/24435#M17825</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; The DH group signifies the strength of the key. Higher the DH group, stronger is the key and hence more secure. Saying that, the higher the DH group more will be the processing time as the key size is larger. Below are the numbers:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;DH group 1: 768-bit key&lt;/LI&gt;&lt;LI&gt;DH group 2: 1024-bit key&lt;/LI&gt;&lt;LI&gt;DH group 5: 1536-bit key&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; If you you have enabled FIPS mode on the firewall and want to know what cipher suites are supported by the PA, go through the discussion on the following thread :&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A __default_attr="25828" __jive_macro_name="message" class="jive_macro jive_macro_message" href="https://live.paloaltonetworks.com/"&gt;&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; The key size in the AES signifies the number of repetition cycles with each cycle consisting of finite processing steps to convert a plain text into a cipher text. The repetition cycles are more in AES256 ( 14 cycles) as compared to AES128 ( 10 cycles ). The additional 4 cycles can delay the processing time.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; If computing time for hash is not a concern, then SHA512 should be preferred. Note that more time to compute hash means more time to crack the hash. Hope this was helpful to you.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Tilak&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 23 Jul 2013 18:59:40 GMT</pubDate>
    <dc:creator>tshiv</dc:creator>
    <dc:date>2013-07-23T18:59:40Z</dc:date>
    <item>
      <title>IPsec Site to Site Tunnel Crypto</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/ipsec-site-to-site-tunnel-crypto/m-p/24434#M17824</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;All,&lt;/P&gt;&lt;P&gt;First, please forgive me if this has been asked before, I wasn't able to find anything conclusive with any good explanation.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Recently I renewed a couple of web server certificates and in doing so the CA recommended that I use SHA2 with a 256-bit message digest as SHA1 was known to have been cracked and was weak. This lead to some further digging on some of the crypto stuff for the PAN firewalls and noticed that a site-to-site IPsec tunnel I had setup nearly a year ago is using SHA1 (both are PAN firewalls). My current config is:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;IKE Crypto is using:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Encryption - aes128, 3des&lt;/LI&gt;&lt;LI&gt;Authentication - sha1&lt;/LI&gt;&lt;LI&gt;DH Group - group2&lt;/LI&gt;&lt;LI&gt;Lifetime - 8 hours&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;IPsec Crypto is using:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;ESP/AH - ESP&lt;/LI&gt;&lt;LI&gt;Encryption - aes128, 3des&lt;/LI&gt;&lt;LI&gt;Authentication - sha1&lt;/LI&gt;&lt;LI&gt;DH Group - group2&lt;/LI&gt;&lt;LI&gt;Lifetime - 1 hours&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I kinda followed the 'book' based on PAN's documentation from a couple years ago, and some of the details are coming back to me, but what I am wondering if implementing some of the higher encryption/authentication standards can be done by stacking.&amp;nbsp; I believe I can do this on both sides with no problem, but what I am little fuzzy on is the DH group setting and does that need to be adjusted. I found this site that explained the details a little bit more: &lt;A href="http://publib.boulder.ibm.com/infocenter/zosmf/vxrx/index.jsp?topic=%2Fcom.ibm.tcp.ipsec.ipsec.help.doc%2Fcom%2Fibm%2Ftcp%2Fipsec%2Fipsec%2FPS_DT_Adv_PFS.CB_Initiate.html" title="http://publib.boulder.ibm.com/infocenter/zosmf/vxrx/index.jsp?topic=%2Fcom.ibm.tcp.ipsec.ipsec.help.doc%2Fcom%2Fibm%2Ftcp%2Fipsec%2Fipsec%2FPS_DT_Adv_PFS.CB_Initiate.html"&gt;Help - IBM z/OS Management Facility&lt;/A&gt;.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Additionally what has been your experience with using AES256 over AES128 for encryption - any performance issues? (IPsec crypto also supports AES128 CCM16). And for Authentication SHA512 over SHA256?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for any help. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 23 Jul 2013 17:57:27 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/ipsec-site-to-site-tunnel-crypto/m-p/24434#M17824</guid>
      <dc:creator>cmateam</dc:creator>
      <dc:date>2013-07-23T17:57:27Z</dc:date>
    </item>
    <item>
      <title>Re: IPsec Site to Site Tunnel Crypto</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/ipsec-site-to-site-tunnel-crypto/m-p/24435#M17825</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; The DH group signifies the strength of the key. Higher the DH group, stronger is the key and hence more secure. Saying that, the higher the DH group more will be the processing time as the key size is larger. Below are the numbers:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;DH group 1: 768-bit key&lt;/LI&gt;&lt;LI&gt;DH group 2: 1024-bit key&lt;/LI&gt;&lt;LI&gt;DH group 5: 1536-bit key&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; If you you have enabled FIPS mode on the firewall and want to know what cipher suites are supported by the PA, go through the discussion on the following thread :&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A __default_attr="25828" __jive_macro_name="message" class="jive_macro jive_macro_message" href="https://live.paloaltonetworks.com/"&gt;&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; The key size in the AES signifies the number of repetition cycles with each cycle consisting of finite processing steps to convert a plain text into a cipher text. The repetition cycles are more in AES256 ( 14 cycles) as compared to AES128 ( 10 cycles ). The additional 4 cycles can delay the processing time.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; If computing time for hash is not a concern, then SHA512 should be preferred. Note that more time to compute hash means more time to crack the hash. Hope this was helpful to you.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Tilak&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 23 Jul 2013 18:59:40 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/ipsec-site-to-site-tunnel-crypto/m-p/24435#M17825</guid>
      <dc:creator>tshiv</dc:creator>
      <dc:date>2013-07-23T18:59:40Z</dc:date>
    </item>
    <item>
      <title>Re: IPsec Site to Site Tunnel Crypto</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/ipsec-site-to-site-tunnel-crypto/m-p/24436#M17826</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello, there had been issues seen with DH group set for cisco devices. Can you try setting up DH as no-pfs on both ends and check?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 25 Jul 2013 01:40:09 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/ipsec-site-to-site-tunnel-crypto/m-p/24436#M17826</guid>
      <dc:creator>ukhapre</dc:creator>
      <dc:date>2013-07-25T01:40:09Z</dc:date>
    </item>
    <item>
      <title>Re: IPsec Site to Site Tunnel Crypto</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/ipsec-site-to-site-tunnel-crypto/m-p/24437#M17827</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;ukhapre,&lt;/P&gt;&lt;P&gt;In our site to site setup, we are not using and Cisco products. Both sides are PAN-2020s.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 25 Jul 2013 16:41:58 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/ipsec-site-to-site-tunnel-crypto/m-p/24437#M17827</guid>
      <dc:creator>cmateam</dc:creator>
      <dc:date>2013-07-25T16:41:58Z</dc:date>
    </item>
  </channel>
</rss>

