Auditing Privacy in Multi-Tenant RAG under Account Collusion
This paper identifies that multi-tenant RAG systems claiming per-account differential privacy are vulnerable to unbounded privacy degradation under same-tenant account collusion, and proposes the first audit protocol using cryptographic primitives to quantitatively verify the retrieval-score channel's privacy guarantees without requiring system modifications or index disclosure.
Original paper licensed under CC BY 4.0 (http://creativecommons.org/licenses/by/4.0/). This is an AI-generated explanation of the paper below. It is not written or endorsed by the authors. For technical accuracy, refer to the original paper. Read full disclaimer
The Big Picture: The "Group Chat" Problem
Imagine a massive, high-security library (the Multi-Tenant RAG Service) where thousands of different people (tenants) store their private documents. To protect privacy, the library has a rule: Every single person is allowed to ask a limited number of questions, and the answers are "noised" (blurred) so that no one can figure out exactly which specific documents are in the library. This is the Per-Account Privacy Guarantee.
The library tells you: "Don't worry, if you ask 100 questions, we guarantee your privacy is safe."
The Paper's Discovery:
The authors found a loophole. What if one bad actor doesn't just use one account, but creates 100 fake accounts (sock puppets) and coordinates them all to ask questions at the same time?
The paper argues that the library's current safety guarantee is like a single-person seatbelt. It works great if you are the only one in the car. But if 100 people pile into the car and all wear seatbelts, but they are all holding hands and pulling together, the seatbelt system fails. The "noise" that protects the documents gets canceled out when the answers from all 100 accounts are combined.
The Core Analogy: The Whispering Game
Imagine a game where you want to guess a secret word hidden in a room.
- The Guard (The Library): The guard whispers the word to you, but adds a lot of static noise so you can't hear it clearly.
- The Rule: If one person listens, the static is too loud to guess the word. The library says, "We are safe because the static is loud enough for one person."
- The Attack (The Collusion): Now, imagine 100 people (a coalition) stand in the room. Each person hears the word with static.
- Person 1 hears: "W...h...s...t..."
- Person 2 hears: "W...h...s...t..."
- Person 100 hears: "W...h...s...t..."
- The Result: When they all compare notes, the random static cancels out, and the real word becomes crystal clear.
The paper proves mathematically that if people collude, the privacy protection doesn't just drop a little; it drops by a factor of (the square root of the number of people).
- If 1 person attacks: Privacy is 100% (as promised).
- If 100 people attack: The privacy protection is effectively 10 times weaker (because ).
The Three Main Contributions
1. The Math: "The Square Root Rule"
The paper calculates exactly how much privacy is lost when accounts team up.
- Old Thinking: If 100 people team up, maybe the risk is 100 times higher (linear).
- New Finding: The risk is actually the square root of 100 times higher (which is 10).
- Why it matters: It's not as bad as the worst-case scenario (100x), but it is much worse than the library admits (1x). A library that claims "100% safe for one person" is actually only "10% safe" for a group of 100.
2. The Proof: "The Fake Attack"
The authors didn't just do math; they built a simulation to prove it works in real life.
- They created a fake library and a group of 20 fake accounts.
- They showed that by combining the answers from these 20 accounts, they could guess the secret documents much better than a single account could.
- Key Finding: Even when the library uses "Top-K" selection (only showing the top 5 results instead of the full list), the group attack still works. The "square root rule" holds true.
3. The Solution: "The Invisible Auditor"
This is the most creative part. The authors designed a new way to check the library without the library having to show its secret documents or change its code.
Imagine a Magic Receipt Book:
- Every time the library answers a question, it generates a cryptographic "receipt" (a digital seal) that proves:
- The answer came from the right documents.
- The "static noise" was added correctly.
- The answer didn't leak info about other people's documents.
- An Auditor (a third party) can look at these receipts and mathematically prove: "Yes, if a group of 10 people attacks, the privacy is only this strong."
- The Verdict: The auditor gives a simple PASS or FAIL grade, along with a number (like "Your privacy is only 3.2 out of 10"). This lets customers know the real risk without the library revealing its secrets.
What This Means for You (The Reader)
- For Users: If you use services like Microsoft Copilot or AI assistants that connect to your private files, the "privacy guarantee" you see in the fine print might be misleading if you are part of a large organization or if attackers create many fake accounts.
- For Companies: You can't just say "We are safe for one user." You need to account for the fact that users might team up.
- For Regulators: The paper suggests a new way to audit AI. Instead of asking companies to show their code (which they won't do), regulators can use this "Magic Receipt" system to verify privacy claims mathematically.
What the Paper Does NOT Say
- It does not say that current AI services are "broken" or that your data is definitely stolen right now.
- It does not say that the "Top-K" (showing only top results) feature is useless; it just says it doesn't stop a coordinated group attack.
- It does not solve the problem of "embedding inversion" (guessing the text just from the math behind the scenes); it focuses only on the retrieval step.
Summary
The paper reveals that privacy in AI libraries is fragile when users team up. It proves that a group of attackers can cancel out the privacy noise much faster than expected. To fix this, the authors invented a cryptographic audit system that acts like a "truth machine," allowing anyone to verify the real privacy level of an AI service without needing to see its secret data.
Drowning in papers in your field?
Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.