Commentary

John Foley
Editor, InformationWeek  

Google's Blind Eye On Child Porn

A politician in Nassau County, New York, has called Google on its dirty little secret. County rep Jeffrey Toback is suing Google for failing to block child porn and for profiting by placing ads alongside the illicit content. Toback may be right, but he's missing a key point that makes the issue more complicated. Law enforcement officials know Google is used by child pornographers and pedophiles, but rather than clamp down, they've been using Google themselves to pursue the bad guys.

A politician in Nassau County, New York, has called Google on its dirty little secret. County rep Jeffrey Toback is suing Google for failing to block child porn and for profiting by placing ads alongside the illicit content. Toback may be right, but he's missing a key point that makes the issue more complicated. Law enforcement officials know Google is used by child pornographers and pedophiles, but rather than clamp down, they've been using Google themselves to pursue the bad guys.Google doesn't deny that child pornography can be accessed from its site. There are billions of images in Google's image database, and somewhere in that haystack are pictures of kids being sexually assaulted and exploited. It's merely a matter of using the right search terms to find them.

Google, in its defense, points out that its policy prohibits child pornography and that it offers a user-controlled filter to block sexually explicit content. If and when Google learns of suspected child pornography in its index, the company removes the offending material and cooperates with law enforcement in any legal action related to it.


More Internet Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

But Google's strategy is deliberately and decidedly passive. Google doesn't actively scan its image database for child pornography, nor does the company block words or phrases known to be used by child-porn consumers and traffickers. For example, Google could block the search phase "sex with girls" or "naked little boys," but it doesn't do that. (I haven't personally searched those terms, so I can't vouch for what would show up, and I don't recommend you try it, either. You get the point.)

I've been following Google's child-porn policy for more than a year. Last year in "Technology And The Fight Against Child Porn," InformationWeek reported on the startling rise of online child pornography. In a related story, we asked, "Should Google filter child porn from its image database?"

The answer, according to some experts, was that Google's passive approach to child pornography is helpful for two reasons: One, law enforcement officials use Google to find child porn as part of their investigative work. And two, Google's cache can be useful in tracking the shady characters and Web site operators who keep this ugly business going. A special agent with Homeland Security's U.S. Immigration and Customs Enforcement division, which pursues child pornographers, told us, "The majority of people in my group use Google" in their work.

So there's the catch in Rep. Toback's legal maneuver. The question in my mind is whether Google is doing more harm than good with its hands-off approach to child pornography, but that's hard to answer. Google officials won't say how often they've worked with law enforcement officials on child-porn cases or discuss the number of arrests or prosecutions that may have resulted. "We do not share information about law enforcement requests," says a Google spokesman.

Without that information, it's impossible to know whether Google's strategy in dealing with child porn is effective. On this issue of child safety and welfare, Google needs to be more forthcoming.


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links