In this article I will give you some insight into how Oracle E-Business Suite Release 11i can be configured to use Oracle Database Vault features to protect sensitive transactional data from powerful users like Apps DBAs.
What is Oracle Database Vault?
A key challenge for security administrators is protecting enterprise data from insider attacks. Oracle Database Vault is an optional database feature that can help you defend against that class of threats, as well as build internal controls to help meet regulatory requirements for privacy and segregation of duties.
Oracle Database Vault can prevent highly privileged users, including powerful application DBAs and others, from accessing sensitive applications and data in Oracle databases outside their authorized responsibilities. You can use customizable Realms and rules to ensure that users, even administrators, have access only to what they need to do their job.
Protecting Database Objects With Realms and Rules
Oracle Database Vault uses Realms to set up boundaries around set of objects in specific schemas; specific conditions must be met to access data protected by those boundaries. Realms specify a set of conditions that must be met before a given command can be executed on a set of database objects.
This provides very granular control over what can be done to certain objects, and by whom. You can define rules to restrict access based on business-specific factors such as data access connections from particular database, from a particular machine, and from specific IP addresses. You can also specify the time of day or authentication modes for data access.
Minimum Requirements
Preseeded Realms for the E-Business Suite
Oracle delivers a set of preseeded Database Vault Realms for your E-Business Suite Release 11i environment via the following patch:
Oracle E-Business Suite Release 11i Realm Creation Patch (Patch 5999012)
This patch contains the master fnddvebs.sql script. The fnddbvebs.sql script creates Realms around Oracle E-Business Suite 11i product schemas and gives authorization only to those users required to allow the Oracle E-Business Suite to function normally.
The fnddvebs.sql script creates six Realms. Each realm protects different product schemas and has its own set of user authorizations.
EBS Realm
EBS Realm - Applsys Schema
EBS Realm - Applsyspub Schema
EBS Realm - Apps Schema
EBS Realm - MSC Schema
CTXSYS Data Dictionary
Extending Oracle-Supplied Realms
Oracle strongly recommends against modifying the preseeded Oracle-supplied Realms for the E-Business Suite. If you're familiar with the E-Business Suite data model, you can create your own realms and secure additional objects as needed. Improperly defined Realms can prevent the E-Business Suite from functioning normally, so careful testing of your custom Realms is advisable.
Metalink Note 428503.1 has a detailed example of extending Oracle E-Business suite 11i realms.
Key Considerations About Realms
The preseeded Realms are not intended to provide:
Protection from user logged into the SYSTEM schema
Protection during Application mid tier patching