<?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: Securing certificates used in CCP in Secrets Management</title>
    <link>https://live.paloaltonetworks.com/t5/secrets-management/securing-certificates-used-in-ccp/m-p/1360116#M1039</link>
    <description>&lt;P&gt;Thanks @Pete Maan​&amp;nbsp;for the comments. certificate auth is configured,as mentioned in the original problem description, the weak link is now shifted from hardcoded password to certificate password (assuming it is hardcoded). If the certificate file and password are stolen, the attacker will be able to transparently retrieve the credentials and it becomes hard to detect. Applying ACL on the certificate and restricting the permissions can be considered.  CP offers better security since it is agent based, with CCP there are certain limitations as it is a webservice.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Combination of certificate, host, user is a good option but with servers behind load balancer introduces further challenges.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;ARR is not supported when using client certificate serial number authentication&lt;/LI&gt;&lt;LI&gt;OS user validation on Linux is still open.&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt; Any thoughts around protecting the certificates in this case?&lt;/P&gt;</description>
    <pubDate>Thu, 15 Aug 2019 10:08:48 GMT</pubDate>
    <dc:creator>mband</dc:creator>
    <dc:date>2019-08-15T10:08:48Z</dc:date>
    <item>
      <title>Securing certificates used in CCP</title>
      <link>https://live.paloaltonetworks.com/t5/secrets-management/securing-certificates-used-in-ccp/m-p/1360114#M1037</link>
      <description>&lt;P&gt;Dear Cyberarkers&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Opening this thread for discussion&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;AIM CCP is a good step to remove hard coded passwords from applications, however the  credential used to authenticating to the CCP becomes the weak link. Of all available/supported options certificate based is most secure. The question now comes down to how to secure the certificate file/password and enable monitoring to make sure there are no copies of private keys. &lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I am aware of applying more restrictions of IP/hostname, but this does not solve the certificate password issue. Moreover, specially when the servers are behind load balancer there are limitations in using combination of certificate and IP/hostname .&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Any ideas / best practices/ recommendations on this topic?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 14 Aug 2019 09:18:50 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/secrets-management/securing-certificates-used-in-ccp/m-p/1360114#M1037</guid>
      <dc:creator>mband</dc:creator>
      <dc:date>2019-08-14T09:18:50Z</dc:date>
    </item>
    <item>
      <title>Re: Securing certificates used in CCP</title>
      <link>https://live.paloaltonetworks.com/t5/secrets-management/securing-certificates-used-in-ccp/m-p/1360115#M1038</link>
      <description>&lt;P&gt;Considerations for Client Certificate Authentication are documented here: https://docs.cyberark.com/Product-Doc/OnlineHelp/AAM-CP/Latest/en/Content/CP%20and%20ASCP/Application-Authentication-Methods-general.htm#Clientcertificatesauthentication&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The points listed in the above link which are pertinent to your question:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;The certificate must be trusted by IIS.&lt;/LI&gt;&lt;LI&gt;Ensure that no duplicate certificates are issued.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Additional considerations for Load Balancing CCP are here: &lt;/P&gt;&lt;P&gt;&lt;A alt="https://docs.cyberark.com/Product-Doc/OnlineHelp/AAM-CP/Latest/en/Content/CCP/Load-Balancing-the-Central-Credential-Provider.htm" href="https://docs.cyberark.com/Product-Doc/OnlineHelp/AAM-CP/Latest/en/Content/CCP/Load-Balancing-the-Central-Credential-Provider.htm" target="_blank"&gt;https://docs.cyberark.com/Product-Doc/OnlineHelp/AAM-CP/Latest/en/Content/CCP/Load-Balancing-the-Central-Credential-Provider.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;As long as SSL is not offloaded at the load balancer, certificate auth is possible.&lt;/P&gt;</description>
      <pubDate>Wed, 14 Aug 2019 12:19:39 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/secrets-management/securing-certificates-used-in-ccp/m-p/1360115#M1038</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2019-08-14T12:19:39Z</dc:date>
    </item>
    <item>
      <title>Re: Securing certificates used in CCP</title>
      <link>https://live.paloaltonetworks.com/t5/secrets-management/securing-certificates-used-in-ccp/m-p/1360116#M1039</link>
      <description>&lt;P&gt;Thanks @Pete Maan​&amp;nbsp;for the comments. certificate auth is configured,as mentioned in the original problem description, the weak link is now shifted from hardcoded password to certificate password (assuming it is hardcoded). If the certificate file and password are stolen, the attacker will be able to transparently retrieve the credentials and it becomes hard to detect. Applying ACL on the certificate and restricting the permissions can be considered.  CP offers better security since it is agent based, with CCP there are certain limitations as it is a webservice.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Combination of certificate, host, user is a good option but with servers behind load balancer introduces further challenges.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;ARR is not supported when using client certificate serial number authentication&lt;/LI&gt;&lt;LI&gt;OS user validation on Linux is still open.&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt; Any thoughts around protecting the certificates in this case?&lt;/P&gt;</description>
      <pubDate>Thu, 15 Aug 2019 10:08:48 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/secrets-management/securing-certificates-used-in-ccp/m-p/1360116#M1039</guid>
      <dc:creator>mband</dc:creator>
      <dc:date>2019-08-15T10:08:48Z</dc:date>
    </item>
    <item>
      <title>Re: Securing certificates used in CCP</title>
      <link>https://live.paloaltonetworks.com/t5/secrets-management/securing-certificates-used-in-ccp/m-p/1360117#M1040</link>
      <description>&lt;P&gt;@Joe Garcia​&amp;nbsp;do you have any recommendations?&lt;/P&gt;</description>
      <pubDate>Thu, 05 Aug 2021 10:28:21 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/secrets-management/securing-certificates-used-in-ccp/m-p/1360117#M1040</guid>
      <dc:creator>mband</dc:creator>
      <dc:date>2021-08-05T10:28:21Z</dc:date>
    </item>
    <item>
      <title>Re: Securing certificates used in CCP</title>
      <link>https://live.paloaltonetworks.com/t5/secrets-management/securing-certificates-used-in-ccp/m-p/1360118#M1041</link>
      <description>&lt;P&gt;@Mohan Bandha​&amp;nbsp;: Assuming you would have been able to configure CCP behind the load balancers. If you could provide your inputs &amp;amp; suggests what should be the best practice (in terms of Authentication) if the CCP servers are behind the LB ? &lt;/P&gt;</description>
      <pubDate>Sat, 15 Jan 2022 11:07:29 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/secrets-management/securing-certificates-used-in-ccp/m-p/1360118#M1041</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2022-01-15T11:07:29Z</dc:date>
    </item>
  </channel>
</rss>

