Skip to main content

Azure Cosmos DB - Security Overview

Azure Cosmos DB it is starting to become one of my favourite database for storing content. The integration with reporting and analytics services change the way how we integrate Azure Cosmos DB inside the application ecosystem.
In this post, we take a high-level overview of the security features that Azure Cosmos DB has at this moment in time. Each time when a new type of repository needs to be integrated or used inside a solution, the security requirements need to be validated.

  1. Access Layer: YES, RBAC, Users and Permissions, Master Keys, Resource Keys
  2. Transport Layer: YES, TLS 1.2
  3. Network Layer: YES, IP based filter for inbound traffic and VNET integration
  4. Application Layer: YES, using SDK and API
  5. Storage Layer: YES, data is encrypted

Access control
Network: IP firewall security layer. There is the ability to define policies to filter inbound traffic based on the IP. Once you define the list of approved IPs, requests from any other IPs is refused.
Authorization: There is the ability to use master or resource key to specify access to resources. The access level can be controlled up to document level. Behind the scene, the HMAC authorisation model is used.
Permission: Using the master key, permissions can be generated for RW/R/No access to a different level of an Azure Cosmos DB resources (functions (UDF), triggers, stored procedures, attachment, document, container, database). Permissions are attached to users.
Users: An Azure Cosmos DB database can be associated with one or multiple users. Each user can have specific permissions on the database resources.
RBAC (AD integration): Access to the database can be done using RBAC using existing users and roles that you already defined inside the AD.
Transport: All internal and external communication with Azure Cosmos DB is encrypted using TLS 1.2
Virtual Networks: There is the ability to specify what VNET Azure Cosmos DB can be accessed

Data protection
Local replication: Data is replicated inside the data center in multiple locations, offering an availability SLA of 99.99%.  
Regional failovers: Data can be automatical replicated in multiple Azure Regions around the globe, offering the capability to be protected in case of failover. Using multiple-regions, the read availability reaches 99.999%.
Backups: Automatical backups stored inside redundant storage are done at specific time intervals. All automatical backups are stored for 30 days and can be used to restore the data. Custom backup retention policies and triggers can be defined.
Data storage: Data is encrypted at REST. All data persistent inside Azure Cosmos DB is encrypted.
Geo-fencing: For specific regions around the world (China, US Government, Germany), the data governance is strictly controlled by local authorities or companies.
Attack protection: Azure security response team has a 5-step incident response process that ensures that any incidents are solved as fast as possible with a minimal impact.
Audit and monitoring: Activity logs and audit logging enables users to monitor activity and access to the data. Attacks or abnormal activities can be identified, and the full activity path can be obtained.
Security certifications: There is a long list of certifications and compliances that Azure Cosmos DB has, including SOCS ½ Type 2, PCI DSS Level 1, ISO 27001, HIPA, HITRUST, FedRamp High and so on.

Security tips and tricks
  • 1     Master keys can be regenerated anytime
  • 2.       Master keys cannot be used to granular access to document and containers
  • 3.       Resource keys are created when a user is granted access to specific resources
  • 4.       Resource keys maximum lifetime is 5 hours with a default value of 1 hour
  • 5.       Users are associated with Azure Cosmos DB databases
  • 6.       IP access control restriction changes can take up to 15 minutes to propagate
  • 7.       Column level encryption is available for Table API
  • 8.       There is no support for BYOK or CMK


Popular posts from this blog

ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded

Today blog post will be started with the following error when running DB tests on the CI machine: threw exception: System.InvalidOperationException: The Entity Framework provider type 'System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer' registered in the application config file for the ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See for more information. at System.Data.Entity.Infrastructure.DependencyResolution.ProviderServicesFactory.GetInstance(String providerTypeName, String providerInvariantName) This error happened only on the Continuous Integration machine. On the devs machines, everything has fine. The classic problem – on my machine it’s working. The CI has the following configuration: TeamCity .NET 4.51 EF 6.0.2 VS2013 It see

How to audit an Azure Cosmos DB

In this post, we will talk about how we can audit an Azure Cosmos DB database. Before jumping into the problem let us define the business requirement: As an Administrator I want to be able to audit all changes that were done to specific collection inside my Azure Cosmos DB. The requirement is simple, but can be a little tricky to implement fully. First of all when you are using Azure Cosmos DB or any other storage solution there are 99% odds that you’ll have more than one system that writes data to it. This means that you have or not have control on the systems that are doing any create/update/delete operations. Solution 1: Diagnostic Logs Cosmos DB allows us activate diagnostics logs and stream the output a storage account for achieving to other systems like Event Hub or Log Analytics. This would allow us to have information related to who, when, what, response code and how the access operation to our Cosmos DB was done. Beside this there is a field that specifies what was th

Azure AD and AWS Cognito side-by-side

In the last few weeks, I was involved in multiple opportunities on Microsoft Azure and Amazon, where we had to analyse AWS Cognito, Azure AD and other solutions that are available on the market. I decided to consolidate in one post all features and differences that I identified for both of them that we should need to take into account. Take into account that Azure AD is an identity and access management services well integrated with Microsoft stack. In comparison, AWS Cognito is just a user sign-up, sign-in and access control and nothing more. The focus is not on the main features, is more on small things that can make a difference when you want to decide where we want to store and manage our users.  This information might be useful in the future when we need to decide where we want to keep and manage our users.  Feature Azure AD (B2C, B2C) AWS Cognito Access token lifetime Default 1h – the value is configurable 1h – cannot be modified