TMA-IBMCLOUD-1.3
Ensure API keys are rotated every 90 days
Description
Replace production API keys with new API keys regularly, every 90 days for example, as a best practice to secure your account. API key rotation can help reduce the impact to your organization if an API key becomes exposed or compromised. If you suspect that a key might have been leaked or compromised, the key must be rotated out of production and deleted.
How it is checked
Audit method: Manual review
This recommendation cannot be checked automatically. A scan lists it with these instructions when you pass --include-manual.
Using Console: To find out when an API key was created, complete the following steps: 1. Log in to IBM Cloud at https://cloud.ibm.com. 2. From the Menu bar, click Manage, Access(IAM), API keys. 3. Identify an API key and from the Actions menu, select Details. 4. View the date the API key was created.
How it is fixed
Fix method: Guidance or infrastructure patch
Using Console: To create new API key, complete the following steps: 1. Log in to IBM Cloud at https://cloud.ibm.com. 2. From the Menu bar, click Manage, Access (IAM), API keys. 3. Click Create an IBM Cloud API key. To rotate an API key, replace an old API key anywhere it is used with the newly created API key. Delete an old API key: 1. Log in to IBM Cloud at https://cloud.ibm.com. 2. From the Menu bar, click Manage, Access (IAM), API keys. 3. Identify the API key you want to delete, and from the Actions menu, select Delete. You can also opt to use IBM Cloud Secrets Manager to auto-rotate keys - https://www.ibm.com/products/secrets-manager
Properties
- Operating systems
- Any
- Tags
- cloudcryptoibmcloud
- Reference
- CIS IBM Cloud Foundations Benchmark v2.0.0 - 1.3 Ensure API keys are rotated every 90 days