Fields to protect
Customer transactions, sensitive financial fields and customer identifiers. Transaction features and identifying details can be governed separately.
NSECURED MemberGo / Financial services
Fraud analysts need transaction features to identify anomalies. Financial institutions can register the fields a risk workload needs and distinguish fraud analysis from marketing through service identities and purpose controls.

Financial services
Customer transactions, sensitive financial fields and customer identifiers. Transaction features and identifying details can be governed separately.
An approved fraud workload may receive custom fields such as transaction amount band, frequency and merchant category.
Synthetic data example
fraud_detectiontxn_frequency amount_band200 · access_id: demo_7c20In a transaction-monitoring pilot, the approved fraud workload can read frequency and amount band to score a synthetic transaction.
marketing ×txn_frequency amount_band403 data_access_deniedA marketing workload requesting the same transaction fields for product recommendations is denied when only fraud analysis has been authorized.
The fields and decisions here are illustrative. Actual access depends on tenant settings, the basis for processing and the approved purpose.
Workflow
The risk team lists the model inputs and identifies the source, purpose and owner of each field.
Set up separate test identities for fraud and marketing so their purposes and permissions can be evaluated independently.
Run both purposes against one synthetic transaction. Verify which features were released and check that audit records omit their values.
Proof of concept
Ask risk and security teams to choose three transaction features. Submit fraud and marketing requests, then compare the decisions, stop behavior and internal trace records.