← Back to System Design Mind Map
🏗️ System DesignID: multi-tenant-partitioning-rbac

Multi-Tenant Partitioning & RBAC

企业级多租户隔离与 RBAC 权限
🎯Core Definition
Multi-Tenant Partitioning & Role-Based Access Control (RBAC) enforces strict physical/logical isolation and granular access authorization across B2B SaaS customers and sensitive enterprise departments (HR, Legal, Finance); the security architecture encompasses: 1) Vector Store Partitioning tiers (Metadata Filtering with strict `tenant_id` invariants, Namespace/Collection isolation, or dedicated physical clusters); 2) Chunk-Level RBAC ACL Inheritance, embedding user/group ACL permissions directly into chunk payloads during ingestion; 3) Pre-Filtering Retrieval Authorization, where the user's cryptographically verified JWT IAM claims are injected into vector search predicates upfront before ANN execution.
💡Use Cases
Multi-tenant enterprise LLM assistants, B2B knowledge management SaaS, and compliance-sensitive financial/healthcare RAG portals.
⚡Key Problems Solved
Post-Filtering (filtering after retrieval) can drop all Top-K candidates due to permission blocks, returning empty answers or leaking metadata titles; Pre-Filtering guarantees zero cross-tenant leakage and absolute compliance.
🎯Core Interview Exam Points
Fundamentals · Production Scenarios · Deep Dive
Core Def
Explain the core definition, underlying mechanism/math, and key principles of Multi-Tenant Partitioning & RBAC.
Use Cases
In production engineering, what are the primary use cases for Multi-Tenant Partitioning & RBAC and what core pain points does it solve?
🔥 High-Frequency Deep-Dive Questions
1
Compare Metadata Filtering, Collection Namespaces, and Physical Cluster Isolation across cost, isolation security, and query latency?
2
Why does secure RAG mandate Pre-Filtering (ACL masking during HNSW graph traversal) rather than Post-Filtering after candidate generation?
3
Design IAM token parsing at the gateway that flattens LDAP/Active Directory organizational hierarchies into chunk-level ACL filters?
4
How to handle immediate permission revocation upon employee departures without re-embedding millions of vector chunks?
5
Design tamper-proof audit logging and AES-256 encryption at rest/transit to pass SOC2 and GDPR multi-tenant enterprise audits?
Updated 2026-08-14
🎯
Verify Mastery: Practice Exam Questions for "Multi-Tenant Partitioning & RBAC"
Take pitfall multiple-choice questions with derivation options; mistakes are automatically logged.
🚀 Start Card Practice ➔
← Previous CardSemantic Cache & Request DeduplicationNext Card →SSE Streaming & Backpressure Control

🔗 More System Design Knowledge Cards

引用出处: TalentMe 450+ 工业级 AI 架构考点知识库 (Tech Vault) · 遵循 CC-BY-4.0 知识共享协议
URL: https://talentme.airsota.com/resources/tech/roadmap/mindmap/System_Design/card/multi-tenant-partitioning-rbac
中文速览与面试要点

企业级多租户隔离与 RBAC 权限 (Multi-Tenant Partitioning & RBAC)

定义: 企业级多租户隔离与 RBAC 权限过滤体系 (Multi-Tenant Partitioning & Role-Based Access Control) 是确保大模型 RAG 系统在服务多家企业客户(B端 SaaS)或企业内部多个敏感部门(财务、HR、研发)时,实现数据严格物理/逻辑隔离与细粒度访问控制的安全中枢;核心架构包括:1) 向量数据库租户隔离策略:逻辑分片 (Metadata Filtering: 向量库中带 `tenant_id` 过滤标量)、命名空间分片 (Namespace Partitioning: 每租户独立 Collection) 与物理独立集群隔离 (Physical Cluster Isolation);2) 文档级/Chunk 级 RBAC 权限继承:在文档切分时将 IAM 权限 ACL(用户 ID、用户组 ID、权限等级 Level)注入每个 Chunk 的元数据中;3) Pre-Filtering 检索期权限裁剪:在发起向量搜索的最初阶段即强行将当前用户的 Token 权限列表注入布尔过滤条件中,严禁未授权文档进入后续 LLM 上下文。 使用场景: 企业级 AI 助手、多租户 SaaS 知识库平台、金融与医疗领域合规 RAG 部署。 解决的问题: 若采用后置过滤 (Post-Filtering: 检索完再过滤权限),会导致返回给 LLM 的上下文被全部过滤导致无结果甚至泄露机密元数据;Pre-Filtering 机制保证了 100% 杜绝跨租户越权访问与机密数据泄露。

核心要点

  • 对比三种向量库多租户架构:标量元数据过滤 (Metadata Filter)、独立 Collection/Namespace、物理独占集群在成本、隔离性与 QPS 上的权衡?
  • 为什么在向量检索中必须执行“前置过滤 (Pre-Filtering: 在 HNSW 遍历图时施加 ACL 掩码)”,而不是“后置过滤 (Post-Filtering)”?
  • 基于 JWT Token 的 IAM 权限在网关层的无状态解析与将组织架构树 (LDAP / Active Directory) 动态扁平化为 Chunk ACL 数组的设计?
  • 当企业员工发生离职或部门调岗时,如何高效处理该用户在海量向量文档上的权限撤销与即时生效(无需全量重新 Embedding)?
  • 合规审计与防数据投毒:多租户环境下如何通过数据加密 (AES-256 at Rest & TLS in Transit) 与不可篡改审计日志防范越权探测?