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.

When It Comes To Cyberthreat Intelligence, Sharing Is Caring
Newest First  |  Oldest First  |  Threaded View
User Rank: Author
4/12/2016 | 6:08:44 AM
Maybe not WHAT but HOW
In theory, the idea of sharing threat intel makes all the sense in the world. As you touched on, the problem in cybersecurity is that you're talking about anonymous adversaries that are constantly changing. While it is important to know file hashes, IPs and some email addresses to block, that system is based on limited data and not exact. Additionally, threats are constantly morphing and changing, so by the time you've identified one, it has already changed. Furthermore, if the bad guys are getting the same threat feed as everyone else, they'll be able to change their attacks in real-time and will see whether they're getting caught -- it's like giving them a real-time tool to check whether their attacks are able to bypass detection systems.

Perhaps the issue isn't WHAT companies are willing to share, but HOW they're willing to share it. For example:

  • What if threat feeds were only machine-to-machine accessible? For instance, if the threat intel was shared in a machine readable format to a SIEM, then only those companies that have detection systems could use that information. It's unlikely that a scammer is going to buy an expensive system to check their work. And if we're talking about systems instead of people, the question then becomes: how do these systems share the information back?
  • What if we could de-couple the organization from the threat, and there was no way to associate the two? Maybe then companies wouldn't have an issue with a system reporting findings back to the mother ship.
  • What if opt-in isn't the right way to go about information sharing? When companies need to opt in to share data, overabundance of caution may get the best of them. On the other hand, if they're already sharing information (albeit anonymously), would that change their mindset?


COVID-19: Latest Security News & Commentary
Dark Reading Staff 5/28/2020
Stay-at-Home Orders Coincide With Massive DNS Surge
Robert Lemos, Contributing Writer,  5/27/2020
Register for Dark Reading Newsletters
White Papers
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: Can you smell me now?
Current Issue
How Cybersecurity Incident Response Programs Work (and Why Some Don't)
This Tech Digest takes a look at the vital role cybersecurity incident response (IR) plays in managing cyber-risk within organizations. Download the Tech Digest today to find out how well-planned IR programs can detect intrusions, contain breaches, and help an organization restore normal operations.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
PUBLISHED: 2020-05-29
There is an Incorrect Authorization vulnerability in Micro Focus Service Management Automation (SMA) product affecting version 2018.05 to 2020.02. The vulnerability could be exploited to provide unauthorized access to the Container Deployment Foundation.
PUBLISHED: 2020-05-29
A Denial of Service vulnerability in MuleSoft Mule CE/EE 3.8.x, 3.9.x, and 4.x released before April 7, 2020, could allow remote attackers to submit data which can lead to resource exhaustion.
PUBLISHED: 2020-05-29
All versions of snyk-broker before 4.72.2 are vulnerable to Arbitrary File Read. It allows arbitrary file reads for users who have access to Snyk's internal network by appending the URL with a fragment identifier and a whitelisted path e.g. `#package.json`
PUBLISHED: 2020-05-29
All versions of snyk-broker after 4.72.0 including and before 4.73.1 are vulnerable to Arbitrary File Read. It allows arbitrary file reads to users with access to Snyk's internal network of any files ending in the following extensions: yaml, yml or json.
PUBLISHED: 2020-05-29
All versions of snyk-broker before 4.73.1 are vulnerable to Information Exposure. It logs private keys if logging level is set to DEBUG.