Skip to content

Commit a0cb564

Browse files
craigg-msftcraigg-msft
committed
bulk of initial draft
1 parent 800416a commit a0cb564

1 file changed

Lines changed: 77 additions & 13 deletions

File tree

‎docs/sql-server/data-classification.md‎

Lines changed: 77 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -21,18 +21,6 @@ ms.workload: "Active"
2121
# SQL Server Documentation
2222
[!INCLUDE[appliesto-ss-xxxx-xxxx-xxx-md](../includes/appliesto-ss-xxxx-xxxx-xxx-md.md)]
2323

24-
25-
|Data Category |Definition |Examples |Details |
26-
|---------|---------|---------|---------|
27-
|Access Control |Credential-related information used to secure logins, users, or accounts within a SQL Server installation |- Passwords<br>- certificates | |
28-
|Row2 | | | |
29-
|Row3 | | | |
30-
|Row4 | | | |
31-
|Row5 | | | |
32-
|Row6 | | | |
33-
|Row7 | | | |
34-
|Row8 | | | |
35-
3624
## Access Control
3725
Credential-related information used to secure logins, users, or accounts within a SQL Server installation.
3826
### Examples
@@ -47,7 +35,83 @@ Credential-related information used to secure logins, users, or accounts within
4735
|Crash Dumps may contain Access Control Data. |NA |Crash Dumps: Maximum 30 days. |
4836
|These credentials never leave the user machine via User Feedback unless Customer injects it manually |Limit to MSFT internal with no third party access. |User Feedback: Max 1 year |
4937
|
38+
## Customer Content
39+
Data stored within user tables, directly or indirectly, including statistics or user literals within query texts that might be stored within user tables.
40+
41+
### Examples
42+
- Data values stored within the rows of any user table
43+
- Statistics objects containing copies of values within the rows of any user table
44+
- Query texts containing literal values
45+
46+
### Permitted Usage Scenarios
47+
|Scenario |Access Restrictions |Retention Requirements |
48+
|---------|---------|---------|
49+
|This data does not leave the user machine via Usage Feedback. |N/A |N/A |
50+
|Crash Dumps may contain Customer Content and be emitted to Microsoft. |N/A |Crash Dumps: Max 30 days. |
51+
|Customers with their consent can send User Feedback that contain Customer Content to Microsoft. |Limit to MSFT internal with no third party access. Microsoft can expose the data to the original customer. |User Feedback: Max 1 year |
52+
53+
## End-User Identifiable Information (EUII)
54+
Data received from a user, or generated from their use of the product.
55+
- Linkable to an individual user
56+
- Does not contain content.
57+
58+
### Examples
59+
- Interface ID (Full IP address)
60+
- Machine Name
61+
- Login/User names
62+
- Local-part of e-mail address (joe@contoso.com)
63+
- Location Information
64+
- Customer Identification ID
65+
66+
### Permitted Usage Scenarios
67+
68+
|Scenario |Access Restrictions |Retention Requirements|
69+
|---------|---------|---------|
70+
|This data does not leave the user machine via Usage Feedback. |N/A |N/A |
71+
|Crash Dumps may contain EUII and be emitted to Microsoft. |N/A |Crash Dumps: Max 30 days |
72+
|Customer Identification ID may be emitted to Microsoft to deliver new hybrid and cloud features that the users have subscribed to. |N/A |Currently no such hybrid or cloud features exist.|
73+
|Customers with their consent can send User Feedback that contain Customer Content to Microsoft.|Limit to MSFT internal with no third party access. Microsoft can expose the data to the original customer. |User Feedback: Max 1 year |
74+
75+
## Internet-Based Services Data
76+
Data needed to provide Internet-based services per the SQL Server EULA.
77+
78+
### Examples
79+
- Computer Specification Information
80+
- Browser name/version
81+
- SQL Server version
82+
- Language Code
83+
- Partial IP Address
84+
- Map Data
85+
86+
|Scenario |Access Restrictions |Retention Requirements|
87+
|---------|---------|---------|
88+
|May be used by Microsoft to improve features and/or fix bugs in current features. |Limit to MSFT internal with no third party access. Microsoft can expose the data to the original customer (dashboards, etc.) |Min 90 days | Max 3 years |
89+
|Customers with their consent can send User Feedback that contain Customer Content to Microsoft. |Limit to MSFT internal with no third party access. |Customers with their consent can send User Feedback that contain Customer Content to Microsoft. |
90+
|Power View and SQL Reporting Services Map Item(s) may send data for use of Bing Maps. |Limit to session data |- |
91+
92+
## System Metadata
93+
Data generated in the course of running the server. It does not contain Customer Content.
94+
95+
### Examples
96+
The following are System Metadata when devoid of Customer Content/Access Control/EUII:
97+
- Database GUID
98+
- Hash of Machine Name
99+
- Hash of Instance Name
100+
- Hash of Application Name
101+
- Behavioral/Usage Data
102+
- SQM Data / SQLCEIP Data
103+
- Server configuration data (settings of sp_configure, etc.)
104+
- Feature configuration data
105+
- Database names
106+
- Table, Column, Statistics Names
107+
- Event Names and Error Codes
50108

109+
|Scenario |Access Restrictions |Retention Requirements|
110+
|---------|---------|---------|
111+
|May be used by Microsoft to improve features and/or fix bugs in current features.|Limit to MSFT internal with no third party access. |Min 90 days - Max 3 years |
112+
|May be used to make suggestions to the customer (i.e., “Based on your usage of the product, please consider using feature X since it would perform better for you than what you are doing now”). |Microsoft can expose the data to the original customer (dashboards, etc.) |Customer Data Security Logs: Min 3 years - Max 6 years |
113+
May be used by Microsoft for future product planning. |Microsoft may share this information with other hardware and software vendors to improve how their products run with Microsoft software. |Min 90 days - Max 3 years|
114+
|May be used by Microsoft to provide cloud-based services based on emitted Usage Feedback (Example: a customer dashboard showing feature usage across all SQL Server installations in an organization) |Microsoft can expose the data to the original customer (dashboards, etc.) |Min 90 days - Max 3 years |
115+
|Customers with their consent can send User Feedback that contain Customer Content to Microsoft. |Limit to MSFT internal with no third party access. Microsoft can expose the data to the original customer. |User Feedback: Max 1 year |
51116

52-
53117
[!INCLUDE[get-help-options](../includes/paragraph-content/get-help-options.md)]

0 commit comments

Comments
 (0)