Help Center
Go back to application
Help Center
Go back to application
Platform Terms GlossarySupport and Bug Reporting
Task Management
Task Management explained Creating Tasks Setting up Task NotificationsGiving permissions to team members
Organization
Working together in KertosInviting UsersCreating rolesAssigning System AccessCreating Departments and Assigning Users
Integrations
Discovery
Tasks
Device Management
Human Resource Information Systems
Inventory
Inventorization of vendorsInventorization of systemsInventorization of assetsEU AI Act: Inventorization of AI use cases
Risks
Managing risks
Trust Center
Setting up your trust center
Incidents
Reporting incidents
KAIA
KAIA explainedPrinciples of AI at Kertos
Interacting with KAIA
Compliance
Frameworks explainedManaging & implementing controlsCreating & managing policiesCompleting & assigning trainingsGuidance
Privacy Management
Creating a RoPACreating TOMsCreating DPIAs
Data Subject Requests
API Reference
Ingress API Docs for DSRs Webhook API Docs for DSRs
Auto Checks
Auto Checks explainedAuto Checks: AWS Auto Checks: GCPAuto Checks: AzureEnabling Auto Checks by Reconfiguring the Azure IntegrationEnabling Auto Checks by Reconfiguring the GCP IntegrationEnabling Auto Checks by Reconfiguring the AWS Integration
AWS Auto Checks Detailed Explanations
Azure Auto Checks Detailed Explanations
Verify that Server Parameter 'log_retention_days' is greater than 3 days for PostgreSQL Database ServerVerify that server parameter 'connection_throttling' is set to 'ON' for PostgreSQL Database ServerVerify that server parameter 'log_disconnections' is set to 'ON' for PostgreSQL Database ServerVerify that server parameter 'log_connections' is set to 'ON' for PostgreSQL Database ServerVerify that 'Enforce SSL connection' is set to 'ENABLED' for PostgreSQL Database ServerVerify that Server Parameter 'log_checkpoints' is set to 'ON' for PostgreSQL Database ServerVerify that Activity Log Alert exists for Create Policy AssignmentVerify that Activity Log Alert exists for Create or Update Public IP Address ruleVerify that Activity Log Alert exists for Delete SQL Server Firewall RuleVerify that Activity Log Alert exists for Create or Update SQL Server Firewall RuleVerify that Activity Log Alert exists for Delete Network Security GroupVerify that the storage account containing the container with activity logs is encrypted with Customer Managed KeyVerify that Activity Log Alert exists for Delete Policy AssignmentVerify that Activity Log Alert exists for Create or Update Network Security GroupVerify that Diagnostic Setting captures appropriate categoriesVerify that Activity Log Alert exists for Create or Update Security SolutionVerify that Activity Log Alert exists for Delete Public IP Address ruleVerify that logging for Azure AppService 'HTTP logs' is enabledVerify that logging for Azure Key Vault is 'Enabled'Verify that the Expiration Date is set for all Keys in RBAC Key VaultsEnable Role Based Access Control for Azure Key VaultVerify that Private Endpoints are Used for Azure Key VaultVerify that the Key Vault is RecoverableVerify that HTTP(S) access from the Internet is evaluated and restrictedVerify that SSH access from the Internet is evaluated and restrictedVerify that Network Security Group Flow Log retention period is 'greater than 90 days'Verify that Network Watcher is 'Enabled' for all locations in the Azure subscriptionVerify that RDP access from the Internet is evaluated and restrictedVerify that That 'Firewalls & Networks' Is Limited to Use Selected Networks Instead of All NetworksVerify that That Private Endpoints Are Used Where PossibleVerify that 'Enforce SSL connection' is set to 'Enabled' for Standard MySQL Database ServerVerify that 'TLS Version' is set to 'TLSV1.2' for MySQL flexible Database Server

Verify that That 'Firewalls & Networks' Is Limited to Use Selected Networks Instead of All Networks

Framework Reference: A.8.20 Integration: Azure – Cosmos DB

Why this matters
Allowing Azure Cosmos DB accounts to be accessible from all networks — including the public Internet — significantly increases the attack surface. Restricting access to selected virtual networks ensures that only explicitly allowed traffic can reach the database, reducing the risk of unauthorized access and data exfiltration.

What this check does
This Auto Check verifies that Azure Cosmos DB accounts are configured to only allow traffic from selected networks.

Check Logic:
Passes if:

  • publicNetworkAccess = Disabled
    OR
  • publicNetworkAccess = Enabled AND isVirtualNetworkFilterEnabled = true

Fails if:

  • publicNetworkAccess = Enabled AND isVirtualNetworkFilterEnabled = false

This ensures that the database is not exposed to the public Internet and is restricted to a defined list of virtual networks.

How to fix it

Azure Portal:

  1. Go to the Azure portal
  2. Open the Cosmos DB blade
  3. Select the Cosmos DB account
  4. Click on Networking
  5. Under Public network access, select Selected networks
  6. Under Virtual networks, click + Add existing virtual network or + Add new virtual network
  7. For existing networks, select the subscription, virtual network, and subnet
  8. Click Add, then Save

Azure CLI:

az cosmosdb update \  --name <cosmosdb-account-name> \  --resource-group <resource-group> \  --default-action Deny \  --virtual-network-rules "[{id:'/subscriptions/<subscription-id>/resourceGroups/<rg-name>/providers/Microsoft.Network/virtualNetworks/<vnet-name>/subnets/<subnet-name>'}]" 

Confirm configuration:

az cosmosdb show --name <cosmosdb-account-name> --resource-group <resource-group> --query "isVirtualNetworkFilterEnabled" 

PowerShell:

Direct remediation via PowerShell is not explicitly defined in CIS. Use Azure CLI or Portal for enforcement.

Exceptions
None. Cosmos DB accounts should never be open to all networks.

Was this article helpful?

Powered by Product Fruits