Database Security Products (MOSC)

MOSC Banner

understanding oracle operating system audit files

edited Aug 21, 2014 7:08PM in Database Security Products (MOSC) 3 commentsAnswered

We have a large mission critical 11.1.0.7 database running on AIX. Database auditing parameters are left at default values:

NAME                                 TYPE        VALUE

------------------------------------ ----------- ------------------------------

audit_file_dest                      string      <our_path>

audit_sys_operations                 boolean     FALSE

audit_syslog_level                   string

audit_trail                          string      DB

My boss noticed a lot of files in the audit destination for SYSDBA connections (default behavior in 11g). Seeing these files raised a concern for him; and he asked me to investigate and see who/what is connecting to the database as SYSDBA. I suspect that the connections are benign; but I am having a hard time proving this due to limited information provided on them in the documentation. Anybody out there have experience interpreting/mining these files for information?

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center