Secrets Manager secret does not have rotation enabled
- Severity
- Medium
- Service
- Secrets Manager
- Check ID
- SECRETS_MANAGER_ROTATION_DISABLED
What this check finds
Long-lived static secrets increase the window of exposure if a secret is compromised. Automatic rotation ensures credentials are regularly cycled, limiting the usefulness of leaked secrets.
Passing looks like: Secrets Manager rotation enabled.
How to fix it
Configure automatic rotation for the secret in Secrets Manager.
AWS CLI
aws secretsmanager rotate-secret --secret-id SECRET_ID --rotation-lambda-arn LAMBDA_ARN --rotation-rules AutomaticallyAfterDays=30
Names in capitals are placeholders for your own resource. Review a command before you run it.
AWS console
Secrets Manager → Secrets → select secret → Rotation → Edit rotation → Enable automatic rotation.
Compliance controls it is evidence for
A failing result counts against these controls in KloudLytics; a passing one is evidence towards them. How compliance mapping works
| Framework | Controls |
|---|---|
| PCI-DSS v4.0.1 |
|
| SOC 2 — Trust Services Criteria |
|
| NIST SP 800-53 Rev5 (Moderate) |
|
| NIST Cybersecurity Framework 2.0 |
|
| ISO/IEC 27001:2022 Annex A |
|
Checked on every scan
KloudLytics runs this check each time it scans a connected AWS account, through a read-only role, and lists every affected resource with its region. On Pro and Business a fix is written for the specific resource rather than the general case above. The exact access it needs