Ensure access keys are rotated every 90 days or less
Rotating access keys regularly reduces the window of opportunity for compromised keys to be used. AWS recommends rotating access keys every 90 days as a security best practice.
Security Impact
Old access keys have increased exposure time if compromised through code commits, logs, or other means.
How to Remediate
Rotate access keys every 90 days. Create a new access key, update applications, test functionality, then deactivate and delete the old key.
Affected Resources
Compliance Frameworks
How TigerGate Helps
TigerGate continuously monitors your AWS environment to detect and alert on this misconfiguration. Here's what our platform does for this specific check:
- Continuous Scanning
Automatically scans all Identity and Access Management (IAM) resources across your AWS accounts 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 AWS v1.5.0, CIS AWS v2.0, SOC 2 compliance
- Drift Detection
Get alerted if this configuration drifts back to an insecure state after remediation
Check Details
- Check ID
- aws-iam-13
- Service
- Identity and Access Management (IAM)
- Category
- Access Keys
- Severity
- HIGH
- CIS Benchmark
- 1.13
Automate This Check
TigerGate automatically scans your AWS environment for this and 575+ other security checks.
Start Free TrialRelated Identity and Access Management (IAM) Checks
View all checksAvoid the use of root account
Ensure MFA is enabled for the root account
Ensure hardware MFA is enabled for the root account
Ensure no root account access keys exist
Ensure IAM password policy requires at least one uppercase letter