compliance.tf
Azure Compliance ControlsAzure Database for MySQL

MySQL servers should use customer-managed keys to encrypt data at rest

Use customer-managed keys to manage the encryption at rest of your MySQL 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.

What this control checks

MySQL servers must have a key of serverKeyType AzureKeyVault with a non-empty uri

Framework mappings

The clauses this control is mapped to in each framework.

NIST SP 800-53 Rev 5

  • Cryptographic Key Establishment And Management (SC-12)

FedRAMP Moderate Baseline Rev 4

  • SC-12 Cryptographic Key Establishment And Management

NIST SP 800-171 Rev 2

  • 3.13.10 Establish and manage cryptographic keys for cryptography employed in organizational systems

CIS Azure Benchmark v4.0.0

  • 2.1.1.2.1 Ensure Critical Data is Encrypted with Customer Managed Keys (CMK)

RBI IT Framework for NBFCs

  • 3.1.h Public Key Infrastructure (PKI)

CMMC 2.0 Level 2

  • SC.L2-3.13.10 Establish and manage cryptographic keys for cryptography employed in organizational systems

FedRAMP High

  • SC-12 Cryptographic Key Establishment And Management

Tool mappings

Use these identifiers to cross-reference this control across tools, reports, and evidence.

  • Compliance.tf Control: mysql_server_encrypted_at_rest_using_cmk
  • Checkov Check: CKV2_AZURE_16
  • Powerpipe Control: azure_compliance.control.mysql_server_encrypted_at_rest_using_cmk
  • Azure Policy Definition: 83cef61d-dbd1-4b20-a4fc-5fbc7da10833

Last reviewed: 2026-10-13

View all Azure controls →

On this page

Ask AI about this

Help improve this page