20.01.2015 Views

1ihHZ6h

1ihHZ6h

1ihHZ6h

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Legal Implications of Big Data: A Primer | David Navetta<br />

of Big Data practices, specifically where the collection and<br />

aggregation of seemingly harmless data about a person can<br />

be used to reveal sensitive information (e.g., health status,<br />

sexual orientation, and financial status).<br />

Anonymization and Big Data<br />

One technique for mitigating privacy-related risks associated<br />

with Big Data is de-identification or anonymization. 17 Data<br />

sets that are de-identified have had key information stripped<br />

away in order to prevent others from individually identifying<br />

the persons to whom the data set relates. This technique<br />

allows organizations to work with Big Data sets while mitigating<br />

privacy concerns, and has been used in many realms,<br />

including health care, banking and finance, and online advertising.<br />

In fact, many regulatory regimes recognize the concept of<br />

de-identified personal information. Under regulations promulgated<br />

pursuant to Gramm-Leach-Bliley 18 (regulating the<br />

privacy and security of financial data) “personally identifiable<br />

financial information” does not include information that<br />

does not identify a consumer “such as aggregate information<br />

or blind data that does not contain personal identifiers such<br />

as account numbers, names, or addresses.” 19 The Office for<br />

Civil Rights of the Department of Health and Human Services<br />

has issued extensive guidance concerning de-identification<br />

of health data, and sets forth two methods to achieve<br />

de-identification under HIPAA: expert determination and<br />

“safe harbor” de-identification (which involves removing<br />

eighteen types of identifiers from health data). 20 Under European<br />

data protection laws, to achieve legally permissible<br />

de-identification, “anonymization of data should exclude any<br />

possibility of individuals to be identified, even by combining<br />

anonymized information.” 21<br />

However, organizations relying on de-identification to circumvent<br />

privacy issues (and liability) must proceed carefully.<br />

If de-identification is not performed properly, it may be possible<br />

to re-identify individuals in an anonymized data set.<br />

There have been several real-life instances where re-identification<br />

has occurred, and researchers have also been able to<br />

demonstrate methods for identifying individuals from data<br />

that appeared anonymous on its face.<br />

In one infamous example, as part of a contest to create a better<br />

movie recommendation engine, Netflix released an anonymized<br />

data set containing the movie rental histories of approximately<br />

480,000 of its customers. Researchers established<br />

that they could re-identify some of the Netflix customers at<br />

issue by accessing and analyzing publicly available information<br />

concerning movie ratings performed by such custom-<br />

17 See http://en.wikipedia.org/wiki/De-identification.<br />

18 Gramm-Leach-Bliley Act of 1999, Pub. L. No. 106-102, 113 Stat. 1338 (codified as<br />

amended in scattered sections of 12 and 15 U.S.C. (2008)).<br />

19 See 17 CFR PART 248.<br />

20 See Guidance Regarding Methods for De-identification of Protected Health<br />

Information in Accordance with the Health Insurance Portability and Accountability<br />

Act (HIPAA) Privacy Rule, http://www.hhs.gov/ocr/privacy/hipaa/understanding/<br />

coveredentities/De-identification/hhs_deid_guidance.pdf.<br />

21 European Union Directive 95/46/EC.<br />

ers. 22 The Netflix contest eventually led to a lawsuit 23 against<br />

the company and regulatory scrutiny from the Federal Trade<br />

Commission. In another example, a researcher showed how<br />

she could re-identify persons with data in an anonymous<br />

health care data base by using publicly available voter records<br />

(in this case she was able to re-identify the information of the<br />

governor of Massachusetts). 24<br />

The risk of re-identification of Big Data sets using contextual<br />

“micro data” is a significant concern for organizations work-<br />

22 See Robust De-anonymization of Large Data sets (How to Break Anonymity of the<br />

Netflix Prize Data set) http://arxiv.org/PS_cache/cs/pdf/0610/0610105v2.pdf. The<br />

Netflix contest eventually lead to a lawsuit against the company and regulatory<br />

scrutiny by the Federal Trade Commission.<br />

23 See http://www.wired.com/images_blogs/threatlevel/2009/12/doe-v-netflix.pdf.<br />

24 See http://www.cs.duke.edu/~ashwin/pubs/BigPrivacyACMXRDS_final.<br />

pdf.<br />

The ISSA Web Conferences bring together ISSA<br />

members from around the world to share leading<br />

industry presentations and answer members’<br />

questions. Each event is designed to address the timely<br />

needs of our members through a live, online event and a<br />

subsequent recorded version for on-demand viewing.<br />

All content is developed by the ISSA Web Conference<br />

Committee. CPE credit available: ISSA members will be<br />

eligible for a certificate of attendance, after successful<br />

completion of a post-event quiz, to submit CPE credits for<br />

various certifications.<br />

Legislative Landscape<br />

2-Hour Live Event: March 26, 2013<br />

9am US Pacific/12pm US Eastern/5pm London<br />

Generously supported by Venafi.<br />

Increasingly legislation and regulation are becoming extremely<br />

important drivers for what information security<br />

professionals have to do, and the pace of delivery seems to<br />

be increasing wherever you work in the world today. What<br />

impacts will recently enabled, pending, and possible future<br />

legislation and regulation have on organizations and<br />

individuals and their approaches to what and how they do<br />

information security How do we prioritize what is most<br />

important What can we do to make compliance easier<br />

How do we get our policies aligned with the differing<br />

regulatory environments across different jurisdictions<br />

How do we deal with export controls (software and information)<br />

In some cases the question might be “How do<br />

we stay out of jail” Join our industry experts to get their<br />

views on this topic and the questions around it.<br />

Click here to register or here for more information.<br />

Visit https://www.issa.org/page=WebConferences<br />

for information on our 2013 schedule.<br />

18 – ISSA Journal | March 2013<br />

©2013 ISSA • www.issa.org • editor@issa.org • All rights reserved.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!