Securing Sensitive Data by Configuration

Yes. While report assignment relies on standard Oracle Responsibilities , the capability to restrict sensitive data access is integrated. Sensitive data, such as Human Resources information, can be secured by configuration within the Blitz Report environment itself.

Configuration-based security, managed through Blitz Report definitions, complements the foundational security provided by Oracle VPD. VPD provides the ultimate row and column-level security enforced at the database level. Configuration allows you to control which responsibilities or users can even view or attempt to run reports containing that data in the first place.

This is primarily governed by the underlying Oracle security model. By implementing VPD policies, you ensure that even if a user is given access to the report definition, the database dynamically adds a predicate to the executed SQL, restricting the resulting rows to only what is authorized for that user’s security context.

The mechanism applies broadly. All reports, whether seeded Blitz Reports or custom SQL scripts, execute under the EBS security model. If you apply a VPD policy to an underlying table (e.g., employee details), any report querying that table will be restricted. Furthermore, you can assign any Blitz Report (including seeded ones) to a specific user, module, or responsibility.

Yes, for authorized users, the resulting data set—even if filtered by VPD—is outputted as a native, perfectly formatted Excel file, ready for immediate analysis.