<?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: Central Credential Provider Vs Credential Provider in Secrets Management</title>
    <link>https://live.paloaltonetworks.com/t5/secrets-management/central-credential-provider-vs-credential-provider/m-p/1303408#M149</link>
    <description>&lt;P&gt;Hey @sanjay sah​&amp;nbsp;,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Let me see if I understand the constraints of the situation. &lt;/P&gt;&lt;OL&gt;&lt;LI&gt;The CP service is down&lt;/LI&gt;&lt;LI&gt;The cyberark vault is down&lt;/LI&gt;&lt;LI&gt;The application still needs a password&lt;/LI&gt;&lt;LI&gt;The CP Cache is stored as a file (My assumption because the default is in memory so if the process is down then the cache is gone)&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Do I have it right? &lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If so, that's a tricky situation. What would you want to happen in this scenario? What would you design? &lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Darren&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Fri, 10 Jan 2025 20:53:51 GMT</pubDate>
    <dc:creator>CyberArkAlumni</dc:creator>
    <dc:date>2025-01-10T20:53:51Z</dc:date>
    <item>
      <title>Central Credential Provider Vs Credential Provider</title>
      <link>https://live.paloaltonetworks.com/t5/secrets-management/central-credential-provider-vs-credential-provider/m-p/1303400#M141</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I know CCP works 443 and CP on port 1858 and both have local cache mechanism. For Whatever CP can be utilized, CCP can help too only having difference that CP is agent based.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Therefore, my question is -- What major thing/use cases gives different identity and importance to each product (i.e. CCP vs CP?&lt;/P&gt;</description>
      <pubDate>Tue, 17 Dec 2024 18:42:34 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/secrets-management/central-credential-provider-vs-credential-provider/m-p/1303400#M141</guid>
      <dc:creator>Sanzu</dc:creator>
      <dc:date>2024-12-17T18:42:34Z</dc:date>
    </item>
    <item>
      <title>Re: Central Credential Provider Vs Credential Provider</title>
      <link>https://live.paloaltonetworks.com/t5/secrets-management/central-credential-provider-vs-credential-provider/m-p/1303401#M142</link>
      <description>&lt;P&gt;One of the use cases: &lt;/P&gt;&lt;P&gt;CP: If it is a critical application and the application needs to fetch password from Vault very frequently (like multiple times per sec/minutes), cannot afford any downtime, then better to have the agent speak to Vault directly and avoid any delays. Also will have less dependency on another server(CCP).&lt;/P&gt;&lt;P&gt;CCP: A central server which has the required agent and multiple applications fetch password from this CCP server.&lt;/P&gt;</description>
      <pubDate>Tue, 17 Dec 2024 21:51:53 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/secrets-management/central-credential-provider-vs-credential-provider/m-p/1303401#M142</guid>
      <dc:creator>A.Karkera912639</dc:creator>
      <dc:date>2024-12-17T21:51:53Z</dc:date>
    </item>
    <item>
      <title>Re: Central Credential Provider Vs Credential Provider</title>
      <link>https://live.paloaltonetworks.com/t5/secrets-management/central-credential-provider-vs-credential-provider/m-p/1303402#M143</link>
      <description>&lt;P&gt;As I stated above, I am aware about these. BUT once vault (In case of no any failover) goes down CP service also goes down. Then password retrieval breaks. How would you deal in this case except fetching password from local cache? &lt;/P&gt;</description>
      <pubDate>Tue, 17 Dec 2024 21:54:43 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/secrets-management/central-credential-provider-vs-credential-provider/m-p/1303402#M143</guid>
      <dc:creator>Sanzu</dc:creator>
      <dc:date>2024-12-17T21:54:43Z</dc:date>
    </item>
    <item>
      <title>Re: Central Credential Provider Vs Credential Provider</title>
      <link>https://live.paloaltonetworks.com/t5/secrets-management/central-credential-provider-vs-credential-provider/m-p/1303403#M144</link>
      <description>&lt;P&gt;Hi @sanjay sah​&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;There a nice documentation from CyberArk for this. Please refer to the following link. Hope it helps !&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;https://docs.cyberark.com/credential-providers/latest/en/content/ccp/the-cyberark-application-identity-management-solution.htm?tocpath=Get%20Started%7C_____1#:~:text=For%20more%20information%2C%20refer%20to,on%20each%20end%20user%20machine.&lt;/P&gt;</description>
      <pubDate>Wed, 18 Dec 2024 00:38:44 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/secrets-management/central-credential-provider-vs-credential-provider/m-p/1303403#M144</guid>
      <dc:creator>M.Vora780263</dc:creator>
      <dc:date>2024-12-18T00:38:44Z</dc:date>
    </item>
    <item>
      <title>Re: Central Credential Provider Vs Credential Provider</title>
      <link>https://live.paloaltonetworks.com/t5/secrets-management/central-credential-provider-vs-credential-provider/m-p/1303404#M145</link>
      <description>&lt;P&gt;Thank You @Malhar Vora​&amp;nbsp; I was aware about those description. My main motive of this post is -- For an example: - CCP or CP password retrieval gets stopped automatically whenever Vault gets stopped (think that there is no any failover scenario) because CCP and CP service gets stopped. Now, you only have way to retrieve the password from local cache which will take time during some incident and automation will be in hectic situations for some time. What would you think in this case when you are in nonplussed situation except you have idea to pull password from local cache? &lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Therefore, I want to know what other great features make quite make separate identity between CCP and CP because both CCP and CP have local cache mechanism. so, are there any great features which makes some greatest difference between CCP and CP?&lt;/P&gt;</description>
      <pubDate>Wed, 18 Dec 2024 16:32:14 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/secrets-management/central-credential-provider-vs-credential-provider/m-p/1303404#M145</guid>
      <dc:creator>Sanzu</dc:creator>
      <dc:date>2024-12-18T16:32:14Z</dc:date>
    </item>
    <item>
      <title>Re: Central Credential Provider Vs Credential Provider</title>
      <link>https://live.paloaltonetworks.com/t5/secrets-management/central-credential-provider-vs-credential-provider/m-p/1303405#M146</link>
      <description>&lt;P&gt;I'd just like to point out here that you wouldn't really explicitly treat them as separate entities. A CCP functions as an extension to the CP over a web server to make those calls available over the network. A CCP still requires a CP underneath it to work. It's the CP that's still making those calls. It's more to do with the use case for your specific application. For example, let's say you have a Windows server which you have full control over. You may stick with a CP as you can perform the installation on the server and it will fulfil your use case for critical applications on that server. But now let's assume you're trying to use a CP to run authenticated scans with Qualys. A Qualys scanner is an appliance and you cannot install a CP on the appliance. In this scenario you have no option but to have the CP installed on another server, install the CCP on top of it to make those retrieved passwords available over the network, and then have Qualys pull the credentials through REST API calls using the CCP web service.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;That said, as mentioned in the documentation, for mission critical applications, you want the CP on your application server as it provides the secure cache, low latency, and I think stronger authentication mechanisms. The CP allows local retrieval. The CCP can then make the retrieval accessible remotely across the network.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;You can check point 1 in the Implementation section of this really nice CyberArk KB on securing applications using CP/CCP: https://community.cyberark.com/s/article/Securing-Homegrown-Static-OS-Applications-with-CyberArk-Secrets-Manager&lt;/P&gt;</description>
      <pubDate>Wed, 18 Dec 2024 17:54:55 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/secrets-management/central-credential-provider-vs-credential-provider/m-p/1303405#M146</guid>
      <dc:creator>Tanishq</dc:creator>
      <dc:date>2024-12-18T17:54:55Z</dc:date>
    </item>
    <item>
      <title>Re: Central Credential Provider Vs Credential Provider</title>
      <link>https://live.paloaltonetworks.com/t5/secrets-management/central-credential-provider-vs-credential-provider/m-p/1303406#M147</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 can start with the more prevalent defining characteristic. The CCP is called using REST and the CP is a local agent that must be executed. @Tanishq Pandey​&amp;nbsp; is correct in saying they aren't really two distinct solutions. They are both CPs where one just has a website on top of it. Everything else is identical since it's just a CP. &lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Hope this helps!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Darren&lt;/P&gt;</description>
      <pubDate>Mon, 06 Jan 2025 20:28:50 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/secrets-management/central-credential-provider-vs-credential-provider/m-p/1303406#M147</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2025-01-06T20:28:50Z</dc:date>
    </item>
    <item>
      <title>Re: Central Credential Provider Vs Credential Provider</title>
      <link>https://live.paloaltonetworks.com/t5/secrets-management/central-credential-provider-vs-credential-provider/m-p/1303407#M148</link>
      <description>&lt;P&gt;Yes, I am aware about that I would be quite happy if CP had something similar that Password Retrieval is ongoing/continued fetching out from local cache in the case/event of CP service failure or CA down. It would be really nicer one. Instead of going to retrieve the password from local cache in the emergency. I don't mean local cache should be removed, I meant in addition of local cache, if CP had capability to fetch password in really hectic situation, then it would be real nice. I hope I made sense&lt;/P&gt;</description>
      <pubDate>Tue, 07 Jan 2025 18:39:35 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/secrets-management/central-credential-provider-vs-credential-provider/m-p/1303407#M148</guid>
      <dc:creator>Sanzu</dc:creator>
      <dc:date>2025-01-07T18:39:35Z</dc:date>
    </item>
    <item>
      <title>Re: Central Credential Provider Vs Credential Provider</title>
      <link>https://live.paloaltonetworks.com/t5/secrets-management/central-credential-provider-vs-credential-provider/m-p/1303408#M149</link>
      <description>&lt;P&gt;Hey @sanjay sah​&amp;nbsp;,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Let me see if I understand the constraints of the situation. &lt;/P&gt;&lt;OL&gt;&lt;LI&gt;The CP service is down&lt;/LI&gt;&lt;LI&gt;The cyberark vault is down&lt;/LI&gt;&lt;LI&gt;The application still needs a password&lt;/LI&gt;&lt;LI&gt;The CP Cache is stored as a file (My assumption because the default is in memory so if the process is down then the cache is gone)&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Do I have it right? &lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If so, that's a tricky situation. What would you want to happen in this scenario? What would you design? &lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Darren&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 10 Jan 2025 20:53:51 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/secrets-management/central-credential-provider-vs-credential-provider/m-p/1303408#M149</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2025-01-10T20:53:51Z</dc:date>
    </item>
    <item>
      <title>Re: Central Credential Provider Vs Credential Provider</title>
      <link>https://live.paloaltonetworks.com/t5/secrets-management/central-credential-provider-vs-credential-provider/m-p/1303409#M150</link>
      <description>&lt;P&gt;Hi Darren, &lt;/P&gt;&lt;P&gt;Thats correct. I think you got me. &lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I would think to design as like mentioned below:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Let's assume the real bad scenario in the first place: We have situation where vault is down, and CCP/CP Service is down. Now, in this scenario we are in difficult situation where automatic password retrieval has been stopped, and we are thinking to retrieve the password from local cache, but it will take time, and we are in non-plussed situation. Therefore, I would think like below which is mentioned below.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Reasonable Design if possible: I would say CCP/CP service should be mostly useful to retrieve the password from vault and store somewhere inside CCP/CP same/similar as/to local cache. Whenever CCP/CP service is down, or Vault is down or BOTH are down, then Password retrieval should not stop. so basically, password retrieval should process from CCP/CP and should be ongoing to the users' application or servers where it has been worked to be fetched. This is the way I would think. I don't know if this is smart way of thinking. &lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I hope I made sense.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 10 Jan 2025 21:08:03 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/secrets-management/central-credential-provider-vs-credential-provider/m-p/1303409#M150</guid>
      <dc:creator>Sanzu</dc:creator>
      <dc:date>2025-01-10T21:08:03Z</dc:date>
    </item>
    <item>
      <title>Re: Central Credential Provider Vs Credential Provider</title>
      <link>https://live.paloaltonetworks.com/t5/secrets-management/central-credential-provider-vs-credential-provider/m-p/1303410#M151</link>
      <description>&lt;P&gt;Are you saying to store it in a file?&lt;/P&gt;</description>
      <pubDate>Fri, 10 Jan 2025 21:32:27 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/secrets-management/central-credential-provider-vs-credential-provider/m-p/1303410#M151</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2025-01-10T21:32:27Z</dc:date>
    </item>
    <item>
      <title>Re: Central Credential Provider Vs Credential Provider</title>
      <link>https://live.paloaltonetworks.com/t5/secrets-management/central-credential-provider-vs-credential-provider/m-p/1303411#M152</link>
      <description>&lt;P&gt;Nope. Something same as local cache or if local cache can be enhanced then its also fine. or some type of static database with high security. Definitely I would not think file &lt;span class="lia-unicode-emoji" title=":grinning_face:"&gt;😀&lt;/span&gt; &lt;span class="lia-unicode-emoji" title=":grinning_face:"&gt;😀&lt;/span&gt; &lt;span class="lia-unicode-emoji" title=":grinning_face:"&gt;😀&lt;/span&gt; &lt;/P&gt;</description>
      <pubDate>Fri, 10 Jan 2025 21:38:13 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/secrets-management/central-credential-provider-vs-credential-provider/m-p/1303411#M152</guid>
      <dc:creator>Sanzu</dc:creator>
      <dc:date>2025-01-10T21:38:13Z</dc:date>
    </item>
    <item>
      <title>Re: Central Credential Provider Vs Credential Provider</title>
      <link>https://live.paloaltonetworks.com/t5/secrets-management/central-credential-provider-vs-credential-provider/m-p/1303412#M153</link>
      <description>&lt;P&gt;Well it can't be in the cache because the cache is gone if the process is not running. Where else could it be placed?&lt;/P&gt;</description>
      <pubDate>Fri, 10 Jan 2025 21:44:24 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/secrets-management/central-credential-provider-vs-credential-provider/m-p/1303412#M153</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2025-01-10T21:44:24Z</dc:date>
    </item>
    <item>
      <title>Re: Central Credential Provider Vs Credential Provider</title>
      <link>https://live.paloaltonetworks.com/t5/secrets-management/central-credential-provider-vs-credential-provider/m-p/1303413#M154</link>
      <description>&lt;P&gt;You question is million dollars' worth. &lt;span class="lia-unicode-emoji" title=":grinning_face:"&gt;😀&lt;/span&gt; As I am not developer. I would say/ask you if it is possible to have tiny database created with high security whenever we install CCP/CP in our server and that tiny database would be helpful in this scenario? Can CCP/CP be enhanced in this way?&lt;/P&gt;</description>
      <pubDate>Fri, 10 Jan 2025 21:48:22 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/secrets-management/central-credential-provider-vs-credential-provider/m-p/1303413#M154</guid>
      <dc:creator>Sanzu</dc:creator>
      <dc:date>2025-01-10T21:48:22Z</dc:date>
    </item>
    <item>
      <title>Re: Central Credential Provider Vs Credential Provider</title>
      <link>https://live.paloaltonetworks.com/t5/secrets-management/central-credential-provider-vs-credential-provider/m-p/1303414#M155</link>
      <description>&lt;P&gt;A tiny database could work. We both agree that it shouldn't be written to the file system. That leaves storing across the network (but we already don't want this because the network is down in this scenario) and in memory. Storing in memory will work but needs a process to actively store something in memory so that it isn't just floating in some random memory address. We can wrap the memory space with some encryption but then need an active process to perform decrypt and encrypt functions when needing a secret. That sound good so far?&lt;/P&gt;</description>
      <pubDate>Wed, 15 Jan 2025 21:43:57 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/secrets-management/central-credential-provider-vs-credential-provider/m-p/1303414#M155</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2025-01-15T21:43:57Z</dc:date>
    </item>
    <item>
      <title>Re: Central Credential Provider Vs Credential Provider</title>
      <link>https://live.paloaltonetworks.com/t5/secrets-management/central-credential-provider-vs-credential-provider/m-p/1303415#M156</link>
      <description>&lt;P&gt;Yes sounds good, but able to decrypt the password whenever service is down as well as password retrieval should be ongoing even though CCP/CP service is down&lt;/P&gt;</description>
      <pubDate>Wed, 15 Jan 2025 21:49:13 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/secrets-management/central-credential-provider-vs-credential-provider/m-p/1303415#M156</guid>
      <dc:creator>Sanzu</dc:creator>
      <dc:date>2025-01-15T21:49:13Z</dc:date>
    </item>
    <item>
      <title>Re: Central Credential Provider Vs Credential Provider</title>
      <link>https://live.paloaltonetworks.com/t5/secrets-management/central-credential-provider-vs-credential-provider/m-p/1303416#M157</link>
      <description>&lt;P&gt;In order to do that then you'd need to have the decryption material available to the new process. Now we are back to our original issue. Do you store that material on the file system, memory, or over the network. &lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The thing we are ultimately designing, if we continue down this route, is the CP/CCP. The CP actually has a mode to store the decryption material in the vault so that it's never touching the machines memory or file system. &lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Having the cache (which is basically a tiny database in memory) available to other processes is a security risk. We lock down the cache to only the CP process. This inherently means that the CP process needs to be running. We should never have sensitive material saved to memory without some process protecting that memory space. &lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The scenario that you are putting forth is one where the problem isn't with the CP process. It's the fact that you can't trust the machine to keep the CP process running.  We can't solve that problem at the application layer. It'll need to be at the OS layer or higher. &lt;/P&gt;</description>
      <pubDate>Wed, 15 Jan 2025 22:05:45 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/secrets-management/central-credential-provider-vs-credential-provider/m-p/1303416#M157</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2025-01-15T22:05:45Z</dc:date>
    </item>
    <item>
      <title>Re: Central Credential Provider Vs Credential Provider</title>
      <link>https://live.paloaltonetworks.com/t5/secrets-management/central-credential-provider-vs-credential-provider/m-p/1303417#M158</link>
      <description>&lt;P&gt;You understood me very well. It's not like that I am only doubting on OS which can only do service interruptions, but other things can also do service interruptions, right? so something similar like I mentioned should be thought, right? &lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;As you are explaining that CP local cache is dependent on service running and indeed this is what current design is. Again, users will be in trouble in service goes down and automation breaks. So, CP helps in critical apps to make it up all time but we can face issue due to service disruption. Therefore, I would think to go in robust manner. I am sorry. I am not developer and no any development experience. otherwise, I would suggest you some roadmap too.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I completely understand as per current design. No filesystem or memory has been touched which is quite good. Don't know I am also thinking how it can be designed where there is 0% interruption/disruption/blockage. Believe me this solution will be very demanding and helpful if we can figure out &lt;span class="lia-unicode-emoji" title=":grinning_face:"&gt;😀&lt;/span&gt; &lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I will let you know if I can think very different than what we are discussing.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;But I can say you that whoever develop vault, pvwa and CCP. If these three engineers can see my rubbish idea or whatever I am talking rubbish about. Then, they will definitely come up with very novice and innovative idea. I bet on this. &lt;/P&gt;</description>
      <pubDate>Wed, 15 Jan 2025 22:11:12 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/secrets-management/central-credential-provider-vs-credential-provider/m-p/1303417#M158</guid>
      <dc:creator>Sanzu</dc:creator>
      <dc:date>2025-01-15T22:11:12Z</dc:date>
    </item>
  </channel>
</rss>

