Sensitive data in agent chat

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-24-2023 08:22 PM
Hi all,
Our Service Desk have suddenly started seeing the sanitization of email addresses that customers send via agent chat. The message that accompanies the sanitization is "This message was sensitive and has been sanitized.".
We haven't enabled this feature at all and when I search the sensitive data regexes, they are all set to inactive. Sensitive data detection is also disabled in the conversational interface settings.
Any ideas on where else to search so that I can disable this?
Cheers,
Brad
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-26-2023 08:02 AM
What version are you guys on? Just asking so I know what to look forward to when we go to a newer version.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-26-2023 03:20 PM
We're on Utah Patch 7.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-21-2023 12:23 AM
Hi Brad. Did you find the cause of this issue? I'm getting this message: "You have inputted sensitive information and it has been cleared from the chat history". But sensitive data handler is turned off.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-21-2023 12:56 PM
Hi @Albert6 . Unfortunately we couldn't identify the cause. ServiceNow took a copy of our production instance and did some testing from their end but they couldn't identify the cause either. They did confirm that all of our settings are correct and the filtering shouldn't be occurring. Our Service Desk haven't noticed it happening again since it first appeared so we are putting it down to a weird once-off issue for now.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
a month ago
Did you ever find the cause of the sensitive data marking while the feature was disabled?