Data masking
Replacing the personal or confidential values in a prompt with placeholders before it leaves for a model, and putting them back in the answer. Anonymisation, where the values are gone for good, and pseudonymisation, where they return, are the two forms; which fields count as sensitive is the application's question, not the module's.
Overview
A module of the orchestration service in SAP AI CoreSAP AI CoreSAP's AI service on BTP: the runtime for AI assets, and through the Generative AI Hub inside it the access to foundation models, the orchestration service with its templating, masking, filtering and grounding modules, the Prompt Registry and Document Grounding.sap official, btp: the prompt is masked before the model sees it, by anonymisation or pseudonymisation, and with pseudonymisation the placeholders in the response are unmasked again.
Not covered: At the prompt text. The module works on what is in the prompt it is handed, with the entity types chosen per call; anything a model reaches by another route is outside it.
Every provider behind this door is SAP's, so core-only is a assessment of the corpus rather than a quote from the core.
No community artifact is documented here.
Artifacts
Content
Seen working
Every CDS service in both samples is marked `@requires: 'any'` and left publicly accessible, which the README says simplifies the testing and deployment process, and it asks for proper authentication mechanisms to be applied in their place.
Details
Coverage
For your agent
- Ref
capability:data-masking- JSON
- /capabilities/data-masking.json
- MCP
- Connecting an agent