Skip to content

Commit 2fdd911

Browse files
committed
Adding docs content for validation of Data encryption
1 parent e516578 commit 2fdd911

File tree

2 files changed

+24
-20
lines changed

2 files changed

+24
-20
lines changed

articles/mysql/howto-data-encryption-validation.md

Lines changed: 12 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -16,35 +16,37 @@ This article helps you validate that data encryption using customer managed key
1616

1717
### From portal
1818

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:
2020

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**.
2424

2525
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.
2626

2727
In order to make the server **Available** against, you can revalidate the key.
2828

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**.
3232

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.
3434

3535
![Access policy overview](media/concepts-data-access-and-security-data-encryption/byokvalidate.png)
3636

3737
### From CLI
3838

39-
* 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.
4040

4141
```azurecli-interactive
4242
az mysql server key list --name '<server_name>' -g '<resource_group_name>'
4343
```
4444
4545
For a server without Data encryption set, this command results in empty set [].
4646
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.
4850
4951
## Next steps
5052

articles/postgresql/howto-data-encryption-validation.md

Lines changed: 12 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -16,35 +16,37 @@ This article helps you validate that data encryption using customer managed key
1616

1717
### From portal
1818

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:
2020

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**.
2424

2525
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.
2626

2727
In order to make the server **Available** against, you can revalidate the key.
2828

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**
3232

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.
3434

3535
![Access policy overview](media/concepts-data-access-and-security-data-encryption/byokvalidate.png)
3636

3737
### From CLI
3838

39-
* 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.
4040

4141
```azurecli-interactive
4242
az postgres server key list --name '<server_name>' -g '<resource_group_name>'
4343
```
4444
4545
For a server without Data encryption set, this command will results in empty set [].
4646
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.
4850
4951
## Next steps
5052

0 commit comments

Comments
 (0)