Technical Review by
Craig MacAlpine
Legit Security protects your software supply chain by hunting down exposed secrets across your entire development ecosystem
Akeyless is a SaaS-native secrets management platform built for DevOps teams who need centralized control over credentials, certificates, and encryption keys
AWS Secrets Manager is Amazon’s native secrets management service for teams already invested in the AWS ecosystem
Secrets management separates mature DevSecOps practices from teams that hardcode credentials and rotate them manually. But the market spans wildly different approaches. Some platforms assume you want zero infrastructure overhead. Others prioritize encryption-at-rest with dedicated appliances. Still others focus on integration range across cloud platforms and CI/CD systems.
Choosing wrong means either vendor lock-in, security gaps when integrations fail, or operational overhead that becomes another team headache. You need secrets management that secures credentials without creating friction for developers or impossible maintenance burden for ops teams.
We evaluated multiple secrets management platforms across cloud-native, hybrid, and on-premises environments, evaluating secret type support, automation capabilities, integration depth, deployment models, and ease of integration into existing DevSecOps pipelines. We reviewed customer deployment experiences to identify where vendor promises about ease diverge from actual complexity.
This guide walks you through the trade-offs that matter for your specific infrastructure, security requirements, and team’s operational capacity.
We reviewed 11 products and selected the top performers for different use cases.
Legit Security protects your software supply chain by hunting down exposed secrets across your entire development ecosystem. It goes beyond source code scanning to cover CI/CD pipelines, build logs, ticketing systems, and collaboration tools like Slack and Confluence.
We found the scanning scope impressive. Most secrets scanners stop at repositories. Legit extends into Jenkins pipelines, Jira tickets, and even developers’ personal GitHub accounts. That range matters when credentials leak through unexpected channels.
The AI-powered prioritization reduces noise significantly. It analyzes whether secrets are valid, where they’re exposed, and what business impact they carry. We saw claims of up to 90% fewer false positives through integrations with GitHub, GitLab, and CrowdStrike.
Customers praise the DevOps integrations and the ability to prioritize vulnerabilities from code to cloud. Several highlight early insights into AI-related security risks before competitors offered similar visibility.
If you’re running complex DevSecOps environments in finance or healthcare, we think Legit deserves serious consideration. The compliance coverage for GDPR, PCI DSS, and NIST aligns with regulated industries.
API-based deployment takes minutes, not weeks. For smaller teams with simpler pipelines, the full supply chain approach might be more than you need. But if secrets exposure across distributed development workflows keeps you up at night, this addresses that problem directly.
Customer feedback highlights Intuitive UI with strong self-hosted GitLab integration for developer adoption. Ai-powered prioritization validates secrets and reduces false positive noise. Responsive support team with regular sync meetings and quick turnaround.
Some reviews indicate that documentation lacks detail, especially for Kubernetes integration scenarios, however.
Customer feedback highlights Strong encryption with TLS in transit and AES-256 at rest. Native integration with google cloud identity for role-based access control. Automated credential rotation without manual intervention or productivity impact.
Some users note that secret format and application integration can feel unintuitive, however.
Users value Dynamic secrets with automatic revocation eliminate stale credential risk. Open-source option with active community building extended tooling. Broad identity integrations including aws, azure, google cloud, okta, and ping.
Some reviews indicate that documentation quality inconsistent, especially for specific integrations like Keycloak, however.
Customers consistently praise Tight integration with Azure DevOps Pipelines and GitHub Actions workflows. Role-based access control through azure’s native identity framework. Expiry date feature supports automated credential rotation policies.
Some users note that initial setup for private access configurations can be tricky, however.
Akeyless is a SaaS-native secrets management platform built for DevOps teams who need centralized control over credentials, certificates, and encryption keys. It consolidates secrets management, remote access, and certificate lifecycle management into a single platform.
We found the range of supported secret types practical. SSH keys, API credentials, database passwords, PKI certificates, and encryption keys all live in one place. Timed secrets and automated certificate rotation reduce manual overhead for teams managing large credential estates.
The zero-deployment model stands out. There’s no infrastructure to maintain. Akeyless handles backup and disaster recovery, which removes operational burden from your team. For organizations tired of managing on-prem vault infrastructure, that trade-off has real appeal.
Integrations with Okta, AWS IAM, and Azure AD enable smooth authentication. Admins can automatically push secrets into the vault and enforce least privilege access at granular levels. Detailed audit logs capture all user activity for compliance reporting.
The analytics and SIEM integration give visibility into your secrets posture. If you’re dealing with GDPR, SOC 2, or similar requirements, the compliance tooling addresses those needs directly.
Customers appreciate the unified approach and clear product vision. The maintenance-free model resonates with smaller teams lacking dedicated infrastructure staff.
AWS Secrets Manager is Amazon’s native secrets management service for teams already invested in the AWS ecosystem. It handles database credentials, API keys, and other sensitive data with automatic rotation and API-based retrieval.
We found the integration story compelling if you’re running AWS workloads. Amazon RDS, Redshift, and DocumentDB credentials rotate automatically without IT involvement. That eliminates stagnant credentials, one of the more common attack vectors in cloud environments.
The API-based retrieval model means secrets never get hardcoded in plain text. Applications pull current credentials at runtime. This approach keeps secrets fresh and reduces breach risk from exposed configuration files.
IAM permission policies let you enforce context-aware access. You can restrict developers to accessing passwords only from within your corporate network. The flexibility here matches what enterprises expect from AWS.
All access gets logged through AWS CloudTrail. Admins can configure alerts for sensitive events like secret deletion. If you’re already using AWS security tooling, this fits naturally into existing workflows.
Customers highlight easy integration across AWS services. A few IAM permissions and you’re connected. The learning curve exists, but it’s manageable for teams familiar with AWS conventions.
CyberArk Conjur is an enterprise secrets management platform built for containerized applications and DevOps environments. It removes hardcoded secrets from code while supporting hybrid and multi-cloud deployments through flexible APIs.
We found the stability impressive. The platform runs rock solid when properly deployed. Auto-failover clustering keeps services available during infrastructure issues. For organizations where secrets management downtime isn’t an option, that reliability matters.
The integration range covers major DevOps tools and container orchestration platforms.
Conjur sits within CyberArk’s broader Identity Security platform alongside privileged access management and workforce identity tools. If you’re already a CyberArk customer, the unified approach simplifies vendor management and policy consistency.
Automatic credential rotation reduces unauthorized access risk. Full audit trails support compliance requirements. The reporting capabilities help teams demonstrate regulatory adherence during audits.
Customers praise the integrations and operational stability. However, the user interface draws consistent criticism. Several describe the experience as unpleasant enough to avoid when possible. The API for managing authentication tokens feels unintuitive and adds complexity.
Cycode is an AI-powered secrets management platform that scans source code, ticketing systems, documentation, and messaging tools for exposed credentials. It prioritizes risky secrets using pre-set rules and validates their status to reduce false positives.
We found the coverage practical. Cycode monitors SCM tools, CI/CD pipelines, and pull requests continuously. Hardcoded secrets get caught in IDEs before they hit production. That shift-left approach catches problems when they’re cheapest to fix.
The prioritization engine focuses developer time on what matters. Not every exposed secret carries equal risk. Cycode validates status and ranks exposures by criticality. Auto-remediation and streamlined ticketing accelerate the fix cycle without creating busywork.
The UI earns praise for being intuitive. Self-hosted GitLab integration works well. Customers highlight the responsive support team as a differentiator. Weekly syncs and quick inquiry turnaround make a real difference when rolling out new security tooling.
Documentation needs work, particularly around Kubernetes integration.
We think Cycode suits organizations wanting an intuitive secrets management solution that integrates into existing developer workflows. The feature range across DevSecOps and security scanning is impressive. If your team values vendor responsiveness and clean UX over API elegance, this delivers. Enterprises building heavy custom integrations should evaluate the API experience first.
Doppler is a cloud-based secrets manager that consolidates credentials and app configurations into a single platform. It targets DevOps teams tired of secrets scattered across multiple services, syncing everything to platforms like AWS, Azure, and GitHub.
We found the dashboard well-organized. Secrets group around projects, giving developers quick visibility into what they need. Creating projects feels straightforward. Importing files and syncing across platforms works without friction.
The native integrations cover essential ground. AWS, Azure, Cloudflare, and GitHub connections deploy secrets to production environments. For teams managing credentials across multiple cloud providers, that consolidation saves real time. The rollback feature adds safety when configuration changes go wrong.
Doppler handles team workflows well. Sharing secrets across team members happens without the usual spreadsheet chaos or insecure workarounds. Full audit logs track changes, showing who modified what and when. That visibility matters for both troubleshooting and compliance.
The free tier makes evaluation easy. Small teams can run production workloads without immediate cost pressure. Larger organizations will hit limits, particularly around subscriber counts, but the upgrade path is clear.
Customers praise the simplicity and data security. However, some report lag during uploads and downloads. Document handling can slow down workflows. This isn’t an instant messaging tool, but for teams needing snappy interactions, the performance may frustrate.
Google Cloud Secrets Manager provides centralized storage for API keys, passwords, and credentials within the GCP ecosystem. It offers encryption, access policies, and automated rotation for teams already running Google Cloud workloads.
We found the security posture solid. Data encrypts in transit with TLS and at rest with AES-256. Secret data is immutable once stored. You can pin aliases to secrets for additional access control granularity.
The platform handles core secrets management without overcomplicating things.
API integrations extend into GitHub and other platforms. For teams running GCP infrastructure, the native connections reduce friction. Secrets share across teams with user-level policies enforcing least privilege. Automated credential rotation keeps secrets fresh without manual intervention or productivity hits.
The central dashboard gives visibility into your secrets posture. Auditing and management policies help meet compliance requirements. Nothing significant here, just reliable execution on the fundamentals.
Customers describe it as easy to use and effective. No complicated scenarios where it falls short, but also no standout features beyond solid basics. Some find the secret format and application integration less intuitive than expected.
HashiCorp Vault is an industry-standard secrets manager available as both self-managed open-source and cloud-hosted options. It secures tokens, passwords, certificates, and encryption keys for DevOps teams across hybrid and multi-cloud environments.
We found the encryption model thoughtful. Vault encrypts secrets before writing to storage. Even if attackers reach raw storage, they get nothing usable. The platform can encrypt and decrypt data without storing it, useful for sensitive processing workflows.
Dynamic secrets generation sets Vault apart. One-time credentials auto-revoke after a set period. No stale passwords sitting around waiting to be compromised. For environments where credential hygiene matters, this capability reduces attack surface meaningfully.
Identity integrations cover the major platforms: AWS, Google Cloud, Azure, Okta, and Ping Identity. LDAP and OIDC connections work well. Terraform integration feels straightforward for infrastructure-as-code workflows. The open-source community builds additional tooling that extends functionality.
Automated credential rotation handles security hygiene without manual overhead. Access controls ensure only authorized users reach sensitive credentials. The flexibility supports multiple use cases beyond basic secrets storage.
Customers praise the community, security track record, and overall functionality. Long-term users report no security issues and describe it as top-tier. However, documentation quality varies. Some integrations, particularly Keycloak, lack clear guidance. Expect to piece together answers from community resources for edge cases.
Keeper Secrets Manager is a cloud-based platform for storing infrastructure secrets, API keys, certificates, and access credentials. It extends Keeper’s enterprise password management into DevOps workflows with cross-platform access and team sharing.
We found the multi-platform approach practical. Web portal, browser extension, desktop app, mobile app. Each user manages unlimited secrets in their private vault. SAML 2.0 passwordless authentication or master password options give flexibility on access methods.
The fully cloud-based model means no hosted software, no complex deployments, no new infrastructure to maintain. The always-on API lets teams access vaults securely from any device. For organizations wanting to skip infrastructure management entirely, that simplicity has value.
Secrets share across teams through Microsoft Teams and Slack integrations. CI/CD system integrations cover popular platforms, with support for major programming languages and machine types. Central admin console handles enforcement policies, user provisioning, and audit reporting.
Customers praise the simplicity and central administration. Long-term users describe it as effective with a strong toolset. However, deployment can feel cumbersome given the extensive options and settings. The taskbar app occasionally causes login conflicts with the main client.
We think Keeper Secrets Manager fits best for organizations already using Keeper’s password management. The native integration creates a unified credential platform. Teams wanting that ecosystem benefit will find real value here.
Azure Key Vault is Microsoft’s native secrets management solution for storing cryptographic keys, certificates, and credentials. It supports both standard vaults and managed hardware security module pools for teams with stricter compliance requirements.
We found the Azure ecosystem integration straightforward. Azure DevOps Pipelines and GitHub Actions retrieve secrets without complex configuration. For teams already running Azure workloads, the connection points exist where you need them.
Role-based access control ties into Azure’s identity framework. Only authorized users push and retrieve secrets. The expiry date feature lets credentials auto-expire at defined periods, helping enforce rotation policies without manual tracking.
TLS encryption protects data in transit and at rest. Keys stay safeguarded by Azure using standard algorithms, key lengths, and hardware security models. You can import and manage your own keys while Azure handles operations when SaaS applications need access.
The single control interface appeals to security officers wanting centralized visibility. Anyone with an Azure subscription can create and use key vaults, lowering the barrier for teams starting their secrets management journey.
Customers praise ease of use and tight integration with Azure and third-party apps. Secrets, certificates, API keys, and passwords stay secure with minimal friction during daily operations.
Pulumi ESC combines secrets management with configuration orchestration, giving teams centralized control over credentials, API keys, and infrastructure settings. It works standalone, with Pulumi Cloud, or alongside Pulumi Infrastructure-as-Code.
We found the configuration-plus-secrets approach distinctive. This isn’t just credential storage. It centralizes environment configuration and pulls secrets from multiple sources including 1Password, HashiCorp Vault, AWS Secrets Manager, and Google Secret Manager.
Composable environments let you import configurations into one another. Shared secrets and settings inherit across projects without duplication. Hierarchical configuration organization handles complex variable sets as infrastructure grows. For teams managing sprawling cloud environments, that structure reduces chaos.
Access works through CLI, API, Kubernetes operator, Pulumi Cloud UI, or in-code SDKs for TypeScript, Python, and Go. The VS Code extension makes adding secrets or editing configuration entries fast. All changes get logged and versioned, simplifying rollbacks.
Dynamic secrets connect ESC to cloud providers and secrets stores to generate just-in-time credentials. Short-lived tokens via OpenID Connect reduce standing credential risk. Combined with Pulumi IaC, stack configuration becomes straightforward environment imports.
Customers praise the flexibility, scalability, and ecosystem integration. The tool grows with project needs. However, the learning curve exists, even for teams familiar with Pulumi. OpenID Connect configuration for short-lived tokens could be easier.
When evaluating secrets management platforms, we’ve identified seven critical criteria. Here’s what you should be asking:
Weight these criteria based on your environment. If you’re AWS-centric, native integration reduces complexity. For teams with strict compliance requirements, audit capabilities become non-negotiable. Organizations managing multi-cloud deployments should prioritize integration range and flexibility over platform-specific features.
Expert Insights is an independent editorial team that researches, tests, and reviews cybersecurity and IT solutions. No vendor can pay to influence our review of their products. Our Editor’s Scores are based solely on product quality. Before testing, we map the full vendor landscape for each category, identifying all active vendors from market leaders to emerging challengers.
We evaluated 13 secrets management platforms across cloud-native, hybrid, and on-premises deployments, assessing secret type support, credential rotation capabilities, integration range across cloud providers and CI/CD systems, deployment flexibility, and developer experience. Each platform was tested with real-world secret storage and retrieval scenarios, integration with common DevOps tools, and configuration of access controls.
Beyond hands-on testing, we conducted extensive market research across the secrets management landscape and reviewed deployment experiences and customer feedback to validate vendor claims against actual implementation complexity. We spoke with product teams to understand architectural decisions and roadmap priorities. Our editorial and commercial teams operate independently. No vendor can pay to influence our review of their products.
This guide is updated quarterly. For full details on our evaluation process, visit our How We Test & Review Products.
Secrets management eliminates a critical vulnerability class only if your team actually uses the platform and it integrates cleanly with your infrastructure.
For AWS-native teams, AWS Secrets Manager integrates tightly with RDS, Redshift, and DocumentDB for automatic rotation. Pay-as-you-go pricing keeps overhead minimal. If you need beyond AWS or want more secret type flexibility, consider alternatives.
For enterprises wanting uncompromising security architecture, HashiCorp Vault delivers encryption before storage write and dynamic credential generation.
For DevSecOps teams prioritizing simplicity, Doppler offers straightforward consolidation with minimal configuration. The free tier, clean UI, and native integrations make adoption frictionless. Performance trade-offs emerge at scale.
For cloud-native teams wanting zero infrastructure overhead, Akeyless handles backup and disaster recovery without operational burden.
For teams managing multi-cloud environments, Pulumi ESC unifies secrets management and configuration orchestration. It pulls secrets from 1Password, Vault, AWS Secrets Manager, and Google Secret Manager, reducing integration work across platforms.
Read the individual reviews above to dig into deployment details, secret type support, and integration specifics for your infrastructure.
Secrets Management is a term used in DevOps process to refer to the management of “secrets,” which can include digital authentication credentials such as passwords, APIs, tokens, certificates and keys used for accessing applications, accounts services and more.
Using a Secrets Management solution ensures that these critical secrets can only be accessed by authenticated users, by storing them in a secure, but easy to access vault, in much the same way a password manager works with passwords.
Role-based access controls, automated credential rotation and auditing features used to regulate access to these secrets and help reduce the risk of a data breach and ensure compliance with industry regulates that mandate data to be securely stored.
We asked Zane Bond, Director of Product Management at Keeper Security why it is so important for secrets to be stored in a secure secrets management solution:
“You hear this statistic all the time: 80% of breaches involve credentials in some way, shape or form. They are a high-value target for an attacker. But in general, the attacker is not trying to get your desktop password. That’s not the goal. The valuable information is in your environment––it could be your source code, it could be your customer lists, it could be where you store credit card information, it could be where you store all HR information or documents.
Those types of data are usually accessed exclusively by machines. So typically, the entry point [for an attack] will be a desktop or laptop, because somebody clicked on something. But after that, there’s going to be recon to figure out the environment and there’s going to lateral movement in your environment to get to the crown jewels.
Secrets management helps protect those most sensitive credentials. So that when somebody is spelunking around your network and doing recon, and they find an apache config file and they’re like, “Sweet, I’m on the web server, I found it!” there’s no password in there, so they can’t directly connect to the database. That’s why it’s so important to protect these secrets—they access your crown jewels.”
Joel is the Director of Content and a co-founder at Expert Insights; a rapidly growing media company focussed on covering cybersecurity solutions.
He’s an experienced journalist and editor with 8 years’ experience covering the cybersecurity space. He’s reviewed hundreds of cybersecurity solutions, interviewed hundreds of industry experts and produced dozens of industry reports read by thousands of CISOs and security professionals in topics like IAM, MFA, zero trust, email security, DevSecOps and more.
He also hosts the Expert Insights Podcast and co-writes the weekly newsletter, Decrypted. Joel is driven to share his team’s expertise with cybersecurity leaders to help them create more secure business foundations.
Craig MacAlpine is CEO and Founder of Expert Insights. Before founding Expert Insights in August 2018, Craig spent 10 years as CEO of EPA Cloud, an email security provider that rebranded as VIPRE Email Security following its acquisition by Ziff Davies, formerly J2Global (NASQAQ: ZD) in 2013.
Craig is a passionate security innovator with over 20 years of experience helping organizations to stay secure with cutting-edge information security and cybersecurity solutions.
Using his extensive experience in the email security industry, he founded Expert Insights with the singular goal of helping IT professionals and CISOs to cut through the noise and find the right cybersecurity solutions they need to protect their organizations.