Secrets management
What is Google Secret Manager? An introduction to Google Cloud's secrets storage service
Google Secret Manager is Google Cloud's storage system for API keys, passwords, certificates, and other sensitive data. It holds these values as managed secrets, with access controlled through Cloud IAM and activity recorded through Cloud Audit Logs. Secrets are versioned, so applications can request a specific version or the latest one.
- Tool
- Google Secret Manager
- Made by
- Google Cloud
- Official site
- cloud.google.com/security/products/secret-manager
- Category
- Secrets management
Who makes Google Secret Manager
Google Secret Manager is made by Google Cloud, and it is described by the vendor as Google Cloud's storage system for sensitive data. The official product page is linked below this article.
Official website: cloud.google.com/security/products/secret-manager
What Google Secret Manager is for
Secret Manager exists to store sensitive values in one managed place. The kinds of data it handles include API keys, passwords, certificates, and other sensitive data. Secrets can be stored as binary blobs or as text strings, and the value can be in any format as long as it stays within the limit of 64 KiB.
The vendor describes it as a good fit for runtime configuration. Typical examples are database passwords, API keys, and TLS certificates that an application needs when it runs. Keeping these values in a dedicated store, instead of scattering them across files and scripts, gives teams a single point at which to apply permissions and review activity.
Who Google Secret Manager is for
The vendor does not state a specific audience. Based on the facts available, the service is relevant to teams that run workloads on Google Cloud and need to hand credentials and certificates to applications in a controlled way.
It is also relevant to teams that automate their infrastructure, since it integrates with third-party tools such as Terraform and GitHub Actions. Organizations that need to know who touched a credential, and when, will find the audit logging described below directly applicable.
Notable capabilities
The capabilities below describe how Secret Manager controls access, tracks change, and protects stored data. Each one comes from the vendor's own description of the product.
- Per-secret permissions: Cloud IAM roles allow permissions to be set on individual secrets and separate the ability to manage a secret from the ability to access its data. Access defaults to project owners, and other roles must be granted permissions through Cloud IAM.
- Versioning: secrets are versioned, and requests can be pinned to the latest version. Secret data is immutable, and most operations act on secret versions rather than on the secret itself.
- Rotation automation: Cloud Functions can be used to automate secret rotation, so credentials can be replaced without manual steps.
- Audit logging: the Cloud Audit Logs integration generates an audit log for every interaction. These logs can feed anomaly detection systems that spot abnormal access.
- Regional control: users can choose the regions where secret data is stored, or let Google decide.
- Encryption: data is encrypted in transit with TLS and at rest with AES-256-bit keys.
- Network context: VPC Service Controls enable context-aware access from hybrid environments.
- Tooling integration: it works with third-party tools such as Terraform and GitHub Actions.
How Google Secret Manager fits secrets management
Secrets management is the practice of storing credentials centrally, controlling who can read them, and recording how they are used. Secret Manager covers that ground inside Google Cloud, combining storage, versioned values, role-based access, and logging in a single service.
Within Cipherholt's wider niche of encryption, cryptography, secure messaging, VPN, and secrets management, it sits on the secrets side. It is not a messaging or VPN product. Its relationship to encryption is that stored data is protected with TLS in transit and AES-256-bit keys at rest, while its relationship to access control comes from Cloud IAM and VPC Service Controls. Teams assessing it will want to consider how closely their workloads are tied to Google Cloud.
Frequently asked questions
What is Google Secret Manager used for?
It is used to store API keys, passwords, certificates, and other sensitive data. It suits runtime configuration such as database passwords, API keys, or TLS certificates.
Who develops Google Secret Manager?
Google Cloud develops Secret Manager. It is presented as Google Cloud's storage system for sensitive data.
Does Google Secret Manager support secret rotation?
Cloud Functions can be used to automate secret rotation. Secrets are also versioned, and requests can be pinned to the latest version.
How large can a secret be in Google Secret Manager?
Secret values can be in any format but are limited to 64 KiB. They can be stored as binary blobs or text strings.
How does Google Secret Manager protect stored data?
Data is encrypted in transit with TLS and at rest with AES-256-bit keys. Access defaults to project owners, and other roles must be granted permissions via Cloud IAM.
Cipherholt is independent and is not affiliated with Google Cloud. Product names belong to their owners. Features change; confirm details on the official website.