VPD Implementation Steps and Security Scope

To implement VPD with Blitz Report, you must first define which tables or columns need securing . You configure this via the lookup `XXEN_REPORT_VPD_POLICY_TABLES` . Navigate to Application Developer > Application > Lookups > Application Object Library, query the lookup, and define an entry for each table or column, specifying the owner, table name, and the column name if needed . After setup, you typically run a concurrent program to activate the underlying database policies.

The key limitation is that using the Blitz Report method to secure data with VPD only enforces restrictions when data is accessed through the Blitz Report concurrent program itself . It explicitly does not secure data access if users try to run direct queries using database access tools like SQL Developer or Toad . This is crucial for managing security expectations.

The definition of which tables/columns are subject to VPD is managed within the Blitz Report lookup `XXEN_REPORT_VPD_POLICY_TABLES` . The activation of the policy is handled through a corresponding concurrent program, likely named ‘Blitz Report Update VPD Policies’ (based on context), which leverages the lookup configuration to apply the underlying database policy definitions . The complexity of the actual policy logic may still involve DBA input.

The profile option ‘Blitz Report VPD Policy Rule’ can be used for tracking or potentially setting up access related to sensitive data protected through Blitz Report VPD policies . However, the documentation does not detail the exact reporting mechanisms available within Blitz Report itself to display the active VPD policy SQL applied to a user’s session .