Data Masking and Anonymisation in the Orchestration Service
As of 2026-11-08
What is Data Masking and Anonymisation in the Orchestration Service?
The orchestration service's masking module anonymizes or pseudonymizes personal data before an LLM call, using one provider, SAP Data Privacy Integration, and roughly thirty named entity types with uneven regional scope — most notably profile-person for English names only and profile-location/profile-address for the United States only. Anonymization is irreversible and loses distinctions between people; pseudonymization is restored in the answer and in tool-call arguments.
One optional module, one provider, two methods
Why it matters
- A consultant who tells a customer 'masking handles GDPR' without reading the entity scope table is making a claim SAP itself does not make — profile-location and profile-address only cover the United States.
- Choosing anonymization when a downstream tool call needs the real value silently breaks the automation the customer asked for; the failure only shows up when someone inspects what the agent actually sent.
- mask_grounding_input defaults to off, so a masking configuration that looks complete on paper can still leak a name or an ID into whatever grounding retrieves from.
Key points
- One provider today: sap_data_privacy_integration. masking_providers is deprecated; use providers.
- Anonymization = irreversible MASKED_ENTITY; pseudonymization = numbered MASKED_ENTITY_ID, restored in the answer and in tool-call arguments.
- ~30 entity types, uneven regional scope: profile-person is English-only; profile-location/profile-address are US-only; profile-nationalid spans 20+ regions, profile-iban 70+.
- Anonymization destroys distinguishability between two entities of the same type in one input (SAP's own 'Michael and Donna' example).
- Replacement strategies: fabricated_data (plausible fake) or constant (fixed label, auto-numbered under pseudonymization). Custom regex entities require constant.
- allowlist exempts named values from masking regardless of entity type.
- mask_grounding_input (default disabled) masks the query sent to document grounding.
- PDF input requires an explicit mask_file_input_method: anonymization or skip.
Terms used on this page
- Anonymization
- Replaces personal data with an irreversible MASKED_ENTITY placeholder; the original value is not retained.
- Pseudonymization
- Replaces personal data with a numbered MASKED_ENTITY_ID placeholder, restored in the response and in tool-call arguments.
- Allowlist
- A list of exact string values exempted from masking regardless of entity type.
- mask_grounding_input
- A masking option (default disabled) that masks the query sent to document grounding before retrieval.
- Custom entity
- A masking entity defined by a regular expression instead of a named category; requires the constant replacement strategy.
- profile-sensitive-data
- A bundled entity covering nationality, religious group, gender, political group, pronoun gender, ethnicity and sexual orientation in one configuration line.
Sources
- SAP AI Core docs (SAP-docs GitHub, Sep 2026) — Data Masking (full entity catalog, scope, anonymization vs pseudonymization)
- SAP AI Core docs — Enhancing Model Consumption with Data Masking (allowlist, replacement strategies, custom entities, mask_grounding_input, PDF input)
- SAP AI SDK for Java — Orchestration chat completion, data masking (SAP-authored SDK docs)
- SAP AI SDK for JavaScript — Orchestration chat completion, data masking (SAP-authored SDK docs)
- SAP Developers — Tutorial: AI Core orchestration consumption options (masking as a consumption-pipeline option)
- GitHub SAP-docs — Get an orchestration deployment URL (SAP-authored mirror; the deployment this masking config attaches to)
- GitHub SAP-docs — Create a deployment for orchestration (SAP-authored mirror)
- GitHub SAP-docs — Enhancing model consumption with data masking, earlier revision (SAP-authored mirror, cross-reference on custom entity configuration)
- SAP Help Portal — Generative AI hub orchestration service overview (pipeline context for the masking module)
- SAP Developers — Tutorial: AI Core orchestration grounding (context for mask_grounding_input)
- SAP Help Portal — Orchestration deployment reference (legacy viewer URL, security/dependency context)
- Discovering the Orchestration Service — SAP Learning
- Orchestration Service V2 API (SAP Cloud SDK for AI, Python) — SAP Help Portal
- What Happens to Your Data When You Enable SAP's AI Features — SAP Community
- Securing SAP Business AI Architectures: Trust Boundaries and Secure Data Flows — SAP Community
Full card with the Consultant plan — €19.90/month. What the full card adds: the full decision framework · the SAP vs Snowflake / Databricks / Fabric comparison · the common pitfalls and their fix · the cheat sheet · the architecture schemas · the code blocks · the facts worth quoting.