<?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: Credentials Service is Down in Secrets Management</title>
    <link>https://live.paloaltonetworks.com/t5/secrets-management/credentials-service-is-down/m-p/1303323#M134</link>
    <description>&lt;P&gt;Hi @sanjay sah​&amp;nbsp;,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;You're on the right thought process! We always want to think about the "what if" scenarios that are most likely. An overview of the caching utilized by the CCP is outlined here: https://docs.cyberark.com/credential-providers/latest/en/content/cp%20and%20ascp/configuring-caching.htm?tocpath=Administration%7CCredential%20Provider%20(CP)%7CCredential%20Provider%20configuration%7C_____3&lt;/P&gt;&lt;P&gt;You can manipulate the cache settings to meet your needs better given your potential outage scenario. &lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;What @Vinay Vasanth​&amp;nbsp; mentioned is exactly true as well. Putting multiple CCPs behind a load balancer will help with availability of the CCP service. If the vault is down, then the cache on each CCP will come into play. A properly set up DR Vault failover will help mitigate any potential password changes because the CPM will not be in effect during a failover scenario. &lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Ideally, the recommendation is to build in some redundancy to your Vault infrastructure since that seems to be your main point of concern. There shouldn't be much to worry about if you have a healthy DR vault and a CPM that's configured to not update any secrets during a failover scenario. This way the cache on the CCP will be valid until you can bring the primary vault back online. &lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Just retrieving the credential from the CCP will give you the cached password. Out of the box configuration doesn't fetch the secret in real time from the vault unless it's the first retrieval. Every time after the first is pulled from the cache. &lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Hope this helps. &lt;/P&gt;</description>
    <pubDate>Mon, 16 Dec 2024 20:50:17 GMT</pubDate>
    <dc:creator>CyberArkAlumni</dc:creator>
    <dc:date>2024-12-16T20:50:17Z</dc:date>
    <item>
      <title>Credentials Service is Down</title>
      <link>https://live.paloaltonetworks.com/t5/secrets-management/credentials-service-is-down/m-p/1303321#M132</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;We have various numbers of automation ongoing using CCP to different applications Therefore, something is haunting my mind. I am thinking What If Vault went down and due to no communication of CCP and Vault, CCP service will go off? If CCP services stop working, then automation will break. &lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;What would you suggest being safe prior to happen anything such kind of issue? Also, is there any command to get local cache password inside CCP?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I would appreciate if I got any detailed and great in-depth answers. &lt;/P&gt;</description>
      <pubDate>Mon, 16 Dec 2024 19:22:39 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/secrets-management/credentials-service-is-down/m-p/1303321#M132</guid>
      <dc:creator>Sanzu</dc:creator>
      <dc:date>2024-12-16T19:22:39Z</dc:date>
    </item>
    <item>
      <title>Re: Credentials Service is Down</title>
      <link>https://live.paloaltonetworks.com/t5/secrets-management/credentials-service-is-down/m-p/1303322#M133</link>
      <description>&lt;P&gt;@sanjay sah​&amp;nbsp; There will always be a what if situation. What if all the vault fails. In my opinion having multiple CCP behind a load balancer is the solution with Vault HA/DR or some sort of high availability to the vault.&lt;/P&gt;&lt;P&gt;I would not trust the cache on the CCP - what if the CPM changes the password of the account that was supposed to be used by the automation.&lt;/P&gt;</description>
      <pubDate>Mon, 16 Dec 2024 20:09:14 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/secrets-management/credentials-service-is-down/m-p/1303322#M133</guid>
      <dc:creator>V.Vasanth982517</dc:creator>
      <dc:date>2024-12-16T20:09:14Z</dc:date>
    </item>
    <item>
      <title>Re: Credentials Service is Down</title>
      <link>https://live.paloaltonetworks.com/t5/secrets-management/credentials-service-is-down/m-p/1303323#M134</link>
      <description>&lt;P&gt;Hi @sanjay sah​&amp;nbsp;,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;You're on the right thought process! We always want to think about the "what if" scenarios that are most likely. An overview of the caching utilized by the CCP is outlined here: https://docs.cyberark.com/credential-providers/latest/en/content/cp%20and%20ascp/configuring-caching.htm?tocpath=Administration%7CCredential%20Provider%20(CP)%7CCredential%20Provider%20configuration%7C_____3&lt;/P&gt;&lt;P&gt;You can manipulate the cache settings to meet your needs better given your potential outage scenario. &lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;What @Vinay Vasanth​&amp;nbsp; mentioned is exactly true as well. Putting multiple CCPs behind a load balancer will help with availability of the CCP service. If the vault is down, then the cache on each CCP will come into play. A properly set up DR Vault failover will help mitigate any potential password changes because the CPM will not be in effect during a failover scenario. &lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Ideally, the recommendation is to build in some redundancy to your Vault infrastructure since that seems to be your main point of concern. There shouldn't be much to worry about if you have a healthy DR vault and a CPM that's configured to not update any secrets during a failover scenario. This way the cache on the CCP will be valid until you can bring the primary vault back online. &lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Just retrieving the credential from the CCP will give you the cached password. Out of the box configuration doesn't fetch the secret in real time from the vault unless it's the first retrieval. Every time after the first is pulled from the cache. &lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Hope this helps. &lt;/P&gt;</description>
      <pubDate>Mon, 16 Dec 2024 20:50:17 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/secrets-management/credentials-service-is-down/m-p/1303323#M134</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2024-12-16T20:50:17Z</dc:date>
    </item>
    <item>
      <title>Re: Credentials Service is Down</title>
      <link>https://live.paloaltonetworks.com/t5/secrets-management/credentials-service-is-down/m-p/1303324#M135</link>
      <description>&lt;P&gt;Yes that correct but if CPM changed the password and not updated in CCP won't hurt in most of the cases because we use local cache and depen on that password in  most of the cases. BUT biggest fear is what if both vaults get down and you have no failover thing going and you are going bald in that scenes due to anger and on top of that your automation team making feel like you are only the reason of everything going on. &lt;span class="lia-unicode-emoji" title=":grinning_face:"&gt;😀&lt;/span&gt;  &lt;/P&gt;</description>
      <pubDate>Mon, 16 Dec 2024 22:09:08 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/secrets-management/credentials-service-is-down/m-p/1303324#M135</guid>
      <dc:creator>Sanzu</dc:creator>
      <dc:date>2024-12-16T22:09:08Z</dc:date>
    </item>
    <item>
      <title>Re: Credentials Service is Down</title>
      <link>https://live.paloaltonetworks.com/t5/secrets-management/credentials-service-is-down/m-p/1303325#M136</link>
      <description>&lt;P&gt;I am aware about those. My concern is -- think both  Vaults (i.e. primary and DR down) and no chance of any failover scenarios. What would you think in that case? because you are relying on CCP to automate very important stuff and you come to know that CCP service is down too.&lt;/P&gt;</description>
      <pubDate>Mon, 16 Dec 2024 22:10:53 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/secrets-management/credentials-service-is-down/m-p/1303325#M136</guid>
      <dc:creator>Sanzu</dc:creator>
      <dc:date>2024-12-16T22:10:53Z</dc:date>
    </item>
    <item>
      <title>Re: Credentials Service is Down</title>
      <link>https://live.paloaltonetworks.com/t5/secrets-management/credentials-service-is-down/m-p/1303326#M137</link>
      <description>&lt;P&gt;In that case I'd think you have bigger problems than the CCP &lt;span class="lia-unicode-emoji" title=":grinning_face:"&gt;😀&lt;/span&gt; . If both Primary and DR vaults are anticipated to be down and that's a likely scenario you wish to solve then you need a new vault HA/Redundancy plan. A single DR vault might not be enough. You may also need to move to HA Vault pairs in addition to multiple DR vaults. All of this comes with additional operational overhead but you gain more fault tolerance with every step. The only thing I can't answer is what your org is willing to spend in order to achieve a given reliability number. If you say you want 4 9's of reliability then we can help you build that functionality. Just know that it comes with a cost, both software license and operationally. &lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;How concerned are you with both vaults being down? It sounds like your automation is very important so having redundancy at the CCP, networking, and vault level is a good starting point to build the robust environment you need. &lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Happy to discuss more!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;DK&lt;/P&gt;</description>
      <pubDate>Mon, 16 Dec 2024 22:24:55 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/secrets-management/credentials-service-is-down/m-p/1303326#M137</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2024-12-16T22:24:55Z</dc:date>
    </item>
    <item>
      <title>Re: Credentials Service is Down</title>
      <link>https://live.paloaltonetworks.com/t5/secrets-management/credentials-service-is-down/m-p/1303327#M138</link>
      <description>&lt;P&gt;Hi @Darren Khan​&amp;nbsp;We are really stable, and we have more 2 DR and everything works fine. I am just wondering WHAT IF because I had seen in some environment previously than my current job. No failover scenario. Just all network outage and no functionalities of Vaults. Any way that was not just related to Cyberark vaults network. Whole company had issue. Therefore, thinking that bad times, I am wondering if there are any safeguard solutions if same/similar situations happen in future. &lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Let's consider whole company network is not down. Just there is no failover and no vaults working. Hence, all components and AAM service are down. What would you do in this case only Cyberark resources (just vaults) networks are down? What would you do if you were there, and you don't want to stop automation of password retrieval from local cache using CCP? Because concern is CCP service also gets stopped&lt;/P&gt;</description>
      <pubDate>Mon, 16 Dec 2024 22:32:17 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/secrets-management/credentials-service-is-down/m-p/1303327#M138</guid>
      <dc:creator>Sanzu</dc:creator>
      <dc:date>2024-12-16T22:32:17Z</dc:date>
    </item>
    <item>
      <title>Re: Credentials Service is Down</title>
      <link>https://live.paloaltonetworks.com/t5/secrets-management/credentials-service-is-down/m-p/1303328#M139</link>
      <description>&lt;P&gt;It's a hard situation to give an answer. The premise is that "all safeguards and all CyberArk components are down". Well CyberArk is down then, your automation will fail if it's reliant on CyberArk components. I only see two ways forward:&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;Make the CyberArk components more robust so that the likelihood of the entire CyberArk environment being down is remote. &lt;/LI&gt;&lt;LI&gt;Find a solution outside of CyberArk. &lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I can give you more recommendations from the CyberArk perspective but it will all fall under the presumption that "All CyberArk components are down". &lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;DK&lt;/P&gt;</description>
      <pubDate>Tue, 17 Dec 2024 16:45:16 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/secrets-management/credentials-service-is-down/m-p/1303328#M139</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2024-12-17T16:45:16Z</dc:date>
    </item>
    <item>
      <title>Re: Credentials Service is Down</title>
      <link>https://live.paloaltonetworks.com/t5/secrets-management/credentials-service-is-down/m-p/1303329#M140</link>
      <description>&lt;P&gt;Thanks for your response&lt;/P&gt;</description>
      <pubDate>Tue, 17 Dec 2024 18:31:43 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/secrets-management/credentials-service-is-down/m-p/1303329#M140</guid>
      <dc:creator>Sanzu</dc:creator>
      <dc:date>2024-12-17T18:31:43Z</dc:date>
    </item>
  </channel>
</rss>

