Attested Code Execution With Encrypted Session Tokens in Data Clean Rooms
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing cloud computing systems restrict users from executing dynamically generated SQL queries, limiting data sharing and collaboration while ensuring data privacy, especially in multi-tenant database environments.
Innovation Solution
A process orchestration layer generates a stored procedure with initialization, run, and output functions, using encrypted session tokens validated by a secret key to execute mutually approved code across multiple parties in a data clean room, ensuring data privacy and preventing unauthorized access or manipulation.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If users are restricted from executing dynamically generated SQL queries to ensure data privacy, then data security is improved, but user functionality and collaboration capability deteriorate
Solution Approach 1:
The patent introduces a process orchestration layer as an intermediary between users and the database system. This layer validates and executes approved code through stored procedures, acting as a mediator that enables user functionality while maintaining data security. The orchestration layer verifies code approval status and manages execution without exposing raw data to users.
Solution Approach 2:
The system segments code execution into distinct components: approval validation, token generation, and query execution. By dividing the execution process into separate stored procedure functions (initialization, run, output), the system can enforce security checks at each stage while allowing flexible user operations within approved boundaries.
2Reliability
If data clean rooms are set up to share aggregated and anonymized data, then data privacy is improved, but query flexibility and dynamic code execution deteriorate
Solution Approach 1:
The patent implements dynamic code execution within the data clean room environment by allowing approved code to be executed at runtime. The system validates code approval status dynamically through token verification and executes queries based on runtime conditions, enabling flexible analysis while maintaining privacy protections.
Solution Approach 2:
The system changes the parameter of code execution from static (pre-defined queries only) to dynamic (approved code execution). By using approval tokens and validated stored procedures, the system allows queries to be constructed and executed dynamically based on user needs while maintaining data privacy through the clean room architecture.
3Reliability
If approved code is executed through process orchestration with encrypted tokens, then security is improved, but system complexity increases
Solution Approach 1:
The process orchestration layer serves multiple functions: code validation, token generation, query execution, and result verification. By consolidating these security-critical functions into a single universal layer, the system improves security without proportionally increasing complexity, as the same layer handles multiple security tasks.
Solution Approach 2:
The system uses encrypted session tokens as copies of approval credentials. Instead of storing or transmitting actual approval information, the system creates encrypted token copies that verify code approval status. This copying mechanism simplifies security verification while maintaining strong security guarantees.
Data Source
AI summary
Methods, systems, and devices for data processing are described. A process orchestration layer of a data processing system may obtain an indication of code that has been approved by two or more parties of a secured sharing session. The process orchestration layer may generate a stored procedure that includes an initialization function, an output function, and a run function with the approved code. The process orchestration layer may output, to a first sub-system associated with a first party of the secured sharing session, a request that causes the first sub-system to execute the stored procedure. The process orchestration layer may receive an indication of an encrypted session token from the first sub-system in accordance with the initialization function of the stored procedure. The process orchestration layer may validate the encrypted session token and provide the validated session token to other parties of the secured sharing session.