Table of Contents

Search

  1. Preface
  2. Introduction to the Stored Procedure Accelerator for Oracle
  3. Masking Stored Procedures and User-Defined Table Functions
  4. Stored Procedure Accelerator Setup
  5. Stored Procedure Accelerator Rules

Stored Procedure Accelerator Guide for Oracle

Stored Procedure Accelerator Guide for Oracle

Masking Stored Procedures and User-Defined Table Functions Overview

Masking Stored Procedures and User-Defined Table Functions Overview

Dynamic Data Masking uses a Java Action security rule to determine whether an incoming statement is a call to a stored procedure or a SELECT statement that includes a user-defined table function that returns a result set. The Java Action rewrites the SQL statement so that the masking rules can use the result set structures.
If the stored routine is a user-defined table function, the Rule Engine rewrites the SQL statement so that the Java Action receives the altered statement.
The Dynamic Data Masking user defines a temporary Oracle schema in the DefMaskRSSym security rule. To mask stored procedure outputs, Dynamic Data Masking dynamically creates a temporary stored procedure in the temporary schema. The temporary stored procedure creates global temporary tables within the temporary schema based on the structure of the result set. It then populates the table with the data in the temporary schema. Dynamic Data Masking names the tables in the temporary schema in the following way:
T_<Timestamp>
For example, a table in the temporary schema might have the following name:
T_5290365863
The timestamp is an automatically generated number.
The temporary stored procedure forms SELECT queries for each table in the temporary schema and masks the queries based on the security rules.
Because the Stored Procedure Accelerator for Oracle uses methods implemented on Oracle 11g, the database must be Oracle 11g or later.

0 COMMENTS

We’d like to hear from you!