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 salt and MAC


In this recipe, you'll understand when you should use salt and MAC.

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 has administer key privilege or SYSKM privilege (for example, maja):

    $ connect maja
    
  2. Encrypt two columns in an existing table (for example, sh.customers)

    Figure 15 - Using salt and MAC

How it works...

In step 2:

  • You encrypted the last_name column using the AES256 algorithm with salt and used MAC

  • You encrypted the cust_street_address column using the AES256 algorithm with no salt and used MAC

In general, you have to use same encryption algorithm for all encrypted columns at the same time. You can choose a SALT option on the encrypted column level in a table, but you have to choose either the MAC or NOMAC option on a table level (meaning that all encryption columns in a table must use the same option).

There's more...

To understand why salt is important, let's consider a basic scenario...