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 an application context


In this recipe, you'll see one possible usage (in SQL) of the application contexts. Some other usages are shown in other parts of the book, and their references are given in the See also section of this recipe.

Getting ready

Create a new user (for example, sofia). Make sure that his or her e-mail in the format [email protected] is unique. Grant him or her privileges: create session and select on sh.customers table.

Figure 12 - New user

Insert data about him or her into the sh.customers table.

Figure 13 - The new data in sh.customers

How to do it...

  1. Connect to the database as a newly created user (for example, user sofia):

    $ sqlplus sofia
    
  2. Verify that the user (for example, sofia) can access all data in the sh.customers table.

    Figure 14 - The entire data in sh.customers

  3. Verify that when executing the following statement, he or she (for example, sofia) can view only his or her data.

    Figure 15 - Only data about newly created user

How it works...

In step 3, a simple way...