<?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: ITATP151W Vault Certification Affect in PAM Self-Hosted Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/itatp151w-vault-certification-affect/m-p/1422058#M88833</link>
    <description>&lt;P&gt;Hi Gil,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;There is no feedback about this subject but i changed it from SHA1 to SHA256.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;My question is if we can not change it, do we have any vulnerability on this system?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards.&lt;/P&gt;</description>
    <pubDate>Mon, 02 Jan 2023 06:52:00 GMT</pubDate>
    <dc:creator>CyberArkAlumni</dc:creator>
    <dc:date>2023-01-02T06:52:00Z</dc:date>
    <item>
      <title>ITATP151W Vault Certification Affect</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/itatp151w-vault-certification-affect/m-p/1422056#M88831</link>
      <description>&lt;P&gt;Dear All,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I just want to ask a question about Vault certification.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The issue is like below:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;ITATP151W Security warning - The Signature Hash Algorithm of the Vault certificate is SHA1. We recommend that you use at least Signature Hash Algorithm SHA2-256&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;What is the affect when we use SHA1 instead of SHA256 ? We know that vault use another encryption and decryption algorithm for account and records.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If we can not change SHA1 to SHA256, what is the vulnerability?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards.&lt;/P&gt;</description>
      <pubDate>Fri, 07 Oct 2022 11:03:03 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/itatp151w-vault-certification-affect/m-p/1422056#M88831</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2022-10-07T11:03:03Z</dc:date>
    </item>
    <item>
      <title>Re: ITATP151W Vault Certification Affect</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/itatp151w-vault-certification-affect/m-p/1422057#M88832</link>
      <description>&lt;P&gt;Hi @Sevki Sahin​&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;As it seems some time has passed since this question was raised. &lt;/P&gt;&lt;P&gt;Can you please update if you were able to find this information?&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Gil&lt;/P&gt;</description>
      <pubDate>Sun, 01 Jan 2023 14:58:31 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/itatp151w-vault-certification-affect/m-p/1422057#M88832</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2023-01-01T14:58:31Z</dc:date>
    </item>
    <item>
      <title>Re: ITATP151W Vault Certification Affect</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/itatp151w-vault-certification-affect/m-p/1422058#M88833</link>
      <description>&lt;P&gt;Hi Gil,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;There is no feedback about this subject but i changed it from SHA1 to SHA256.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;My question is if we can not change it, do we have any vulnerability on this system?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards.&lt;/P&gt;</description>
      <pubDate>Mon, 02 Jan 2023 06:52:00 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/itatp151w-vault-certification-affect/m-p/1422058#M88833</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2023-01-02T06:52:00Z</dc:date>
    </item>
    <item>
      <title>Re: ITATP151W Vault Certification Affect</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/itatp151w-vault-certification-affect/m-p/1422059#M88834</link>
      <description>&lt;P&gt;Hi @Sevki Sahin​&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We introduced on 11.5 version this Vault security alert when the Vault uses a certificate signed with SHA1 to encourage customers to use SHA2 (CyberArk is planning to migrate out of SHA1 in many areas, but we do not have clear timelines for all components yet). &lt;/P&gt;&lt;P&gt;Generally speaking, SHA1 consider less secure as it uses a 160-bit long key to encrypt data, while SHA256 uses a 256-bit long key to encrypt data(along with various &lt;A alt="https://en.wikipedia.org/wiki/SHA-2#Comparison_of_SHA_functions" href="https://en.wikipedia.org/wiki/SHA-2#Comparison_of_SHA_functions" target="_blank"&gt;security enhancements&lt;/A&gt;). So SHA1 is theoretically vulnerable to collision attacks and less recommended for encryption. &lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;In CyberArk, note that the added security of SHA2 is in the integrity data part, not in exposing data, as CyberArk doesn't use SHA1 for the vault encryption itself, but for the part of the Vault protocol we use SHA1 for MAC(message authentication code) to ensure that messages are not tampered with over the network (just like the MD5 signature is being used).&lt;/P&gt;&lt;P&gt;For that purpose, there is no problem using SHA1.&lt;/P&gt;&lt;P&gt;To protect the Vault database and data files that reside in the&amp;nbsp;Digital Vault,&amp;nbsp;CyberArk&amp;nbsp;employs AES-256 encryption with a unique encryption key for each object. Since decryption is done only by the client requesting access to the data, data encryption also protects the information from tampering. &lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If further details are required on this topic, I would advise you also to check the below documents and contact your cyberark representative/ success engineer regarding your environmental security considerations:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;"&lt;A alt="https://www.cyberark.com/resources/product-datasheets/the-cyberark-digital-vault-built-for-security" href="https://www.cyberark.com/resources/product-datasheets/the-cyberark-digital-vault-built-for-security" target="_blank"&gt;The CyberArk Digital Vault: Built for Security&lt;/A&gt;"&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;A alt="https://cyberark-customers.force.com/s/article/ITATP151W-Security-warning-The-Signature-Hash-Algorithm-of-the-Vault-certificate-is-SHA1-We-recommend-that-you-use-at-least-Signature-Hash-Algorithm-SHA2-256-with-this-Vault-s-configuration" href="https://cyberark-customers.force.com/s/article/ITATP151W-Security-warning-The-Signature-Hash-Algorithm-of-the-Vault-certificate-is-SHA1-We-recommend-that-you-use-at-least-Signature-Hash-Algorithm-SHA2-256-with-this-Vault-s-configuration" target="_blank"&gt;ITATP151W Security warning - The Signature Hash Algorithm of the Vault certificate is SHA1. We recommend that you use at least Signature Hash Algorithm SHA2-256 with this Vault's configuration.&lt;/A&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Gil&lt;/P&gt;</description>
      <pubDate>Wed, 04 Jan 2023 10:03:18 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/itatp151w-vault-certification-affect/m-p/1422059#M88834</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2023-01-04T10:03:18Z</dc:date>
    </item>
  </channel>
</rss>

