Home Discussions Questions & Answers Security Continuity: How Blitz Report Preserves EBS Responsibility and VPD Policies Post-Discoverer Migration

Security Continuity: How Blitz Report Preserves EBS Responsibility and VPD Policies Post-Discoverer Migration

Avatar photoCustomer November 20, 2025 at 10:09 am

A core compliance requirement is maintaining the integrity of our data access controls following our Oracle Discoverer replacement . Discoverer automatically inherited security definitions based on EBS Responsibilities, sometimes leveraging Virtual Private Database (VPD) logic internally. We must confirm that any new tool, such as Blitz Report, seamlessly respects and enforces the same underlying data constraints, preventing unauthorized access to sensitive information, especially when accessing large tables via direct SQL.

Viewing 4 reply threads
  • Author
    Replies
    • Support November 20, 2025 at 1:55 pm  

      Security is paramount. Blitz Report is architecturally integrated into the EBS foundation and explicitly follows EBS assignment rules, ensuring full compliance with user responsibilities and security configurations from the moment of implementation .

    • Support November 20, 2025 at 7:07 pm  

      Critically, Blitz Report fully enforces advanced database security, including the use of Oracle VPD policies at both the row and column levels . This means that when migrating Discoverer reports, the inherent security constraints travel with the data access .

    • Avatar photoCustomer November 21, 2025 at 12:12 am  

      If we grant a technical user access to run a report through Blitz Report under the APPS schema, how is the VPD constraint applied to prevent accidental data exposure?

    • Support November 21, 2025 at 2:30 am  

      VPD policies attached to tables dynamically restrict data based on user session attributes. When Blitz Report executes as APPS, custom VPD functions can check the application context (SYS_CONTEXT) to determine if the session originated from the Blitz Report module (‘XXEN_REPORT – %’) and apply necessary restrictions, such as hiding salary data or applying row-level constraints .

    • Support November 21, 2025 at 7:52 am  

      This robust layer of protection guarantees that your newly migrated EBS reporting capabilities maintain stringent data governance and cannot be bypassed, fulfilling critical audit requirements.

Viewing 4 reply threads
  • You must be logged in to reply to this post.

Login with: