Client secrets and credentials: secure access without sharing passwords

Published on 2026-11-14 by frfrand

Key management, rotation, permissions, and revocation across teams and projects.

Client secrets and credentials: secure access without sharing passwords

The problem isn't remembering passwords: it's controlling who accesses what

An agency or technical team usually manages SSH keys, API tokens, DNS access, database credentials, and client payment accounts. Sharing everything via chat or reusing an administrator password turns an isolated mistake into a problem for multiple projects.

An inventory by client and by purpose

Record each secret with its owner, system, purpose, creation date, review date, and revocation procedure. Do not copy its value into the inventory: store that value in a vault with encryption, auditing, and access control.

The essential distinction is between human identity and service credential. A person should have a nominative account that can be deactivated; an integration should have its own technical identity, minimum permissions, and independent lifecycle. Avoid shared administrator accounts when the provider allows delegation.

Principle of least privilege

A technician who maintains a website does not need access to the billing system or to all company servers. A pipeline that deploys an API does not need permissions to delete the database. Segment permissions by environment, client, and task; require MFA where possible and review access at the end of each project.

For automated deployments, prioritize short-lived identities or OIDC-compatible federation. If you use secrets stored in GitHub Actions, check the scope of each environment and which workflows can run them. Never place keys in a repository, in the frontend, in a published Docker image, or in logs.

Onboarding, rotation, and offboarding process

When a collaborator joins, request named permissions and document their scope. When a key changes, first identify the consumers, create the new one, update dependencies, validate its operation, and revoke the previous one. When the collaboration ends, disable identities, tokens, SSH, and active sessions according to the system.

Rotation is not simply changing the text in a file. An encryption or signing secret can affect sessions or historical data. Design temporal compatibility when necessary and document the recovery plan.

Response to a leak

Treat an exposed credential as potentially compromised. Revoke it, investigate where it was used, review logs and permissions, replace derived secrets if applicable, and analyze the scope. Removing it from the last commit does not erase it from history nor guarantee that third parties have not copied it.

Minimum model for a small agency

Use a corporate vault with folders per client, permission groups, MFA, access auditing, and recovery. Reserve emergency credentials under controlled procedures. In Linux environments, combine non-privileged accounts, per-person SSH keys, and adjusted sudo policies.

You can complement this guide with GitHub Actions secrets and how to avoid uploading secrets to GitHub. ArduMaker offers infrastructure and deployment tools; evaluate the necessary permission capabilities before centralizing client credentials.

Frequently asked questions

### Can I store keys in environment variables? They are useful for configuration injection, but they do not replace a secrets store nor guarantee protection against privileged processes. ### Does each client need their own key? Yes, whenever the integration allows it, to limit incidents. ### How often should they be rotated? According to sensitivity, duration, provider, and exposure; rotate immediately upon suspicion of leakage.

Technical reference: OWASP Secrets Management Cheat Sheet.

  • seguridad
  • DevOps
  • credenciales
  • GitHub
  • clientes

Keep reading

All articles · VPS plans