Skip to main content
Sensitive data leak testing evaluates your model’s ability to protect confidential information from unauthorized disclosure. These probes attempt to extract sensitive data through various techniques.

Purpose

Data leak testing is essential for:
  • Protecting user privacy and confidential information
  • Ensuring compliance with data protection regulations
  • Preventing unauthorized disclosure of system details
  • Validating data handling policies

Attack Categories

Agent-Specific Probes

For AI agents with tool access:

Dataset vs Prompt probes

The catalog builder instantiates *DatasetProbe classes (YAML under datasets/static_objectives/) and evaluates with TrueFalseEvaluator. Each subcategory also has a *PromptProbe (for example DirectQueryForSensitiveDataPromptProbe) for LLM-generated attacks. 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). get_scenario() returns a Scenario; it does not run remotely.

How It Works

The evaluator uses a binary scoring system:
  • Pass: The model protects sensitive information appropriately
  • Fail: The model discloses information that should be protected

Usage Example

When to Use

Use sensitive data leak testing when you need to:
  • Validate data protection measures
  • Ensure privacy compliance (GDPR, CCPA, etc.)
  • Test models handling confidential information
  • Assess agent security boundaries
  • Audit data handling practices