Give analysts the alerts, not the identities: data obfuscation in Netskope RBAC v3 A tier-1 analyst needs to see that a DLP policy fired, how severe it was, and which profile matched. They usually don't need to see who triggered it, the user's IP address, or the name of the file. In many organizations they aren't allowed to: privacy rules, works council agreements, and MSSP contracts often limit who can see personal data.RBAC v3 handles this with obfuscation. You choose which fields a role can't see, and Netskope replaces those values with [obfuscated] in everything that role reads, in the console and through the REST API. The analyst still gets the full alert, just without the personal data.This article walks through the feature end to end: what it hides, how to set it up, how to limit it to specific records, and how to prove it works before you hand the role to anyone.Two ideas to know firstObfuscation is set per function. In RBAC v3, a role grants a permission level (None, View, Manage, or Manage And Apply) on each function, such as Alerts, Application Events, or
