Encrypting the Payload on Database Level

Use

For more data security, you have the option of encrypting the payload for postprocessing orders on database level. This means that all corresponding, configured payloads for postprocessing orders are stored in the database in encrypted form. Users, who start a database query, for example with SQL, cannot read the payload contents. For more information about the use of payloads according to the PCI standard, see Using ECH Payloads in PCI-Compliant Processes.

Procedure

Configuration Tasks

  1. Define the encryption key.

  2. Define your Personal Security Environment (PSE).

For more detailed information about the configuration, see Customizing for Cross-Application Components under Start of the navigation pathGeneral Application Functions Next navigation step Error and Conflict Handler Next navigation step Define Payload EncryptionEnd of the navigation path.

Activities

You use the report Encrypting and Reassigning Payloads ( FEHR_CHANGE_ENCRYPTION_KEY) to check the use of keys in payloads and to encrypt, reassign, or decrypt payloads.

For more information, see Encrypting and Reassigning Payloads.