<?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 How to secure service users / use client ID+Secret for API? in Workforce Identity Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/workforce-identity-discussions/how-to-secure-service-users-use-client-id-secret-for-api/m-p/1340408#M512</link>
    <description>&lt;P&gt;Hello, all,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We would like to use automation tools (e.g. psPAS, Ansible, etc.) in order to operationalize CyberArk Privilege Cloud into a DevSecOps pipeline. Technically, this is achieved, and we are now moving to a security review for this process.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;As far as we can tell from the Shared Services Platform, CyberArk Identity does NOT support API entitlements via a client ID and client Secret. Instead, our workflow must leverage a legacy workflow using an MFA-less Service Account. &lt;B&gt;Is there a better way??&lt;/B&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Preferably we would like to create a policy which geo/IP-restricts logins for this user &lt;B&gt;and &lt;/B&gt;mandates a particular certificate for API logins. Furthermore, &lt;B&gt;interactive logons should be impossible with the account&lt;/B&gt;. That way, the certificate and private key become the zero-secret for such a workflow.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Does the community have any wisdom here for CyberArk Identity API Security for workflows like these?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;</description>
    <pubDate>Thu, 05 Jun 2025 15:39:48 GMT</pubDate>
    <dc:creator>TSell</dc:creator>
    <dc:date>2025-06-05T15:39:48Z</dc:date>
    <item>
      <title>How to secure service users / use client ID+Secret for API?</title>
      <link>https://live.paloaltonetworks.com/t5/workforce-identity-discussions/how-to-secure-service-users-use-client-id-secret-for-api/m-p/1340408#M512</link>
      <description>&lt;P&gt;Hello, all,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We would like to use automation tools (e.g. psPAS, Ansible, etc.) in order to operationalize CyberArk Privilege Cloud into a DevSecOps pipeline. Technically, this is achieved, and we are now moving to a security review for this process.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;As far as we can tell from the Shared Services Platform, CyberArk Identity does NOT support API entitlements via a client ID and client Secret. Instead, our workflow must leverage a legacy workflow using an MFA-less Service Account. &lt;B&gt;Is there a better way??&lt;/B&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Preferably we would like to create a policy which geo/IP-restricts logins for this user &lt;B&gt;and &lt;/B&gt;mandates a particular certificate for API logins. Furthermore, &lt;B&gt;interactive logons should be impossible with the account&lt;/B&gt;. That way, the certificate and private key become the zero-secret for such a workflow.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Does the community have any wisdom here for CyberArk Identity API Security for workflows like these?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;</description>
      <pubDate>Thu, 05 Jun 2025 15:39:48 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/workforce-identity-discussions/how-to-secure-service-users-use-client-id-secret-for-api/m-p/1340408#M512</guid>
      <dc:creator>TSell</dc:creator>
      <dc:date>2025-06-05T15:39:48Z</dc:date>
    </item>
    <item>
      <title>Re: How to secure service users / use client ID+Secret for API?</title>
      <link>https://live.paloaltonetworks.com/t5/workforce-identity-discussions/how-to-secure-service-users-use-client-id-secret-for-api/m-p/1340409#M513</link>
      <description>&lt;P&gt;Hi @Tyler Sell​&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Are you using or have explore CyberArk Conjur which will allow automation tools to use the secret on the fly? &amp;nbsp;In addition of that, you can explore Identity's policies to add extra layers of security like IP restrictions and making sure no one can ever log in interactively with that automation account.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Or if you have CCP you can use to retrieve the secret in run-time. &lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Please also check "API Authentication for&amp;nbsp;CyberArk Identity Security Platform Shared Services" &lt;/P&gt;&lt;P&gt;https://docs.cyberark.com/ispss-access/latest/en/content/ispss/ispss-api-authentication.htm &lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I think the above two possible ways would give you the zero-secret solution which you're looking for in your automation tools.  Hope it helps ! &lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Please refer to the following CyberArk documents.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;https://docs.cyberark.com/conjur-enterprise/latest/en/content/operations/authn/cjr-authn-support.htm&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;https://docs.cyberark.com/identity/latest/en/content/coreservices/authenticate/ipblock.htm&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;https://docs.cyberark.com/identity/latest/en/content/coreservices/authenticate/securezones.htm &lt;/P&gt;</description>
      <pubDate>Thu, 10 Jul 2025 21:52:56 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/workforce-identity-discussions/how-to-secure-service-users-use-client-id-secret-for-api/m-p/1340409#M513</guid>
      <dc:creator>M.Vora780263</dc:creator>
      <dc:date>2025-07-10T21:52:56Z</dc:date>
    </item>
  </channel>
</rss>

