Detections
Analytics

1.12 Ensure API Keys Only Exist for Active Services

Warning! Audit Deprecated

This audit has been deprecated and will be removed in a future update.

View Next Audit Version

Information

API Keys should only be used for services in cases where other authentication methods are unavailable. Unused keys with their permissions in tact may still exist within a project. Keys are insecure because they can be viewed publicly, such as from within a browser, or they can be accessed on a device where the key resides. It is recommended to use standard authentication flow instead.

Rationale:

To avoid the security risk in using API keys, it is recommended to use standard authentication flow instead. Security risks involved in using API-Keys appear below:

API keys are simple encrypted strings

API keys do not identify the user or the application making the API request

API keys are typically accessible to clients, making it easy to discover and steal an API key

Impact:

Deleting an API key will break dependent applications (if any).

Solution

From Console:

Go to APIs & Services\Credentials using

In the section API Keys, to delete API Keys: Click the Delete Bin Icon in front of every API Key Name.

From Google Cloud Command Line

Run the following from within the project you wish to audit gcloud services api-keys list --filter

**Pipe the results into **
gcloud alpha services api-keys delete

Default Value:

By default, API keys are not created for a project.

See Also

https://workbench.cisecurity.org/benchmarks/11843

Item Details

References: CSCv7|16.8

Plugin: GCP

Control ID: c3388ee775c8657a7e3b8b44436e2f6cfb43c6e3302ac2f8c997306293ec2177