Encrypting data for encrypted text fields

We have a new application in Appian that is replacing a legacy application in a fairly closed environment. Because of the nature of our shared tenancy Appian environment the new application uses Encrypted Text fields for some of the sensitive data, and persists the data as encrypted text. There is however, a significant amount of legacy data that we wish to import, is there a method or best practice around encrypting those fields in the legacy data?

OriginalPostID-233829

  Discussion posts and replies are publicly visible

Parents
  • Hi Richard
    One way of achieving this is following:

    1. As a first step dump all your legacy data in the new system database.
    2. Have an utility process in place that will pull your data from the new system database (which you need to store them as encrypted) - this process will then encrypt your data using a!encryptedtext field component wrapped in a rule that will save your encrypted value in your inputs which you can then use them to store them in the database. (If you are on 16.2 you can use a!writetodatastore component directly to write the encrypted text to respective tables in database- else you would need to take the encrypted values in your utility process and then write to database).

    Ideally you can have one interface for every table you wa to write to make sure all your encryption are done.

    Hope this helps !
Reply
  • Hi Richard
    One way of achieving this is following:

    1. As a first step dump all your legacy data in the new system database.
    2. Have an utility process in place that will pull your data from the new system database (which you need to store them as encrypted) - this process will then encrypt your data using a!encryptedtext field component wrapped in a rule that will save your encrypted value in your inputs which you can then use them to store them in the database. (If you are on 16.2 you can use a!writetodatastore component directly to write the encrypted text to respective tables in database- else you would need to take the encrypted values in your utility process and then write to database).

    Ideally you can have one interface for every table you wa to write to make sure all your encryption are done.

    Hope this helps !
Children
No Data