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

Creating a driving context


In the previous recipe, you saw that having multiple VPD policies (most probably created because multiple application use that same table) is harder to manage, and it can lead to unexpected/unwanted results.

For example, you have two applications and want to create two policy groups. If the first application accesses the table, the test_pol1 and test_col policies should be enforced, and if second application accesses the table, the test_pol2 policies should be applied. There will be no default policies.

In this recipe, you'll create an application context and set it.

Getting ready

To complete this recipe, you'll need an existing user who can create an application context (for example, the user maja).

How to do it...

  1. Connect to the database as a user who has appropriate privileges (for example, the user maja):

    $ sqlplus maja
    
  2. Create a driving context (for example, driver_ctx):

    SQL> CREATE CONTEXT driver_ctx using driver_ctx_pkg;
    
  3. Set the driving context:

    SQL> CREATE...