Executive interview: Stuart Tarmy on a technical hurdles of GDPR compliance

“For example, If we need to strengthen Bill’s personal information, we need to know everywhere Bill’s information is kept,” says Tarmy. “From a GDPR perspective, it’s critical to brand this documented data. Clearly, this means a information insurance officer obliged for GDPR correspondence needs to know where a information relating to Bill is located.

“The information insurance officers will have to yield reports to contend they know where all is,” he says.

Here lies a large plea for standard enterprises. “This information could be contained in undocumented siloes or bequest systems. If we have worldwide IT systems, we need to go to all of them and opposite all a platforms a information could reside in,” says Tarmy.

He argues that partial of a problem is routine and partial is technological, and ideally companies would essay to have some form of master data, with a singular chronicle of a truth, as in one record for Bill.

But in Tarmy’s experience, while all companies will contend they have a golden source, a problem is that opposite departments will wish to cgange that singular version. It might seem ideally reasonable to bucket a patron database into Salesforce or to have another duplicate in a billing systems, or achievement might need a possess copy.

“If we afterwards call support to change your address, a information is no longer consistent,” he says. One of a issues confronting companies going by a GDPR correspondence programme is to brand all a surplus information they have.

For Tarmy, GDPR is a wake-up call to IT to modernize bequest and siloed systems. “GDPR offers outrageous advantages for upkeep and modernisation by ensuring information is kept adult to date,” he says.

It starts with bargain information flow. “You need to follow everywhere personal information exists,” says Tarmy. “Only afterwards can we figure out all a databases being used, and so yield a 360-degree viewpoint of a customer.”

This is what Io-Tahoe effectively does in a program as a use (SaaS) product. It ingests all constructional information and analyses it regulating appurtenance learning. “In a product we have a judgment of information excess – to brand all a sources of information that demeanour similar,” he says.

Most experts determine that GDPR needs to be driven from a really tip of a organisation, though Tarmy sees opportunities to adopt best practices from a bottom up, such as selecting to standardize on a singular database on a project-by-project basis. New applications will afterwards during slightest be easier to conduct from a GDPR perspective.