Enhancement Request for Application-Level Encryption of Sensitive PII Data in IBM Identity Insight Database (DB2)

We currently use IBM Identity Insight for Galactic ID generation, which serves as a unique identifier for our customers. At present, customer data within Identity Insight is stored in a DB2 database as unencrypted (plain-text) values.

To align with our Information Security requirements, we would like Identity Insight to support application-level encryption of sensitive PII data prior to persistence in the database.

As Identity Insight utilizes customer information during the Galactic ID generation process, we are seeking an enhancement that provides a native capability to encrypt sensitive data before storage and decrypt it when required by the application. This would help ensure that sensitive customer information remains protected while preserving existing application functionality.

Additionally, we request that the proposed solution address the following considerations:

We maintain a large volume of historical customer records and their associated Galactic IDs. As a result, we require a mechanism to encrypt existing data that is currently stored in plain text within the EAS tables.

What migration strategy would you recommend to encrypt historical records while ensuring there is no business disruption and no impact on the Galactic ID generation process?

Our objective is to leverage Identity Insight's native capabilities and establish a secure, scalable approach for encrypting both new and existing customer data, while ensuring seamless continuity of business operations.