Resources / Technical reading

Follow the data flow

Explore the product mechanism, policy boundaries and VISCOR reference integration from the perspective of your evaluation team.

Reading guide

Choose a starting point

Product & data owners

The lifecycle of a field

Follow a synthetic process temperature from collection through tokenization to approved use. See who can receive the value and when.

Read the product guide

Security & governance

Protection and verification scope

Review encryption, field authorization, audit scope and attestation status before a technical assessment.

Open the trust center

Platform & integration engineers

VISCOR integration guide

Review ownership of service identities, event catch-up, field release and usage reconciliation.

Read the integration guide

Terms in practice

Three terms used throughout the guides

A · field token

Field token

An opaque reference to a protected field. The caller still needs authorization before it can receive the original value.

B · purpose

Purpose

A registered reason for processing data, such as quality auditing. The requested purpose is checked against the grant and processing basis.

C · workload

Workload

A program or model job that performs a specific task. Each deployment uses a managed service identity to request fields within its grant.

Start with an allowed and a denied use case

Select a type and purpose, explore the product example and define an initial proof of concept.