From ed701a99d50303f256e58f91325173495d78e7ca Mon Sep 17 00:00:00 2001 From: Martin Haintz Date: Tue, 26 Nov 2024 11:34:35 +0100 Subject: [PATCH] update the data scrubbing default values --- .../scrubbing/server-side-scrubbing/index.mdx | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/docs/security-legal-pii/scrubbing/server-side-scrubbing/index.mdx b/docs/security-legal-pii/scrubbing/server-side-scrubbing/index.mdx index 5d92e22eb4557..03e52381f5437 100644 --- a/docs/security-legal-pii/scrubbing/server-side-scrubbing/index.mdx +++ b/docs/security-legal-pii/scrubbing/server-side-scrubbing/index.mdx @@ -20,15 +20,13 @@ With it enabled, Sentry will scrub the following: - passwd - api_key - apikey - - access_token - auth - credentials - mysql_pwd - - stripetoken - - card[number] - - github_token - privatekey - private_key + - token + - bearer - Values that contain strings in, or whose keynames are listed in, [Project] > Settings > Security & Privacy in "Additional Sensitive Fields". - An entry in "Additional Sensitive Fields" such as `mysekret`, for example, will cause the removal of any field named `mysekret`, but also removes any field _value_ that contains `mysekret`. Sentry does this to protect against sensitive data leaking as part of structured data that has been sent as a single string to Sentry (such as a JSON object that is stringified and embedded as JSON string in another JSON structure). - As an extreme example where this behavior can become surprising, the string `"Unexpected error"` will be removed from events if the entry `exp` is in "Additional Sensitive Fields".