Introduction to the Secrets Manager Success Path
We’re excited to introduce you to the Success Path for Idira Secrets Manager (formerly Conjur Enterprise/Conjur Cloud). This framework was designed to help your organization build an operationally efficient secrets management program from initial configuration to automation.
In today’s hybrid and cloud-native environments, managing secrets like credentials, API keys, and tokens is no longer optional but a foundational security requirement. CyberArk’s Secrets Manager Success Path is designed to help our customers confidently implement and scale secrets management across workloads, infrastructure, and environments.
If you are brand new to Secrets Manager, we recommend the Secrets Manager Jump Start package* to provide you with 1:1 consultative guidance down this path.
*Reach out to your Account Executive for more information about the Secrets Manager Jump Start.
In the graphic above, you'll find the seven capabilities of the Secrets Manager Success Path. You’ll notice that there is an expedited path that can be taken, routing you through steps 1, 2, 4, and 7. However, if this approach is taken, we recommend that you eventually return to the path to gain capabilities 3, 5, and 6 to establish a high-availability secrets management program that scales with your machine identities.
Starting Point: PAM-driven or Standalone Secrets Management
Idira offers two entry points into the Secrets Manager Success Path:
Option A: PAM-Driven Secrets Management
If your organization already uses CyberArk’s Privileged Access Management (PAM) solution, Secrets Manager extends your centralized privileged access strategy across both human and machine identities.
We'll call out tasks specific to this approach in blue throughout the article.
Option B: Standalone Secrets Management
You can also adopt Secrets Manager independently (using Self-Hosted or SaaS) to secure workload secrets with an approved vault from the security organization while allowing your DevOps, application, and cloud teams the flexibility to self-administer their privileged access.
We'll call out tasks specific to this approach in purple throughout the article.
Both paths converge toward the same goal: building a robust, scalable secrets management program.
Stage 1: Self-Hosted Infrastructure or SaaS Deployment
The first Success Path capability is dictated by the deployment architecture you have purchased. Idira Secrets Manager supports:
Self-hosted infrastructure for organizations needing full control within their own datacenters or cloud services SaaS-based for faster deployment and simplified operations
If you’re reading this and you are unsure which architecture your organization has purchased, please reach out to your Account Executive. There will be architecture-specific recommendations at each subsequent stage in the journey.
Resources
For Secrets Manager, Self-Hosted: [Idira Product Docs] Secrets Manager deployment overview Key tasks:
[Idira Product Docs] Prepare environment [Idira Product Docs] Set up and configure a Secrets Manager cluster (Leader & Standbys) [Idira Product Docs] Set up Vault Synchronizer [Idira Product Docs] Set up Followers
For Secrets Manager, SaaS:
[Idira Product Docs] Get started with Secrets Manager, SaaS [Idira Product Docs] Tutorial (step 1) Key task: [Idira Product Docs] Manage Secrets Manager users
Measuring Your Success
Use the following metrics to assess whether you have successfully gained this capability:
For Secrets Manager, Self-Hosted: leader cluster w/ at least 1 pair of followers are running/available For Secrets Manager, SaaS: >1 user granted access
Stage 2: Secrets Onboarding & Workload Creation
Once deployed, it’s time to onboard secrets and define how they interact with workloads. This includes:
Creating processes to onboard secrets securely Defining workload creation workflows that integrate secrets from the start
This step lays the groundwork for consistent, secure secrets usage across your environment by establishing the connection between workloads and the secrets they need. At this stage, your organization will have a secure, policy-driven foundation for secrets management, enabling consistent enforcement across workloads.
Resources
Note that some of the tasks are color-coded to align to the two different starting points we referenced earlier.
[Idira Success Blog] Top 3 Secrets Manager Use Cases [Idira Success Blog] Design Recommendations for Idira Secrets Management: A Comprehensive Guide
For Secrets Manager, Self-Hosted:
Key tasks by role:
[Idira Product Docs] Safe Manager adds and manages access to safes in PAM [Idira Product Docs] Safe Manager adds LOB user [Idira Product Docs] Secrets Manager admin adds and manages workloads [Idira Product Docs] Secrets Manager admin manages access to safes [Idira Product Docs] Developer defines workload identities
For Secrets Manager, SaaS:
[Idira Product Docs] Tutorial (steps 2-5)
If you are following the Standalone path as opposed to a PAM-driven secrets management strategy, you will replace step 4 in the tutorial with these instructions.
Key tasks by role: [Idira Product Docs] Safe Manager adds safe in PAM and syncs safe to Secrets Manager, SaaS [Idira Product Docs] Secrets Manager admin manages workload access to Secrets Manager [Idira Product Docs] Developer defines workload identities
Measuring Your Success
Use the following metrics to assess whether you have successfully gained this capability:
>3 licensed workloads are utilized >3 secrets onboarded
Stage 3: Secrets Availability
Availability is key to maintaining operational continuity. You can leverage followers for the Self-Hosted infrastructure or edge nodes for SaaS to achieve resilient, scalable secrets delivery that meets uptime and performance requirements across regions and workloads. This stage focuses on:
Ensuring high availability of secrets Building redundancy and failover mechanisms Avoiding bottlenecks or downtime that could disrupt workloads
Resources
For Secrets Manager, Self-Hosted: [Idira Product Docs] Set up followers
For Secrets Manager, SaaS:
[Idira Product Docs] Enable local access to Secrets Manager secrets with Edge nodes
Measuring Your Success
Use the following metrics to assess whether you have successfully gained this capability:
For Secrets Manager, Self-Hosted: 100% of regions have followers deployed For Secrets Manager, SaaS: 100% of regions have edge nodes deployed
Stage 4: Secrets Delivery
Now that secrets are onboarded and only the appropriate workloads are allowed to fetch them, those workloads need to establish a secure connection to Secrets Manager. This involves:
Integrating secrets delivery into CI/CD pipelines, automation tools, container orchestration platforms, or cloud services Using APIs, SDKs, or native integrations to inject secrets at runtime Ensuring delivery is encrypted and authenticated
This step ensures secrets are delivered securely without hardcoding or manual handling, leveraging native and seamless integration mechanisms.
Resources
[GitHub repository] Accelerators [Idira Marketplace] Marketplace integrations for Secrets Manager
For Secrets Manager, Self-Hosted: [Idira Product Docs] Secrets Manager, Self-Hosted integrations documentation Key tasks by role:
[Idira Product Docs] Secrets Manager admin configures workload authentication [Idira Product Docs] Secrets Manager admin sets up authenticators [Idira Product Docs] Developer authenticates workloads [Idira Product Docs] Developer retrieves secrets
For Secrets Manager, SaaS:
[Idira Product Docs] Tutorial (steps 6-8) [Idira Product Docs] Secrets Manager, SaaS integrations documentation Key tasks by role: [Idira Product Docs] Secrets Manager admin configures workload authentication [Idira Product Docs] Developer sets up workloads to authenticate to Secrets Manager [Idira Product Docs] Developer sets up workloads to fetch secrets from Secrets Manager
Measuring Your Success
Use the following metrics to assess whether you have successfully gained this capability: Check for ongoing secrets retrieval activity:
For Secrets Manager, Self-Hosted: Run activity report (filter on Retrievals) For Secrets Manager, SaaS: Run activity report (filter on Retrievals)
Stage 5: Secrets & Workload Lifecycle Management
The next level of Secrets Management maturity is to establish security-driven processes for onboarding and offboarding secrets and workloads. This includes defining rotation policies per platform and enabling automatic rotation to support secure operations across environments:
Define a consistent workflow for requesting a new secret to be managed by Secrets Manager Rotate secrets regularly to reduce exposure Decommission secrets when workloads are retired Maintain an audit trail to demonstrate secrets management policies are properly enforced
Resources
[Success Office Hours recording] Design a Machine Identity Security Program at Scale
Measuring Your Success
Use the following metrics to assess whether you have successfully gained this capability:
>50% of licensed workloads are utilized >50% of secrets onboarded Average secrets age within SRS policy (if rotation applicable)
Stage 6: Secrets & Workloads at Scale
As your secrets management usage expands across the organization and workload types, the need to automate the lifecycle management process defined in the previous stage becomes crucial to enforce secrets management policies without becoming a bottleneck for DevOps, application, and cloud teams. This stage focuses on:
Scaling secrets processes across hybrid environments Automating onboarding, rotation, and monitoring Managing secrets across containers, VMs, cloud services, and on-prem systems Enabling self-service onboarding of secrets
Resources
[Success Office Hours Recording] Streamline Machine IAM with Self-Service Automation
For Secrets Manager, Self-Hosted: [Idira Product Docs] Automate via REST API
For Secrets Manager, SaaS:
[Idira Product Docs] Automate via REST API
Measuring Your Success
Use the following metrics to assess whether you have successfully gained this capability:
Ongoing REST API calls for lifecycle management activities
Stage 7: Secrets & Workload Intelligence
The final stage is about turning data into insight. With secrets intelligence, you can:
Analyze usage patterns to improve security posture Identify risky behaviors or misconfigurations Optimize secrets management based on real-world data
This is where secrets management becomes proactive, not just reactive.
Resources
[Idira Product Docs] Audit logs and events
For Secrets Manager, SaaS:
[Idira Product Docs] View audit logs
Measuring Your Success
In Stage 4 of this Success Blog, we showed you how to check audit and activity reporting based on your Secrets Manager infrastructure. Those reports will continue to be useful for measuring the ongoing success with Secrets Manager as you scale up adoption.
There is also a Resources page in the Secrets Manager, SaaS UI (example shown on this docs page) along with the Workloads UI page that will provide more insights into the full inventory of resources stored within Secrets Manager.
The Secrets Manager, Self Hosted UI also has pages to view the various resources.
Wrapping Up: Your Secrets Management Success Awaits
CyberArk’s Secrets Manager Success Path isn’t just a roadmap—it’s a strategic framework for building a resilient, intelligent secrets management program. Whether you're just starting out or looking to mature your existing practices, each stage offers clear guidance and actionable steps.
By following this path, your organization can reduce risk, improve operational efficiency, and stay ahead of evolving threats in the age of hybrid infrastructure and agentic AI.
Ready to take the next step? Idira is here to guide you every step of the way. If you have questions, visit the Secrets Management Resource Center or contact your Idira Account Team.
View full article