Data Masking for MongoDB is the data masking tool in Studio 3T Ultimate that lets you obfuscate collections on a field level. Try it for free here.
Data masking, obfuscation, or anonymization is required when certain personally identifiable information (PII) or other sensitive data must be kept private.
This requirement arises to comply with common data protection regulations such as:
- General Data Protection Regulation (GDPR) – EU
- Payment Card Industry (PCI) – Global
- Health Insurance Portability & Accountability Act (HIPAA) – USA
- Sarbanes-Oxley Act (SOX) – USA
- Telecommunications Bill – UK
Data Masking for MongoDB provides a static way of data obfuscation.
You can apply a data masking technique to each field in a source collection, and choose whether to overwrite the source collection or export the masked documents to a new target collection.
1. Launch Studio 3T.
2. Connect to a MongoDB instance containing the collection you want to mask.
3. Choose the collection from the Connection Tree.
4. With the collection selected (e.g.
customers), open Data Masking by clicking on the icon in the toolbar, or by right-clicking on the collection and choosing Mask Collection.
5. A new Data Masking tab will open with two sub-tabs: Data Masking tutorial and Overview.
Studio 3T will automatically create a data masking unit for the collection in the Overview tab.
Each data masking unit corresponds to a collection to be obfuscated.
6. (Optional). Choose the source and/or target connection in the Overview tab. Selecting Change source or Change target will open the Connection Manager window. The default configurations are the current working connection.
7. Double-click on the unit. This will open a separate Data Masking Unit where the field-level data masking configuration takes place.
The source collection is the collection you’ve chosen – or dragged – from the Connection Tree.
Click on Change Source to switch to a different collection within your connection. You have the option to retain the current data masking unit configuration or to create a new default configuration.
The target collection will be automatically set to
<<source_collection_name>>_masked, in the same database where the source collection is located.
To change the target collection at any time, click on Change Target.
Choose an existing collection from the list of databases in your connection, then click OK.
Click on the target database from the tree, click on the Add new collection button, type the new collection name, and click OK.
It is also possible to overwrite the source collection instead of choosing a target collection.
Click on Click here to overwrite source. Note that overwriting the source will overwrite the original documents in place and masking the
_id is disabled.
You will find all the fields in your source collection in the Mapping Tree section.
Choose a field from the Mapping Tree and click on the Edit mask button. Alternatively, right-click on a field and choose Edit mask.
The Edit Field Mapping window will open.
From here, you can choose the data masking technique to apply to any given field, depending on its type.
- Not masked*
- Null out*
- Exclude field*
*These three data masking techniques are the only options for Binary, Regex, Reference, Code, Min key, Max key, Mixed, Symbol, Timestamp, Undefined, and Unknown types.
- Show only first or last characters
- Mask entire string
- Mask substrings matching regex
- Scramble characters
- Replace entire field with a fixed string
Includes Double, Int32, Int64, and Decimal128 types.
- Substitute value with fixed number
- Add percentage to number
- Subtract percentage from number
- Substitute with random date and time
- Substitute with fixed date and time
- Empty contents of the array
- Negate boolean value
- Substitute with fixed boolean value
- Substitute with new ObjectId
The JSON Preview tab dynamically updates as you apply data masking methods, so you can preview the documents in the target collection or the overwritten source collection.
Next to the JSON Preview tab you’ll find an Exception Logs tab, where you’ll find any exceptions thrown during the data masking configuration.
Exceptions can arise, for example, when two types are detected for the same field in the initial scan, if only two characters are detected in a document but you’ve set a rule to show the first three characters, or if you have chosen to be warned in the Edit Field Mapping dialog for a particular field.
The History tab tracks all changes made to the source collection.
You can add more units by dragging and dropping collections from the Connection Tree to the Overview tab, or by clicking on Add unit from the toolbar.
A window will open where you can choose another source collection (
housing below) from the tree. Click OK.
The new data masking unit will appear in the Overview tab and open a separate Data Masking Unit tab. Repeat the field-level configuration as needed.
From the Overview tab, double-click on the data masking unit.
You can also right-click on the unit and choose Edit selected unit, or select it and click on Edit unit in the toolbar.
With a unit tab open, click on Remove unit in the toolbar.
Alternatively from the Overview tab, select the unit to be removed and either click on Remove unit in the toolbar or right-click and choose Remove data masking unit.
In the Overview tab, check or uncheck the units. Alternatively, right-click on a unit and choose Enable unit or Disable unit (depending on its state).
Once the changes look good in preview, you can choose to execute all units or only the enabled units (in the Overview tab).
Click on either the Execute all units or Execute enabled units button in the toolbar. You will be prompted if you’d like to continue, then click OK.
You can track the progress of the data masking job in the Operations panel, on the bottom-left.
Once the data masking job has been run, you will also see the masked collection (e.g.
customers_masked) in the target database.
Open any data masking unit and you’ll find the Mapping Tree toolbar, which provides these options:
Reset configuration – Click on Reset Configuration to either clear the current configuration and restore to the default setting (fields won’t be masked), or rescan the collection to detect any new fields in the documents.
Data Masking scans the last 50 documents of a collection by default. You can adjust the limit as needed.
Most of these toolbar options are also available by right-clicking on a field.
Edit mask – Edit the mask applied to the selected field.
Remove mask – Removes the mask from the data masking configuration, not the field.
Add sibling – Manually adds a sibling field to the selected field. This is handy option if you know precisely which fields are new to the collection – instead of doing a collection rescan – or for adding a field back in the configuration.
Add child – Manually adds a child if an array is selected, or the document.
Move up/down (arrows) – Move a selected rule up and down.
Undo and Redo – Undo and redo changes.
Dropdown menu – Handy for showing all, only masked, or only unmasked fields.
Data Masking integrates with two other features – Tasks and Task Scheduler – so that you can save data masking jobs as tasks.
Click on Save task (as) to save the job as a task.
Name the task. Then, click OK.
This saves the task in the Task Viewer, from which you can choose to schedule, unschedule, edit, clone, delete, add, and execute tasks.
You can also specify data masking rules when using our Export Wizard tool. You can export collections, views, queries, query results, or specific documents to CSV, JSON, BSON/mongodump, SQL, or another collection.
On the Export Wizard tab, scroll down to the Data Masking subsection and click Open field masking editor to begin configuring your data masking rules. The original data source won’t be overwritten.