secret-rotation

Scan your codebase and configuration files to identify hardcoded secrets. This skill evaluates repositories, deployment configurations, and CI/CD pipelines to surface plaintext credentials and ensure secrets are properly referenced through secret managers.

A secrets rotation policy defines schedules for updating credentials to maintain security. You can evaluate your repository for defined rotation schedules, automation readiness, and policy compliance to identify missing or misconfigured rotation practices across your deployment configurations.

Yes, you can audit secret manager usage by verifying that secrets are referenced through secret managers rather than plaintext credentials. This assessment generates audit-ready findings suitable for security reviews and compliance attestations across your codebase.

Yes, secrets detection applies directly to CI/CD pipelines and deployment configurations. It evaluates these environments to surface automation gaps, improper secret manager references, and misconfigurations to ensure overall security and compliance readiness.

The best way to enforce secrets management is to validate practices across repositories by detecting hardcoded credentials, assessing secret manager integration, and evaluating rotation policies. This comprehensive approach surfaces misconfigurations and generates audit-ready compliance reporting.