# GRD-014: Prevent sensitive data reaching unauthorized tools or account tiers


- Area: Runtime Guardrails

- Verification: Live test
- OWASP adoption tier: AT0–AT4
- Formerly: DAT-004
- URL: /r/GRD-014

**Acceptance criteria:** Block before egress while allowing legitimate work and treating sanctioned and personal tiers differently.

**Why it matters:** The same content can be fine in an enterprise tenant and a reportable incident in a personal one.

**How to verify:** The same sensitive content is allowed to the enterprise tenant and stopped for a personal account.

**OWASP adoption context:** Unauthorized destinations and account tiers can occur throughout the listed employee AI contexts; an approved tool name alone does not establish an approved destination.

**Mappings:**
- NIST CSF 2.0: PR.AA-05, PR.DS-02; SOC 2: CC6.7; ISO 27001: A.8.12, A.8.3, A.5.14 — Blocking sensitive data before egress to unauthorized tools or account tiers enforces a concrete authorization and transfer boundary. Coverage must include actual routes and tier changes; sanctioned status does not authorize every transfer. Classification, monitoring and warnings alone do not enforce these restrictions.
ISO/IEC 27001: A.8.12: Use an active, approved leakage-control workflow at the stated data boundary. If claiming blocking, demonstrate it before egress. A.8.3: Access restrictions must act before the operation. Correct sensitivity and account-tier identification are prerequisites.
- NIST AI RMF: MANAGE 1.3 — Pre-egress blocking is a mitigation option for the identified AI disclosure risk. The buyer must connect the policy to documented risk priorities and response decisions.
- ISO 42001: A.9.2 — Blocking sensitive data before it reaches an unauthorized tool or account implements a specific responsible-use rule for AI inputs. Define the permitted destinations and verify enforcement; destination approval alone does not establish conformity with the AI system’s intended functions.