Hi Sanjay,
In your case, your mentioned "500 users in the database" , is it all
database user/schema accounts or application users that use a common app
schema to connect to the database. You can do something like this - use
database log on trigger / set db context and use client identifier (if its
a app user) or session user (if its a db user) to identify logged in user
details and apply custom written functions that can dynamically add where
clause to the queries based on conditions that can filter and provide
appropriate results. Finally you can add policy to the object where you
want to apply vpd. so whenever that object gets requested, policy will be
applied to restrict the results.
Thanks,
Vishnu
On Thu, Jun 14, 2018 at 11:54 AM Sanjay Mishra <dmarc-noreply@xxxxxxxxxxxxx>
wrote:
YEs VPD look like is the solution and so looking for some high level
approach from the experts who has worked with VPD.
Tx
Sanjay
On Thursday, June 14, 2018, 9:31:33 AM EDT, Jko <jacques.kostic@xxxxxxxxx>
wrote:
Hi
Vpd will solve your problem easily.
Cheers
Jki
Le 14 juin 2018 15:26:26 "Sanjay Mishra" <dmarc-noreply@xxxxxxxxxxxxx>
(Redacted sender "smishra_97" for DMARC) a écrit :
Hi Everyone
Need some view on best approach to do data masking. I had around 8-10
tables with 2 columnn that has secured financial data. Column name are same
in all tables where data need to masked.
The requirement is that there are 500 users in the database and data need
to be restricted using these 2 columns for these 10 tables
1. One set of the user will have access to all Data
2. Another set can use column 1 value condition
3. Another set of the user who can see the data based on Column 2 value
condition
Oracle 12.1 and has Enterprise license for all Oracle options. ANy
approach that can help in creating the plan will be helpful
TIA
Sanjay
