If you use account keys or connection strings to access Azure resources, there is a better way!
User Assigned Managed Identities (#UAMI) are more secure and less work to "manage", because you really don't have to maintain them once they are setup.
In this demo we setup connectivity from an #AppService to an Azure #KeyVault and #StorageAccount using UAMI's, showing the .Net code changes required to successfully connect to multiple resources. It isn't difficult!
So I've been trying to figure out the answer to a theoretical problem: what would I do if I was in a foreign country and had my phone and laptop seized / stolen?
I'm not too concerned about the shit on them, but nowadays everything is 2FA. Even my password manager needs second factor auth on a new device, and the second factor is email which... You guessed it needs a second factor. I feel like I'm one lost device from disaster.
How do you go from zero to re-equipped with your logins without access to your own desk and devices?
Would it be insane to post an encrypted binary blob in like a public git repo? Random webpage? What encryption would be sufficient to confidentiality drop an entire password vault, ssh keys, etc into a public space?
(Encryption not my area of expertise)
#2fa #encryption #passwords #keyvault #multifactor #backups #cybersecurity
【Azure】App Service 証明書の購入で注意すべき点
https://qiita.com/bluesea_nishi/items/2beb4656d286d3e2ba70?utm_campaign=popular_items&utm_medium=feed&utm_source=popular_items
Sensitive data like passwords, connection strings, access keys, etc. should not be included in the source code that is committed in a shared repository. Secrets must not be deployed with the apps, too. For developers that use Visual Studio, since man...
Now that the #golang #AzureSDK for #KeyVault has released v1.0.0, I have updated to it and released v1 of https://pkg.go.dev/github.com/heaths/azcrypto@v1.0.0 : a cryptography client for Key Vault and #ManagedHSM that not only makes it easier to call crypto operations but tries to first cache the public key and do public key operations locally to improve performance and help mitigate throttling.
We have this in our other languages' SDKs but doesn't fit our design goals for #golang, so I wrote it as a separate module.
My https://github.com/heaths/azcrypto module for easy #Azure #KeyVault and #ManagedHSM crypto operations is now feature-complete and at parity with our other #AzureSDK languages' crypto libraries. It now supports crypto operations locally using a JWK.
Not likely to make it into our official azkeys SDK, but written to our same SDK guidelines.
azkeys will GA soon, and once I upgrade my dependency I plan to GA this module.