doc(pii): Advanced data scrubbing stabilized #1786
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
PeloWriter
approved these changes
Jun 24, 2020
| sidebar_order: 4 | ||
| keywords: ["pii", "gdpr", "personally identifiable data", "compliance"] | ||
| --- | ||
|
|
||
| In addition to using [`beforeSend`]({% link _documentation/data-management/sensitive-data.md %}#custom-event-processing-in-the-sdk) in your SDK or our [server-side data scrubbing features]({% link _documentation/data-management/sensitive-data.md %}#server-side-scrubbing) to redact sensitive data, we are currently beta-testing ways to give you more granular control over server-side data scrubbing of your events. Additional functionality includes: | ||
| In addition to using [`beforeSend`]({% link _documentation/data-management/sensitive-data.md %}#custom-event-processing-in-the-sdk) in your SDK or our [regular server-side data scrubbing features]({% link _documentation/data-management/sensitive-data.md %}#server-side-scrubbing) to redact sensitive data, Advanced Data Scrubbing is an alternative way to redact sensitive information just before it is saved in Sentry. It allows you to: |
There was a problem hiding this comment.
the {% link...} approach is apparently problematic - might wish to use the markdown format here.
| @@ -40,7 +30,7 @@ Rules generally consist of three parts: | |||
| ## Methods | |||
|
|
|||
| - _Remove_: Remove the entire field. We may choose to either set it to `null`, remove it entirely or replace it with an empty string depending on technical constraints. | |||
There was a problem hiding this comment.
nit: serial comma (add a comma after "remove it entirely")
| @@ -40,7 +30,7 @@ Rules generally consist of three parts: | |||
| ## Methods | |||
|
|
|||
| - _Remove_: Remove the entire field. We may choose to either set it to `null`, remove it entirely or replace it with an empty string depending on technical constraints. | |||
| - _Mask_: Replace all characters with `*`. For creditcards this replaces everything but the last 4 digits. | |||
| - _Mask_: Replace all characters with `*`. | |||
| - _Hash_: Replace the matched substring with a hashed value. | |||
| - _Replace_: Replace the matched substring with a constant placeholder value such as `[Filtered]` or `[creditcard]`. Right now this value cannot be configured. | |||
There was a problem hiding this comment.
Suggest replacing "Right now" with "Currently" (it's what we're using in other places, so easier to find if we're searching and making changes. But it's not critical.
There was a problem hiding this comment.
the entire sentence was incorrect, removed
|
thanks @PeloWriter for reviewing early! |
priscilawebdev
approved these changes
Jun 25, 2020
|
GA toggle PR is here: getsentry/sentry#19630 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is the absolute minimum amount of changes we need to get out on June 30th.