Auditing an Oracle database for security issues is very important. PeteFinnigan.com provides all of the information and tools that you will need Click here for details of PeteFinnigan.com Limited's detailed Oracle database security audit service Click here for details of PeteFinnigan.com Limited's Oracle Security Training Courses
Cookie Policy:We only use essential cookies on small sections of this website. For details see here.

Welcome, Guest. Please Login.
Feb 16th, 2019, 5:07am
News: If you would like to register contact the forum admin
Home | Help | Search | Members | Login
   Pete Finnigan's Oracle Security Forum
   Oracle Security
   Oracle Security
(Moderator: Pete Finnigan)
   Database Authentication
« Previous topic | Next topic »
Pages: 1  Reply | Notify of replies | Send Topic | Print
   Author  Topic: Database Authentication  (Read 1738 times)
Pete Finnigan
PeteFinnigan.com Administrator
*****




Oracle Security is easier if you design for it

   
View Profile | WWW | Email

Gender: male
Posts: 309
Database Authentication
« on: Dec 11th, 2009, 3:33pm »
Quote | Modify

We are going over how to set up authentication for our Java/Oracle in house applications.    
 
From a security standpoint, what is the best recommendation for database authentication?
 
1. Lightweight users?  (No schema)
2. Database schema authentication (This is how we are currently set up)
3. Each user has a schema using LDAP authentication?  
 
I have not looked that hard yet but was wondering what is the best method from an "Enterprise" standpoint.
IP Logged

Pete Finnigan (email:pete@petefinnigan.com)
Oracle Security Web site: http://www.petefinnigan.com
Forum: http://www.petefinnigan.com/forum/yabb/YaBB.cgi
Oracle security blog: http://www.petefinnigan.com/weblog/entries/index.html
Pete Finnigan
PeteFinnigan.com Administrator
*****




Oracle Security is easier if you design for it

   
View Profile | WWW | Email

Gender: male
Posts: 309
Re: Database Authentication
« Reply #1 on: Dec 14th, 2009, 9:46am »
Quote | Modify

Hi,
 
I think some further questions must be asked. What are the users doing?, do they need to be identified for traceability?, does the application already indentify end users outside of the database connections, i.e. at the application layer?, how many users, are their performance/scalability/maintainability issues to solve?
 
It always comes to a compromise. For tracability, there is more chance to trace people if they have their own schemas but this is not perfect as end to end traceability is not guarenteed. For performance, connection pooling is a much better option and for maintainability lightweight users probably fits the bill better.  
 
Have you thought about using Oracle connection pooling and proxy users? - this is a good compromise for tracability and performance but will depend on how many people (users) you need to deal with.
 
cheers
 
Pete
IP Logged

Pete Finnigan (email:pete@petefinnigan.com)
Oracle Security Web site: http://www.petefinnigan.com
Forum: http://www.petefinnigan.com/forum/yabb/YaBB.cgi
Oracle security blog: http://www.petefinnigan.com/weblog/entries/index.html
Pete Finnigan
PeteFinnigan.com Administrator
*****




Oracle Security is easier if you design for it

   
View Profile | WWW | Email

Gender: male
Posts: 309
Re: Database Authentication
« Reply #2 on: Dec 14th, 2009, 1:59pm »
Quote | Modify

Thank you for your reply.  
 
We don't have enough of a user base to require connection pooling in the past.  Our users are not doing anything out of the ordinary,  just some mild data entry and reporting.
 
We do have a heavy traceability requirement, we would probably have to have the applications audit connections manually if we removed the schema.
 
I will look into Proxy users and connection pooling.  The other problem is no money if these require licenses above what we have then there would be a problem too.
 
The customer all of the sudden seems to want to eliminate user schema.  I just want to be prepared for when that day comes.
 
Thanks
 
Neil Blevins
IP Logged

Pete Finnigan (email:pete@petefinnigan.com)
Oracle Security Web site: http://www.petefinnigan.com
Forum: http://www.petefinnigan.com/forum/yabb/YaBB.cgi
Oracle security blog: http://www.petefinnigan.com/weblog/entries/index.html
Pete Finnigan
PeteFinnigan.com Administrator
*****




Oracle Security is easier if you design for it

   
View Profile | WWW | Email

Gender: male
Posts: 309
Re: Database Authentication
« Reply #3 on: Dec 14th, 2009, 5:47pm »
Quote | Modify

Hi Niel,
 
Thanks for your reply. I think proxy users/connection pooling is a good option for you. You will also need to ensure end-to-end tracability is included. All of these can be done with JDBC and you said its an inhouse application so you should be in a good position. These features are not cost options so you should be good to go on licenses.
 
Kind regards
 
Pete
IP Logged

Pete Finnigan (email:pete@petefinnigan.com)
Oracle Security Web site: http://www.petefinnigan.com
Forum: http://www.petefinnigan.com/forum/yabb/YaBB.cgi
Oracle security blog: http://www.petefinnigan.com/weblog/entries/index.html
Pete Finnigan
PeteFinnigan.com Administrator
*****




Oracle Security is easier if you design for it

   
View Profile | WWW | Email

Gender: male
Posts: 309
Re: Database Authentication
« Reply #4 on: Dec 14th, 2009, 5:57pm »
Quote | Modify

Thank you. I will move that option to the top of the list to research.
IP Logged

Pete Finnigan (email:pete@petefinnigan.com)
Oracle Security Web site: http://www.petefinnigan.com
Forum: http://www.petefinnigan.com/forum/yabb/YaBB.cgi
Oracle security blog: http://www.petefinnigan.com/weblog/entries/index.html
Pages: 1  Reply | Notify of replies | Send Topic | Print

« Previous topic | Next topic »

Powered by YaBB 1 Gold - SP 1.4!
Forum software copyright 2000-2004 Yet another Bulletin Board