Ensure API keys are rotated regularly
API keys should be rotated within 90 days to limit exposure from compromised keys.
Security Impact
Long-lived API keys increase the window for misuse if exposed.
How to Remediate
Delete old API keys and create new ones. Update applications with new keys.
Affected Resources
Compliance Frameworks
How TigerGate Helps
TigerGate continuously monitors your GCP environment to detect and alert on this misconfiguration. Here's what our platform does for this specific check:
- Continuous Scanning
Automatically scans all Google Cloud IAM resources across your GCP projects every hour
- Instant Alerts
Get notified via Slack, email, or webhooks when this misconfiguration is detected
- One-Click Remediation
Fix this issue directly from the TigerGate dashboard with our guided remediation
- Compliance Evidence
Automatically collect audit evidence for CIS GCP v1.3.0, SOC 2, PCI-DSS compliance
- Drift Detection
Get alerted if this configuration drifts back to an insecure state after remediation
Check Details
- Check ID
- gcp-iam-10
- Service
- Google Cloud IAM
- Category
- Credential Management
- Severity
- MEDIUM
- CIS Benchmark
- 1.10
Automate This Check
TigerGate automatically scans your GCP environment for this and 79+ other security checks.
Start Free TrialRelated Google Cloud IAM Checks
View all checksEnsure service account keys are rotated within 90 days
Ensure user-managed service account keys are not used
Ensure primitive roles (Owner, Editor, Viewer) are not used
Ensure service accounts do not have admin privileges
Ensure MFA is enforced for all users