Our great sponsors
-
The CI/CD has a service account with permissions to all envs, and during deployment it renders the config files and inserts the "real" values by pulling it from Vault/KMS. Something very simple is Spruce, which is actually a powerful general templating tool but I've seen it only used for vault secrets so far.
-
There's a central key management service. Hashicorp Vault is pretty much the de-facto standard and most other tools integrate nicely with this. The only exception I've seen if companies are fully invested into a single cloud provider, in which case their cloud native alternative is used (AWS KMS, GCP KMS, Azure Keyvault). Even then, sometimes Vault is used as a frontend with the Cloud KMS as backing store.
-
SonarLint
Deliver Cleaner and Safer Code - Right in Your IDE of Choice!. SonarLint is a free and open source IDE extension that identifies and catches bugs and vulnerabilities as you code, directly in the IDE. Install from your favorite IDE marketplace today.
Related posts
- SSH Keys Hosting
- What are secure methods of storing log in credentials when programs and scripts need to access other computers or databases?
- Should I put sensitive information inside a .env file? Can I just delete it after the server is online?
- My first attempt at using HashiCorp Vault (inc. C# Client Library)
- Secure your Kubernetes secrets easily with Trousseau