Defense Against Prompt Inversion Attacks: An Information-Theoretic Approach for LLM Collaborative Inference
This paper proposes an information-theoretic defense framework for collaborative LLM inference that utilizes privacy adapters and low-dimensional information bottlenecks to minimize mutual information between intermediate activations and input prompts, thereby achieving superior privacy-utility-latency tradeoffs against prompt inversion attacks.
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 "Cloud Kitchen" Problem
Imagine you have a very small, low-powered kitchen (your phone or laptop) that wants to cook a complex meal using a world-class recipe book (a Large Language Model, or LLM). Your kitchen doesn't have enough space or tools to cook the whole meal, so you decide to send the ingredients halfway through the process to a giant, professional "Cloud Kitchen" to finish the cooking.
The Problem:
When you send those half-cooked ingredients (the "intermediate activations") to the Cloud Kitchen, a nosy chef there might be able to look at the state of the food and guess exactly what your original secret recipe was. This is called a Prompt Inversion Attack. Even if you just send a few clues, a smart attacker can reconstruct your private input (like a medical diagnosis or a legal secret) just by looking at the halfway point of the cooking process.
The Old Solutions:
Previous attempts to stop this were like putting a little bit of salt or pepper in your ingredients before sending them (adding noise) or trying to hide them in a smaller box (reducing size). The problem is that these methods are often hit-or-miss. They might ruin the taste of the meal (make the AI's answer worse) without actually hiding the secret ingredients very well.
The New Solution: The "Smart Filter" (Privacy Adapters)
The authors propose a new, smarter way to protect your secrets. They call it an Information-Theoretic Defense.
Think of this as installing a Smart Filter (called a "Privacy Adapter") right before you send your ingredients to the Cloud Kitchen.
The Squeeze (Information Bottleneck):
Imagine your ingredients are a huge, colorful pile of vegetables, spices, and meats. The Smart Filter forces this huge pile through a tiny, narrow straw.- What gets through? The essential structure of the meal (the "syntax" or grammar). The Cloud Kitchen still gets enough info to finish cooking the sentence correctly.
- What gets left behind? The specific, sensitive details (the "semantics" or secret words). Because the straw is so narrow, the unique, rare ingredients (like a specific drug name or a person's ID) get crushed or lost in the squeeze.
The "No-Residual" Rule:
The paper makes a crucial point: You cannot just add a little noise to the ingredients and hope for the best. If you just add noise on top of the original ingredients, a smart chef can mathematically "subtract" the noise and see the original ingredients anyway.- The Fix: The authors' filter replaces the ingredients entirely with a compressed version. It doesn't add to the pile; it throws the original pile away and only sends the squeezed, compressed version. This makes it mathematically impossible to reverse-engineer the original secret.
How They Train the Filter
The authors didn't just guess how to build this filter. They used a "training camp" approach:
- The Defender (You): Tries to make the filter squeeze the ingredients as hard as possible to hide the secrets.
- The Attacker (The Cloud Chef): Tries to look at the squeezed ingredients and guess the original recipe.
- The Game: They play a game back and forth. The Defender tries to make the Attacker fail, while the Attacker tries to get better at guessing. The goal is to find the perfect balance where the Cloud Chef can still finish the meal (high utility) but cannot guess your secret ingredients (high privacy).
The "Selective Protection" Surprise
One of the coolest findings is that this filter is naturally selective.
- Common words (like "the," "is," "and," or punctuation) are like flour or water. They are common and easy to describe even through a tiny straw. The filter lets these pass through easily so the sentence still makes grammatical sense.
- Sensitive words (like "cancer," "SSRI," or "flight number 621") are like rare, exotic spices. They are hard to describe with limited space. When the filter squeezes the data, these rare, sensitive words are the first to get lost.
The Result: The Cloud Kitchen can still say, "The flight was good, the staff was friendly," but it completely loses the specific flight number, the route, or the medical condition. The attacker might know that you wrote a review, but they can't tell you what the review was about.
The Results in Plain English
The authors tested this on real-world scenarios (medical notes, legal documents, airline reviews) using powerful AI models.
- Privacy: They reduced the attacker's ability to guess your secrets by 15% to 35% compared to other methods. In some cases, the attacker's success rate dropped from nearly 90% down to about 50% (essentially a coin flip).
- Quality: The AI's answers were still very good. The "taste" of the meal wasn't ruined.
- Speed: The filter is so lightweight that it only slowed down the process by about 6% to 8%. This is fast enough to use on a phone without making you wait.
Summary
The paper introduces a "Smart Filter" for AI that squeezes your data before sending it to the cloud. It mathematically guarantees that sensitive secrets get crushed while keeping the useful structure intact. It's like sending a letter where the envelope is so small that only the general topic fits through, but the specific names and numbers get left behind, all without slowing down the mail delivery.
Drowning in papers in your field?
Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.