Product News System administration

Brightspace PII Data Anonymizer - FAQ

This article answers basic questions about the Brightspace PII Data Anonymizer.

What is the Brightspace PII Data Anonymizer?

The Brightspace PII Data Anonymizer (Anonymizer) replaces user PII in the LMS using various definitions, such as replacing usernames with newly generated GUIDs. The process is a mix of pseudonymization, setting blank values and nulling personal identifiable information

Anonymizer should not be run on production sites.

Can I request Data Anonymization without a Refresh?

Data Anonymization does not require a refresh; it is typically done with a Refresh.

A maintenance page is required for Anonymizer on the test site but will not have any impact on production; Data Anonymization can take several hours for large clients.

How do I undo the anonymization of a Brightspace Environment?

The non-production environment needs a Test Site Refresh to undo anonymization.

Which users are targeted by anonymizer?

By default, users who are not in Cascading roles will be anonymized. Users who are in Cascading roles will not be anonymized.Cascading roles are typically used for only Administrator, Developer or Support users.Please view About roles and permissions for additional information about roles.

If specific roles should be either targeted or excluded, either the exact role names or role ids must be provided along with the request.

The following non-cascading tool roles are excluded from anonymizer.→ [LTI Advantage User], [SIS Integration User], [SIS Integration], [CourseCatalog], [D2LMonitor]

What comes with the Default Data Anonymizer?

The Default Anonymizer affects fundamental user PII and maintains user information for users in Cascading Roles or Tool Roles.

Expand the Spoiler for details.

Basic User Information

→ Both Legal and Preferred First Name and Last Name

→ Middle Name, Email Address and Username

User Profile Information

→ We anonymize the entire User Profile for all users

→ This includes Favorite Memories, Hobbies, Hometown, Nickname, Phone numbers, etc

Additional User Information

→ EmailSignature, GoogleUrl, FacebookUrl, LinkedInUrl, TwitterUrl and Local Password

IPSIS User Information

→ Clear user relationship with exchange and sharepoint services.

→ Replace IM User Identifier with random GUID

User Contact Information

→ We clear Contact Info

→ Address, Phone Numbers, Websites, Email Address, etc.

→ ePortfolio objects are dropped

User Contacts

→ We clear the User's Contact lists

→ Address, Phone Numbers, Websites, Email Address, etc

User Login Attempts

→ The originating IP Address set to 0.0.0.0

→ Username is set to a random GUID

Email

→ We anonymize all email in the ILP for all users including the Cascading and Tool users

→ This includes To, From, ReplyTo, CC, BCC, Title, Body and Attachments

How did all the student users get back in the ILP the day after the anonymizer?

Test Site User Integrations (SIS/IPSIS/Banner) can either create duplicate or update anonymized users if they are setup to use a strict integration side ownership of users.

It is important that you tune your Test Site User Integrations to not fix broken users if you want an anonymization run.

How do I get additional Tools Anonymized?

There are more than 10,000 points in the ILP where anonymization is possible. It is possible to over-anonymize an ILP to the point where test isn’t a useful environment.

An IC engagement, including an initial commit for multiple refreshes in the same week, to tune the anonymizer configuration to the unique requirements. The anonymizer config will be preserved and can be used on every refresh that you request going forward.