Audit Architecture Oracle Fusion Middleware Audit Framework Concepts

Introduction to Oracle Fusion Middleware Audit Framework 11-9 With Oracle Business Intelligence: ■ You can select records based on criteria like username, date-time range, and so on. Note that Oracle Business Intelligence works with the database audit store only, and is not usable with bus-stop files. The pre-defined audit report types available with Oracle Business Intelligence include: ■ errors and exceptions ■ operational ■ user activity ■ authentication and authorization history ■ transaction history For further details, see Section C.2, Pre-built Audit Reports. You can also use the audit schema details to create custom audit reports as needed. 11-10 Oracle Fusion Middleware Application Security Guide 12 Configuring and Managing Auditing 12-1 12 Configuring and Managing Auditing This chapter explains how to perform day-to-day audit administration tasks. ■ Audit Administration Tasks ■ Managing the Audit Store ■ Managing Audit Policies ■ Audit Logs ■ Advanced Management of Database Store

12.1 Audit Administration Tasks

The audit administrator should plan the site’s audit setup carefully by following the steps in these areas: ■ Implementation Planning This includes planning the type of store to use for audit records, data store configuration details, and so on. See Section 12.2, Managing the Audit Store for details. ■ Policy administration The administrator must configure the appropriate audit policies to ensure that the required audit events are generated. This is an ongoing activity since the audit policies must be able to reflect changes to the application environment, addition of components and users, and so on. See Section 12.3, Managing Audit Policies for details. ■ Reports Management This includes planning for and configuring audit reports and queries. See Chapter 13, Using Audit Analysis and Reporting for details. ■ Data Administration This includes planningincreasing the database size required to store the audit data generated, backing up the audit data and purging the audit data based on company policy. See Also: Chapter 11, Introduction to Oracle Fusion Middleware Audit Framework for background information about auditing in Oracle Fusion Middleware. 12-2 Oracle Fusion Middleware Application Security Guide See Section 12.5, Advanced Management of Database Store for details about audit store administration.

12.2 Managing the Audit Store

Out of the box, the audit framework uses the file system to store audit records. In a production environment, however, Oracle recommends that you use a database audit store to provide scalability and high-availability for the audit framework. In addition, an audit store residing in a database allows the audit data to be viewed through Oracle Business Intelligence Publisher with pre-packaged audit reports that are available with that product. Oracle Business Intelligence Publisher is available in the 11g Release 1 11.1.1 CD pack. This section explains these audit store management tasks in detail: ■ Create the Audit Schema using RCU ■ Set Up Audit Data Sources ■ Configure a Database Audit Store for Java Components ■ Configure a Database Audit Store for System Components ■ Tuning the Bus-stop Files ■ Configuring the Stand-alone Audit Loader

12.2.1 Create the Audit Schema using RCU

To switch to a database as the permanent store for your audit records, you first use the Repository Creation Utility RCU to create a database store for audit data. This section explains how to create the audit schema. Once the database schema is created, you can: ■ create a datasource to point to this schema ■ update the domain configuration to switch the audit store for audit records see Section 12.2.3.2, Configure the Audit Store . Before You Begin Before you begin, make sure to collect the details on which database to use, along with the DBA credentials to use. Configuring the Database Schema Take these steps to configure a schema for the audit store: 1. Go to RCU_HOMEbin and execute the RCU utility.

2. Choose Create at the starting screen. Click Next.

Note: The bus-stop files store audit records in the absence of database storage. Note: This discussion assumes that RCU and the database is already installed in your environment. See the Installation Guide for more information.