Blog post

On Security Data Sharing Research

By Anton Chuvakin | February 10, 2013 | 2 Comments

sharingsecuritydata

As I promised in my post On Security Data Sharing, we are starting a new research project on information security data sharing. Specifically, our research (joint with Dan Blum) will focus on how organizations can benefit from shared security data, what types of data can/should be shared, what are the barriers to sharing, what methods and protocols can be used and, most importantly, how to share/receive security data for enhancing your security defenses. We will look at the new commercial data sharing providers (RedSky, SecurityStarfish), ISACs (FS-, REN- … any others still alive?), and other organizations and will try to learn from both successes and failures (of which there are plenty, BTW).

So, here is my next call to action:

  • We have requested briefings from two commercial data sharing service providers and some ISACs. Other vendors, if you think you are closely related to security data sharing, got anything to say about it?  Here is a briefing link … you know what to do.
  • Enterprises, got a data sharing-related story to ..well… share? Hit the comments or email me privately (Gartner client NDA will cover it, if you are a client).

Related posts:

Comments are closed

2 Comments

  • Anton,
    This should be a productive and interesting discussion. I am interested to hear the differences between commercial information sharing for a fee, and information sharing from a funded organization serving the needs of Critical Infrastructure protection.

    Cheers!
    Glenn Merrell, CAP
    ICS-ISAC.org Workforce Development Director / Advisor

  • First, thanks for the comment. If you are involved with ICS-ISAC, would you consider briefing us on its status, etc via http://www.gartner.com/it/about/vbriefings_faq.jsp

    Second, we’d be exploring this (commercial vs “public” sharing) and other issues in this multi-decade saga (started in 1998 with PDD63 if not earlier) towards information sharing.