Hierarchical Tenant Filtering for Secure Report Data Access

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In multi-tenancy data management systems, there is a challenge in efficiently and securely managing access authorization for report data across hierarchical tenant structures, where higher-level tenants need to access data from their subtenants while ensuring data security and reliability.

Innovation Solution

The system determines user permissions based on the tenant associated with a login session, filters computing objects within an object hierarchy, and generates a mapping table to ensure only authorized access to report data, allowing higher-level tenants to view filtered data from subtenants.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If the system allows higher-level tenants to access data from subtenants, then data accessibility and reporting capability are improved, but data security and authorization management complexity increase

Engineering Contradiction:
Improvedata accessibilityVSAvoidauthorization management complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system segments authorization management by implementing tenant-specific context identification and filtering. Each tenant's access to report data is controlled through separate context identifiers (tenant IDs) that are embedded in data requests and responses. This segmentation allows higher-level tenants to access subtenant data while maintaining distinct authorization boundaries, resolving the contradiction between data accessibility and authorization management complexity.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system introduces an intermediary filtering mechanism that processes data requests between tenants. The filter component acts as a mediator that automatically validates tenant context, applies appropriate authorization rules, and returns only permitted data. This intermediary layer simplifies authorization management by automating the complex validation logic, allowing higher-level tenants to access subtenant data without manual authorization configuration.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If the system implements comprehensive access filtering and context verification, then data security is improved, but processing time and system overhead increase

Engineering Contradiction:
Improvedata securityVSAvoidprocessing time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs preliminary context identification and tenant verification at the beginning of data processing operations. By establishing the tenant context early in the request lifecycle and caching authorization decisions, the system minimizes repeated verification overhead. This preliminary action ensures data security through comprehensive filtering while reducing processing time by avoiding redundant validation operations throughout the data pipeline.

Inventive Principle:
Principle #10Preliminary action

3Productivity

If the system stores and processes report data for multiple tenants in a unified structure, then data consolidation and analysis capability are improved, but data isolation and tenant privacy are compromised

Engineering Contradiction:
Improvedata consolidation capabilityVSAvoiddata isolation
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The system implements local quality by applying tenant-specific filtering rules and context identifiers to different portions of the unified data structure. Each tenant's report data is marked with unique identifiers that enable selective retrieval and processing. This approach allows the system to maintain a consolidated data storage structure for improved productivity while ensuring data isolation through tenant-specific quality attributes that prevent unauthorized access to other tenants' data.

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS12461947B2Access authorization for report data in a multi-tenancy data management system
Publication Date: 2025.11.04 RUBRIK INC
  • US12461947B2 patent drawing
  • US12461947B2 patent drawing
  • US12461947B2 patent drawing

AI summary

Methods, systems, and devices for data management are described. A multi-tenancy data management system (DMS) may include multiple computing objects organized as a hierarchy of computing objects. The DMS may receive a request for report data associated with a first set of computing objects of the DMS. The DMS may identify context information for a log-in session associated with the request. The context information may include a tenant identifier (ID) for a tenant associated with the request. The DMS may apply a filter to the first set of computing objects. The filter may be based on a second set of computing objects to which the tenant has access within the hierarchy of computing objects. The DMS may output the report data for at least one computing object of the first set based on the at least one computing object being included in the second set of computing objects.