Workspace
    • Briefing
    • Ask Airframe
    Transformation
    • Audit
    Your Stack
    • Registry
    • Finance
    • Context
    Discover
    Powered by Airframe
    1. Research
    2. /
    3. Products
    4. /
    5. CyberArk Secrets Management
    CyberArk Secrets Management

    CyberArk Secrets Management

    Leader

    CyberArk is the global leader in identity security.

    Est 1999|Valuation $20.6B|Raised $1.5B
    LinkedIn 325K|Website|Web traffic 444K|FTEs 4,000|HQ Newton, MA
    MarketsCloud-Native Application Protection Platform (CNAPP)Privileged Access Management (PAM)Security Service Edge (SSE)Identity Provider (IdP) & Single Sign-On (SSO)Secrets Management
    Platform CoversPrivileged Access Management (PAM)
    CyberArk Secrets Management screenshot
    FirmCompareTractionAnalysisAdvocates

    Insights

    All insightsAccountingFinanceSoftwareCustomer experience

    Benchmarks

    The Software LeaderboardMethodology

    Tools & data

    Market ExplorerStudioRegistry

    Company

    AboutCareers

    Legal

    Privacy PolicyTerms of Service

    © 2026 Airframe, Inc. All rights reserved.

      Published Sep 26, 2026

      01Common complaints

      1) When a low-complexity, developer-led rollout with minimal platform overhead is the primary requirement. Community posts describe CyberArk/Conjur as having multiple components and higher operational complexity. 2) When the organization will not fund specialized administration or partner services. Several users report reliance on partners or professional services for deployment and ongoing operations. 3) When the deployment is primarily single-cloud and CSP-native controls are acceptable. Cloud provider secret stores may meet requirements without an additional platform layer, although they may not provide consistent cross-cloud governance. 4) When deletion and lifecycle synchronization fidelity across multiple systems is a strict operational requirement without tolerance for edge-cases. Deletion and sync limitations have been reported in review platforms and community discussions. 5) When the organization lacks a mature patching and upgrade pipeline and is highly sensitive to operational risk from vulnerability remediation. Public vulnerability disclosures emphasize the need for rapid patching and tested upgrade workflows.

      Disqualifiers (poor fit)

      • Small teams seeking a lightweight secrets manager without dedicated security operations,
      • organizations seeking transparent self-serve pricing and minimal adoption ceremony.

      Publicly discussed limitations and friction points

      • Initial bootstrap identity material remains a practical requirement; some practitioners argue that an initial secret or credential must exist somewhere to establish trust.
      • Deletion and lifecycle synchronization gaps have been reported in some sync scenarios.
      • Integration maturity across some product components has been described as uneven in community discussions.

      Security vulnerabilities (material risk to track)

      • Public disclosures in the research period cite multiple CVEs affecting Conjur open source and self-hosted components, including issues with remote code execution and authentication bypass in unpatched systems.

      Roadmap and packaging transition risk

      • Product renaming and SKU changes can create confusion in procurement, documentation, and entitlement mapping.
      • Post-acquisition integration into a larger vendor platform may lead to bundling or product-line rationalization; buyers should verify long-term SKU stability and roadmap commitments.

      02Why they buy

      Differentiators with evidence

      - Multiple deployment models: offering SaaS, self-hosted, and open-source editions supports different operating models across organizational maturity levels. - Secrets Hub approach: provides governance and rotation across CSP-native secret stores while aiming to preserve developer workflows rather than forcing centralization into a single vault. - Evidence of enterprise scale: customer quotes and case studies reference high secret call volumes and rotation activity, which signal enterprise usage patterns.

      Where competitors have advantages

      • Developer mindshare and ecosystem: alternatives may be more commonly integrated into DevOps toolchains and community resources.
      • Simplicity: some administrators report that certain competitors are simpler to run with fewer dedicated staff.
      • Single-cloud simplicity and cost: cloud-native secret stores can be lower friction for single-cloud workloads.

      03Field reports

      Note: a Gartner Peer Insights page exists for Conjur Secrets Manager Enterprise; full review text may be gated. Review platforms referenced in the research set include G2, TrustRadius, PeerSpot, and Gartner Peer Insights.

      Review platform sentiment (G2)

      G2 displayed an aggregate rating for Conjur in the captured data with generally positive comments on usability and documentation, alongside user-reported deployment complexity and some functional limitations. Representative user statements included both positive and negative experiences.

      Review platform sentiment (TrustRadius)

      TrustRadius entries in the dataset indicated generally positive scores for the product with some variability across specific deployment experiences.

      PeerSpot / other review aggregators

      PeerSpot commentary emphasizes security and scalability while noting relatively higher cost in some comparisons.

      Community/Social feedback (Reddit)

      Reddit threads show more polarized views than structured review platforms. Common positive themes include suitability where secrets conform to predictable patterns and the availability of enterprise controls. Common negative themes include perceived complexity, integration friction, surprise dependencies or bundling, and the need for specialized administration.

      Hacker News discussions

      A targeted search for Conjur/CyberArk on Hacker News did not surface a strong, directly relevant discussion in the accessible outputs; community coverage is therefore uneven across public forums.

      Reasons organizations select CyberArk (inferred from sources)

      Organizations appear to select CyberArk Secrets Management when prioritizing:

      • enterprise policy and audit rigor across hybrid estates,
      • integration with existing privileged access management and identity ecosystems,
      • central rotation and control while aiming to preserve cloud-native workflows via overlays such as Secrets Hub.

      Why some customers leave or avoid (churn risks)

      Common churn drivers identified or implied in community feedback include:

      • perceived higher cost compared with cloud-native or simpler tools,
      • complexity and maintenance overhead associated with multi-component architectures,
      • mismatches between DevOps expectations and enterprise PAM processes that affect developer adoption.

      Case study: North American insurance company (OpenShift)

      CyberArk describes an insurer using Secrets Manager for OpenShift containerized applications, reporting outcomes such as elimination of initial secret bootstrap problems, reduced development-cycle effort, and support for a large volume of secret retrievals during migration. Critical evaluation: these metrics are vendor-published; methodology and baselines are not independently audited in the accessible material. Important clarifications for buyers include what counts as a "secret" (fetch calls versus distinct secret objects), how high-frequency retrieval claims were measured, and the infrastructure footprint that supported the reported scale.

      Case study: Cisco (secrets volume)

      Vendor materials include a customer quote referencing a large number of secret retrievals and rotation activity.

      Critical evaluation: the quote signals scale but is marketing-selected and does not disclose architecture, costs, or operational staffing required to achieve the results.

      Case study: TIAA (financial services)

      A vendor case study references Conjur Secrets Manager as part of a broader portfolio deployment supporting organization-wide needs.

      Critical evaluation: in portfolio deployments, it can be difficult to attribute outcomes specifically to Secrets Management versus adjacent components.

      04Best fit

      Company sizes

      Best fit tends to be large enterprises (typically thousands of employees) with many applications and non-human identities, and regulated organizations with audit and least-privilege requirements.

      Industries

      Evidence and examples in the sources include insurance, financial services, and large technology/enterprise environments.

      Roles/personas

      • Security/IAM/PAM program owners,
      • DevSecOps leaders,
      • Platform engineering and SRE teams,
      • Compliance and audit stakeholders.

      Pain points addressed

      • Hard-coded secrets in code and pipelines,
      • vault sprawl and lack of visibility across cloud provider secret stores,
      • the need for rotation policies and centralized audit trails.

      05The pitch

      What the product does (objective core value)

      CyberArk Secrets Management is a set of products and deployment models aimed at securing non-human identities (applications, CI/CD jobs, scripts, automation, containers, cloud workloads) by centrally storing, brokering, rotating, and auditing access to secrets (passwords, API keys, tokens, certificates) across hybrid and multi-cloud environments. CyberArk’s current packaging includes: - Secrets Manager, SaaS (formerly Conjur Cloud Secrets Manager) for managed SaaS secrets management - Secrets Manager, Self-Hosted (formerly Conjur Secrets Manager Enterprise) for on-prem/self-managed deployments - Conjur Open Source for open-source adoption/POCs (with trade-offs versus enterprise editions) - Secrets Hub for central visibility/rotation/policy across cloud-native secret stores (AWS Secrets Manager, Azure Key Vault, Google Secret Manager), and discovery for HashiCorp Vault

      Target market and positioning

      Positioned for large and regulated enterprises and security-led identity programs that require: - centralized governance and auditability, - integration with a broader privileged access management and identity security platform, - high scale (large secret volumes, many applications and teams), - options for both SaaS and self-hosted deployments. CyberArk’s messaging frames secrets management as part of machine identity and non-human identity security.

      Get a comprehensive analysis of CyberArk Secrets Management including market position, competitive landscape, adoption trends, and peer benchmarks.

      Download full report →
      1. When a low-complexity, developer-led rollout with minimal platform overhead is the primary requirement. Community posts describe CyberArk/Conjur as having multiple components and higher operational complexity.

      2. When the organization will not fund specialized administration or partner services. Several users report reliance on partners or professional services for deployment and ongoing operations.

      3. When the deployment is primarily single-cloud and CSP-native controls are acceptable. Cloud provider secret stores may meet requirements without an additional platform layer, although they may not provide consistent cross-cloud governance.

      4. When deletion and lifecycle synchronization fidelity across multiple systems is a strict operational requirement without tolerance for edge-cases. Deletion and sync limitations have been reported in review platforms and community discussions.

      5. When the organization lacks a mature patching and upgrade pipeline and is highly sensitive to operational risk from vulnerability remediation. Public vulnerability disclosures emphasize the need for rapid patching and tested upgrade workflows.

      • Multiple deployment models: offering SaaS, self-hosted, and open-source editions supports different operating models across organizational maturity levels.
      • Secrets Hub approach: provides governance and rotation across CSP-native secret stores while aiming to preserve developer workflows rather than forcing centralization into a single vault.
      • Evidence of enterprise scale: customer quotes and case studies reference high secret call volumes and rotation activity, which signal enterprise usage patterns.

      CyberArk describes an insurer using Secrets Manager for OpenShift containerized applications, reporting outcomes such as elimination of initial secret bootstrap problems, reduced development-cycle effort, and support for a large volume of secret retrievals during migration.

      Critical evaluation: these metrics are vendor-published; methodology and baselines are not independently audited in the accessible material. Important clarifications for buyers include what counts as a "secret" (fetch calls versus distinct secret objects), how high-frequency retrieval claims were measured, and the infrastructure footprint that supported the reported scale.

      CyberArk Secrets Management is a set of products and deployment models aimed at securing non-human identities (applications, CI/CD jobs, scripts, automation, containers, cloud workloads) by centrally storing, brokering, rotating, and auditing access to secrets (passwords, API keys, tokens, certificates) across hybrid and multi-cloud environments.

      CyberArk’s current packaging includes:

      • Secrets Manager, SaaS (formerly Conjur Cloud Secrets Manager) for managed SaaS secrets management
      • Secrets Manager, Self-Hosted (formerly Conjur Secrets Manager Enterprise) for on-prem/self-managed deployments
      • Conjur Open Source for open-source adoption/POCs (with trade-offs versus enterprise editions)
      • Secrets Hub for central visibility/rotation/policy across cloud-native secret stores (AWS Secrets Manager, Azure Key Vault, Google Secret Manager), and discovery for HashiCorp Vault

      Positioned for large and regulated enterprises and security-led identity programs that require:

      • centralized governance and auditability,
      • integration with a broader privileged access management and identity security platform,
      • high scale (large secret volumes, many applications and teams),
      • options for both SaaS and self-hosted deployments.

      CyberArk’s messaging frames secrets management as part of machine identity and non-human identity security.