0620-0622

Previous | Table of Contents | Next

Page 620

SQL> audit insert, update, delete  2> on sys.aud$  3> by access; Statement processed. 

Although this technique cannot prevent a more experienced user from circumventing auditing, it should keep cursory pilfering at bay, especially if the users lack the ability to modify the audit status.

The database stops processing, however, if the SYS.AUD$ table reaches its maximum capacity. This problem is easily resolved. As a DBA user, do connect internal from Oracle Server Manager. From Oracle Server Manager, do truncate sys.aud$. This returns the database to its full operational capacity.

Operating System

By directing the database to archive its information at the operating system level, the DBA enables Oracle to store its audit trail information in the same location as the audit information generated by the operating system. This provides a consolidated source of information for DBAs who fill the dual roles DBA and system administrator.

There are a few drawbacks to consider, though. Because the data is no longer in a table, non-database utilities are needed to access it. Likewise, depending on the amount of information being audited , the database can double, triple, or even further increase the amount of information that the operating system currently produces.

Summary

Setting up a security plan for a site can be a challenge for any Oracle DBA. Aside from the development issues involved in defining requirements and developing an overall plan, he is faced with political issues that are often insurmountable in creating the security plan.

It is important to understand that there are two types of privileges: system privileges and object privileges. They are the basis of anything that a user can do while he is connected to an Oracle database. These also form the building blocks of database roles, which provide a means for the DBA to group together sets of similar privileges and grant them to a single user or a group of users.

The idea of a security policy is not an easy thing to implement, especially in environments in which one has never existed. Even so, it is a crucial piece of the database setup that should not be overlooked.

Page 621

Part V

In This PART

• Designing a Database
• Object-Oriented Programming with Packages
• Transaction Processing
• Enforcing Integrity
• Application Security

Developing Applications

Page 622

Previous | Table of Contents | Next