On June 28, 2018, California adopted what is considered the strictest general privacy and data security law in the country. Called the California Consumer Privacy Act (CCPA), it will become effective on January 1, 2020. It’s been called a mini GDPR, but there are differences. Here’s how you can start preparing.
In just a few weeks on May 25, 2018, the deadline to be in compliance with GDPR will be here. For IT professionals who manage SaaS apps, GDPR compliance can be a little tricky. The sprawl of SaaS data can be hard to see and, in turn, protect. Here’s what you need to know to be GDPR compliant in the age of SaaS.
While GDPR does require you to report a data breach within 72 hours, that’s not the only rule IT needs to be aware of. GDPR also involves the newly defined role of a Data Protection Officer (do you need to appoint one?), and new responsibilities for data controllers vs. data processors (which one are you?). Find out the answers in this post. Plus, we’re including a 10-step checklist to get you jump-started on your path to GDPR compliance.
Did you know that under GDPR, users can request their data to be erased (aka be forgotten)? What kind of data does this apply to, and how can IT prepare for this? In Part Two of our series, our data privacy expert dives into three critical GDPR concepts that IT needs to be aware of: the right to be forgotten, consent, and data portability. All three elements affect IT’s responsibilities. This post covers what this means for IT and what their next steps should be.
GDPR will go into effect in less than seven months. Are you prepared? We’re kicking off a three-part series that covers everything IT needs to know about GDPR. In this first post, a data privacy expert explains 11 key concepts and why you need to starting preparing now.
