Compliancemanzill.com
CIS Microsoft Azure Foundations Benchmark v1.4.0

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

4.3.8Ensure 'Infrastructure double encryption' for PostgreSQL Database Server is 'Enabled'

Control family: Database Services

Control description

Enable encryption at rest for PostgreSQL Databases.

How to implement

ResponsibilityCustomerYou configure and operate this in your own cloud accounts.

Infrastructure double encryption was a Single Server option that added a second layer of encryption at rest. Flexible server doesn't offer it: data is always encrypted at rest, with service-managed keys by default or a customer-managed key chosen when the server is created. Choosing a customer-managed key gives the extra control this recommendation is after. 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.

  • Decide which PostgreSQL servers hold data critical enough for a customer-managed key, and record that service-managed encryption is accepted for the rest.

Evidence

  • The recorded decision per server

On Azure the tasks create new flexible servers with a customer-managed key, and record the decision for existing ones.

Task 1Create servers with a customer-managed key

  1. Sign in to the Azure portal at portal.azure.com and start creating an Azure Database for PostgreSQL flexible server.
  2. On the Security tab, under data encryption, choose Customer managed key.
  3. Select a user-assigned managed identity and a key from a key vault with purge protection on (8.6).
  4. Finish the other tabs and select Create.
  5. Check it: the server's Data encryption page shows the customer-managed key.

Task 2Record the decision for existing servers

  1. List flexible servers that use service-managed keys from each server's Data encryption page.
  2. For servers holding critical data, plan a move to a new server with a customer-managed key, since the key type can't be changed after creation.
  3. For the rest, record that service-managed encryption at rest is accepted and why.

Evidence

  • The Data encryption page of each flexible server
  • The recorded decision for servers that keep service-managed keys

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.