Stored Procedure Accelerator Guide for Microsoft SQL Server

Stored Procedure Accelerator Guide for Microsoft SQL Server

Masking Stored Procedures and Table-Valued Functions

Masking Stored Procedures and Table-Valued Functions

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 table-valued 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 table-valued function, the Rule Engine rewrites the SQL statement so that the Java Action receives the altered statement.
To mask stored procedure outputs, Dynamic Data Masking dynamically creates tables within the Microsoft SQL Server TempDb database based on the structure of the result set. It then populates the table with data in the TempDb database. Dynamic Data Masking names the tables in the TempDb database in the following way:
DDM_<Procedure Name>_<unique long number for call>_<result set sequence number>
For example, a table in the TempDb database might have the following name:
DDM_Proc_Dept_Emp_1381918459930_1
The unique long number for call and the result set sequence number are automatically generated numbers.
For each result set that the procedure returns, Dynamic Data Masking creates a new table in the TempDb database and populates the table with data. Dynamic Data Masking then applies masking rules to the SQL request and sends the modified SQL request to the table in the TempDb database. It then returns masked data to the client.

0 COMMENTS

We’d like to hear from you!