A comprehensive guide for organizing secrets in Thales CipherTrust Secrets Manager, powered by Akeyless
Choose a secret organization pattern based on your team structure:
| Organization Size | Scenario | Pattern | Example |
|---|---|---|---|
| 1-10 people | Simple apps | Environment-First | /prod/api/postgres/service-account-password |
| 10-50 people | Multiple products | Service-First | /user-service/prod/postgres/service-account-password |
| 50+ people | Multiple business units | Organization-First | /payments-bu/prod/billing/stripe/key |
| Multi-tenant | SaaS platform | Tenant-First | /customer-a/prod/crm/db/service-account-password |
| High-security | Compliance requirements | Classification-First | /pci/prod/payment/encryption/key |
| DevOps-focused | Clear team ownership | Team-First | /platform-team/prod/monitoring/grafana/admin-password |
- Quick Decision Tree - Choose the right pattern for your organization
- Core Patterns - 6 essential organizational patterns with examples
- Naming Conventions - Best practices for consistent secret naming
- Implementation Guide - Simple steps to get started
- Akeyless CLI Commands - Essential commands for secret management
- Best Practices - Key principles for success
Small Teams (1-10 people)
/prod/api/database/service-account-password
/prod/api/jwt-secret
/staging/api/database/service-account-passwordGrowing Teams (10-50 people)
/user-service/prod/database/service-account-password
/payment-service/prod/external/stripe-secret-key
/notification-service/prod/internal/jwt-secretEnterprise (50+ people)
/payments-bu/prod/billing-service/stripe/secret-key
/identity-bu/prod/auth-service/oauth/client-secret
/shared/prod/encryption/master-keyFound an issue or have a suggestion? Contributions are welcome.
- Fork the repository
- Create a feature branch (
git checkout -b feature/improvement) - Commit your changes (
git commit -m 'Add improvement') - Push to the branch (
git push origin feature/improvement) - Open a Pull Request
This project is licensed under the MIT License - see the LICENSE file for details.