Approved data environments
An approved environment is authorized for the relevant data class, model behavior, retention, access, and connected tools.
Definition
An approved environment is authorized for the relevant data class, model behavior, retention, access, and connected tools.
V1 rule
User-reported approval is an input to the check; the product does not certify the environment. Approval applies to a specific configuration and use, not a vendor name. It should cover the data class, account, model behavior, region, retention, access, logs, connectors, tools, and incident process.
Operational test
- Data: Which fields are allowed, prohibited, or subject to minimization?
- Processing: May the provider retain, train on, review, or move the data?
- Access: Which people, service accounts, connectors, and tools can reach prompts, sources, logs, and outputs?
- Lifecycle: How are exports, deletion, backups, incidents, and configuration changes handled?
Worked example
An enterprise account approved for internal documents does not automatically authorize a new web-search connector or customer-record workflow. The data owner reviews the changed data path first.
Record and reassess
- Record who approved the exact environment, for which data class and task, and when that decision must be reviewed.
- Reassess on any provider, account, model, region, retention, access, connector, tool, or data-class change.
Scope
The Task Fit Check applies approved data environments from categorical answers and deterministic house rules. It does not inspect the real environment, verify professional credentials, determine applicable law, or certify residual risk.