BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//hacksw/handcal//NONSGML v1.0//EN
METHOD:PUBLISH
BEGIN:VEVENT
DTSTAMP:20260606T104448Z
DESCRIPTION:Click for Latest Location Information: http://edw2020.dataversi
 ty.net/sessionPop.cfm?confid=128&proposalid=11615\n<p>Research shows that t
 raditional de-identification of data is not working as expected.&nbsp;Curre
 nt research shows that a data set with 15 demographic attributes can make 9
 9.98% of the state of Massachusetts unique. In smaller areas it is,&nbsp;of
  course,&nbsp;much less.&nbsp;Examples of re-identified data include Netfli
 x in 2008 and data leaked to the public, as well as&nbsp;home addresses of 
 New York taxi drivers from an anonymous data set of individual trips in the
  city.&nbsp;This presentation will detail exactly what GDPR and CCPA requir
 e in data protection and the shortcomings of some current de-identification
  techniques.&nbsp;Additionally covered will be techniques to properly ident
 ify data,&nbsp;which include purposely fuzzing data so that data reported i
 s not actually accurate.&nbsp;The data would be &quot;skewed&quot; in a sta
 ndard way.&nbsp;Other options include encryption techniques where the data 
 cannot be decrypted except by the owner.&nbsp;&nbsp;</p>\n<p>Attendees will
  learn:</p>\n\n	Why and how data is re-identified\n
 What GDPR and CCPA require\n	Examples of re-identification\n
 Best solutions to properly de-identify data\n
 Companies that are doing a better job of de-identification of data\n\n
DTSTART:20200325T083000
SUMMARY:Why "De-Identification" Will NOT Satisfy GDPR and CCPA Solutions
DTEND:20200325T092959
LOCATION: See Description
END:VEVENT
END:VCALENDAR