I want to mask sensitive variables (like msisdn) in debug/Trace only for a specific API proxy in Apigee X without affecting other APIs in the same environment. Currently, debug masking is applied at the environment level, and I cannot find a way to configure it per proxy. Is there a supported method to achieve proxy-level data masking in Apigee X?
1 Like
Hi,
Have you taken a look at using the private. prefix?
Masking and hiding data | Apigee | Google Cloud Documentation
If the data is being generated or load from something like a KVM, the easiest way to prevent sensitive data from even appearing in trace/debug sessions is by choosing a name that begins with private. for these custom variables.
Cheers,
In Apigee Edge, you could set a proxy (or revision) specific debugmask.
This is not possible in Apigee X, or hybrid. It’s a feature we considered but did not implement.
For now you have to use
- environment scoped masks
- the
private.prefix that Paul described.
1 Like
Alright, thank you for the response dchiesa1
Yeah I know about that but the data is coming in a request so will be visible in data coming from request.