π Google Project has API Keys π’
- Contextual name: π Google Project has API Keys π’
- ID:
/ce/ca/google/project/api-keys-for-active-services
- Located in: π Google Project
Flagsβ
- π’ Policy with categories
- π’ Policy with type
- π’ Production policy
Our Metadataβ
- Policy Type:
COMPLIANCE_POLICY
- Policy Category:
SECURITY
Similar Policiesβ
- Cloud Conformity
Logicβ
- π§ prod.logic.yaml π π’
- π Google Project
- π§ͺ test-data.json
Descriptionβ
Descriptionβ
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 keyImpactβ
Deleting an API key will break dependent applications (if any).
Auditβ
From Consoleβ
- From within the Project you wish to audit Go to
APIs & Services\Credentials
.- In the section
API Keys
, no API key should be listed.... see more
Remediationβ
Remediationβ
From Consoleβ
- Go to
APIs & Services\Credentials
- In the section
API Keys
, to delete API Keys: Click theDelete Bin Icon
in front of everyAPI 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
policy.yamlβ
Linked Framework Sectionsβ
Section | Sub Sections | Internal Rules | Policies | Flags |
---|---|---|---|---|
πΌ CIS GCP v3.0.0 β πΌ 1.12 Ensure API Keys Only Exist for Active Services - Level 2 (Automated) | 1 | |||
πΌ Cloudaware Framework β πΌ Cryptographic Configuration | 8 |