This page (revision-4) was last changed on 26-Nov-2021 10:22 by jaiken

This page was created on 26-Nov-2021 10:22 by rforbes

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Page revision history

Version Date Modified Size Author Changes ... Change note
4 26-Nov-2021 10:22 2 KB jaiken to previous
3 26-Nov-2021 10:22 2 KB rforbes to previous | to last
2 26-Nov-2021 10:22 2 KB rforbes to previous | to last
1 26-Nov-2021 10:22 2 KB rforbes to last

Page References

Incoming links Outgoing links
ENABLING ENCRYPTION
ENABLING ENCRYPTION

Version management

Difference between version and

At line 1 changed one line
The following steps must be followed to __enable__ encryption in a database. Note that these steps do not encrypt any of the employee data, but will encrypt any user and role passwords.
The following steps must be followed to __enable__ encryption in a database. Note that these steps do not encrypt any of the employee data.
At line 3 changed one line
1. On the database server, create two new folders to hold the database encryption keys. These folders must be secured from outside access, and only accessible by the database processes and the system administrator. These folders __must__ also be backed up as part of any database backup, but should be backed up seperately. One folder will be known as the KEY_DIR - that holds the current active key and the KEYBACKUP_DIR which will hold all keys ever created and the files will be named with a timestamp of when they were created. Key files are also encrypted.
1. On the database server, create two new folders to hold the database encryption keys. These folders must be secured from outside access, and only accessible by the database processes and the system administrator. These folders __must__ also be backed up as part of any database backup. One folder will be known as the KEY_DIR - that holds the current active key and the KEYBACKUP_DIR which will hold all keys ever created and the files will be named with a timestamp of when they were created. Key files are also encrypted.
At line 5 changed one line
2. Do not allow other connection to the database while you are applying the initial encryption install. This may be as simple as taking your Personality application server connections down.
2. Do not allow other connection to the database while you are applying the initial encryption install. This may be as simple as taking your ePersonality application server connections down.
This page (revision-4) was last changed on 26-Nov-2021 10:22 by jaikenTop