<?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: Mega Post: CyberArk Privilege Cloud as Code + DevOps Best Practice for CyberArk | Help me! in Privilege Cloud Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/mega-post-cyberark-privilege-cloud-as-code-devops-best-practice/m-p/1340393#M2355</link>
    <description>&lt;P&gt;I have great news for ISP customers! CyberArk + RedHat now have a RedHat-certified Ansible collection for idempotent management of CyberArk Privilege Cloud infrastructure!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;https://galaxy.ansible.com/ui/repo/published/cyberark/isp/docs/&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I will be testing this in the coming weeks -- very excited to see what it can do. I still REALLY wish that Terraform was supported, or that psPAS was officially maintained by CyberArk, but this is great too! Ansible gives us nice self-documenting code-based deployments.&lt;/P&gt;</description>
    <pubDate>Fri, 30 May 2025 13:40:32 GMT</pubDate>
    <dc:creator>TSell</dc:creator>
    <dc:date>2025-05-30T13:40:32Z</dc:date>
    <item>
      <title>Mega Post: CyberArk Privilege Cloud as Code + DevOps Best Practice for CyberArk | Help me!</title>
      <link>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/mega-post-cyberark-privilege-cloud-as-code-devops-best-practice/m-p/1340391#M2353</link>
      <description>&lt;P&gt;Hello!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I am interested in managing CyberArk STATEFULLY through code, and I am running into some issues as a Privilege Cloud customer. Allow me to elaborate and ask the community for insight!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Generally, I would prefer a typical solution for code-based stateful management of a product like this. I imagined using Terraform or Ansible to accomplish the goal of tracking the state of CyberArk configurations through code, writing new changes via code, and provisioning new infrastructure through code. However, the support for these tools for Privilege Cloud is rather scant, so I moved to homebrewing something with PowerShell or Python. I found that there are no officially supported PowerShell libraries, and only one officially supported Python library...but the documentation for the SDK is incomplete.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;To summarize:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Terraform: The provider is supported by CyberArk but is not in version 1.0 yet and only supports the Safes API, and some other misc. pieces of the API.&lt;/P&gt;&lt;P&gt;&lt;A alt="https://registry.terraform.io/providers/cyberark/cyberark/latest/docs" href="https://registry.terraform.io/providers/cyberark/cyberark/latest/docs" target="_blank"&gt;Docs overview | cyberark/cyberark | Terraform | Terraform Registry&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Ansible: There is an Ansible collection plugin, but it appears to only support the Accounts API for account management. Nothing for infrastructure like Safes, for example.&lt;/P&gt;&lt;P&gt;&lt;A alt="https://docs.ansible.com/ansible/latest/collections/cyberark/pas/index.html" href="https://docs.ansible.com/ansible/latest/collections/cyberark/pas/index.html" target="_blank"&gt;Cyberark.Pas — Ansible Community Documentation&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;PowerShell: The famous psPAS is &lt;B&gt;seriously awesome &lt;/B&gt;and may just be the choice here, but management is worried about enterprise support and maintenance. Even if psPAS were the play here, we would have to build the state tracking in house (probably by dumping platforms and safes to JSON and storing that as a file. Then, prior to write operations, I would check if the state had changed since the last write).&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Python: This is what our developers are most familiar with but, despite the published SDK being officially CyberArk's, the documentation appears incomplete! I have attached the link here for review: &lt;A alt="https://github.com/cyberark/ark-sdk-python/tree/main" href="https://github.com/cyberark/ark-sdk-python/tree/main" target="_blank"&gt;https://github.com/cyberark/ark-sdk-python/tree/main&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;As an example of the issues with Python, here are the incomplete Safes SDK documents:&lt;/P&gt;&lt;P&gt;&lt;A alt="https://cyberark.github.io/ark-sdk-python/latest/reference/models/services/pcloud/safes/" href="https://cyberark.github.io/ark-sdk-python/latest/reference/models/services/pcloud/safes/" target="_blank"&gt;https://cyberark.github.io/ark-sdk-python/latest/reference/models/services/pcloud/safes/&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;In conclusion, &lt;B&gt;does anybody out there have success with a stateful and DevOps-oriented management workflow with CyberArk Privilege Cloud?&lt;/B&gt; Ideally -- life would look like this: "A user submits a ticket form with safe details, etc. That form dumps to JSON and triggers a GitHub Action where an IAC tool / script checks the state for changes or conflicts and builds the requested infrastructure after approval. The state is then updated."&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you!&lt;/P&gt;</description>
      <pubDate>Wed, 28 May 2025 17:19:12 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/mega-post-cyberark-privilege-cloud-as-code-devops-best-practice/m-p/1340391#M2353</guid>
      <dc:creator>TSell</dc:creator>
      <dc:date>2025-05-28T17:19:12Z</dc:date>
    </item>
    <item>
      <title>Re: Mega Post: CyberArk Privilege Cloud as Code + DevOps Best Practice for CyberArk | Help me!</title>
      <link>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/mega-post-cyberark-privilege-cloud-as-code-devops-best-practice/m-p/1340392#M2354</link>
      <description>&lt;P&gt;Fantastic post, and questions I also definitely want answers to. CyberArk seem to be focussing a lot of attention on dynamic Discovery of assets which isn't quite enough to satisfy an IAC approach.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;There may be additional requirements to manage SIA and SCA as code. There is already a Terraform module for SCA which handles policies, and as I understand it there is a move towards unifying SIA and SCA policies with a single API to manage them. &lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This wouldn't quite solve all the SIA requirements, because many SIA use-cases require explicit strong accounts to be onboarded (eg non-domain Windows devices, non-domain Databases) and the Terraform modules don't cover strong account onboarding, or resource configuration, or TLS certificates. For domain-joined Windows targets and SSH targets w/certificates the terraform module will probably be sufficient once the update to the unified Administration space is completed and a new terraform module is released to use it.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This also doesn't solve all SCA use-cases because Identity Apps have no Terraform support at all afaik, nor any IaC approach. So to onboard a new SaaS target environment will require manual work to create the Identity app integration. I have heard that there may be work going on at CyberArk to automate this into the unified Administration space (with a unified API) but I don't think automation of Identity Apps is even announced yet.&lt;/P&gt;</description>
      <pubDate>Thu, 29 May 2025 09:24:10 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/mega-post-cyberark-privilege-cloud-as-code-devops-best-practice/m-p/1340392#M2354</guid>
      <dc:creator>Jon_Musker</dc:creator>
      <dc:date>2025-05-29T09:24:10Z</dc:date>
    </item>
    <item>
      <title>Re: Mega Post: CyberArk Privilege Cloud as Code + DevOps Best Practice for CyberArk | Help me!</title>
      <link>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/mega-post-cyberark-privilege-cloud-as-code-devops-best-practice/m-p/1340393#M2355</link>
      <description>&lt;P&gt;I have great news for ISP customers! CyberArk + RedHat now have a RedHat-certified Ansible collection for idempotent management of CyberArk Privilege Cloud infrastructure!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;https://galaxy.ansible.com/ui/repo/published/cyberark/isp/docs/&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I will be testing this in the coming weeks -- very excited to see what it can do. I still REALLY wish that Terraform was supported, or that psPAS was officially maintained by CyberArk, but this is great too! Ansible gives us nice self-documenting code-based deployments.&lt;/P&gt;</description>
      <pubDate>Fri, 30 May 2025 13:40:32 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/mega-post-cyberark-privilege-cloud-as-code-devops-best-practice/m-p/1340393#M2355</guid>
      <dc:creator>TSell</dc:creator>
      <dc:date>2025-05-30T13:40:32Z</dc:date>
    </item>
  </channel>
</rss>

