{"id":"GRD-014","section":"Runtime Guardrails","requirement":"Prevent sensitive data reaching unauthorized tools or account tiers","acceptance":"Block before egress while allowing legitimate work and treating sanctioned and personal tiers differently.","tier":"AT0–AT4","whyItMatters":"The same content can be fine in an enterprise tenant and a reportable incident in a personal one.","verificationMethod":"LT","verificationTest":"The same sensitive content is allowed to the enterprise tenant and stopped for a personal account.","formerly":"DAT-004","alsoIn":[],"sort":24,"adoptionContext":"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":[{"frameworks":["csf","soc2","iso27001"],"explanation":"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.\nISO/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.","kind":"framework","references":{"csf":["PR.AA-05","PR.DS-02"],"soc2":["CC6.7"],"iso27001":["A.8.12","A.8.3","A.5.14"]},"relation":null,"conditions":[]},{"frameworks":["rmf"],"explanation":"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.","kind":"framework","references":{"rmf":["MANAGE 1.3"]},"relation":null,"conditions":[]},{"frameworks":["iso"],"explanation":"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.","kind":"framework","references":{"iso":["A.9.2"]},"relation":null,"conditions":[]}],"area":"Runtime Guardrails","areaSlug":"GRD","url":"/r/GRD-014","frameworkRefs":{"ISO27001":["A.8.12","A.8.3","A.5.14"],"ISO42001":["A.9.2"],"NIST-CSF":["PR.AA-05","PR.DS-02"],"NIST-AI-RMF":["MANAGE 1.3"],"SOC2":["CC6.7"]}}