Table of contents
- Introduction
- Why automate onboarding?
- Assumptions
- Process overview
- Planning the automation
- Building the automation
- Securing the automation
- Streamlining for success
Introduction
One of the challenges with successfully executing a robust cloud security strategy is the need for alignment and coordination between various internal teams: application teams, Cloud Administrators, Operations, and the PAM team.
Secrets Hub offers a simple integration that provides centralized management, visibility, and rotation of secrets stored in your cloud service provider’s native secrets manager – but only if your internal teams actually use it. Efficient intraorganizational collaboration is a critical prerequisite for successfully implementing Secrets Hub, as each team must participate in the end-to-end workflow (outlined here in our product documentation).
In this article you can expect to learn:
- Why automated onboarding can help drive adoption of Secrets Hub and how it benefits your stakeholder teams
- How to determine if your organization is operationally mature enough to consider automating these flows
- CyberArk’s recommended flow for automating new accounts into Secrets Hub
- Why you should leverage another secrets manager to secure your automation
After reading this article and reviewing the linked resources, you will have the tools to begin building these automations yourself and/or effectively communicate requirements with another team who can build them on your behalf.
As the security team, it is necessary to consider the needs of your stakeholder teams to drive internal adoption and operationalization of Secrets Hub. Automating the application onboarding process is one way to respond to the various priorities of your stakeholder teams while ensuring a high standard of security for all. We’ll outline below how automating the onboarding process serves each of your stakeholder teams:
- Application teams want to work fast. When they’re ready to deploy an app, they’re less tolerant of the delays that may arise while they attempt to follow security standards. If they must wait for the PAM team to manually onboard a newly created AWS account and IAM role to Secrets Hub, then application team’s end goal – the deployment of their app – is also delayed. Repeated delays may tempt them to avoid these steps altogether, hindering successful adoption of Secrets Hub. Automation enables the PAM team to support a high volume of requests from your application teams while also maintaining a consistent, standard configuration.
- Cloud operations teams have many responsibilities related to the management, delivery, and consumption of cloud environments and applications. Anything we can do to reduce their workload with automated account provisioning and role creation benefits them greatly. It also ensures that their processes align to Secrets Hub’s requirements without manually having to do so.
- Operations teams have a vested interest in maintaining a high level of security for their environments. They are often accountable for the integrity and availability of their environments, and as such, are often the first call if there is a security incident. Following our suggested onboarding flow will uplift the security of the provisioning process (which today might involve the practice of sending credentials to the application team via Teams or email).
Bear in mind, before we can consider automating the onboarding process, you must have clearly defined processes in place. If your organization has not achieved this level of operational maturity, you’re welcome to continue reviewing our proposed workflow before – hopefully it inspires a vision of what “good” might look like at your organization. However, we’d encourage you to hold off on employing any automation until you’ve formalized these processes.
In order to implement the recommended automation below, we are assuming you have clearly defined cloud processes and separation of duties. Here are some statements that we are assuming of your organization in the proposed flow:
- You use a ticketing system for application teams to request resources.
- You have a Cloud operations team that reviews those requests and provisions AWS and Azure resources.
- You are following AWS best practices where you have one AWS account per application, and this process of provisioning new AWS accounts is happening regularly. If you use Microsoft Azure, you follow the equivalent best practice of one Azure subscription per application.
- You have an Operations team responsible for provisioning the accounts used by these applications, rather than the application team or PAM team doing so.
Here is our proposed process flow for onboarding Secrets Hub accounts in an automated fashion. Take a moment to review the diagram below.
Figure 1: Secrets Hub Automated Onboarding Workflow
In this flow, you’ll notice a pattern that plays out three times: the application team submits a ticket >> which is assigned to [TEAM] >> who reviews and approves it >> who triggers a specific automation to complete [TASKS].This pattern repeats for three teams/sets of tasks:
| Team | Tasks |
| Cloud Operations | Provisions new AWS account or Azure subscription and the IAM role required by Secrets Hub for each new application |
| Privileged Access Management (PAM) | Creates the PAM safe, the Secrets Hub secret store, and Secrets Hub sync policy for each new account/subscription |
| Operations | Provisions the accounts used by the applications built by the application team (such as a database user) |
Something to note: Cloud Operations and Operations are likely already leveraging some sort of automation to complete these tasks. When we consider automating the overall flow as outlined in Figure 1, we are building upon the other teams’ existing automation for standing up a tenant and extending it to include additional functionality. In our experience, it’s likely you will need to 1) modify existing automations created by the Cloud Operations and Operations teams and 2) build automation for the PAM team’s tasks (unless you’re a team who has already ventured into PAM automation – in which case, well done!) The key here is that there is already a process in place for provisioning these accounts. If that process has not been formalized, it will be impossible to automate.
Now that we've outlined the high-level flow, let’s dive into each step. To support you as you plan and coordinate across teams, we've created this this Excel workbook, which guides you through the details and particulars of implementing this automation. This Secrets Hub Automation Planning workbook includes a list of all the tasks we’ve outlined in the diagram above, along with the inputs and outputs you'll need at each step to facilitate the automation. It also provides best practice notes and relevant links to product documentation so that you can technically execute each step.

Figure 2: Secrets Hub Automation Planning Workbook
If you’re reading this as a member of the PAM team, your first step is to start creating targets and policies for Secrets Hub via REST API. Postman is a user-friendly app you can use to gain some experience creating API calls, and Idira has assembled a Secrets Hub API Postman Collection so you can easily reference all of the APIs. It can be intimidating, but your willingness to jump in and learn will only benefit you and your stakeholders. Here are several resources you can use to get started!
Next, you’ll use the APIs you’ve set up using Postman to build the automation. We’ve outlined 4 approaches you can take to build automation.
Option 0: Build it within your TeamDoes someone on your PAM team have scripting knowledge? Engage them with the prep work you’ve done with the APIs above as well as your automation planning workbook.If your PAM team does not have scripting and automation knowledge, you could change that by taking a few free online courses in a scripting language like PowerShell or Python. If that’s not something you are willing or able to do, never fear; we have several other ideas to help you get started!Option 1: Build a partnership with your Operations teamAn Operations team typically has the scripting/automation skills you need to automate the PAM onboarding tasks above. Consider sharing this proposed automated flow with a representative from that team, illustrating how these improvements can uplift the security of their current provisioning processes (i.e., no more emailing passwords to app teams) and absorb other responsibilities (i.e., automated password rotation via PAM). Then ask for their assistance with building PAM automation to support the middle section of tasks. They’re more likely to assist if you have done your homework with the API calls that will be needed, using the Postman collection we referenced above.Option 2: Contract with a partner to build and/or support the automationIf your Operations team is not able to assist you with these tasks, it can always be outsourced to one of our trusted partners. Reach out to your AE to learn more. Alternatively, you can check to see if there’s an internal team dedicated to building this kind of automation at your organization.Option 3: Procure assistance with CYBR Prof ServicesWork with us, we’ll provide guidance. If you go this route, you’ll ultimately need to identify an internal owner for the code so you can support it long-term, but Idira Professional Services can provide the guidance you need to level up your skillset for rudimentary automation. Reach out to your AE for next steps.
Finally, a word of caution about securing your automation. Any automation that is leveraging APIs will also require credentials to authenticate to Secrets Hub and PAM – and as we’ve covered before, hard-coded credentials are a security risk. Our recommendation is to secure your automation with Conjur Cloud or Credential Providers, which you can review in detail in this Success blog.You may be thinking, “This was already enough effort before you told me I needed to secure my automation!” But consider it from this perspective – this is the same request you are making of all your application teams when they incorporate secrets management into their development work. By building an automation with secured credentials, you have a great opportunity to lead by example and gain firsthand knowledge of the tools you’re asking them to utilize as well. Use this as a success story as you evangelize secrets management across the business and gain true empathy for your stakeholders that will serve your long-term partnership.
Once you have reviewed this article, along with the supporting resources we referenced, you should now be able to:
- Articulate the benefits of automation to your stakeholder teams
- Determine if your organization is operationally ready for automation
- Plan and build onboarding automation for your organization
- Secure your automation with a secrets manager
What are your thoughts? What lessons have you learned from implementing this at your organization? Start a conversation in the Secrets Manager Resource Center or explore our Secrets Hub topic on the Community!