Job Seekers   Employers
dbapool: Authors | Submissions | Contact Us
   Forgot password? | Sign up
  Home   Discussion Forum   Articles   Interview Questions   FAQs   Scripts   Rewards   Analyzer   White Papers   Blog   Certification   Downloads   Tools
 

Topic: User Administration >> Database Security issues

Disclaimer: The purpose of all dbapool forums including OCP and Other Oracle Certification forums is to help each other with specific issues but not to share dump and copyrighted exam content, materials or intellectual property. You may review the entire Oracle Certification Program Candidate Agreement online Here.



  


 Title: Database Security issues
 Emmanuel  Posted: Sep 02, 2005 07:51:19 AM

 Total Post: 4
 Joined: Jun, 2005






 How can I know the following:
1.All users and the times they log on and log out
2.Tables users queried in their last session
3.Tables users attept to access without having a privilege and the number of times this access in made

Thank you.

Emmanuel

 Gregg
Posted: Oct 14, 2005 09:59:13 PM  

 Total Post: 2
 Joined: Oct, 2005






 
Use Oracle's auditing feature, read the Administrator's guide.

Things to watch for:
audit table is sys.aud$, in system tablespace
Oracle does not support moving this table out of system (though people do do this)
Be careful what you turn auditing on for, you can end up with a lot of entries really quick.
You'll want to setup a job to purge it, or move it off to a different tablespace or different database entirely.
You can also use a logon trigger to capture session info on logons/logoffs, this doesn't show failed logon attempts though, but it can capture program information (that doesn't show up in audit_trail).

You can audit actions by session or by access:

session only creates 1 audit trail entry for each action for each session

access creates a separate entry for each action (user runs a delete sql 5 times, 5 rows in audit_trail for delete action)


add "whenever not successful" to the end of an audit command to capture only errors, this will show you most sql errors that happen - like someone miss-typing a column name on an insert, or trying to delete rows from a table they don't have privs to. "whenever successful" will capture only valid actions. Leave it out all together and get both.

good luck...

 positive
Posted: Jun 29, 2008 03:40:22 PM  

 Total Post: 418
 Joined: Jun, 2008






 
Try auditing user actions.

Enable fine-grained auditing.

http://neworacledba.blogspot.com/

 Time Zone: EDT

  




Forum Rules & Description


Who Can Read The Forum? Any registered user or guest
Who Can Post New Topics? Any registered user
Who Can Post Replies? Any registered user




 








Get FREE Magazines

Top 10 Forum User

  Murtuja Khokhar816
  Mohammed Taj746
  Jayanta Sur479
  positive fanatic418
  Vigyan Kaushik386
  Gitesh Trivedi322
  Gopu Gopi250
  Ramesh Jois245
  neeraj sharma243
  Bishal Khetan207






oracle Mag



  About Us Advertise Terms of Use Privacy Newsletters Contact Us    

Home   Discussion Forum   FAQs  Articles  Jobs   Newsletters  Directory  Downloads 

Our Premium Sponsor
Confio Software