Scribd
Upload
46 views2 pages

Database Auditing

Database auditing involves monitoring and recording activities within a database, with Oracle providing functions to audit various actions. There are three main types of auditing: Schema Object Auditing, SQL Statement Auditing, and SQL Privilege Auditing, which can be configured based on user, success, and session access. To implement auditing, the audit_trail parameter must be set at the database level, with options for internal data dictionary, OS audit trail, or disabling auditing altogether.

Uploaded by

deekondakartheek
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
46 views2 pages

Database Auditing

Database auditing involves monitoring and recording activities within a database, with Oracle providing functions to audit various actions. There are three main types of auditing: Schema Object Auditing, SQL Statement Auditing, and SQL Privilege Auditing, which can be configured based on user, success, and session access. To implement auditing, the audit_trail parameter must be set at the database level, with options for internal data dictionary, OS audit trail, or disabling auditing altogether.

Uploaded by

deekondakartheek
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
You are on page 1/ 2

Auditing:

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

Database auditing is the monitoring and recording of activities occuring within a


database.

Oracle Provides functions that let you audit most actions that can be taken within
and aganist the database.

Oracle Auditing factility is action oriented . When a sql statement that meets a
specific requirement.

Types of Auditing:

1. Schema Object Auditing : Allows us to specific schema objects to be audited

2. SQL Statement Auditing: allows us to specifySQL Statements to be audited

3. SQL Privilege Auditing : allows us to specify paritucular system privileges to


be audited.

scope

1. by successful or unsuccesful

2. by user or all

3. by session or access

by user : allows us of specify a specific user to audit (default : all users)

Whenever successful / whenever not successful :

allows us to specify whether we want auditing to accour at all times , or only


whenever the specific action was
successful or unsuccessful (default :both)

By session/by access:

allows us to specify how often audit records are to generated (default : by access)

Implementing Auditing:

1. Enable auditing at the database level with the spfile or pfile parameter

audit_trial

2. Enable the level of auditing through the audit SQL statement

The audit_trial parameter must be enabled for auditing to work. The valid values
are DB,NONE, AND OS
AUDIT_TRAIL= DB (ENABLES AUDITING TO THE INTERNAL DATA DICTIONARY)

AUDIT_TRAIL=OS (Enable auditing to os audit trail, when set to os ,


another parameter audit_file_dest
has to be set in the init.ora for dumping
audit_trail files in the os)

AUDIT_TRAIL = none (DISABLES ALL AUDITING)

AUDIT TRAIL VIEWS:


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

dba_audit_object
dba_audit_session
dba_audit_statement
dba_audit_trail
dba_object_audit_opts
dba_stmt_audit_opts
dba_priv_audit_opts
dba_audit_exists
audit_actions

You might also like