TMA-IBMCLOUD-1.2
Ensure API keys unused for 180 days are detected and optionally disabled
Description
Monitor API key usage in your account and search for API keys that are unused or used infrequently. If an API key is unused for long period in your account, it must be suspended or disabled as a security best practice. All API keys, even those that are used infrequently, must be rotated periodically. To reduce the likelihood of accidental exposure or leaking, monitoring for infrequently used API keys can indicate that an API key can be suspended and even deleted, if there is no anticipated future usage.
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: 1. Log in to IBM Cloud at https://cloud.ibm.com. 2. Click Manage, Access (IAM), and select Inactive Identities 3. Click Update report to view the most recent report of inactive identities in your account 4. Select the API keys tab to review a list of unused API keys
How it is fixed
Fix method: Guidance or infrastructure patch
On the Inactive Identities report under API keys tab, review and remove the API keys no longer in use. To delete inactive identities that are no longer in use for over 180 days, click the Actions icon, Remove
Properties
- Operating systems
- Any
- Tags
- cloudcryptoibmcloud
- Reference
- CIS IBM Cloud Foundations Benchmark v2.0.0 - 1.2 Ensure API keys unused for 180 days are detected and optionally disabled