You register Oracle Database Vault with common users who will use the Database Vault-enforced roles in the CDB root.

1. Log into the root of the database instance as a user who has privileges to create users and grant the CREATE SESSION and SET CONTAINER privileges.

   For example:

   sqlplus c##dba_debra
   Enter password: password
   

2. Select user accounts (or create new users) that will be used for the Database Vault Owner (DV_OWNER role) and Database Vault Account Manager (DV_ACCTMGR role) accounts.

   Oracle strongly recommends that you maintain two accounts for each role. One account, the primary named user account, will be used on a day-to-day basis and the other account will be used as a backup account in case the password of the primary account is lost and must be reset.

   Prepend the names of these accounts with c## or C##. For example:

   GRANT CREATE SESSION, SET CONTAINER TO c##sec_admin_owen 
     IDENTIFIED BY password CONTAINER = ALL;
   GRANT CREATE SESSION, SET CONTAINER TO c##dbv_owner_root_backup 
     IDENTIFIED BY password CONTAINER = ALL;
   GRANT CREATE SESSION, SET CONTAINER TO c##accts_admin_ace 
     IDENTIFIED BY password CONTAINER = ALL;
   GRANT CREATE SESSION, SET CONTAINER TO c##dbv_acctmgr_root_backup 
     IDENTIFIED BY password CONTAINER = ALL;

   In this specification:

   • Create the primary accounts (c##sec_admin_owen and c##accts_admin_ace) if these do not already exist for the new roles, DV_ADMIN and DV_ACCTMGR.
   • Replace password with a password that is secure.
3. Connect to the root as user SYS with the SYSDBA administrative privilege

   CONNECT SYS AS SYSDBA
   Enter password: password
   

4. Configure the two backup Database Vault user accounts.
   For example:

   BEGIN
    CONFIGURE_DV (
      dvowner_uname         => 'c##dbv_owner_root_backup',
      dvacctmgr_uname       => 'c##dbv_acctmgr_root_backup',
      force_local_dvowner   => FALSE);
    END;
   /

   In this example, setting force_local_dvowner to FALSE enables the common users to have DV_OWNER privileges for the PDBs that are associated with this CDB root. Setting it to TRUE restricts the common DV_OWNER user to have the DV_OWNER role privileges for the CDB root only. If you grant DV_OWNER locally to the CDB root common user, then that user cannot grant the DV_OWNER role commonly to any other user.
5. Run the utlrp.sql script to recompile invalidated objects in the root.

   @?/rdbms/admin/utlrp.sql
   

   If the script provides instructions, follow them, and then run the script again. If the script terminates abnormally without giving any instructions, then run it again.

6. Connect to the root as the primary Database Vault Owner user that you just configured.

   For example:

   CONNECT c##dbv_owner_root_backup
   Enter password: password
   

7. Enable Oracle Database Vault using one of the following commands:

   • To enable Oracle Database Vault to use regular mode:

     EXEC DBMS_MACADM.ENABLE_DV;

   • If every associated PDB will need to have Database Vault enabled in this database, then use the following command. (You will need to enable each of these PDBs after you complete this procedure.) PDBs that do not have Database Vault enabled will be in restricted mode after the database is restarted and until Database Vault is enabled in the PDB:

     EXEC DBMS_MACADM.ENABLE_DV (strict_mode => 'y');

8. Connect with the SYSDBA administrative privilege.

   CONNECT / AS SYSDBA
   

9. Restart the database.

   SHUTDOWN IMMEDIATE
   STARTUP
   

10. Verify that Oracle Database Vault and Oracle Label Security are installed and enabled.

    SELECT * FROM DBA_DV_STATUS;
    SELECT * FROM DBA_OLS_STATUS;

11. Connect as the backup DV_OWNER user and then grant the DV_OWNER role to the primary DV_OWNER user that you created earlier.

    For example:

    CONNECT c##dbv_owner_root_backup
    Enter password: password
    
    GRANT DV_OWNER TO c##sec_admin_owen WITH ADMIN OPTION;
    

12. Connect as the backup DV_ACCTMGR user and then grant the DV_ACCTMGR role to the backup DV_ACCTMGR user.

    For example:

    CONNECT c##dbv_acctmgr_root_backup
    Enter password: password
    
    GRANT DV_ACCTMGR TO c##accts_admin_ace WITH ADMIN OPTION
    CONTAINER=ALL;

13. Store the two backup account passwords in a safe location such as a privileged account management (PAM) system in case they are needed in the future.

You must register Oracle Database Vault in the root first, then in the PDBs afterward.

1. If you have not already done so, then identify or create named common user accounts to be used as the Database Vault accounts along with associated backup accounts.
2. Ensure that you have registered Oracle Database Vault in the CDB root and that the DV_OWNER role was granted commonly to the common user.
3. Connect to the PDB as an administrator who is local to the PDB.
   For example:

   CONNECT dba_debra@pdb_name
   Enter password: password
   

   To find the available PDBs, query the DBA_PDBS data dictionary view. To check the current PDB, run the show con_name command.

4. Grant the CREATE SESSION and SET CONTAINER privileges to the users for this PDB.
   For example:

   GRANT CREATE SESSION, SET CONTAINER TO c##sec_admin_owen CONTAINER = CURRENT;
   GRANT CREATE SESSION, SET CONTAINER TO c##accts_admin_ace CONTAINER = CURRENT;
   

5. Connect as user SYS with the SYSDBA administrative privilege

   CONNECT SYS@pdb_name AS SYSDBA
   Enter password: password
   

6. While still in the PDB, configure the two backup Database Vault user accounts.

   BEGIN
    CONFIGURE_DV (
      dvowner_uname         => 'c##dbv_owner_root_backup',
      dvacctmgr_uname       => 'c##dbv_acctmgr_root_backup');
    END;
   /
   

   In this example, the force_local_dvowner parameter is omitted because it is unnecessary. All common users who are configured within a PDB are restricted to the scope of the PDB.

7. Run the utlrp.sql script to recompile invalidated objects in this PDB.

   @?/rdbms/admin/utlrp.sql
   

   If the script provides instructions, follow them, and then run the script again. If the script terminates abnormally without giving any instructions, then run it again.

8. Connect to the PDB as the backup Database Vault Owner user that you just configured.
   For example:

   CONNECT c##dbv_owner_root_backup@pdb_name
   Enter password: password
   

9. Enable Oracle Database Vault in this PDB.

   EXEC DBMS_MACADM.ENABLE_DV;
   

10. Connect to the CDB with the SYSDBA administrative privilege.

    CONNECT / AS SYSDBA
    

11. Close and reopen the PDB.
    For example:

    ALTER PLUGGABLE DATABASE pdb_name CLOSE IMMEDIATE;
    ALTER PLUGGABLE DATABASE pdb_name OPEN;
    

12. Verify that the PDB is configured and enabled for Database Vault and Oracle Label Security.

    CONNECT SYS@pdb_name AS SYSDBA
    Enter password: password
    
    SELECT * FROM DBA_DV_STATUS;
    SELECT * FROM DBA_OLS_STATUS;

13. Connect as the backup DV_OWNER user and then grant the DV_OWNER role to the primary DV_OWNER user that you created earlier.

    For example:

    CONNECT c##dbv_owner_root_backup@pdb_name
    Enter password: password
    
    GRANT DV_OWNER TO c##sec_admin_owen WITH ADMIN OPTION;
    

14. Connect as the backup DV_ACCTMGR user and then grant the DV_ACCTMGR role to the primary DV_ACCTMGR user.

    For example:

    CONNECT c##dbv_acctmgr_root_backup@pdb_name
    Enter password: password
    
    GRANT DV_ACCTMGR TO c##accts_admin_ace WITH ADMIN OPTION;

15. Store the two backup account passwords in a safe location such as a privileged account management (PAM) system in case they are needed in the future.

In this tutorial, you create a realm around for the HR sample database schema by using the Oracle Database Vault PL/SQL packages.

In the HR schema, the EMPLOYEES table has information such as salaries that should be hidden from most employees in the company, including those with administrative access. To accomplish this, you add the HR schema to the secured objects of the protection zone, which in Oracle Database Vault is called a realm, inside the database. Then you grant limited authorizations to this realm. Afterward, you test the realm to make sure it has been properly secured.

You must enable the HR schema for this tutorial.

1. Log in to a PDB as a user who has been granted the DBA role, and then access the HR schema.

   For example:

   sqlplus system@pdb_name
   Enter password: password
   

   To find the available PDBs, query the PDB_NAME column of the DBA_PDBS data dictionary view. To check the current container, run the show con_name command.

2. Query the HR.EMPLOYEES table as follows.

   SELECT FIRST_NAME, LAST_NAME, SALARY FROM HR.EMPLOYEES WHERE ROWNUM < 10;
   

   Output similar to the following appears:

   FIRST_NAME           LAST_NAME                     SALARY
   -------------------- ------------------------- ----------
   Steven               King                           24000
   Neena                Kochhar                        17000
   Lex                  De Haan                        17000
   Alexander            Hunold                          9000
   Bruce                Ernst                           6000
   David                Austin                          4800
   Valli                Pataballa                       4800
   Diana                Lorentz                         4200
   Nancy                Greenberg                      12008
   
   9 rows selected.
   

3. If the HR schema is locked and expired, log in to the database instance as the DV_ACCTMGR user and unlock and unexpire the account. For example:

   sqlplus bea_dvacctmgr@pdb_name
   Enter password: password
   
   ALTER USER HR ACCOUNT UNLOCK IDENTIFIED BY password
   

   Replace password with a password that is secure.

   As you can see, SYSTEM has access to the salary information in the EMPLOYEES table of the HR schema. This is because SYSTEM is automatically granted the DBA role, which includes the SELECT ANY TABLE system privilege.

4. Do not exit SQL*Plus.

Realms can protect one or more schemas, individual schema objects, and database roles.

1. Connect to a PDB as a user who has been granted the DV_OWNER role.
   For example:

   CONNECT c##sec_admin_owen@pdb_name
   Enter password: password

2. Create the HR App realm around the HR.EMPLOYEES table.
   1. Create the HR Apps realm itself.

      BEGIN
       DBMS_MACADM.CREATE_REALM(
        realm_name    => 'HR Apps', 
        description   => 'Realm to protect the HR schema', 
        enabled       => DBMS_MACUTL.G_YES, 
        audit_options => DBMS_MACUTL.G_REALM_AUDIT_OFF,
        realm_type    => 0);
      END; 
      /

   2. Add the HR.EMPLOYEES table to this realm.

      BEGIN
       DBMS_MACADM.ADD_OBJECT_TO_REALM(
        realm_name   => 'HR Apps', 
        object_owner => 'HR', 
        object_name  => 'EMPLOYEES', 
        object_type  => 'TABLE'); 
      END;
      /

At this stage, there are no database accounts or roles authorized to access or otherwise manipulate the database objects the realm will protect.

1. In SQL*Plus, connect to the PDB as the Database Vault Account Manager, who has the DV_ACCTMGR role, and create the local user SEBASTIAN.

   For example:

   CONNECT bea_dvacctmgr@pdb_name
   Enter password: password
   
   GRANT CREATE SESSION TO SEBASTIAN IDENTIFIED BY password;
   

   Replace password with a password that is secure.

2. Connect as SYS with the SYSDBA privilege, and then grant SEBASTIAN the following additional privilege.

   CONNECT SYS@pdb_name AS SYSDBA
   Enter password: password
   
   GRANT READ ANY TABLE TO SEBASTIAN;
   

3. Do not exit SQL*Plus.

Next, user SEBASTIAN must be granted authorization to the HR Apps realm, so that he can access the HR.EMPLOYEES table.

1. Connect to the PDB as the user who created the HR Apps realm.
   For example:

   c##sec_admin_owen@pdb_name
   Enter passwod: password

2. Create an authorization for the HR Apps realm.

   BEGIN
    DBMS_MACADM.ADD_AUTH_TO_REALM(
     realm_name  => 'HR Apps', 
     grantee     => 'SEBASTIAN'); 
   END;
   /

To test the realm, you must try to access the EMPLOYEES table as a user other than HR.

You can remove the components that you created for this tutorial if you no longer need them.