In the Publish Service to UDDI dialog box

Advanced Administration 14-13 You can also audit the events for a specific user, for example, you can audit all events by an administrator. For more information about configuring audit policies, see Configuring and Managing Auditing in Oracle Fusion Middleware Application Security Guide. The following sections describe how to define audit policies and view audit data: ■ Configuring Audit Policies ■ Managing Audit Data Collection and Storage ■ Viewing Audit Reports Configuring Audit Policies Follow the steps in this section to configure audit policies.

1. In the Navigator pane, expand WebLogic Domain.

2. Click the domain for which you want to manage assertion templates.

3. From the WebLogic Domain menu select Security Audit Policy.

The Audit Policy Settings page is displayed. 4. Select and audit level from the Audit Level menu. Valid audit levels include: ■ None—Disables auditing. ■ Low—Audits a small scope of events. The subset of events is predefined individually for each component. For example, for a given component, Low may collect authentication and authorization events only. ■ Medium—Audits a medium scope of events which is a superset of the events collected at the Low level. For example, for a given component, Medium may collect authentication, authorization, and policy authoring events. ■ Custom—Enables you to provide a custom auditing policy. You can view the components and applications that are selected for audit at each level in the audit policies list. For all audit levels other than Custom, the Table 14–2 Auditing Events for Web Services Enable auditing for the following Web service events . . . Using this system component . . . ■ User authentication. ■ User authorization. ■ Policy enforcement, including message integrity, message confidentiality, and security policy. Oracle Web Services Manager—Agent ■ Web service requests sent and responses received. ■ SOAP faults incurred. Oracle Web Services ■ Oracle WSM policy creation, deletion, or modification. ■ Assertion template creation, deletion, or modification. Oracle Web Services Manager ■ Oracle WSM policy attachment. Oracle Web Services Manager— Policy Attachment 14-14 Oracle Fusion Middleware Security and Administrators Guide for Web Services information in the audit policies list is greyed out, as you cannot customize other audit level settings. 5. If you selected the Custom audit level, perform one of the following steps: ■ Select the information that you want to audit by clicking the associated checkbox in the Enable Audit column. You can audit at the following levels of granularity: All events for a component, all events within a component event group, an individual event, or a specific outcome of an individual event such as success or failure. At the event outcome level, you can specify an edit filter. Filters are rules-based expressions that you can define to control the events that are returned. For example, you might specify an Initiator as a filter for policy management operations to track when policies were created, modified, or deleted by a specific user. To define a filter for an outcome level, click the Edit Filter icon in the appropriate column, specify the filter attributes, and click OK . The filter definition appears in the Filter column. Deselect the checkbox for a component at a higher level to customize auditing for its subcomponents. You can select all components and applications by checking the checkbox adjacent to the column name. ■ To audit only failures for all system components and applications, Select Failures Only . If selected, all checkboxes in the Enable Audit column are cleared. 6. If required, enter a comma-separated list of users in the Always Audit Users text box. Specified users will always be audited, regardless of whether auditing is enabled or disabled, and at what level auditing is set.

7. Click Apply.

To revert all changes made during the current session, click Revert. Managing Audit Data Collection and Storage To manage the data collection and storage of audit information, you need to perform the following tasks: ■ Set up and manage an audit data repository. You can store records using one of two repository modes: file and database. It is recommended that you use the database repository mode. The Oracle Business Intelligence Publisher-based audit reports only work in the database repository mode. ■ Set up audit event collection. For more information, see Managing the Audit Store in Oracle Fusion Middleware Application Security Guide. Viewing Audit Reports For database repositories, data is exposed through pre-defined reports in Oracle Business Intelligence Publisher. A number of predefined reports are available, such as: authentication and authorization history, Oracle WSM policy enforcement and management, and so on.