domains / families / security / secrets-management

secrets-management

combined

Implement secure secrets management for CI/CD pipelines using Vault, AWS Secrets Manager, or native platform solutions. Use when handling sensitive credentials, rotating secrets, or securing CI/CD environments. Secure secrets management practices for CI/CD pipelines using Vault, AWS Secrets Manager, and other tools.

When to use

• 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
• Design or repair secret retrieval, CI credentials, workload identity, access policies and rotation for an authorized system.

When not to use

• You plan to hardcode secrets in source control
• You cannot secure access to the secrets backend
• You only need local development values without sharing
• Masking cannot make logging secrets safe. Secret data can persist in infrastructure state, subprocess environments or backups; review those boundaries explicitly. Do not alter real credentials or deploy secret infrastructure without author…

Skill page

Conflict

The two skills cover the same domain but with different emphases and non-overlapping material. The first copy (rmyndharis) is a broad, example-heavy guide that includes specific tool integrations (Vault, AWS, Azure, GCP), Terraform, and a Python rotation script. The second copy (sickn33) is a stricter, security-focused procedure that emphasizes workload identity, least privilege, specific verification steps (testing denied access, synthetic markers), and explicitly warns against the development-mode patterns shown in the first copy. Crowning one would hide the other's unique constraints (e.g., the second's strict verification and identity focus vs. the first's concrete tooling examples).