AwsCLI icon
If icon
SlackIncomingWebhook icon
Schedule icon

AWS Secrets Manager Unrotated and Stale Secret Sentinel

Audits AWS Secrets Manager to detect unrotated credentials exceeding 90 days and enforce automated rotation policies.

Categories
BusinessCloud

How it works

This sentinel leverages AwsCLI to list secrets in AWS Secrets Manager across the target region. It evaluates RotationEnabled flags and calculates days elapsed since the secret was last rotated, alerting SecOps teams when static or dormant credentials violate compliance rotation standards.

What you get

  • Proactive visibility into stale database, API, and third-party credentials.
  • Early prevention of compliance non-conformities under SOC 2, HIPAA, and PCI-DSS.
  • Automated Slack delivery detailing secret names and days of staleness.

Who it's for

  • Security operations (SecOps) teams and cloud governance officers.
  • Application architects overseeing automated secret management.

Why orchestrate this with Kestra

Kestra runs automated scheduled operational health checks with native error handling, secret injection, and multi-channel alerting.

Prerequisites

  • AWS IAM credentials with secretsmanager:ListSecrets permissions.
  • Secrets AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, and SLACK_WEBHOOK configured in Kestra.

Quick start

  1. Import this blueprint into Kestra.
  2. Configure aws_region, threshold days, and credentials.
  3. Run manually to check current secret rotation ages.

How to extend

  • Configure automated rotation via secretsmanager:RotateSecret Lambda functions.
  • Verify secret resource policies to block cross-account access.
  • Export secret audit inventory to AWS Security Hub.

Links

See How

New to Kestra?

Use blueprints to kickstart your first workflows.