Risk
2/2/2007
12:11 PM
50%
50%

How We Could Protect Pre-Teens Online

Are you familiar with COPPA, the Children's Online Privacy Protection Act? It's a worthy bill, aimed at preventing the online collection of personal information from children under 13 years of age. What most people don't know is, it's turned out to be rather cumbersome for companies to comply with. The result has been that there are few social networking sites which provide a safe place from pre-teens to hang out and chat.

Are you familiar with COPPA, the Children's Online Privacy Protection Act? It's a worthy bill, aimed at preventing the online collection of personal information from children under 13 years of age. What most people don't know is, it's turned out to be rather cumbersome for companies to comply with. The result has been that there are few social networking sites which provide a safe place from pre-teens to hang out and chat.COPPA's regulations mandate certain things in a Web site's privacy policy, when parental consent is required, and what a site's responsibilities are when they offer services to those under 13. Sure, children can simply lie about their age to register. Any many do, as a trip to MySpace will quickly prove. Interestingly, if you look deeper within the profile pages at MySpace and other similar sites, you'll often find that kids tell their true ages, which are often lower than the minimum required to register.

What I'm proposing is, what if we encourage kids of a certain age to gather together and chat in appropriately monitored venues (not necessarily MySpace, but other, as yet unestablished sites)? If done correctly, it could provide safe gathering places where kids can gather completely separated from the sometimes sewer-like atmosphere of the sites used by high-schoolers and young adults.

Here's my idea: What if the minimum age wasn't the gating factor, but that the controls allowed only children of a certain age group to talk together. For example, you couldn't be older than 14 to talk to kids between 10-14 and you could effectively block kids who were younger than that from using a site. And let's say you didn't need to install software on you own PC to do that, that this would be universal. No child could get on an inappropriate site via any computer. How? It's a controversial idea, but one that needs to be discussed: the Social Security number.

If this idea is implemented properly, a child's identity won't be compromised. "This could be easily done via a third-party government agency," Brandon Watson, founder of IMSafer, told me in my investigation into this issue. IMSafer is software and a service that monitors IM traffic for text that's likely coming from (or going to) a predator or pedophile, and sends an e-mail alert to the person who set up the service.

"The idea could be, for a particular site, that if you want to sign up, you enter in your Social Security Number, and maybe one other identifier, say your town, to ensure the number is not a duplicate," Watson said. "Say the service might have a rule for that site that a user has to be older than 16. The service wouldn't store it, wouldn't do anything but say yea or nay."

There it is, as easy as pie. A simple approved/not approved solution. Every time your kid wanted to register, he or she would go through the process through this third party, the site would be apprised of his or her approval status, and admittance would be gained or denied. Same for the predators.

Of course, there is worry that the numbers would be stored, stolen, etc. But I am afraid that all the lawsuits against social networking sites, all the Congressional hearings, and all the good intentions in the world are not going to be as effective a solution. Just asking the predators for their birth dates isn't a solution. Remember, they are bad guys, and bad guys lie. There is a solution. We now need to implement the technology and the rules to make it do exactly what we want it to do: Protect children without compromising their privacy.

Comment  | 
Print  | 
More Insights
Register for Dark Reading Newsletters
White Papers
Cartoon
Current Issue
Dark Reading Tech Digest, Dec. 19, 2014
Software-defined networking can be a net plus for security. The key: Work with the network team to implement gradually, test as you go, and take the opportunity to overhaul your security strategy.
Flash Poll
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2014-3580
Published: 2014-12-18
The mod_dav_svn Apache HTTPD server module in Apache Subversion 1.x before 1.7.19 and 1.8.x before 1.8.11 allows remote attackers to cause a denial of service (NULL pointer dereference and server crash) via a REPORT request for a resource that does not exist.

CVE-2014-4801
Published: 2014-12-18
Cross-site scripting (XSS) vulnerability in IBM Rational Quality Manager 2.x through 2.0.1.1, 3.x before 3.0.1.6 iFix 4, 4.x before 4.0.7 iFix 2, and 5.x before 5.0.1 allows remote authenticated users to inject arbitrary web script or HTML via a crafted URL.

CVE-2014-6076
Published: 2014-12-18
IBM Security Access Manager for Mobile 8.x before 8.0.1 and Security Access Manager for Web 7.x before 7.0.0 FP10 and 8.x before 8.0.1 allow remote attackers to conduct clickjacking attacks via a crafted web site.

CVE-2014-6077
Published: 2014-12-18
Cross-site request forgery (CSRF) vulnerability in IBM Security Access Manager for Mobile 8.x before 8.0.1 and Security Access Manager for Web 7.x before 7.0.0 FP10 and 8.x before 8.0.1 allows remote attackers to hijack the authentication of arbitrary users for requests that insert XSS sequences.

CVE-2014-6078
Published: 2014-12-18
IBM Security Access Manager for Mobile 8.x before 8.0.1 and Security Access Manager for Web 7.x before 7.0.0 FP10 and 8.x before 8.0.1 do not have a lockout period after invalid login attempts, which makes it easier for remote attackers to obtain admin access via a brute-force attack.

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
Join us Wednesday, Dec. 17 at 1 p.m. Eastern Time to hear what employers are really looking for in a chief information security officer -- it may not be what you think.