Help Center/ Database Security Service/ User Guide/ Database Encryption/ Series 2/ Deployment Process
Updated on 2026-09-24 GMT+08:00
View PDF
Share

Deployment Process

The database encryption system offers the most granular data security capabilities (at the column level) and the highest security tier (at the column content level), making it one of the few data security technologies that provides a five-layer protection framework.

The high security level also imposes stringent requirements on the deployment process, particularly the need for comprehensive testing of all operations involving encrypted fields after encryption has been applied.

The following provides a detailed description of the deployment process for the Application-Plugin pattern and the Proxy pattern.

The encryption process involves encrypting the data content; therefore, comprehensive testing before deployment is crucial – particularly for business processes and operations that are affected by encrypted fields.

Prerequisite

  • Identify which data types should be encrypted, such as phone numbers, ID cards, etc.
  • The data fields to be encrypted have been identified.

Plugin Mode Deployment Process

The plugin deployment process includes the following core steps:

  • Test environment deployment and testing.
  • Official environment deployment, verification, and go-live.

Specific tasks include:

  1. Configure Asset Database.
  2. Define the encryption rules and encryption keys to be used by this business system.
  3. Configure encryption rules and keys for fields that require encryption.
  4. Encrypt existing historical data.
  5. Pre-Release phase (no actual encryption performed; deployment plugin functionality is verified).
  6. Download the plugin.
  7. Deploy the plugin.
  8. encrypted business system functional testing and performance impact testing.
  9. Officially launched.

Proxy Pattern Deployment Process

The implementation process for the Proxy Pattern includes the following core steps:

  • Test environment deployment and testing.
  • Official environment deployment, verification, and go-live.

Specific tasks include:

  1. Configure asset database.
  2. Define the encryption rules and encryption keys to be used by this business system.
  3. Configure encryption rules and keys for fields that require encryption.
  4. Encrypt existing historical data.
  5. Configure proxy service.
  6. The configuration application directs the database connection to the proxy service.
  7. Pre-Release phase (no actual encryption performed; deployment plugin functionality is verified).
  8. encrypted business system functional testing and performance impact testing.
  9. Officially launched.
Parent Topic: Series 2