Oracle Database 12c Security Cookbook

Oracle Database 12c Security Cookbook

By : Zoran Pavlovic, Maja Veselica

Buy this Book

Oracle Database 12c Security Cookbook

By: Zoran Pavlovic, Maja Veselica

Buy this Book

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.

Oracle Database 12c Security Cookbook

Credits

About the Authors

About the Reviewers

www.PacktPub.com

Preface

Free Chapter

Basic Database Security

Introduction

Creating a password profile

Creating password-authenticated users

Changing a user's password

Creating a user with the same credentials on another database

Locking a user account

Expiring a user's password

Creating and using OS-authenticated users

Creating and using proxy users

Creating and using database roles

The sysbackup privilege – how, when, and why should you use it?

The syskm privilege – how, when, and why should you use it?

The sysdg privilege – how, when, and why should you use it?

Security Considerations in Multitenant Environment

Introduction

Creating a common user

Creating a local user

Creating a common role

Creating a local role

Granting privileges and roles commonly

Granting privileges and roles locally

Effects of plugging/unplugging operations on users, roles, and privileges

PL/SQL Security

Introduction

Creating and using definer's rights procedures

Creating and using invoker's right procedures

Using code-based access control

Restricting access to program units by using accessible by

Virtual Private Database

Introduction

Creating different policy functions

Creating Oracle Virtual Private Database row-level policies

Creating column-level policies

Creating a driving context

Creating policy groups

Setting context as a driving context

Adding policy to a group

Exempting users from VPD policies

Data Redaction

Introduction

Creating a redaction policy when using full redaction

Creating a redaction policy when using partial redaction

Creating a redaction policy when using random redaction

Creating a redaction policy when using regular expression redaction

Using Oracle Enterprise Manager Cloud Control 12c to manage redaction policies

Changing the function parameters for a specified column

Add a column to the redaction policy

Enabling, disabling, and dropping redaction policy

Exempting users from data redaction policies

Transparent Sensitive Data Protection

Introduction

Creating a sensitive type

Determining sensitive columns

Creating transparent sensitive data protection policy

Associating transparent sensitive data protection policy with sensitive type

Enabling, disabling, and dropping policy

Altering transparent sensitive data protection policy

Privilege Analysis

Introduction

Creating database analysis policy

Creating role analysis policy

Creating context analysis policy

Creating combined analysis policy

Starting and stopping privilege analysis

Reporting on used system privileges

Reporting on used object privileges

Reporting on unused system privileges

Reporting on unused object privileges

How to revoke unused privileges

Dropping the analysis

Transparent Data Encryption

Introduction

Configuring keystore location in sqlnet.ora

Creating and opening the keystore

Setting master encryption key in software keystore

Column encryption - adding new encrypted column to table

Column encryption - creating new table that has encrypted column(s)

Using salt and MAC

Column encryption - encrypting existing column

Auto-login keystore

Encrypting tablespace

Rekeying

Backup and Recovery

Database Vault

Introduction

Registering Database Vault

Preventing users from exercising system privileges on schema objects

Securing roles

Preventing users from executing specific command on specific object

Creating a rule set

Creating a secure application role

Using Database Vault to implement that administrators cannot view data

Running Oracle Database Vault reports

Disabling Database Vault

Re-enabling Database Vault

Unified Auditing

Introduction

Enabling Unified Auditing mode

Configuring whether loss of audit data is acceptable

Which roles do you need to have to be able to create audit policies and to view audit data?

Auditing RMAN operations

Auditing Data Pump operations

Auditing Database Vault operations

Creating audit policies to audit privileges, actions and roles under specified conditions

Enabling audit policy

Finding information about audit policies and audited data

Auditing application contexts

Purging audit trail

Disabling and dropping audit policies

Additional Topics

Introduction

Exporting data using Oracle Data Pump in Oracle Database Vault environment

Creating factors in Oracle Database Vault

Using TDE in a multitenant environment

Appendix – Application Contexts

Introduction

Exploring and using built-in contexts

Creating an application context

Setting application context attributes

Using an application context

Customer Reviews

5 star

4 star

3 star

2 star

1 star

Creating and using proxy users

In this recipe, you'll learn about proxy users.

Getting ready

To complete this recipe, you'll need an existing (for example, OS-authenticated) user who has a DBA role and another existing user (for example, mike).

How to do it...

Connect to the database as a user who has a DBA role:
```
$ sqlplus /
```

Create a proxy user named appserver:

SQL> create user appserver identified by oracle_1;

Grant create session to the user appserver:

SQL> grant create session to appserver;

Alter the user to connect through the proxy user:

SQL> alter user mike grant connect through appserver;

Connect to the database through proxy user:
```
SQL> connect appserver[mike]
```
Enter a password for the appserver user (for example, oracle_1):
```
Enter password:
```
To revoke connection through the proxy user, first connect to the database as a user who has altered user privilege:
```
$ sqlplus /
```
Revoke connection through the proxy user appserver from user mike:
```
SQL> alter user mike revoke connect through appserver;
```

How it works...

Proxy authentication is best-suited type of authentication for three-tiered environments. The middle tier is represented as a proxy user in the database and this user can authenticate end-users in such a way that these end users can be audited by the database. In the second step, you created a user appserver (to be the proxy user). In the third step, you granted this user only the create session privilege.

Tip

It is recommended that you grant only the create session privilege to proxy users.

In step 4, you authorized user mike to connect through proxy user appserver. This means that the user appserver can connect to the database on behalf of user mike:

SQL> connect appserver[mike]

Enter password:
Connected.

SQL> show user
USER is "MIKE"

SQL> select sys_context('USERENV','PROXY_USER') from dual;
SYS_CONTEXT('USERENV','PROXY_USER')
-----------------------------------
APPSERVER

To see proxy users, you can query the proxy_users view:

SQL> select * from proxy_users;

PROXY      CLIENT  AUT   FLAGS---------- ------- ---- ------------------------------------
APPSERVER   MIKE    NO   PROXY MAY ACTIVATE ALL CLIENT ROLES

In the last step, you revoked authorization from user mike to connect through proxy user appserver. This means that the user appserver can no longer connect to the database on behalf of user mike.

There's more...

You can control which roles the proxy user can activate for user. By default, all user roles are activated. If you want the proxy user to activate only particular roles (or no roles) for a user, you can do that by adding the WITH ROLES <role1, role2, .., roleN> (or WITH NO ROLES) clause at the end of the alter user statement. For instance, if the user mike has many roles (including usr_role), and you want him to have only usr_role when he is connected through proxy user appserver, statement will look like this:

SQL> alter user mike grant connect through appserver with roles usr_role;


User altered.


SQL> connect appserver[mike]


Enter password:
Connected.


SQL> select * from session_roles;


ROLE
------------
USR_ROLE


SQL> connect mike


Enter password:
Connected.


SQL> select count(*) from session_roles;


COUNT(*)
--------
25

You can request reauthentication of a user to the database. This means that during proxy authentication, a user's password must be provided. This is done by using the authentication required clause at the end of alter user statement:

SQL> alter user mike grant connect through appserver authentication required;
User altered.

Oracle Database 12c Security Cookbook

By : Zoran Pavlovic, Maja Veselica

Oracle Database 12c Security Cookbook

By: Zoran Pavlovic, Maja Veselica

Overview of this book

Related Content you might be interested in

Current Title:

Oracle Database 12c Security Cookbook

Creating and using proxy users

Getting ready

How to do it...

How it works...

Tip

There's more...