Oracle Audit Vault 12c includes a standard interface for BMC Remedy ticketing systems. You can configure the Oracle Audit Vault to connect to BMC Remedy Action Request (AR) System Server 7.x. This connection enables the Oracle Audit Vault to raise trouble tickets in response to Audit Vault alerts.
Oracle E-Business Suite environments may be vulnerable due to excessive privileges granted on the SYS.DUAL table to PUBLIC. This security issue has been resolved in the January 2015 Oracle Critical Patch Update (CPU) and has been assigned the CVE tracking identifier CVE-2015-0393. The problem may impact all Oracle E-Business Suite versions including 11.5, 12.0, 12.1, and 12.2. Recent press reports have labeled this vulnerability as a “major misconfiguration flaw.” The security issue is actually broader than just the INDEX privilege that is being reported in the press
The Oracle Audit Vault has seeded reports for the following compliance and legislative requirements – no additional license is required.
For each compliance statue, following table lists the included reports available –
Oracle E-Business Suite 12.0 Extended Support ends on January 31, 2015. Sustaining Support does not include security fixes in the form of Critical Patch Updates (CPU). The final 12.0 CPU will be the January 2015 CPU released on January 20th.
Oracle E-Business Suite 12.0 customers should be looking to upgrade to 12.1 or 12.2 in the near future.
Custom reports can be created in Oracle Audit Vault using Oracle BI Publisher. BI Publisher is an add-on to Microsoft Word and can be used to modify or create new reports.
For example, to modify a new report, to meet specific corporate or internal audit needs, download a standard Oracle Audit Vault report that is similar (Auditor -> Reports -> Custom Reports -> Uploaded Reports). Click on the icon to download both the template and the report definition and load both files into BI Publisher.
The Oracle Audit Vault by default installs over one-hundred (100) reports. This includes core audit reports as well as compliance reports. Reporting is a key feature of the Oracle Audit Vault and one which well-built as evidenced by the use of BI Publisher to allow for easy modification and creation of new reports.
The audit reporting bundle installed by the default has the following categories –
The Oracle Audit Vault uses Plug-Ins to define data sources. The following table summarizes several of the important facts about the Oracle Audit Vault database plug for Oracle databases –
|
Oracle Database Plug-In for the Oracle Audit Vault |
|
|---|---|
|
Plug-in Specification | |
The Oracle Audit Vault is installed on a server, and collector agents are installed on the hosts running the source databases. These collector agents communicate with the audit vault server.
If the collection agents are not active, no audit data is lost, as long as the source database continues to collect the audit data. When the collection agent is restarted, it will capture the audit data that the source database had collected during the time the collection agent was inactive.
When upgrading the Oracle E-Business Suite database to Oracle Database 12c (12.1), there are a number of security considerations and steps that should be included in the upgrade procedure. Oracle Support Note ID 1524398.1 Interoperability Notes EBS 12.0 or 12.1 with RDBMS 12cR1 details the upgrade steps. Here, we will document steps that should be included or modified to improve database security. All refer
For Oracle database customers the Oracle Audit Vault can protect the following:
Oracle Audit Vault is aptly named; the Oracle Audit Vault is a vault in which data about audit logs is placed, and it is based on two key concepts. First, Oracle Audit Vault is designed to secure data at its source. Second, Oracle Audit Vault is designed to be a data warehouse for audit data.
Certainly from an auditing and logging perspective, one of the best new features delivered by Oracle 12c is mandatory auditing of the administrative users such as SYSDBA. This can be described as ‘always on auditing’. By default, the following audit related activities are now mandatorily audited -
What is Oracle 12c Unified Auditing? The short answer is the view UNIFED_AUDIT_TRAIL. This view consolidates all logging and auditing information into a single source. Regardless of using either Mixed Mode or Pure Unified Auditing, the SYS.UNIFIED_AUDIT_TRAIL can be used.
The key column in SYS.UNIFIED_AUDIT_TRAIL is AUDIT_TYPE. This column shows from which Oracle component the log data originated -
Next in our blog series on Oracle 12 Unified Auditing is a discussion of Mixed Mode. Mixed Mode is the default auditing mode for Oracle 12c. Oracle describes Mixed Mode auditing as a means of becoming familiar with Unified Auditing prior to migrating to Pure Unified Auditing. Mixed Mode allows for all traditional, pre-12c log and audit functionality to co-exist with Unified Auditing. More importantly, Mixed Mode will support any current Syslog-based logging solution.
Mixed mode auditing provides the following key capabilities –
Continuing our blog series on Oracle 12 Unified Auditing is a discussion of Pure Mode. Mixed mode is intended by Oracle to introduce Unified Auditing and provide a transition from the traditional Oracle database auditing. Migrating to PURE Unified Auditing requires the database be stopped, the Oracle binary linked to uniaud_on, and then restarted. This operation can be reversed if auditing needs to be changed back to Mixed Mode.
Add us to your favorite news reader.
Get the latest updates.