Our great sponsors
-
If data infrastructure is evolving to a dynamic nature, why is it still the case that you're using static database credentials inside your organization? Not only are these shared credentials used by humans, often times the same credentials are used in all of the API calls made by the applications. This poses a huge security risk as a leaked database credential in the wrong hands can cause havoc. In this blog, I introduce the concept of dynamic credentials and use HashiCorp Vault to dispense a short-lived credential to connect to a managed PostgreSQLĀ® service.
NOTE:
The number of mentions on this list indicates mentions on common posts plus user suggested alternatives.
Hence, a higher number means a more popular project.
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)
- How do you manage sensitive keys when using foreign developers?