Book Image

Oracle Database 12c Security Cookbook

By : Zoran Pavlovic, Maja Veselica
Book Image

Oracle Database 12c Security Cookbook

By: Zoran Pavlovic, Maja Veselica

Overview of this book

Businesses around the world are paying much greater attention toward database security than they ever have before. Not only does the current regulatory environment require tight security, particularly when dealing with sensitive and personal data, data is also arguably a company’s most valuable asset - why wouldn’t you want to protect it in a secure and reliable database? Oracle Database lets you do exactly that. It’s why it is one of the world’s leading databases – with a rich portfolio of features to protect data from contemporary vulnerabilities, it’s the go-to database for many organizations. Oracle Database 12c Security Cookbook helps DBAs, developers, and architects to better understand database security challenges. Let it guide you through the process of implementing appropriate security mechanisms, helping you to ensure you are taking proactive steps to keep your data safe. Featuring solutions for common security problems in the new Oracle Database 12c, with this book you can be confident about securing your database from a range of different threats and problems.
Table of Contents (18 chapters)
Oracle Database 12c Security Cookbook
Credits
About the Authors
About the Reviewers
www.PacktPub.com
Preface

Using Database Vault to implement that administrators cannot view data


In this recipe, you will use multiple components (realms, command rules, and rule sets) to secure data in database from administrators.

How to do it...

  1. Connect to the pluggable database PDB1 as the user c##dbv_acctmgr:

    SQL> connect c##dbv_acctmgr@pdb1
    SQL> create user orders_dba identified by oracle1;
    SQL> create user orders_user identified by oracle2;
    
  2. Connect to the pluggable database PDB1 as a SYS user and execute the following statements:

    SQL> connect sys@pdb1 as sysdba
    SQL> grant dba to orders_dba;
    SQL> grant create session to orders_user;
    SQL> grant select on oe.orders to orders_user;
    SQL> grant update on oe.orders to orders_user;
    SQL> create role ord_usr_role;
    SQL> grant ord_usr_role to orders_user;
    
  3. Create a realm that protects all objects in OE schema and authorize user orders_dba as owner (for detailed explanation on creating realms, see recipe Preventing users from exercising system...