Enhancing Security in Azure Cosmos DB: Best Practices
summary
Claims that 80% of attacks start at the identity level and shows how to eliminate key-based secrets by switching to managed identities (Microsoft Entra ID) and setting disable local auth via ARM/Bicep/Azure CLI; demo deploys the ARM template successfully. Describes using Key Vault for automatic key rotation, and building a Network Security Perimeter with profiles, inbound/outbound rules and diagnostics to group many resources under one access rule.
AI-written summary · about
chapters (9)
- 0:00Cosmos DB security intro
- 1:56Identities and secrets protection
- 4:26Disable key-based auth
- 6:36Automate key rotation
- 8:22Secure network access
- 10:31Network security perimeter
- 13:41Firewall vs perimeter
- 16:33Demo: perimeter setup
- 18:00Closing remarks
related talks
51mSecuring Azure Cosmos DB
49mTop 5 ways to secure Azure resources
39mTop 13 best security practices for Azure
19mKeyless Connections to Azure Cosmos DB
01h 00mEverything You Always Wanted to Know About Azure Security But Were Afraid to Ask
56mEnter the Matrix: Securing Azure’s Assets
19mKeyless Connections to Azure Cosmos DB (RBAC auth for data)
43mSecure Development