DataBreaches.Net

Menu
  • About
  • Breach Notification Laws
  • Privacy Policy
  • Transparency Report
Menu

Quinn Norton: We Should All Step Back from Security Journalism. I’ll Go First.

Posted on January 28, 2015 by Dissent

Last week, Quinn Norton wrote a disturbing and thoughtful essay. Those of us who conduct research or investigate and report on breaches generally share her concerns, if not her decision to withdraw from security journalism.  The Barrett Brown case, and the prosecution’s attempt to criminalize linking to publicly available data may lead others, too, to pull back from investigating or reporting. And on some level, I suspect that’s exactly what the DOJ wanted/wants to happen – we’ll get scared of prosecution and not investigate or report as we otherwise might. 

Quinn writes, in part:

Part of Barrett Brown’s 63 month sentence, issued yesterday, is a 12 month sentence for a count of Accessory After the Fact, of the crime of hacking Stratfor. This sentence was enhanced by Brown’s posting a link in chat and possessing credit card data. This, and a broad pattern of misunderstanding and criminalizing normal behavior online, has lead me to feel that the situation for journalists and security researchers is murky and dangerous.

I am stepping back from reporting on hacking/databreach stories, and restricting my assistance to other journalists to advice. (But please, journalists, absolutely feel free to ask me for advice!) I can’t look at the specific data another journalist has, and I can’t pass it along to a security expert, without feeling like there’s risk to the journalists I work with, the security experts, and myself.

I know some of my activist hacker contacts will find this cowardly of me. Many of them risk much more than this in the course of their lives, but I have two replies to this. One is that I have a family to care for including a child, and I can’t ask them to enter this murky legal territory. The other is that my causes are often not the same as the causes I write about, and I feel I best serve my causes by stepping back and highlighting this problem of law to the public.

Read her whole essay on Medium.

This blog and blogger already had a policy of not linking to data dumps, a policy that flows from the notion of protecting personal information and not adding to people’s woes by pointing readers to exposed personal, and sometimes sensitive, information.  If a post does link to hacked data, such as tables structure, etc., I suppose the government could try to prosecute me as an accessory after-the-fact. If they do, I hope all the great First Amendment attorneys I know will step in to help.

Until then, it will be business as usual here, but I am saddened to read Quinn’s decision, even though I do understand her concerns. We have lost a great security journalist.

 

No related posts.

Category: Breach LawsCommentaries and AnalysesOf Note

Post navigation

← UK: ICO reports on community healthcare providers’ data protection
No jail time for cop who stole and shared suspects’ nudes →

Now more than ever

"Stand with Ukraine:" above raised hands. The illustration is in blue and yellow, the colors of Ukraine's flag.

Search

Browse by Categories

Recent Posts

  • Russia Jailed Hacker Who Worked for Ukrainian Intelligence to Launch Cyberattacks on Critical Infrastructure
  • Kentfield Hospital victim of cyberattack by World Leaks, patient data involved
  • India’s Max Financial says hacker accessed customer data from its insurance unit
  • Brazil’s central bank service provider hacked, $140M stolen
  • Iranian and Pro-Regime Cyberattacks Against Americans (2011-Present)
  • Nigerian National Pleads Guilty to International Fraud Scheme that Defrauded Elderly U.S. Victims
  • Nova Scotia Power Data Breach Exposed Information of 280,000 Customers
  • No need to hack when it’s leaking: Brandt Kettwick Defense edition
  • SK Telecom to be fined for late data breach report, ordered to waive cancellation fees, criminal investigation into them launched
  • Louis Vuitton Korea suffers cyberattack as customer data leaked

No, You Can’t Buy a Post or an Interview

This site does not accept sponsored posts or link-back arrangements. Inquiries about either are ignored.

And despite what some trolls may try to claim: DataBreaches has never accepted even one dime to interview or report on anyone. Nor will DataBreaches ever pay anyone for data or to interview them.

Want to Get Our RSS Feed?

Grab it here:

https://databreaches.net/feed/

RSS Recent Posts on PogoWasRight.org

  • On July 7, Gemini AI will access your WhatsApp and more. Learn how to disable it on Android.
  • German court awards Facebook user €5,000 for data protection violations
  • Record-Breaking $1.55M CCPA Settlement Against Health Information Website Publisher
  • Ninth Circuit Reviews Website Tracking Class Actions and the Reach of California’s Privacy Law
  • US healthcare offshoring: Navigating patient data privacy laws and regulations
  • Data breach reveals Catwatchful ‘stalkerware’ is spying on thousands of phones
  • Google Trackers: What You Can Actually Escape And What You Can’t

Have a News Tip?

Email: Tips[at]DataBreaches.net

Signal: +1 516-776-7756

Contact Me

Email: info[at]databreaches.net

Mastodon: Infosec.Exchange/@PogoWasRight

Signal: +1 516-776-7756

DMCA Concern: dmca[at]databreaches.net
© 2009 – 2025 DataBreaches.net and DataBreaches LLC. All rights reserved.