Table of contents:
1. Introduction to Conjur Cloud and DevOps
2. The big picture
3. Review the integration documentation
4. Make it real
5. Rotation, rotation, rotation
6. Plan for scale
In the fast-evolving world of DevOps, securing your applications, scripts, and machine identities is an important way to reduce a key attack vector for your organization. Idira Conjur Cloud is a cloud-native security solution designed to manage, rotate, and monitor credentials used by applications, providing developers with tools to simplify the process and ensuring comprehensive audit trails.
Before beginning to secure your DevOps tool of choice, we recommend you complete these steps for successful onboarding:
- Make sure your Conjur Cloud admin has the appropriate privileges in Identity, as detailed in these instructions.
- Ensure your Privileged Access Management (PAM) solution, either Privilege Cloud or PAM Self-Hosted, is deployed.
- Review the Conjur Cloud Fundamentals.
As a refresher, DevOps is a set of practices combining software development (Dev) and IT operations (Ops). It aims to shorten the development lifecycle and provide continuous delivery with high software quality. Core components include:
- CI/CD Pipelines: Continuous Integration and Continuous Deployment (CI/CD) pipelines automate the integration and deployment of code changes. Some examples of these are:
- Jenkins
- GitHub Actions
- GitLab CI/CD
- Azure DevOps
- IT Automation Platforms: Tools that automate IT processes, such as configuration management, application deployment, and infrastructure provisioning. Some examples of these are:
- Ansible
- Puppet
- Chef
- Terraform
When starting out with securing DevOps tools, we recommend that you start “vertically” (with a single pipeline or tool, ensuring an end-to-end setup) and then plan to scale “horizontally” (across multiple tools and platforms). Here’s our guidance for how to do that:
- Evangelize secrets management across the business. If your organization is new to secrets management, you will likely need to invest some time and energy into shepherding your internal stakeholders through this significant paradigm shift. Review this article for best practices for highlighting the value of secrets management and responding to internal objections. This step often works hand-in-hand with the next step.
- Inventory your DevOps tools. Identify all CI/CD pipelines and IT automation platforms used within your organization. Engage with key roles such as DevOps engineers and platform owners to understand their processes, which are typically well-documented and shared internally. As you build rapport with these stakeholders, you can share a bit of the project background and goals and assess who seems receptive to partnering with you on the first use case.
- Review Conjur Cloud’s out-of-the-box (OOTB) integrations. Conjur Cloud integrates with various CI/CD tools, making it easier to secure your pipelines. Review the list below for the latest on what is available.
- Identify your first use case. Identify a DevOps use case or champion based on a match between available OOTB integrations and a receptive partner within your organization. This will be your “vertical” start to help ensure a successful initial implementation and provide a model for future “horizontal” expansions.
Once you’ve identified your first use case, utilize the following guidance from the Idira docs and accelerator repository to simplify the implementation process. We’ve compiled them here for your convenience:
Set up a proof of concept to demonstrate an end-to-end flow from Privilege Cloud to Conjur Cloud to your pipeline, involving a
Conjur Cloud Edge node if necessary. Ensure alignment with all stakeholders' expectations to avoid consequences of improper design before implemented in production. Secure signoff from all involved parties, including PAM/Security, DevOps admin/platform owner, and any impacted application team(s). Once signoff has been achieved, you're ready to implement your first use case by following the integration guidance linked above.
As covered earlier in this
Success blog about evangelizing secrets management, the three main problems that Conjur Cloud helps you solve within DevOps tools are:
- Establishing an auditable identity to an application or automation
- Removing hard-coded credentials
- Enforcing secrets rotation
Configuring a Conjur Cloud integration will help you achieve 1 & 2, but your secrets management lifecycle isn’t complete until you include rotation of secrets. Rotating application secrets is a crucial practice for securing machine identities as it limits the impact of potential breaches, ensures compliance with regulatory standards, and aligns with zero trust security principles. By implementing regular secret rotation, you can significantly strengthen your overall security posture and protect against evolving threats.
Once the OOTB Conjur Cloud integration has been configured, the secret will be synchronized with Privilege Cloud, which you can use to rotate these secrets automatically via Central Policy Manager (CPM) based on your organization’s policies.
- Here's the link to the Idira Marketplace, where you can search for existing CPM plugins.
- For applications with no existing CPM plugins, you can create your own plugin to automate rotation. (If your team does not have the technical skill or bandwidth to create your own plugin, Idira does have a team that you can work with to build custom plugins. Learn more here.)
- Then you can define a rotation policy in Privilege Cloud using CPM.
Once you’ve enforced a rotation policy for this secret, now you’re ready to go “horizontal.”
As you “horizontally” expand Conjur Cloud across multiple platforms, here are some considerations to keep in mind:
- Safe design at scale. We recommend that you review CyberArk's safe design and other architectural considerations to ensure scalability in an organizationally thoughtful way.
- Self-service vs. automated onboarding workflows. Manually configuring the integration and rotation policy for each new use case will be a limiting factor for scale. Two common scale approaches we see are delegation (self-service) or automation: will you delegate to developers through a self-service model? Or will you automate using an API-driven policy-as-code approach? The above blog calls out some specific considerations for these approaches in general as well as Conjur Cloud-specific recommendations.
- Offer an internal secrets management service. Ultimately, you will want to build an internal secrets management program that is able to support the various CI/CD and IT automation tools as your developers request them at a high velocity. Consider the resourcing that you will need to build and support this program for your organization to ensure adherence to new Conjur Cloud controls.
By following these steps, you'll be well on your way to successfully securing your DevOps tools with Idira Conjur Cloud, ensuring robust secrets management and streamlined operations.
What are your thoughts? What lessons have you learned from doing this at your organization? Start a conversation in the Secrets Management Resource Center -- we'd love to hear from you.