For many organizations, the countdown has started. As of this writing, there are 233 days left until GDPR goes into effect. When you take into account the time it’s going to take to find and purchase a platform to achieve compliance, you’re looking at a significant difference in the time left to fully implement that solution. Can you afford to risk it?
We’ve already highlighted the 10 measures to GDPR compliance and have dived into how governed data lakes can help you on the road to compliance. You’ve done the research, you know your data, now the trick is finding a solution that can be implemented before the deadline hits. Based on your process, this might take longer than you think.
Deployment state or size doesn’t matter
Regardless of what comprises your big data ecosystem today - be it a data lake, data swamp, RDBMS, EDW, or other variation - you need a solution that can be implemented quickly. The solution should also be able to ingest all past, present, and future data while applying metadata tags to it...fast. Especially since metadata is the key to GDPR compliance. Every little bit of time matters when you realize just how little is left until that May deadline for compliance.
All pieces needed for GDPR Compliance
Tracking data lineage, managing the data lifecycle, and monitoring personal identifiable information are all major aspects of GDPR compliance. Wouldn’t it be great to have a solution with these capabilities, and then some? When you start to think of a data lake as more than a simple repository of data and understand the possibilities that can be gained by a management platform, then you will see just how perfectly suited a data lake is for GDPR. We've highlighted a checklist below that should help to show where a technology can help or where a person/process should be put in place.
About the AuthorMore Content by Brett Carpenter