Review how provider requests, Cortex telemetry, deployment choices, access controls, retention, and assurance evidence fit together before Cortex connects to your environment.
On a standard provider request path, the selected model provider receives the prompt required to fulfill the request. Cortex telemetry synchronization is a separate path with its own capture, minimization, deployment, retention, and access boundary.
Selected model route
The selected client prepares the request for the chosen model provider.
Pinned traffic keeps its provider. A configured managed route can apply the controls documented for that path.
The provider receives the prompt and context required to return the requested response.
Configured evidence boundary
Device, provider, model, process, harness, and tool signals depend on the deployed capture path.
Local capture policy minimizes the telemetry written and prepared for synchronization.
Approved telemetry synchronizes to the configured Cortex data plane under the deployment's retention and access controls.
Supported device capture applies local policy before telemetry is written or prepared for synchronization. This is separate from provider-request handling.
The local capture proxy listens on loopback. Managed routing or interception controls are documented separately for the configured deployment path.
Approved Cortex telemetry synchronizes to the configured data plane under the deployment's capture, access, retention, and deletion policy.
Cortex access controls scope who can review synchronized evidence. Source-system permissions and integration behavior remain part of the documented boundary.
Choose the control boundary that matches your architecture, then verify the data handling, integration, access, and operational prerequisites.
Managed Cortex services with data handling defined by the selected service, region, and retention configuration.
Cortex telemetry is processed and stored in the customer-controlled cloud environment defined by the deployment architecture.
Customer-operated deployment subject to architecture review, supported infrastructure, and integration requirements.
Available reports and certifications can change. Cortex provides the current package, scope, and applicability directly to your security and procurement team.
It depends on the configured route. On a standard provider request path, the selected provider receives the prompt required to fulfill the request. Cortex telemetry is a separate path. Managed enforcement applies only when the request or execution traverses a documented Cortex-controlled decision point.
The model provider receives the request content required for the selected AI workflow. Separately, approved Cortex telemetry synchronizes according to the deployed capture, minimization, destination, retention, and access policy.
The answer depends on the selected deployment. Cortex Cloud, a customer data plane, and customer-hosted options have different infrastructure and operational boundaries. The architecture review documents the applicable storage, processing, and integration path.
Cortex access controls scope who can review synchronized evidence. Source-system permissions, identity-provider configuration, tenant isolation, service identities, and administrative access are reviewed as separate controls for the selected deployment.
Cortex can provide current architecture and data-flow documentation, identity and access information, retention and deletion controls, subprocessor information, applicable assurance reports, and security-questionnaire support. The package is confirmed for scope and currency during the review.
Review the current architecture, data flows, deployment model, access controls, retention, and applicable assurance evidence with the Cortex team.