Google Cloud Compliance ControlsGoogle Cloud API Keys
API keys should allow access only to APIs needed by the application
API 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 restrict API keys to use (call) only APIs required by an application.
What this control checks
API keys are limited to only the APIs the application needs
Framework mappings
The clauses this control is mapped to in each framework.
- 10.2.1.2: Audit logs are implemented to support the detection of anomalies and suspicious activity, and the forensic analysis of events.
- A.8.12 Data leakage prevention
- 6 Security in network and information systems acquisition, development and maintenance
- 9 Cryptography
- PL-8 Information Security Architecture
- SA-8 Security Engineering Principles
NIST Cybersecurity Framework v2.0
- PR.AA-01: Identities and credentials for authorized users, services, and hardware are managed by the organization.
- PR.AA-03
- PR.AA-05
- 1.14 Ensure API Keys Are Restricted to Only APIs That Application Needs Access
- 1.14 Ensure API Keys Are Restricted to Only APIs That Application Needs Access
- IAM-08.05B The cloud service provider documents, communicates and makes available to all users under its responsibility rules and recommendations for the management of credentials, including at least: - Non-reuse of credentials;- Trade-offs between entropy and ability to memorise;-...
- PSS-05.01B The cloud service provider provides authentication mechanisms that can force strong authentication (e.g. two or more factors) for users, IT components or applications within the cloud users' area of responsibility. These authentication mechanisms are set up at all access points that...
- 1.14 Ensure API keys are restricted to only APIs that application needs access
- 1.14 Ensure API keys are restricted to only APIs that application needs access
- 1.14 Ensure API keys are restricted to only APIs that application needs access
NIST Cybersecurity Framework v1.0
- PR.IP-2: A System Development Life Cycle to manage systems is implemented.
Related controls
Tool mappings
Use these identifiers to cross-reference this control across tools, reports, and evidence.
- Compliance.tf Control:
iam_api_key_restricts_apis - Powerpipe Control:
gcp_compliance.control.iam_api_key_restricts_apis - Prowler Check:
apikeys_api_restrictions_configured
Last reviewed: 2026-10-09