Hi @staskh,

Thanks for the extra context. I’d flag that your requirement is a bit self‑contradictory...

end user has access to all data and capabilities within Databricks
while preventing download of large amounts of data

If a user can see all the data and use all capabilities (including notebooks, SQL, APIs), there’s no frontend technology... RBI included... that can guarantee they don’t exfiltrate large volumes. They can always script incremental reads, copy/paste, or do exactly what you already accept (screenshots/photos).

Given you’re already planning a strong backend airlock with VPC + controlled egress, I’d frame the frontend airlock requirement as "Not make exfiltration impossible, but make bulk exfiltration harder and more visible."

In practice, that usually means a mix of:

• Databricks‑side controls: strict authZ (Unity Catalog), sensible query/result size limits, and audit/monitoring for unusual volumes.
• Endpoint/channel controls: DLP, rate‑limiting, possibly VDI/RDS for the user session if you need extra assurance.

RBI can add friction to bulk download options in the browser, but because you already allow screenshots/photos, its incremental benefit is limited. I’d start by tightening permissions, limits, and monitoring, and only add RBI/VDI if your security team still feels the residual risk is too high.

If this answer resolves your question, could you mark it as “Accept as Solution”? That helps other users quickly find the correct fix.