Ethical Hacking

Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package.
Computer Forensics Training at InfoSec Institute

Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors.




Network Security Security-Basics
[Top] [All Lists]

Re: Securing data from Database Admin

Subject: Re: Securing data from Database Admin
Date: Thu, 27 Mar 2008 16:34:06 -0500
Oracle 11g has added a suite of security functions. Ask your DBA to help you. S/he should not have any issue with helping you secure your data to whatever level you want or need to, including restricting their own access. For instance, you can still patch the database without being able to look at the data and you can still back up and restore data even if it's encrypted.

http://www.oracle.com/database/database-vault.html
http://www.oracle.com/database/advanced-security.html
http://www.oracle.com/technology/deploy/security/database-security/secure-application-roles/index.html
http://www.oracle.com/technology/deploy/security/database-security/virtual-private-database/index.html
http://www.oracle.com/technology/deploy/security/database-security/transparent-data-encryption/index.html

I haven't implemented these in 11g myself and don't have any plans to.

-Mike

WALI wrote:
Is there a way we can secure data within (Oracle 9i) database? Supposingly there is an application developed by internal developers and it's backend database is administered by a DB Admin. There is no segregation of duties between development and live environments due to resource constraints.

Is there a way data can be protected from being revealed to or being tempered by DB Admin? He would only be called in when there's some kind of malfunction that too under the watchful eyes of project team leader.

Any thoughts to bring in preventive/detective controls over DB Admin activities?




<Prev in Thread] Current Thread [Next in Thread>