Fine grained audit

Feature introduced from the RDBMS 9i release. Fine grained auditing extends Oracle existing auditing capabilities. Main features: – Regular auditing must be enabled using the parameter AUDIT_TRAIL. FGA does not require any parameter change . – Sql bind variables are captured by default in FGA – In FGA auditing is more flexible when certain columns are accessed, when a certain condition is considered true. – FGA can be temporarily disabled and enabled. Once identified schema and tables to check we set the policy audit. Suppose you want to control all access to the table ETICA and all operation sql that Read More

Moving Audit Trail Table

Reading the previous article posted on June 3 about enabling auditing in an Oracle Database, I’d like to add some other useful information. Oracle stores all the audit results in the SYS.AUD$ table, as stated in the previous article. But the bad news are that the table is by default in the SYSTEM tablespace: SELECT OWNER, TABLE_NAME, TABLESPACE_NAME FORM DBA_TABLES WHERE TABLE_NAME = ‘AUD$’; OWNER  TABLE_NAME      TABLESPACE_NAME —— ————— —————————— SYS    AUD$            SYSTEM So the risk of having a full SYSTEM tablespace is very high if you plan to enable the audit feature, leading to possible unpredictable errors. The solution Read More


The Oracle RDBMS provides various control functions of the system security. Among these, there is also a function of AUDIT TRAIL that lets you record any activity carried out on the database of interest. The control possibilities are very sophisticated and flexible, but it is necessary to avoid excessive control to avoid needlessly heavy and impossible access checks. Controls POSSIBLE And ‘possible to activate controls aimed at: • specific SQL statement (eg. connect, create table, …), • specific privileges (eg. grant system, …), • operations (select, insert, alter, execute, …) of objects RDBMS. Can be controlled actions that returned errors Read More