Product / Field-level data protection

NSECURED MemberGo

Give each sensitive field a token that applications can use. When an AI workload needs the original value, MemberGo checks its purpose, identity and field policy before release.

Protection model

One field, three representations

Follow a temperature reading from a production line. The token and value shown here are synthetic.

01 / Collection
182 °C

A source submits a value

The collection flow receives a field in the context of a tenant, data type and registered purpose.

02 / Reference
pii_demo_7f3a

Applications carry the token

The vault encrypts the value. Applications link records with a token. Possessing that token grants no authority to retrieve the field.

03 / Authorized use
182 °C

An approved job uses the value

An approved quality-audit job may use the field in memory and clears it after use. Logs and usage records exclude the raw value.

Tokenization controls where raw values travel. Envelope encryption protects those values in the vault.

Interactive example

Change the purpose. See the decision.

The process parameter and service account stay the same. Only the declared purpose changes.

Manufacturing quality analysisInteractive demo · Synthetic data

Workload request

Process temperature

pii_7f3a…

Access granted

✓ 182 °C
access_id: demo_ac9d

The approved field is used in memory for this workload. A successful access is traceable. Its original value stays out of logs.

Policy design

Data owners define the conditions of use

01

Define fields and purposes

A tenant registers custom types such as process parameters or study codes and sets allowed purposes, retention and workload access.

02

Bind the service account to its scope

Each workload uses a service account in its tenant. Its grant can include model versions, permitted hours and a daily access limit.

03

Check each field before approving the request

MemberGo checks ownership, state, type and processing basis for every field. If any field fails its checks, the whole request is denied.

04

Record the access before release

Release follows successful access and audit writes. Reviewers can trace an access ID to its purpose, workload and model version.

Start with one data type

Scope the first evaluation around one workload, one permitted purpose and one case that should be denied.