PostgreSQL servers should use customer-managed keys to encrypt data at rest
Use customer-managed keys to manage the encryption at rest of your PostgreSQL servers. By default, the data is encrypted at rest with service-managed keys. Customer-managed keys enable the data to be encrypted with an Azure Key Vault key created and owned by you.
By default, the data is encrypted at rest with service-managed keys, but customer-managed keys are commonly required to meet regulatory compliance standards. Customer-managed keys enable the data to be encrypted with an Azure Key Vault key created and owned by you. You have full control and responsibility for the key lifecycle, including rotation and management.
What this control checks
Pass/fail result for the PostgreSQL server encryption at rest with customer-managed keys check
Common pitfalls
Default is service-managed keys
By default, the data is encrypted at rest with service-managed keys.
Audit evidence
Evidence that deployed resources meet this control: PowerPipe control azure_compliance.control.postgres_sql_server_encrypted_at_rest_using_cmk.
Framework-specific interpretation
NIST SP 800-53 Rev 5: Mapped to SC-12 (Cryptographic Key Establishment and Management).
Framework mappings
The clauses this control is mapped to in each framework.
- Cryptographic Key Establishment And Management (SC-12)
- 3.13.10 Establish and manage cryptographic keys for cryptography employed in organizational systems
- 3.1.h Public Key Infrastructure (PKI)
- SC-12 Cryptographic Key Establishment And Management
Related controls
Tool mappings
Use these identifiers to cross-reference this control across tools, reports, and evidence.
- Compliance.tf Control:
postgres_sql_server_encrypted_at_rest_using_cmk - Powerpipe Control:
azure_compliance.control.postgres_sql_server_encrypted_at_rest_using_cmk
Last reviewed: 2026-10-14