Prerequisites to Use Customer-Managed
Encryption Keys in Azure Key Vault 🔗
Describes prerequisite steps to use customer-managed master encryption keys
on Autonomous Database that reside in Azure Key
Vault.
Limitations:
Azure Key Vault is only supported in commercial regions.
Cross-tenancy access, where the Autonomous Database instance and
the Azure Key Vault are in different tenancies, is not supported.
Azure Key Vault is not supported in cross-region standbys.
Azure Key Vault is not supported in refreshable clones.
Supported key shapes and sizes are the following:
RSA 2048
EC P-256
Follow these steps:
Create an Autonomous Database
instance that uses the default Encryption key setting of Encrypt using an
Oracle-managed key. See Provision an Autonomous Database Instance for more information.
Note
Encryption key settings
for customer-managed keys in Azure Key Vault are not available during the
creation process. The options are available post provisioning, when editing
the instance.
Create an Azure Key Vault with a Transparent Data Encryption (TDE) master
key.
Enable Azure service principal authentication with the Azure Directory
tenant_id to allow your Autonomous Database instance access to
the Azure Key Vault.
Obtain your Microsoft Azure Active Directory tenant ID.
Enable Azure service principal with
DBMS_CLOUD_ADMIN.ENABLE_PRINCIPAL_AUTH. The value
of azure_tenantid is the Azure Directory ID you
obtained in the previous step.
For
example:
BEGIN
DBMS_CLOUD_ADMIN.ENABLE_PRINCIPAL_AUTH(
provider => 'AZURE',
params => JSON_OBJECT('azure_tenantid' value 'azure_directoryID'));
END;
/
This enables Azure service principal authentication and
creates an Azure application for Autonomous Database on the
Azure portal. See Enable Azure Service Principal for more information.
Provide the Azure application consent to access Azure resources from Autonomous Database.
For Permissions on the Create an access policy page, select all Key
permissions, including: Key Management Operations, Cryptography
Operations, Privileged Key Operations, and Rotation Policy Operations
and click Next.
For Principal, search the application name.
Select the displayed application name and click Next.
For Application (optional), select Next.
For Review + create, review the policy details and click
Create.
On the Azure Key Vault details page, click Refresh and search for the
application name. It is included in the displayed list of applications
with permission to access keys in this Azure Key Vault.
On the Details page, from the More actions drop-down list, select
Manage encryption key.
Note
If you are already using customer-managed Transparent Data
Encryption (TDE) keys stored in Azure Key Vault and you want to rotate
the keys, follow these steps and select a different key (select a key
that is different from the currently selected master TDE key).
On the Manage encryption key page, select Encrypt using a
customer-managed key.
From the Key type drop-down, select Microsoft Azure.
Enter the copied Azure key name into the Key name field in the
Autonomous Database Manage
encryption key page.
Click Save.
The Lifecycle state changes to
Updating. When the request completes, the
Lifecycle state shows
Available.
After the request completes, on the Oracle Cloud
Infrastructure Console, the key information shows on the Autonomous Database Information page
under the heading Encryption. This area shows the
Encryption Key is Customer-managed key (Microsoft
Azure), and displays the Vault URI and Key name.