Are long-lived access keys and service account keys absent, or rotated at least every 90 days and unused ones deleted?
Facts read 16 Nov 2026. Page reviewed 16 Nov 2026.
Question 3 of the assessment asks: Are long-lived access keys and service account keys absent, or rotated at least every 90 days and unused ones deleted? A static key works from anywhere, never expires on its own and often ends up in code, tickets and laptops.
Start the assessment ยท All 40 questions
Why it matters
A static key works from anywhere, never expires on its own and often ends up in code, tickets and laptops.
Answers and what each is worth
| Answer | Value |
|---|---|
| Yes, none or all under 90 days | 1 |
| Some are older or unused | 0.5 |
| No or not known | 0 |
How to check it in each cloud
- AWS
- Download the IAM credential report and sort by access_key_last_rotated and access_key_last_used; every active key older than 90 days is a finding.
- Azure
- List app registration client secrets and certificates with their expiry dates (Entra admin center, App registrations), and flag any valid for more than 12 months.
- Google Cloud
- Run gcloud iam service-accounts keys list for each service account with --managed-by=user, and use the Policy Intelligence service account insights to find unused keys.
The fix
Replace static keys with short-lived credentials, and delete every key older than 90 days or unused for 90 days. Effort: medium.
Where it comes from
- Google Cloud security best practices Service account keys: Best practices for managing service account keys
- Microsoft cloud security benchmark IM-8: source
- NIST SP 800-53 Rev. 5 IA-5: source
Related pages
Sources
- Google Cloud security best practices Service account keys, read 16 Nov 2026
- Microsoft cloud security benchmark IM-8, read 16 Nov 2026
- NIST SP 800-53 Rev. 5 IA-5, read 16 Nov 2026
Last reviewed 16 Nov 2026.