Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Comments
Threat Intelligence Sharing: The New Normal?
Oldest First  |  Newest First  |  Threaded View
Page 1 / 2   >   >>
cybersavior
50%
50%
cybersavior,
User Rank: Strategist
6/23/2017 | 11:38:43 AM
Comment:
The hardship in "crowdsourcing" threat intelligence is this.  On one hand, a corporation doesn't want to share intimate details of attacks and vectors it has seen (and perhaps suffered from).  It's not something you advertise.  On the other hand, it's natural to want similar data from other companies to use to advantage. 

Until a dedicated exchange or forum exists (besides the existing tools that mesh subscriber detections today) that anonymizes the reporting entity sources, we won't see any real open collaboration.  The fundamental problem in this interchange model is that the closer you get to anonymity the farther you get from assurance and authenticity.  Meaning, the reliability of threat articulation from an anonymous source is less than a vetted representative from "MegaCorp, LLC" proper.  This could be overcome by a intermediate, sanctioned broker to ensure the reporting entity is genuine.

Until the exchange mechanism is sexy and "now" it won't work either.  The threat intelligence collaboration and sharing service needs to solidly be edgy social media.  Think "HackedIn" and not some cold, corporate or government offering that reads like RFC's and NIST documentation.

Until the threat intelligence interchange is highly automated, it won't be accepted.  MegaCorp is not going to dedicate service agents or ongoing labor to the contributions nor consuming content.  If the end-all solution doesn't facilitate fast-flux transactions in both directions and provide actionable output that itself can be automated, it won't be widely adopted.
RetiredUser
100%
0%
RetiredUser,
User Rank: Ninja
6/24/2017 | 6:20:43 PM
Re: Comment:
I have to agree.  Coming from the healthcare industry (currently) we see great value in partnerships with other medical organizations, from pharmacy to radiology to hospitals.  By setting up "health information exchanges" (HIE) with vetted partners, we feel confident the data we exchange is mostly clean, true and of interest.  This is key for me especially since the data I share and receive is tech-related.

A similar model for threat intelligence is really crucial.  Where HIEs are trying to save lives by increasing access to health data, corporations could be saving millions/billions/trillions of dollars for their customers by keeping major corps up-to-date with exploits as they are discovered - immediate and before any other groups outside the initial penetrator(s) are aware.     
Dr.T
50%
50%
Dr.T,
User Rank: Ninja
6/26/2017 | 2:38:02 PM
Threat Intelligence Sharing: The New Normal
I would like it not to be a new normal but given the situation, threat intelligence sharing would be quite helpful for the communities.
Dr.T
50%
50%
Dr.T,
User Rank: Ninja
6/26/2017 | 2:39:55 PM
Re: Comment:
"a corporation doesn't want to share intimate details of attacks and vectors"

That makes sense, it is going to be hard to share the threats that the company encountered and  what they did about it. 
Dr.T
50%
50%
Dr.T,
User Rank: Ninja
6/26/2017 | 2:42:27 PM
Re: Comment:
"MegaCorp is not going to dedicate service agents or ongoing labor to the contributions nor consuming content."

That makes sense. At the same time, if thread management is already done sharing information would not be taking that much time. I see your point tough.
Dr.T
50%
50%
Dr.T,
User Rank: Ninja
6/26/2017 | 2:45:45 PM
Re: Comment:
"health information exchanges"

I see your point. Health organization would want to do this since it reduces workload for the organization itself, and it is just sensitive information not anything related to threats.
Dr.T
50%
50%
Dr.T,
User Rank: Ninja
6/26/2017 | 2:48:02 PM
Re: Comment:
"A similar model for threat intelligence is really crucial"

I agree, automation would really help. I am not sure if any organization would bear the initial setup cost, unless there is sum subsidy it is most likely not going to happen.
Joe Stanganelli
100%
0%
Joe Stanganelli,
User Rank: Ninja
6/26/2017 | 6:34:10 PM
Fin Svcs
To be sure, the financial-services sector in particular has -- after an all too long period of siloed silence -- been heartily embracing threat sharing. These days, in fact, the talk seems to be less about "old-style" threat sharing and more about an elevated approach they dub "collaborative defense" -- with organizations working together on problems.

Of course, this is usually evangelized by and conducted through "non-profit" organizations that charge mega-large annual fees for membership. Threat sharing is big business.
Joe Stanganelli
50%
50%
Joe Stanganelli,
User Rank: Ninja
6/26/2017 | 6:36:08 PM
Re: Comment:
Of course, there is an economic cost and economic value to everything, monetary or not -- consumer privacy included. At the end of the day, those interests still need to be balanced appropriately lest there be significant customer backlash.
HardenStance
50%
50%
HardenStance,
User Rank: Strategist
6/28/2017 | 5:27:58 AM
Nice piece, couple of remarks
Couple of remarks.

First, thanks for a nice piece on a REALLY important area. 

We're at the foot of a mountain relative to where we need to be on threat intel sharing.

We need a lot more of it, although there's a significant risk that if the number of organizations facilitating it continues to proliferate we could end up with a sharing infrastructure that is too complex and unwieldy.

Thanks too for drawing attention to ISAO. I hadn't heard of that organization but they seem to be performing a useful function in recording and tracking the many threat sharing organizations.

Last, I've had an opportunity to meet with some of the leaders of the Cyber Threat Alliance in recent weeks. They seem to me to be pretty advanced in what they're doing and where they're going with the support of many of the big beasts of the cyber security vendor community.

Over time the market needs to evolve from one in which actors can differentiate according to what they know to one in which what's known is an increasingly level playing field and actors instead compete around how quickly, how universally and how effectively they are able to respond before, during and after an attack.

 

 

  
Page 1 / 2   >   >>


Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
6 Emerging Cyber Threats That Enterprises Face in 2020
This Tech Digest gives an in-depth look at six emerging cyber threats that enterprises could face in 2020. Download your copy today!
Flash Poll
State of Cybersecurity Incident Response
State of Cybersecurity Incident Response
Data breaches and regulations have forced organizations to pay closer attention to the security incident response function. However, security leaders may be overestimating their ability to detect and respond to security incidents. Read this report to find out more.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-15789
PUBLISHED: 2020-04-08
Privilege escalation vulnerability in MicroK8s allows a low privilege user with local access to obtain root access to the host by provisioning a privileged container. Fixed in MicroK8s 1.15.3.
CVE-2020-10633
PUBLISHED: 2020-04-08
A non-persistent XSS (cross-site scripting) vulnerability exists in eWON Flexy and Cosy (all firmware versions prior to 14.1s0). An attacker could send a specially crafted URL to initiate a password change for the device. The target must introduce the credentials to the gateway before the attack can...
CVE-2020-10366
PUBLISHED: 2020-04-08
LogicalDoc before 8.3.3 allows /servlet.gupld Directory Traversal, a different vulnerability than CVE-2020-9423 and CVE-2020-10365.
CVE-2020-11543
PUBLISHED: 2020-04-08
OpsRamp Gateway 3.0.0 has a backdoor account vadmin with the password [email protected] that allows root SSH access to the server.
CVE-2020-11626
PUBLISHED: 2020-04-08
An issue was discovered in EJBCA before 6.15.2.6 and 7.x before 7.3.1.2. Two Cross Side Scripting (XSS) vulnerabilities have been found in the Public Web and the Certificate/CRL download servlets.