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

Column encryption - encrypting existing column


It is common case that organizations first create database and later decide that they want to implement encryption. In this recipe, you're going to encrypt an existing column using TDE column encryption.

Getting ready

It is assumed that a keystore is opened and a master key is created.

How to do it...

  1. Connect to the database as a user who can read data from the OE.CUSTOMERS table (for example, the oe user):

    $ sqlplus oe
    
  2. Select data from column you want to encrypt (for example, cust_email), just to verify that the user can view it.

    Figure 18 - A test query

  3. Connect to the database as a user who has administer key privilege or SYSKM privilege (for example, maja):

    SQL> connect maja
    
  4. Encrypt the cust_email column in the oe.customers table using the default encryption algorithm (AES192) and no salt.

    Figure 19 - Encrypting an existing column, which has an index

  5. Execute steps 1 and 2 again to verify that there is no change in the way user/application views...