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?
Newest First  |  Oldest First  |  Threaded View
Page 1 / 2   >   >>
Agate
50%
50%
Agate,
User Rank: Apprentice
11/29/2017 | 6:44:53 AM
Re: Nice piece, couple of remarks to from Agate
You are right.

But whithout international cooperation, what about a worlwide attack ?

Agate
WoW100
50%
50%
WoW100,
User Rank: Apprentice
7/8/2017 | 5:10:48 AM
Re: Comment: Social Media
I think the same, the intelligence sharing can really help some poor countries, so i support it.
DanelleA058
50%
50%
DanelleA058,
User Rank: Apprentice
6/28/2017 | 8:50:49 PM
Re: Comment:
Thank you for reading my article. 

Agree with the comments you made. Context is everything with threat intel, along with automation. 

I talk about the need for these three elements here-- sharing, processing and responding here:  https://www.darkreading.com/attacks-breaches/hacking-forward-with-weaponized-intelligence-/a/d-id/1326955?
  1. Sharing: There must be a way for organizations to share meaningful threat intelligence using a common format that makes things easy to understand and correlate based on common factors such as industry, but that does not reveal the contributor's confidential information. If there is no trust within the system, it simply will not succeed.
  2. Processing: As inbound volumes of threat intelligence increase there's a real risk of being overwhelmed by big data, meaning users of threat intelligence will be right back where they started, ignoring signals because of an abundance of false positives. Making threat intelligence actionable means processing the data in more practical ways, including tracking indicators of compromise to see not just how they start, but to understand how they play out using new methods like breach simulations.
  3. Responding: The true value of actionable threat intelligence is not simply in distinguishing real threats from false positives, but in speeding incident response time. The longer a threat goes undisrupted, the greater the chance for damage; once a hacker reaches the target, the more damage they can do. Security teams must learn to act, but automation must be a part of the solution in order to cut response times from days and months down to minutes and seconds.
DanelleA058
50%
50%
DanelleA058,
User Rank: Apprentice
6/28/2017 | 8:45:36 PM
Re: Nice piece, couple of remarks
Thank you for reading my article. I agree the Cyber Threat Alliance is doing great things and they do have a great set of participating security vendors. I should have included them in the article as well. 

Additionally, one of the interesting ways of operationalizing threat intelligence is via breach and attack simulations -- ie. by transforming indicators of compromise to breach methods to see how an attack might play out in an environment. I think this might address some of the issues you raised, which is how we can respond quicker to an attack. 
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.

 

 

  
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.
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.
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.
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: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.
Page 1 / 2   >   >>


Exploits Released for As-Yet Unpatched Critical Citrix Flaw
Jai Vijayan, Contributing Writer,  1/13/2020
Major Brazilian Bank Tests Homomorphic Encryption on Financial Data
Kelly Sheridan, Staff Editor, Dark Reading,  1/10/2020
Will This Be the Year of the Branded Cybercriminal?
Raveed Laeb, Product Manager at KELA,  1/13/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
The Year in Security: 2019
This Tech Digest provides a wrap up and overview of the year's top cybersecurity news stories. It was a year of new twists on old threats, with fears of another WannaCry-type worm and of a possible botnet army of Wi-Fi routers. But 2019 also underscored the risk of firmware and trusted security tools harboring dangerous holes that cybercriminals and nation-state hackers could readily abuse. Read more.
Flash Poll
[Just Released] How Enterprises are Attacking the Cybersecurity Problem
[Just Released] How Enterprises are Attacking the Cybersecurity Problem
Organizations have invested in a sweeping array of security technologies to address challenges associated with the growing number of cybersecurity attacks. However, the complexity involved in managing these technologies is emerging as a major problem. Read this report to find out what your peers biggest security challenges are and the technologies they are using to address them.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-3682
PUBLISHED: 2020-01-17
The docker-kubic package in SUSE CaaS Platform 3.0 before 17.09.1_ce-7.6.1 provided access to an insecure API locally on the Kubernetes master node.
CVE-2019-17361
PUBLISHED: 2020-01-17
In SaltStack Salt through 2019.2.0, the salt-api NEST API with the ssh client enabled is vulnerable to command injection. This allows an unauthenticated attacker with network access to the API endpoint to execute arbitrary code on the salt-api host.
CVE-2019-19142
PUBLISHED: 2020-01-17
Intelbras WRN240 devices do not require authentication to replace the firmware via a POST request to the incoming/Firmware.cfg URI.
CVE-2019-19801
PUBLISHED: 2020-01-17
In Gallagher Command Centre Server versions of v8.10 prior to v8.10.1134(MR4), v8.00 prior to v8.00.1161(MR5), v7.90 prior to v7.90.991(MR5), v7.80 prior to v7.80.960(MR2) and v7.70 or earlier, an unprivileged but authenticated user is able to perform a backup of the Command Centre databases.
CVE-2019-19802
PUBLISHED: 2020-01-17
In Gallagher Command Centre Server v8.10 prior to v8.10.1134(MR4), v8.00 prior to v8.00.1161(MR5), v7.90 prior to v7.90.991(MR5), v7.80 prior to v7.80.960(MR2) and v7.70 or earlier, an authenticated user connecting to OPCUA can view all data that would be replicated in a multi-server setup without p...