Auditing an Oracle database for security issues is very important. provides all of the information and tools that you will need Click here for details of Limited's detailed Oracle database security audit service Click here for details of 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.
Mar 23rd, 2018, 4:53am
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)
   Top 10 worst Oracle database configurations
« Previous topic | Next topic »
Pages: 1  Reply | Notify of replies | Send Topic | Print
   Author  Topic: Top 10 worst Oracle database configurations  (Read 3526 times)
Marcel-Jan Junior Member

View Profile | WWW |

Gender: male
Posts: 83
Top 10 worst Oracle database configurations
« on: Mar 4th, 2010, 11:20am »
Quote | Modify

I'm working on a presentation about Oracle database security and I was thinking of adding a slide with the top 10 worst mistakes a DBA which have the most negative effect on the database security.
When I compiled the list I was thinking what a great topic for discussion this would be.
Here is my list up till now. It is a list of things that I commonly encounter (except 1 fortunately) and with a big impact.
1. No firewall protection for the db server
(Okay, firewalls usually aren't a topic the DBA works on, but he/she should at least check).
2. Default accounts with default passwords.
3. DBA-like privileges for non-DBAs or schema accounts.
4. No backup / no restore tested (which is equally bad).
5. Running Oracle versions <=9i out of the box. (They are out there plenty!)
6. Public database links to priviliged accounts on other databases.
7. Grants to PUBLIC (amongst which Oracle's DBMS_ and UTL_ packages)
8. Access to large parts of the operating system of the db server (utl_file_dir='*', directory objects to sensitive directories, Java privileges, extproc)
9. Never installing Critical Patch Updates.
10. Never monitoring database usage (no listener log, no auditing)
I probably have forgotten a thing or two (not requiring complex passwords also comes to mind) and the order of items needs some more thought, but there it is for now.
What is your Top 10?
« Last Edit: Mar 9th, 2010, 3:54pm by Marcel-Jan » IP Logged
jdebever Newbie

I love YaBB 1G - SP1!

View Profile |

Posts: 1
Re: Top 10 worst Oracle database configurations
« Reply #1 on: Aug 23rd, 2010, 12:33pm »
Quote | Modify

Hoi MJ,
How about only having 1 database.
All developers etc. directly in production...
For the rest we score 8/10.. we have a firewall, and O11..
Anyone up for a chalenge?
IP Logged
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