You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/mysql/howto-data-encryption-validation.md
+12-10Lines changed: 12 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,35 +16,37 @@ This article helps you validate that data encryption using customer managed key
16
16
17
17
### From portal
18
18
19
-
* If you want to verify that the customer's key is used for encryption, follow these steps:
19
+
1. If you want to verify that the customer's key is used for encryption, follow these steps:
20
20
21
-
1. In the Azure portal, navigate to the **Azure Key Vault** -> **Keys**
22
-
2. Select the key used for server encryption.
23
-
3. Set the status of the key **Enabled** to **No**.
21
+
* In the Azure portal, navigate to the **Azure Key Vault** -> **Keys**
22
+
* Select the key used for server encryption.
23
+
* Set the status of the key **Enabled** to **No**.
24
24
25
25
After some time (**~15 min**), the Azure Database for MySQL server **Status** should be **Inaccessible**. Any I/O operation done against the server will fail which validates that the server is indeed encrypted with customers key and the key is currently not valid.
26
26
27
27
In order to make the server **Available** against, you can revalidate the key.
28
28
29
-
4. Set the status of the key in the Key Vault to **Yes**.
30
-
4. On the server **Data Encryption**, select **Revalidate key**.
31
-
5. After the revalidation of the key is successful, the server **Status** changes to **Available**.
29
+
* Set the status of the key in the Key Vault to **Yes**.
30
+
* On the server **Data Encryption**, select **Revalidate key**.
31
+
* After the revalidation of the key is successful, the server **Status** changes to **Available**.
32
32
33
-
* On the Azure portal, if you can ensure that the encryption key is set, then data is encrypted using the customers key used in the Azure portal.
33
+
2. On the Azure portal, if you can ensure that the encryption key is set, then data is encrypted using the customers key used in the Azure portal.
* We can use *az CLI* command to validate the key resources being used for the Azure Database for MySQL server.
39
+
1. We can use *az CLI* command to validate the key resources being used for the Azure Database for MySQL server.
40
40
41
41
```azurecli-interactive
42
42
az mysql server key list --name '<server_name>' -g '<resource_group_name>'
43
43
```
44
44
45
45
For a server without Data encryption set, this command results in empty set [].
46
46
47
-
* [Audit Reports](https://servicetrust.microsoft.com) can also be reviewed that provides information about the compliance with data protection standards and regulatory requirements.
47
+
### Azure audit reports
48
+
49
+
[Audit Reports](https://servicetrust.microsoft.com) can also be reviewed that provides information about the compliance with data protection standards and regulatory requirements.
Copy file name to clipboardExpand all lines: articles/postgresql/howto-data-encryption-validation.md
+12-10Lines changed: 12 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,35 +16,37 @@ This article helps you validate that data encryption using customer managed key
16
16
17
17
### From portal
18
18
19
-
* If you want to verify that the customer's key is used for encryption, follow these steps:
19
+
1. If you want to verify that the customer's key is used for encryption, follow these steps:
20
20
21
-
1. In the Azure portal, navigate to the **Azure Key Vault** -> **Keys**
22
-
2. Select the key used for server encryption.
23
-
3. Set the status of the key **Enabled** to **No**.
21
+
* In the Azure portal, navigate to the **Azure Key Vault** -> **Keys**
22
+
* Select the key used for server encryption.
23
+
* Set the status of the key **Enabled** to **No**.
24
24
25
25
After some time (**~15 min**), the Azure Database for PostgreSQL server **Status** should be **Inaccessible**. Any I/O operation done against the server will fail which validates that the server is indeed encrypted with customers key and the key is currently not valid.
26
26
27
27
In order to make the server **Available** against, you can revalidate the key.
28
28
29
-
4. Set the status of the key in the Key Vault to **Yes**.
30
-
4. On the server **Data Encryption**, select **Revalidate key**.
31
-
5. After the revalidation of the key is successful, the server **Status** changes to **Available**
29
+
* Set the status of the key in the Key Vault to **Yes**.
30
+
* On the server **Data Encryption**, select **Revalidate key**.
31
+
* After the revalidation of the key is successful, the server **Status** changes to **Available**
32
32
33
-
* On the Azure portal, if you can ensure that the encryption key is set, then data is encrypted using the customers key used in the Azure portal.
33
+
2. On the Azure portal, if you can ensure that the encryption key is set, then data is encrypted using the customers key used in the Azure portal.
* We can use *az CLI* command to validate the key resources being used for the Azure Database for PostgreSQL server.
39
+
1. We can use *az CLI* command to validate the key resources being used for the Azure Database for PostgreSQL server.
40
40
41
41
```azurecli-interactive
42
42
az postgres server key list --name '<server_name>' -g '<resource_group_name>'
43
43
```
44
44
45
45
For a server without Data encryption set, this command will results in empty set [].
46
46
47
-
* [Audit Reports](https://servicetrust.microsoft.com) can also be reviewed that provides information about the compliance with data protection standards and regulatory requirements.
47
+
### Azure audit reports
48
+
49
+
[Audit Reports](https://servicetrust.microsoft.com) can also be reviewed that provides information about the compliance with data protection standards and regulatory requirements.
0 commit comments