Join our Newsletter — 33% off our NHI Course
Home› Guides› Akeyless, Doppler and 1Password: Securing How Machines Access…
Guide Secrets Management

Akeyless, Doppler and 1Password: Securing How Machines Access Your Secrets Manager

PDF for newsletter subscribers · free to read online

← All guides
By NHI Mgmt Group, edited by Lalit Choda Updated 8 November 2026 13 min read
On this page

Akeyless, Doppler and 1Password all protect your other credentials, but every application that reads from them first has to get in, and whatever it uses to get in is the most valuable secret in the stack. In many organisations that entry credential is a long-lived token sitting in a CI variable, a Kubernetes secret or a .env file, with no expiry and read access to a whole project or vault. This guide looks at how machines get into each of the three products, what each machine credential can reach, how to move from stored tokens to workload identity, and how to scope, administer, log and clean up that access. The same model applies to other managers such as Infisical. It is for platform, DevOps and security engineers who run these tools. For the underlying problem see the Secrets Zero Problem Guide, and for the wider discipline the Secrets Management Guide.

Platforms are listed alphabetically throughout; the order is not a ranking.

Key takeaways

  • The entry credential decides the blast radius. Whatever a machine presents to Akeyless, Doppler or 1Password can read everything its role, config or vault grant allows, so scope that grant before worrying about anything else.
  • The three products start from different places. Akeyless is built around identity based auth methods (cloud IAM, Kubernetes, OAuth2.0/JWT, certificates) with access keys as one option; Doppler offers stored service tokens plus OIDC federated service account identities; 1Password service accounts use a stored token that itself carries decryption keys.
  • Stored keys are the fallback, not the default. Akeyless says its API key method is not recommended for production; Doppler advises against personal and CLI tokens in live environments; 1Password lets you rotate a service account token with a delayed expiry for the old one. Prefer workload identity where the platform supports it.
  • Permissions follow different shapes. Akeyless binds auth methods to access roles with path rules and an overriding deny; Doppler binds a service token to one config and a service account to workplace and project roles; 1Password fixes a service account's vaults and permissions at creation.
  • Logs only help if someone reads them. All three expose activity data you can export to a SIEM or reporting tool. Alert on new credentials, unusual sources and bulk reads.

Three access models side by side

AspectAkeylessDoppler1Password
How a machine gets inAn authentication method (AWS IAM, Azure AD, GCP, OCI, Kubernetes, certificate, OAuth2.0/JWT, Universal Identity, API key, Kerberos) returns a temporary Akeyless tokenA service token (one config), a service account token, or a service account identity that swaps an OIDC token for a short-lived Doppler tokenA service account token (ops_ prefix) supplied as OP_SERVICE_ACCOUNT_TOKEN, or an access token to a self-hosted Connect server
Stored secret needed?Not for cloud IAM, Kubernetes or certificate methods; yes for API keys (Access ID and Access Key)Yes for service tokens and service account tokens; no for service account identitiesA service account token is used; set an expiry and rotate it
Where permissions liveAccess roles attached to the auth method, with path rulesService token: one config; service account: workplace role plus per project role and environmentsPer vault read, write and share permissions chosen at creation
Default accessNone until a role grants itService token read-only, write optional; new service account has no workplace role and no project accessOnly the vaults granted at creation
Lifetime and network controlsMinimum, default and maximum token TTL, per method expiration date and allowed client IPsOptional token expiry; ephemeral service tokens with CLI --max-age; short-lived OIDC tokens; per config Trusted IPsOptional expiry, for example --expires-in 24h; rotation with a delayed expiry for the old token

What each machine credential can reach

  • Akeyless: exactly what the access roles bound to its auth method grant. Rules target paths (exact items, prefixes and single segments) with list, read, create, update, delete and deny capabilities, and deny overrides any other permission. Roles can also be scoped by sub-claims, such as a Kubernetes namespace, so one auth method can serve several workloads with different reach. Deeper rule design is in the planned Akeyless Security Guide.
  • Doppler: a service token reaches one config in one project. A service account reaches every project it has been added to, with a role and environments set per project, and can hold several tokens. Where roles combine, the highest permission applies. Personal (dp.pt.) and CLI (dp.ct.) tokens reach everything their creator can, including write access.
  • 1Password: the vaults granted at creation, with read, write or share permission per vault (write and share both require read), plus read-only access to any Environments granted. Service accounts cannot reach Personal, Private, Employee or the default Shared vault and cannot manage users. Because the token contains the Account Unlock Key and keyset, holding it is enough to decrypt those vaults.

Write down, per credential, the answer to "what could someone read with this today?". If that list includes production and non-production, or more than one application, the credential is too broad. See the Least Privilege Techniques Guide.

Moving from stored tokens to workload identity

The goal on every platform is the same: let the workload prove who it is with something it already has, such as a cloud role, a Kubernetes service account or a CI OIDC token, instead of a secret someone pasted into a variable. The general patterns are in the Workload Identity Federation Guide; this section covers what each product offers.

Akeyless

  • Cloud IAM, Kubernetes, OAuth2.0/JWT and certificate methods let a workload authenticate with an identity it already holds and receive a temporary Akeyless token. For Kubernetes, the Gateway reviews the pod's service account JWT and, per Akeyless, the JWT is never shared with Akeyless itself; enforce namespace and service account name claims in the role association.
  • The Gateway is a customer hosted, stateless service that receives application requests, enforces local access rules, caches locally and forwards logs, reaching Akeyless SaaS over outbound connections only.
  • Access keys are shown once and can be reset. Akeyless describes the API key method as not recommended for production, so treat any you find on a server as a migration item.

Doppler

  • Service account identities accept OIDC tokens from GitHub, GitLab, CircleCI, AWS IAM outbound identity federation or a custom discovery URL. Audience and subject are required; add claims and avoid wildcards. doppler oidc login or the OIDC auth API returns a short-lived token with expires_at; do not persist it.
  • Trusted IPs limit which source ranges can reach a config's API endpoints. New configs start open at 0.0.0.0/0, so replace that with your CI and runtime ranges.
  • Where a stored token remains, use a service token per config and consumer with an expiry, or ephemeral tokens with --max-age for jobs.

1Password

  • Service accounts always use a stored token, so the work is to contain it: short expiry, one service account per workload, exposure only as OP_SERVICE_ACCOUNT_TOKEN in the process that needs it, and delivery through a platform secret store that itself uses workload identity.
  • Connect servers are self-hosted in your own infrastructure, cache secrets locally and serve them to your applications over a private REST API, so only your services reach them.
  • Rate limits apply per token per hour and per account per day, which caps how fast a stolen service account token can be used for bulk export.

Pilot on one CI pipeline or cluster, confirm secrets still load, keep the old credential with a short expiry for one release cycle, then delete it.

Availability

  • Akeyless: the fetched documentation for auth methods, roles, Gateway and audit logs does not state plan limits for these features.
  • Doppler: service accounts, service account identities and Trusted IPs are on Team and Enterprise plans; custom roles are standard on Enterprise and can be added to Team; activity log streaming to Splunk is Enterprise only.
  • 1Password: hourly and daily service account rate limits differ by plan (on Business, 10,000 reads and 1,000 writes per token per hour and 50,000 per account per day); the Events API needs a Business account; service account management settings apply to Teams and Business.

Scoping by environment and least privilege

NeedAkeylessDoppler1Password
One app, one environment, read onlyRole with read on that app's production path only, bound to its auth method and sub-claimsRead-only service token on that config, with expiryService account with read on one vault
Separating productionSeparate path tree, with deny rules protecting production items from broad rolesProject roles scoped to environments, so non-production roles do not include productionDedicated production vault, other service accounts not granted it
Writes or rotation automationSeparate role with create and update on the narrowest pathSeparate service account with a write role on one projectSeparate service account with write on one vault
Changing scope laterEdit the role rulesChange project roles and environmentsVaults and permissions cannot be changed after creation; create a new service account

That last row drives behaviour. Where scope is fixed, teams tend to reuse an older, broader credential rather than create a new one, so make creation easy. Where scope is easy to edit, role changes need review. See the OWASP NHI Top 10 NHI8 Environment Isolation Guide.

Admin roles and privileged access

  • Akeyless: whoever can create auth methods or edit access roles can mint access. Non-admins cannot grant capabilities beyond their own effective permissions, and deny rules that apply to a non-admin creator are copied into roles they create.
  • Doppler: creating service accounts needs the Admin role or the Manage Service Accounts permission, and only workplace Admins manage Trusted IPs. Custom workplace and project roles let you narrow both; remove personal and CLI tokens from automation.
  • 1Password: users need permission from an administrator to create service accounts, creators can only grant vaults they can access, and a vault can be set to refuse service accounts entirely.

Audit logging and detection

  • Akeyless audit logs record nearly every action, with time, action, status, client and source IP, and can be forwarded raw to tools such as Splunk. Add audit log sub-claims on an auth method so entries name the actual workload.
  • Doppler activity logs record team actions and secret changes, with commit style config logs that can be rolled back, and can be streamed as JSON to a Splunk HTTP Event Collector. Token prefixes (dp.st., dp.sa., dp.said. and others) exist to help secret scanning.
  • 1Password gives each service account an item usage report showing which vaults it used, when items were last accessed and what action was taken, and the Events API exposes up to 120 days of event data for external reporting tools.

Scanner coverage differs: GitHub's partner programme covers six Doppler token types with push protection and validity checks, while 1Password service account tokens are detected only in private repositories with Advanced Security, without validity checks. Default Gitleaks rules match Doppler dp.pt. tokens and 1Password ops_ tokens, so add custom rules for other Doppler types. Coverage was checked on 27 October 2026. Across all three, alert on new credentials or auth methods for production scope, use from source IPs outside your CI and runtime ranges, a read credential suddenly listing everything, human tokens used from servers, and credentials unused for 90 days. The Secrets Access Logging and Detection guide covers the pipeline in depth.

If a credential leaks

Revoke or reset the credential, then rotate every secret it could read, because the attacker may already have copied them. In Akeyless, reset the access key; in Doppler, revoke the token and clear CLI fallback files that can still hold last fetched secrets; in 1Password, revoke the token, which removes vault access immediately. Platform specific steps are in the Akeyless Security Guide, the Doppler Security Guide and the 1Password Security Guide. The 230 Million AWS Cloud Environments Campaign 2024 shows where stored tokens of any kind leak in practice: publicly reachable .env files.

Common misconfigurations

  • Akeyless access keys in production when a cloud IAM, Kubernetes or certificate method would remove the stored secret.
  • Akeyless roles without sub-claim checks, so any pod or principal that passes the auth method gets the same reach.
  • A Doppler personal or CLI token in production, inheriting its owner's write access.
  • Doppler configs left on the default 0.0.0.0/0 Trusted IPs range, or OIDC identities with wildcard subjects.
  • One 1Password service account for every app, which nobody can revoke without breaking all of them.
  • 1Password service accounts given write or share when read is enough, which cannot be narrowed later without a new account.
  • Tokens with no expiry on any platform.
  • Audit and activity logs never forwarded or reviewed, so a bulk read goes unseen.

Practitioner checklist

  • Inventory every Akeyless auth method, Doppler token and service account, and 1Password service account, with owner, workload, scope, expiry and last use. See the Service Account Inventory Template.
  • Move Akeyless workloads to cloud IAM, Kubernetes or certificate methods and retire production access keys.
  • Move Doppler CI and cloud workloads to service account identities with strict audience and subject, and set Trusted IPs.
  • Give every 1Password service account one workload, a short expiry, the fewest vaults and read only where possible.
  • Separate production paths, environments and vaults from everything else.
  • Review who can create auth methods, roles, service accounts and tokens.
  • Forward audit logs, activity logs and events to your SIEM, and alert on new credentials and bulk reads.
  • Add scanner rules for dp.st., dp.sa. and ops_ and enable push protection.
  • Rehearse revocation and rotation for one credential on each platform.

Standards and references

Related NHI Mgmt Group resources: Akeyless Security Guide · Doppler Security Guide · 1Password Security Guide · Secrets Management Guide · Secrets Zero Problem Guide · Cloud Secrets Managers Guide · Kubernetes Secrets Security Guide

PDF for subscribers

Take this guide with you

Every section, table and checklist in one PDF, with links to the sources and related guides. Subscribe to our weekly NHI & AI Identity Journal and we’ll email you a download link.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Researched and written by the NHI Mgmt Group editorial team using AI tools, under the editorial direction of Lalit Choda. Facts are drawn from the sources listed on this page and checked by our automated quality process. Last updated 8 November 2026. Spotted an error? Use our contact page.
NHI Mgmt Group, the independent authority on Non-Human Identity, IAM and Agentic AI security. nhimg.org

PDF Downloads for Newsletter Subscribers

Get the guide

Enter your details and we’ll email you a download link.

The full guide is free to read online. The PDF is a thank you for subscribing.

Fill in all fields marked * and tick the PDF box to continue.