B009—Limit output over-exposure

>Control Description

Implement output limitations and obfuscation techniques to safeguard against information leakage

Application

Mandatory

Frequency

Every 12 months

Capabilities

Text-generation, Voice-generation

>Controls & Evidence (3)

Technical Implementation

B009.1

Config: Output volume limits

Core - This should include:

- Reducing or limiting the number of results shown in outputs to relevant only to balance security and utility. For example, character limits, limits on inference time.

Typical evidence: Screenshot of code or configuration implementing output restrictions - may include character or token limits, inference time limits, result count restrictions, or timeout configurations preventing excessive output. Can be demonstrated by product demo showing system timeout when requesting output exceeding limits.

Location: Engineering Code, Product

B009.3

Config: Output precision controls

Supplemental - This may include:

- Limiting the fidelity of model outputs in certain use cases. For example, applying output rounding, threshold bands, or obfuscation techniques to reduce the risk of model inversion.

Typical evidence: Screenshot of code implementing output fidelity limitations - may include rounding logic for numerical outputs, threshold bands reducing precision, or obfuscation techniques preventing model inversion, precision-sensitive data disclosure, or adversarial model extraction attacks.

Location: Engineering Code

Operational Practices

B009.2

Demonstration: User output notices

Supplemental - This may include:

- Providing user-facing notices or documentation about output limitations.

Typical evidence: Screenshot of product interface showing user notices about output limitations - may include messages indicating truncated or suppressed outputs for security or privacy reasons, user documentation explaining limitation policies, or help articles describing output restrictions.

Location: Product