Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Security/Privacy Bug Fix: SQL command collection off by default [change in behavior] #1690

Closed
TimothyMothra opened this issue Feb 18, 2020 · 13 comments
Assignees
Milestone

Comments

@TimothyMothra
Copy link
Member

We're introducing a new change in 2.14 which will disable the collection SQL command text by default.
We understand this will likely be a breaking change for many customers, but this is being addressed as a security and privacy bug fix.

This will be introduced in 2.14-Beta1 and the stable release will be early April.

Before then we MUST update public documentation and add a post on our Announcements repo.
We will discuss with PMs to consider a blog post about this breaking change.

@TimothyMothra
Copy link
Member Author

#1514

@TimothyMothra
Copy link
Member Author

@cijothomas
Copy link
Contributor

@TimothyMothra Lets mention explicitly that this only affects .NET Core apps. For .NET Framework, SQL command was not collected by default and required additional steps.

@cijothomas
Copy link
Contributor

https://github.com/microsoft/ApplicationInsights-Announcements/issues - we can announce it here instead of a blog post?

@stebet
Copy link
Contributor

stebet commented Mar 10, 2020

@TimothyMothra Lets mention explicitly that this only affects .NET Core apps. For .NET Framework, SQL command was not collected by default and required additional steps.

This does affect the .NET Framework as well, since the SQL Command can now be collected when using the Microsoft.Data.SqlClient package.

@cijothomas
Copy link
Contributor

I meant "Off by default" is a new behavior for .NET Core. For .NET Framework, it was always "Off by default".

Agree that doc should cover the new way to turn on SQL Text for .NET Framework.

@stebet
Copy link
Contributor

stebet commented Mar 11, 2020

It's on by default in the .NET Framework if you use the latest release of the Microsoft.Data.SqlClient libs. It's why I submitted #1723

@cijothomas
Copy link
Contributor

@stebet
https://github.com/microsoft/ApplicationInsights-dotnet/blob/develop/WEB/Src/DependencyCollector/Shared/DependencyTrackingTelemetryModule.cs#L76

This shows the default value is false?
For .NET framework, using MS.Data.SqlClient also, one has to turn this ON to get full query, right?

@stebet
Copy link
Contributor

stebet commented Mar 27, 2020

Yeah, my point was that before this change, if you referenced Microsoft.Data.SqlClient, you will get full SQL statements on .NET Framework, so this will affect those scenarios as well, even if they were just recently possible.

@cijothomas
Copy link
Contributor

Got it. Thanks for clarifying.

@TimothyMothra
Copy link
Member Author

Just an update,

@ank3it is working on public announcements about this issue.
He posted an announcement here: microsoft/ApplicationInsights-Announcements#28
There will be an official blog post soon.

I'm working on the release and this will be published to NuGet this week. :)

@TimothyMothra
Copy link
Member Author

TODO:
Need to follow up with Attach Teams (App Service and Functions)

  • need to update to our SDK v2.14
  • will need a config change (opt-in)
  • need to update SqlClient dependency

@TimothyMothra TimothyMothra modified the milestones: 2.14, 2.15 Apr 30, 2020
@TimothyMothra TimothyMothra modified the milestones: 2.15, 2.14 Apr 30, 2020
@TimothyMothra TimothyMothra reopened this May 8, 2020
@TimothyMothra
Copy link
Member Author

Reopening this.
I think we need to update this page has well: https://docs.microsoft.com/azure/azure-monitor/app/asp-net-dependencies

@cijothomas, @ank3it lets discuss in our next standup

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants