Two-tier access to a lookup table is the method of choice when your replacement values must come from a specific data range.
Before a lookup table is set up, some thoughts must be given to the method you’ll use for accessing the data lookup table and how replacement rows are retrieved.
As long as testers are humans, they’ll prefer working with real names. This brings us to data translation (a.k.a. data lookup), another commonly used data disguise technique.
In light of the ensuing General Data Protection Regulation (GDPR), let’s have a look at common data disguise techniques, taking a closer look at one in particular later on.
The end users of disguised data—the testers—in a test data privacy project typically have two objections to how pseudonymization affects test data quality. The first objection is easily handled, but the other must be delicately approached with the right solution.
Test environments are vulnerable against GDPR legislation, and therefore, action must be taken to desensitize test data and improve data protection. More than likely, a lot of IT organizations need to be thinking of how to start a test data privacy project.