Can this skill help with compliance requirements?

Yes, by automating rotation and providing audit trails for credential usage, this skill helps organizations meet regulatory requirements for credential lifecycle management and access control.

What is the dual-secret rotation pattern?

The dual-secret pattern maintains two valid versions of a secret during a transition window, allowing services to migrate to the new credential without interrupting active workflows or causing downtime.

What are event-driven rotation triggers?

Event-driven rotation triggers are conditions that require immediate secret updates regardless of the schedule, such as an employee leaving the company, a detected breach, or a service compromise.

How often should critical production secrets be rotated?

According to the skill's risk-based tiers, critical secrets with production write access or infrastructure control should be rotated every 7 to 14 days.

Does this support cloud-native secret managers?

Yes, the provided patterns include implementation examples for integrating GitHub Actions with cloud services like Google Cloud Secret Manager and Workload Identity Federation.

Secret Rotation Patterns

Name: Secret Rotation Patterns
Author: adaptive-enforcement-lab

byadaptive-enforcement-lab

セキュリティとテスト

Automates credential lifecycle management and zero-downtime secret rotation within GitHub Actions workflows.

概要

This skill provides Claude with standardized patterns and automated workflows for managing credential lifecycles within GitHub Actions to minimize the security risks of long-lived secrets. It implements risk-based rotation tiers, dual-secret strategies for zero-downtime updates, and proactive notification systems through Slack or GitHub Issues. By leveraging these patterns, developers can ensure that compromised credentials expire automatically, audit trails are maintained, and production environments remain secure without manual intervention or operational downtime.

主な機能

Proactive expiration monitoring with automated notification patterns
Event-driven rotation triggers for security incidents or offboarding
0 GitHub stars
Zero-downtime dual-secret implementation strategy
Risk-based rotation scheduling tiers (7 to 180 days)
Automated GitHub Action rotation and revocation workflows

ユースケース

Implementing zero-downtime secret updates for high-availability CI/CD pipelines
Setting up automated security alerts and inventory tracking for expiring secrets
Automating rotation for production database keys and cloud provider credentials

概要

主な機能

Proactive expiration monitoring with automated notification patterns
Event-driven rotation triggers for security incidents or offboarding
0 GitHub stars
Zero-downtime dual-secret implementation strategy
Risk-based rotation scheduling tiers (7 to 180 days)
Automated GitHub Action rotation and revocation workflows

ユースケース

Implementing zero-downtime secret updates for high-availability CI/CD pipelines
Setting up automated security alerts and inventory tracking for expiring secrets
Automating rotation for production database keys and cloud provider credentials