LOW

Ensure Secrets Manager secret versions are managed

Old secret versions should be managed to prevent accumulation and reduce exposure.

Security Impact

Accumulated old versions may contain previously compromised credentials.

How to Remediate

Configure rotation to properly manage staging labels. Review and clean up old versions if needed.

Affected Resources

AWS::SecretsManager::Secret

Compliance Frameworks

SOC 2

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 AWS Secrets Manager 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 SOC 2 compliance

  • Drift Detection

    Get alerted if this configuration drifts back to an insecure state after remediation

Check Details

Check ID
aws-secretsmanager-10
Service
AWS Secrets Manager
Category
Credential Management
Severity
LOW

Automate This Check

TigerGate automatically scans your AWS environment for this and 575+ other security checks.

Start Free Trial

Related AWS Secrets Manager Checks

View all checks
aws-secretsmanager-1high

Ensure Secrets Manager secrets have automatic rotation enabled

aws-secretsmanager-2medium

Ensure Secrets Manager secrets are encrypted with KMS CMK

aws-secretsmanager-3medium

Ensure Secrets Manager secrets have resource policies

aws-secretsmanager-4critical

Ensure Secrets Manager secrets are not publicly accessible

aws-secretsmanager-5medium

Ensure Secrets Manager rotation is tested