Security control has always been a crucial link of data orchestration; data masking falls into this category. For both Internet enterprises and traditional sectors, data security has always been a highly focused and sensitive topic. Data masking refers to transforming some sensitive information through masking 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 masking according to relevant regulations.
Security control has always been a crucial link of orchestration; data masking falls into this category. For both Internet enterprises and traditional sectors, data security has always been a highly focused and sensitive topic. Data masking refers to transforming some sensitive information through masking 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 masking according to relevant regulations.
Because of that, ShardingSphere has provided the function of data masking, 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 masking algorithm, which can directly used by users. In the same time, we have also provided masking 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 masking operations.
| name | String | Data orchestration example name |
| name | String | Orchestration example name |
| overwrite | boolean | Local configurations overwrite registry center configurations or not; if they overwrite, each start takes reference of local configurations |
| regCenterConfig | RegistryCenterConfiguration | Registry center configurations |
sharding.jdbc.config.sharding.encryptRule.encryptors.<encryptor-name>.props.<property-name>= #Properties, e.g. `aes.key.value` for AES encryptor
```
### Data Orchestration
### Orchestration
```properties
#Omit data source, data sharding and read-write split configurations
sharding.jdbc.config.sharding.orchestration.name=#Data orchestration instance name
sharding.jdbc.config.sharding.orchestration.name=#Orchestration instance name
sharding.jdbc.config.sharding.orchestration.overwrite= #Whether to overwrite local configurations with registry center configurations; if it can, each initialization should refer to local configurations
sharding.jdbc.config.sharding.orchestration.registry.type=#Registry center type. Example:zookeeper
sharding.jdbc.config.sharding.orchestration.registry.server-lists= #The list of servers that connect to registry center, including IP and port number; use commas to separate
overwrite:#Whether to overwrite local configurations with registry center configurations; if it can, each initialization should refer to local configurations
registry:#Registry center configuration
serverLists:#The list of servers that connect to registry center, including IP and port number; use commas to seperate addresses, such as: host1:2181,host2:2181
