tristaZero commented on a change in pull request #101: Sharding-JDBC manual 
modification
URL: 
https://github.com/apache/incubator-shardingsphere-doc/pull/101#discussion_r267257592
 
 

 ##########
 File path: document/current/content/features/orchestration/encrypt.en.md
 ##########
 @@ -1,15 +1,42 @@
 +++
 pre = "<b>3.3.5. </b>"
 toc = true
-title = "Data Masking"
+title = "Data Desensitization"
 weight = 5
+
 +++
 
 ## Background
-TODO
 
-## Solutions
+Security control has always been a crucial link of data orchestration; data 
desensitization falls into this category. For both Internet enterprises and 
traditional sectors, data security has always been a highly focused and 
sensitive topic. Data desensitization refers to transforming some sensitive 
information through desensitization rules to safely protect the private data. 
Data that involves client security or business sensibility, such as ID number, 
phone number, card number, client number and other personal information, is 
required of data desensitization according to relevant regulations.
+
+Because of that, ShardingSphere has provided the function of data 
desensitization, which stores users' sensitive information in the database 
after encryption. When users search for them, they will be decrypted and 
returned to users as the original data. It has the encryption and decryption 
processes totally transparent to users, who can store desensitized data and 
acquire original data without any awareness. In addition, ShardingSphere has 
provided internal desensitization algorithm, which can directly used by users. 
In the same time, we have also provided desensitization algorithm related 
interfaces, which can be implemented by users themselves. Then, after simple 
configurations, ShardingSphere can use algorithms provided by users to perform 
encryption, decryption and desensitization operations.
 
 Review comment:
   `When users search for them` ---> `When user query them in dataBases`

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


With regards,
Apache Git Services

Reply via email to