Skip to main content
Input leakage testing evaluates whether your model inadvertently reveals information from previous conversations or user inputs. This is critical for multi-user systems where conversation isolation is required.

Purpose

Input leakage testing helps ensure:
  • User privacy between conversations
  • Proper session isolation
  • No cross-contamination of user data
  • Compliance with data handling requirements

Attack Categories

Dataset vs Prompt probes

The catalog builder instantiates *DatasetProbe classes and evaluates with TrueFalseEvaluator. Each subcategory also has a *PromptProbe (for example InputPersistenceCheckPromptProbe). Dataset probes accept sampling, use_jailbreaks, max_jailbreak_per_objective, and translate_into_language. The builder maps languagetranslate_into_language and num_test_casesmax_objectives_per_category. See StaticDatasetProbe. Catalog scenarios attach framework tags (EU AI Act, OWASP, MITRE ATLAS, ISO/IEC 42001).

How It Works

The evaluator checks for information leakage:
  • Pass: The model maintains proper input isolation
  • Fail: The model reveals information from previous inputs inappropriately

Usage Example

When to Use

Use input leakage testing when you need to:
  • Validate session isolation
  • Ensure user privacy in multi-tenant systems
  • Test conversation boundary handling
  • Audit data handling practices
  • Meet privacy compliance requirements