Microsoft AzureOverview
Azure Database for PostgreSQL servers should be created with 'infrastructure double encryption' enabled.
NOTE: This recommendation currently only applies to Single Server, not Flexible Server. See the additional information below for details about the planned retirement of Azure PostgreSQL Single Server.
Rationale
If Double Encryption is enabled, another layer of encryption is implemented at the hardware level before the storage or network level. Information will be encrypted before it is even accessed, preventing interception of data in motion if the network layer encryption is broken and data is at rest in system resources such as memory or processor cache. Encryption will also be in place for any backups taken of the database so that the key will secure access to the data in all forms. For the most secure implementation of key-based encryption, it is recommended to use a Customer-managed asymmetric RSA 2048 Key in Azure Key Vault.
Impact
The read and write speeds to the database will be impacted if both default encryption and Infrastructure Encryption are checked, as a secondary form of encryption requires more resource overhead for the cryptography of information. This cost is justified for information security.
Customer-managed keys are recommended for the most secure implementation, leading to the overhead of key management. The key will also need to be backed up in a secure location, as losing the key will mean losing the information in the database.
Default Value
By default, Double Encryption is disabled.
Additional Information
RETIREMENT of Azure PostgreSQL Single Server: Azure PostgreSQL Single Server is slated for retirement by March 25, 2025. Please use these resources to consider and prepare for migration:
Remediation guidance
It is not possible to enable 'infrastructure double encryption' on an existing Azure Database for PostgreSQL server.
The remediation steps detail creating a new Azure Database for PostgreSQL server with 'infrastructure double encryption' enabled.
Remediate from Azure Portal
- Go through the normal process of database creation.
- On step 2 titled
Additional settingsensure thatInfrastructure double encryption enabledis checked. - Acknowledge that you understand this will impact database performance.
- Finish database creation as normal.
Remediate from Azure CLI
az postgres server create --resource-group <resourcegroup> --name <servername> --location <location> --admin-user <adminusername> --admin-password <server_admin_password> --sku-name GP_Gen4_2 --version 11 --infrastructure-encryption Enabled
Service-wide remediation
Recommended when many resources are affected: fix the platform baseline first so new resources inherit the secure setting, then remediate the existing flagged resources in batches.
Azure
Use management group or subscription Azure Policy assignments, remediation tasks where supported, landing-zone standards, and IaC modules so drift is prevented at scale.
Operational rollout
- Fix the baseline first at the account, subscription, project, cluster, or tenant scope that owns this control.
- Remediate the currently affected resources in batches, starting with internet-exposed and production assets.
- Re-scan and track approved exceptions with an owner and expiry date.
Query logic
These are the stored checks tied to this control.
Azure Postgres Single Servers without infrastructure encryption
Connectors
Covered asset types
Expected check: eq []
{
postgreSqlServers(where: { infrastructureEncryption: "Disabled" }) {
...AssetFragment
}
}
