How to Prevent Hard-Coded Secrets
Instead of writing a secret directly into the source code, you should define an alternative mechanism for obtaining the secret at the places where it is used, such as using environment variables or local files not under version control, or relaying to an external secret vault (aka secret manager). These are the most common options:
Environment Variables or Configuration files
Taking secrets from environment variables or configuration files works for any programming language and operating system.
Environment variables are not hard-coded, but they should be given the value somewhere. Application code and scripts may read the environment variable, but environment variables must be set before the application or script runs.
With local files, you may need to enforce that the exclude patterns in .gitignore or .dockerignore configurations are properly excluding the secret-holding files
A popular way to setup environment variables is to load them from an .env file, but remember: that file should never be under version control.
The following are examples for how to get a secret from .env file for each ecosystem. Replace the name of the environment variable SECRET_VAR and <path> to the .env file accordingly.
See dotenv for full details.
See dotenv-java for full details.
See GoDotEnv for full details.
See dotenv.net for full details.
Using SCM Secrets
Collaboration platforms (aka Source Code Management Systems, SCM) and CI/CD tools often provide Secret Management, so CI/CD pipelines may get the secret securely.
GitHub
Secrets in GitHub are variables set in an organization, repository, or repository environment, available to use in GitHub Actions workflows.
For secrets stored at the organization-level, access policies control which repositories can use organization secrets. Organization-level secrets let secrets be shared between multiple repositories, which reduces the need for creating duplicate secrets. Updating an organization secret in one location also ensures that the change takes effect in all repository workflows that use that secret.
For secrets stored at the environment level, you can enable required reviewers to control access to the secrets. A workflow job cannot access environment secrets until approval is granted by required approvers.
Once a secret is registered, it can be referenced in a CI/CD workflow using a {{ secret.SECRET }} expression. But if possible, do not pass the secret value to the command to be executed. The command should read the environment variable instead. In the following example, a secret named API_KEY is passed to the workflow step in the environment variable API_KEY, but its value is then hard-coded in the command line, so it will be visible in the process table:
Read creating secrets for a repository, for organization, or for environment for details on how to register a secret for GitHub Actions at a given scope.
GitLab
GitLab provides CI/CD Variables as a convenient wau to store and reuse data in a CI/CD pipeline, but they can be exposed by accidental pipeline misconfiguration.
GitLab provides support for external secret management providers:
After configuring a vault server, you may use vault secrets in a GitLab CI job:
This stores the value of the secret fetched from the vault into the SECRET variable.
Read Using external secrets in CI for full details.
Using Cloud Secret Management Services
AWS Secrets Manager
AWS Secrets Manager is the secret vault service in Amazon Web Services platform. The following are examples of how to use the official libraries for getting a secret using different programming languages:
See AWS SDK for JavaScript v3 for further details.
The following uses Boto3, the official Python interface maintained by AWS.
See SecretsManager client for further details.
The AWS Secrets Manager Java caching client is the official Java library for accessing AWS Secrets Manager
The secretsmanager package provides the official API client, operations, and parameter types for AWS Secrets Manager, using the AWS SDK for Go.
For full details, proceed with Get a Secrets Manager secret value using the .NET AWS SDK.
Azure Key Vault
The Azure Key Vault is the secrets management service in Azure. The following shows how to retrieve a secret using the official libraries for some popular languages.
The following shows how to use the @azure/keyvault-secrets package.
The azure-keyvault-secrets is the official Python library for accessing the Key Vault.
The following shows how to fetch a secret from Key Vault using the com.azure:azure-security-keyvault-secrets library.
Read azure-security-keyvault-secrets documentation for full details.
The following fetches a secret from Key Vault using Azure Key Vault Secrets client module for Go.
The following shows how to fetch a secret using the Azure Key Vault secret client library for .NET.
Google Cloud Secret Manager
Secret Manager is Google Cloud’s storage system for API keys, passwords, certificates, and other sensitive data.
In the following, <project_id> represents your Google Cloud Project ID, and SECRET is the name of the secret to fetch. It is assumed that the latest version of the secret is fetched. Examples can be found in the Quickstart page.
The @google-cloud/secret-manager is the official JavaScript library for Secret Manager. The following example shows how to fetch a secret.
Using a Third-Party Secret Vault
HashiCorp Vault
HashiCorp Vault is a centralized secrets management system that provides secure storage of sensitive information, such as password, API keys, access tokens or cryptographic keys, encrypted in transit and at rest. It permits dynamic generation for temporary, on-demand credentials, and advanced features like automated key rotation and leasing/renewal of secrets, plus some built-in support for secret revocation.
In what follows, we assume a mount point of "secret" and a vault path of "SECRET", and the secret is stored under key "value".
See node-vault, unofficial NPM package for Vault.
The following uses hvac, a Python client for Vault and other secret managers.
The example uses the (unofficial) Vault Java Driver.
The following example uses the Vault API official Go library.
The following example uses VaultSharp, .NET library for Vault.
CyberArk Conjur
CyberArk Conjur is an open-source security tool for managing secrets and credentials in modern IT environments.
The following show how to fetch a secret from CyberArk Conjur for popular programming languages. The environment variables CONJUR_APPLIANCE_URL, CONJUR_ACCOUNT, CONJUR_USERNAME and CONJUR_APIKEY contain the configuration needed to authenticate for fetching the secret.
Go to Client Libraries or https://docs.cyberark.com/conjur-open-source/Latest/en/Content/Developer/lp_REST_API.htm?tocpath=Developer%7CREST%C2%A0APIs for further detail.
The following code uses the official conjur-api-java library.
The following code uses the official conjur-api-java library.
In Python, there is no official SDK but the REST api could be invoked directly using the requests library:
The following example retrieves a secret using the community-supported conjurapi Go module.
This example uses the official Conjur API for .NET.
Last updated