Yes, I believe this is the correct field.  My other question is, is there a way to change this key without having to decrypt the existing data, and then re-encrypt that data, or is that the only way to change this key and still retain access to the encrypted information?

Thanks,

Pheng

You will have to decrypt and reencrypt -- that's the nature of encryption.

Are you perhaps looking at some PCI compliance requirements? You should be aware that since 15.1.2, iMIS has included PCI compliance features, including the ability to reassign the encryption key and reencrypt all the data using the new key.
--
Bruce Wilson
Director, Technical Services
RSM McGladrey, Inc.

Thank's Bruce, I assumed as much; and yes, this is for PCI compliance.

Thanks again,

Pheng

I suspected as much.  Since the "advanced PCI compliance" feature is a standard, supported part of iMIS, that would definitely be the preferred approach.  Creating your own would introduce some risks (Did you catch all the fields?  How does it recover if it fails mid-operation? How does it handle new transactions that come in while reencrypting?), and it's far easier to say "yes, iMIS does this for us" than "yes, we have built something".

While the CPI compliance feature was added in 15.1.2, it may work in previous versions too.  This usage wouldn't be supported by ASI, but if it does the right thing without having to reinvent the wheel, bonus!  Naturally, you'd have to have at least some version of iMIS 15 already.

--
Bruce Wilson
Director, Technical Services
RSM McGladrey, Inc.