Cross-tenant data leakage isolation
First Claim
1. A method for cross-tenant data leakage isolation in a multi-tenant database, comprising:
- monitoring, by a proxy device, traffic flows between a server executing at least one cloud-based application and the multi-tenant database, wherein the proxy device is communicatively connected between the server and the multi-tenant database;
capturing, by the proxy device, at least a request to access the multi-tenant database, wherein the request is communicated using a database-specific protocol;
analyzing the request to determine if the request is illegitimate, wherein an illegitimate request is not addressed to a global-tenant table including records of individual database tables of tenants in the multi-tenant database;
upon determining that the request is not legitimate, modifying the request to point to a global-tenant table and to designate a condition with a unique tenant identifier having permissions to access the table identified in the received query, wherein the unique tenant identifier corresponds to a tenant-specific table name designated in the global-tenant table, and wherein the global-tenant table is shared across multiple machines; and
sending the modified request to the multi-tenant database using the database-specific protocol.
1 Assignment
0 Petitions
Accused Products
Abstract
A method and proxy device for cross-tenant data leakage isolation in a multi-tenant database are provided. The method includes monitoring, by a proxy device, traffic flows between a server executing at least one cloud-based application and the multi-tenant database, wherein the proxy device is communicatively connected between the server and the multi-tenant database; capturing, by the proxy device, at least a request to access the multi-tenant database, wherein the request is communicated using a database-specific protocol; analyzing the request to determine if the request is legitimate; upon determining that the request is not legitimate, modifying the request to point to a global-tenant table and to designate a unique tenant identifier, wherein the unique tenant identifier corresponds to a tenant-specific table name designated in the global-tenant table; and sending the modified request to the multi-tenant database using the database-specific protocol.
32 Citations
22 Claims
-
1. A method for cross-tenant data leakage isolation in a multi-tenant database, comprising:
-
monitoring, by a proxy device, traffic flows between a server executing at least one cloud-based application and the multi-tenant database, wherein the proxy device is communicatively connected between the server and the multi-tenant database; capturing, by the proxy device, at least a request to access the multi-tenant database, wherein the request is communicated using a database-specific protocol; analyzing the request to determine if the request is illegitimate, wherein an illegitimate request is not addressed to a global-tenant table including records of individual database tables of tenants in the multi-tenant database; upon determining that the request is not legitimate, modifying the request to point to a global-tenant table and to designate a condition with a unique tenant identifier having permissions to access the table identified in the received query, wherein the unique tenant identifier corresponds to a tenant-specific table name designated in the global-tenant table, and wherein the global-tenant table is shared across multiple machines; and sending the modified request to the multi-tenant database using the database-specific protocol. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 11)
-
-
12. A non-transitory computer readable medium having stored thereon instructions for causing a processing circuitry to execute a method, the method comprising:
-
monitoring, by a proxy device, traffic flows between a server executing at least one cloud-based application and the multi-tenant database, wherein the proxy device is communicatively connected between the server and the multi-tenant database; capturing, by the proxy device, at least a request to access the multi-tenant database, wherein the request is communicated using a database-specific protocol; analyzing the request to determine if the request is illegitimate, wherein an illegitimate request is not addressed to a global-tenant table including records of individual database tables of tenants in the multi-tenant database; upon determining that the request is not legitimate, modifying the request to point to a global-tenant table and to designate a condition with a unique tenant identifier having permissions to access the table identified in the received query, wherein the unique tenant identifier corresponds to a tenant-specific table name designated in the global-tenant table, and wherein the global-tenant table is shared across multiple machines; and sending the modified request to the multi-tenant database using the database-specific protocol.
-
-
13. A proxy device for cross-tenant data leakage isolation in a multi-tenant database, the proxy device is communicatively connected between a server executing a cloud-based application and the multi-tenant database, comprising:
-
a processing circuitry; and a memory, the memory containing instructions that, when executed by the processing circuitry, configure the proxy device to; monitor traffic flows between the server and the multi-tenant database; capture at least a request to access the multi-tenant database, wherein the request is communicated using a database specific protocol; analyze the request to determine if the request is illegitimate, wherein an illegitimate request is not addressed to a global-tenant table including records of individual database tables of tenants in the multi-tenant database; modify the request to point to a global-tenant table and designate a condition with a unique tenant identifier having permissions to access the table identified in the received query, upon determination that the request is not legitimate, wherein the unique tenant identifier corresponds to the tenant-specific table name designated in the global-tenant table, and wherein the global-tenant table is shared across multiple machines; and send the modified request to the multi-tenant database using the database specific protocol. - View Dependent Claims (14, 15, 16, 17, 18, 19, 20, 21, 22)
-
Specification