Sensitive data can leak in two directions. It can sit on a page where the wrong person is looking, or be typed into a field it was never meant to reach. Sensitive Data Protection, which takes over from PII Rules, covers both right in the browser.
Setup starts from a built-in library of data types under Policy Management → Policies → Sensitive Data Protection, and anything the library doesn’t cover can be added as a custom type using keywords, regex or both.
Sensitive Data Policies decide how each type is treated. On screen a match can be blurred or masked, and when someone tries to send it, the response ranges from a silent log to a hard block. Policies are still applied through Custom URL Groups in a policy group.
Matches can be reviewed under Logs & Reports → Logs → Sensitive Data Logs, showing who triggered each one, on which site, when, under which policy and with what outcome.
For configuration details, see the Sensitive Data Protection knowledge base article.
This feature requires a CORE+ subscription or higher.