<?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 CCP and password rotation in Secrets Management</title>
    <link>https://live.paloaltonetworks.com/t5/secrets-management/ccp-and-password-rotation/m-p/1392504#M1713</link>
    <description>&lt;P&gt;Is there a common way, when rotating the password for an account, that the surounding system which uses this account get's the new credential? I know that these surounding systems (we call them consumers) should call the REST API from CCP. But there are an overwhelming number of systems/appliances that can not initiate an API call. Often these are static fields you can fill with username and password.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Let me make an example. A company has a policy which states that all machine-to-machine (M2M) accounts need to be rotated on a regular basis. We have many devices in our company that use service accounts which are set on the consumer during bootstrap with a playbook over Ansible Automation Platform (AAP). The Platform policy is set to rotate password for these accounts after 5 days. Our CPM plugins are built that credentials are rotated on the target system, but not on the consumer system. How is the consumer system now updated with the new credential?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have two thoughts regarding this problem:&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;Write a playbook that logins to PVWA to trigger a password rotation (timing), CPM will rotate PW on the target system, after rotation AAP will grab the new credential from either CCP or PVWA and update the consumer system.&lt;/LI&gt;&lt;LI&gt;Create a new PAM Platform and write a new CPM plugin for each M2M use case, where the target and the consumer system is being updated. This means that during account onboarding you need to add another field for the consumer system. &lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is there a common way, best practice, for this problem?&lt;/P&gt;</description>
    <pubDate>Thu, 06 Jun 2024 07:04:20 GMT</pubDate>
    <dc:creator>CHgeek</dc:creator>
    <dc:date>2024-06-06T07:04:20Z</dc:date>
    <item>
      <title>CCP and password rotation</title>
      <link>https://live.paloaltonetworks.com/t5/secrets-management/ccp-and-password-rotation/m-p/1392504#M1713</link>
      <description>&lt;P&gt;Is there a common way, when rotating the password for an account, that the surounding system which uses this account get's the new credential? I know that these surounding systems (we call them consumers) should call the REST API from CCP. But there are an overwhelming number of systems/appliances that can not initiate an API call. Often these are static fields you can fill with username and password.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Let me make an example. A company has a policy which states that all machine-to-machine (M2M) accounts need to be rotated on a regular basis. We have many devices in our company that use service accounts which are set on the consumer during bootstrap with a playbook over Ansible Automation Platform (AAP). The Platform policy is set to rotate password for these accounts after 5 days. Our CPM plugins are built that credentials are rotated on the target system, but not on the consumer system. How is the consumer system now updated with the new credential?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have two thoughts regarding this problem:&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;Write a playbook that logins to PVWA to trigger a password rotation (timing), CPM will rotate PW on the target system, after rotation AAP will grab the new credential from either CCP or PVWA and update the consumer system.&lt;/LI&gt;&lt;LI&gt;Create a new PAM Platform and write a new CPM plugin for each M2M use case, where the target and the consumer system is being updated. This means that during account onboarding you need to add another field for the consumer system. &lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is there a common way, best practice, for this problem?&lt;/P&gt;</description>
      <pubDate>Thu, 06 Jun 2024 07:04:20 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/secrets-management/ccp-and-password-rotation/m-p/1392504#M1713</guid>
      <dc:creator>CHgeek</dc:creator>
      <dc:date>2024-06-06T07:04:20Z</dc:date>
    </item>
    <item>
      <title>Re: CCP and password rotation</title>
      <link>https://live.paloaltonetworks.com/t5/secrets-management/ccp-and-password-rotation/m-p/1392505#M1714</link>
      <description>&lt;P&gt;Hey @Yan Peyer​&amp;nbsp;&lt;/P&gt;&lt;P&gt;I would suggest the second option of managing the consumer accounts with the CPM. You can group accounts as well so if they require the same password, you can make sure they all have it. &lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Def an interesting situation you've got, but it sounds manageable. &lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;-Matt&lt;/P&gt;</description>
      <pubDate>Thu, 06 Jun 2024 12:40:09 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/secrets-management/ccp-and-password-rotation/m-p/1392505#M1714</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2024-06-06T12:40:09Z</dc:date>
    </item>
    <item>
      <title>Re: CCP and password rotation</title>
      <link>https://live.paloaltonetworks.com/t5/secrets-management/ccp-and-password-rotation/m-p/1392506#M1715</link>
      <description>&lt;P&gt;Thanks Matt for your feedback. &lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Actually group accounts is the right approach.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We will now create individual CPM plugins for each device/account/role and group them together mit "group accounts". How the CPM plugins handle pw rotation, either with ssh/web or with python/powershell calling an api, is secondary. &lt;/P&gt;</description>
      <pubDate>Tue, 18 Jun 2024 19:36:31 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/secrets-management/ccp-and-password-rotation/m-p/1392506#M1715</guid>
      <dc:creator>CHgeek</dc:creator>
      <dc:date>2024-06-18T19:36:31Z</dc:date>
    </item>
  </channel>
</rss>

