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.
Overview
- Access Layer: YES, RBAC, Users and Permissions, Master Keys, Resource Keys
- Transport Layer: YES, TLS 1.2
- Network Layer: YES, IP based filter for inbound traffic and VNET integration
- Application Layer: YES, using SDK and API
- 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
Comments
Post a Comment