- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.
06-05-2025 08:39 AM
Hello, all,
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.
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. Is there a better way??
Preferably we would like to create a policy which geo/IP-restricts logins for this user and mandates a particular certificate for API logins. Furthermore, interactive logons should be impossible with the account. That way, the certificate and private key become the zero-secret for such a workflow.
Does the community have any wisdom here for CyberArk Identity API Security for workflows like these?
Thanks!
07-10-2025 02:52 PM
Hi @Tyler Sell
Are you using or have explore CyberArk Conjur which will allow automation tools to use the secret on the fly? 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.
Or if you have CCP you can use to retrieve the secret in run-time.
Please also check "API Authentication for CyberArk Identity Security Platform Shared Services"
https://docs.cyberark.com/ispss-access/latest/en/content/ispss/ispss-api-authentication.htm
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 !
Please refer to the following CyberArk documents.
https://docs.cyberark.com/conjur-enterprise/latest/en/content/operations/authn/cjr-authn-support.htm
https://docs.cyberark.com/identity/latest/en/content/coreservices/authenticate/ipblock.htm
https://docs.cyberark.com/identity/latest/en/content/coreservices/authenticate/securezones.htm
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!

