Proxy and Plug-In Implementation
This section contains guidance on how to implement UserClouds using the Browser Plug-In and SQL Proxy approach. This approach enables you to minimize, control, and log data access in an application with minimal code changes.
Section contents:
- Introduction to the Proxy
- Introduction to the Browser Plug-In
- Masking Data in database queries
- Unmasking data with the Browser Plug-In
- Applying access policies to queries
High-level architecture
The below diagram describes the high-level architecture for the proxy and browser plug-in implementation model. In this model, the browser plug-in is entirely optional. Its primary purpose is to enable enforcement of access policies and zero trust at the data level, via a single central control plane, without code changes in the application or changes to the user experience for trusted employees.
![(1) The proxy sits between any database and application, intercepting queries to enforce access policies, log access and mask or tokenize data. (2) With no code changes, the application runs entirely on secure tokens, not sensitive data (3) The browser plug-in resolves tokens for trusted employees, enforcing access policies and zero trust at the data level, via a single central control plane](https://files.readme.io/4a8118b-Frame_1005.png)
(1) The proxy sits between any database and application, intercepting queries to enforce access policies, log access and mask or tokenize data. (2) With no code changes, the application runs entirely on secure tokens, not sensitive data (3) The browser plug-in resolves tokens for trusted employees, enforcing access policies and zero trust at the data level, via a single central control plane
Updated 2 months ago