Skip to content

Commit e516578

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

File tree

2 files changed

+12
-17
lines changed

2 files changed

+12
-17
lines changed

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

Lines changed: 7 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ ms.date: 04/28/2020
1010

1111
# Validating data encryption for Azure Database for MySQL
1212

13-
This articles helps you validate that data encryption using customer managed key for Azure Database for MySQL is working as expected.
13+
This article helps you validate that data encryption using customer managed key for Azure Database for MySQL is working as expected.
1414

1515
## Check the encryption status
1616

@@ -24,27 +24,25 @@ This articles helps you validate that data encryption using customer managed key
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

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

2929
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 resumes its normal functionality.
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**.
3232

33-
* On the Azure Portal if can ensure that the encryption key is set this would mean that the data is encrypted using the key used in the Azure portal.
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.
3434

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

37-
This ensures that the data encryption using the customers key in the Azure key vault is being used.
38-
3937
### From CLI
4038

41-
* We can use *az cli* command to validate the key resources being used for the Azure Database for MySQL server.
39+
* We can use *az CLI* command to validate the key resources being used for the Azure Database for MySQL server.
4240

4341
```azurecli-interactive
4442
az mysql server key list --name '<server_name>' -g '<resource_group_name>'
4543
```
4644
47-
For a server without Data encryption set, this command will results in empty set [].
45+
For a server without Data encryption set, this command results in empty set [].
4846
4947
* [Audit Reports](https://servicetrust.microsoft.com) can also be reviewed that provides information about the compliance with data protection standards and regulatory requirements.
5048

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

Lines changed: 5 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ ms.date: 04/28/2020
1010

1111
# Validating data encryption for Azure Database for PostgreSQL
1212

13-
This articles helps you validate that data encryption using customer managed key for Azure Database for PostgreSQL is working as expected.
13+
This article helps you validate that data encryption using customer managed key for Azure Database for PostgreSQL is working as expected.
1414

1515
## Check the encryption status
1616

@@ -27,19 +27,16 @@ This articles helps you validate that data encryption using customer managed key
2727
In order to make the server **Available** against, you can revalidate the key.
2828

2929
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 resumes its normal functionality.
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**
3232

33-
* On the Azure Portal if can ensure that the encryption key is set this would mean that the data is encrypted using the key used in the Azure portal.
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.
3434

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

37-
This ensures that the data encryption using the customers key in the Azure key vault is being used.
38-
39-
4037
### From CLI
4138

42-
* We can use *az cli* command to validate the key resources being used for the Azure Database for PostgreSQL server.
39+
* We can use *az CLI* command to validate the key resources being used for the Azure Database for PostgreSQL server.
4340

4441
```azurecli-interactive
4542
az postgres server key list --name '<server_name>' -g '<resource_group_name>'

0 commit comments

Comments
 (0)