Securing Azure Cosmos DB using Microsoft Defender
summary
Demo shows Azure Defender for Cosmos DB toggled on in Environment settings to scan two accounts: one using selected networks (blocked) and one allowing all networks (unhealthy). Defender surfaces a medium recommendation “accounts should have firewall rules,” lists unhealthy resources, and raises alerts for a SQL injection attempt with IP source, anomalous queries, container name and remediation steps. Backup defaults are four‑hour interval with two retentions, key rotation and replication with automatic failover are demonstrated; Defender is preview and free now.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 0:35Motivation
- 1:59Agenda
- 2:50Overview
- 3:28Cloud Security
- 6:42Microsoft Defender
- 8:45Security Alerts
- 9:14Network Security
- 10:43Global Replication
- 11:42Regional Failures
- 13:17Backup and Restore
- 13:41Backup Interval and Retention
- 14:48Key Rotation
- 16:42Resource Lock
- 17:06Importance of Resource Lock
- 26:05Limitations
related talks
51mSecuring Azure Cosmos DB
54mCloud & Hybrid Workload Protection using Azure Defender
19mEnhancing Security in Azure Cosmos DB: Best Practices
48mSecuring Cosmos DB: Ready for Production!
43mDefending the Cloud: Securing Your Microsoft Data Workloads
43mLearn Azure SQL Database through Demos
19mMicrosoft Defender for SQL: Advanced Threat Protection
55mOffensive Azure Security