The Oracle Database Vault security controls protect application data from unauthorized access, and comply with privacy and regulatory requirements.

You can deploy controls to block privileged account access to application data and control sensitive operations inside the database using trusted path authorization. Through the analysis of privileges and roles, you can increase the security of existing applications by using least privilege best practices. Oracle Database Vault secures existing database environments transparently, eliminating costly and time consuming application changes.

To provide increased security for consolidation, you can use Oracle Database Vault with Oracle Multitenant.

Oracle Database Vault can prevent privileged user access inside a pluggable database (PDB) and between the PDB and the common privileged user at the container database. Each PDB has its own Database Vault metadata, such as realms, rule sets, command rules, default policies (such as default realms), and so on. In addition, the objects within the DVSYS and DVF schemas are automatically available to any child PDBs. Both schemas are common user schemas.

You can configure common realms in the application root only, but you can create common rule sets and command rules in either the application root or the CDB root. A common command rule in the application root applies to its associated PDBs, and common command rules in the CDB root apply to all PDBs in the CDB environment. The ability to create common realms and command rules enables you to create policies that use a shared set of realms, rule sets, or command rules throughout the CDB environments, rather than having to create these same components for every PDB in the multitenant environment. The common protection applies for all PDBs associated with the application root that have Oracle Database Vault enabled.

You can create individual local policies for each PDB. When you use Database Vault to protect an object, Database Vault subjects common privileges for common objects to the same enforcement rules as local system privileges.

When you configure a PDB that has Database Vault enabled, the DVSYS schema is a common user schema that is stored in the root. This means that all the objects within the DVSYS schema (tables, data dictionary views, user accounts, PL/SQL packages, default policies, and so on) are subject to the common privileges available for this schema. In other words, you can create realms, factors, and so on in the root to protect the schema in the root. Ensure that you configure Database Vault in the root first, before you configure it in the associated PDBs.

When you enable Oracle Database Vault in the CDB root, you can choose either regular mode or strict mode. The settings propagate throughout the CDB based on the setting you choose. For example, suppose a CDB contains both Database Vault-enabled PDBs and PDBs in which Database Vault is not enabled. If you enable Database Vault using regular mode, then both types of PDBs continue to function normally. If you enable Database Vault using strict mode, then the Database Vault-disabled PDBs operate in restricted mode.

Figure 24-1 illustrates how the database in regular mode allows different access for common and local database administrators depending if Database Vault is enabled. In this scenario, neither the common user nor the local users have access to the realms in PDB1 and PDB2. Both the common user and the PDB3 local user have access to the Custom App application in PDB3, where Database Vault is not enabled.

Figure 24-1 Oracle Database Vault in a Multitenant Environment with Regular Mode

Description of "Figure 24-1 Oracle Database Vault in a Multitenant Environment with Regular Mode"

The DBA_DV_STATUS, CDB_DV_STATUS, DBA_OLS_STATUS, and CDB_OLS_STATUS data dictionary views verify if Oracle Database is configured and enabled.

You can register Oracle Database Vault in a multitenant environment based on several scenarios.

• Registering Database Vault in the CDB Root
  In a multitenant environment, you register Oracle Database Vault with common users who will use the Database Vault-enforced roles in the CDB root.
• Registering Database Vault Common Users to Manage Specific PDBs
  In a multitenant environment, you must register Oracle Database Vault in the root first, then in the PDBs afterward.
• Registering Database Vault Local Users to Manage Specific PDBs
  In a multitenant environment, you must register Oracle Database Vault in the root first, and then in the PDBs afterward.
• Plugging in a Database Vault-Enabled PDB
  From SQL*Plus, in a multitenant environment, you can plug in a database that already has Database Vault enabled.
• Manually Installing Oracle Database Vault in a Multitenant Environment
  Under certain conditions, for a multitenant environment, you must manually install Oracle Database Vault. For example, a release 11g Oracle database without Database Vault is upgraded to release 12c, then converted to a PDB to be plugged into a 12c Database Vault-enabled database.

In a multitenant environment, you can create common and local command rules in either the CDB root or the application root.

Common command rules can be associated only with common realms, rule sets, and rules. Local command rules can be associated only with local realm, rule sets, and rules.

To apply these command rules to the entire multitenant environment, you must execute the command rule procedures from the CDB root or application root as a common user who has been granted the DVADM or DVOWNER role. A common command rule that is created in the CDB root will be applied to all PDBs in that CDB environment. A common command rule that is created in the application root will only be applied to the PDBs that are associated with this application root. To propagate the command rule to the PDBs that are associated with the CDB root or application root, you must synchronize the PDB. For example, to synchronize an application root called saas_sales_app to its application PDBs:

ALTER PLUGGABLE DATABASE APPLICATION saas_sales_app SYNC;

To synchronize a common command rule in the CDB root to a PDB:

ALTER PLUGGABLE DATABASE APPLICATION APP$CDB$SYSTEM SYNC;

You can check a user’s roles by querying the USER_ROLE_PRIVS data dictionary view. To find information about command rules, query the DBA_DV_COMMAND_RULE data dictionary view.

You can convert a standalone Oracle Database Release 12c or later database to a PDB, and then plug this PDB into a CDB.

1. Connect to the root as a user who has been granted the DV_OWNER role.

   For example:

   sqlplus c##sec_admin
   Enter password: password
   

2. Grant the DV_PATCH_ADMIN role to user SYS with CONTAINER = CURRENT.

   GRANT DV_PATCH_ADMIN TO SYS CONTAINER = CURRENT;
   

3. In the root, connect as user SYS with the SYSOPER system privilege.

   For example:

   CONNECT SYS AS SYSOPER -- Or, CONNECT SYS@hrpdb AS SYSOPER
   Enter password: password
   

4. Restart the database in read-only mode.

   For example:

   SHUTDOWN IMMEDIATE
   STARTUP MOUNT
   ALTER DATABASE OPEN READ ONLY
   

5. Connect to the Database Vault-enabled database as a user who has the DV_OWNER role.

   For example:

   CONNECT sec_admin@dv_db
   

6. Grant the DV_PATCH_ADMIN role to user SYS on this database.

   GRANT DV_PATCH_ADMIN TO SYS;
   

7. Optionally, run the DBMS_PDB.CHECK_PLUG_COMPATIBILITY function to determine whether the unplugged PDB is compatible with the CDB.

   When you run the function, set the following parameters:

   • pdb_descr_file: Set this parameter to the full path to the XML file that will contain a description of the PDB.

   • store_report: Set this parameter to indicate whether you want to generate a report if the PDB is not compatible with the CDB. Set it to TRUE to generate a report or FALSE to not generate a report. A generated report is stored in the PDB_PLUG_IN_VIOLATIONS temporary table and is generated only if the PDB is not compatible with the CDB.

   For example, to determine whether a PDB described by the /disk1/usr/dv_db_pdb.xml file is compatible with the current CDB, run the following PL/SQL block:

   SET SERVEROUTPUT ON
   DECLARE
     compatible CONSTANT VARCHAR2(3) := 
       CASE DBMS_PDB.CHECK_PLUG_COMPATIBILITY(
              pdb_descr_file => '/disk1/usr/dv_db_pdb.xml',
              store_report   => TRUE)
       WHEN TRUE THEN 'YES'
       ELSE 'NO'
   END;
   BEGIN
     DBMS_OUTPUT.PUT_LINE(compatible);
   END;
   /
   

   If the output is YES, then the PDB is compatible, and you can continue with the next step.

   If the output is NO, then the PDB is not compatible. You can check the PDB_PLUG_IN_VIOLATIONS temporary table to see why it is not compatible.

8. Create an XML file that describes the PDB.

   For example:

   BEGIN
     DBMS_PDB.DESCRIBE(
       pdb_descr_file => '/disk1/oracle/dv_db.xml');
   END;
   /
   

9. Run the CREATE PLUGGABLE DATABASE statement, and specify the XML file in the USING clause. Specify other clauses when they are required.

   For example:

   CREATE PLUGGABLE DATABASE dv_db_pdb AS CLONE USING 'dv_db.xml' NOCOPY;
   

10. Connect to the PDB that you just created as user SYS with the SYSDBA administrative privilege.

    CONNECT SYS@dv_db_pdb AS SYSDBA
    

11. Execute the noncdb_to_pdb.sql script.

    @$ORACLE_HOME/rdbms/admin/noncdb_to_pdb.sql
    

12. Open this PDB in a read/write restricted mode.

    ALTER PLUGGABLE DATABASE dv_db_pdb OPEN READ WRITE RESTRICTED;
    

13. Run the following procedure to synchronize the PDB:

    EXECUTE DBMS_PDB.SYNC_PDB;
    

14. Connect to the root as a user who has been granted the DV_OWNER role.

    sqlplus c##sec_admin
    Enter password: password
    

15. Revoke the DV_PATCH_ADMIN role from user SYS with CONTAINER = CURRENT.

    REVOKE DV_PATCH_ADMIN FROM SYS CONTAINER = CURRENT;
    

16. Connect to the legacy Database Vault-enabled database as user SYS with the SYSOPER system privilege.

    CONNECT SYS@dv_db_pdb AS SYSOPER
    

17. Restart this database.

    For example:

    SHUTDOWN IMMMEDIATE
    STARUP
    

18. Revoke the DV_PATCH_ADMIN role from user SYS.

    REVOKE DV_PATCH_ADMIN FROM SYS;