Encrypt Private Info

After setting up an encryption control record (see Setting up Database Encryption), all new private data that is entered will be encrypted. However, you must use this option to encrypt your existing data. Once existing data is encrypted, you also have the option to re-encrypt it using a current encryption key.

To encrypt private subscriber and account information:

1. In character Circulation, select Encrypt Private Info from the Setup | System | Security menu.
2. Select Add and enter encryption information in the fields described in the table below.

   Field

   Type

   What to enter

   ALL TABLES

   yes/no

   Indicate whether all private data (credit card numbers, bank account numbers, etc.) should be encrypted in all tables. Set this to “n” if you only wish to encrypt certain tables.

   TABLE

   predefined

   If All Tables is set to “n”, indicate the table that should be encrypted. The choices are: AutoRenewSubscription, AutoRenewTran, Carrier, CashTransaction, SubscriptionPayment and SubscriptionRefund.

   UPDATE KEY

   yes/no

   Enter “y” if you want to re-encrypt previously encrypted data using the current encryption control ID.

   OLD CONTROL

   setup

   If you entered “y” above, enter the old encryption control ID of the data you want to re-encrypt.

   EXPORT DATA

   yes/no

   Indicate whether the private information should be exported to an ASCII file before it is encrypted. This is recommended.

   EXPORT TO

   open (50)

   If Export Data is set to “y”, enter the directory to which the data will be exported. The default is /dti/exchange/cm/secure. Each table will be exported to a separate file named [table name].[mmddyy].enc, where the table names are “autosub”, “autotran”, “cashtran”, “carrier”, “subpaymt” and “refund”. For example, if encryption is run on the 14th of May, SubscriptionRefund data would be exported to the file “refund.051404.enc”. Only private information (credit card number, social security number, etc.) will be exported.

3. Select Continue to encrypt the data. The encrypted information will be kept in separate tables and fields, and the original fields will be masked.