📝 Azure Cosmos DB Account Virtual Network Filter is not enabled 🟢

• Contextual name: 📝 Virtual Network Filter is not enabled 🟢
• ID: /ce/ca/azure/cosmos-db/virtual-network-filter
• Located in: 📁 Azure Cosmos DB

Flags

• 🟢 Policy with categories
• 🟢 Policy with type
• 🟢 Production policy

Our Metadata

• Policy Type: COMPLIANCE_POLICY
• Policy Category:
  • SECURITY

Similar Policies

• Cloud Conformity
  • Restrict Default Network Access for Azure Cosmos DB Accounts
• Internal
  • dec-x-46a83a30

Similar Internal Rules

Rule	Policies	Flags
✉️ dec-x-46a83a30	1

Logic

• 🧠 prod.logic.yaml 🟢
  • 📕 Azure Cosmos DB Account
  • 🔌 Azure Cosmos DB Account - object.extracts.yaml
  • 🧪 test-data.json

Description

Open File

Description

Limiting your Cosmos DB to only communicate on whitelisted networks lowers its attack footprint.

Rationale

Selecting certain networks for your Cosmos DB to communicate restricts the number of networks including the internet that can interact with what is stored within the database.

Impact

WARNING: Failure to whitelist the correct networks will result in a connection loss.

WARNING: Changes to Cosmos DB firewalls may take up to 15 minutes to apply. Ensure that sufficient time is planned for remediation or changes to avoid disruption.

Audit

From Azure Portal

1. Open the portal menu.
2. Select the Azure Cosmos DB blade.
3. Select a Cosmos DB to audit.
4. Select Networking.
5. Under Public network access, ensure Selected networks is selected.
6. Under Virtual networks, ensure appropriate virtual networks are configured.

From Azure CLI

Retrieve a list of all CosmosDB database names:

az cosmosdb list

For each database listed, run the following command:

az cosmosdb show <database id>

... [see more](description.md)

Remediation

Open File

Remediation

From Azure Portal

1. Open the portal menu.

2. Select the Azure Cosmos DB blade.

3. Select a Cosmos DB account to audit.

4. Select Networking.

5. Under Public network access, select Selected networks.

6. Under Virtual networks, select + Add existing virtual network or + Add a new virtual network.

7. For existing networks, select subscription, virtual network, subnet and click Add.

   For new networks, provide a name, update the default values if required, and click Create.

8. Click Save.

policy.yaml

Open File

Linked Framework Sections

Section	Sub Sections	Internal Rules	Policies	Flags
💼 APRA CPG 234 → 💼 36d access management controls —only authorised users, software and hardware are able to access information assets (refer to Attachment B for further guidance);		13	14
💼 APRA CPG 234 → 💼 36e hardware and software asset controls —appropriate authorisation to prevent security compromises from unauthorised hardware and software assets;		15	16
💼 APRA CPG 234 → 💼 36f network design — to ensure authorised network traffic flows and to reduce the impact of security compromises;		26	28
💼 APRA CPG 234 → 💼 45 An understanding of plausible worst case scenarios can help regulated entities identify and implement additional controls to prevent or reduce the impact of such scenarios. One example is malware that infects computers and encrypts data, both on the infected computer and any connected storage, including (corporate) networks and cloud storage. Such attacks reinforce the importance of protecting the backup environment in the event that the production environment is compromised. Common techniques to achieve this include network segmentation, highly restricted and segregated access controls and network traffic flow restrictions.		32	35
💼 APRA CPG 234 → 💼 52d appropriate segmentation of data, based on sensitivity and access needs;		10	10
💼 APRA CPG 234 → 💼 53 Wholesale access to sensitive data (e.g. contents of customer databases or intellectual property that can be exploited for personal gain) would be highly restricted to reduce the risk exposure to significant data leakage events. Industry experience of actual data leakage incidents include the unauthorised extraction of debit/credit card details, theft of personally identifiable information, loss of unencrypted backup media and the sale/trade or exploitation of customer identity data.		10	10
💼 CIS Azure v2.1.0 → 💼 4.5.1 Ensure That 'Firewalls & Networks' Is Limited to Use Selected Networks Instead of All Networks - Level 2 (Automated)			1
💼 CIS Azure v3.0.0 → 💼 5.4.1 Ensure That 'Firewalls & Networks' Is Limited to Use Selected Networks Instead of All Networks (Automated)			1
💼 Cloudaware Framework → 💼 Public and Anonymous Access			69
💼 FedRAMP High Security Controls → 💼 AC-3 Access Enforcement (L)(M)(H)		35	46
💼 FedRAMP High Security Controls → 💼 AC-4(21) Physical or Logical Separation of Information Flows (M)(H)		11	38
💼 FedRAMP Low Security Controls → 💼 AC-3 Access Enforcement (L)(M)(H)			46
💼 FedRAMP Moderate Security Controls → 💼 AC-3 Access Enforcement (L)(M)(H)			46
💼 FedRAMP Moderate Security Controls → 💼 AC-4(21) Physical or Logical Separation of Information Flows (M)(H)			38
💼 ISO/IEC 27001:2013 → 💼 A.9.4.1 Information access restriction		17	19
💼 NIST CSF v1.1 → 💼 PR.AC-4: Access permissions and authorizations are managed, incorporating the principles of least privilege and separation of duties		15	34
💼 NIST CSF v1.1 → 💼 PR.DS-5: Protections against data leaks are implemented		41	50
💼 NIST CSF v1.1 → 💼 PR.IP-1: A baseline configuration of information technology/industrial control systems is created and maintained incorporating security principles (e.g. concept of least functionality)		2	13
💼 NIST CSF v1.1 → 💼 PR.PT-3: The principle of least functionality is incorporated by configuring systems to provide only essential capabilities		21	25
💼 NIST CSF v2.0 → 💼 PR.AA-05: Access permissions, entitlements, and authorizations are defined in a policy, managed, enforced, and reviewed, and incorporate the principles of least privilege and separation of duties			57
💼 NIST CSF v2.0 → 💼 PR.DS-01: The confidentiality, integrity, and availability of data-at-rest are protected			81
💼 NIST CSF v2.0 → 💼 PR.DS-02: The confidentiality, integrity, and availability of data-in-transit are protected			68
💼 NIST CSF v2.0 → 💼 PR.DS-10: The confidentiality, integrity, and availability of data-in-use are protected			66
💼 NIST SP 800-53 Revision 4 → 💼 CM-7 LEAST FUNCTIONALITY	5	4	5
💼 NIST SP 800-53 Revision 5 → 💼 AC-4(21) Information Flow Enforcement _ Physical or Logical Separation of Information Flows		33	38
💼 PCI DSS v3.2.1 → 💼 1.3 Prohibit direct public access between the Internet and any system component in the cardholder data environment.	7	7	10
💼 PCI DSS v3.2.1 → 💼 1.3.1 Implement a DMZ to limit inbound traffic to only system components that provide authorized publicly accessible services, protocols, and ports.		5	7
💼 PCI DSS v3.2.1 → 💼 1.3.2 Limit inbound Internet traffic to IP addresses within the DMZ.			7
💼 PCI DSS v3.2.1 → 💼 1.3.5 Permit only “established” connections into the network.			7
💼 PCI DSS v4.0.1 → 💼 1.4.1 NSCs are implemented between trusted and untrusted networks.			9
💼 PCI DSS v4.0.1 → 💼 1.4.2 Inbound traffic from untrusted networks to trusted networks is restricted.			7
💼 PCI DSS v4.0 → 💼 1.4.1 NSCs are implemented between trusted and untrusted networks.			9
💼 PCI DSS v4.0 → 💼 1.4.2 Inbound traffic from untrusted networks to trusted networks is restricted.			7
💼 SOC 2 → 💼 CC6.1-6 Manages Points of Access		5	6
💼 UK Cyber Essentials → 💼 1.2 Prevent access to the administrative interface from the internet		33	36