CyberArk Secrets Hub
LeaderCyberArk is the global leader in identity security.
Est 1999|Valuation $20.6B|Raised $1.5B
Published May 16, 2026
Mainstream review platforms have extensive coverage for CyberArk PAM and CyberArk Secrets Manager/Conjur, but limited reviews explicitly identify Secrets Hub as a standalone product. This is common for newer add-on modules or platform extensions.
CyberArk product pages and partner materials include customer logos and testimonials that typically reference the broader Identity Security platform rather than Secrets Hub as a distinct product. These materials provide vendor-side descriptions and use cases but are not third-party validated references.
Public case studies referencing Secrets Hub specifically are limited. Most public customer stories reference platform-wide deployments (CyberArk Identity Security or Secrets Manager/Conjur) rather than Secrets Hub alone.
Sponsor-funded technical validations (e.g., vendor-paid analyst work) can be useful for architecture understanding but should not substitute for independent third-party references and customer reference calls.
Get a comprehensive analysis of CyberArk Secrets Hub including market position, competitive landscape, adoption trends, and peer benchmarks.
Download full report →"Secrets Hub … manages secrets in Cloud Service Provider secret stores, such as AWS Secrets Manager or Azure Key Vault, based on changes detected on the accounts/secrets in Privilege Cloud."
Community comments also note an operational nuance:
"Secrets Hub does NOT manage the rotation of accounts, it simply detects changes to an account in Privilege Cloud and makes sure it’s up to date in the related CSP secret store."
This indicates that rotation actions may depend on CyberArk PAM/CPM or other components, with Secrets Hub responsible for synchronization and governance visibility.
"When an account is deleted from a Safe, the corresponding secret is not deleted from the target."
This suggests organizations need explicit lifecycle governance or automation to avoid orphaned secrets in cloud-native stores.
Data formatting / integration friction: Community threads discuss formatting expectations (for example, whether synced secrets are base64 encoded), which can cause integration delays in CI/CD pipelines if not documented or configurable.
Broader CyberArk sentiment (commercial/UX concerns, not specific to Secrets Hub): Some administrator discussions cite concerns about overall platform cost and administrative complexity. While not Secrets Hub-specific, these perceptions can affect procurement and adoption decisions when Secrets Hub is bundled with other CyberArk offerings.
AWS partner material and vendor joint content describe architecture patterns in which Secrets Hub integrates with AWS Secrets Manager and is presented as being designed to avoid impacting production applications in the event of a Secrets Hub outage. Critical evaluation of such vendor- and partner-authored materials requires procurement validation:
CyberArk Secrets Hub is a SaaS governance layer that provides discovery, standardization, and enforcement of rotation and policy for secrets consumed from cloud-provider secret stores—primarily AWS Secrets Manager, Azure Key Vault, and Google Secret Manager—while allowing developer teams to continue using native store interfaces and APIs. The product also provides discovery and visibility for HashiCorp Vault usage to help address so-called vault sprawl.
In operational terms: Secrets Hub provides a single enterprise governance model (visibility, policy and rotation standards) while enabling continued use of cloud-native secret store interfaces/APIs.