encryption - Encrypting data in oracle database -


what ways in data can encrypted? example salary column, admin should not able see encrypted columns if possible, data should visible through application users have access defined in application, changes in application (adding new functionality encrypt/decrypt @ application level) last resort , minimal.

so far have thought of 2 ways fresh ideas or pros , cons of ones below appreciated: 1. using oracle tde (transparent data encryption). - con : admin can possibly grant himself rights see data 2. creating trigger encrypt before insert , along lines of pipeline retrieve.

oracle database vault way prevent dba being able access data stored in database. cost product, however, , requires have additional set of security admins job grant dbas whatever privileges need.

barring that, you'd looking @ solutions encrypt , decrypt data in application outside database. involve making changes database structure (i.e. salary column declared raw rather number). , involves application changes call encryption , decryption routines. , requires solve key management problem these sorts of solutions fail. storing encryption key somewhere application can retrieve somewhere no admin can access non-trivial. , need ensure key backed , restored separately since encrypted data in database useless without key.

most of time, though, i'd tend suggest right approach allow dba see data , audit queries run instead. if see 1 particular dba running queries fun rather looking @ bits of data in course of doing job, can take action @ point. knowing queries being audited enough keep dba accessing data doesn't need.


Comments

Popular posts from this blog

database - VFP Grid + SQL server 2008 - grid not showing correctly -

jquery - Set jPicker field to empty value -

.htaccess - htaccess convert request to clean url and add slash at the end of the url -