Encryption of Data at Rest

Encryption of data at rest provides data security by allowing you to encrypt sensitive data such as social security numbers and credit card numbers, which are saved in a database. This feature ensures that data is kept safe if the storage medium is stolen. It also helps in addressing security-related regulatory compliance issues.

Infor Lawson does not provide advice or technical details about how data encryption is implemented. Refer to your RDBMS provider for implementation details.

Before applying encryption of data at rest in Lawson, you must create a master encryption key that is stored in a wallet. You must open the wallet to perform any encryption or decryption. After opening the wallet, encryption and decryption happens transparently on tables in the encrypted tablespace until you explicitly close the wallet or the database instance is shut down.

Lawson database configuration is determined by how you configure encryption in Oracle. If you encrypt all tables in the Oracle instance, no additional Lawson configuration is needed. If you encrypt a single table space in Oracle, then all Lawson files that you wish to encrypt must be assigned to that table space. You must define a tablespace as encrypted when it is created. You cannot make an existing tablespace encrypted using the ALTER TABLESPACE statement.

Note: You can assign the database space to a product line or data area, a system code, or to individual files. The database space assignment for a file overrides the definition for the system code, and the data area definition overrides the system code definition.