Idira Secrets Manager (formerly CyberArk Conjur)
Capability scores
Methodology →- Authentication
- 3.0
- SSO & Federation
- 2.5
- Authorization
- 4.0
- Lifecycle & Provisioning
- 4.0
- MFA & Passwordless
- 2.0
- Governance & Audit
- 4.5
- Developer Experience
- 4.0
- Deployment Flexibility
- 4.0
- Pricing Transparency
- 3.5
- Support & Ecosystem
- 3.5
Scored 0–5 against a published rubric. Independent analysis, no vendor sponsorship.
Overview
Idira Secrets Manager (formerly CyberArk Conjur) is the secrets management product of Idira, the brand Palo Alto Networks gave the CyberArk portfolio on 12 May 2026, with customer-visible changes from 31 May. Conjur Cloud and Conjur Enterprise are now sold as Idira Secrets Manager, in SaaS and self-hosted editions, while the open-source core keeps the name Conjur Open Source. It provides policy-as-code secrets for applications, containers, and CI/CD pipelines, and it integrates tightly with Idira Privileged Access Manager. In the secrets management category it is the enterprise, governance-heavy option, most compelling for organizations already standardized on Idira (CyberArk) for human privileged access who want to extend the same controls to machine and application identities. Idira Secrets Hub is a separate product that syncs secrets into cloud-native vaults.
What it is good at
The policy model is the differentiator: secrets, roles, and access rules are defined as declarative, version-controlled policy, which suits teams that treat security configuration like code. Authorization is granular, and audit and governance are strong, with detailed logging that satisfies demanding compliance regimes. Integration with the broader Idira platform means privileged human access and machine secrets sit under one governance umbrella. Kubernetes, OpenShift, and CI/CD integrations are mature, and the open-source core lets teams evaluate before committing.
Where it falls short
Idira Secrets Manager is heavier to operate than newer developer-first tools. The policy-as-code approach has a learning curve, and standing up and running the enterprise edition takes real platform investment. Its value is highest inside the Idira (formerly CyberArk) ecosystem; standalone, lighter-weight needs are over-served. Developer experience, while solid, is less frictionless than tools built SaaS-first.
Pricing
Conjur Open Source is free to self-operate. Idira Secrets Manager, SaaS and self-hosted, is quote-based: the product page routes to a demo request, and it is typically licensed alongside the wider Idira platform. No public list pricing. Model it against a managed alternative with the TCO calculator.
Best for, and who should look elsewhere
Choose Idira Secrets Manager when you are an Idira (formerly CyberArk) customer extending privileged access to applications and DevOps, or you want policy-driven secrets with strong audit. If you want lighter, developer-first secrets, see Doppler or Infisical; for cloud-native AWS, AWS Secrets Manager. Compare directly via HashiCorp Vault vs CyberArk Conjur.
Bottom line
A strong, governance-heavy enterprise secrets engine, most compelling for organizations already invested in Idira, formerly CyberArk.
Idira Secrets Manager (formerly CyberArk Conjur) comparisons
More Secrets Management vendors
All Secrets Management →- Azure Key Vault4.3/5
- GitGuardian4.3/5
- AWS Secrets Manager4.2/5
- Google Cloud Secret Manager4.2/5
- Doppler4.1/5
Related on Start with Identity
- Vendor1Password Secrets Automation
strong
- VendorDelinea DevOps Secrets Vault
strong_contender
- VendorGoogle Cloud Secret Manager
strong_contender
- Comparisonaws-secrets-manager-vs-hashicorp-vault
AWS Secrets Manager costs 0.40 dollars per secret per month with nothing to run. Vault has dynamic secrets everywhere and no public price, and you have to opera
- ArticleCyberArk Alternatives in 2026: 6 PAM Options Compared After the Idira Rebrand
CyberArk is now Idira, inside Palo Alto Networks, and the vendor neutrality many buyers chose it for is gone. Six alternatives compared on depth, operational we
- CVECyberArk Conjur IAM authenticator bypass via malformed regex
Conjur's AWS IAM authenticator could be pointed at an attacker-controlled STS by a malformed regex (CWE-807). CVSS 9.1. One of five Cyata findings, chainable to
By SWI Community Team · Last evaluated 2026-11-05
Independent, community-driven analysis. No vendor sponsorship. Compiled from public research and community input and verified on a best-effort basis, so details may be incomplete or out of date. Scores are opinions, not advice. Trademarks belong to their owners; mention does not imply affiliation or endorsement. See the full disclaimer, or send corrections to community@startwithidentity.com.