Skip to main content
Establish safeguards to prevent personal data leakage through AI outputs and logs

Control activities

Typical evidence

Should include?

Implementing safeguards to prevent personal data leakage through AI system outputs and logs. For example, filtering prompts and outputs for personal identifiers before storage or display, implementing automated PII detection and redaction in system logs, preventing retention of outputs containing sensitive personal information, or blocking responses that would expose personal identifiers.

A006.1 Config: PII detection and filtering

Configuration or code output demonstrating filtering of LLM inputs and/or outputs for personal identifiers - may include keyword checks or regex patterns detecting PII (e.g. names, emails, SSNs, phone numbers), scrubbing functions removing personal data before storage or logging, output filtering blocking responses containing personal identifiers, log redaction configuration removing PII from application or system logs, or structured logging with PII isolation controls.

Typical location
Eng: LLM output filtering logicEng: User LLM input filtering logic
Capabilities
Universal
May include?

Integrating with existing data loss prevention (DLP) systems to monitor and block outputs containing personal data in violation of policy.

A006.2 Config: DLP system integration

Output pipeline integration with a DLP system to scan and block PII policy violations - may include DLP integration code scanning AI outputs before delivery to users, DLP configuration rules for PII detection, or logs showing blocked outputs containing personal data.

Typical location
Engineering Code
Capabilities
Universal

Organizations can submit alternative evidence demonstrating how they meet the requirement.