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   >   >>


COVID-19: Latest Security News & Commentary
Dark Reading Staff 9/25/2020
Hacking Yourself: Marie Moe and Pacemaker Security
Gary McGraw Ph.D., Co-founder Berryville Institute of Machine Learning,  9/21/2020
Startup Aims to Map and Track All the IT and Security Things
Kelly Jackson Higgins, Executive Editor at Dark Reading,  9/22/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Special Report: Computing's New Normal
This special report examines how IT security organizations have adapted to the "new normal" of computing and what the long-term effects will be. Read it and get a unique set of perspectives on issues ranging from new threats & vulnerabilities as a result of remote working to how enterprise security strategy will be affected long term.
Flash Poll
How IT Security Organizations are Attacking the Cybersecurity Problem
How IT Security Organizations are Attacking the Cybersecurity Problem
The COVID-19 pandemic turned the world -- and enterprise computing -- on end. Here's a look at how cybersecurity teams are retrenching their defense strategies, rebuilding their teams, and selecting new technologies to stop the oncoming rise of online attacks.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-15208
PUBLISHED: 2020-09-25
In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, when determining the common dimension size of two tensors, TFLite uses a `DCHECK` which is no-op outside of debug compilation modes. Since the function always returns the dimension of the first tensor, malicious attackers can ...
CVE-2020-15209
PUBLISHED: 2020-09-25
In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, a crafted TFLite model can force a node to have as input a tensor backed by a `nullptr` buffer. This can be achieved by changing a buffer index in the flatbuffer serialization to convert a read-only tensor to a read-write one....
CVE-2020-15210
PUBLISHED: 2020-09-25
In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, if a TFLite saved model uses the same tensor as both input and output of an operator, then, depending on the operator, we can observe a segmentation fault or just memory corruption. We have patched the issue in d58c96946b and ...
CVE-2020-15211
PUBLISHED: 2020-09-25
In TensorFlow Lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, saved models in the flatbuffer format use a double indexing scheme: a model has a set of subgraphs, each subgraph has a set of operators and each operator has a set of input/output tensors. The flatbuffer format uses indices f...
CVE-2020-15212
PUBLISHED: 2020-09-25
In TensorFlow Lite before versions 2.2.1 and 2.3.1, models using segment sum can trigger writes outside of bounds of heap allocated buffers by inserting negative elements in the segment ids tensor. Users having access to `segment_ids_data` can alter `output_index` and then write to outside of `outpu...