|
The main idea I am trying to advocate with these posts is a simple one.
Compare a database you are auditing against a database that you know already meets the standards required by the organisation you are auditing.
This is achieved by creating “CSV ty...
Posted By : Ian Cooke | 1 comments
|
We have covered most of the core items that should be consider when performing an Oracle database audit in previous posts, however there a number of other items that I would typically look into.
Database Links
A database link is an object in one database...
Posted By : Ian Cooke | 0 comments
|
|
The company you are auditing should have a policy on what is being audited within your Oracle database. The level of auditing will almost certainly be affected by the sensitivity of the data. Good examples and bench marks for auditing may be seen in the...
Posted By : Ian Cooke | 0 comments
|
Typically application access to an Oracle database is via one of two methods.
Either all users access the same database using a single (proxy) user which is defined in an initialisation (.INI) file, registry etc.
Or the users access the database individ...
Posted By : Ian Cooke | 1 comments
|
|
Before we get into auditing Oracle privileges a reminder of a few definitions might be helpful.
A user privilege is the right to run a particular type of SQL statement, or the right to access an object belonging to another user, run a PL/SQL package, and...
Posted By : Ian Cooke | 1 comments
|
As with parameters the company you are auditing should have a policy on password controls. For Oracle databases these can be seen in the Dba_Profiles view.
A description of the fields in this view can be seen at http://docs.oracle.com/cd/B19306_01/server...
Posted By : Ian Cooke | 0 comments
|