Navigating Privacy Risks in Generative AI: Concerns, Challenges, and Potential Solutions
TL;DR Highlight
A survey paper covering 4 types of attacks that extract training data from LLMs and defense strategies against them.
Who Should Read
ML engineers, security researchers, and privacy officers responsible for deploying LLMs in production, especially on sensitive or proprietary data.
Core Mechanics
- Taxonomy of 4 training data extraction attack types: memorization extraction, model inversion, membership inference, and attribute inference
- Memorization rate increases with model size — larger models are more vulnerable to verbatim extraction
- Repeated data in training sets dramatically increases extraction risk
- Defense strategies: differential privacy, data deduplication, output filtering, and canary detection
- No single defense fully mitigates all attack types; layered approaches are needed
Evidence
- Survey covers 50+ papers published through 2024
- Empirical evidence that GPT-2 and larger models can be prompted to regurgitate training data verbatim
- Differential privacy provides formal guarantees but at a significant accuracy cost
How to Apply
- Deduplicate your training data before fine-tuning — repeated examples are the primary driver of memorization.
- Add output filtering to block responses that match known sensitive patterns (PII, proprietary text).
- Use canary tokens in training data to detect if your model has been successfully queried for training data extraction.
Code Example
# Differential Privacy application example (Hugging Face + Opacus)
from opacus import PrivacyEngine
from torch.optim import AdamW
optimizer = AdamW(model.parameters(), lr=5e-5)
privacy_engine = PrivacyEngine()
model, optimizer, train_loader = privacy_engine.make_private_with_epsilon(
module=model,
optimizer=optimizer,
data_loader=train_loader,
epochs=3,
target_epsilon=5.0, # recommended value from paper
target_delta=1e-6, # recommended value from paper
max_grad_norm=1.0,
)
# Training loop can be used the same way
for batch in train_loader:
outputs = model(**batch)
loss = outputs.loss
loss.backward()
optimizer.step()
optimizer.zero_grad()
print(f"Privacy budget used: ε={privacy_engine.get_epsilon(delta=1e-6):.2f}")Terminology
Related Papers
What happened after 2k people tried to hack my AI assistant
실제로 6,000개 이상의 이메일로 AI 에이전트에 prompt injection 공격을 시도한 공개 실험 결과로, Claude Opus 4.6이 비밀 파일 유출을 한 번도 허용하지 않았지만 실험 설계의 현실성에 대한 논란이 뜨거웠다.
When Does Combining Language Models Help? A Co-Failure Ceiling on Routing, Voting, and Mixture-of-Agents Across 67 Frontier Models
여러 LLM을 조합해도 '모든 모델이 동시에 틀리는 비율(β)'이 성능 상한선이며, 업계가 쓰는 pairwise 상관계수(ρ)는 이 상한선을 예측하지 못한다.
Beyond Function Calling: Benchmarking Tool-Using Agents under Tool-Environment Unreliability
실제 환경처럼 API가 망가지거나 결과가 이상할 때 LLM 에이전트가 얼마나 잘 버티는지 측정하는 벤치마크 ToolBench-X 공개.
Nearly Half of LG Smart TV Apps Contain Residential Proxy SDKs
6,038개의 LG·Samsung 스마트 TV 앱을 스캔했더니 2,058개에서 사용자의 IP를 몰래 팔아 트래픽을 중계하는 Residential Proxy SDK가 발견됐다. TV는 컴퓨터처럼 감시받지 않아서 프록시 호스트로 거의 이상적인 환경이다.
Prompt Injection as Role Confusion
LLM이 시스템 프롬프트, 사용자 입력, 툴 출력을 구분하지 못하는 구조적 결함이 prompt injection의 근본 원인이라는 ICML 2026 논문으로, 현재 LLM 보안 아키텍처의 한계를 명확히 분석한다.
GPT-5.5 hallucinates 3x more than MIT-licensed GLM-5.2
모델 크기가 커질수록 성능이 좋아진다는 통념에 반해, 오픈소스 753B 모델 GLM-5.2가 추정 1~2T 규모의 GPT-5.5보다 환각 비율이 3배 낮다는 벤치마크 결과가 나왔다. 단순히 파라미터 수와 벤치마크 점수만으로 모델을 선택하면 실제 업무에서 낭패를 볼 수 있다는 경고다.
Original Abstract (Expand)
The rapid advancement of Generative Artificial Intelligence (GenAI) and Large Language Models (LLMs) has revolutionized numerous applications across healthcare, finance, and customer service. However, these technological breakthroughs introduce significant privacy risks as models may inadvertently memorize and expose sensitive information from their training data. This paper provides a comprehensive analysis of current privacy vulnerabilities in GenAI systems, including membership inference attacks, model inversion attacks, data extraction techniques, and data poisoning vulnerabilities. We examine state-of-the-art mitigation strategies including differential privacy (DP), cryptographic methods, anonymization techniques, and perturbation strategies. Through analysis of real-world case studies and empirical evidence, we demonstrate that current privacy-preserving techniques, while promising, face significant utility-privacy trade-offs. Our findings indicate that ε-differential privacy with ε = 5, δ = 10^-6 provides adequate protection for most practical applications, though stronger guarantees may be necessary for highly sensitive data. We conclude by presenting a comprehensive framework for user-centric privacy design and identifying critical areas for future research in privacy-preserving generative AI.