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

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
10 26-Nov-2021 10:22 4 KB kparrott to previous
9 26-Nov-2021 10:22 4 KB jaiken to previous | to last
8 26-Nov-2021 10:22 3 KB jaiken to previous | to last
7 26-Nov-2021 10:22 3 KB jaiken to previous | to last
6 26-Nov-2021 10:22 3 KB rforbes to previous | to last
5 26-Nov-2021 10:22 3 KB rforbes to previous | to last
4 26-Nov-2021 10:22 3 KB rforbes to previous | to last
3 26-Nov-2021 10:22 439 bytes rforbes to previous | to last
2 26-Nov-2021 10:22 399 bytes rforbes to previous | to last
1 26-Nov-2021 10:22 366 bytes rforbes to last

Page References

Incoming links Outgoing links
ENCRYPTION
ENCRYPTION

Version management

Difference between version and

At line 3 changed one line
* Within the data itself, when it is "at rest"
* Within the data itself
At line 10 changed one line
Encrypting sensitive data in the database when it is not being used (known as data at rest) prevents it from being viewed or otherwise used by an unauthorized user who has gained access to the database files. Having the data encrypted does bring a performance consideration. The more data that the system has to encrypt and decrypt en route to/from the database, the more of an impact it will have on your performance.
Encrypting sensitive data in the database (known as data at rest) prevents it from being viewed or otherwise used by an unauthorized user who has gained access to the database files. Having the data encrypted does bring a performance consideration. The more data that the system has to encrypt and decrypt enroute to/from the database, the more of an impact tit will have on your performance.
At line 32 removed 3 lines
|P2K_WS_SERVICE_DEFINITIONS |WS_PASSWORD |RAW_WS_PASSWORD
|P2K_WS_SERVICE_DEFINITIONS |WALLET_PASSWORD |RAW_WALLET_PASSWORD
|P2K_WS_SERVICE_DEFINITIONS |TOKEN_PASSWORD |RAW_TOKEN_PASSWORD
At line 33 added one line
The views provided with the application handle the decryption of data, so if you are creating reports using external tools with these views, there is nothing more to be done. If you are accessing the fields above directly, then you will need to modify your reports to handle the decryption of the data. A database function, [P2K_PMSEC.CHECKANDDECRYPT] is provided to help your external reports with the decryption of the data.
At line 37 removed 2 lines
The views provided with the application handle the decryption of data, so if you are creating reports using external tools with these views, there is nothing more to be done. If you are accessing the fields above directly, then you will need to modify your reports to handle the decryption of the data. A database function, [P2K_PMSEC.CHECKANDDECRYPT] (and for date columns [P2K_PMSEC.CHECKANDDECRYPTDATE|P2K_PMSEC.CHECKANDDECRYPT]) is provided to help your external reports with the decryption of the data.
At line 40 changed one line
Note that any Oracle Report that reports on or utilizes a field that has been encrypted will now show that field to be blank. Processes (such as UEEF) that are trying to run backend code utilizing encryption will error out.
Note that any Oracle Report that reports on or utilizes a field that has been encrypted will now show that field to be blank. Oracle Report
At line 46 removed 3 lines
----
![Notes|Edit:Internal.ENCRYPTION]
[{InsertPage page='Internal.ENCRYPTION' default='Click to create a new notes page'}]
This page (revision-10) was last changed on 26-Nov-2021 10:22 by kparrottTop