Overview
Overview
+API keys are weaker than identity-based authentication and are frequently exposed in client code and repositories. Projects should avoid API key usage when service accounts or stronger controls are available.
Remediation guidance
GCP remediation
+### Console
+1. Open APIs and Services -> Credentials.
+2. Identify and remove unnecessary API keys.
+3. For keys that must exist temporarily, restrict by API, application, and source.
+4. Prefer service accounts and workload identity over API keys.
+
+### Google Cloud CLI
+List API keys in a project:
+
+~~~bash
+gcloud services api-keys list --project
Service-wide remediation
Recommended when many resources are affected: fix the platform baseline first so new resources inherit the secure setting, then remediate the existing flagged resources in batches.
Platform
Use the provider or platform baseline, preventive policy, and IaC modules to enforce this setting consistently when many resources are affected.
Operational rollout
- Fix the baseline first at the account, subscription, project, cluster, or tenant scope that owns this control.
- Remediate the currently affected resources in batches, starting with internet-exposed and production assets.
- Re-scan and track approved exceptions with an owner and expiry date.
Query logic
These are the stored checks tied to this control.
No stored query bodies are attached to this entry.
