Oracle Audit Vault. Auditor's Guide Release E

Transcription

1 Oracle Audit Vault Auditor's Guide Release E October 2009

2 Oracle Audit Vault Auditor's Guide, Release E Copyright 2007, 2009, Oracle and/or its affiliates. All rights reserved. Primary Author: Patricia Huey Contributing Author: Rodney Ward Contributors: Tammy Bednar, Janet Blowney, Raghavendran Hanumantharau, Ravi Kumar, Srivatsan Kannan, K. Karun, Anurag Prasad, Vipul Shah, Prahlada Varadan Thirumalai, Lok Sheung, Srividya Tata This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this software or related documentation is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable: U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR , Commercial Computer Software License (December 2007). Oracle USA, Inc., 500 Oracle Parkway, Redwood City, CA This software is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications which may create a risk of personal injury. If you use this software in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure the safe use of this software. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software in dangerous applications. Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners. This software and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.

3 Contents Preface... xiii Audience... Documentation Accessibility... Related Documents... Conventions... xiii xiii xiv xv What's New in Oracle Audit Vault for Auditors?... xvii Near Real Time Activity Monitoring... xvii User Entitlement Audit Data... xvii Notifications for Alerts and Reports... xviii Trouble Ticket Notifications for Alerts... xviii Annotating and Attesting Alerts and Reports... xviii More Functionality for Advanced Alerts... xix Scheduling Reports to be Sent to Other Users in PDF Format... xix Additional and Changed Reports... xix New and Changed Audit Events... xxi Oracle Audit Vault Console User Interface Enhancements... xxiii 1 Introducing Oracle Audit Vault for Auditors 1.1 How Do Auditors Use Oracle Audit Vault? General Steps for Using Oracle Audit Vault Step 1: Ensure That the Source Databases Are Collecting Audit Data Step 2: Create Audit Policies for Oracle Database Data Step 3: Optionally, Create and Monitor Alerts Step 4: View and Customize the Oracle Audit Vault Reports Step 5: Respond to Reports and Alerts Database Requirements for Collecting Audit Data Requirements for Oracle Database Ensuring That Auditing Is Enabled in the Source Database Using Recommended Audit Settings in the Source Database Requirements for SQL Server, Sybase ASE, and IBM DB2 Databases Starting the Oracle Audit Vault Console Ensuring That the Oracle Audit Vault Collectors Can Collect Data iii

4 2 Creating Oracle Audit Vault Policies and Alerts 2.1 About Oracle Audit Vault Policies and Alerts General Steps for Creating Oracle Audit Vault Policies and Alerts Retrieving Audit Policy Settings from the Source Oracle Database Step 1: Retrieve the Audit Settings from the Source Oracle Database Step 2: Activate (Update) the Fetched Audit Settings State Creating Oracle Vault Audit Policies for SQL Statements About SQL Statement Auditing Defining a SQL Statement Audit Policy Creating Oracle Audit Vault Policies for Schema Objects About Schema Object Auditing Defining a Schema Object Audit Policy Creating Oracle Audit Vault Policies for Privileges About Privilege Auditing Defining a Privilege Audit Policy Creating Oracle Audit Vault Policies for Fine-Grained Auditing About Fine-Grained Auditing Auditing Specific Columns and Rows Using Event Handlers in Fine-Grained Auditing Defining a Fine-Grained Auditing Policy Creating Capture Rules for Redo Log File Auditing About Capture Rules Used for Redo Log File Auditing Defining a Capture Rule for Redo Log File Auditing Verifying Oracle Audit Vault Policy Settings Provisioning Audit Vault Policies to the Source Oracle Database Saving the Audit Policy Settings to a SQL Script for a Database Administrator Manually Provisioning the Audit Policy Settings to the Source Database Copying Oracle Audit Vault Policies to Other Oracle Databases Creating and Configuring Alerts About Alerts Creating Templates to be Used for Alerts Creating an Notification Profile Creating an Notification Template Creating a Trouble Ticket Template Creating Alert Status Values Creating a Basic Alert Creating an Advanced Alert About Advanced Alerts Creating an Advanced Alert That Uses a Condition Creating an Advanced Alert Condition That Uses a Function Monitoring Alerts Responding to an Alert Setting a Retention Period for Audit Data Using Oracle Audit Vault Reports 3.1 What Are Oracle Audit Vault Reports? Accessing the Oracle Audit Vault Audit Reports iv

5 3.3 Using the Default Reports About the Default Reports Using the Default Access Reports About the Default Access Reports Activity Overview Report Data Access Report Database Vault Report Distributed Database Report Procedure Executions Report User Sessions Report Using the Default Management Activity Reports About the Default Management Activity Reports Account Management Report Audit Commands Report Object Management Report Procedure Management Report Role and Privilege Management Report System Management Report Using the Default System Exception Reports About the Default System Exception Reports Exception Activity Report Invalid Audit Record Report Uncategorized Activity Report Using the Default Entitlement Reports About the Default Entitlement Reports User Accounts Report and User Accounts by Source Report User Privileges Report and User Privileges by Source Report User Profiles Report and User Profiles by Source Report Database Roles Report and Database Roles by Source Report System Privileges Report and System Privileges by Source Report Object Privileges Report and Object Privileges by Source Report Privileged Users Report and Privileged Users by Source Report Using the Compliance Reports About the Compliance Reports Credit Card Compliance Report: Related Data Access Compliance Report Financial Compliance Reports Financial Related Data Access Report Financial Related Data Modifications Report Health Care Compliance Report: EPHI Related Data Access Report Common Credit Card, Financial, and Health Care Compliance Reports Audit Setting Changes Report Before/After Values Report Database Failed Logins Report Database Login/Logoff Report Database Logoff Report Database Logon Report Database Startup/Shutdown Report v

6 vi Deleted Objects Report Program Changes Report Schema Changes Report System Events Report User Privilege Change Activity Report Using the Critical and Warning Alert Reports About the Critical and Warning Alert Reports All Alerts Report Critical Alerts Report Warning Alerts Report Scheduling and Creating PDF Reports About Scheduling and Creating PDF Reports Scheduling and Creating a PDF Report Annotating and Attesting Reports About Annotating and Attesting Reports Annotating and Attesting a Report Generating and Comparing Snapshots of Entitlement Audit Data About Entitlement Report Snapshots and Labels General Steps for Using Entitlement Reports Retrieving Entitlement Audit Data to Create the Snapshot Creating an Entitlement Snapshot Label Assigning Snapshots to a Label Viewing Entitlement Snapshot and Label Audit Data Checking Entitlement Reports for Individual Snapshot or Label Audit Data Checking Entitlement Reports for Changes to Snapshot or Label Audit Data Controlling the Display of Data in a Report About Controlling the Display of Report Data Hiding or Showing Columns in a Report Hiding the Currently Selected Column Hiding or Showing Any Column Filtering Data in a Report Filtering All Rows Based on Data from the Currently Selected Column Filtering Column and Row Data Filtering Row Data Using an Expression Sorting Data in a Report Sorting Row Data for the Currently Selected Column Sorting Row Data for All Columns Highlighting Rows in a Report Charting Data in a Report Adding a Control Break to a Column in a Report Resetting the Report Display Values to Their Default Settings Finding Information About Report Data Finding Detailed Information About an Audit Record Finding Information About the Purpose of a Column Working with User-Defined Reports About User-Defined Reports Creating a Category for User-Defined Reports

7 Creating a Category Name Alphabetizing the Category Name List Editing a Category Name Creating a User-Defined Report Accessing a User-Defined Report Downloading a Report to a CSV File Oracle Audit Vault Data Warehouse Schema 4.1 About the Oracle Audit Vault Data Warehouse Schema Oracle Audit Vault Audit Data Warehouse Architecture Design of the Audit Data Warehouse Schema How the Fact Table and Dimension Tables Work Fact Table Constraints and Indexes Relationships Between the Fact and Dimension Tables AUDIT_EVENT_FACT Fact Table CLIENT_HOST_DIM Dimension Table CLIENT_TOOL_DIM Dimension Table CONTEXT_DIM Dimension Table EVENT_DIM Dimension Table PRIVILEGES_DIM Dimension Table SOURCE_DIM Dimension Table TARGET_DIM Dimension Table TIME_DIM Dimension Table USER_DIM Dimension Table A Oracle Database Audit Events A.1 About the Oracle Database Audit Events... A-1 A.2 Account Management Events... A-2 A.3 Application Management Events... A-3 A.4 Audit Command Events... A-6 A.5 Data Access Events... A-7 A.6 Oracle Database Vault Events... A-9 A.7 Exception Events... A-10 A.8 Invalid Record Events... A-11 A.9 Object Management Events... A-13 A.10 Peer Association Events... A-16 A.11 Role and Privilege Management Events... A-17 A.12 Service and Application Utilization Events... A-18 A.13 System Management Events... A-20 A.14 Unknown or Uncategorized Events... A-22 A.15 User Session Events... A-23 B Microsoft SQL Server Audit Events B.1 About the Microsoft SQL Server Audit Events... B-1 B.2 Account Management Events... B-2 B.3 Application Management Events... B-4 vii

8 B.4 Audit Command Events... B-6 B.5 Data Access Events... B-8 B.6 Exception Events... B-9 B.7 Invalid Record Events... B-11 B.8 Object Management Events... B-13 B.9 Peer Association Events... B-16 B.10 Role and Privilege Management Events... B-17 B.11 Service and Application Utilization Events... B-20 B.12 System Management Events... B-22 B.13 Unknown or Uncategorized Events... B-24 B.14 User Session Events... B-26 C D Sybase Adaptive Server Enterprise Audit Events C.1 About the Sybase Adaptive Server Enterprise Audit Events... C-1 C.2 Account Management Events... C-2 C.3 Application Management Events... C-3 C.4 Audit Command Events... C-4 C.5 Data Access Events... C-6 C.6 Exception Events... C-7 C.7 Invalid Record Events... C-8 C.8 Object Management Events... C-9 C.9 Peer Association Events... C-11 C.10 Role and Privilege Management Events... C-12 C.11 Service and Application Utilization Events... C-14 C.12 System Management Events... C-15 C.13 Unknown or Uncategorized Events... C-17 C.14 User Session Events... C-18 IBM DB2 Audit Events D.1 About the IBM DB2 Audit Events... D-1 D.2 Account Management Events... D-2 D.3 Application Management Events... D-3 D.4 Audit Command Events... D-4 D.5 Data Access Events... D-5 D.6 Exception Events... D-6 D.7 Invalid Record Events... D-7 D.8 Object Management Events... D-8 D.9 Peer Association Events... D-10 D.10 Role and Privilege Management Events... D-10 D.11 Service and Application Utilization Events... D-12 D.12 System Management Events... D-13 D.13 Unknown or Uncategorized Events... D-15 D.14 User Session Events... D-16 Index viii

9 List of Figures 2 1 Dashboard Page Default Reports Page Activity Overview Report Page Compliance Reports Page Showing Individual Snapshot or Label Audit Data Comparing Entitlement Report Snapshot or Label Audit Data Architecture of the Oracle Audit Vault Audit Data Warehouse Structure of the Oracle Audit Data Warehouse Source Dimension Hierarchy Tables in the Oracle Audit Vault Data Warehouse ix

10 List of Tables 1 1 Oracle Database Audit Trail Types and Corresponding Collectors Database Collector Types Provided by Oracle Audit Vault Fields Under Apply Audit Settings in the Audit Settings Page Fields in the Statement Page Fields in the Create Statement Audit Page Fields in the Object Page Fields in the Create Object Audit Page Fields in the Privilege Page Fields in the Create Privilege Audit Page Fields in the Fine-Grained Audit Page Fields in the Create Fine Grained Audit Page Fields in the Capture Rule Page Fields in the Create Capture Rule Page Fields in the Add Notification Profile Page Fields in the Add Notification Template Page Notification Template Alert Tags Notification Template Report Tags Fields Used in the Add Trouble Ticket Template Page Fact Table Constraints and Indexes Local Bitmap Indexes Defined on the AUDIT_EVENT_FACT Table AUDIT_EVENT_FACT Fact Table CLIENT_HOST_DIM Dimension Table CLIENT_TOOL_DIM Dimension Table CONTEXT_DIM Dimension Table EVENT_DIM Dimension Table PRIVILEGES_DIM Dimension Table SOURCE_DIM Dimension Table TARGET_DIM Dimension Table TIME_DIM Dimension Table USER_DIM Dimension Table A 1 Oracle Database Account Management Audit Events... A-2 A 2 Oracle Database Account Management Event Attributes... A-2 A 3 Oracle Database Application Management Audit Events... A-3 A 4 Oracle Database Application Management Event Attributes... A-5 A 5 Oracle Database Audit Command Audit Events... A-6 A 6 Oracle Database Audit Command Event Attributes... A-6 A 7 Oracle Database Data Access Audit Events... A-7 A 8 Oracle Database Data Access Event Attributes... A-7 A 9 Oracle Database Vault Audit Events... A-9 A 10 Oracle Database Vault Event Attributes... A-10 A 11 Oracle Database Exception Audit Events... A-10 A 12 Oracle Database Exception Event Attributes... A-10 A 13 Oracle Database Invalid Record Audit Events... A-12 A 14 Oracle Database Invalid Record Event Attributes... A-12 A 15 Oracle Database Object Management Audit Events... A-13 A 16 Oracle Database Object Management Event Attributes... A-14 A 17 Oracle Database Peer Association Audit Events... A-16 A 18 Oracle Database Peer Association Event Attributes... A-16 A 19 Oracle Database Role and Privilege Management Audit Events... A-17 A 20 Oracle Database Role and Privilege Management Event Attributes... A-17 A 21 Oracle Database Service and Application Utilization Audit Events... A-18 A 22 Oracle Database Service and Application Utilization Event Attributes... A-19 A 23 Oracle Database System Management Audit Events... A-20 x

11 A 24 Oracle Database System Management Event Attributes... A-21 A 25 Oracle Database Unknown or Uncategorized Audit Events... A-22 A 26 Oracle Database Unknown or Uncategorized Event Attributes... A-22 A 27 Oracle Database User Session Audit Events... A-23 A 28 Oracle Database User Session Event Attributes... A-24 B 1 SQL Server Account Management Audit Events... B-2 B 2 SQL Server Account Management Event Attributes... B-2 B 3 SQL Server Application Management Audit Events... B-4 B 4 SQL Server Application Management Event Attributes... B-4 B 5 SQL Server Audit Command Audit Events... B-6 B 6 SQL Server Audit Command Events Logged in Windows Event Viewer... B-6 B 7 SQL Server Audit Command Event Attributes... B-6 B 8 SQL Server Data Access Audit Events... B-8 B 9 SQL Server Data Access Event Attributes... B-8 B 10 SQL Server Exception Audit Events... B-9 B 11 SQL Server Exception Events Logged in the Windows Event Viewer... B-9 B 12 SQL Server Exception Event Attributes... B-10 B 13 SQL Server Invalid Record Event Attributes... B-11 B 14 SQL Server Object Management Audit Events... B-13 B 15 SQL Server Object Management Event Attributes... B-14 B 16 SQL Server Peer Association Event Attributes... B-16 B 17 SQL Server Role and Privilege Management Audit Events... B-17 B 18 SQL Server Role and Privilege Management Event Attributes... B-19 B 19 SQL Server Service and Application Utilization Audit Events... B-20 B 20 SQL Server Service and Application Utilization Event Attributes... B-20 B 21 SQL Server System Management Audit Events... B-22 B 22 SQL Server System Management Event Attributes... B-23 B 23 SQL Server Unknown or Uncategorized Event Attributes... B-25 B 24 SQL Server Unknown or Uncategorized Event Attributes... B-25 B 25 SQL Server User Session Audit Events... B-26 B 26 SQL Server User Session Event Attributes... B-27 C 1 Sybase ASE Account Management Audit Events... C-2 C 2 Sybase ASE Account Management Event Attributes... C-2 C 3 Sybase ASE Application Management Audit Events... C-3 C 4 Sybase ASE Application Management Event Attributes... C-3 C 5 Sybase ASE Audit Command Audit Events... C-5 C 6 Sybase ASE Audit Command Event Attributes... C-5 C 7 Sybase ASE Data Access Audit Events... C-6 C 8 Sybase ASE Data Access Event Attributes... C-6 C 9 Sybase ASE Exception Audit Events... C-7 C 10 Sybase ASE Exception Event Attributes... C-7 C 11 Sybase ASE Invalid Record Event Attributes... C-8 C 12 Sybase ASE Object Management Audit Events... C-10 C 13 Sybase ASE Object Management Event Attributes... C-10 C 14 Sybase ASE Peer Association Event Attributes... C-11 C 15 Sybase ASE Role and Privilege Management Audit Events... C-12 C 16 Sybase ASE Role and Privilege Management Event Attributes... C-13 C 17 Sybase ASE Service and Application Utilization Audit Events... C-14 C 18 Sybase ASE Service and Application Utilization Event Attributes... C-14 C 19 Sybase ASE System Management Audit Events... C-15 C 20 Sybase ASE System Management Event Attributes... C-16 C 21 Sybase ASE Unknown or Uncategorized Audit Events... C-17 C 22 Sybase ASE Unknown or Uncategorized Event Attributes... C-17 C 23 Sybase ASE User Session Audit Events... C-18 C 24 Sybase ASE User Session Event Attributes... C-19 xi

12 xii D 1 IBM DB2 Account Management Audit Events... D-2 D 2 IBM DB2 Account Management Event Attributes... D-2 D 3 IBM DB2 Application Management Audit Events... D-3 D 4 IBM DB2 Application Management Event Attributes... D-3 D 5 IBM DB2 Audit Command Audit Events... D-4 D 6 IBM DB2 Audit Command Event Attributes... D-5 D 7 IBM DB2 Data Access Audit Events... D-5 D 8 IBM DB2 Data Access Event Attributes... D-6 D 9 IBM DB2 Exception Event Attributes... D-6 D 10 IBM DB2 Invalid Record Event Attributes... D-7 D 11 IBM DB2 Object Management Audit Events... D-8 D 12 IBM DB2 Object Management Event Attributes... D-9 D 13 IBM DB2 Peer Association Event Attributes... D-10 D 14 IBM DB2 Role and Privilege Management Audit Events... D-10 D 15 IBM DB2 Role and Privilege Management Event Attributes... D-11 D 16 IBM DB2 Service and Application Utilization Audit Events... D-12 D 17 IBM DB2 Service and Application Utilization Event Attributes... D-12 D 18 IBM DB2 System Management Audit Events... D-13 D 19 IBM DB2 System Management Event Attributes... D-15 D 20 IBM DB2 Unknown or Uncategorized Audit Events... D-15 D 21 IBM DB2 Unknown or Uncategorized Event Attributes... D-16 D 22 IBM DB2 User Session Audit Events... D-16 D 23 IBM DB2 User Session Event Attributes... D-17

13 Preface Oracle Audit Vault Auditor's Guide explains how Oracle Audit Vault auditors can use the Audit Vault Console to monitor database activity in Oracle, Microsoft SQL Server, Sybase Adaptive Server Enterprise, and IBM DB2 databases. This preface contains: Audience Documentation Accessibility Related Documents Conventions Audience This document is intended for users who have been granted the AV_AUDITOR role and who are responsible for performing auditing tasks using Oracle Audit Vault. Documentation Accessibility Our goal is to make Oracle products, services, and supporting documentation accessible to all users, including users that are disabled. To that end, our documentation includes features that make information available to users of assistive technology. This documentation is available in HTML format, and contains markup to facilitate access by the disabled community. Accessibility standards will continue to evolve over time, and Oracle is actively engaged with other market-leading technology vendors to address technical obstacles so that our documentation can be accessible to all of our customers. For more information, visit the Oracle Accessibility Program Web site at Accessibility of Code Examples in Documentation Screen readers may not always correctly read the code examples in this document. The conventions for writing code require that closing braces should appear on an otherwise empty line; however, some screen readers may not always read a line of text that consists solely of a bracket or brace. Accessibility of Links to External Web Sites in Documentation This documentation may contain links to Web sites of other companies or organizations that Oracle does not own or control. Oracle neither evaluates nor makes any representations regarding the accessibility of these Web sites. xiii

14 Deaf/Hard of Hearing Access to Oracle Support Services To reach Oracle Support Services, use a telecommunications relay service (TRS) to call Oracle Support at An Oracle Support Services engineer will handle technical issues and provide customer support according to the Oracle service request process. Information about TRS is available at and a list of phone numbers is available at Related Documents For more information about Audit Vault, see the following documents: Oracle Audit Vault Administrator's Guide Oracle Database Vault Administrator's Guide Oracle Database Security Guide Oracle Database Advanced Security Administrator's Guide Oracle Database Reference Oracle Streams Concepts and Administration Oracle Database Data Warehousing Guide Oracle Technology Network (OTN) You can download free release notes, installation documentation, updated versions of this guide, white papers, or other collateral from the Oracle Technology Network (OTN). Visit: If you are not a member, you can register for free at: For security-specific information about OTN, visit: For the latest version of the Oracle documentation, including this guide, visit: Oracle Documentation Search Engine To access the database documentation search engine directly, visit: Oracle Audit Vault-Specific Sites For OTN information specific to Oracle Audit Vault, visit For the Oracle Audit Vault Discussion Forums, visit Oracle Store Printed documentation is available for sale in the Oracle Store at: xiv

15 My Oracle Support (formerly OracleMetaLink) You can find information about security patches, certifications, and the support knowledge base by visiting My Oracle Support at: Conventions The following text conventions are used in this document: Convention boldface italic monospace Meaning Boldface type indicates graphical user interface elements associated with an action, or terms defined in text or the glossary. Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values. Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter. xv

16 xvi

17 What's New in Oracle Audit Vault for Auditors? This section describes new features in Oracle Audit Vault that affect auditors, and provides pointers to additional information. This section contains: Near Real Time Activity Monitoring User Entitlement Audit Data Notifications for Alerts and Reports Trouble Ticket Notifications for Alerts Annotating and Attesting Alerts and Reports More Functionality for Advanced Alerts Scheduling Reports to be Sent to Other Users in PDF Format Additional and Changed Reports New and Changed Audit Events Oracle Audit Vault Console User Interface Enhancements Near Real Time Activity Monitoring Starting with this release, the Oracle Audit Vault data warehouse automatically refreshes, because Audit Vault can send thousands of audit records continuously to the repository. This feature enables the reports to reflect the up-to-the-latest collection point of the audit data content. See Chapter 4, "Oracle Audit Vault Data Warehouse Schema," for more information about the data warehouse. User Entitlement Audit Data This release introduces a new set of reports called entitlement reports. These reports capture privilege-related audit data from Oracle source databases, such as the types of privileges users have been granted, user account information, the system privileges that have been used in a source database, and so on. To view the entitlement information, you retrieve it from the source databases, similar to retrieving audit policies from source databases. Each time the entitlement content is retrieved from the Oracle database, it creates a snapshot of the entitlement xvii

18 information, which records the state of the entitlement data at the time of retrieval. With this information, you can compare the snapshots of the entitlement content to see how it has changed over time. For example, you can find out how a user s set of privileges were changed, or what object privileges were modified, between snapshots. See the following sections for more information: Section describes the entitlement reports Section 3.8 describes how to create and work with snapshot audit data Notifications for Alerts and Reports notifications have been integrated into the Oracle Audit Vault alerts and reports. This provides the ability to you and your security team when an alert has been triggered in Oracle Audit Vault. This way, you and your team can proactively review violations in the business processes or malicious activity. In addition, you can notify managers that a report is ready for their review of database activity performed by their database administrative team. The notification contains a link to the report from the Oracle Audit Vault console, or you can directly attach the report to the notification in PDF format. See the following sections for more information: Section describes how to create an notification profile, which is an address list that you can associate with the . Section describes how to create an notification template, which provides boilerplate text for the notification. Section 2.12 describes how to configure an alert to use the notification. Section 3.6 describes how to send other users an notification for a report. Trouble Ticket Notifications for Alerts You now can configure Oracle Audit Vault alerts to automatically generate trouble ticket notifications. Currently, you can use this feature for BMC Remedy Service Management trouble ticketing systems. See the following sections for more information: Section describes how to create a trouble ticket template, which contains boilerplate text to be used for the trouble ticket. Section 2.12 describes how to configure an alert to use the trouble ticket notification. Section 2.13 describes how to send a trouble ticket notification from an alert. Annotating and Attesting Alerts and Reports When you schedule a report, you can optionally assign other auditors to attest to the report. While reviewing the report in Oracle Audit Vault, you, the auditor, can annotate the report with comments that will remain until the report is deleted. This enables you to create a record of all notes and attestations for the report in one place, with the most recent note and attestation listed first. In addition to a record of all annotations and attestations, you can find additional detailed information about alerts and reports. xviii

19 See the following sections for more information: Section 3.6 describes how to assign other auditors to attest to a specific report. Section 3.7 describes how to annotate and attest a report. More Functionality for Advanced Alerts When you create an alert, you can create either a basic alert or an advanced alert. The advanced alert enables you to create a condition that can trigger the alert. In this release, you can incorporate more SQL functionality in the advanced alert condition that provides the ability to compare a list of valid values to incoming audit data content. For example, you can compare if the database activity was performed on a trusted host. You also can create PL/SQL functions that help you to retrieve more data to be used as a basis for triggering the alert. And, as described elsewhere in this section, you can configure the alert to be automatically sent to other users or to trigger a trouble ticket. See Section for more information. Scheduling Reports to be Sent to Other Users in PDF Format You now can schedule reports to be generated in PDF format and then send it to a list of recipient users and to other auditors to attest. You can design the report so that it only captures data within a specified window of time based on when the report is run, and set formatting standards such as header and footer information, and whether the report will appear in portrait or landscape orientation. See Section 3.6 for more information. Additional and Changed Reports This release of Oracle Audit Vault provides many additional compliance reports and entitlement reports, which are designed to help meet compliance regulations that were established by the Sarbanes-Oxley Act (SOX) and Health Insurance Portability and Accountability Act (HIPAA). The following table describes how the reports have changed for this release. Report Name Category of Report Change for This Release Audit Setting Changes Report All compliance reports Previously called the Changes to Audit Report Before/After Values Report All compliance reports Previously called the Data Change Report Changes to Audit Report Default compliance reports Now called the Audit Setting Changes Report Credit Card Related Data Access Report Credit card compliance reports New for this release Data Change Report Default compliance reports Now called the Before/After Values Report xix

20 Report Name Category of Report Change for This Release Database Failed Logins Report All compliance reports Previously called the Login Failures Report. Mostly the same as in earlier releases except that the report varies depending whether it is a credit card, financial, or health care compliance report. Database Login/Logoff Report All compliance reports Previously called the Login/Logoff Report. Mostly the same as in earlier releases except that the report varies depending whether it is a credit card, financial, or health care compliance report. Database Logoff Report All compliance reports Contains the user logoff information from the Login/Logoff Report. Mostly the same as in earlier releases except that the report varies depending whether it is a credit card, financial, or health care compliance report. Database Logon Report All compliance reports Contains the user logon information from the Login/Logoff Report. Mostly the same as in earlier releases except that the report varies depending whether it is a credit card, financial, or health care compliance report. Database Roles by Source Report Default entitlement reports New for this release Database Roles Report Default entitlement reports New for this release Database Startup/Shutdown Report All compliance reports New for this release Data Change Report Default compliance reports Now called the Program Changes Report DDL Report Default compliance reports Now called the Schema Changes Report Deleted Objects Report All compliance reports Mostly the same as in earlier releases except that the report varies depending whether it is a credit card, financial, or health care compliance report EPHI Related Data Access Report Financial Related Data Access Report Financial Related Data Modifications Report Health care compliance report Financial compliance reports Financial compliance reports New for this release New for this release New for this release Login Failures Report Default compliance reports Now called the Database Failed Logins Report Login/Logoff Report Default compliance reports Now called the Database Login/Logoff Report Object Privileges by Source Report Default entitlement reports New for this release Object Privileges Report Default entitlement reports New for this release Privileged Users by Source Report Default entitlement reports New for this release xx

21 Report Name Category of Report Change for This Release Privileged Users Report Default entitlement reports New for this release Program Changes Report All compliance reports Previously called the Data Change Report. Mostly the same as in earlier releases except that the report varies depending whether it is a credit card, financial, or health care compliance report. Schema Changes Report All compliance reports Previously called the DDL Report. Mostly the same as in earlier releases except that the report varies depending whether it is a credit card, financial, or health care compliance report. System Events Report All compliance reports New for this release System Privileges by Source Report Default entitlement reports New for this release System Privileges Report Default entitlement reports New for this release User Accounts by Source Report Default entitlement reports New for this release User Accounts Report Default entitlement reports New for this release User Privilege Change Activity All compliance reports New for this release Report User Privileges by Source Default entitlement reports New for this release Report User Privileges Report Default entitlement reports New for this release User Profiles by Source Report Default entitlement reports New for this release User Profiles Report Default entitlement reports New for this release See the following sections for more information about the new reports: Section 3.4 describes the new compliance reports. Section describes the new entitlement reports. New and Changed Audit Events This section contains: New and Changed Oracle Database Audit Events New Microsoft SQL Server Audit Events New and Changed Oracle Database Audit Events Starting with this release, Oracle Audit Vault supports the new audit events that were added to Oracle Database 11g Release 2 (11.2). Event Name Description Source Event Oracle Audit Vault Category ALTER ASSEMBLY 217 Application Management ALTER FLASHBACK ARCHIVE 219 System Management ALTER EDITION 213 Object Management ALTER MINING MODEL 130 Object Management xxi

22 Event Name Description Source Event Oracle Audit Vault Category ALTER PUBLIC SYNONYM 134 Object Management ALTER SYNONYM 192 Object Management CREATE ASSEMBLY 216 Application Management CREATE FLASHBACK ARCHIVE 218 System Management CREATE EDITION 212 Object Management CREATE MINING MODEL 133 Object Management DROP ASSEMBLY 215 Application Management DROP EDITION 214 Object Management DROP FLASHBACK ARCHIVE 220 System Management SELECT MINING MODEL 131 Data Access SUPER USER TRANSACTION CONTROL System Management In addition, the following Oracle Database source events have changed: Event Name Description Previous Source Event New Source Event SHUTDOWN STARTUP SUPER USER DDL SUPER USER DML SUPER USER LOGON SUPER USER UNKNOWN See Appendix A, "Oracle Database Audit Events," for more information. New Microsoft SQL Server Audit Events For Microsoft SQL Server 2008, the following new events have been added to the User Session Events category. Event Name Description Source Event Audit Vault Event Audit Database Mirroring Login Event DATABASE MIRRORING LOGIN:LOGIN SUCCESS DATABASE MIRRORING LOGIN:LOGIN PROTOCOL ERROR DATABASE MIRRORING LOGIN:MESSAGE FORMAT ERROR DATABASE MIRRORING LOGIN:NEGOTIATE FAILURE DATABASE MIRRORING LOGIN:AUTHENTICATION FAILURE DATABASE MIRRORING LOGIN:AUTHORIZATION FAILURE LOGON See Section B.14 for more information. xxii

23 Oracle Audit Vault Console User Interface Enhancements The Audit Vault Console has the following new enhancements: Dashboard. The Dashboard, accessible from the Home tab, has been expanded to include the following new information: Recently raised alerts, including all warning and critical alerts Top five objects accessed Failed logins Report accession actions for the auditor who has logged into the Audit Vault Auditor console The following components from earlier releases of Oracle Audit Vault are still available: View data time ranges Alert severity summary Summary of alert activity Top five audit source by number of alerts Alerts by audit event category Statement, Object, Privilege, FGA, and Capture Rules Audit Settings pages. The audit settings pages for statements, object privileges, fine-grained auditing, and capture rules now have a Mark All as Not Needed button. If you have set one or more policies as being needed (for example, by clicking the Mark All as Needed button) and realize that this was not a good idea, you can reverse the action by clicking the Mark All as Not Needed button. Audit Settings page. This page now has the following new functionality: User Entitlement option. This option enables you to retrieve user entitlement (privileges) information from the source databases. See "User Entitlement Audit Data" on page xvii for more information. Check boxes for individual source databases. You now can select one or more source databases and then perform a bulk retrieval of the audit policies and user entitlement information from the selected source databases. To select all the source databases, select the Select All link; to remove them from selection, select Select None. Settings tab. This tab provides access to pages that enable you to configure the following new features: notification profiles, notification templates, trouble ticket templates, and alert statuses. It also provides access to the Collector Status page. xxiii

24 xxiv

25 1 1 Introducing Oracle Audit Vault for Auditors This chapter contains: How Do Auditors Use Oracle Audit Vault? General Steps for Using Oracle Audit Vault Database Requirements for Collecting Audit Data Starting the Oracle Audit Vault Console Ensuring That the Oracle Audit Vault Collectors Can Collect Data 1.1 How Do Auditors Use Oracle Audit Vault? Oracle Audit Vault collects audit data from multiple databases and then consolidates this data in a set of audit reports. You can collect audit data from multiple instances of the following database products: Oracle Database (including Oracle Real Application Clusters and Oracle Data Guard) Microsoft SQL Server Sybase Adaptive Server Enterprise (ASE) IBM DB2 Before you, as an auditor, can use Oracle Audit Vault, an Audit Vault administrator must configure the Audit Vault Server to connect to your source databases. Oracle Audit Vault then collects the audit data that these databases generate, organizes the data, and provides it to you in a variety of reports. For Oracle databases, you can create policies and collect data from redo log files. For all four database products, you can create alerts to help you detect security threats to these databases. For example, an alert can notify you when a system administrator tries to view sensitive application data, such as employee salaries. In addition to the Oracle Audit Vault reports, you can design reports using another tool, such as Oracle Business Intelligence, or with third-party products. To manage Oracle Audit Vault policies, alerts, and reports, you use the Audit Vault Console. The Oracle Audit Vault default reports are designed to satisfy standard compliance regulations, such as those mandated by the Sarbanes-Oxley Act. You can create user-defined versions of these reports for specific needs. For example, you can create reports to track activities that occur outside of normal office hours, or to track the activities of specific users. The audit policies feature lets you manage audit policies for Oracle Database source databases. Because Oracle Audit Vault centralizes audit settings for Oracle Database, Introducing Oracle Audit Vault for Auditors 1-1

26 General Steps for Using Oracle Audit Vault your job as an auditor is easier and more efficient. You can create, manage, and monitor audit information from one location. This also makes it easier to demonstrate the compliance policy of your company to outside auditors. The audit data collected by Oracle Audit Vault is stored in its own secure data warehouse repository, where an administrator can use Oracle Database Vault and Oracle Advanced Security to prevent tampering with the audit data. 1.2 General Steps for Using Oracle Audit Vault To use Oracle Audit Vault, follow these general steps: Step 1: Ensure That the Source Databases Are Collecting Audit Data Step 2: Create Audit Policies for Oracle Database Data Step 3: Optionally, Create and Monitor Alerts Step 4: View and Customize the Oracle Audit Vault Reports Step 5: Respond to Reports and Alerts Step 1: Ensure That the Source Databases Are Collecting Audit Data Check that auditing is enabled in the databases from which you want to collect audit data and that the Oracle Audit Vault collectors are working. For source databases, there are recommended audit settings that your database administrator should consider having in place. Your database administrator also should ensure that these databases are properly configured to send audit data to the Audit Vault Server. See Section 1.3 and Section 1.5 for more information Step 2: Create Audit Policies for Oracle Database Data You use the Audit Vault Console to manage audit policies for Oracle Database source databases. Section 1.4 explains how to start the Audit Vault Console. You can create policies for the following kinds of data: SQL statements. You can audit statements that users use when attempting to query the database or modify data, such as SELECT or UPDATE. Database Schema Objects. You can audit actions that users may try to perform on database objects, tables, or views. Database Privileges. You can audit the use of a system privilege, such as SELECT ANY TABLE. In this kind of auditing, Oracle Audit Vault records SQL statements that require the audited privilege to succeed. Fine-grained audit conditions. You can audit specific activities that take place in the database, such as whether an IP address from outside the corporate network is being used, or if specific table columns are being modified. Redo log data. You can capture data from redo log files. The redo log files store all changes that occur in the database. Every instance of an Oracle database has an associated redo log to protect the database in case of an instance failure. In Oracle Audit Vault, the capture rule specifies DML and DDL changes that should be checked when Oracle Database scans the database redo log. For SQL statements, objects, privileges, and fine-grained auditing data, you create audit policies. For redo log data, you create a capture rule. 1-2 Oracle Audit Vault Auditor's Guide

27 General Steps for Using Oracle Audit Vault Chapter 2, "Creating Oracle Audit Vault Policies and Alerts" describes how to create audit policies and capture rules Step 3: Optionally, Create and Monitor Alerts You can create either warnings or critical alerts that are triggered when certain events occur in an Oracle Database, SQL Server, Sybase ASE, or IBM DB2 database. You can configure the notifications or trouble tickets in response to the alert. Oracle Audit Vault alerts enable you to detect threats, which helps keep systems in compliance with internal and external policies. After you create the alerts, you can monitor them in the Audit Vault Console. Section 2.12 explains how you can configure and trouble ticket notifications, and create and monitor alerts Step 4: View and Customize the Oracle Audit Vault Reports Oracle Audit Vault automatically populates its reports with the audit data from your source databases. You can view this data by selecting from the reports provided in the Audit Vault Console Default Reports, Compliance Reports, and User-Defined Reports pages. The reports are organized by commonly used categories, including categories for compliance regulations. You can perform the following actions with the reports: Create user-defined reports to filter specific data. Send the report to other users as a PDF file. Schedule the report to be generated at specific times and then sent to users as a PDF file. You can create an distribution list, called a profile, to be used specifically for different types of reporting and alert activities. Oracle Audit Vault has an open data warehouse schema, which you can use to build custom reports using Oracle Application Express, business intelligence tools such as Oracle Business Intelligence Publisher, or third-party business intelligence tools. Chapter 3, "Using Oracle Audit Vault Reports" explains how to view and customize Oracle Audit Vault reports Step 5: Respond to Reports and Alerts At this stage, the Oracle Audit Vault reports and alerts are generating as Audit Vault monitors your source databases. When you review an Audit Vault report, you can annotate and attest the report, which is described in Section 3.7. When you are notified of an alert, you can take the following actions: Notify other users of the alert so that they can take the appropriate actions. Log a trouble ticket if one is necessary. In this release, you can log trouble tickets to the BMS Remedy Service Management trouble ticketing system. You can design trouble ticket templates to be used for different types of trouble ticket scenarios. View notes that other users may have created for the alert report. Set a status for the alert, such as NEW or CLOSED. Section 2.13 explains how to respond to an alert. Introducing Oracle Audit Vault for Auditors 1-3

28 Database Requirements for Collecting Audit Data 1.3 Database Requirements for Collecting Audit Data This section contains: Requirements for Oracle Database Requirements for SQL Server, Sybase ASE, and IBM DB2 Databases Requirements for Oracle Database This section contains: Ensuring That Auditing Is Enabled in the Source Database Using Recommended Audit Settings in the Source Database Ensuring That Auditing Is Enabled in the Source Database Before Oracle Audit Vault can collect audit data from the source databases, auditing must be enabled in those databases. A database administrator can check the type of auditing your database uses by logging in to SQL*Plus and running the appropriate command. For example, to check if standard auditing is enabled: SQL> SHOW PARAMETER AUDIT_TRAIL NAME TYPE VALUE audit_trail string DB This output shows that standard auditing is enabled and audit records are being written to the database audit trail. For fine-grained auditing, you can query the AUDIT_TRAIL column of the DBA_ AUDIT_POLICIES data dictionary view to find the audit trail types that are set for the fine-grained audit policies on the database. For more information, see Oracle Database Security Guide. 1-4 Oracle Audit Vault Auditor's Guide

29 Database Requirements for Collecting Audit Data Table 1 1 Table 1 1 describes the audit trail types and their corresponding Audit Vault collectors. Oracle Database Audit Trail Types and Corresponding Collectors Audit Trail Type How Enabled Corresponding Collector Database audit trail Operating system audit trail Redo log files For standard audit records: The AUDIT_TRAIL initialization parameter is set to DB or DB, EXTENDED. For fine-grained audit records: The audit_trail parameter of the DBMS_FGA.ADD_POLICY procedure is set to DBMS_FGA.DB or DBMS_FGA.DB + DBMS_ FGA.EXTENDED. For standard audit records: The AUDIT_TRAIL initialization parameter is set to OS, XML, or XML, EXTENDED. For syslog audit trails, AUDIT_TRAIL is set to OS and the AUDIT_SYS_OPERATIONS parameter is set to TRUE. In addition, the AUDIT_SYSLOG_LEVEL parameter must be set. For fine-grained audit records: The audit_trail parameter of the DBMS_FGA.ADD_POLICY procedure is set to DBMS_FGA.XML or DBMS_FGA.XML + DBMS_ FGA.EXTENDED. The table that you want to audit must be eligible. See "Creating Capture Rules for Redo Log File Auditing" on page 2-17 for more information. DBAUD OSAUD REDO Using Recommended Audit Settings in the Source Database After your database administrator checks that auditing is enabled, Oracle recommends that the following areas of the database have auditing enabled: Database schema or structure changes. Use the following AUDIT SQL statement settings: AUDIT ALTER ANY PROCEDURE BY ACCESS; AUDIT ALTER ANY TABLE BY ACCESS; AUDIT ALTER DATABASE BY ACCESS; AUDIT ALTER SYSTEM BY ACCESS; AUDIT CREATE ANY JOB BY ACCESS; AUDIT CREATE ANY LIBRARY BY ACCESS; AUDIT CREATE ANY PROCEDURE BY ACCESS; AUDIT CREATE ANY TABLE BY ACCESS; AUDIT CREATE EXTERNAL JOB BY ACCESS; AUDIT DROP ANY PROCEDURE BY ACCESS; AUDIT DROP ANY TABLE BY ACCESS; Database access and privileges. Use the following AUDIT SQL statements: AUDIT ALTER PROFILE BY ACCESS; AUDIT ALTER USER BY ACCESS; AUDIT AUDIT SYSTEM BY ACCESS; Introducing Oracle Audit Vault for Auditors 1-5

30 Starting the Oracle Audit Vault Console AUDIT CREATE PUBLIC DATABASE LINK BY ACCESS; AUDIT CREATE SESSION BY ACCESS; AUDIT CREATE USER BY ACCESS; AUDIT DROP PROFILE BY ACCESS; AUDIT DROP USER BY ACCESS; AUDIT EXEMPT ACCESS POLICY BY ACCESS; AUDIT GRANT ANY OBJECT PRIVILEGE BY ACCESS; AUDIT GRANT ANY PRIVILEGE BY ACCESS; AUDIT GRANT ANY ROLE BY ACCESS; AUDIT ROLE BY ACCESS; Requirements for SQL Server, Sybase ASE, and IBM DB2 Databases Ensure that auditing is enabled in these databases. You also should ensure that they are correctly configured to send audit data to the Audit Vault Server. A database administrator can check these requirements for you. For more information, check the documentation for these three products and Oracle Audit Vault Administrator's Guide. 1.4 Starting the Oracle Audit Vault Console To start the Audit Vault Console: 1. From a browser, enter the following URL: In this specification: host is the server where you installed Oracle Audit Vault port is the Audit Vault Console HTTP port number For example: If you are unsure of the URL, from the terminal window that you use for the Audit Vault Server, enter the following command, which displays the URL that starts the Audit Vault Console: $ avctl show_av_status 2. In the Login page, enter your user name and password. From the Connect As list, select AV_AUDITOR. Then click Login. The Dashboard page appears and displays information about configured alerts and audit trail activity. 1-6 Oracle Audit Vault Auditor's Guide

31 Ensuring That the Oracle Audit Vault Collectors Can Collect Data From the Dashboard page, you can do the following: View audit data from a range of dates. To view the audit data, which includes data such as the top five objects accessed and failed logins, specify the range you want, and then click the Go button. To automatically refresh the data every 60 seconds, click the Refresh every 60 seconds check box, or manually refresh it by clicking the Refresh button. Check alerts. The Dashboard page displays recently raised alerts, as well as all warning and critical alerts. Check attestation actions. The Dashboard page displays a list of reports that you may need to attest. Create Oracle Database audit policies and alerts. Chapter 2, "Creating Oracle Audit Vault Policies and Alerts" explains how to create policies and alerts for an Oracle database. Access audit reports. You can view audit information that has been collected in the Oracle Audit Vault reports. Optionally, you can control the display of data and create user-defined reports. See Chapter 3, "Using Oracle Audit Vault Reports" for more information. Ensure that the Oracle Audit Vault collection agents are working. Section 1.5 explains how to ensure that these agents are collecting audit data. 1.5 Ensuring That the Oracle Audit Vault Collectors Can Collect Data The Oracle Audit Vault collection agents are responsible for the connection between the source database and the Audit Vault Server while collectors collect the audit data. In the Audit Vault Console, you can check the status of the collection agents and collectors. If you cannot access Oracle Database audit policies, or if the Oracle Audit Introducing Oracle Audit Vault for Auditors 1-7

32 Ensuring That the Oracle Audit Vault Collectors Can Collect Data Table 1 2 Vault default reports do not show any information, then the collection agents may not be working, or the source database has been shut down. See also Oracle Audit Vault Administrator's Guide for additional troubleshooting tips for the reports. To check the status of the source database collection agents: 1. Log in to the Audit Vault Console as a user who has been granted the AV_ AUDITOR role. Section 1.4 explains how to log in to the Audit Vault Console. 2. Click the Settings tab. 3. Click the Collection Status secondary tab. The Collection Status page shows the following information for collectors: Source name. The name of the audit source database where the audit data is being collected Collector Name. Name of the collector Agent Name. The name of the agent with which this collector is associated Bytes Per Sec. Number of bytes per second it takes to retrieve the audit data Records Per Sec. Number of audit records that are being retrieved per second Is Alive. Whether the collector is running or not. When the collector is up, a green up arrow indicator is displayed. When the collector is down, a red down arrow indicator is displayed. When there is a problem, an error is displayed. If the collector is not working, then contact your Oracle Audit Vault administrator. Table 1 2 summarizes the database collector types. Database Collector Types Provided by Oracle Audit Vault Database Collectors Description Oracle DBAUD Collector that performs the following: Extracts audit records from the Oracle Database audit trail. For the standard audit trail, it extracts records from the SYS.AUD$ system table. For fine-grained auditing, it extracts audit events from the SYS.FGA_LOG$ system table. Extracts audit records from the Oracle Database Vault audit trail DVSYS.AUDIT_TRAIL$ table Oracle OSAUD Collector that performs the following: For Linux and UNIX platforms: Extracts audit records from the operating system files (audit logs) and XML (.xml) files) For Linux and UNIX platforms: SYSLOG Collector to extract audit records from the system audit trail where database audit trail records are written to a syslog file For Microsoft Windows: EVTLOG Collector to extract audit records from the system audit trail where database audit trail records are written to the Event Log Oracle REDO Collector using Oracle Streams technology to retrieve logical change records from the redo logs. 1-8 Oracle Audit Vault Auditor's Guide

33 Ensuring That the Oracle Audit Vault Collectors Can Collect Data Table 1 2 (Cont.) Database Collector Types Provided by Oracle Audit Vault Database Collectors Description SQL Server MSSQLDB Collector (for Windows platforms) to extract audit records from Microsoft SQL Server databases from the Windows Event logs, Server-side trace files, and C2 auditing logs. Sybase ASE SYBDB Collector to extract audit records from the Sybase databases audit trail logged in audit tables in the SYBSECURITY database. IBM DB2 DB2DB Collector to extract records from the ASCII text file in which IBM DB2 generates audit data. Introducing Oracle Audit Vault for Auditors 1-9

34 Ensuring That the Oracle Audit Vault Collectors Can Collect Data 1-10 Oracle Audit Vault Auditor's Guide

35 2 2 Creating Oracle Audit Vault Policies and Alerts This chapter contains: About Oracle Audit Vault Policies and Alerts General Steps for Creating Oracle Audit Vault Policies and Alerts Retrieving Audit Policy Settings from the Source Oracle Database Creating Oracle Vault Audit Policies for SQL Statements Creating Oracle Audit Vault Policies for Schema Objects Creating Oracle Audit Vault Policies for Privileges Creating Oracle Audit Vault Policies for Fine-Grained Auditing Creating Capture Rules for Redo Log File Auditing Verifying Oracle Audit Vault Policy Settings Provisioning Audit Vault Policies to the Source Oracle Database Copying Oracle Audit Vault Policies to Other Oracle Databases Creating and Configuring Alerts Responding to an Alert Setting a Retention Period for Audit Data 2.1 About Oracle Audit Vault Policies and Alerts In the Audit Vault Console, you can create the following types of audit policies for Oracle databases: SQL statements Schema objects Privileges Fine-grained auditing Capture rules (for redo log file activities) For all database types, you can create alerts. See Section 2.12 for more information. Creating Oracle Audit Vault Policies and Alerts 2-1

36 General Steps for Creating Oracle Audit Vault Policies and Alerts 2.2 General Steps for Creating Oracle Audit Vault Policies and Alerts In general, to create Oracle Audit Vault policies and alerts, you follow these steps: 1. Retrieve the current policy settings from the source Oracle database. See Section 2.3 for more information. 2. Create audit policies. See the following sections: Section 2.4 to create SQL statement policies Section 2.5 to create schema object policies Section 2.6 to create privilege policies Section 2.7 to create fine-grained auditing policies Section 2.8 to create capture rules for redo log file auditing Section 2.9 to verify the Oracle Audit Vault policies 3. Save the Oracle Audit Vault policy settings to a.sql file or manually provision them to the source database. See the following sections: Section 2.10 to export the policies to the source Oracle database Section 2.11 to copy the policy settings to other Oracle databases 4. Optionally, create alerts. See Section 2.12 for more information. 5. Optionally, set a retention period for the audit data from all source databases. See Section 2.14 for more information. 2.3 Retrieving Audit Policy Settings from the Source Oracle Database Before you create policies in the Audit Vault Console, you must retrieve the current audit settings that have been created in the source Oracle database. This way, you have a snapshot of the audit settings in the source database from that point in time, before you begin to create policies and alerts. Follow these steps: Step 1: Retrieve the Audit Settings from the Source Oracle Database Step 2: Activate (Update) the Fetched Audit Settings State Step 1: Retrieve the Audit Settings from the Source Oracle Database To retrieve audit settings from the source Oracle Database: 1. Log in to the Audit Vault Console as a user who has been granted the AV_ AUDITOR role. Section 1.4 explains how to start the Audit Vault Console. The Dashboard page appears. 2. In the Audit Vault Console, select the Audit Policy tab. By default, the Audit Settings page appears. 2-2 Oracle Audit Vault Auditor's Guide

37 Retrieving Audit Policy Settings from the Source Oracle Database 3. From the Audit Source listing, select the check boxes for the source databases you want. To filter the list of audit sources, enter text in the Audit Source text field or click the flashlight icon to display the Search And Select: Audit Source page. If you make selections on the Search And Select: Audit Source page, when you return, the Audit Source column will be populated with your selections. 4. Click the Audit Settings option. 5. Click the Retrieve button. Oracle Audit Vault displays a message letting you know that the audit policy data is being retrieved. To check the status of the retrieval, click the Show Status button. The Audit Vault Console displays a summary of audit settings for the available source databases. At this stage, you are ready to view the audit settings. Table 2 1 shows the fields used in the audit settings list in the Audit Settings page, which indicate the state of the source database. If the Problem field contains a value higher than 0, then most likely you must activate (that is, update for use in Oracle Audit Vault) the audit settings. If the Problem field is set to 0, then all the existing audit settings already have been activated. Table 2 1 Field Select Audit Source In Use Needed Problem Fields Under Apply Audit Settings in the Audit Settings Page Description Select the audit source to retrieve Displays the name of the audit source database Number of active settings in the source database Number of required audit settings you (the auditor) have specified Number of audit settings that require attention by the auditor Creating Oracle Audit Vault Policies and Alerts 2-3

38 Retrieving Audit Policy Settings from the Source Oracle Database Table 2 1 Field Audit Trail Audit Sys Audit Setting Retrieved Audit Setting Provisioned User Entitlement Retrieved (Cont.) Fields Under Apply Audit Settings in the Audit Settings Page Description The location to which database audit records are directed, based on the AUDIT_TRAIL initialization parameter. See Oracle Database Reference for the AUDIT_TRAIL parameter values. If the setting is NONE, then ask the database administrator to enable auditing. See Section for more information. Indicates that the SYS user is being audited The time that the audit information for the selected audit source was last retrieved The time that the audit settings were provisioned to the source database The time that the user entitlement information was retrieved. See Section 3.8 for more information Step 2: Activate (Update) the Fetched Audit Settings State After you retrieve the source database audit settings, you can view and modify them as needed. Remember that you are capturing a snapshot of the audit settings from a particular point in time: if these settings change in the source database, then you must retrieve the audit settings again. 1. In the Audit Settings page, select the name of the source database listed in the Audit Source field. The Apply Audit Settings section appears. In the following example, the Problem field shows that there are three SQL statement audit settings that may need to be activated or removed from the source database. None of the other audit settings types must be activated. A nonzero value in the Problem field can indicate that an audit policy that was created in the source database has not yet been updated in Oracle Audit Vault. If you do not need the audit policy, then do not activate it. In that case, when you provision the Audit Vault settings back to the source database, this audit policy will be deleted in the source database. 2. To update the statement audit settings, select the Statement tab. 2-4 Oracle Audit Vault Auditor's Guide

39 Creating Oracle Vault Audit Policies for SQL Statements The Statement page appears. The settings that must be updated are indicated with an X in the Needed column. As the Audit Vault auditor, you can indicate that the audit policies are required. 3. Select each X in the Needed column to update the audit settings for SQL statements. Alternatively, click the Mark All as Needed button select all the audit settings. To deselect all of the selected settings, click Mark All as Not Needed. A check mark indicates that the Oracle Audit Vault auditor has determined that the audit setting is needed. A green up arrow in the In Use column indicates that both Oracle Audit Vault and the source database are currently storing consistent definitions of the audit policies. A red X in the Needed column indicates that these policy definitions are inconsistent, with Oracle Audit Vault having the outdated version of the policy. 4. After completing the Needed column updates, click the Save All Audit Settings button. At this stage, the audit settings between the source database and Oracle Audit Vault should be the same, except for any settings that you have omitted in Step 3, or if changes in the audit settings are made independently in the source database. 2.4 Creating Oracle Vault Audit Policies for SQL Statements This section contains: About SQL Statement Auditing Defining a SQL Statement Audit Policy About SQL Statement Auditing Statement auditing audits SQL statements by type of statement, not by the specific schema objects on which the statement operates. Statement auditing can be broad or focused (for example, by auditing the activities of all database users or only a select list of users). Typically broad statement auditing audits the use of several types of related actions for each option. These statements are in the following categories: Data definition statements (DDL). For example, AUDIT TABLE audits all CREATE TABLE and DROP TABLE statements. AUDIT TABLE tracks several DDL Creating Oracle Audit Vault Policies and Alerts 2-5

40 Creating Oracle Vault Audit Policies for SQL Statements statements regardless of the table on which they are issued. You can also set statement auditing to audit selected users or every user in the database. Data manipulation statements (DML). For example, AUDIT SELECT TABLE audits all SELECT... FROM TABLE or SELECT... FROM VIEW statements, regardless of the table or view Defining a SQL Statement Audit Policy To define a SQL statement audit policy: 1. If necessary, retrieve and activate the current statement audit policies. See Section 2.3 for more information. 2. In the Audit Settings page, select the Statement tab to display the Statement page. Table 2 2 on page 2-6 describes the fields used in the Statement page. 3. Click the Create button and in the Create Statement Audit page, define the audit policy. Table 2 3 on page 2-7 describes the Create Statement Audit fields. 4. Click OK. The statement audit policy is created. To ensure that the statement audit policy is semantically correct, see Section In the Dashboard page, select Save All Audit Settings. To display the Dashboard page, click the Audit Settings link, and then in the Audit Settings page, select the name of the source database. Table 2 2 lists the fields used in the Statement page. Table 2 2 Field (Leftmost column) Fields in the Statement Page Description An exclamation mark icon indicates one of the following conditions: The statement is needed but is not in use. The statement is in use but is not needed. Statement User The statement that is audited The user to which this setting applies, if any 2-6 Oracle Audit Vault Auditor's Guide

41 Creating Oracle Vault Audit Policies for SQL Statements Table 2 2 Field Proxy User Execution Condition Audit granularity In Use Needed (Rightmost column) (Cont.) Fields in the Statement Page Description The proxy user for the database, if any The execution condition audited: WHENEVER SUCCESSFUL, WHENEVER NOT SUCCESSFUL, or BOTH The granularity of auditing: BY ACCESS or BY SESSION The arrow points upward if the setting is active in the source database and downward if it has not been provisioned or is not active. A check mark indicates that the policy is needed. An X indicates that the policy is not needed. If a policy that is not in use is set to needed, the In Use arrow points up after provisioning. If a policy that is in use is set to not needed, the audit policy is no longer displayed after provisioning. To select all policies as needed, click the Mark All as Needed button. To reverse this action, click Mark All as Not Needed. Click the trash can icon to remove the policy. You can use the trash can icon to remove the policy only if you had just created it and decided it was not required in the source database, or if it is not active in the source database. Table 2 3 lists the fields used in the Create Statement Audit page. Table 2 3 Field Statements Fields in the Create Statement Audit Page Description Select the SQL statements to audit. To display the list of SQL statements for selection, click the flashlight icon. Examples are: ALTER TABLE DATABASE LINK DROP DIRECTORY Audited By Statement Execution Condition Choose the category of users to audit: All: Audits all users, including proxy users. User: Audits the user to which this setting applies. When you select this option, the Users field appears, in which you must specify at least one user. To display a list of users and their audit sources for selection, click the flashlight icon. Proxy User: Audits the proxy user for the database. When you select this option, the Proxy User field appears, in which you must specify at least one user. To display a list of proxy users and their audit sources for selection, click the flashlight icon. Choose the execution condition: Both: Audits both successful and failed statements Success: Audits the statement if it is successful Failure: Audits the statement if it fails Creating Oracle Audit Vault Policies and Alerts 2-7

42 Creating Oracle Audit Vault Policies for Schema Objects Table 2 3 Field (Cont.) Fields in the Create Statement Audit Page DML Audit Granularity Description Choose the level of granularity: Access: Creates an audit record each time the operation occurs Session: Creates an audit record the first time an operation occurs in the current session 2.5 Creating Oracle Audit Vault Policies for Schema Objects This section contains: About Schema Object Auditing Defining a Schema Object Audit Policy About Schema Object Auditing Schema object auditing is the auditing of specific statements on a particular schema object, such as AUDIT SELECT ON HR.EMPLOYEES. Schema object auditing is very focused, auditing only a specific statement on a specific schema object for all users of the database. For example, object auditing can audit all SELECT and DML statements permitted by object privileges, such as SELECT or DELETE statements on a given table. The GRANT and REVOKE statements that control those privileges are also audited. Object auditing lets you audit the use of powerful database commands that enable users to view or delete very sensitive and private data. You can audit statements that reference tables, views, sequences, standalone stored procedures or functions, and packages. Oracle Database and Oracle Audit Vault always set schema object audit options for all users of the database. You cannot set these options for a specific list of users Defining a Schema Object Audit Policy To define a schema object audit policy: 1. If necessary, retrieve and activate the current object audit policies. See Section 2.3 for more information. 2. In the Audit Settings page, select the Object tab to display the Object page. Table 2 4 on page 2-9 describes the fields used in the Object page. 3. Click the Create button and in the Create Object Audit page, define the audit policy. Table 2 5 on page 2-9 describes the Create Object Audit fields. 4. Click OK. The object audit policy is created. To ensure that the object audit policy is semantically correct, see Section In the Dashboard page, select Save All Audit Settings. To display the Dashboard page, click the Audit Settings link, and then in the Audit Settings page, select the name of the source database. 2-8 Oracle Audit Vault Auditor's Guide

43 Creating Oracle Audit Vault Policies for Schema Objects Table 2 4 lists the fields used in the Object page. Table 2 4 Field (Leftmost column) Fields in the Object Page Description An exclamation mark icon indicates one of the following conditions: The statement is needed but is not in use. The statement is in use but is not needed. Statement Schema Object Execution Condition Audit granularity In Use Needed (Rightmost column) The statement that is audited The database schema to which this setting applies The object (such as a database table) to which this setting applies The execution condition audited: WHENEVER SUCCESSFUL, WHENEVER NOT SUCCESSFUL, or BOTH The granularity of auditing: BY ACCESS or BY SESSION The arrow points upward if the setting is active in the source database and downward if it has not been provisioned or is not active. A check mark indicates that the policy is needed. An X indicates that the policy is not needed. If a policy that is not in use is set to needed, the In Use arrow points up after provisioning. If a policy that is in use is set to not needed, the audit policy is no longer displayed after provisioning. To select all policies as needed, click the Mark All as Needed button. To reverse this action, click Mark All as Not Needed. Click the trash can icon to remove the policy. You can use the trash can icon to remove the policy only if you had just created it and decided it was not required in the source database, or if it is not active in the source database. Table 2 5 lists the fields used in the Create Object Audit page. Table 2 5 Field Statements Object Type Fields in the Create Object Audit Page Description Select the SQL statements to audit. To display a list of SQL statements for selection, click the flashlight icon. Examples are: ALTER AUDIT UPDATE Select the type of object to audit, such as table. To display a list of object types and their audit sources for selection, click the flashlight icon. Examples are: LOB RULE TABLE VIEW Creating Oracle Audit Vault Policies and Alerts 2-9

44 Creating Oracle Audit Vault Policies for Privileges Table 2 5 Field Object Statement Execution Condition (Cont.) Fields in the Create Object Audit Page Description Optional. Select the object to audit. To display a list of objects and their source databases for selection, and to filter the list by audit source and object owner, click the flashlight icon. For example, if you entered TABLE for the Object Type field, you could select EMPLOYEES, JOBS, or any of the other tables in the HR schema. Choose the execution condition: Both: Audits both successful and failed statements Success: Audits the statement if it is successful Failure: Audits the statement if it fails DML Audit Granularity Choose the level of granularity: Access: Creates an audit record each time the operation occurs Session: Creates an audit record the first time an operation occurs in the current session 2.6 Creating Oracle Audit Vault Policies for Privileges This section contains: About Privilege Auditing Defining a Privilege Audit Policy About Privilege Auditing Privilege auditing is the auditing of SQL statements that use a system privilege. You can audit the use of any system privilege. Like statement auditing, privilege auditing can audit the activities of all database users or only a specified list of users. For example, if you enable AUDIT SELECT ANY TABLE, Oracle Database audits all SELECT tablename statements issued by users who have the SELECT ANY TABLE privilege. This type of auditing is very important for the Sarbanes-Oxley (SOX) Act compliance requirements. Sarbanes-Oxley and other compliance regulations require the privileged user be audited for inappropriate data changes or fraudulent changes to records. Privilege auditing audits the use of powerful system privileges enabling corresponding actions, such as AUDIT CREATE TABLE. If you set both similar statement and privilege audit options, then only a single audit record is generated. For example, if the statement clause TABLE and the system privilege CREATE TABLE are both audited, then only a single audit record is generated each time a table is created. The statement auditing clause, TABLE, audits CREATE TABLE, ALTER TABLE, and DROP TABLE statements. However, the privilege auditing option, CREATE TABLE, audits only CREATE TABLE statements, because only the CREATE TABLE statement requires the CREATE TABLE privilege. Privilege auditing does not occur if the action is already permitted by the existing owner and schema object privileges. Privilege auditing is triggered only if these privileges are insufficient, that is, only if what makes the action possible is a system privilege. Privilege auditing is more focused than statement auditing for the following reasons: 2-10 Oracle Audit Vault Auditor's Guide

45 Creating Oracle Audit Vault Policies for Privileges It audits only a specific type of SQL statement, not a related list of statements. It audits only the use of the target privilege Defining a Privilege Audit Policy To define a privilege audit policy: 1. If necessary, retrieve and activate the current privilege audit policies. See Section 2.3 for more information. 2. In the Audit Settings page, select the Privilege tab to display the Privilege page. Table 2 6 on page 2-11 describes the fields used in the Privilege page. 3. Click the Create button and in the Create Privilege Audit page, define the privilege audit policy. Table 2 7 on page 2-12 describes the Create Privilege Audit fields. 4. Click OK. The privilege audit policy is created. To ensure that the privilege audit policy is semantically correct, see Section In the Dashboard page, select Save All Audit Settings. To display the Dashboard page, click the Audit Settings link, and then in the Audit Settings page, select the name of the source database. Table 2 6 lists the fields used in the Privilege page. Table 2 6 Field (Leftmost column) Fields in the Privilege Page Description An exclamation mark icon indicates one of the following conditions: The statement is needed but is not in use. The statement is in use but is not needed. Privilege User Proxy User Execution Condition Audit granularity In Use Needed The privilege that is audited The user to which this setting applies The proxy user for the database, if any The execution condition audited: WHENEVER SUCCESSFUL, WHENEVER NOT SUCCESSFUL, or BOTH The granularity of auditing: BY ACCESS or BY SESSION The arrow points upward if the setting is active in the source database and downward if it has not been provisioned or is not active. A check mark indicates that the policy is needed. An X indicates that the policy is not needed. If a policy that is not in use is set to needed, the In Use arrow points up after provisioning. If a policy that is in use is set to not needed, the audit policy is no longer displayed after provisioning. To select all policies as needed, click the Mark All as Needed button. To reverse this action, click Mark All as Not Needed. Creating Oracle Audit Vault Policies and Alerts 2-11

46 Creating Oracle Audit Vault Policies for Fine-Grained Auditing Table 2 6 Field (Rightmost column) (Cont.) Fields in the Privilege Page Description Click the trash can icon to remove the policy. You can use the trash can icon to remove the policy only if you had just created it and decided it was not required in the source database, or if it is not active in the source database. Table 2 7 lists the fields used in the Create Privilege Audit page. Table 2 7 Field Privilege Fields in the Create Privilege Audit Page Description Select the privilege to audit. To display a list of privileges for selection, click the flashlight icon. Examples are: ADMINISTER DATABASE TRIGGER CREATE ANY TABLE MANAGE TABLESPACE Audited By Statement Execution Condition DML Audit Granularity Choose the category of users to audit: All: Audits all users, including proxy users. User: Audits the user to which this setting applies. When you select this option, the Users field appears, in which you must specify at least one user. To display a list of users and their audit sources for selection, click the flashlight icon. Proxy User: Audits the proxy user for the database. When you select this option, the Proxy User field appears, in which you must specify at least one user. To display a list of proxy users and their audit sources for selection, click the flashlight icon. Choose the execution condition: Both: Audits both successful and failed statements Success: Audits the statement if it is successful Failure: Audits the statement if it fails Choose the level of granularity: Access: Creates an audit record each time the operation occurs Session: Creates an audit record the first time an operation occurs in the current session 2.7 Creating Oracle Audit Vault Policies for Fine-Grained Auditing This section contains: About Fine-Grained Auditing Defining a Fine-Grained Auditing Policy About Fine-Grained Auditing Fine-grained auditing (FGA) enables you to create a policy that defines specific conditions that must exist for the audit to occur. For example, fine-grained auditing lets you audit the following types of activities: 2-12 Oracle Audit Vault Auditor's Guide

47 Creating Oracle Audit Vault Policies for Fine-Grained Auditing Accessing a table between 9 p.m. and 6 a.m. or on Saturday and Sunday Using an IP address from outside the corporate network Selecting or updating a table column Modifying a value in a table column A fine-grained audit policy provides granular auditing of select, insert, update, and delete operations. Furthermore, you reduce the amount of audit information generated by restricting auditing to only the conditions that you want to audit. This creates a more meaningful audit trail that supports compliance requirements. For example, a central tax authority can use fine-grained auditing to track access to tax returns to guard against employee snooping, with enough detail to determine what data was accessed. It is not enough to know that a specific user used the SELECT privilege on a particular table. Fine-grained auditing provides a deeper audit, such as when the user queried the table or the computer IP address of the user who performed the action Auditing Specific Columns and Rows When you define the fine-grained audit policy, you can target one or more specific columns, called a relevant column, to be audited if a condition is met. This feature enables you to focus on particularly important, sensitive, or privacy-related data to audit, such as the data in columns that hold credit card numbers, patient diagnoses, U.S. Social Security numbers, and so on. A relevant-column audit helps reduce the instances of false or unnecessary audit records, because the audit is triggered only when a particular column is referenced in the query. You further can fine-tune the audit to specific columns and rows by adding a condition to the audit policy. For example, suppose you enter the following fields in the Create Fine Grained Audit page: Condition: department_id = 50 Columns: salary, commission_pct This setting audits anyone who tries to select data from the salary and commission_pct columns of employees in Department 50. If you do not specify a relevant column, then Oracle Database applies the audit to all the columns in the table; that is, auditing occurs whenever any specified statement type affects any column, whether or not any rows are returned Using Event Handlers in Fine-Grained Auditing In a fine-grained audit policy, you can specify an event handler to process an audit event. The event handler provides flexibility in determining how to handle a triggering audit event. For example, it could write the audit event to a special audit table for further analysis, or it could send a pager or an alert to a security administrator. This feature enables you to fine-tune audit responses to appropriate levels of escalation. For additional flexibility in implementation, you can employ a user-defined function to determine the policy condition, and identify a relevant column for auditing (audit column). For example, the function could allow unaudited access to any salary as long as the user is accessing data within the company, but specify audited access to executive-level salaries when they are accessed from outside the company. Creating Oracle Audit Vault Policies and Alerts 2-13

48 Creating Oracle Audit Vault Policies for Fine-Grained Auditing Defining a Fine-Grained Auditing Policy To define a fine-grained auditing policy: 1. If necessary, retrieve and activate the current fine-grained auditing policies. See Section 2.3 for more information. 2. In the Audit Settings page, select the FGA tab to display the FGA (fine-grained auditing) page. The FGA page appears similar to the following: Table 2 8 on page 2-15 describes the fields used in the FGA page. 3. Click the Create button and in the Create Fine Grained Audit page, define the audit policy. Table 2 9 on page 2-15 describes the Create Fine Grained Audit fields. 4. Click OK. The fine-grained audit policy is created. To ensure that the fine-grained audit policy is semantically correct, see Section In the Dashboard page, select Save All Audit Settings. To display the Dashboard page, click the Audit Settings link, and then in the Audit Settings page, select the name of the source database Oracle Audit Vault Auditor's Guide

49 Creating Oracle Audit Vault Policies for Fine-Grained Auditing Table 2 8 lists the fields used in the Fine-Grained Audit page. Table 2 8 Field (Leftmost column) Fields in the Fine-Grained Audit Page Description An exclamation mark icon indicates one of the following conditions: The statement is needed but is not in use. The statement is in use but is not needed. Policy Name Schema Object Statement Columns In Use Needed (Rightmost column) The name of this fine-grained audit policy The schema to which this policy applies The object to which this policy applies The SQL statement to which this policy applies. Values are: S: SELECT I: INSERT U: UPDATE D: DELETE M: MERGE The database columns being audited, also referred to as the relevant columns. If this field is empty, all columns are audited. The arrow points upward if the setting is active in the source database and downward if it has not been provisioned or is not active. A check mark indicates that the policy is needed. An X indicates that the policy is not needed. If a policy that is not in use is set to needed, the In Use arrow points up after provisioning. If a policy that is in use is set to not needed, the audit policy is no longer displayed after provisioning. To select all policies as needed, click the Mark All as Needed button. To reverse this action, click Mark All as Not Needed. Click the trash can icon to remove the policy. You only can use the trash can icon to remove the policy if you had just created it and decided it was not required in the source database, or if it is not active in the source database. Table 2 9 lists the fields in the Create Fine Grained Audit page. Table 2 9 Fields in the Create Fine Grained Audit Page Field Description Policy Name Enter a name for this fine-grained audit policy. Creating Oracle Audit Vault Policies and Alerts 2-15

50 Creating Oracle Audit Vault Policies for Fine-Grained Auditing Table 2 9 Field Audit Trail Object Statements (Cont.) Fields in the Create Fine Grained Audit Page Description Select from one of the following audit trail types: Database: Writes the policy records to the database audit trail SYS.FGA_LOG$ system table. Database with SQL Text: Performs the same function as the Database option, but also populates the SQL bind and SQL text CLOB-type columns of the SYS.FGA_LOG$ table. XML: Writes the policy records to an operating system XML file. To find the location of this file, a database administrator can run the following command in SQL*Plus: SQL> show parameter audit_file_dest XML with SQL Text: Performs the same function as the XML option, but also includes all columns of the audit trail, including SQLTEXT and SQLBIND values. Be aware that sensitive data, such as credit card numbers, appear in the audit trail if you collect SQL text. Select an object to audit (for example OE.CUSTOMERS). To display a list for selection and to filter objects by audit source, object owner, and object, click the flashlight icon. Select one or more SQL statements to audit. To display a list of statements for selection, click the flashlight icon. Select from the following SQL statements: SELECT INSERT UPDATE DELETE MERGE Columns Condition Handler Schema Optional. Enter the names of the database columns (relevant columns) to audit. Separate each column name with a comma. If you enter more than one column, select All or Any as the condition that triggers this policy. For example, if you selected the OE.CUSTOMERS table, you could select these columns: CUSTOMER_ID, CREDIT_LIMIT, DATE_OF_BIRTH See Section for more information about relevant columns. Optional. Enter a Boolean condition to filter row data. For example: department_id = 50 If this field is blank or null, auditing occurs regardless of condition. Mandatory if you specify an event handler. Enter the name of the schema account in which the event handler was created. For example: SEC_MGR See Section for more information about event handlers Oracle Audit Vault Auditor's Guide

51 Creating Capture Rules for Redo Log File Auditing Table 2 9 Field Handler Package Handler (Cont.) Fields in the Create Fine Grained Audit Page Description Mandatory if you specify an event handler. Enter the name of the package in which the event handler was created. For example: OE_FGA_POLICIES Optional. Enter the name of the event handler. For example: CHECK_OE_VIOLATIONS If you specify an event handler, then you must specify its schema and package as well. 2.8 Creating Capture Rules for Redo Log File Auditing This section contains: About Capture Rules Used for Redo Log File Auditing Defining a Capture Rule for Redo Log File Auditing About Capture Rules Used for Redo Log File Auditing You can create a capture rule to track before and after value changes in the database redo log files. The capture rule specifies DML and DDL changes that should be checked when Oracle Database scans the database redo log. You can apply the capture rule to an individual table, a schema, or globally to the entire database. Unlike statement, object, privilege, and fine-grained audit policies, you do not retrieve and activate capture rule settings from a source database, because you cannot create them there. You only can create the capture rule in the Audit Vault Console. In the source database, ensure that the table that you plan to use for the redo log file audit is not listed in the DBA_STREAMS_UNSUPPORTED data dictionary view. This is because the REDO collector uses Oracle Streams and Oracle LogMiner to read the redo logs. If there is a column type that is unsupported, then Oracle Audit Vault cannot extract the before and after values from the table Defining a Capture Rule for Redo Log File Auditing To define a capture rule: 1. In the Audit Settings page, select the Capture Rule tab to display the Capture Rule page. Table 2 10 on page 2-18 describes the fields used in the Capture Rule page. 2. Click the Create button and in the Create Capture rule page, define the capture rule. Creating Oracle Audit Vault Policies and Alerts 2-17

52 Creating Capture Rules for Redo Log File Auditing Table 2 11 on page 2-19 describes the Create Capture Rule page fields. 3. Click OK. The capture rule is created. To ensure that the capture rule is semantically correct, see Section In the Dashboard page, select Save All Audit Settings. To display the Dashboard page, click the Audit Settings link, and then in the Audit Settings page, select the name of the source database. Table 2 10 lists the fields used in the Capture Rule page. Table 2 10 Field (Leftmost column) Fields in the Capture Rule Page Description An exclamation mark icon indicates one of the following conditions: The statement is needed but is not in use. The statement is in use but is not needed. Rule Type Schema Table DDL DML In Use Needed (Rightmost column) The types of capture rules are as follows: Table: Captures or discards either row changes resulting from DML changes or DDL changes to a particular table. Schema: Captures or discards either row changes resulting from DML changes or DDL changes to the database objects in a particular schema. Global: Captures or discards either all row changes resulting from DML changes or all DDL changes in the database. Indicates the schema to which this rule applies For table capture rules, this fields indicates the table to which this rule applies. YES or NO indicates whether data definition language (DDL) statements are audited. YES or NO indicates whether data manipulation language (DML) statements are audited. The arrow points upward if the setting is active in the source database and downward if it has not been provisioned or is not active. A check mark indicates that the policy is needed. An X indicates that the policy is not needed. If a policy that is not in use is set to needed, the In Use arrow points up after provisioning. If a policy that is in use is set to not needed, the audit policy is no longer displayed after provisioning. To select all policies as needed, click the Mark All as Needed button. To reverse this action, click Mark All as Not Needed. Click the trash can icon to remove the policy. You can use the trash can icon to remove the policy only if you had just created it and decided it was not required in the source database, or if it is not active in the source database Oracle Audit Vault Auditor's Guide

53 Provisioning Audit Vault Policies to the Source Oracle Database Table 2 11 lists the fields used in the Create Capture Rule page. Table 2 11 Field Capture Rule Capture Fields in the Create Capture Rule Page Description Select from the following capture rule types: Table: Captures either row changes resulting from DML changes or DDL changes to a particular table. The Table field appears; enter the name of the table to which the capture rule applies. To display a list of tables and their audit sources, and to filter by object owner and object, click the flashlight icon. Schema: Captures either row changes resulting from DML changes or DDL changes to the database objects in a particular schema. The Schema field appears; enter the name of the schema, or click the flashlight icon to select from a list. Global: Captures either all row changes resulting from DML changes or all DDL changes in the database. Select from the following: DDL (data definition language) DML (data manipulation language) Both 2.9 Verifying Oracle Audit Vault Policy Settings After you have created an audit policy or capture rule, you can verify its semantic correctness. 1. From within the Audit Vault Console, select the Audit Policy tab. 2. Under Audit Source, select the name of the source database. The Apply Audit Settings section appears. 3. Select the audit settings types that you want to verify: Statement, Object, Privilege, FGA, or Capture Rule. By default, all audit types are selected. 4. Under Apply Audit Settings, click the Verify button. The Audit Vault Console displays a message letting you know that the settings have been verified Provisioning Audit Vault Policies to the Source Oracle Database After you have created, verified, and saved the audit policies, you can provision the audit policy changes to the source database. To verify that the audit policy changes have taken affect, you can retrieve a snapshot from the source database, as described in Section You can provision the audit policy settings in the following ways: Saving the Audit Policy Settings to a SQL Script for a Database Administrator Manually Provisioning the Audit Policy Settings to the Source Database Creating Oracle Audit Vault Policies and Alerts 2-19

54 Provisioning Audit Vault Policies to the Source Oracle Database Caution: Any audit policy that is not indicated as Needed in Audit Vault will be turned off on the source database. Section describes how to retrieve audit policies from a source Oracle database Saving the Audit Policy Settings to a SQL Script for a Database Administrator To save the audit settings to a SQL script: 1. From within the Audit Vault Console, click the Database Instance link to display the Dashboard page. 2. Select the name of the source database. The Apply Audit Settings section appears. 3. Select from the audit settings types the audit settings that you want to export: Statement, Object, Privilege, FGA, or Capture Rule. By default, all the audit settings types are selected. 4. Click Export as SQL to save the settings to a SQL script. In the Browse dialog field, select a location for the SQL file. 5. Give this script to your database administrator, who can apply the policies to the source database Manually Provisioning the Audit Policy Settings to the Source Database To manually provision the audit settings to the source database. 1. From within the Audit Vault Console, click the Database Instance link to display the Dashboard page. 2. Select the name of the source database. The Apply Audit Settings section appears. 3. Select from the audit settings types the audit settings that you want to export: Statement, Object, Privilege, FGA, or Capture Rule. By default, all the audit settings types are selected. 4. In the Audit Source User Name field, enter the user name of a user who has been granted the EXECUTE privilege for the AUDIT SQL statement, the NOAUDIT SQL statement, and the DBMS_FGA PL/SQL package. If the source database is protected with Oracle Database Vault, ensure that the user has been granted the AUDIT SYSTEM and AUDIT ANY privileges. If there is an audit command rule in place, ensure the command is enabled and the user whose name you enter is able to execute the command. 5. In the Audit Source Password field, enter the password of this user. 6. Click the Provision button. After you provision the audit settings to the source database, a database administrator can modify or delete audit policies. For this reason, you should periodically retrieve the settings to ensure that you have the latest audit settings. Section 2.3 describes how to fetch audit settings Oracle Audit Vault Auditor's Guide

55 Creating and Configuring Alerts 2.11 Copying Oracle Audit Vault Policies to Other Oracle Databases You can copy audit policies from one Oracle database to another Oracle database that has been added to Oracle Audit Vault. You can copy policies that are already in use in the database or copy policies that you have created in Oracle Audit Vault but not yet applied to that database. 1. From within the Audit Vault Console, click the Database Instance link to display the Dashboard page. 2. Select the name of the source database. The Apply Audit Settings section appears. 3. Select audit settings for types that you want to copy: Statement, Object, Privilege, FGA, and Capture Rule. By default, all the audit settings types are selected. 4. In the From field under Copy Audit Settings from Another Source, enter the name of a source database that is different from the current source database, or use the flashlight icon to select it from a list. 5. After Copy, select either of the following options: Actual (In Use): Copies the settings listed in the In Use field under Apply Audit Settings. Needed (Not Yet In Use): Copies the settings listed in the Needed field under Apply Audit Settings. 6. In the From field, enter the full name of the source database from which you want to copy, or use the flashlight icon to select its name from a list. You can filter the source databases by source name, host name, and host IP address. 7. Click the Load button. 8. Click the Save All Audit Settings button. 9. Export the settings to a SQL file or provision the settings to the source database, using the procedure described in Section Creating and Configuring Alerts About Alerts This section contains: About Alerts Creating Templates to be Used for Alerts Creating Alert Status Values Creating a Basic Alert Creating an Advanced Alert Monitoring Alerts You can create and configure alerts for Oracle Database, Microsoft SQL Server, Sybase ASE, and IBM DB2 source databases. The alert is raised when the incoming audit data Creating Oracle Audit Vault Policies and Alerts 2-21

56 Creating and Configuring Alerts violates specific audit policies. You can specify an alert level and associate the alert with the events described in Appendix A through Appendix D. When an incoming audit record meets the specified condition, an alert is raised and placed in the alert store, where you can review and respond to it as necessary. For example, you may want to send an to a security officer or file a trouble ticket within the appropriate tracking system. You can configure templates to be used for this type of alert notification. Section 2.13 describes how to respond to an alert. Remember that alerts are raised when the audit data reaches the Oracle Audit Vault database, not when the actual action occurs. The time lag between when the action occurs and when the alert is raised depends on several factors, including how frequently the audit data collectors collect the audit records. An Oracle Audit Vault administrator can configure this frequency. Alerts are independent of audit policies. That is, you do not need to perform the tasks described under Section 2.3 before you create an alert. Note: An Oracle Audit Vault administrator can disable alerts. If the alerts are not firing, then check with your administrator Creating Templates to be Used for Alerts You can configure Oracle Audit Vault alerts to trigger an in response to an Audit Vault alert being raised or a report being generated. For example, suppose you create an alert that is triggered every time a connection is made by a application shared schema account outside of the application (for example, APPS or SYSADM). When the user tries to log in, Oracle Audit Vault sends an to an administrator warning him or her of misuse of the application account. To accomplish this, you must create an notification profile that defines who will receive the , and then create an template that contains a message. You also can create a trouble ticket that can be used log trouble tickets in response to an alert. Before you can do so, you must create a trouble ticket template. This section contains: Creating an Notification Profile Creating an Notification Template Creating a Trouble Ticket Template Creating an Notification Profile The notification profile is a way of creating an group for a specific notification purpose, that is, a distribution list. For example, if you need to send to all auditors in your group, you can create an notification profile. When you create an alert, you can use this profile to specify an list of recipients. To create a notification profile: 1. Log in to the Audit Vault Console as a user who has been granted the AV_ AUDITOR role. Section 1.4 explains how to start the Audit Vault Console. 2. From the Dashboard page, select the Settings tab. 3. Select the Notification Profiles tab Oracle Audit Vault Auditor's Guide

57 Creating and Configuring Alerts The Notification Profiles page is displayed by default. It displays a list of existing notification profiles, which you can modify or delete. 4. Click the Create button, and in the Add Notification Profile page, define the notification profile. Table 2 12 describes the Add Notification Profile fields. 5. Click the Save button. After you create the profile, it is listed in the Profile List section of the Notification Profile. From there, you can modify or delete profiles as necessary. Table 2 12 lists the fields used in the Add/Edit Notification Profile Page. Table 2 12 Field Profile Name Description To CC Fields in the Add Notification Profile Page Description Enter a name of the notification profile. For example: All Auditors Optionally, enter a description of the notification profile. For example: Profile used for notifications that are sent to all auditors Enter a list of user or group addresses, each separated by a comma. For example: auditors_ca@example.com, sec_admin@example.com Optionally, include additional addresses if you want. For example: ida.neau@example.com, kari.uksa@example.com, nessa.sarie@example.com, ima.kuksa@example.com Creating an Notification Template An notification template enables you to specify the content of the when you send it to other users, including the recipients specified in an notification template, when an Oracle Audit Vault alert is raised or an Audit Vault report is generated. To create a notification template: 1. Log in to the Audit Vault Console as a user who has been granted the AV_ AUDITOR role. Creating Oracle Audit Vault Policies and Alerts 2-23

58 Creating and Configuring Alerts Section 1.4 explains how to start the Audit Vault Console. 2. From the Dashboard page, select the Settings tab. 3. Select the Notification Templates tab. The Notification Templates page displays a list of existing notification templates, which you can modify or delete. Some of these templates are predefined. 4. Click the Create button and in the Add Notification Template page, define a notification template. Table 2 13 describes the Add Notification Template page. 5. Click Save. After you create the template, it is listed in the Notification Templates page. From there, you can modify or delete templates as necessary. Table 2 13 lists the fields used in the Add Notification Template page. Table 2 13 Field Type Name Description Fields in the Add Notification Template Page Description Specify the type of notification. Select from the following options: Alert: Creates a notification template used by the alerts. Report Attachment: Attaches a PDF of the audit report to the notification. Report Notification: Creates a notification template used by reports, but does not attach the PDF file of the report. Enter a name for the template. For example: Critical Alert for non-os User Access Attempts Enter a brief description of what the template will be used for. For example: Alerts admins if non-os users try to log into the database 2-24 Oracle Audit Vault Auditor's Guide

59 Creating and Configuring Alerts Table 2 13 Field Subject Format Body (Cont.) Fields in the Add Notification Template Page Description Enter a subject header for the alert. You can use the supplied tags to provide dynamic text based on the content of the alert or report. For example: #AlertSeverity# Alert: Non-OS User Trying to Access the employee_db Database #Date_ created# Select either Plain Text or HTML. Enter the body text for the notification. You can use the tags listed under Available Tags to associate existing alerts with the notification. Table 2 14 and Table 2 15 describe these tags in detail. For example, suppose you create the following body text for an alert notification: The "#Report_name#", generated on #Date_created#, is ready for your review. You can review the report at the following location: #URL# Please do not reply to this . This is an automatically generated message. The generated message could, depending on the circumstances and alert generated, say something similar to the following: The System Privileges Report, generated on Sept 26, 2009, 3:15:06 PM, is ready for your review. You can review the report at the following location: ID:36 Please do not reply to this . This is an automatically generated message. Table 2 14 lists the available tags for alert notifications. Table 2 14 Alert Tag Name #AlertName# #AlertTime# #AlertStatus# #Object# #AlertSeverity# #ClientHost# #ClientHostIP# #Event# Notification Template Alert Tags Description Name of the alert Time the event causing the alert was created Status of the Alert (for example, New, Open, or Closed) Schema name and object name from the event that caused the alert Severity of the alert (Critical or Warning) Host name of the client IP address of the client Audit event (for example, DELETE for a data access event). See the following appendixes for more information about audit events: Appendix A, "Oracle Database Audit Events" Appendix B, "Microsoft SQL Server Audit Events" Appendix C, "Sybase Adaptive Server Enterprise Audit Events" Appendix D, "IBM DB2 Audit Events" #OSUserName# The operating system user name associated with the event Creating Oracle Audit Vault Policies and Alerts 2-25

60 Creating and Configuring Alerts Table 2 14 Alert Tag Name #UserName# #SourceName# #Description# #TroubleTicketID# #TroubleTicketTime# #URL# #AlertBody# (Cont.) Notification Template Alert Tags Description The user name associated with the event (a database event because Oracle Audit Vault currently collects only database events) Source database in which the alert was raised. Description of the alert The trouble ticket ID that has been created for this alert The time the trouble ticker has been created URL of the alert A special tag that is a shortcut to include the following fields in the Alert Name, Alert Time, Alert Status, Object, Alert Severity, Client Host, Client Host IP, Event, OS User Name, User Name, Source Name, Description, Trouble Ticket ID, Trouble Ticket Time, and URL Table 2 15 lists the available tags for report notifications. Table 2 15 Report Tag Name #ReportName# #DateCreated# #ReportCategory# Notification Template Report Tags Description Name of the report Date and time the alert was generated Event category for the report (for example, data access event). See the following appendixes for more information about audit event categories: Appendix A, "Oracle Database Audit Events" Appendix B, "Microsoft SQL Server Audit Events" Appendix C, "Sybase Adaptive Server Enterprise Audit Events" Appendix D, "IBM DB2 Audit Events" #URL# URL to the report that was generated Creating a Trouble Ticket Template A trouble ticket template is a form that defines a trouble ticket action that must be logged in response to an alert. To create a trouble ticket template: 1. Log in to the Audit Vault Console as a user who has been granted the AV_ AUDITOR role. Section 1.4 explains how to start the Audit Vault Console. 2. From the Dashboard page, select the Settings tab. 3. Select the Trouble Ticket Templates tab. The Trouble Ticket Templates page displays a list of existing trouble ticket templates, which you can modify or delete. 4. Click the Create button and in the Add Trouble Ticket Template page, define the template Oracle Audit Vault Auditor's Guide

61 Creating and Configuring Alerts Table 2 16 lists the fields used in the Trouble Ticket Template page. 5. Click Save. After you create the template, it is listed in the Trouble Ticket Templates page. From there, you can modify or delete templates as necessary. Table 2 16 lists the fields used in the Trouble Ticket Template page. Table 2 16 Field Template Name Description Assigned Support Group Fields Used in the Add Trouble Ticket Template Page Assigned Support Company Assigned Support Org Description Enter a name for the trouble ticket template. For example: hr_data_tmpl Optionally, enter a description for the trouble ticket template. For example: Template to be used for any HR data violations Enter the name of the support group that is assigned the trouble ticket. Check with your Remedy administrator for the value to be used. For example: sec_support Enter the name of the company that is assigned the trouble ticket. Check with your Remedy administrator for the value to be used. For example: Example, Inc. Enter the name of the support organization that is assigned to the trouble ticket. Check with your Remedy administrator for the value to be used. For example: sec_support_org Creating Oracle Audit Vault Policies and Alerts 2-27

62 Creating and Configuring Alerts Table 2 16 Field First Name Last Name Summary (Cont.) Fields Used in the Add Trouble Ticket Template Page Description Enter the first name of the customer for whom you are creating the trouble ticket. Check with your Remedy administrator for the value to be used. For example: Ima Enter the last name of the customer. Check with your Remedy administrator for the value to be used. For example: Noyd Enter a detailed summary of the trouble ticket incident. You can use the tags listed under Available Tags to associate existing alerts with the trouble ticket template. Table 2 15 on page 2-26 describes these tags in detail. For example, suppose you enter the following text: #ReportName# was generated on #DateCreated#. Please see the following URL: #URL# In the trouble ticket, depending on the circumstances, it could appear as follows: The Data Access Report was generated on Sept 30, 2009, 3:15:06 PM. Please see the following URL: ::NO::P4_REPORT_ID:58 Notes Critical level Alert Warning level Alert Enter notes for this ticket. For example: I think someone has been tampering with HR files again. Select from the following levels: 1-Critical 2-High (default) 3-Medium 4-Low These levels categorize the alert only. Select from the following levels: 1-Critical 2-High 3-Medium (default) 4-Low These levels categorize the alert only Creating Alert Status Values You can create alert status values to assign to an alert during the lifetime of the alert. Oracle Audit Vault provides two status values: NEW and CLOSED. You can create additional ones to suit your needs, such as PENDING. To create an alert status value: 1. Log in to the Audit Vault Console as a user who has been granted the AV_ AUDITOR role Oracle Audit Vault Auditor's Guide

63 Creating and Configuring Alerts Section 1.4 explains how to start the Audit Vault Console. 2. In the Audit Vault Console, select the Settings tab, and then select the Alert Status Values secondary tab. The Alert Status Values page appears. 3. To create a new alert status, click the Create button. The Add Alert Status Value page appears. 4. Enter the following settings: Status Value: Enter a name for the status value (for example, PENDING). Description: Optionally, enter a description for the status value. For example: Use this value to assign to alerts that are in process of being resolved and have not yet been closed. 5. Click the Save button. The new alert status appears in the Alert Status Values page. From there, you can edit the alert status. To delete it, click the trash icon Creating a Basic Alert A basic alert specifies a user, table, audit event, success criteria, and notification settings. For example, you could create a basic alert to be raised each time User X tries to modify Table Y. To create a basic alert: 1. Log in to the Audit Vault Console as a user who has been granted the AV_ AUDITOR role. Section 1.4 explains how to start the Audit Vault Console. 2. In the Audit Vault Console, select the Audit Policy tab, and then select the Alerts secondary tab. The Audit Alerts page appears, which lists the existing alerts. You can use the Audit Source Type, Audit Source, and Audit Event Category fields or their flashlight icons to filter the list of existing alerts. To view the definition for an existing alert, select its name in the Alert Name field. Creating Oracle Audit Vault Policies and Alerts 2-29

64 Creating and Configuring Alerts 3. Click Create. The Create Alert Rule page appears. 4. In the Alert field, enter the alert name and then in the Description field, enter a brief description of the alert. 5. Specify the following information: Alert Severity: Select Warning or Critical. Audit Source Type: Select one of the following audit source types: SYBDB (for Sybase Adaptive Server Enterprise) MSSQLDB (for Microsoft SQL Server) ORCLDB (for Oracle Database) DB2DB (for IBM DB2) Audit Source: Select from the list of source databases based on the audit source type that you selected. Audit Event Category: Select from the list of available categories based on the audit source type that you selected. For detailed information about the audit events for these categories, see the following appendixes: Appendix A, "Oracle Database Audit Events" Appendix B, "Microsoft SQL Server Audit Events" Appendix C, "Sybase Adaptive Server Enterprise Audit Events" Appendix D, "IBM DB2 Audit Events" 6. After Specify additional alert conditions in, select Basic Oracle Audit Vault Auditor's Guide

65 Creating and Configuring Alerts The following area appears on the Alerts page: 7. Specify the following information: User: Specify the name of one or more users or click the flashlight icon to search for and select user names. Oracle Audit Vault only lists the tables from the Oracle databases that have been configured for Audit Vault and since the last retrieve of the audit policy settings. To retrieve the latest audit policy settings, see Section 2.3. Table: Specify the name of one or more tables or click the flashlight icon to search for and select table names. Oracle Audit Vault only lists the tables from the Oracle databases that have been configured for Audit Vault and since the last retrieve of the audit policy settings. Audit Event: Select the name of an audit event from the list. The audit events that appear are based on the audit event category that you selected. See the following appendixes for more information about audit events: Appendix A, "Oracle Database Audit Events" Appendix B, "Microsoft SQL Server Audit Events" Appendix C, "Sybase Adaptive Server Enterprise Audit Events" Appendix D, "IBM DB2 Audit Events" Audit Event Status: Select an option to represent whether the event has a status of Success, Failure, or Both. 8. Under Notification Action, optionally specify the following information: Template: From the list, select a notification template. Profile: From the list, select a profile template. Creating Oracle Audit Vault Policies and Alerts 2-31

66 Creating and Configuring Alerts To: Enter one or more addresses, each separated by a comma. Cc: Enter one or more addresses, each separated by a comma. Add to List: Click the Add to List button to record the recipients that you entered in the To and Cc fields. 9. Under Trouble Ticket Action, from the list, optionally select a trouble ticket template. 10. Click OK. After you create the basic alert, you can modify all the fields of the alert except for the following fields: Alert Severity Audit Source Type Audit Source Audit Event Category In addition, you can monitor the alert activity from the Dashboard page. See Section for more information Creating an Advanced Alert This section contains: About Advanced Alerts Creating an Advanced Alert That Uses a Condition Creating an Advanced Alert Condition That Uses a Function About Advanced Alerts In the Advanced Alert Condition section of the Create Alert Rule page, you can construct a Boolean condition that evaluates audit event behavior. When the Boolean condition evaluates to TRUE, then Oracle Audit Vault raises the alert, and either notifies other users or creates a trouble ticket. The alert condition can be simple or complex. As a general guideline, try to keep your alert conditions simple. Overly complex conditions can slow the Audit Vault Server database performance. The syntax for the alert condition is as follows: audit_field operator expression When you insert the audit event fields for the expression, Oracle Audit Vault encloses them in # (pound) symbols. For example: #USERNAME# #HOST_IP# #EVENT_STATUS# See the event attributes tables in Appendix A through Appendix D for a full listing of the event attributes for the Oracle Database, SQL Server, Sybase ASE, and IBM DB2 source databases. You can use any legal SQL function. For example: upper() lower() 2-32 Oracle Audit Vault Auditor's Guide

67 Creating and Configuring Alerts to_char() You can use any legal SQL operator. For example: not like < > in and null When using operators, follow these guidelines: Remember that Oracle Audit Vault evaluates an alert condition for each incoming audit record. You cannot use nested queries (for example, not in SELECT...) in the condition. Wildcards are as follows: % (to match zero or more characters) _ (to match exactly one character) You can group components within the condition by using parentheses. For example: (((A > B) and (B > C)) or C > D) You can create a user-defined function that retrieves data from a table for the alert evaluation. Section Creating an Advanced Alert That Uses a Condition To create an advanced alert: 1. Follow Step 1 through Step 5 in Section After Specify additional alert conditions in, select Advanced. The following area appears on the Alerts page: 3. From the Select an event to insert in the condition list, select an event. The event appears in the Condition field with its associated source event. For example, suppose you wanted to monitor application shared schema accounts that Creating Oracle Audit Vault Policies and Alerts 2-33

68 Creating and Configuring Alerts are being used outside the database. An example of this scenario is when the database user is APPS and the client identifier is set to NULL. From the Audit Event Category list, you would select USER SESSION. Then from the Select an event to insert it in the condition list, you select LOGON. Oracle Audit Vault then adds the following event code for logons to the Condition field: #SOURCE_EVENTID# = '100' (Appendix A through Appendix D describe the event codes in detail.) 4. From the Select an attribute to insert in the condition list, select an attribute. For this example, you select USERNAME, which Oracle Audit Vault adds to the Condition field. At this stage, the Condition field appears as follows: #SOURCE_EVENTID# = '100' #USERNAME# Do not remove the # symbols that enclose the event code or the attribute. 5. Modify the condition to build the expression. For example: #SOURCE_EVENTID# ='100'and lower (#USERNAME#) = 'apps' and #CLIENT_ID" = null This alert says, "Raise an error if any ex-employee tries to log in to the database." 6. Under Notification Action, optionally specify the following information: Template: From the list, select a notification template. Profile: From the list, select a profile template. To: Enter one or more addresses, each separated by a comma. Cc: Enter one or more addresses, each separated by a comma. Add to List: Click Add to List to create a listing of existing notification recipients, which will be listed 7. Under Trouble Ticket Action, from the list, optionally select a trouble ticket template. 8. Click OK Creating an Advanced Alert Condition That Uses a Function You can create a function (or a package containing a set of functions) to use with the alert condition. For example, if the alert condition must test for a specific host name, then you can create a function that checks the host names listed in a table. This function can be used for any of the supported source database types. Follow these guidelines when you create a table and function to use with an alert condition: Create the function and table on the Audit Vault Server database. The function and table should reside in the schema of the user who creates them. The user who creates the function and table must have the following privileges: CREATE TABLE CREATE PROCEDURE In addition, ensure that this user has enough space to create the table and procedure in his or her tablespace, which by default is USERS. For example: 2-34 Oracle Audit Vault Auditor's Guide

69 Creating and Configuring Alerts SQL> ALTER USER HOSTCHECKER QUOTA 10M ON USERS; The return type for the function can be any legal type, such as CHAR, VARCHAR2, or. However, you cannot have a Boolean return type. You must grant the EXECUTE privilege for the function to the AVREPORTUSER account. This is a default user account that is designed to manage the Audit Vault reports. If the function is modified in the future or the function privileges changed, then the alert becomes invalid and does not work. Furthermore, the other alerts that were created for the alert category and source database (for example, all alerts created for the Account Management category for Oracle source databases) may not work as well. If this problem occurs, then check and correct the alert functions and privileges. Then drop and recreate the alert to use the corrected function. Afterward, all alerts created for the affected alert category and source database should work. Work with your Oracle Audit Vault administrator to troubleshoot alert issues. To accomplish this, follow these general steps: 1. Log in to SQL*Plus in the Audit Vault Server database as the user responsible for creating the alert table and function. For example: $ sqlplus hostchecker Enter password: password Connected. 2. Create a table that contains the data that the function will retrieve. For example: SQL> CREATE TABLE hostlist (hostname VARCHAR2(100)); 3. Create the function. For example, to create a function that retrieves the host names populated in the hostlist table: CREATE OR REPLACE FUNCTION checkhost (host IN VARCHAR2) RETURN CHAR AS hostcount ; BEGIN SELECT COUNT(*) INTO hostcount FROM hostchecker.hostlist WHERE LOWER(host) = hostname; IF (hostcount > 0) THEN RETURN 'Y'; ELSE RETURN 'N'; END IF; END checkhost; / 4. Grant the EXECUTE privilege to the AVREPORTUSER user account. For example: SQL> GRANT EXECUTE ON CHECKHOST TO AVREPORTUSER; Grant succeeded. Creating Oracle Audit Vault Policies and Alerts 2-35

70 Creating and Configuring Alerts 5. Create the advanced alert as described in Section For example, the alert condition can be as follows: hostchecker.checkhost(#host_name#) = 'N' If you have not created the function properly, then Oracle Audit Vault prevents you from creating an alert to use the function. If this happens, check the structure of the alert and ensure that you have granted the AVREPORTUSER account the EXECUTE privilege for the function Monitoring Alerts The Overview page is where auditors can view alert summaries, drill down to reports, and view agent and collector status. To display the Dashboard page, select the Home tab. When an audit record is generated, Oracle Audit Vault classifies it in the event category that you specified when you created the alert. Audit event activity is monitored by the event category to which the audit record belongs. For example, a Logon event belongs to the User Session event category. Oracle Audit Vault raises an alert when data in a single audit record matches an alert rule condition. Alerts are grouped by the sources with which they are associated, by the event category to which the event belongs, and by the severity level of the alert (warning or critical). Figure 2 1 shows the a partial view of the Dashboard page. Figure 2 1 Dashboard Page 2-36 Oracle Audit Vault Auditor's Guide

71 Responding to an Alert From the Dashboard page, you can: Select an event start time and end time for viewing Audit Vault event data. You can specify a time period by month, week, or day time span or the period between a specified begin and end date. View five types of graphical summaries (pie charts and bar graphs) of alert activity and event activity over the specified time period. These graphical summaries include: Alert Severity Summary (pie chart) Click a section in this pie chart to drill down to a more detailed critical or warning alert report to see what sources are showing a particular severity level. See Section 3.5 for more information about critical and warning alert reports. Summary of Alert Activity (pie chart) Click a section in this pie chart to find critical and warning alerts to see the affected sources for all alert activity. Top Five Audit Sources by Number of Alerts (bar graph) Click a bar in this bar graph to find more detailed critical and warning alert information that shows a severity level for a particular source. Alerts by Audit Event Category frequency (number of alerts) (bar graph) Click an event category link in this bar graph to drill down to see more detailed critical and warning alert information that shows all alerts for that event category. Activity by Audit Event Category frequency (number of events) (bar graph) Click an event category link in this bar graph to find events for that event category. You can generate default reports for these event categories. See Chapter 3, "Using Oracle Audit Vault Reports" for more information. Click a pie section or bar chart y-axis event category label to drill down to a more detailed report level Responding to an Alert After you have created alerts and when they are generated, you or other auditors can respond to them. You can change the alert status (for example, closing it), notify other users of the alert, or log a trouble ticket for the alert. To respond to an alert: 1. Log in to the Audit Vault Console as a user who has been granted the AV_ AUDITOR role. Section 1.4 explains how to start the Audit Vault Console. The Dashboard page appears. 2. Access the alert by using one of the following methods: From the Dashboard page, select the alert from the Recent Alerts list. From the Dashboard page, select the See All Warning Alerts link to access warning alerts. From the Dashboard page, select the See All Critical Alerts link to access critical alerts. Creating Oracle Audit Vault Policies and Alerts 2-37

72 Setting a Retention Period for Audit Data Select the Audit Report tab, then the Default Reports secondary tab. Under Alert Reports, select either All Alerts, Critical Alerts, or Warning Alerts. Click Go to filter the report display. The All Alerts page appears similar to the following: 3. In the All Alerts page, select the check boxes for the reports to which you want to respond. 4. Perform any of the following actions: Notify another auditor of the alert. Click the Notify button. In the Manual Alert Notification page, select the notification template and profile that you want to use, and optionally enter addresses in the To and Cc fields. Separate multiple addresses with a comma. Click the Add to List button to compile the listing, and then click the Notify button to send the notification. Log a trouble ticket. Click the Log Trouble Tickets button. In the Manual Trouble Ticketing page, select the trouble ticket template that you want from the Template list. Then click OK. The Alerts page appears, with a message describing the status (for example, Successfully queued the trouble ticket logging request). Details. Select the page icon under the Details column for the report, and under the Notes area, select either Current Note or Previous Notes to update the status of the alert, or log or update a Remedy ticket. This method also enables you to file notification and trouble ticket information. Set the alert status. From the Set Status to list, select either NEW or CLOSED, and then click the Apply button. When an alert is first generated, it is set to OPEN. The Alerts page displays a message describing the status (for example, Successfully updated the alert statuses) Setting a Retention Period for Audit Data You can set a period of 1 to 99 years for Oracle Audit Vault to retain audit data. By default, Oracle Audit Vault retains collected audit data for 10 years. When you set this retention period, it applies to audit records from all source databases, not just the currently selected source database. Oracle Audit Vault deletes the data based on the time that it was collected by Oracle Audit Vault, not when the audit event actually 2-38 Oracle Audit Vault Auditor's Guide

73 Setting a Retention Period for Audit Data occurred. For example, suppose you load audit data that is more than 10 years old and then you set the retention period to 7 years. Oracle Audit Vault will delete this audit data 7 years from now. To set the audit data retention period: 1. Log in to the Audit Vault Console as a user who has been granted the AV_ AUDITOR role. Section 1.4 explains how to start the Audit Vault Console. The Dashboard page appears. 2. In the Audit Vault Console, select the Audit Policy tab. By default, the Audit Settings page appears. 3. Under Audit Data Retention, enter a value (1 99) in the Retain audit data field. 4. Click Go. Creating Oracle Audit Vault Policies and Alerts 2-39

74 Setting a Retention Period for Audit Data 2-40 Oracle Audit Vault Auditor's Guide

75 3 3Using Oracle Audit Vault Reports This chapter contains: What Are Oracle Audit Vault Reports? Accessing the Oracle Audit Vault Audit Reports Using the Default Reports Using the Compliance Reports Using the Critical and Warning Alert Reports Scheduling and Creating PDF Reports Annotating and Attesting Reports Generating and Comparing Snapshots of Entitlement Audit Data Controlling the Display of Data in a Report Finding Information About Report Data Working with User-Defined Reports Downloading a Report to a CSV File 3.1 What Are Oracle Audit Vault Reports? The Oracle Audit Vault reports are automatically generated reports that describe the state of audited activities. They reflect audited data collected from the Oracle Database, Microsoft SQL Server, Sybase ASE, and IBM DB2 source databases that connect to the Audit Vault Server. For all of these products, they track the audit events described in Appendix A through Appendix D. The default reports are organized into various categories, such as access reports and management reports. You can create user-defined reports that focus on specific areas or audited events. Any user who has been granted the AV_AUDITOR role can view and modify the reports. 3.2 Accessing the Oracle Audit Vault Audit Reports To access the Oracle Audit Vault audit reports: 1. Log in to the Oracle Audit Vault Console as a user who has been granted the AV_ AUDITOR role, as explained in Section 1.4. Using Oracle Audit Vault Reports 3-1

76 Using the Default Reports The Dashboard page appears. 2. Click the Audit Reports tab in the upper-right corner of the window. 3. Do one of the following: 3.3 Using the Default Reports To view and work with reports: Click the appropriate secondary tab to find the report you want to view (Default Reports, Compliance Reports, Custom Reports, or Generated Reports). To view the report (for example, Data Access under the Access Reports category), click its link. To schedule and send to another user a PDF report: Click the Report Schedules secondary tab. See Section 3.6. To annotate and attest a report: Click the Generated Reports secondary tab, select the report, and then click the Details button. See Section 3.7. To view snapshots of audit data in the entitlement reports: Click Entitlement Snapshots secondary tab. See Section 3.8. This section contains: About the Default Reports Using the Default Access Reports Using the Default Management Activity Reports Using the Default System Exception Reports Using the Default Entitlement Reports 3-2 Oracle Audit Vault Auditor's Guide

77 Using the Default Reports About the Default Reports The default reports are predefined reports that cover commonly required audit data. Figure 3 1 shows the Default Reports page. Figure 3 1 Default Reports Page Using the Default Access Reports This section contains: About the Default Access Reports Activity Overview Report Data Access Report Database Vault Report Distributed Database Report Procedure Executions Report User Sessions Report About the Default Access Reports The default access reports track general database access activities such as audited SQL statements, Oracle Database Vault activities, application access activities, and user login activities. These reports display the following kinds of information: source database name, source database type, host name for the source database, version of the source database, IP address of the source database, audit time, Audit Vault category, the event itself (such as LOGIN statements), current and previous values of the event, user and host client information, the event status (such as failure), and the time the event took place. Using Oracle Audit Vault Reports 3-3

78 Using the Default Reports You can create user-defined custom reports from the reports. See Section 3.9 and Section Activity Overview Report The Activity Overview page displays all audit trail records. Audit records appear based on their audit event time in descending order (newest record first). This report can be very large, but you can create a user-defined version that filters specific audit data. By default, 15 audit records are displayed on each page. Figure 3 2 shows the Activity Dashboard page. Figure 3 2 Activity Overview Report Page Data Access Report The Data Access Report displays audited SQL statements, such as Oracle Database data manipulation language (DML) activities (for example, all SELECT, INSERT, UPDATE, or DROP SQL statements). See Also: Section A.5 for Oracle Database audit events Section B.5 for SQL Server audit events Section C.5 for Sybase Adaptive Server Enterprise audit events Section D.5 for IBM DB2 audit events Section if you want to use the Program Change Report to track changes to row data from INSERT or UPDATE statements 3-4 Oracle Audit Vault Auditor's Guide

79 Using the Default Reports Database Vault Report The Database Vault Report displays audited Oracle Database Vault activity. These audit records are collected from the Oracle Database Vault audit trail. If the Database Vault Report does not show data, then Oracle Database Vault may not be enabled. To check that Oracle Database Vault is enabled, log in to SQL*Plus and then query the V$OPTION table. Any user can query this table. If Oracle Database Vault is enabled, the query returns TRUE; otherwise, it returns FALSE. Remember that you must enter the parameter value, Oracle Database Vault, using case-sensitive letters, as in the following example: SQL> SELECT * FROM V$OPTION WHERE PARAMETER = 'Oracle Database Vault'; PARAMETER VALUE Oracle Database Vault TRUE See also Section A.6 for a listing of the Oracle Database Vault audit events Distributed Database Report The Distributed Database Report displays audited distributed database activity, such as Oracle Database CREATE DATABASE LINK or DROP DATABASE LINK statements. (Note that the associated audit events are called peer association events.) See Also: Section A.10 for Oracle Database audit events Section B.9 for SQL Server audit events Section C.9 for Sybase Adaptive Server Enterprise audit events Section D.9 for IBM DB2 audit events Procedure Executions Report The Procedure Executions Report displays audited application access activity, such as the execution of SQL procedures or functions. (Note that the associated audit events are called service and application utilization events.) See Also: Section A.12 for Oracle Database audit events Section B.11 for SQL Server audit events Section C.11 for Sybase Adaptive Server Enterprise audit events Section D.11 for IBM DB2 audit events Section for information about the Procedure Management Report User Sessions Report The User Sessions Report displays audited authentication events for users who log in to the database. This includes the time the user logged in, the login event, and how the user was authenticated. Using Oracle Audit Vault Reports 3-5

80 Using the Default Reports See Also: Section A.15 for Oracle Database audit events Section B.14 for SQL Server audit events Section C.14 for Sybase Adaptive Server Enterprise audit events Section D.14 for IBM DB2 audit events Using the Default Management Activity Reports This section contains: About the Default Management Activity Reports Account Management Report Audit Commands Report Object Management Report Procedure Management Report Role and Privilege Management Report System Management Report About the Default Management Activity Reports The default management activity reports track the use of AUDIT SQL statements, changes to user accounts, actions performed on the underlying packages for applications, actions performed on database objects, roles and privileges, and system management activities such as database shutdowns and startups. These reports display the following kinds of information: source database name, source database type, host name for the source database, version of the source database, IP address of the source database, audit time, Audit Vault category, the event itself (such as GRANT statements), current and previous values of the event, user and host client information, the event status (such as failure), and the time the event took place. You can create user-defined reports from the reports. See Section 3.9 and Section Account Management Report The Account Management Report displays account management activity of the user's audited SQL statements. This includes audited changes to user accounts and profiles (setting limits on database resources), for example, when user accounts are created, altered, or deleted, and when database schemas are created. See Also: Section A.2 for Oracle Database audit events Section B.2 for SQL Server audit events Section C.2 for Sybase Adaptive Server Enterprise audit events Section D.2 for IBM DB2 audit events Audit Commands Report The Audit Commands Report displays the use of audit commands, such as Oracle Database AUDIT SQL statements for other SQL statements and database objects. For example, for Oracle Database, this page tracks AUDIT ALL, AUDIT SELECT ON table_name statements, NOAUDIT statements, and so on. 3-6 Oracle Audit Vault Auditor's Guide

81 Using the Default Reports See Also: Section A.4 for Oracle Database audit events Section B.4 for SQL Server audit events Section C.4 for Sybase Adaptive Server Enterprise audit events Section D.4 for IBM DB2 audit events Object Management Report The Object Management Report displays audited actions performed on database objects. For example, these audit records are created for create, alter, or drop operations on database objects that are performed on a database table. See Also: Section A.9 for Oracle Database audit events Section B.8 for SQL Server audit events Section C.8 for Sybase Adaptive Server Enterprise audit events Section D.8 for IBM DB2 audit events Procedure Management Report The Procedure Management Report displays audited actions that were performed on the underlying procedures or functions of system services and applications. For example, it lists the audit records that were created for Oracle Database ALTER FUNCTION, ALTER JAVA, or ALTER PACKAGE statements. (Note that the associated audit events are called application management events.) See Also: Section A.3 for Oracle Database audit events Section B.3 for SQL Server audit events Section C.3 for Sybase Adaptive Server Enterprise audit events Section D.3 for IBM DB2 audit events Section for information about the Procedure Executions Report Role and Privilege Management Report The Role and Privilege Management Report lists audited role and privilege management activity, such as the creating, granting, revoking, and dropping of roles and privileges. It lists the name of the user performing the action, and the user to whom the action applies. See Also: Section A.11 for Oracle Database audit events Section B.10 for SQL Server audit events Section C.10 for Sybase Adaptive Server Enterprise audit events Section D.10 for IBM DB2 audit events Using Oracle Audit Vault Reports 3-7

82 Using the Default Reports System Management Report The System Management Report displays audited system management activity. For example, it lists activities such as startup and shutdown operations on a database, enable and disable operations on all triggers, and rollback operations. It also lists user-related operations, such as unlocking a user account. See Also: Section A.13 for Oracle Database audit events Section B.12 for SQL Server audit events Section C.12 for Sybase Adaptive Server Enterprise audit events Section D.12 for IBM DB2 audit events Using the Default System Exception Reports This section contains: About the Default System Exception Reports Exception Activity Report Invalid Audit Record Report Uncategorized Activity Report About the Default System Exception Reports The default system exception reports track audit events, such as exceptions that occur and audit activities that Oracle Audit Vault cannot recognize or place into a category. These reports display the following kinds of information: source database name, source database type, host name for the source database, version of the source database, IP address of the source database, audit time, Audit Vault category, the event itself (such as network errors), current and previous values of the event, user and host client information, the event status (such as failure), and the time the event took place. You can create user-defined reports from the reports. See Section 3.9 and Section Exception Activity Report The Exception Activity Report displays audited error and exception activity, such as network errors. See Also: Section A.7 for Oracle Database audit events Section B.6 for SQL Server audit events Section C.6 for Sybase Adaptive Server Enterprise audit events Section D.6 for IBM DB2 audit events Invalid Audit Record Report The Invalid Audit Record Report displays audited activity that Oracle Audit Vault cannot recognize, possibly due to a corrupted audit record. 3-8 Oracle Audit Vault Auditor's Guide

83 Using the Default Reports See Also: Section A.8 for Oracle Database audit events Section B.7 for SQL Server audit events Section C.7 for Sybase Adaptive Server Enterprise audit events Section D.7 for IBM DB2 audit events Uncategorized Activity Report The Uncategorized Activity Report displays audited activity that cannot be categorized. For example, it lists events such as Oracle Database COMMENT, CREATE SUMMARY, or NO-OP events. See Also: Section A.14 for Oracle Database audit events Section B.13 for SQL Server audit events Section C.13 for Sybase Adaptive Server Enterprise audit events Section D.13 for IBM DB2 audit events Using the Default Entitlement Reports This section contains: About the Default Entitlement Reports User Accounts Report and User Accounts by Source Report User Privileges Report and User Privileges by Source Report User Profiles Report and User Profiles by Source Report Database Roles Report and Database Roles by Source Report System Privileges Report and System Privileges by Source Report Object Privileges Report and Object Privileges by Source Report Privileged Users Report and Privileged Users by Source Report About the Default Entitlement Reports An entitlement report describes the types of access that users have to an Oracle source database. It provides information about the user, role, profile, and privileges used in the source database. For example, the entitlement reports capture information such as access privileges to key data or privileges assigned to a particular user. These reports are useful for tracking unnecessary access to data, finding duplicate privileges, and simplifying privilege grants. After you generate a default entitlement report, you can view a snapshot of the metadata that describes user, role, profile, and privilege information. This enables you to perform tasks such as comparing different snapshot labels to find how the entitlement information has changed over time. See Section 3.8. You can create user-defined reports from the reports. See Section 3.9 and Section User Accounts Report and User Accounts by Source Report The User Accounts Report and User Accounts by Source Report show the following information about user accounts: source database in which the user account was Using Oracle Audit Vault Reports 3-9

84 Using the Default Reports created, user account name, account status (LOCKED or UNLOCKED), expiration date for the password, initial lock state (date the account will be locked), default tablespace, temporary tablespace, initial resource consumer group, when the user account was created, associated profile, and external name (the Oracle Enterprise User DN name, if one is used). The difference between these reports is that the "by Source" report enables you to view snapshot data from a specific Oracle source database. The regular report includes snapshot label data from all Oracle source databases assigned to given labels User Privileges Report and User Privileges by Source Report The User Privileges Report and User Privileges by Source Report show the following information about user privileges: source database in which the privilege was created, user name, privilege, schema owner, table name, column name, type of access (direct access or if through a role, the role name), whether the user privilege was created with the ADMIN option, whether the user can grant the privilege to other users, and who granted the privilege. The difference between these reports is that the "by Source" report enables you to view snapshot data from a specific Oracle source database. The regular report includes snapshot label data from all Oracle source databases assigned to given labels User Profiles Report and User Profiles by Source Report The User Profiles Report and User Profiles by Source Report show the following information about user profiles: source database in which the user profile was created, profile name, resource name, resource type (KERNEL, PASSWORD, or INVALID), and profile limit. The difference between these reports is that the "by Source" report enables you to view snapshot data from a specific Oracle source database. The regular report includes snapshot label data from all Oracle source databases assigned to given labels Database Roles Report and Database Roles by Source Report The Database Roles Report and Database Roles by Source Report lists names of database roles and application roles. If the role is a secure application role, then the Schema and Package columns of the report indicate the underlying PL/SQL package used to enable the role. The difference between these reports is that the "by Source" report enables you to view snapshot data from a specific Oracle source database. The regular report includes snapshot label data from all Oracle source databases assigned to given labels System Privileges Report and System Privileges by Source Report The System Privileges Report and System Privileges by Source Report show the following information about system privileges: source database in which the system privilege was created, user granted the system privilege, privilege name, type of access (direct access or if through a role, the role name), and whether it was granted with the ADMIN option. The difference between these reports is that the "by Source" report enables you to view snapshot data from a specific Oracle source database. The regular report includes snapshot label data from all Oracle source databases assigned to given labels Oracle Audit Vault Auditor's Guide

85 Using the Compliance Reports Object Privileges Report and Object Privileges by Source Report The Object Privileges Report and Object Privileges by Source Report show the following information about object privileges: the source database in which the object was created, users granted the object privilege, schema owner, target name (which lists tables, packages, procedures, functions, sequences, and other objects), column name (that is, column-level privileges), privilege (object or system privilege, such as SELECT), type of access allowed the object (direct access or if through a role, the role name), whether the object privilege can be granted, and who the grantor was. The difference between these reports is that the "by Source" report enables you to view snapshot data from a specific Oracle source database. The regular report includes snapshot label data from all Oracle source databases assigned to given labels Privileged Users Report and Privileged Users by Source Report The Privileged Users Report and Privileged Users by Source Report show the following information about privileged users: source database in which the privileged user account was created, user name, privileges granted to the user, type of access (direct access or if through a role, the role name), and whether the privileged user was granted the ADMIN option. The difference between these reports is that the "by Source" report enables you to view snapshot data from a specific Oracle source database. The regular report includes snapshot label data from all Oracle source databases assigned to given labels. 3.4 Using the Compliance Reports This section contains: About the Compliance Reports Credit Card Compliance Report: Related Data Access Compliance Report Financial Compliance Reports Health Care Compliance Report: EPHI Related Data Access Report Common Credit Card, Financial, and Health Care Compliance Reports About the Compliance Reports The compliance reports provide out-of-the-box reports to help you meet regulations associated with credit card, financial, and health care related data. They track activities that are typically required to meet standard compliance regulations, such as changes to the database structure or its objects, failed logins, administrator activities, system events, and user logins or logoffs. Internal and external auditors request many of these reports to monitor security and compliance for your business. The compliance reports have three categories: credit card, financial, and health care. For example, all three of the categories listed have a Database Logon Report, but each category determines the type of data shown in the report. To customize the display name, description, data output, and source database for a report, under Tasks, select the Customize Categories link. To access the compliance reports, select the Audit Reports tab, then select Compliance Reports. You can create user-defined reports from the reports. See Section 3.9 and Section Using Oracle Audit Vault Reports 3-11

86 Using the Compliance Reports Figure 3 3 shows the Compliance Reports page. Figure 3 3 Compliance Reports Page Credit Card Compliance Report: Related Data Access Compliance Report The Credit Card Related Data Access Report displays audited SQL statements, such as Oracle Database data manipulation language (DML) activities (for example, all SELECT, INSERT, UPDATE, or DELETE SQL statements). For additional compliance reports that can be used for credit card audit data, see Section Financial Compliance Reports The financial compliance reports are as follows: Financial Related Data Access Report Financial Related Data Modifications Report Financial Related Data Access Report The Financial Related Data Access Report displays audited SQL statements that were used to access financial data, such as SELECT SQL statements. For additional compliance reports that can be used for financial audit data, see Section Financial Related Data Modifications Report The Financial Related Data Modifications Report displays audited SQL statements that were used to modify financial data, such as Oracle Database data manipulation language (DML) activities (for example, all INSERT, UPDATE, or DELETE SQL statements). For additional compliance reports that can be used for financial audit data, see Section Oracle Audit Vault Auditor's Guide

87 Using the Compliance Reports Health Care Compliance Report: EPHI Related Data Access Report The EPHI (Electronic Protected Health Information) Related Data Access Report displays audited SQL statements that were used to access or modify health care data, such as Oracle Database data manipulation language (DML) activities (for example, all INSERT, UPDATE, or DELETE SQL statements). For additional compliance reports that can be used for health care audit data, see Section Common Credit Card, Financial, and Health Care Compliance Reports The credit card, financial, and health care reports all have the following common reports: Audit Setting Changes Report Before/After Values Report Database Failed Logins Report Database Login/Logoff Report Database Logoff Report Database Logon Report Database Startup/Shutdown Report Deleted Objects Report Program Changes Report Schema Changes Report System Events Report User Privilege Change Activity Report Audit Setting Changes Report The Audit Settings Changes Report displays audited activity of audit setting changes (for example, changes to the AUDIT ALL SQL statement). It captures data such as Oracle Database Vault rules, rule sets, and factors; original content; fine grained audit policies if any were used; and proxy session IDs Before/After Values Report The Before/After Values Report displays a wide range of before and after values for events such as schema owners, events, event values, timing of the event changes, and which source databases they affect. It tracks information such as the IP address and client user connections. This report is designed for users who must capture specific before and after values of Oracle database tables using the REDO collector. Contact your Oracle Audit Vault administrator for more information about the REDO collector Database Failed Logins Report The Database Failed Logins Report displays audited failed login attempts. These audit records are generated for failed login, proxy authentication only, and super user login attempts. Using Oracle Audit Vault Reports 3-13

88 Using the Compliance Reports Database Login/Logoff Report The Database Login/Logoff Report displays audited login and logoff operations of users. For example, these audit records are generated when you audit events, such as login, logoff, privileged user login, logoff by cleanup, and proxy authentication only Database Logoff Report The Database Logoff Report displays information about user logoff operations, such as the user name, proxy session ID, client user information, and when the logoff operation took place Database Logon Report Similar to the Database Logoff Report, the Database Logon Report shows information about user logon operations. It captures the same type of information the Database Logoff Report captures Database Startup/Shutdown Report The Database Startup/Shutdown Report tracks when the source database was started and shut down, and includes information such as the user who performed the startup or shutdown operation Deleted Objects Report The Deleted Objects Report displays audited SQL statements that were used to delete database objects, such as delete operations on a specific table. It tracks the user who deleted the object and the command the user used to delete the object Program Changes Report The Program Changes Report displays changes to row data when an insert or update operation occurs in Oracle Database. It tracks data such as the user who performed the action the action itself, and when the action took place. This report is especially useful if you are using the redo collector to extract the before and after values of data updates Schema Changes Report The Schema Changes Report displays audited data definition language (DDL) activities (for example, changes to the database schema that result from SQL ALTER, CREATE, or DROP statements). It tracks data such as the user who changed the schema, when the change took place, and the status of the change attempt System Events Report The System Events Report displays audited system event activities. These audit records are generated when you audit local system processes. It tracks events such as the SQL text that caused the system event, the user responsible for it, the privilege required for the event, and when the event took place. Examples of a local system process are starting and shutting down a database or changing database parameters User Privilege Change Activity Report The User Privilege Change Activity Report displays information about the privileges that were required when users change data in the source database. It tracks data such as the SQL statements the user run, event time, and the target of the change Oracle Audit Vault Auditor's Guide

89 Scheduling and Creating PDF Reports 3.5 Using the Critical and Warning Alert Reports The alert reports are as follows: About the Critical and Warning Alert Reports All Alerts Report Critical Alerts Report Warning Alerts Report About the Critical and Warning Alert Reports All Alerts Report See Also: Critical Alerts Report The critical and warning alert reports track critical and warning alerts. An alert is raised when data in a single audit record matches a predefined alert rule condition. Alerts are grouped by associated source, by event category, and by the severity level of the alert (either warning or critical). You can create user-defined reports from these alerts; see Section 3.9. This report tracks all alerts, both critical and warning alerts. This report tracks critical alerts Warning Alerts Report Section 2.12 for information about creating and configuring alerts Section 2.13 for information about responding to an alert This report tracks warning alerts. 3.6 Scheduling and Creating PDF Reports This section contains: About Scheduling and Creating PDF Reports Scheduling and Creating a PDF Report About Scheduling and Creating PDF Reports You can schedule reports to be sent to other users in PDF format. You can run the report immediately, or you can create or select a schedule to run the report at a later time. In addition to setting a time to run the report, you can create the following components for the report: A retention time for the data to be used in the report. For example, if you schedule a report to run once a month but you only want that month s audit data in the report, then you can set a retention time to store the data for each month the report runs, and then discard the data after each month. This way, the report recipients always receives the most recent month of audit data. Using Oracle Audit Vault Reports 3-15

90 Scheduling and Creating PDF Reports A list of users who should be notified when the report runs. You can notify other users of the report and either send them a notification or the report in an attachment. A list of auditors who must attest to the report. You can select one or more auditors, including yourself, to attest to the report. Formatting for the report. You can design the title to include certain components, such as the category and report names. You also can control the header and footer text for the report, as well as the orientation of the report Scheduling and Creating a PDF Report To schedule and create a PDF report: 1. Log in to the Oracle Audit Vault Console as a user who has been granted the AV_ AUDITOR role, as explained in Section 1.4. The Dashboard page appears. 2. Select the Audit Reports tab. 3. Access the Create or Schedule PDF Report page using one of the following methods: Select the report from the Default Reports, Compliance Reports, Custom Reports, or Generated Reports secondary tab, and then click the Create PDF button. Select the Audit Reports tab, and then select the Report Schedules secondary tab. Then click the Create button. The Create or Schedule PDF Report page appears. 4. In the Create or Schedule PDF Report page, if you had selected the Report Schedules secondary tab, then under Create or Schedule PDF Report, first select the category and then select the name of the report from the Category Name and Report Name lists. 5. Under Schedule, select a time to run the report: Immediately if you want to run the report right away. Specify Schedule if you want to create a schedule to run the report. From here, select how often the report should be run, the report run time and date, and the time zone offset to reflect the time zone in which the report should appear. Select Schedule if you want to select an existing schedule for the report. From here, select the schema in the Audit Vault Server database in which the schedule is stored, and the schedule name Oracle Audit Vault Auditor's Guide

91 Scheduling and Creating PDF Reports A database administrator can create this schedule by using the DBMS_ SCHEDULER PL/SQL package, assuming this user has the EXECUTE privilege for this package. The Schema list displays schemas that contain DBMS_ SCHEDULER schedules. The Schedule list displays all the DBMS_SCHEDULER schedules in that schema. By default, Schema contains the SYS schema, which owns the DBMS_SCHEDULER package. 6. Under Retention, enter the retention period years and months to specify how long to keep the data in the report. The retention period determines how long to keep the audit data in storage, based on times the report is run. For example, suppose you set the retention period to 6 months. Oracle Audit Vault will delete this audit data 6 months from the last time the report is run. If you specify the retention to be 0 years and 0 months, each night the reports clean up job deletes the PDF report. You can use this special 0 years, 0 months setting to create a PDF report for immediate viewing or printing. 7. Under Notification, select the following options, and then click Add to List to create a notification list: For Send, select either Notification or Attachment. The Notification option sends the user an with a URL link to the report. The Attachment option attaches the PDF report to the user s . From the Template list, select a report notification template. From the Profile list, select a profile, which contains a list of default recipients who should receive the report. If you want to send the report to additional recipients, enter their addresses in the To and Cc fields. Enter the full address. Separate multiple addresses with a comma. 8. Under Attestation, select one or more auditors who should attest to the report. Optionally, you can set the order in which the auditors are listed in the Attestation area. 9. Under Report Formatting, specify the following: For Title, select one or more of the following options: Category Name, Report Name, Generated Time, Filters, Timezone, and Custom. If you select Custom, then enter customized text for the report title. For Header and Footer, select from these options: Report Name, Generated Time, Page #, and Custom Text. If you select Custom Text, then enter this text in the appropriate field. You can designate these elements to appear on the left, center, or right side of the page. For Orientation, select either Portrait or Landscape. 10. Click the Create PDF button. The PDF is stored in the database. To find and review the PDF, click the Generated Reports tab. Using Oracle Audit Vault Reports 3-17

92 Annotating and Attesting Reports 3.7 Annotating and Attesting Reports This section contains: About Annotating and Attesting Reports Annotating and Attesting a Report About Annotating and Attesting Reports After a report has been generated, auditors can annotate and attest to the report. This enables you to create a record of all notes and attestations for the report in one place, with the most recent note and attestation listed first. If you delete the report, its associated annotation and attestations are removed as well Annotating and Attesting a Report To annotate and attest a report: 1. Log in to the Oracle Audit Vault Console as a user who has been granted the AV_ AUDITOR role, as explained in Section 1.4. The Dashboard page appears. 2. Access the list of reports to attest by using one of the following methods: From the Dashboard page, select the number of the report from the Attestation Actions list. Select the Audit Reports tab, and then select the Generated Reports secondary tab. Find the report that you want to annotate or attest and then click the report name. When you display the report, it appears in PDF format. Click the Details button to display the Details for Generated Report page. You can quickly filter the reports if you want. See Section for more information. 3. In the New Note field, enter a note for the report. 4. Perform one of the following actions: To save the note only, click the Save button. The note appears in the Previous Notes area. To save the note and attest to the report, click the Save & Attest button. The note appears in the Previous Notes area and the Attestation area is updated with your user name and the time that you attested to the report. To return to the report, click the View Report button. 5. Click Done when you are finished. The Generated Reports page appears. 3.8 Generating and Comparing Snapshots of Entitlement Audit Data This section contains: About Entitlement Report Snapshots and Labels General Steps for Using Entitlement Reports Retrieving Entitlement Audit Data to Create the Snapshot Creating an Entitlement Snapshot Label 3-18 Oracle Audit Vault Auditor's Guide

93 Generating and Comparing Snapshots of Entitlement Audit Data Assigning Snapshots to a Label Viewing Entitlement Snapshot and Label Audit Data About Entitlement Report Snapshots and Labels An entitlement snapshot captures the state of user entitlement information. The snapshot contains the metadata of users and roles that a user has to a database: system and other SQL privileges, object privileges, role privileges, and user profiles. Snapshots are created automatically whenever you retrieve the entitlement data, and only apply to Oracle Database source databases. Each snapshot is unique, and it is time-stamped in the following format: MM/DD/YYYY HH:MM:SS AM/PM The name for the snapshot is the time stamp assigned to it when the entitlement data was retrieved (for example, 9/22/ :56:17 AM). Each source database can only have one snapshot of a particular time stamp. In other words, you cannot have multiple snapshots entitled 9/22/ :56:17 AM in one source database. If you retrieve entitlement audit data for all your source databases at the same time, then each source database gets its own 9/22/ :56:17 AM snapshot. Optionally, you can group snapshots from multiple source databases by assigning these snapshots to a label. For example, suppose the source databases payroll, sales, and hr each have a 9/22/ :56:17 AM snapshot. You can create a label and then assign these three snapshots to that label. This enables you to compare the snapshot data from the three source databases at once, all in the same report. You can filter a report to show the data from an earlier snapshot or label, or you can compare the audit data from two snapshots or two labels. This way, you can find changes that have occurred over time, from different entitlement audit data retrievals. For example, you can find how user privileges have been modified between two snapshots or labels. The type of entitlement report determines whether you can view its audit data by snapshot or by label. The reports appended with "by Source" (for example, User Accounts by Source) provide snapshot data for specific source databases. The regular entitlement reports (such as User Accounts) enable you to view audit data across all the source databases or snapshots, based on a label General Steps for Using Entitlement Reports The general steps that you must take to use entitlement reports are as follows: 1. Retrieve the entitlement audit data to create a snapshot. See Section Optionally, organize the snapshots into a group and then assign them a label. See Section Optionally, assign one or more snapshots to a label. See Section View the entitlement snapshot and label data. See Section For a listing of entitlement reports, see Section Using Oracle Audit Vault Reports 3-19

94 Generating and Comparing Snapshots of Entitlement Audit Data Retrieving Entitlement Audit Data to Create the Snapshot Each time you retrieve entitlement audit data, you create a snapshot. To retrieve the entitlement audit data: 1. Log in to the Audit Vault Console as a user who has been granted the AV_ AUDITOR role. Section 1.4 explains how to start the Audit Vault Console. The Dashboard page appears. 2. In the Audit Vault Console, select the Audit Policy tab. By default, the Audit Settings page appears. 3. From the Audit Source listing, select the check boxes for the source databases that you want. To filter the list of audit sources, enter text in the Audit Source text field or click the flashlight icon to display the Search And Select: Audit Source page. If you make selections on the Search And Select: Audit Source page, when you return, the Audit Source column will be populated with your selections. 4. Select the User Entitlement option. 5. Click the Retrieve button. Oracle Audit Vault displays a message letting you know that the user entitlement data is being retrieved. To check the status of the retrieval, click the Show Status button Creating an Entitlement Snapshot Label If you want to organize the snapshots into a group, assign them to a label. The name LATEST is automatically assigned to the latest snapshot for each Oracle source database. Therefore, each source database has its own LATEST label for its most recent retrieval. To create an entitlement snapshot label: 1. From the Home page, select the Audit Reports tab, and then select the Entitlement Snapshots tab. 2. Under Tasks, select Manage Snapshot Labels. The Snapshot Labels page appears. 3. Click Create. The Add Snapshot Label page appears. 4. Enter the following information: Label Name: Enter a name for the label. Do not name the label LATEST, which is a reserved word. Typically, label names are based on time, such as financial quarters. For example: Q1_2009 Description: Optionally, enter a brief description of the label. For example: 5. Click Save. This label captures the snapshot 9/22/ :56:17 AM data for the payroll, sales, and hr source databases Oracle Audit Vault Auditor's Guide

95 Generating and Comparing Snapshots of Entitlement Audit Data The new label is listed in the Snapshot Labels page. From here, you can edit the label by selecting its name, or remove it by clicking the trash icon. Later on, if you want to edit or remove a label, select Manage Snapshot Labels from the Entitlement Snapshots page. To edit the label, select the label name and then use the Edit Snapshot Label page to modify the label name and description. To remove the label, select its trash icon Assigning Snapshots to a Label You only can assign one snapshot from each source database to a label. To assign snapshots to a label: 1. From the Home page, select the Audit Reports tab, and then select the Entitlement Snapshots tab. 2. Select one or more source database snapshots to be assigned to a label. 3. Click the Assign Label button. The Assign Label page appears. The following example shows two snapshots listed for a source database called avsource. 4. Enter the following information: Label: For a new label, enter the name in the Label field. To select an existing label, select the label name from the Label list. Description: For a new label, optionally enter a brief description of the label. Snapshots: Ensure that the snapshots listed are the correct snapshots. If they are incorrect, then click Cancel and then select the correct snapshots. 5. Click Save. The label assignment appears in the Entitlement Snapshots page. From here, you can modify or move the label assignments for the snapshots Viewing Entitlement Snapshot and Label Audit Data After snapshots have been created and if you have created and assigned labels for them, then you are ready to check the entitlement reports. This section contains: Checking Entitlement Reports for Individual Snapshot or Label Audit Data Checking Entitlement Reports for Changes to Snapshot or Label Audit Data Using Oracle Audit Vault Reports 3-21

96 Generating and Comparing Snapshots of Entitlement Audit Data Checking Entitlement Reports for Individual Snapshot or Label Audit Data To check entitlement reports for individual snapshot or label audit data: 1. Log in to the Audit Vault Console as a user who has been granted the AV_ AUDITOR role. Section 1.4 explains how to start the Audit Vault Console. The Dashboard page appears. 2. Select the Audit Reports tab, and in the Default Reports page, under Entitlement Reports, select link for the entitlement report that you want. 3. In the entitlement report, do the following: For a "by Source" report, from the Source list, select the source database for the snapshot that you want. From the Snapshot or Label list, select the snapshot or label. For example: 4. Click the Go button (to the right of the compare list). The entitlement report data appears. The generated report contains an additional column, either Snapshot or Label, indicating which snapshot or label was used for the report. From here, you can expand the Snapshot or Label column to filter its contents. Figure 3 4 shows how the User Accounts by Source Report typically appears with generated snapshot audit data. Figure 3 4 Showing Individual Snapshot or Label Audit Data Checking Entitlement Reports for Changes to Snapshot or Label Audit Data To compare the audit data for two snapshots or labels: 1. Log in to the Audit Vault Console as a user who has been granted the AV_ AUDITOR role. Section 1.4 explains how to start the Audit Vault Console. The Dashboard page appears. 2. Select the Audit Reports tab, and in the Default Reports page, under Entitlement Reports, select the link for the entitlement report that you want Oracle Audit Vault Auditor's Guide

97 Controlling the Display of Data in a Report 3. In the report, do the following: For a "by Source" report, from the Source list, select the source database for the snapshot that you want. From the Snapshot or Label list, select the first snapshot or label. Click the compare check box. Select from the second snapshot or label list. For example: 4. Click Go. The entitlement report data appears. It contains an additional column entitled Change Category, and - Changes is appended to the name of the report. The Change Category column shows how the data has changed between the two snapshots or labels. From here, you can filter the data to show only MODIFIED, NEW, DELETED, or UNCHANGED data. Figure 3 5 shows how the User Accounts - Changes Report typically appears with generated comparison data. No deletions have occurred in this label; otherwise, the Change Category column would include a DELETED category. Figure 3 5 Comparing Entitlement Report Snapshot or Label Audit Data 3.9 Controlling the Display of Data in a Report This section contains: About Controlling the Display of Report Data Hiding or Showing Columns in a Report Filtering Data in a Report Sorting Data in a Report Highlighting Rows in a Report Charting Data in a Report Adding a Control Break to a Column in a Report Using Oracle Audit Vault Reports 3-23

98 Controlling the Display of Data in a Report Resetting the Report Display Values to Their Default Settings See Also: Section 3.8.6, which describes additional ways that you can view audit data in entitlement reports About Controlling the Display of Report Data You can control the display of data in a default or user-defined report to focus on a particular set of data. Oracle Audit Vault automatically saves the report settings so that if you leave the page, the report settings are still in place when you return. Optionally, you can save the report to a user-defined report Hiding or Showing Columns in a Report When you hide or show columns in a report, you still can perform operations on hidden columns, such as filtering data based on a column that you have hidden. This section contains: Hiding the Currently Selected Column Hiding or Showing Any Column Hiding the Currently Selected Column To hide the currently selected column: 1. In the report, select the column that you want to hide. 2. In the Column Heading menu, click the Hide Column button Hiding or Showing Any Column To hide or show columns in a report: 1. Access the report that you want. Section 3.2 explains how to access a report. 2. Select the Actions menu (gear) icon on the Search bar. The Actions menu appears Oracle Audit Vault Auditor's Guide

99 Controlling the Display of Data in a Report 3. From the Actions menu, select Select Columns. The Select Columns dialog field appears under the Search bar. 4. To move column names between the Do Not Display and Display in Report boxes: Select the column names to move and then click the left or right arrow between the column name boxes. Move all columns left or right by using the >> and << buttons. Use the top button (the arrows in a circle) to reset the columns to their original locations in the two boxes. 5. To set the order of appearance in the report for displayed columns, in the Display in Report box, select the column name, then click the up arrow or down arrow on the right side of the box to reorder its position in the list. Report columns names are arranged in a report from left to right by their top-to-bottom order in the Display in Report box. 6. Click Apply Filtering Data in a Report You can filter the report to show all rows based on a particular column, or a subset of of rows, using an expression. If you must perform subquery, join, and AND SQL operations, you can create multiple filters as needed. For example, if you want to filter all SYS users who are being audited for the SUPER USER LOGON event, you would create one filter to catch all SYS users, and then a second filter to catch all SUPER USER LOGON events. If two or more of the filters for a report are enabled, then Oracle Audit Vault uses both or all of them (as in an AND operation). You can toggle specific filters on or off, depending on the results that you want. This section contains: Filtering All Rows Based on Data from the Currently Selected Column Filtering Column and Row Data Filtering Row Data Using an Expression Filtering All Rows Based on Data from the Currently Selected Column This filtering method lets you filter data in all rows based on the currently selected column (for example, all rows that only contain SYS in the User column). Using Oracle Audit Vault Reports 3-25

100 Controlling the Display of Data in a Report To filter all rows based on data from the current column: 1. Access the report that you want. Section 3.2 explains how to access a report. 2. Under the report name, select the column that you want to use as a basis for the filter. The Column Heading menu appears, showing the row data used in the selected column. For example, if you select the User column, it will list user names found in the source database for this column, such as users APPS, OE, and SH. 3. In the Column Heading menu, select the row data on which you want to base the filter, or enter the row data item in the text area field. For example, to show only rows for users SYS and SYSTEM, select SYS and SYSTEM from the Column Heading menu. Oracle Audit Vault filters the display accordingly. The filter definitions for the current user session are added above the report columns. 4. To enable or disable the display of the filtered data, select its corresponding check box. To remove a filter, click its Remove Filter icon Filtering Column and Row Data You can use the Search bar to search for row data in one or all columns in the report (for example, all rows that contain the letters SYS, such as SYS and SYSTEM, in the User column). To search for row data in one or all columns: 1. Access the report that you want. Section 3.2 explains how to access a report. 2. If you want to focus the search on a specific column, in the Search bar, use the Search icon to select from the list of available columns. By default, Oracle Audit Vault searches all columns Oracle Audit Vault Auditor's Guide

101 Controlling the Display of Data in a Report 3. In the Search bar text area, enter all or part of the text in the column row that you want. For example, enter SYS to find all user names that contain the letters SYS. The search is not case-sensitive. 4. In the Rows list, select the number of rows that you want to appear on each page. The default is 15 rows. 5. Click Go Filtering Row Data Using an Expression This method lets you select all rows that meet a WHERE condition, such as all users who are not user SYS. You can create the expression for all columns in the source database table, even those that are not shown in the current report. To filter row data using an expression: 1. Access the report that you want. Section 3.2 explains how to access a report. 2. Select the Actions menu (gear) icon on the Search bar. 3. Select Filter. The Filter dialog box appears under the Search bar. 4. Enter the following information: Column: Select the name of the column from the list. Note that you can select all columns, including hidden columns. Operator: Select a SQL operator from the list, for example, > for "greater than" or = for "equals." Expression: Select an expression from the list. The expression lists the row data (for example, names of users found in the User column). If you type the expression in the Expression field, remember that the expression is case-sensitive. In most cases, use uppercase letters. 5. Click Apply. Oracle Audit Vault filters the display of row data based on the expression you created, and then adds the filter definition before the report columns. From here, Using Oracle Audit Vault Reports 3-27

102 Controlling the Display of Data in a Report you can disable or enable the display of the filtered data, or remove the filter, if you want Sorting Data in a Report You can sort data in ascending or descending order for all columns at once, or sort data on a selected column. This section contains: Sorting Row Data for the Currently Selected Column Sorting Row Data for All Columns Sorting Row Data for the Currently Selected Column To sort row data for the current column: 1. Select the column on which you want to base the sort. 2. In the Column Heading menu, select either the Sort Ascending or Sort Descending icon Sorting Row Data for All Columns To sort row data for all columns: 1. Access the report that you want. Section 3.2 explains how to access a report. 2. Select the Actions menu (gear) icon on the Search bar. 3. In the Actions Menu, select Sort. The Sort dialog box appears under the Search bar. 4. Enter the following information: Column: For up to six columns, select the columns to sort. By default, the first sort column is Event Time, which is sorted in descending order. Direction: Select either Ascending or Descending Oracle Audit Vault Auditor's Guide

103 Controlling the Display of Data in a Report Null Sorting: Select the Null sorting rule for each column (Default, Nulls Always Last, or Nulls Always First). The default is to not sort nulls. 5. Click Apply Highlighting Rows in a Report You can highlight specific rows in a report by assigning them colors. This enables anyone viewing the report to quickly find areas that are of particular interest. To highlight rows in the report: 1. Access the report that you want. Section 3.2 explains how to access a report. 2. Select the Actions menu (gear) icon on the Search bar. 3. In the Actions menu, select Highlight. The Highlight dialog box appears under the Search bar. 4. Enter the following information: Name: Enter a name for this highlight instance. (Optional) Sequence: Enter a sequence number to determine the order in which the highlight filter rules are to be applied when two or more highlight filter rules are in effect. The default value is 10. Enabled: Select Yes to enable the highlight or select No to disable it. Highlight Type: Select Row to highlight a row or select Cell to highlight a cell. Background Color: Select a background color for the row or cell. Click a color to display color options, or click the colored icon to the right of the color selection field to display a color selection box from which to choose a different color. Alternatively, you can manually enter the HTML code for a color. Text Color: Select a text color for the row or cell using the same method you used for the background color. (Optional) Highlight Condition: Edit the highlight filter rule expression by identifying the column, the operator, and the expression for each of the three fields in the highlight condition. Column: Select any column name, including hidden columns. Operator: Select an operator from a list of standard Oracle Database operators, such as =,!=, NOT IN, and BETWEEN. Expression: Enter the comparison expression (without quotation marks) based on a known value for that column name to complete the filter expression. For example, entering the filter expression EVENT=SUPER USER LOGON filters for all values in the Event column that contain the value SUPER USER LOGON. Using Oracle Audit Vault Reports 3-29

104 Controlling the Display of Data in a Report 5. Click Apply Charting Data in a Report You can select from four chart styles to chart data in a report. After you create the chart, you can access it whenever you access the report. To chart data in a report: 1. Access the report that you want. Section 3.2 explains how to access a report. 2. Select the Actions menu (gear) icon on the Search bar, and then select Chart. The Chart dialog box appears under the Search bar. 3. Enter the following information: Chart style: Select from one of the four chart styles: Horizontal Column, Vertical Column, Pie, and Line. Label: Select from the list of columns for this report. You can include hidden columns as well as displayed columns. Value: Select from the list of columns for this report, including hidden columns. If you select Count from the Function list, then you do not need to select a value. Function: Select an aggregate function (Sum, Average, Minimum, Maximum, or Count) on which to aggregate the data values. Sort: Select ascending or descending sorting for values and labels. Axis Title for Label: Enter a name for the axis title. Axis Title for Value: Enter a name for the axis value. 4. Click Apply Oracle Audit Vault Auditor's Guide