<?xml version="1.0" encoding="utf-8"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Blog Rss Feed</title><description>Blog Rss Feed</description><copyright /><generator>BDS</generator><atom:link href="http://mediatechlaw.loeb.com/?view=rss" rel="self" type="application/rss+xml" /><link>http://mediatechlaw.loeb.com/?view=rss</link><item><guid>http://mediatechlaw.loeb.com/blog.aspx?entry=140</guid><title>House Cybersecurity Information-Sharing Bill Provides Immunity Provisions for Reporting Companies</title><link>http://mediatechlaw.loeb.com/housepassescyberintelligencesharingprotectionact/</link><description><![CDATA[<P>The U.S. House of Representatives passed an amended version of the Cyber Intelligence Sharing and Protection Act (CISPA), with a 288-127 vote. The current version of CISPA (<A href="http://www.loeb.com/files/Uploads/BILLS_hr624rh.pdf" target=_blank><SPAN style="COLOR: #2684c3; TEXT-DECORATION: underline">H.R. 624</SPAN></A>) would provide private-sector companies with protection from liability for sharing information on cyber-threats with federal government agencies. With the passage of this bill, the House attempts to resolve the problem of President Barack Obama’s Cybersecurity Executive Order not providing any liability protection to reporting companies. (Read our alert on President Obama’s Executive Order <A href="http://www.loeb.com/presidentissuescybersecurityexecutiveorder/" target=_blank><SPAN style="COLOR: #2684c3; TEXT-DECORATION: underline">here</SPAN></A>.) The bill provides both criminal and civil immunity for corporations sharing information with government agencies, as long as they act “in good faith.” The amended version defines a lack of good faith as including “any act or omission taken with intent to injure, defraud or otherwise endanger any individual, government entity, private entity or utility.” It also requires the Director of National Intelligence to establish procedures to permit “elements of the intelligence community” to share cyber-threat information, including classified information, with U.S. companies and utilities.</P>
<P>CISPA expressly limits the federal government’s use of cyber-threat information to only cybersecurity purposes and for the investigation and prosecution of cybersecurity crimes (as well as the prevention of death or serious bodily injury to individuals and various threats against children), and specifically prohibits the government from searching cybersecurity information for any other purpose. The federal government also may not use sensitive personal information (defined to include a number of categories containing information that can be used to identify individuals, including tax returns, medical and educational records, firearms sales records, library circulation records and patron lists, and book sales records), except in accordance with established policies and procedures to protect the private and confidential nature of this information. The bill mandates that the Director of National Intelligence, in consultation with the Secretary of Homeland Security and the Attorney General, establish these policies and procedures.</P>
<P>While CISPA immunizes private-sector companies from liability, it also establishes a private right of action in federal court for actual or statutory damages for any person “adversely affected” by the government’s willful or intentional violation of the express restrictions on the protection, disclosure, and use of the shared information.</P>
<P>The recent amendments to the House version of CISPA were aimed at satisfying concerns about protection of individual privacy – including those expressed by President Barack Obama in a&nbsp;<A href="http://www.scribd.com/doc/136328405/Administration-Policy-CISPA" target=_blank><SPAN style="TEXT-DECORATION: underline">statement</SPAN></A>&nbsp;released prior to the bill’s passage. The President, however, has expressed grave concerns about this bill in its present form and has threatened to veto the bill because it does not require private-sector organizations sharing information “to take reasonable steps to remove irrelevant personal information when sending cybersecurity data to the government or other private sector entities,” and affords broad immunity to the sharing companies. The amended version now goes to the Senate for consideration.</P>]]></description><pubDate>Wed, 15 May 2013 10:23:57 GMT</pubDate></item><item><guid>http://mediatechlaw.loeb.com/blog.aspx?entry=139</guid><title>Commissioner Edith Ramirez Elevated to Chair of Federal Trade Commission</title><link>http://mediatechlaw.loeb.com/commissionerramirezchairftc/</link><description><![CDATA[Commissioner Edith Ramirez began her term as chair of the Federal Trade Commission March 4, 2013, filling the vacancy left by outgoing chair Jon Leibowitz. As a current commissioner, Ramirez assumed the agency’s head position without Senate approval of her selection by President Obama. Her appointment does leave the Commission with only four members — two Democrats and two Republicans — until the President names a fifth commissioner, who must then be confirmed by the Senate. Under Ramirez, the FTC is likely to continue to advance its agenda on consumer privacy, especially in the areas of online and mobile privacy and data collection, and the Commission’s aggressive exercise of its enforcement authority in those and other areas of consumer protection. President Obama has not yet disclosed his pick for the open commissioner seat. Filling the seat is likely to be delayed, given the need for Senate confirmation.<BR><BR>Read our full alert on the appointment of Ramirez to chair of the FTC <A href="http://www.loeb.com/edithramirezelevatedchairfederaltradecommission/" target=_blank>here</A>.]]></description><pubDate>Tue, 05 Mar 2013 17:21:22 GMT</pubDate></item><item><guid>http://mediatechlaw.loeb.com/blog.aspx?entry=138</guid><title>Two California Privacy Bills Introduced </title><link>http://mediatechlaw.loeb.com/twocaliforniaprivacybillsintroduced/</link><description><![CDATA[California Assemblyman Isadore Hall introduced&nbsp;<A href="http://www.leginfo.ca.gov/pub/13-14/bill/asm/ab_0251-0300/ab_257_bill_20130207_introduced.pdf" target=_blank>Assembly Bill 257</A> which addresses mobile privacy. The bill would codify many of the best practices proposed by the California Attorney General in her report titled “<A href="http://oag.ca.gov/sites/all/files/pdfs/privacy/privacy_on_the_go.pdf" target=_blank>Privacy on the Go: Recommendations for the Mobile Ecosystem</A>,” such as requiring mobile apps to have a privacy policy; allowing consumers to access their own personally identifiable information (PII) that the app collects and retains; provide a supplemental privacy policy with enhanced measures if an app collects PII that is not essential to the app’s basic function; providing a special notice if the app accesses text messages, call logs, the camera, dialer or microphone, or collects location, financial, or medical information or passwords. The bill also would require advertising networks that deliver ads through a mobile application to obtain prior express consent before displaying an ad and before accessing PII; use application-specific or temporary device identifiers rather than unchangeable device-specific identifiers; and transmit user data securely, using encryption for permanent unique device identifiers and personal information.<BR><BR>A few weeks after the California Attorney General published her best practices for mobile privacy, members of the advertising industry&nbsp;<A href="http://gaia.adage.com/images/bin/pdf/TradeGroupLettertoCA1.10.13.pdf" target=_blank>sent her a letter</A> expressing their concerns, calling her recommendations “unworkable.” Since that time, the FTC released its own mobile privacy guidelines titled “<A href="http://www.ftc.gov/os/2013/02/130201mobileprivacyreport.pdf" target=_blank>Mobile Privacy Disclosures: Building Trust Through Transparency</A>” (which we summarized in an <A href="http://www.loeb.com/ftcguidelinesmobileprivacydisclosures/" target=_blank>alert</A>). The FTC also issued guidance for mobile security: <A href="http://business.ftc.gov/documents/bus83-mobile-app-developers-start-security" target=_blank>http://business.ftc.gov/documents/bus83-mobile-app-developers-start-security</A>.<BR><BR>California Assemblyman Ed Chau introduced&nbsp;<A href="http://www.leginfo.ca.gov/pub/13-14/bill/asm/ab_0201-0250/ab_242_bill_20130206_introduced.pdf" target=_blank>Assembly Bill 242</A> which would amend&nbsp;<A href="http://www.leginfo.ca.gov/cgi-bin/displaycode?section=bpc&amp;group=22001-23000&amp;file=22575-22579" target=_blank>California’s Online Privacy Protection Act</A> by requiring that privacy policies be no more than 100 words long, be written in clear and concise language that an eighth grader could read, and indicate whether PII may be sold or shared with others, and how and with whom the information may be shared.]]></description><pubDate>Wed, 13 Feb 2013 10:49:20 GMT</pubDate></item></channel></rss>