<?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: selfsigned vs CA-signed certificate in PAM Self-Hosted Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/selfsigned-vs-ca-signed-certificate/m-p/1410878#M85157</link>
    <description>&lt;P&gt;QQ:- Whatever CA signed certificate we install in vault should be installed in Component Servers too?&lt;/P&gt;</description>
    <pubDate>Fri, 20 Dec 2024 16:42:12 GMT</pubDate>
    <dc:creator>Sanzu</dc:creator>
    <dc:date>2024-12-20T16:42:12Z</dc:date>
    <item>
      <title>selfsigned vs CA-signed certificate</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/selfsigned-vs-ca-signed-certificate/m-p/1410876#M85155</link>
      <description>&lt;P&gt;this article explains how to replace the selfsigned certificate on the vault with a CA-signed cert: &lt;A alt="https://community.cyberark.com/s/article/00004635" href="https://community.cyberark.com/s/article/00004635" target="_blank"&gt;Article Detail&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;however, as we are not using TLS to connect to the vault (yet), I have the discussion with some collegues on the value of replacing the selfsigned certificate with a CA-signed certificate.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;What is the added value as long as we keep using CASOS instead of TLS connections with our components? (other than not getting the itatp044w warning when starting the vault)&lt;/LI&gt;&lt;LI&gt;if we use CA-signed cert and the validity expired...will the vault keep running/working?&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;the documentation from cyberark in this case is not explicit enough to draw conclusions. I hope the community can provide details on this.&lt;/P&gt;</description>
      <pubDate>Wed, 18 Dec 2024 10:15:36 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/selfsigned-vs-ca-signed-certificate/m-p/1410876#M85155</guid>
      <dc:creator>a.hoogendoorn919146</dc:creator>
      <dc:date>2024-12-18T10:15:36Z</dc:date>
    </item>
    <item>
      <title>Re: selfsigned vs CA-signed certificate</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/selfsigned-vs-ca-signed-certificate/m-p/1410877#M85156</link>
      <description>&lt;P&gt;@Arie Hoogendoorn​&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Other than Prevention of Warnings .. &lt;/P&gt;&lt;P&gt;&lt;B&gt;1) Trustworthiness:&lt;/B&gt; A CA-signed certificate establishes trust between the Vult  nd other sytems by ensuring the identity of the Vault is verified by a trusted authority. this can be useful if your organization security policies or auditors require the use of CA-signed certificates.&lt;/P&gt;&lt;P&gt;&lt;B&gt;2) Compliance:&lt;/B&gt; Many organizations have compliance requirements to use certificates issued by trusted authorities rather than self-signed ones, even if TLS is not actively being used.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I think The Vault will continue to run if the CA-signed certificate expires, but not sure 100% about that. Haven't tested .&lt;/P&gt;</description>
      <pubDate>Fri, 20 Dec 2024 16:04:32 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/selfsigned-vs-ca-signed-certificate/m-p/1410877#M85156</guid>
      <dc:creator>A.Weerasinghe346640</dc:creator>
      <dc:date>2024-12-20T16:04:32Z</dc:date>
    </item>
    <item>
      <title>Re: selfsigned vs CA-signed certificate</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/selfsigned-vs-ca-signed-certificate/m-p/1410878#M85157</link>
      <description>&lt;P&gt;QQ:- Whatever CA signed certificate we install in vault should be installed in Component Servers too?&lt;/P&gt;</description>
      <pubDate>Fri, 20 Dec 2024 16:42:12 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/selfsigned-vs-ca-signed-certificate/m-p/1410878#M85157</guid>
      <dc:creator>Sanzu</dc:creator>
      <dc:date>2024-12-20T16:42:12Z</dc:date>
    </item>
    <item>
      <title>Re: selfsigned vs CA-signed certificate</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/selfsigned-vs-ca-signed-certificate/m-p/1410879#M85158</link>
      <description>&lt;P&gt;Hi @Arie Hoogendoorn​&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;It seems that AsankaW provided an answer to your question. Could you kindly let us know if this solution helped?&lt;/P&gt;&lt;P&gt;If so, please mark the answer as 'Select as Best' to assist other community members.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you, Liad&lt;/P&gt;</description>
      <pubDate>Sun, 29 Dec 2024 12:28:32 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/selfsigned-vs-ca-signed-certificate/m-p/1410879#M85158</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2024-12-29T12:28:32Z</dc:date>
    </item>
    <item>
      <title>Re: selfsigned vs CA-signed certificate</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/selfsigned-vs-ca-signed-certificate/m-p/1410880#M85159</link>
      <description>&lt;P&gt;thanks @Asanka Weerasinghe​&amp;nbsp;,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;if talking about "&lt;B&gt;trustwothiness"&lt;/B&gt; I also expect that components will report untrusted/expired certificates. But as we are still using CASOS to communicate (and not TLS), I do not see the security added value to have an CA-signed certificate on the vault.....from that perspective it would only be a &lt;B&gt;compliance&lt;/B&gt; reason without security increase (and I hate compliance rules for security measures that do not add security &lt;span class="lia-unicode-emoji" title=":winking_face:"&gt;😉&lt;/span&gt; )&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;nevertheless, I now have the perfect opportunity to wait for my acceptance environment which has certificates expiring within a week and see what happens.&lt;/P&gt;</description>
      <pubDate>Mon, 06 Jan 2025 07:22:28 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/selfsigned-vs-ca-signed-certificate/m-p/1410880#M85159</guid>
      <dc:creator>a.hoogendoorn919146</dc:creator>
      <dc:date>2025-01-06T07:22:28Z</dc:date>
    </item>
    <item>
      <title>Re: selfsigned vs CA-signed certificate</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/selfsigned-vs-ca-signed-certificate/m-p/1410881#M85160</link>
      <description>&lt;P&gt;Finaly we got to actively check on the behaviour when the certificate expires.&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;PVWA keeps working&lt;/LI&gt;&lt;LI&gt;Vault keeps working (including restart)&lt;/LI&gt;&lt;LI&gt;CPM keeps working&lt;/LI&gt;&lt;LI&gt;&lt;B&gt;PAclient starts complaining about expired certificate and refuses tot logon&lt;/B&gt;&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;so based on above there is actually a requirement to have the certiciate not expired.&lt;/P&gt;</description>
      <pubDate>Mon, 03 Feb 2025 09:17:06 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/selfsigned-vs-ca-signed-certificate/m-p/1410881#M85160</guid>
      <dc:creator>a.hoogendoorn919146</dc:creator>
      <dc:date>2025-02-03T09:17:06Z</dc:date>
    </item>
    <item>
      <title>Re: selfsigned vs CA-signed certificate</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/selfsigned-vs-ca-signed-certificate/m-p/1410882#M85161</link>
      <description>&lt;P&gt;Even though TLS isn't currently used, replacing the self-signed certificate with a CA-signed one helps eliminate browser/security warnings and prepares the system for future secure configurations. We tested this ourselves—when the CA certificate expired, PAClient stopped working, even though Vault, PVWA, and CPM continued running. So yes, make sure your CA certificate is valid to avoid issues with PAClient functionality. &lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I hope it helps!&lt;/P&gt;</description>
      <pubDate>Fri, 30 May 2025 12:01:48 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/selfsigned-vs-ca-signed-certificate/m-p/1410882#M85161</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2025-05-30T12:01:48Z</dc:date>
    </item>
  </channel>
</rss>

