Skip to content

Latest commit

 

History

History
27 lines (17 loc) · 1.67 KB

05-data-masking.md

File metadata and controls

27 lines (17 loc) · 1.67 KB

Challenge 5: Mask Data for Privacy

< Previous Challenge - Home - Next Challenge >

Introduction

My team says that I don't give them enough privacy...

...at least that's what their sent emails say.

Description

The powerlifting event data contains participants first and last names. This falls within the terms of use for the current data set. However, the federation is planning some data analysis and data sharing initiatives that may require limiting the use of identifiying information.

As a trial of capabilities, the data privacy team has asked you to implement masking of first and last names.

The suggested masking should correctly show the first two characters of the foirst and last name. All subsequent characters should be replaced with an "x".

Success Criteria

  • Modified your solution so that any user queries against the data store return masked values for First and Last name. This should apply to all user queries whether via reporting tool or direct SQL queries.
  • Shown how you would grant specific users or user groups the ability to bypass the masking and see the full names.
  • Shown how you would turn the masking "on" or "off" altogether.
  • Shown the least privilege approach to allowing someone to manage masking (e.g., enforce or bypass) without granting them full database admin permissions.
  • Shown how a database admin could identify all the columns in the data store which currently have masking policies applied.

Learning Resources