PII Leak concern - GDPR

[p10tyr]

Relating to this line we need to turn this off since PII data is being passed to Stackify which is NOT our sub processor

stackify-api-dotnet/Src/StackifyLib/StackifyError.cs

Line 158 in 21e4254

UserName = HttpContext.Current.User.Identity.Name;

This can also apply to serialising cookies and would be very good to have options to control the level of data being exported from our application.

[danatcofo]

Would a setting override to disable this capture suffice?

Generally this is the system username that is captured and as such is one of the PII exceptions that is in place as its considered necessary for operation. Given that we would default the setting to allow capture.

[p10tyr]

In our case the HttpContext.Current.User.Identity.Name is probably not what you expected it to be as we have implemented extensions around identity.

Problem is that this Name can contain PII data that is considered exported once the data on the wire leaves the region.. which it can do.

The only time this is a problem, is when there is an exception. Looking at the Stackify code it then tries to grab allot of contextual information - which in our case is unnecessary. Identity.Name has no value compared to the Stacktrace.

If you were to look at Open Telemetry the approach there is to minimise risk of exporting sensitive data by default. For example to the point URL's don't contain formatted URLs for routes, say you have a custom route /api/{tenant}/records that is what you will see in the APM. No other context (including cookies or Identity) is used unless you explicitly enable it or add it in code.

We are restricted with sub processors and the less data exported the safer in our world.

Options that can be set upfront for all kinds of areas of sensitivity would probably be beneficial to everybody in the age of strict data restrictions.

[danatcofo]

Yup, @ppumkin we've got this scheduled for implementation with the next release and I'll be working on this issue. This is an open source project so we do and have accepted 3rd party PR's as well if you want to submit anything.

[danatcofo]

@ppumkin you might review the following documentation as well. https://docs.stackify.com/docs/errors-logs-capturing-web-request-details

[t-lair]

@ppumkin This will be fixed in the 2.2.9 release of this library