secrets-management

Topics in the source

• Secrets Management
• Purpose
• Use this skill when
• Do not use this skill when
• Instructions
• Safety
• Secrets Management Tools
• HashiCorp Vault

Secure secrets management practices for CI/CD pipelines using Vault, AWS Secrets Manager, and other tools. Implement secure secrets management in CI/CD pipelines without hardcoding sensitive information. Store API keys and credentials Manage database passwords Handle TLS certificates Rotate secrets automatically Implement least-privilege access You plan to hardcode secrets in source control You cannot secure access to the secrets backend You only need local development values without sharing 1. Identify secret types, owners, and rotation requirements. 2. Choose a secrets backend and access model. 3. Integrate CI/CD or runtime retrieval with least privilege. 4. Validate rotation and audit logging. Never commit secrets to source control. Limit access and log secret usage for auditing. Centralized secrets management Dynamic secrets generation Secret rotation Audit logging Fine-grained access control AWS-native solution Automatic rotation Integration with RDS CloudFormation support Azure-native solution HSM-backed keys Certificate management RBAC integration GCP-native solution Versioning IAM integration Reference: See references/vault-setup.md Reference: See references/github-secrets.

This is an excerpt. Refer to the complete source and its current requirements.