Risk
7/2/2013
06:58 PM
Connect Directly
RSS
E-Mail
50%
50%
Repost This

Child Privacy Online: FTC Updates COPPA Rules

Children's Online Privacy Protection Act of 1998 expands to regulate behavioral tracking, plus geolocation data, photos, videos and audio recordings made by kids under 13.

The Syrian Electronic Army: 9 Things We Know
(click image for larger view)
The Syrian Electronic Army: 9 Things We Know
The Federal Trade Commission said this week that revised rules for the Children's Online Privacy Protection Act of 1998 (COPPA) have taken effect.

COPPA, which the FTC enforces, prohibits anyone from knowingly collecting personal information on children under the age of 13, without first obtaining their parents' verifiable consent. COPPA also requires sites to post clear, complete and accessible privacy policies, and to secure any children's information they collect. The rule first went into effect in 2000.

"At the FTC, protecting children's privacy is a top priority," said FTC chairwoman Edith Ramirez in a statement. "The updated COPPA rule helps put parents in charge of their children's personal information as it keeps pace with changing technologies."

Since COPPA was first written, notions of what constitutes an online site or service, as well as data collection practices, have evolved substantially, not least due to the rise of mobile computing and social networking. Also relatively new is behavioral tracking, which can record what users do across multiple sites.

[ Should search engines be held responsible for listing harmful websites? Read Google Launches Attack On Online Child Pornography. ]

On the latter front, the new final rule amendments to COPPA now "make clear that the rule covers an operator of a child-directed site or service where it integrates outside services, such as plug-ins or advertising networks, that collect personal information from its visitors."

The revision also updates the FTC's definition of personal information "to include geolocation information and persistent identifiers that can be used to recognize a user over time and across different websites or online services," as well as photos, videos and audio recordings. That said, COPPA also relies on children self-reporting their age, and exonerates businesses that don't provide notification or obtain parental consent if a child reports his age is 13 or above.

Before the new rules took effect, the FTC already had signaled that COPPA applied not only to websites, but also smartphone apps and the greater mobile and advertising ecosystem. In 2011, for example, the FTC filed its first-ever smartphone-related COPPA complaint, against W3 Innovations, as well as its owner and president. The agency charged them with failing to comply with COPPA's parental notification and consent requirements. According to the complaint, W3 -- developer of such iOS titles as "Emily's Dress Up and Shop," "Santa's Run" and "Zombie Duck Hunt" -- also "allowed children to publicly post information, including personal information, on message boards."

Which businesses must comply with COPPA? To help organizations answer that question, the FTC released "A Six-Step Compliance Plan for Your Business" guide. The agency also maintains a "COPPA hotline" email address, COPPAHotLine@ftc.gov, to field businesses' related compliance questions.

The FTC is also continuing five safe-harbor programs that assess business's COPPA compliance, now based on the updated rules.

"Under COPPA, safe harbor status allows certain organizations to create comprehensive self-compliance programs for their members," said the FTC in a press release. "Companies that participate in a COPPA safe harbor program are generally subject to the review and disciplinary procedures provided in the safe harbor's guidelines in lieu of formal FTC investigation and law enforcement."

Such safe-harbor programs are offered by Aristotle International, the Children's Advertising Review Unit of the Council of Better Business Bureaus, ESRB Privacy Online, Privo and TRUSTe.

Comment  | 
Print  | 
More Insights
Register for Dark Reading Newsletters
White Papers
Flash Poll
Current Issue
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2011-3154
Published: 2014-04-17
DistUpgrade/DistUpgradeViewKDE.py in Update Manager before 1:0.87.31.1, 1:0.134.x before 1:0.134.11.1, 1:0.142.x before 1:0.142.23.1, 1:0.150.x before 1:0.150.5.1, and 1:0.152.x before 1:0.152.25.5 does not properly create temporary files, which allows local users to obtain the XAUTHORITY file conte...

CVE-2013-2143
Published: 2014-04-17
The users controller in Katello 1.5.0-14 and earlier, and Red Hat Satellite, does not check authorization for the update_roles action, which allows remote authenticated users to gain privileges by setting a user account to an administrator account.

CVE-2014-0036
Published: 2014-04-17
The rbovirt gem before 0.0.24 for Ruby uses the rest-client gem with SSL verification disabled, which allows remote attackers to conduct man-in-the-middle attacks via unspecified vectors.

CVE-2014-0054
Published: 2014-04-17
The Jaxb2RootElementHttpMessageConverter in Spring MVC in Spring Framework before 3.2.8 and 4.0.0 before 4.0.2 does not disable external entity resolution, which allows remote attackers to read arbitrary files, cause a denial of service, and conduct CSRF attacks via crafted XML, aka an XML External ...

CVE-2014-0071
Published: 2014-04-17
PackStack in Red Hat OpenStack 4.0 does not enforce the default security groups when deployed to Neutron, which allows remote attackers to bypass intended access restrictions and make unauthorized connections.

Best of the Web