Sensitive Data Separation for Geneva & Monaco

Context

Private banks in Switzerland and Monaco have to keep client-identifying data under tight control, even as that data flows through interfaces, generated documents and file transfers. Avaloq’s Sensitive Data Separation (SDS) architecture does this by splitting sensitive values from the rest of the data and resolving them only where that’s allowed.

What I did

• Implemented and supported SDS for the Geneva and Monaco business units, covering messages, forms and file-processing workflows.
• Configured message-level sensitive field control with CODE_SDS_MSG_FLD and field-level control with CODE_SDS_META_TYP_FLD.
• Supported pseudonymisation and sensitive-data resolution through the Avaloq Message Interface (AMI), in line with the SDS architecture.
• Enabled SDS-compliant file processing through AFP, applying tokenisation and detokenisation patterns for downstream processes such as EMI letter generation.
• Troubleshot and fixed production issues involving AMI, SDS adapters and downstream integrations.

Outcome

Sensitive data is handled consistently across every channel it passes through, and production processing that depends on SDS is more stable.

Details are kept at the level of standard Avaloq concepts. No client data or bank-internal specifics are shown here.