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.
The EU General Data Protection Regulation legislation has been published in the Official Journal, making it a valid law in all 28 EU countries, and it’s coming into full force two years from today on May 25, 2018.
Until recently, data controllers maintained sole responsibility for upholding EU data protection laws, and made sure data processors they partnered with followed suit. However, under the EU’s newly adopted GDPR, data processors will no longer be free of liability for breaking data privacy laws, and will share with data controllers the onus of data protection for EU citizens.
The GDPR is making data protection more complex for companies. The coding of data masking rules for each and every column (field) is a redundant task. Data Elements solves this problem by reducing the complexity and tedium involved.
Recently, the EU Parliament adopted the General Data Protection Regulation (GDPR) legislation. Apart from losing credibility, companies failing to comply with the GDPR will face fines up to €20 million or 4 percent of annual worldwide turnover—whichever is greater.
If any real personal data is used for testing, it's high time to start protecting it with a test data privacy project to ensure compliance with the existing as well as new EU regulations. There is absolutely no excuse for continuing to use unmasked customer data in testing projects, and those that continue to do so will have nowhere left to hide when the EU legislators come calling.