## About Cloud KMS

### What is Cloud KMS? What can it do?

Cloud Key Management Service (Cloud KMS) is a cloud-hosted key management service that lets you
manage encryption for your cloud services the same way you do on-premises. You
can generate, use, rotate, and destroy cryptographic keys.
Cloud KMS is integrated with Identity and Access Management (IAM) and Cloud Audit Logs so
you can manage permissions on individual keys, and monitor how they are used.

### Can I store secrets?

Cloud KMS stores keys and metadata about keys, and does not
have a general data storage API. [Secret Manager](https://docs.cloud.google.com/secret-manager) is
recommended for storing and accessing sensitive data for use in Google Cloud.

### Is there an SLA?

Yes, see [Cloud KMS Service Level Agreement](https://docs.cloud.google.com/kms/sla).

### How do I provide product feedback?

Contact the engineering team at [cloudkms-feedback@google.com](mailto:cloudkms-feedback@google.com).

### How do I provide documentation feedback?

While viewing Cloud KMS documentation, click **Send feedback** near
the top right of the page. This will open a feedback form.

### If I need help, what are my options?

We invite our users to post their questions on [Stack Overflow](http://stackoverflow.com/questions/tagged/google-cloud-kms). Along with
the active Stack Overflow community, our team actively monitors Stack Overflow
posts and answers questions with the tag [google-cloud-kms](http://stackoverflow.com/questions/tagged/google-cloud-kms).

We also offer various levels of support depending on your needs. For additional
support options, see our [Google Cloud Support Packages](https://cloud.google.com/support).

### Does Cloud KMS have any quotas?

Yes. For information about quotas, including viewing or requesting additional
quotas, see [Cloud KMS quotas](https://docs.cloud.google.com/kms/quotas).

There is no limit on the number of keys, key rings, or key versions. Additionally,
there is no limit on the number of keys per key ring and key versions per key.

### In what countries can I use Cloud KMS?

You can use Cloud KMS in any country where Google Cloud services
are supported.

## Keys

### Does key rotation re-encrypt data? If not, why?

[Key rotation](https://docs.cloud.google.com/kms/docs/key-rotation) does not automatically re-encrypt data. When you decrypt data,
Cloud KMS knows which key version to use for the decryption. As
long as a key version is not disabled or destroyed, Cloud KMS can
decrypt data protected with that key.

> [!IMPORTANT]
> **Important:** If you suspect unauthorized use of a key, you should [re-encrypt](https://docs.cloud.google.com/kms/docs/re-encrypt-data) the data protected by that key, [revoke IAM access](https://docs.cloud.google.com/kms/docs/iam#revoking_access_to_a_resource) to the key, and either [disable](https://docs.cloud.google.com/kms/docs/enable-disable#disable_an_enabled_key_version) or [schedule destruction](https://docs.cloud.google.com/kms/docs/destroy-restore#schedule_a_key_version_for_destruction_destroy_a_key_version) of the compromised key version.

### Why can't I delete keys or key rings?

To prevent resource name collisions, key ring and key resources CANNOT be
deleted. Key versions also cannot be deleted, but key version material can be
destroyed so that the resources can no longer be used. For more information,
see [Lifetime of objects](https://docs.cloud.google.com/kms/docs/object-hierarchy#lifetime). Billing is based on the number of active
key versions; if you destroy all active key version material, there is no charge
for the key rings, keys, and key versions which remain.

## Authorization and authentication

### How do I authenticate to the Cloud KMS API?

How clients authenticate may vary a bit depending on the platform on which the
code is running. For details, see [Accessing the API](https://docs.cloud.google.com/kms/docs/accessing-the-api).

### What IAM roles should I use?

To enforce the principle of least privilege, ensure that the user and service
accounts in your organization have only the permissions essential to performing
their intended functions. For more information, see [Separation of duties](https://docs.cloud.google.com/kms/docs/separation-of-duties).

### How quickly is an IAM permission removed?

Removal of a permission should be in effect in less than one hour.

## Miscellaneous

### What is additional authenticated data, and when would I use it?

Additional authenticated data (AAD) is any string that you pass to
Cloud KMS as part of an encrypt or decrypt request. It is used as
an integrity check and can help protect your data from a *confused deputy
attack* . For more information, see [Additional authenticated data](https://docs.cloud.google.com/kms/docs/additional-authenticated-data).

### Are data access logs enabled by default? How do I enable data access logs?

Data access logs are not enabled by default. For more information, see
[Enabling data access logs](https://docs.cloud.google.com/kms/docs/logging#enabling_data_access_logs).

### How do Cloud KMS keys relate to service account keys?

[Service account keys](https://docs.cloud.google.com/iam/docs/service-account-creds#key-types) are used for service-to-service authentication within
Google Cloud. Service account keys are unrelated to Cloud KMS
keys.

### How do Cloud KMS keys relate to API keys?

An [API key](https://docs.cloud.google.com/docs/authentication/api-keys) is a simple encrypted string that can be used when calling
certain APIs that don't need access to private user data. API keys track
API requests associated with your project for quota and billing. API keys are
unrelated to Cloud KMS keys.

### Do you have additional details about the HSMs used by Cloud HSM?

All HSM devices are manufactured by Marvell (formerly Cavium). The
FIPS certificate for the devices is [on the NIST website](https://csrc.nist.gov/projects/cryptographic-module-validation-program/certificate/4399).