Information Technology, Control, Audit and Security Experience

Column Level VPD In my previous post we did a practical on how to perform Row level restriction using VPD policies. This practical will focus on the Column level restriction. And as said earlier we will be using the HR sample schema. In this tutorial we are going to secure some columns in the HR table “EMPLOYMENT” data.

In our previous post we learnt what the Oracle Virtual Database was all about. If you haven't read it click here . Without wasting much of your time, let get busy with our practicals What is needed W orking Oracle database (10g and above) HR sample schema. Sql work environment (SQL Navigator, Toad, etc) Today's tutorial will look at the following types of Virtual Private Databases: Row level VPD which restricts access to specific rows in a table Column Level VPD  which restricts access to specific columns in a table

Oracle  Virtual Private Database  (VPD)  enables you to create security policies or group policies to control database access at the row and column level. It allows multiple users to access a single schema while preventing them from accessing data which is not relevant to them. VPD uses Fine-Grained Access Control to limit visibility of the data to the specific users. In this post I will be showing you how a VPD is used with its advantages

In my previous post I talked about Auditing UTL_FILE_DIR parameter file entry. If you haven't read it, you can check it out here . In this post I will be focusing on how the UTL_FILE package is actually used to transfer files to the host operating system from the database. This post will be showing you exactly how dangerous the package can be in the hands of a malicious person. Note that EXECUTE on the UTL_FILE package is granted to PUBLIC by default. What this means is that any user created in the database automatically has the right to use this package. Enough of the stories. Now lets get straight to business