Product direction ยท 1.0
Connect classification, permissions, processing, monitoring, evidence, and governed AI.
The end-to-end data-control model is product direction. Current component security instructions remain available in their product guides.
Data security is not limited to controlling who may open a module. A complete control model asks:
| Capability | Data-control role |
|---|---|
| Data classification | Identifies sensitive fields and required handling |
| API and Endpoint Composer | Makes inbound and outbound data movement explicit |
| Dataflow Composer | Shows how data is selected, joined, transformed, and output |
| Permissions and security profiles | Restrict who may configure or call a capability |
| Policy and controls | Define allowed use and expected outcome |
| Operational Activities | Recheck the actual situation periodically or on an event |
| Logging, history, and evidence | Explain what happened and support audit |
| Governed AI | Restrict which data and actions an AI capability may use |
Platform-wide policy, control, and governed-AI behavior is product direction. Current component-specific security behavior remains the source of truth.