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.
Nov 20th, 2017, 1:33am
News: Welcome to Pete Finnigan's Oracle security forum
Home | Help | Search | Members | Login
   Pete Finnigan's Oracle Security Forum
   Oracle Security
   Oracle Auditing
(Moderator: Pete Finnigan)
   Audit logging which (sensitive) rows Selected
« Previous topic | Next topic »
Pages: 1  Reply | Notify of replies | Send Topic | Print
   Author  Topic: Audit logging which (sensitive) rows Selected  (Read 2377 times)
IBJatTVP
PeteFinnigan.com Newbie
*





   
View Profile |

Posts: 3
Audit logging which (sensitive) rows Selected
« on: Aug 30th, 2006, 5:01pm »
Quote | Modify

Does anyone know of a mechanism that can record (audit log) which (sensitive) records a user has SELECTed on an Oracle (9i, 10g) database? [Clearly this needs to restrict to sensitive records else data volumes too large.]  
I'm aware of Oracle's Fine Grained Auditing (FGA), but believe this only returns the SQL statement, not a record of what data was actually accessed.
IP Logged
isaez
PeteFinnigan.com Junior Member
**



Ivan

   
View Profile |

Gender: male
Posts: 76
Re: Audit logging which (sensitive) rows Selected
« Reply #1 on: Aug 30th, 2006, 6:44pm »
Quote | Modify

Hi IBJAtTVP,
 
I think the clue of your question is :  sensitive records
How do you define the term sensitive records?
 
Why don't you create a view which return the sensitive records and audit on this view?
something like this:
 
connect a/a
create view sensitive as select * from top_secret where
this_is_sensitive='Y';
grant select on sensitive to user_x;
 
 
connect system/pw
audit select on a.sensitive;
 
 
From now on every select on view SENSITIVE will be audit.
 
regards,
 
Ivan
IP Logged

regards,

Ivan
Pete Finnigan
PeteFinnigan.com Administrator
*****




Oracle Security is easier if you design for it

   
View Profile | WWW | Email

Gender: male
Posts: 309
Re: Audit logging which (sensitive) rows Selected
« Reply #2 on: Aug 30th, 2006, 7:00pm »
Quote | Modify

I think the solution should involve FGA if the data is sensitive. FGA can be used to store the SQL and the binds so the poster is right the actuial data is hard to get at. FGA can be controlled to pin point the access made though and if its done at a row level can be very useful. FGA works at a statement level though.  
 
Ivans solution will also not show the data though. If you want the data and have big pockets some of the network based audit appliances are worth looking at.
 
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
IBJatTVP
PeteFinnigan.com Newbie
*





   
View Profile |

Posts: 3
Re: Audit logging which (sensitive) rows Selected
« Reply #3 on: Sep 13th, 2006, 1:18pm »
Quote | Modify

Many thanks Pete, Ivan.
 
This appears to be a sticky problem, possibly beyond current technology.
I did wonder about using FGA to log and retrieve the SQL, then resubmitting the SQL (modified) to record which sensitive records actually hit by it and logging that. However, might end up in an endless recurrsion there! And it still does n't identify what the user actually saw - only what the database query hit.
 
Regards, IBJ
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