<?xml version="1.0" encoding="UTF-8"?> <rss
version="2.0"
xmlns:content="http://purl.org/rss/1.0/modules/content/"
xmlns:wfw="http://wellformedweb.org/CommentAPI/"
xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:atom="http://www.w3.org/2005/Atom"
xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
><channel><title>CIPP Guide &#187; Surveillance</title> <atom:link href="http://www.cippguide.org/tag/surveillance/feed/" rel="self" type="application/rss+xml" /><link>https://www.cippguide.org</link> <description>Your Guide to the CIPP</description> <lastBuildDate>Sat, 11 Feb 2012 07:47:27 +0000</lastBuildDate> <language>en</language> <sy:updatePeriod>hourly</sy:updatePeriod> <sy:updateFrequency>1</sy:updateFrequency> <generator>http://wordpress.org/?v=3.3.1</generator> <item><title>CALEA: Increasing Government Surveillance, Limiting Technological Innovation</title><link>https://www.cippguide.org/2012/01/19/calea-increasing-government-surveillance-limiting-technological-innovation/</link> <comments>https://www.cippguide.org/2012/01/19/calea-increasing-government-surveillance-limiting-technological-innovation/#comments</comments> <pubDate>Thu, 19 Jan 2012 12:00:57 +0000</pubDate> <dc:creator>hannah</dc:creator> <category><![CDATA[Privacy]]></category> <category><![CDATA[CALEA]]></category> <category><![CDATA[FCC]]></category> <category><![CDATA[Surveillance]]></category> <category><![CDATA[wiretapping]]></category><guid
isPermaLink="false">https://www.cippguide.org/?p=2812</guid> <description><![CDATA[This article takes a look at the Communications Assistance for Law Enforcement Act (CALEA), which was passed in 1994 to facilitate law enforcement authorities’ wiretapping of digital telephone networks. In 2004, the FCC suggested substantial expansions in the scope of the CALEA in its Notice of Proposed Rulemaking (NPRM). In August 2005, the FCC’s Final Rule expanded the CALEA to include Internet broadband and VoIP providers. This article also explores privacy watchdogs’ criticism of government surveillance [...]]]></description> <content:encoded><![CDATA[<p>Since its enactment in 1994, privacy rights experts and watchdogs have been wary of the <a
href="http://cippguide.org/tag/CALEA/">Communications Assistance for Law Enforcement Act</a> (CALEA). This article explores the history of the CALEA, how it has evolved over the years and some privacy issues surrounding wiretapping and other forms of surveillance.</p><p><strong>Background</strong></p><p><a
href="http://epic.org/privacy/wiretap/calea/calea_law.html">CALEA was passed in 1994</a> in order to facilitate law enforcement authorities’ wiretapping of digital telephone networks. It was the first piece of legislation in history that required telecommunications companies to modify their equipment in order to facilitate government surveillance. The FBI originally proposed the CALEA in 1992. This proposal was broadly inclusive – for instance, computer networks would have been part of this Act, in the name of government surveillance.</p><p>The CALEA essentially forced telephone companies to redesign their architectures in order to facilitate wiretapping. Notably, the CALEA did not regulate data traveling over the internet.</p><p>According to privacy watchdogs, wiretapping of suspected criminal activity by law enforcement agencies can rapidly degenerate into suspicionless monitoring of the general public, which violates the <a
href="http://en.wikipedia.org/wiki/Fourth_Amendment_to_the_United_States_Constitution">Fourth Amendment</a>.</p><p><a
href="http://www.privacyrights.org/fs/fs9-wrtp.htm">According to the Privacy Rights Clearinghouse</a>, “Wiretapping is any interception of a telephone transmission by accessing the telephone signal itself.” Another related concept is ‘electronic eavesdropping,’ which is defined as “the use of an electronic transmitting or recording device to monitor conversations without the consent of the parties.”</p><p>Under US law, there are very few situations in which wiretaps are legal. However, technological improvements have made it increasingly easier to illegally wiretap communications.</p><p><strong>Evolution of CALEA</strong></p><p>In August 2004, the <a
href="https://www.cippguide.org/tag/fcc/">Federal Communications Commission</a> (FCC) released a <a
href="http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-04-187A1.pdf">Notice of Proposed Rule Making</a> (NPRM), which expanded the boundaries of CALEA by redefining what constitutes telephone service, concluding that broadband Internet access providers and managed VoIP systems substantially replace local exchanges and therefore are subject to the requirements of CALEA.</p><p>In August 2005, the FCC announced a Final Rule, which expanded CALEA to Internet broadband providers and certain VoIP providers.</p><p><strong>Critics Say…</strong></p><p>In response to the expanding reach of CALEA, the <a
href="https://www.eff.org/">Electronic Frontier Foundation</a> (EFF) has listed a number of objections and concerns. These are briefly summarized below.</p><ul><li><strong>Wiretapping Convenience</strong> – According to the EFF, wiretapping is already a relatively easy practice as is. Existing legislation already permits law enforcement agencies to place Internet users under surveillance, regardless of what programs or protocols being used to communicate. The reality is that most types of surveillance has gotten easier in this day and age.</li><li><strong>“Tappability Principle” is Problematic</strong> – The FBI suggested that if something is legally searchable sometimes, it should be physically searchable all the time (the “tappability principle”). However, this could lead to all individual phones having built-in bugs, leaving consumers to trust that the phone companies or law enforcement would not activate those bugs without a legitimate reason.</li><li><strong>Increased Costs for Services </strong>– Expanding CALEA in the manner suggested by the FCC’s NPRM would cause broadband providers to spend millions of dollars restructuring their network architectures and design and manufacture surveillance-friendly technologies. This would cause telecommunications bills to skyrocket. It would also eliminate privacy-friendly technologies from the marketplace.</li><li><strong>Takes a Toll on Innovation</strong> – CALEA compliance would significantly reduce the scope of technological research and development. It would also allow the FCC to have authority over a wider range of technologies. CALEA’s requirements might result in economic incentives for software developers to create new programs (e.g. email, IM programs) that are more surveillance-friendly. This would mean that innovators will need to work within the guidelines of CALEA’s surveillance.</li><li><strong>Phone Regulations are not Applicable</strong> – The NPRM assumes that regulations that apply within the phone network (a closed, insulated system) should be extended to the internet (an open, always-changing system). This could severely hamper technological development and innovation on the Internet, where new services and devices are being introduced all the time.</li><li><strong>Internet Insecurities</strong> – Unfortunately, many of the technologies that are used to create surveillance-friendly computer networks might increase the risk of attacks or breaches of personal data. Broadband service providers who must make their networks or applications more tappable end up introducing potential points of vulnerability into their system. Many users are unaware of this reality when they register for such services.</li></ul><p><strong>Surveillance-Industrial Complex</strong></p><p>Services that facilitate wiretapping, and the types of policies that are necessitated by such legislation as the CALEA essentially facilitates what the American Civil Liberties Union (ACLU) refers to as the <a
href="http://www.aclu.org/files/FilesPDFs/surveillance_report.pdf">surveillance-industrial complex</a>, which involves the integration of private individuals and organizations with a government-sanctioned surveillance network. Private entities motivated by profiting from surveillance activities have an incentive to lobby for increased government surveillance authority.</p><p>Regarding the CALEA, the ACLU <a
href="http://www.aclu.org/files/FilesPDFs/surveillance_report.pdf">comments</a>,</p><p>“Americans have long feared the specter of the government maintaining dossiers filled with information about the lives of individual, innocent citizens. Data retention, whether mandatory or de facto, achieves the same goal indirectly, by ensuring that information is stored by corporations – from where, as we have seen, it can easily be accessed by the authorities.”</p><p><strong>Summary </strong></p><p>This article takes a look at the Communications Assistance for Law Enforcement Act (CALEA), which was passed in 1994 to facilitate law enforcement authorities’ wiretapping of digital telephone networks. In 2004, the FCC suggested substantial expansions in the scope of the CALEA in its Notice of Proposed Rulemaking (NPRM). In August 2005, the FCC’s Final Rule expanded the CALEA to include Internet broadband and VoIP providers. This article also explores privacy watchdogs’ criticism of government surveillance expansion.</p><p><strong>CIPP Exam Preparation</strong></p><p>In preparation for the Certified Information Privacy Professional (CIPP) exam, a privacy professional should be comfortable with topics related to this post, including:</p><ul><li>Communications Assistance to Law Enforcement Act – CALEA (I.B.a.iii.3.)</li></ul> ]]></content:encoded> <wfw:commentRss>https://www.cippguide.org/2012/01/19/calea-increasing-government-surveillance-limiting-technological-innovation/feed/</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item><title>Senate Investigates Mobile Data Collection, Companies Respond to Consumer Fears</title><link>https://www.cippguide.org/2011/10/04/senate-investigates-mobile-data-collection-companies-respond-to-consumer-fears/</link> <comments>https://www.cippguide.org/2011/10/04/senate-investigates-mobile-data-collection-companies-respond-to-consumer-fears/#comments</comments> <pubDate>Tue, 04 Oct 2011 12:00:03 +0000</pubDate> <dc:creator>hannah</dc:creator> <category><![CDATA[Privacy]]></category> <category><![CDATA[data collection]]></category> <category><![CDATA[Do-Not-Track]]></category> <category><![CDATA[FTC]]></category> <category><![CDATA[GPS]]></category> <category><![CDATA[mobile devices]]></category> <category><![CDATA[regulators]]></category> <category><![CDATA[Senate]]></category> <category><![CDATA[SPI]]></category> <category><![CDATA[Surveillance]]></category><guid
isPermaLink="false">https://www.cippguide.org/?p=2591</guid> <description><![CDATA[On May 19, 2001, a US Senate subcommittee met to discuss "Consumer Privacy &#38; Protection in the Mobile Market Place." As mobile phones and location-based apps are becoming more ubiquitous, this has raised a number of consumer concerns regarding the amount and type of sensitive information that is being collected, stored and shared by developers and third-parties. [...]]]></description> <content:encoded><![CDATA[<p>Both US and European regulators alike are turning the focus to mobile technology, especially the collection of location-based data and other consumer behavioral information. An <a
href="http://www.mobileforum.com/blogs/26-000-people-stalked-using-gps-devices-year-2006-119">American statistic</a> revealed that over 26,000 adults were stalked annually through the use of <a
href="http://www.cippguide.org/tag/GPS/">GPS</a> devices, including those on mobile phones. This number is from 2006, and today there are three times as many smartphones in use.</p><p>On May 19, 2011, the <a
href="http://commerce.senate.gov/public/">US Senate Committee on Commerce, Science and Transportation</a> had a hearing that focused on “Consumer Privacy &amp; Protection in the Mobile Market Place.” Present were representatives from Google, Apple and Facebook, as well as David Vladeck, director of the Bureau of Consumer Protection of the <a
href="http://www.cippguide.org/tag/FTC/">Federal Trade Commission</a> (FTC).</p><p><strong>Voicing Concerns</strong></p><p>At the subcommittee hearing, Senator John Rockefeller <a
href="http://www.clickz.com/clickz/news/2072622/growing-scrutiny-mobile-collection">expressed concerns</a> about the amount of information mobile devices are actually able to collect about their owners. He demanded stronger controls over how and when such personal data is shared, saying, “As smartphones become more powerful, more personal information is being concentrated in one place. Consumers want to understand and have control of their personal information. ” Senator Rockefeller is the chairman of the US Senate Committee on Commerce, Science and Transportation.</p><p><a
href="http://abcnewsradioonline.com/politics-news/senate-subcommittee-investigates-mobile-safety-data-collecti.html">According to Senator Al Franken</a>, the chairman of the judiciary subcommittee on Privacy, Technology and the Law, “Consumers have a fundamental right to know what data is being collected about them. I also believe they have a right to decide whether or not they want to share that information and with who they want to share it and when.”</p><p>Jessica Rich from the FTC <a
href="http://www.pointofview.net/site/News2?page=NewsArticle&amp;id=17115&amp;news_iv_ctrl=1201">expressed worries</a> about mobile device safety, saying, “These concerns stem from the always-on, always-with-you personal nature of mobile devices.” She also pointed out the possible hazards of “invisible collection and sharing of data with multiple parties, the ability to track consumers – including children and teens – to their precise location.”</p><p><strong>Responding to the Fears</strong></p><p>In response to the increased concerns regarding mobile data collection, Catherine Novelli, Apple’s VP of worldwide government affairs explained that the company currently provides tools allowing customers to control the collection and use of data on its mobile devices, including location data. <a
href="http://crashcollective.com/uncategorized/growing-scrutiny-of-mobile-data-collection/">Novelli said</a>, “Apple does not track users’ locations – Apple has never done so and has no plans to ever do so.” However, the recent flurry of activity over the company’s iPhone and 3G-enabled iPads speak to the contrary.</p><p>Alan Davidson, Google’s director of public policy for the Americas <a
href="http://crashcollective.com/uncategorized/growing-scrutiny-of-mobile-data-collection/">responded</a> that Google supports the development of a legal privacy framework that ensures broad-based user trust and that will support continued innovation.</p><p>Bret Taylor, the Chief Technology Officer of Facebook, <a
href="http://crashcollective.com/uncategorized/growing-scrutiny-of-mobile-data-collection/">warned</a> that too much regulation may stifle innovation amongst mobile technology and service providers: “Adopting overly restrictive policies will prevent our social features from functioning in the way that individuals expect and demand.”</p><p><strong>FTC Suggestions</strong></p><p>In its statement to the subcommittee, the FTC suggested extending the application of its <a
href="http://www.ftc.gov/opa/2010/12/dnttestimony.shtm">Do-Not-Track mechanism</a>. Introduced in December 2010, the Do Not Track feature for internet browsers would allow users to opt out of sharing browsing data completely and protect their privacy. This suggestion was made in order to give end users increased control over the amount and type of personal data stored by companies, preventing the sharing of sensitive data with third parties, or the use of sensitive data against the individual’s wishes.</p><p>The FTC recommended that this Do-Not-Track mechanism should apply to mobile and desktop devices: “At least for purposes of web browsing, the issues surrounding implementation of Do Not Track are the same on mobile devices and desk top computers.” Currently, FTC staff is developing ways to implement Do Not Track mechanisms on mobile apps.</p><p><strong>Summary</strong></p><p>This article takes a look at the May 19, 2011 Senate Subcommittee hearing on “Consumer Privacy &amp; Protection in the Mobile Market Place.” As mobile phones and location-based apps are becoming more ubiquitous, this has raised a number of consumer concerns regarding the amount and type of sensitive information that is being collected, stored and shared by developers and third-parties. The subcommittee hearing was an opportunity for those on both sides of the debate to express their opinions. The FTC suggested extending the Do Not Track mechanism for web browsers to include mobile devices as well.</p><p><strong>CIPP Exam Preparation</strong></p><p>In preparation for the Certified Information Privacy Professional/Information Technology (CIPP/IT) exam, a privacy professional should be comfortable with topics related to this post, including:</p><ul><li>Sensitive Personal Information (SPI) (I.A.b.)</li><li>Data accountability (I.B.c.)</li><li>Consumer privacy concerns (II.A.a.)</li><li>Government and citizen surveillance (II.A.k.)</li><li>Social networking services (VI.C.)</li><li>Location-based services (VI.E.)</li></ul> ]]></content:encoded> <wfw:commentRss>https://www.cippguide.org/2011/10/04/senate-investigates-mobile-data-collection-companies-respond-to-consumer-fears/feed/</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item><title>Implementing the EU e-Privacy Directive: The Cookie Problem</title><link>https://www.cippguide.org/2011/04/12/implementing-the-eu-e-privacy-directive-the-cookie-problem/</link> <comments>https://www.cippguide.org/2011/04/12/implementing-the-eu-e-privacy-directive-the-cookie-problem/#comments</comments> <pubDate>Tue, 12 Apr 2011 12:00:44 +0000</pubDate> <dc:creator>hannah</dc:creator> <category><![CDATA[Privacy]]></category> <category><![CDATA[cookies]]></category> <category><![CDATA[EU]]></category> <category><![CDATA[EU e-Privacy Directive]]></category> <category><![CDATA[legislation]]></category> <category><![CDATA[online privacy]]></category> <category><![CDATA[Surveillance]]></category><guid
isPermaLink="false">https://www.cippguide.org/?p=2400</guid> <description><![CDATA[<p>This article explores the EU e-Privacy Directive, with a focus on the “Cookie Law,” which was passed late 2009. The Directive has yet to be fully implemented in all EU member states and the amendment of the “Cookie Law” has created additional roadblocks to harmonization of legislation across Europe.</p><p>Background: e-Privacy Directive
The European Commission’s Directive of Privacy and Electronic Communications 2002/58/EC (also referred to as the e-Privacy Directive) required that public communications providers (i.e. internet service providers and telecommunications companies) inform national regulatory authorities of any data security breach. Subscribers should also be notified if the personal data breach is likely [...]]]></description> <content:encoded><![CDATA[<p>This article explores the EU e-Privacy Directive, with a focus on the “Cookie Law,” which was passed late 2009. The Directive has yet to be fully implemented in all EU member states and the amendment of the “Cookie Law” has created additional roadblocks to harmonization of legislation across Europe.</p><p>Background: e-Privacy Directive<br
/> The European Commission’s <a
href="http://eur-lex.europa.eu/LexUriServ/LexUriServ.do?uri=OJ:L:2002:201:0037:0047:EN:PDF">Directive of Privacy and Electronic Communications 2002/58/EC</a> (also referred to as the e-Privacy Directive) required that public communications providers (i.e. internet service providers and telecommunications companies) inform national regulatory authorities of any data security breach. Subscribers should also be notified if the personal data breach is likely to adversely affect the personal data or the privacy of the subscriber. The deadline for member states to implement this Directive is May 25, 2011.</p><p>The Cookie Law<br
/> On November 9, 2009, the European Parliament made additions to the e-Privacy Directive, which included an effort to regulate <a
href="https://www.cippguide.org/tag/cookies/">online cookies</a>. According to the previous law, web sites were required to allow consumers to opt-out of cookies, typically by selecting a setting on their web browsers. A Parliament committee determined that the practice be reversed; users should be presented with the opportunity to opt in before cookies are placed on their computers.</p><p>Under the new addition, companies are required to secure consent from users before tracking files, such as online cookies, are placed on the users’ computers. This addition is commonly referred to as the “cookie law:”</p><p>“The new e-Privacy Directive will include a provision requiring the EU Member States to ensure that the storing of information, or the gaining of access to information already stored, in the terminal equipment of a subscriber or user is only allowed on condition that the subscriber or user concerned has given his or her consent, having been provided with clear and comprehensive information, in accordance with Directive 95/46/EC, inter alia about the purposes of the processing.”</p><p>Although it does not directly mention cookies, commenters point out that the wording includes cookies as well as any other technologies which may be used to track users’ behavior through their internet browsers.</p><p>Cookie Law Controversy<br
/> The Cookie Law applies to cookies that collect personal data. Some experts have pointed out that certain cookies are not covered by this consent requirement. According to data protection authorities, persistent cookies that contain a unique user ID would qualify as personal data, thus subject to applicable data protection regulations. However, there are other types of cookies that do not meet such criteria.</p><p>Another uncertainty regarding the Cookie Law is the process by which <a
href="https://www.cippguide.org/tag/consent/">consent </a>should be obtained. The statement does not mention prior consent, rather suggests that users are presented with an opportunity to refuse cookies before they are delivered to their computers. The means by which consent should be obtained has given rise to a series of discussions between internet service providers, privacy advocates, advertisers, law makers and EU member states.</p><p>It is unclear if “consent” means that users need to agree to cookies when setting up their web browsers, or if they must give unambiguous consent for each and every cookie. Others have interpreted “consent” to mean a standardized plan that allows users to view and opt-out of data collected about them through cookies.</p><p>Advertising Outcry<br
/> Europe’s online advertising industry currently generates US$20.12 billion in advertising spending annually. The initial idea that cookie placement needed the user’s prior consent concerned industry executives, who argued it would be a costly and disruptive practice. As a result, the requirement of “prior consent” was moved to an addendum.</p><p>Rather than recurring pop-up windows requesting consent, advertising executives suggested placing icons on internet ads that rely on tracking tools. Users can click on the icon to view what data is being collected about them, or to block any cookies.</p><p>Dutch Telecommunications Act<br
/> On November 3, 2010, an <a
href="https://zoek.officielebekendmakingen.nl/kst-32549-2.pdf">amendment </a>to the Dutch Telecommunications Act was submitted to the Dutch Parliament. This was an effort to implement the EU e-Privacy Directive.</p><p>The proposed Bill requires telecommunications and internet service providers to give notification of data security breaches involving personal data to the Dutch Telecom Authority. If individuals’ privacy is likely to be compromised in a breach, service providers would also be obliged to notify the appropriate individuals.<br
/> The proposed Bill also requires that consent be secured before the use of cookies, in particular, prior to the use of third party cookies that are designed to track individuals’ web browsing activities for behavioral advertising purposes. In response to confusion regarding unambiguous consent (i.e. whether or not consent was required for placing individual cookies), the Bill indicates that browser consent would be sufficient. However, browser consent may not be enough in all situations.</p><p>Summary<br
/> This article discusses the European Union’s e-Privacy Directive, also referred to as the Directive of Privacy and Electronic Communications 2002/58/EC. The Directive is a continuation of the EU Data Protection Directive and deals with data protection and privacy issues relating to digital technologies. The article takes a look at the “Cookie Law,” an amendment to the Directive that requires user consent before cookies are placed on users’ computers. This amendment has given rise to controversial discussions between internet service providers, privacy advocates, advertisers, law makers and EU member states. Finally, the article takes a look at how the elements of the e-Privacy Directive are being implemented in the legislation of member states.</p><p>CIPP Exam Preparation<br
/> In preparation for the Certification Foundation exam (Foundations) and the Certified Information Privacy Professional/Information Technology (CIPP/IT) exam, a privacy professional should be comfortable with topics related to this post, including:<br
/> •	Online Privacy – Online Identification Mechanisms – Cookies (Foundations; III.B.g.i.)<br
/> •	Privacy-Enhancing Technologies – Web Cookies (CIPP/IT; III.B.c.i.)<br
/> •	Privacy &amp; Data Protection Regulation – Europe (Foundations; I.F.b.ii.)</p><p><a
class="a2a_dd a2a_target addtoany_share_save" href="http://www.addtoany.com/share_save#url=https%3A%2F%2Fwww.cippguide.org%2F2011%2F04%2F12%2Fimplementing-the-eu-e-privacy-directive-the-cookie-problem%2F&amp;title=Implementing%20the%20EU%20e-Privacy%20Directive%3A%20The%20Cookie%20Problem" id="wpa2a_2"><img
src="https://www.cippguide.org/wp-content/plugins/add-to-any/share_save_171_16.png" width="171" height="16" alt="Share"/></a></p>]]></content:encoded> <wfw:commentRss>https://www.cippguide.org/2011/04/12/implementing-the-eu-e-privacy-directive-the-cookie-problem/feed/</wfw:commentRss> <slash:comments>1</slash:comments> </item> <item><title>Justice Department Pushes for Mandatory Data Retention</title><link>https://www.cippguide.org/2011/03/29/justice-department-pushes-for-mandatory-data-retention/</link> <comments>https://www.cippguide.org/2011/03/29/justice-department-pushes-for-mandatory-data-retention/#comments</comments> <pubDate>Tue, 29 Mar 2011 12:00:52 +0000</pubDate> <dc:creator>hannah</dc:creator> <category><![CDATA[Privacy]]></category> <category><![CDATA[data retention]]></category> <category><![CDATA[Department of Justice]]></category> <category><![CDATA[Do-Not-Track]]></category> <category><![CDATA[FTC]]></category> <category><![CDATA[Internet Service Provider]]></category> <category><![CDATA[ISP]]></category> <category><![CDATA[Surveillance]]></category><guid
isPermaLink="false">https://www.cippguide.org/?p=2451</guid> <description><![CDATA[On January 25, 2011, the US Department of Justice brought the issue of mandatory data retention to the House Subcommittee on Crime, Terrorism, and Homeland Security. Currently, there is no law requiring internet service providers (ISPs) to retain user data, and ISP retention practices are inconsistent in terms of type of data and retention period. Law enforcement authorities have long argued that mandatory data retention would advance criminal investigations, especially those dealing with child pornography and sexual predators. Critics argue that retention of user data would result in numerous privacy and freedom of speech [...]]]></description> <content:encoded><![CDATA[<h1><span
style="font-weight: normal; font-size: 13px;">In a House subcommittee hearing held January 25, 2011, the US <a
href="http://www.justice.gov/">Department of Justice</a> called for new legislation mandating internet service providers (ISPs) to retain customer usage data for up to two years. This has resulted in a number of concerns, ranging from individuals’ privacy worries, to ISP concerns regarding the storage of large amounts of data for long periods of time.</span></h1><h2>Crucial Evidence</h2><p>In his statement before the <a
href="http://judiciary.house.gov/about/subcrime.html">Subcommittee on Crime, Terrorism, and Homeland Security</a>, Jason Weinstein, deputy assistant attorney general at the Justice Department, <a
href="http://judiciary.house.gov/hearings/pdf/Weinstein01252011.pdf">pointed out</a> that retaining data from ISPs and cell phone service providers can help provide crucial evidence in cases “including child exploitation, violent crime, fraud, terrorism, public corruption, drug trafficking, online piracy, computer hacking, and other privacy crimes.”</p><p>According to Weinstein, many of the Justice Department’s current criminal investigations are being hindered by its inability to monitor and store the online activity of users. He provided numerous examples in which the retention policies of service providers were obstructing federal, state and local law enforcement investigations. Weinstein said, “These decisions by providers to delete records are rarely done out of a lack of desire to cooperate with law enforcement; rather, they are usually done out of an understandable desire to cut costs.  Some providers also seem to delete records out of a concern for customer privacy.”</p><h2>Current Practices</h2><p>At this point, ISPs are required to preserve usage data only at the request of law enforcement authorities. Many ISPs are also collecting and maintaining “non-content records,” for instance a subscriber’s login records, information on who is using their services and how. ISPs have widely varying policies and practices regarding the storage of non-content records. In some cases, it will be deleted within days, while others may retain the data for months. Weinstein would like to see this retention period standardized, so that authorities are guaranteed to be able to access such data, should they require it.</p><p>There is currently no law that requires ISPs to retain user data. However, the push for extensive data retention legislation is not a new issue. In the past, FBI director Robert Mueller requested that Congress consider such legislation for similar reasons.</p><h2>Critics Say…</h2><p>Undoubtedly, the January 25<sup>th</sup> hearing has brought to the surface a number of privacy and freedom of speech concerns. The notion of law enforcement authorities tracking and retaining large amounts of information on over 230 million Americans is an unacceptable outcome for many. This may significantly impact free and anonymous speech and will change how individuals use the internet.</p><p>Jim Harper, the director of information policy studies at the <a
href="http://www.cato.org/">Cato Institute</a>, commenting on the issue of mandatory data retention, says “I fail to see where the Fourth Amendment permits the government to require dragnet surveillance of Internet users.”</p><p>Another issue is that while the federal government is pushing for pro-privacy laws, it is also contradicting itself with anti-privacy laws, such as this data retention legislation. Recently, the <a
href="https://www.cippguide.org/2011/03/01/resisting-online-tracking-new-features-tools">FTC proposed</a> that browsers include Do-Not-Track features, which would help users ensure that their information is not being retained while they browse the internet. At the same time, the Justice Department has asked for more extensive retention laws, though the two are seemingly in conflict with each other.</p><p>According to John Morris, the general counsel for the Washington DC-based think-tank <a
href="http://www.cdt.org/">Center for Democracy and Technology</a>, the hearing does not necessarily mean that a data retention bill is on the way. It is also uncertain what kind of data ISPs would be expected to retain, or if other online services (e.g. e-mail providers) might be included in the new legislation. Morris said:</p><p>“In the best-case scenario, a data retention bill will only require ISPs to track and store Internet Protocol (IP) address allocation data to help law enforcement better link Internet use to specific users. In the worst-case scenario, it could require ISPs and all sorts of online service providers to store and track everything from IP addresses to source data involving e-mail, instant messaging (IM), social media interactions and Web sites visited.”</p><h3>Summary</h3><p>On January 25, 2011, the US Department of Justice brought the issue of mandatory data retention to the House Subcommittee on Crime, Terrorism, and Homeland Security. Currently, there is no law requiring internet service providers (ISPs) to retain user data, and ISP retention practices are inconsistent in terms of type of data and retention period. Law enforcement authorities have long argued that mandatory data retention would advance criminal investigations, especially those dealing with child pornography and sexual predators. Critics argue that retention of user data would result in numerous privacy and freedom of speech concerns.</p><h3>CIPP Exam Preparation</h3><p>In preparation for the Certified Information Privacy Professional/Information Technology (CIPP/IT) exam, a privacy professional should be comfortable with topics related to this post, including:</p><ul><li>Methods of Data Collection (I.B.a.)</li><li>Privacy Concerns – Consumer Perspective (II.A.a.)</li><li>Government and Citizen Surveillance (II.A.k.)</li><li>Privacy Expectations – Consumer Behaviors (II.B.a.)</li><li>Online Privacy (V.D.i.1.)</li></ul> ]]></content:encoded> <wfw:commentRss>https://www.cippguide.org/2011/03/29/justice-department-pushes-for-mandatory-data-retention/feed/</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item><title>Combatting Online Infringements &amp; Counterfeits Act</title><link>https://www.cippguide.org/2011/02/15/combatting-online-infringements-counterfeits-act-2/</link> <comments>https://www.cippguide.org/2011/02/15/combatting-online-infringements-counterfeits-act-2/#comments</comments> <pubDate>Tue, 15 Feb 2011 12:00:08 +0000</pubDate> <dc:creator>hannah</dc:creator> <category><![CDATA[Privacy]]></category> <category><![CDATA[COICA]]></category> <category><![CDATA[copyright]]></category> <category><![CDATA[DCMA]]></category> <category><![CDATA[DMCA]]></category> <category><![CDATA[legislation]]></category> <category><![CDATA[online privacy]]></category> <category><![CDATA[Surveillance]]></category><guid
isPermaLink="false">https://www.cippguide.org/?p=2407</guid> <description><![CDATA[<p>The US Combatting Online Infringements and Counterfeits Act (COICA) made headlines this fall as a censorship bill masquerading as a copyright infringement bill. This article explores the COICA, which aims to amend the United States Code by removing Internet sites that may be dedicated to, or involved with, infringing activities. The article also examines some potential repercussions and criticisms of the COICA, which have been raised by privacy activists and Internet experts.</p><p>What is COICA?
The Combatting Online Infringements and Counterfeits Act (COICA) refers to a potential Internet censorship bill that may be passed in the United States. While it appears to [...]]]></description> <content:encoded><![CDATA[<p>The US Combatting Online Infringements and Counterfeits Act (COICA) made headlines this fall as a censorship bill masquerading as a copyright infringement bill. This article explores the COICA, which aims to amend the United States Code by removing Internet sites that may be dedicated to, or involved with, infringing activities. The article also examines some potential repercussions and criticisms of the COICA, which have been raised by privacy activists and Internet experts.</p><p>What is COICA?<br
/> The <a
href="http://www.wired.com/images_blogs/threatlevel/2010/09/CombatingOnlineInfringementAndCounterfeitsAct1.pdf">Combatting Online Infringements and Counterfeits Act</a> (COICA) refers to a potential Internet censorship bill that may be passed in the United States. While it appears to be focused on copyright infringement issues, many critics argue that it could potentially silence political content as well.</p><p>Initially proposed by Democratic Senator Patrick Leahy, the cross-party supported COICA aims to provide the US Justice Department with the necessary tools to prevent online infringement. The objective of the bill is to create a blacklist of censored domains, through interference with the Internet’s <a
href="http://en.wikipedia.org/wiki/Domain_Name_System">DNS </a>(domain name system). Under the COICA, the Attorney General is permitted to ask the court to place any web site on the blacklist, as long as it can be proven that copyright infringement is central to the web site’s purpose.</p><p>Under the bill, two Internet blacklists would be published. Web sites appearing on the first list would receive a censorship court order from the Attorney General. These sites would have their domains blocked. Web sites appearing on the second list consist of a blacklist of domain names determined to be operating for infringement purposes, as determined by the Department of Justice. It is recommended that sites on this list are blocked and that Internet intermediaries and DNS operators blocking these domains should also receive legal immunity.<br
/> In cases where the registries or registrars are located outside of the US, the COICA gives the Attorney General the authority to serve the order to other third parties. These third parties may include Internet service providers, online ad network providers and payment processors.</p><p>Blacklisted<br
/> According to the Senate Judiciary Committee’s draft COICA bill, released in September 2010, there are a number of different types of web sites that would potentially be taken offline. These sites fall under the following categories:<br
/> • One-click hosting web sites<br
/> • MP3 blogs and mashup/remix music sites<br
/> • Sites discussing piracy<br
/> One-click hosting sites allow users to upload anything, unless <a
href="http://brainz.org/dmca-takedown-101/">DMCA takedown notices</a> are received. Their practices arguably balance copyright enforcement with user innovation. According to the draft COICA, the Department of Justice has the authority to determine if piracy is central to the purpose or functioning of the web sites. Such web sites would include: <a
href="http://www.mediafire.com/">MediaFire</a>, <a
href="http://www.dropbox.com/">Dropbox </a>and <a
href="http://rapidshare.com/">Rapidshare</a>.</p><p>MP3 blogs and mashup/remix sites have historically been involved in litigation for unauthorized sampling, though such uses are protected by the fair use doctrine. Observers are concerned that the Department of Justice may simply take down such sites in fear of complaints from the recording industry. Examples of this category of sites include: <a
href="http://hypem.com/">Hype Machine</a>, <a
href="http://www.mashuptown.com/">Mashup Town</a> and <a
href="http://soundcloud.com/">SoundCloud</a>.</p><p>The final category of targeted sites includes those discussing P2P technology and piracy in an intellectual or political manner. These sites typically link to tools and information related to file sharing, which may be reason enough for the sites to be taken offline, under the COICA. Critics are concerned that this would fundamentally violate the principles of the freedom of speech. Such sites include: <a
href="http://www.slyck.com/">Slyck</a>, <a
href="http://www.zeropaid.com/">ZeroPaid</a>, <a
href="http://www.p2pnet.net/">p2pnet</a>, <a
href="http://www.infoanarchy.org/en/Main_Page">InfoAnarchy </a>and <a
href="http://pirate-party.us/news.php">pirate-party.us</a>.</p><p>Critics say…<br
/> Prominent critics of the COICA, such as the <a
href="http://www.eff.org/work">Electronic Frontier Foundation</a> (EFF), argue that the bill would have a detrimental impact on a wide range of issues, including freedom of speech, internet architecture, copyright doctrine, foreign policy and more. In a recent analysis by the EFF legislative branch, a number of points were raised regarding the harm that the COICA would do. These issues are briefly explained below:</p><p>• <strong>Anti-innovation</strong>: The bill does not resolve the problem of un-compensated artists/creators. The EFF argues that Internet services such as Pandora, Amazon Music and YouTube facilitates a marketplace for digital business to grow. Other new online services are being developed to allow artists/creators to connect with their audiences and raise revenue. However, media-sharing platforms, which give rise to artistic creativity and collaboration, would violate the requirements of the COICA.</p><p>• <strong>Censorship</strong>: The authority to determine which web sites ought to be blacklisted and which ones are acceptable is dangerous territory. The COICA permits a broad, government-initiated, domain-wide authority to take down websites, which may result in mistakes and abuses, as have been perpetrated under the <a
href="http://www.copyright.gov/legislation/dmca.pdf">Digital Millennium Copyright Act</a> (DMCA).</p><p>• <strong>DNS Undermining</strong>: According to Internet engineers, the COICA has the potential to cause significant problems for the DNS. They anticipate that once the US government starts to control DNS infrastructure, much of the Internet may shift to different DNS mechanisms that are not located in the US.<br
/> This may result in inconsistencies between the current DNS hierarchy and the new alternative mechanisms. By using these offshore DNS mechanisms, data may have to travel long physical distances over the network before users can access it on their browsers. This could increase the cost of the Internet infrastructure by 20%. Furthermore, with the dependence on offshore DNS, it may become more difficult to maintain and secure these servers, leading to potential security threats and attacks.</p><p>• <strong>Unconstitutional</strong>: Unlike the DMCA, which gives copyright owners the right to remove their own copyrighted content from a website, the COICA permits everything on a particular domain to be taken offline. This constitutes a significant violation of the freedom of speech and could potentially threaten the innovation of new content.</p><p>By the end of September 2010, privacy activists successfully delayed the passing of the COICA. The bill was postponed before the Senate’s October recess, allowing more time for debate. This result was partially due to the involvement of key Internet scientists, engineers and citizens who publicized the bill and its potential repercussions.</p><p>Summary<br
/> This article looks at the COICA (Combatting Online Infringement and Counterfeits Act), which could grant the Attorney General the power to take down entire domains. The article explores the elements of the bill, which include the release of two separate Internet blacklists for websites deemed to be dedicated to, or engaged in, copyright-infringing activities. Under the bill, a number of different types of web sites could be taken down, including: one-click hosting web sites; MP3 blogs and mashup/remix music sites; and sites discussing piracy. Finally, the article provides a brief overview of some criticisms and concerns regarding the COICA, which have been raised by Internet experts and privacy rights activists in the US.</p><p>CIPP Exam Preparation<br
/> In preparation for the Certified Information Privacy Professional/US Government (CIPP/G) exam; the Certification Foundation (Foundations) exam and the Certified Information Privacy Professional/Information Technology (CIPP/IT) exam, a privacy professional should be comfortable with topics related to this post, including:<br
/> • US Public &amp; Private Sector Information Privacy Laws (CIPP/G; I.B.)<br
/> • Department of Justice (CIPP/G; II.B.f.iv.)<br
/> • Government and Citizen Surveillance (CIPP/IT; II.A.k.)<br
/> • Online Privacy Threats (Foundations; III.B.a.)</p><p><a
class="a2a_dd a2a_target addtoany_share_save" href="http://www.addtoany.com/share_save#url=https%3A%2F%2Fwww.cippguide.org%2F2011%2F02%2F15%2Fcombatting-online-infringements-counterfeits-act-2%2F&amp;title=Combatting%20Online%20Infringements%20%26amp%3B%20Counterfeits%20Act" id="wpa2a_4"><img
src="https://www.cippguide.org/wp-content/plugins/add-to-any/share_save_171_16.png" width="171" height="16" alt="Share"/></a></p>]]></content:encoded> <wfw:commentRss>https://www.cippguide.org/2011/02/15/combatting-online-infringements-counterfeits-act-2/feed/</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item><title>Ontario’s Privacy-Protective Facial Recognition System</title><link>https://www.cippguide.org/2011/01/18/ontario%e2%80%99s-privacy-protective-facial-recognition-system/</link> <comments>https://www.cippguide.org/2011/01/18/ontario%e2%80%99s-privacy-protective-facial-recognition-system/#comments</comments> <pubDate>Tue, 18 Jan 2011 17:00:32 +0000</pubDate> <dc:creator>hannah</dc:creator> <category><![CDATA[Privacy]]></category> <category><![CDATA[Authentication]]></category> <category><![CDATA[biometric]]></category> <category><![CDATA[Canada]]></category> <category><![CDATA[CIPP/C]]></category> <category><![CDATA[cryptography]]></category> <category><![CDATA[identification]]></category> <category><![CDATA[privacy commissioners]]></category> <category><![CDATA[Surveillance]]></category><guid
isPermaLink="false">https://www.cippguide.org/?p=2402</guid> <description><![CDATA[<p>Efficient and accurate authentication of individuals is a growing challenge across a number of sectors. There are currently three main forms of authentication, based on something you know, something you have and something you are. The third form is especially interesting in light of biometric technologies as a means of verification. This article explores some recent applications of biometrics in Ontario.</p><p>OLG and OIPC Announcement
On November 12, 2010, Tom Marinelli, the Acting CEO of the Ontario Lottery &#38; Gaming Corporation (OLG) and Dr. Ann Cavoukian, the Ontario Information &#38; Privacy Commissioner (OIPC), announced a new development in privacy-protective facial recognition technology. [...]]]></description> <content:encoded><![CDATA[<p>Efficient and accurate <a
href="https://www.cippguide.org/tag/authentication/">authentication </a>of individuals is a growing challenge across a number of sectors. There are currently three main forms of authentication, based on something you know, something you have and something you are. The third form is especially interesting in light of biometric technologies as a means of verification. This article explores some recent applications of biometrics in Ontario.</p><p>OLG and OIPC Announcement<br
/> On November 12, 2010, Tom Marinelli, the Acting CEO of the <a
href="http://www.olg.ca/">Ontario Lottery &amp; Gaming Corporation</a> (OLG) and Dr. Ann Cavoukian, the <a
href="http://www.ipc.on.ca/english/Home-Page/">Ontario Information &amp; Privacy Commissioner</a> (OIPC), announced a new development in privacy-protective facial recognition technology. This <a
href="https://www.cippguide.org/tag/biometric/">biometric </a>system is scheduled to be implemented in 2011 in various OLG gaming sites throughout the province. The objective is to better protect the data of OLG customers, as well as support voluntary self-exclusion programs.</p><p>Self-Exclusion Program<br
/> One of the initiatives of the OLG is the voluntary self-exclusion program. This gives individuals the option to initiate a self-imposed ban from one or more gaming sites. Every casino in Canada offers a self-exclusion program, which varies in terms of scope, length and penalty for breaches. Ontario’s self-exclusion program enables individuals to opt out of OLG marketing and promotions databases. Individuals in the program will also be escorted from OLG gaming sites and issued a trespass notice. Enrollment in the program may last a minimum of six months and may extend indefinitely. As one of the OLG’s objectives is to detect program members who are attempting to enter a gaming site, it is necessary to improve detection.</p><p>Currently, the procedures for detecting self-excluded individuals consist of collecting a photograph and personal information, which was stored in secure binders accessible only to security personnel. However, such a manual identification process is largely inefficient and ineffective, especially since most people aren’t good at recognizing faces of those they don’t know.</p><p>In order to address these issues, a new system was developed through collaboration between <a
href="http://www.iviewsystems.com/">iView Systems</a>, an Ontario video surveillance and biometric firm and University of Toronto researchers Professor Kostas Plataniotis and Dr. Karl Martin. This new system combines a watch list module with a BE module. The watch list relies on traditional facial recognition technology for each casino patron. The BE module releases keys for each subject on the top matches list. Should a key be released, a match alert is sounded.</p><p>Privacy Issues &amp; Biometric Encryption<br
/> Privacy professionals have been concerned that surveillance and biometric systems may compromise individuals’ privacy. Some of the main privacy issues regarding biometrics are outlined below:</p><p>1.	Data Linkage – There is the possibility that biometric databases can be linked algorithmically for data mining, profiling and investigation.</p><p>2.	Function Creep – This refers to expanding the scope of a system. For instance, the biometric data may be used for purposes other than the originally described purposes.</p><p>3.	Data Misuse – Biometric data cannot be replaced or reset, thus they present a high risk for threat or abuse.</p><p>4.	Security Vulnerabilities – Such vulnerabilities include: interception, replay, substitution, masquerade, spoofing, Trojan horse attacks and tampering.</p><p>In order to address the above privacy issues, the <a
href="http://www.privacybydesign.ca/">Privacy by Design</a> approach (discussed in further detail below) has developed a process known as biometric <a
href="https://www.cippguide.org/tag/cryptography/">encryption </a>(BE). BE securely binds a key to/extracts a key from a biometric, such that neither the key nor the biometric can be retrieved from the data, except through verification with the correct live biometric sample.</p><p>According to the OIPC, the process of BE offers the following advantages over other types of biometric systems. These advantages are outlined below:<br
/> 1.	Images, biometric templates and keys are not retained. The user’s biometrics are never stored, thus they cannot be compromised. The original biometric is untraceable.</p><p>2.	Multiple, cancellable, revocable identifiers. There is no way to associate a biometric with accounts.</p><p>3.	Improved authentication security. BE securely binds account identifiers to an individual’s biometric. There is no need for the user to remember these identifiers.</p><p>4.	Greater public confidence, acceptance and use. BE enables biometric data to remain under the control of the individual, which limits the possibility of identity theft and surveillance.</p><p>5.	Greater compliance with privacy legislation.</p><p>6.	Suitable for large-scale applications. Other biometric systems store data on centralized databases, which are highly vulnerable to identity theft. There is less risk with BE.</p><p>Privacy by Design Approach<br
/> The Privacy by Design (PbD) Approach was developed by Dr. Ann Cavoukian during the 1990s. It is based on the notion that technology can be used to protect, rather than encroach upon, privacy. PbD links the international standard fair information practices with the 7 Foundational Principles. These unique principles are as follows:</p><p>1. <strong>Proactive </strong>– PbD strives to be proactive, anticipating and preventing privacy invasions, rather than reactive.</p><p>2. <strong>By Default</strong> – Personal data is automatically protected in any IT system or business practice. Privacy protection is incorporated into the design of the system.</p><p>3. <strong>Embedded </strong>– Privacy protections should be embedded into the design and architecture of systems and practices; they are core components of the functionality of the systems.</p><p>4. <strong>Positive-Sum</strong> – All legitimate interests and objectives are included in a positive-sum/win-win approach. It is possible to balance the needs of privacy and security.</p><p>5. <strong>Lifecycle Protection</strong> – Privacy protection practices extend through the entire lifecycle of the data.</p><p>6. <strong>Visibility/Transparency</strong> – All stakeholders are made aware of the operations of the practices or the technologies used.</p><p>7. <strong>Respect for Users</strong> – Architects and operators are required to offer user-friendly options, such as strong privacy defaults and appropriate notice.</p><p>The applicability of these principles has allowed the PbD concept to be used in the following areas:<br
/> I.	Information Technology<br
/> II.	Accountable Business Practices<br
/> III.	Physical Design<br
/> The PbD approach has been recently approved by the Council of International Data Protection and Privacy Commissioners as an “essential component of fundamental privacy protection.”</p><p>Summary<br
/> This article explores the Privacy by Design (PbD) approach, which was initially pioneered by the Ontario Information and Privacy Commissioner as a means of extending privacy concerns beyond legislation and regulation. The PbD approach fundamentally integrates privacy assurance into the design and operations of an organization’s systems and practices. The article looks at how PbD has been used to develop a new facial-recognition technology, which will be implemented in casinos throughout Ontario in 2011.</p><p>CIPP Exam Preparation<br
/> In preparation for the Certified Information Privacy Professional/Canada (CIPP/C) exam; the Certified Information Privacy Professional/Information Technology (CIPP/IT) exam, a privacy professional should be comfortable with topics related to this post, including:<br
/> •	Canada – Provincial Privacy Commissioners (CIPP/C; II.B.e.i.1.b.)<br
/> •	Policy Development &amp; Implementation (CIPP/C; III.B.b.)<br
/> •	Biometric Identification (CIPP/IT; VI.G.iii.)</p><p><a
class="a2a_dd a2a_target addtoany_share_save" href="http://www.addtoany.com/share_save#url=https%3A%2F%2Fwww.cippguide.org%2F2011%2F01%2F18%2Fontario%25e2%2580%2599s-privacy-protective-facial-recognition-system%2F&amp;title=Ontario%E2%80%99s%20Privacy-Protective%20Facial%20Recognition%20System" id="wpa2a_6"><img
src="https://www.cippguide.org/wp-content/plugins/add-to-any/share_save_171_16.png" width="171" height="16" alt="Share"/></a></p>]]></content:encoded> <wfw:commentRss>https://www.cippguide.org/2011/01/18/ontario%e2%80%99s-privacy-protective-facial-recognition-system/feed/</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item><title>EU Data Retention Directive: A Request for Repeal</title><link>https://www.cippguide.org/2011/01/04/eu-data-retention-directive-a-request-for-repeal/</link> <comments>https://www.cippguide.org/2011/01/04/eu-data-retention-directive-a-request-for-repeal/#comments</comments> <pubDate>Tue, 04 Jan 2011 17:00:11 +0000</pubDate> <dc:creator>hannah</dc:creator> <category><![CDATA[Privacy]]></category> <category><![CDATA[EU]]></category> <category><![CDATA[EU Data Retention Directive]]></category> <category><![CDATA[legislation]]></category> <category><![CDATA[online privacy]]></category> <category><![CDATA[Surveillance]]></category><guid
isPermaLink="false">https://www.cippguide.org/?p=2398</guid> <description><![CDATA[<p>Data retention has been an important issue for law enforcement agencies and privacy rights organizations alike. Governments have made efforts to require telecommunications service providers to record and retain information, such as telephone calls, emails, or other communications. This article examines the European Union Directive on Mandatory Retention of Communications Traffic Data, which was enacted in March 2006. The article goes on to look at criticisms of the Directive as well as recent efforts calling for the repeal of this Directive.</p><p>Background: The 2006 EU Data Retention Directive
The EU Data Retention Directive 2006/24/EC required that operators of public electronic communication networks [...]]]></description> <content:encoded><![CDATA[<p>Data retention has been an important issue for law enforcement agencies and privacy rights organizations alike. Governments have made efforts to require telecommunications service providers to record and retain information, such as telephone calls, emails, or other communications. This article examines the European Union Directive on Mandatory Retention of Communications Traffic Data, which was enacted in March 2006. The article goes on to look at criticisms of the Directive as well as recent efforts calling for the repeal of this Directive.</p><p>Background: The 2006 EU Data Retention Directive<br
/> The <a
href="http://register.consilium.eu.int/pdf/en/05/st03/st03677.en05.pdf">EU Data Retention Directive 2006/24/EC</a> required that operators of public electronic communication networks store specific data for the investigation, detection and prosecution of serious crime. The Directive requires that Internet service providers operating in Europe retain telecom and Internet traffic data about all their clients’ communications for at least six months, to a maximum of two years from the date of the communication. This is for the potential use of law enforcement authorities. Retained data includes the traffic and location data, but not the contents of the communications.</p><p>Of specific concern to privacy professionals was that the retained data included the following:<br
/> •	Fixed network telephony<br
/> •	Mobile telephony<br
/> •	Internet access<br
/> •	Internet email<br
/> •	Internet telephony</p><p>The data retention regulations listed four data security principles, applicable to the retained data. These regulations are outlined below:<br
/> 1.	The data must have the same security levels when retained and must remain the same quality.<br
/> 2.	Security measures (both technical and organizational) must be enacted to protect against accidental or unlawful disclosure, access, alteration or loss of the data.<br
/> 3.	The retained data should only be accessible by authorized persons.<br
/> 4.	All retained data must be appropriately destroyed at the end of the retention period.</p><p>As part of the terms of the Directive, the data could only be made available to competent national authorities in particular cases, in line with national law. EU member states are responsible to ensure that any intentional access or transfer of this data is punishable by administrative or criminal penalties. Member states were also required to have a public authority responsible for implementing and monitoring the Directive within 18 months after it was introduced. Each state developed their own version of the Directive, which was integrated into their national laws.</p><p>Controversy Surrounding the Directive<br
/> For public communications providers throughout the EU, the Directive presented a number of different challenges. Service providers were mandated to retain communications data to allow requested access for investigations. This meant that they were faced with the challenge of harmonizing their data center with hundreds of storage devices and petabytes of data. This significantly increased the size of IT infrastructures. Many critics argued that the mandated retention practices made organizations more vulnerable to privacy risks.</p><p>Observers also argued that the requirements of the Directive amounted to a type of surveillance. The Directive requires member states to collect personal data about citizens, without the consent of the citizens. It also allows the states to apply the data to monitor and control citizens, by applying criminal penalties.<br
/> For these and other reasons, many European privacy activists have strongly <a
href="http://www.edri.org/campaigns/dataretention">opposed </a>the Directive.</p><p>One example was the <a
href="http://www.vorratsdatenspeicherung.de/content/view/46/42/lang,en/">Freedom Not Fear</a> movement, which organized protests in major cities across Europe. These demonstrations aimed to raise public awareness of increased surveillance and data retention practices. The Freedom Not Fear movement also demanded the following:<br
/> •	Cutbacks on surveillance measures<br
/> •	Evaluation of existing surveillance powers<br
/> •	Moratorium on new surveillance powers<br
/> •	Ensure the freedom of expression, dialogue and information on the Internet</p><p>During 2007, the <a
href="http://www.vorratsdatenspeicherung.de/index.php?lang=en">German Working Group on Data Retention</a> represented 35 000 people and filed a class-action lawsuit against data retention laws. The court found the laws unconstitutional, which led to requirements for the immediate deletion of all data retained under the law.</p><p>During 2009, the Romanian Constitutional Court ruled that the Directive was in direct violation of <a
href="http://www.hri.org/docs/ECHR50.html#C.Art8">Article 8</a> of the European Convention on Human Rights, guaranteeing the right to respect for private life and correspondence. The Court held that data retention turns all those who use public communication networks into potential criminals.</p><p>Also during 2009, the European Commission initiated a lawsuit with the Swedish government, which had refused to implement the Data Retention Directive within the required time frame. Political leaders argued that the Directive was inconsistent with the European Convention on Human Rights, as well as being an expensive and ineffective means of protecting citizens’ rights and freedoms. In addition to Sweden’s non-cooperation with the Directive, Austria, Greece, Ireland, the Netherlands and Poland also did not implement data retention laws within the April 2009 deadline stipulated by the Directive.</p><p>Calls to repeal the Directive<br
/> During the <a
href="http://www.privacyconference2010.org/">32nd Annual Conference of Data Protection and Privacy Commissioners</a>, which was held during October 27-29, 2010, privacy authorities called for the repeal of the Data Retention Directive.</p><p>A vocal participant in this discussion was the <a
href="http://www.eff.org/work">Electronic Frontier Foundation</a> (EFF), which has protested the indiscriminate collection of traffic data. According to the EFF, there is no clear link between data retention and effective law enforcement. Rather, such retention leads to abuse of authorities, including excessive tracking and over-collection. Furthermore, many of the retention practices pose a serious violation of individuals’ rights and freedoms.</p><p>Summary<br
/> This article explores the 2006 European Union Data Retention Directive, which required member states to implement laws requiring communications service providers to retain data from anywhere between six months to two years. This was supposedly to facilitate law enforcement efforts, particularly anti-terrorist programs. The Directive was met with widespread public outcry, given the potential for surveillance, monitoring and abuse, in addition to arguments that it was a violation of rights and freedoms. The article explores a number of different responses to the Directive, including citizens’ movements throughout Europe, national court rulings against the Directive and non-compliance issues.</p><p>CIPP Exam Preparation<br
/> In preparation for the Certification Foundation (Foundations) exam and the Certified Information Privacy Professional/Information Technology (CIPP/IT) exam, a privacy professional should be comfortable with topics related to this post, including:<br
/> •	Data Retention &amp; Destruction – Period of Retention (CIPP/IT; I.E.a.)<br
/> •	Privacy Concerns – Government Surveillance (CIPP/IT; II.A.k.)<br
/> •	Modern Principles of Privacy – Europe (Foundations; I.D.a.ii.)<br
/> •	Privacy &amp; Data Protection Regulation – Europe (Foundations; I.F.b.ii.)</p><p><a
class="a2a_dd a2a_target addtoany_share_save" href="http://www.addtoany.com/share_save#url=https%3A%2F%2Fwww.cippguide.org%2F2011%2F01%2F04%2Feu-data-retention-directive-a-request-for-repeal%2F&amp;title=EU%20Data%20Retention%20Directive%3A%20A%20Request%20for%20Repeal" id="wpa2a_8"><img
src="https://www.cippguide.org/wp-content/plugins/add-to-any/share_save_171_16.png" width="171" height="16" alt="Share"/></a></p>]]></content:encoded> <wfw:commentRss>https://www.cippguide.org/2011/01/04/eu-data-retention-directive-a-request-for-repeal/feed/</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item><title>RFID Technology</title><link>https://www.cippguide.org/2010/07/27/rfid-technology/</link> <comments>https://www.cippguide.org/2010/07/27/rfid-technology/#comments</comments> <pubDate>Tue, 27 Jul 2010 12:00:26 +0000</pubDate> <dc:creator>hannah</dc:creator> <category><![CDATA[CIPP]]></category> <category><![CDATA[Information Security]]></category> <category><![CDATA[CIPP/C]]></category> <category><![CDATA[CSA]]></category> <category><![CDATA[CSA Model Code]]></category> <category><![CDATA[Office of the Privacy Commissioner]]></category> <category><![CDATA[OPC]]></category> <category><![CDATA[PIPEDA]]></category> <category><![CDATA[Public Interest Advocacy Center]]></category> <category><![CDATA[RFID]]></category> <category><![CDATA[Surveillance]]></category><guid
isPermaLink="false">http://www.cippguide.com/?p=1937</guid> <description><![CDATA[In recent years, RFID (radio frequency identification) has caught the attention of privacy watchdogs, civil organizations and the general public. Its ability to identify and track items as well as individuals raises a number of privacy and security concerns, while the potential for integration into numerous contexts has increased with the development of technology. Discussion and integration of RFID in the workplace, retail situations and other environments should be informed by a number of privacy-respecting practices that will be explored in this [...]]]></description> <content:encoded><![CDATA[<p>In recent years, RFID (<a
href="http://www.cippguide.org/tag/RFID/">radio frequency identification</a>) has caught the attention of privacy watchdogs, civil organizations and the general public. Its ability to identify and track items as well as individuals raises a number of privacy and security concerns, while the potential for integration into numerous contexts has increased with the development of technology. Discussion and integration of RFID in the workplace, retail situations and other environments should be informed by a number of privacy-respecting practices that will be explored in this article.</p><h2>What is RFID?</h2><p>RFID is a term for a group of technologies that enable machines to identify objects. This may include bar codes, smart cards, optical character readers, biometric technologies and more. RFID uses radio waves to identify items. Its first application was the identification of aircraft during WWII. Since then, developments in technology have reduced the cost and increased potential applications of RFID technology. The automatic identification offered by RFID is attractive to many organizations and retail stores, as it reduces the time and labor necessary to manually input data and to improve data accuracy.</p><p>There are three components in an RFID system:</p><ol><li><strong>Tag</strong>: this is usually made up of a microchip unit, antenna and encapsulating material. Microchips can store up to two kB of data. This may be information about a certain product, such as its destination or sell-by date. An RFID system may include multiple tags.</li></ol><p>Tags are also referred to as transponders. They can be read-only or read-write tags. “Read-only” means that the information on the tags cannot be changed in any way. Read-write tags can have the information modified or erased multiple times. Since they offer greater functionality, their price is much higher than read-only tags.</p><ol><li><strong>Reader</strong>: this is a device that has at least one antenna to communicate with the RFID tag. It emits radio waves and receives signals back from the tag. The reader passes digital information to a computer system. Readers are also known as interrogators. They can be portable, handheld devices or fixed terminals positioned in strategic places, such as loading bays or doorways.</li><li><strong>Infrastructure</strong>: this includes the necessary hardware and software for supporting the RFID system. The RFID software translates the data from the tag into the information about the goods and orders. This information is transmitted into other databases and applications for processing.</li></ol><h2>How can RFID be used?</h2><p>RFID technology has and will be applied in a variety of public and private sector organizations. Uses include:</p><ul><li>Product Integrity – to ensure that products are authentic and untampered with</li><li>Supply Chain Management – to monitor and control the flow of goods through the supply chain (i.e. from raw material to finished product to consumer)</li><li>Warranty Services – goods with tags incorporated into the materials, in order to facilitate warranty services</li><li>ID, Travel &amp; Ticketing – to verify the identity of the traveller; to ensure that travel documents are genuine</li><li>Baggage Tracking – to monitor and control the movement of baggage (e.g. from check-in to loading)</li><li>Patient Care &amp; Management – to rapidly, accurately verify patient information (e.g. allergies, prescription, health history, etc.)</li></ul><h2>Privacy Issues</h2><p>According to the Canadian <a
href="http://www.piac.ca/">PIAC</a> (Public Interest Advocacy Center), RFID technology presents a challenge to Canadian privacy legislation. The basic surveillance capabilities of RFID are unlikely to violate privacy, though the <a
href="http://www.cippguide.com/2010/06/10/personal-information-protection-and-electronic-documents-act-pipeda/" target="_blank">PIPEDA</a> significantly limits the use of RFID for consumer surveillance purposes.</p><p>However, later <a
href="http://www.cippguide.org/tag/OPC/">Office of the Privacy Commissioner of Canada</a> (OPC) <a
href="http://www.priv.gc.ca/information/consultations/2010/rep_rfid_1003_e.cfm">research</a> indicated that there were significant concerns regarding the use of RFID in the workplace. Through a number of public consultations, the OPC was able to establish the perspectives of academics, RFID vendors, industry groups and private citizens. Numerous privacy threats were identified:</p><p>Repeated collection of information</p><ul><li>Since RFID tags are very small, they can easily be embedded on/in objects or documents without the individual’s knowledge. It is possible to read RFID tags through fabric, plastic and other materials, as radio waves are not restricted to line of sight. Tags can also be read from a distance. These factors render it impossible for individuals to know if/when he/she is being scanned.</li></ul><p>Tracking Movements</p><ul><li>If there is a sufficient network of RFID readers, the tags can be tracked in time and space. This is possible through a combination of GPS (Global Positioning Systems) and RIFD technologies.</li></ul><p><a
href="http://www.cippguide.org/tag/pass-id/">Profiling Individuals</a></p><ul><li>RFID technology means that each object has its own unique identification. This contrasts bar code technology, which gives the same identification to all similar objects (e.g. in a grocery store, all orange juice cartons of the same brand have the same bar code). If unique identifiers are associated with individuals, then profiles of purchasing habits can be compiled.</li></ul><p>Secondary Use</p><ul><li>Creating profiles and tracking individual movement can be linked to other information which the individual may not want revealed.</li></ul><p><a
href="http://www.cippguide.org/2009/02/05/finlands-fingerprinting-fiasco-centralized-private-records-database-accessible-by-police/">Massive Data Aggregation</a></p><ul><li>RFID records may be linked with personally identifying data, which may facilitate any of the other privacy threats listed previously.</li></ul><h2>OPC Responses</h2><p>The OPC recommends that the ten principles of the <a
href="http://www.cippguide.com/2010/06/29/csa-model-code/" target="_blank">CSA Model Code</a>, as well as the PIPEDA form the basis for an RFID privacy management framework. OPC research responds to each of the ten CSA principles, with respect to RFID technologies:</p><ol><li>Accountability – Who has access to and who is accountable for the data generated by RFID systems, as well as other data collection systems in the workplace?</li><li>Identifying Purposes – RFID systems that are used for legitimate business purposes (e.g. supply chain management) are more likely to be supported than RFID systems used for secondary purposes or surveillance (e.g. employee surveillance, workforce management). The OPC identified that industry standards, policies or guidelines can help to ensure that the data collected through these systems are used and disclosed for identified purposes.</li><li>Consent – Meaningful consent must be secured before an RFID system is implemented. However, there is the challenge of securing meaningful and completely voluntary consent in a workplace setting.</li><li>Limiting Collection – Reasonable expectations of privacy must be balanced with reasonable management of RFID systems. While reasonable expectations of employees are important, the reasonable management of the RFID system is the employer’s responsibility. This involves the protection of employee privacy.</li><li>Limiting Use, Disclosure &amp; Retention – The issue of RFID implants was a significant concern for OPC and other groups who were consulted, as implants present significant privacy and security issues. For instance, employee conduct might be monitored during and after work hours, at lunch, during vacation, and for tracking physical movements and conduct. This may pose a serious security issue.</li></ol><p>Employers should limit the collection of personally identifiable information, including RFID-related data. Data from RFID systems should not be linked to other databases, unless there is a proven need.</p><ol><li>Accuracy – It is the responsibility of the employer to ensure that personal information is accurate, complete and up to date for the purposes for which it is to be used. An audit trail might be established and maintained regarding the lifecycle of the RFID data.</li><li>Safeguards – RFID systems that contain personal information must be protected in a way that is proportionate to its sensitivity. Employers should be made accountable for any breach of RIFD technology. Protecting data in each distinct part of the system is an effective approach to safeguarding employee privacy.</li><li>Openness – For instance, hidden tags or readers should not be implemented. Clients, employees and/or unions should be consulted before RFID systems are installed. Tags and readers ought to be in plain sight, never used for covert surveillance.</li><li>Individual Access – Individuals (e.g. clients, employees, union leaders) should be guaranteed access to any personally identifiable data generated by RFID systems.</li><li>Challenging Compliance – Individuals ought to be able to <a
href="http://www.cippguide.org/2009/07/03/fixing-mistakes-data-subject-access-redress/">challenge compliance</a> with other principles. This may be the ability to make inquiries or lodge a complaint if necessary.</li></ol><p>After examining each principle individually, the OPC stated some guiding applications for the implementation of RFID technology in a way that respects <a
href="http://www.cippguide.org/2010/01/18/fair-information-practices-principles/?action=lostpassword&amp;instance=tml-1">Fair Information Practices</a>:</p><ul><li>If the RIFD chip has an individual’s personal information contained on it, then it is defined as a repository of personal information.</li><li>If the tag is unique, it can be associated with an individual. The tag becomes a unique identifier for that individual.</li><li>Personal information includes information about possessions, purchases or behaviors that can be processed to create a profile.</li></ul><h3>Summary</h3><p>This article provides a brief introduction to RFID (radio frequency identification) technology. It explores some uses of this technology in consumer and work settings. Privacy concerns regarding RFID systems are raised. The article also offers some responses and recommendations made by the Privacy Commissioner of Canada regarding implementation of RFID technology.</p><h3>CIPP/C Preparation</h3><p>In preparation for the Certified Information Privacy Professional/Canada exam, a privacy professional should be comfortable with topics related to this post, including:</p><ul><li>CSA Model Code for the Protection of Personal Information (II.A.a.i.)</li><li>Radio Frequency Identification (RFID) (V.A.a.5.)</li><li>Security threats and vulnerabilities (V.A.b.)</li><li>Information management (V.c.i.)</li></ul> ]]></content:encoded> <wfw:commentRss>https://www.cippguide.org/2010/07/27/rfid-technology/feed/</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item><title>Surveillance &amp; Investigation in Canada</title><link>https://www.cippguide.org/2010/07/20/surveillance-investigation-in-canada/</link> <comments>https://www.cippguide.org/2010/07/20/surveillance-investigation-in-canada/#comments</comments> <pubDate>Tue, 20 Jul 2010 12:00:50 +0000</pubDate> <dc:creator>hannah</dc:creator> <category><![CDATA[CIPP]]></category> <category><![CDATA[Compliance & Regulations]]></category> <category><![CDATA[CIPP/C]]></category> <category><![CDATA[legislation]]></category> <category><![CDATA[Office of the Privacy Commissioner]]></category> <category><![CDATA[OPC]]></category> <category><![CDATA[provincial commissioners]]></category> <category><![CDATA[Surveillance]]></category><guid
isPermaLink="false">http://www.cippguide.com/?p=1939</guid> <description><![CDATA[The introduction of Bills C-46 and C-47 in Canada sparked concern regarding the role of the federal government and other authorities to expand surveillance and increase investigation of the Canadian public. The bills were tabled June 2009 and continue to be met with much concern. This article will elaborate on the significant aspects of each bill, with an eye to some of the potential privacy concerns that may be [...]]]></description> <content:encoded><![CDATA[<p>The introduction of Bills C-46 and C-47 in Canada sparked concern regarding the role of the federal government and other authorities to expand surveillance and increase investigation of the Canadian public. The bills were tabled June 2009 and continue to be met with much concern. This article will elaborate on the significant aspects of each bill, with an eye to some of the potential privacy concerns that may be raised.</p><h2>Bills C-46 &amp; C-47</h2><p>In June 2009, the Canadian federal government tabled two significant pieces of legislation: the <a
href="http://www2.parl.gc.ca/HousePublications/Publication.aspx?DocId=4008179&amp;Language=e&amp;Mode=1">Investigative Powers for the 21<sup>st</sup> Century Act</a> (Bill C-46) and the <a
href="http://www2.parl.gc.ca/HousePublications/Publication.aspx?DocId=4007628&amp;Language=e&amp;Mode=1">Technical Assistance for Law Enforcement in the 21<sup>st</sup> Century Act</a> (Bill C-47).</p><p>Bill C-46 allows police and other authorities to collect digital evidence amongst numerous devices and computer networks. These may be interprovincial or even international. A motivating factor for this bill is to ensure that multiple avenues are examined, in a timely manner, especially since digital data often has a short life span. Some important issues in the Bill C-46 legislation include:</p><p>Transmission Data</p><ul><li>This includes the data from telephone and internet communications. However, this does not include the content.</li><li>This ensures that communications can be traced back to the original service provider. This allows police to trace domestic and international cybercrime.</li><li>Determining the origin of transmission can help identify the jurisdiction of telecommunications.</li></ul><p>Preservation Order</p><ul><li>A preservation order is a temporary order that requires a telecommunications service provider to safeguard and store data (e.g. usage and location) related to a specific communication. It is also known as a “quick freeze” order.</li><li>This is restricted only to the data that is related to a particular investigation.</li></ul><p>Tracking Warrants</p><ul><li>This allows police to remotely activate tracking devices found in some technologies (e.g. cell phones, car tracking devices).</li><li>This may permit police to install new devices to enable tracking.</li><li>Authorities can have special orders for tracing mobile communications devices as well as their owners.</li></ul><p>International Considerations</p><ul><li>International cooperation is crucial for many cybercrime investigations.</li><li>The proposals in this bill strengthen the instruments that enable broad-based international cooperation in investigation as well as prosecution of computer-related crimes.</li></ul><p>Bill C-47 does not provide police or other law enforcement authorities with additional powers, but it does mandate that authorities have a technical solution in place to actually intercept telecommunications. At this point, Canada does not require companies to build interception capability into their telecommunications networks. This means that when warrants are issued, they cannot be acted upon, since the service provider’s network cannot be intercepted. This may create a safe haven for criminal activity.</p><p>In response, Bill C-47 requires companies to create intercept-capable infrastructures, which includes paying for the new equipment and software involved. The government will provide compensation for any required retrofits. The intention is to introduce intercept solutions as flexibly and gradually as possible. This will ensure that telecommunication services are able to build and maintain interception capability without creating undue burdens on the company. Eventually, Bill C-47 will allow authorities to obtain individual information such as name, phone number, address, IP address, and other mobile phone identifiers.</p><h2>Perspectives</h2><p>Some proponents of the Bills have argued that the legislation is not too different from other criminal legislation affecting privacy interests. They argue that Canada is far behind the curve in terms of lawful access legislation. For instance, both the US and Australia have implemented such legislation for more than ten years. Introducing such measures will enable Canadian companies to comply with international obligations, facilitating international competition.</p><p>However, others have cautioned that these measures should not simply be implemented because of the choices of other countries. It is important to note that in a number of countries interception and surveillance measures were passed, in spite of public opposition.</p><p>Opponents of the bills argue that while the proposals are presented as security measures, they may lead to a “chilling effect.” This means that citizens may become nervous about the monitoring of their online activities. Lawful surveillance may silence debates and shut down the development of legal online activities.</p><p>Other observers commented on the fact that there is increased collaboration between government and private actors to track citizens’ actions and activities in the digital world. Surveillance and interception is largely justified based on user agreements. These contain provisions which allow the telecommunications service providers to monitor and transmit the information to authorities. However, many users do not read or understand these agreements. They are also unable to negotiate the terms with the service providers. Arguably, users have no choice but to hand over their constitutional rights, if they want to have access to such necessities as telephone and internet services.</p><h2>OPC Concerns</h2><p>The <a
href="http://www.cippguide.com/2010/06/03/privacy-commissioner-of-canada/" target="_blank">Office of the Privacy Commissioner</a> of Canada (OPC) recommends that Parliament remain cautious about surveillance and interception legislation, which will often have repercussions on other jurisdictions as well as a significant impact upon the privacy rights of Canadians. In a <a
href="http://www.priv.gc.ca/media/nr-c/2009/res_090910_e.cfm">joint resolution</a> issued by the federal Privacy Commissioner as well as <a
href="http://www.cippguide.com/2010/06/15/provincial-territorial-privacy-commissioners/" target="_blank">provincial commissioners and ombudspersons</a>, there must be a clear and demonstrable need for acquiring before expanding investigative powers of law enforcement and other national security agencies. According to the Commissioners and ombudspersons, the federal government has not provided satisfactory evidence that supports the need for the new powers outlined in the proposed legislations.</p><p>The joint resolution argues that the proposed legislations allow authorities to access personal information, such as unlisted telephone numbers, email addresses and IP addresses. However, Canadians consider this information extremely sensitive and expect it to remain confidential. The use of computers and other remote devices should also remain private. Arguably, the proposed legislation does not only target serious criminal offenses, but it might also be applied to investigations of minor infractions and non-criminal matters.</p><p>While the OPC and the ombudspersons are not completely opposed to legislation regarding the monitoring of digital data, it must take into account individual privacy rights and the legitimate needs of law enforcement authorities. The following outlines the OPC’s recommendations regarding Bill C-46 and Bill C-47:</p><ul><li>The federal government needs to demonstrate that the expanded surveillance is actually essential and justified.</li><li>The federal government should explore alternatives to the proposed Bills.</li><li>The Bills should be limited to only specific, serious crimes and life-threatening emergencies.</li></ul><p>If there are any legislative proposals on surveillance, they should embody the following characteristics:</p><ul><li>Minimally intrusive</li><li>Have well-defined limits on the use of the new powers.</li><li>Have appropriate legal thresholds for court authorization.</li><li>Require draft regulations to be publicly reviewed before being enforced.</li><li>Provide effective oversight.</li><li>Publicly report the use of powers.</li><li>Have a five-year Parliamentary review.</li></ul><p>In taking these recommendations into account, Parliament will be able to update surveillance and investigation legislation appropriately to meet the needs of law enforcement.</p><h3>Summary</h3><p>This article examines the proposals in Bill C-46 and Bill C-47, which are the Investigative powers for the 21<sup>st</sup> Century Act and the Technical Assistance for Law Enforcement in the 21<sup>st</sup> Century Act, respectively. It looks at the new powers that may be afforded to police and other law enforcement bodies across Canada. It introduces a number of different perspectives on the Bills. For some, the Bills do not present an issue for concern, as many other countries have introduced similar legislation and Canada is simply catching up with these obligations. But for others, those who are opposed to the Bills point out the repercussions in varied contexts. Finally, the article examines the OPC’s response and recommendations to surveillance legislation.</p><h3>CIPP/C Preparation</h3><p>In preparation for the Certified Information Privacy Professional/Canada exam, a privacy professional should be comfortable with topics related to this post, including:</p><ul><li>Privacy policy, legal requirements (V.C.b.b.)</li><li>End user expectations (V.C.c.a.i.)</li><li>Vendor and contract management (V.C.e.)</li></ul> ]]></content:encoded> <wfw:commentRss>https://www.cippguide.org/2010/07/20/surveillance-investigation-in-canada/feed/</wfw:commentRss> <slash:comments>1</slash:comments> </item> <item><title>Privacy Act of 1974</title><link>https://www.cippguide.org/2010/02/10/privacy-act-of-1974/</link> <comments>https://www.cippguide.org/2010/02/10/privacy-act-of-1974/#comments</comments> <pubDate>Wed, 10 Feb 2010 12:00:05 +0000</pubDate> <dc:creator>jbrook</dc:creator> <category><![CDATA[CIPP]]></category> <category><![CDATA[Compliance & Regulations]]></category> <category><![CDATA[Privacy]]></category> <category><![CDATA[CIPP/G]]></category> <category><![CDATA[Data Sharing Agreement]]></category> <category><![CDATA[data subject access]]></category> <category><![CDATA[Fair Information Practices Principles]]></category> <category><![CDATA[FOIA]]></category> <category><![CDATA[PII]]></category> <category><![CDATA[Privacy Act of 1974]]></category> <category><![CDATA[SORN]]></category> <category><![CDATA[Surveillance]]></category> <category><![CDATA[Systems of Records Notice]]></category><guid
isPermaLink="false">http://www.cippguide.org/?p=1239</guid> <description><![CDATA[The Privacy Act of 1974 is a public sector law that regulates the use of personal information by the United States Government.  Specifically it establishes rules, similar to the Fair Information Practice Principles that determine what information may be collected and how it may be used in order to protect the personal privacy of U.S. [...]]]></description> <content:encoded><![CDATA[<p><script type="text/javascript"></script></p><p>The <a
href="http://www.justice.gov/opcl/privstat.htm">Privacy Act of 1974</a> is a public sector law that regulates the use of personal information by the United States Government.  Specifically it establishes rules, similar to the <a
title="CIPP Guide: Fair Information Practice Principles" href="http://www.cippguide.org/2010/01/18/fair-information-practice-principles/" target="_self">Fair Information Practice Principles</a> that determine what information may be collected and how it may be used in order to protect the personal privacy of U.S. citizens.</p><p><strong><a
href="http://en.wikipedia.org/wiki/Privacy_Act_of_1974">Data Collection and Management</a></strong></p><p>The Privacy Act of 1974 applies to <em>Federal Government Agencies</em> and governs their use of a system of records. By definition, a <a
href="http://nces.ed.gov/StatProg/rudman/a.asp%23s">system of records</a> is “any group of records under the control of any agency from which information is retrieved by the name of an individual or by some identifying number, symbol, or other identifying particular assigned to the individual.”</p><p>The following rules govern the use of a system of records:</p><ul><li>No Federal Government record keeping system may be kept secret</li><li>No agency may disclose personal information to third parties without the consent of the individual (with some exceptions)</li><li>No agency may maintain files on how a citizen exercises their First Amendment rights</li><li>Federal personal information files are limited only to data that is relevant and necessary</li><li>Personal information may able be used for the purposes it was originally collected unless consent is received from the individual.</li><li>Citizens must receive notice of any third party disclosures including with whom the information is shared, the type of information disclosed and the reasons for its disclosure.</li><li>Citizens must have access to the files maintained about them by the Federal Government</li><li>Citizens must have the opportunity to correct or amend any inaccuracies or incompleteness in their files</li></ul><p><strong><a
href="http://epic.org/privacy/1974act/">Data Sharing</a></strong></p><p>The Privacy Act of 1974 places restrictions on the ability of Federal agencies to share a system of records with third parties, including other agencies. However, the Privacy Act does recognize the need of the government to share records in order to improve security, maintain accuracy and consolidate resources. This is often accomplished through matching programs which allow certain data elements in one system of records to be searched against records in another system in order to find any data matches. Such matches would link together the information from both systems.</p><p>In order for any agency to run a matching program with a system of records from an another agency, their must first be a written agreement between both parties. The Committee on Governmental Affairs of the Senate, and the Committee on Government Operations of the House must receive a copy of the agreement. It must also be made available to the public.</p><p>A Data Sharing Agreement:</p><ul><li>Must state the purposes and legal justifications for the matching program</li><li>Must provide rational for the program by estimating the results and savings that will be achieved</li><li>Must describe the records to be matched including the specific data elements, estimate the number of records to be matched and provide estimated start and completion dates for the program</li><li>Must describe how the privacy principles of the Privacy Act will be implemented in the program (ie: notice to the individual, ensure accuracy and completeness, limited used of results)</li><li>Must provide an accuracy assessment of the unmatched records</li><li>Must include a statement allowing the Comptroller General to monitor compliance with the Privacy Act if necessary.</li></ul><p><strong><a
href="http://www.gpoaccess.gov/fr/index.html">Federal Register</a></strong></p><p>To ensure that no system of records is kept secret, the Privacy Act requires all government agencies to provide a System of Records Notice (SORN) to biennially to be published in the Federal Register. Each SORN must also be published on the agencies website under the Electronic Privacy Act Amendment.</p><p>Each SORN must contain:</p><ul><li>The name location of the records system</li><li>The title and business address of the individual overseeing the system of records at the agency</li><li>The types of individuals about whom records are kept</li><li>The categories of records kept in the system</li><li>The general sources from which data is collected</li><li>The privacy and usage policies of the agency, including those for access controls, storage, retrievability and destruction.</li><li>How an individual may determine if an agency maintains a record about them in their system of records</li><li>How an individual may gain access to the records an agency maintains about them</li></ul><p><strong><a
href="http://epic.org/privacy/1974act/">Exceptions to the Privacy Act</a></strong></p><p>While the Privacy Act did take significant steps towards protecting privacy, there are a few important distinctions within the act that create holes in its protection.</p><p>The Privacy Act only applies to a system of records maintained by an agency. Records systems kept by government institutions not considered an agency are exempt. Further more a system of records is defined as a group of records which uses <em>personally identifiably information</em> or signifiers to retrieve a file. There may be records systems which contain personal information but does not use that information to search for and gain access to a record. Such system of records would also be exempt under the Act.</p><p>The Privacy Act also contains a “routine use” exception which allows the disclosure of information without the notice or consent of the individual. Routine use is defined as “the use of such record for a purpose which is compatible with the purpose for which it was collected.” The vague definition of routine use allows agencies to expand their definition of compatible purpose at will, eventually allowing more and more information to be disclosed under the routine use exception. As long as the SORN contains a listing of the routine uses of the information, an agency is considered compliant with the Privacy Act.</p><p><strong>Summary</strong></p><p>Like the <a
title="CIPP Guide: Freedom of Information Act" href="http://www.cippguide.org/2010/02/08/foia-the-freedom-of-information-act/" target="_self">Freedom of Information Act</a>, the Privacy Act of 1974 seeks to protect the privacy of U.S. citizens by giving them the ability to monitor the use of their personal information by the U.S. government. Though the Privacy Act does make significant steps in the protecting the right of privacy, it is also limited enough in its scope and implementation to only provide adequate protection. Privacy professionals and U.S. citizens should be familiar with the Privacy Act of 1974 in order to effectively understand their rights and work to create more comprehensive privacy legislation in the future.</p><p><em>CIPP/G Candidate Preparation</em></p><p>In preparation for the Certified Information Privacy Professional Government exam, a privacy professional should be comfortable with topics related to this post including:</p><ul><li>The Privacy Act of 1974 (I.C.b.i.-iv.)</li></ul> ]]></content:encoded> <wfw:commentRss>https://www.cippguide.org/2010/02/10/privacy-act-of-1974/feed/</wfw:commentRss> <slash:comments>0</slash:comments> </item> </channel> </rss>
<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Minified using disk: basic
Page Caching using disk: enhanced

Served from: www.cippguide.org @ 2012-02-11 04:29:23 -->
