Compliancemanzill.com
CIS Microsoft Azure Foundations Benchmark v1.4.0

CIS Microsoft Azure Foundations Benchmark v1.4.0/Database Services/64 of 115

4.3.7Ensure 'Allow access to Azure services' for PostgreSQL Database Server is disabled

Control family: Database Services

Control description

Disable access from Azure services to PostgreSQL Database Server

How to implement

ResponsibilityCustomerYou configure and operate this in your own cloud accounts.

The option to allow access from any Azure service opens the server to every address inside Azure, including other customers' resources, not just yours. It is turned off, and the server is reached through a virtual network or named firewall rules. Azure Database for PostgreSQL Single Server was retired on 28 March 2025, so this applies to flexible servers.

Before you start

The same on every cloud, before the steps in the tabs.

  • Agree how applications reach PostgreSQL servers: a virtual network, a private endpoint or named firewall rules, never access from all of Azure.
  • List the approved firewall rules and their owners.

Evidence

  • The database network access standard and the list of firewall rules

On Azure the tasks clear the option in each flexible server's networking settings, then check what can still connect.

Task 1Turn off access from all Azure services

  1. Sign in to the Azure portal at portal.azure.com and open Azure Database for PostgreSQL flexible servers, then the server.
  2. Select Settings > Networking.
  3. Clear Allow public access from any Azure service within Azure to this server.
  4. Add firewall rules for the specific addresses that need access, or move the server to private access with a virtual network or private endpoint.
  5. Select Save.
  6. Check it: a connection from an unlisted Azure address is refused, while the applications still connect.

Task 2Review the remaining firewall rules

  1. On the same Networking page, list every firewall rule.
  2. Remove any rule covering 0.0.0.0 to 255.255.255.255 or other wide ranges, and any whose purpose nobody can explain.
  3. Record the owner and purpose of each rule that stays.

Evidence

  • Networking of each flexible server, with access from all Azure services off
  • The list of firewall rules and their owners

Console steps as of 5 November 2026. Not every step has been confirmed in a live console yet, and menus and labels can move between releases, so look for the nearest match if one has changed.