Once you have credentials stored in Azure Key Vault, now they can be accessed by another application in Azure resource if you’d like and if you’d set up the right access for it (using Service Principal). Helping their efficiency while maintaining good security hygiene. If you’re working with technical teams (I’d assume you are), they can access the passwords and keys right from the terminal. AD management takes care of password management. When an employee is terminated, their AD is one of the first things to get disabled. Use your existing AD accounts to maintain access to the passwords/keys.There are some key benefits to this approach: ![]() So I thought I’d give it a go and blog about it. Unfortunately and surprisingly Google didn’t come to my rescue. And since we were an all Azure shop, I immediately wondered if we could use the Azure Key Vault in some way as a password repository. Since I was new to the team and the budget was he-who-must-not-be-named, I wondered what we could use to rectify the issue on hand or at least mitigate some of the risks and improve the workflow. This also leads to scenarios where teams are resorting to sending passwords over chat or worse (email?). Imagine someone updates a password and now s/he would have to update his password, update the password database to a central repository and wait for all other users to ‘pull’ the new file… all in order to be in-sync. ![]()
0 Comments
Leave a Reply. |