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
When It Comes To Cyberthreat Intelligence, Sharing Is Caring
Newest First  |  Oldest First  |  Threaded View
nathanwburke
nathanwburke,
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?

 


Edge-DRsplash-10-edge-articles
I Smell a RAT! New Cybersecurity Threats for the Crypto Industry
David Trepp, Partner, IT Assurance with accounting and advisory firm BPM LLP,  7/9/2021
News
Attacks on Kaseya Servers Led to Ransomware in Less Than 2 Hours
Robert Lemos, Contributing Writer,  7/7/2021
Commentary
It's in the Game (but It Shouldn't Be)
Tal Memran, Cybersecurity Expert, CYE,  7/9/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Practical Network Security Approaches for a Multicloud, Hybrid IT World
The report covers areas enterprises should focus on for their multicloud/hybrid cloud security strategy: -increase visibility over the environment -learning cloud-specific skills -relying on established security frameworks -re-architecting the network
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2022-30333
PUBLISHED: 2022-05-09
RARLAB UnRAR before 6.12 on Linux and UNIX allows directory traversal to write to files during an extract (aka unpack) operation, as demonstrated by creating a ~/.ssh/authorized_keys file. NOTE: WinRAR and Android RAR are unaffected.
CVE-2022-23066
PUBLISHED: 2022-05-09
In Solana rBPF versions 0.2.26 and 0.2.27 are affected by Incorrect Calculation which is caused by improper implementation of sdiv instruction. This can lead to the wrong execution path, resulting in huge loss in specific cases. For example, the result of a sdiv instruction may decide whether to tra...
CVE-2022-28463
PUBLISHED: 2022-05-08
ImageMagick 7.1.0-27 is vulnerable to Buffer Overflow.
CVE-2022-28470
PUBLISHED: 2022-05-08
marcador package in PyPI 0.1 through 0.13 included a code-execution backdoor.
CVE-2022-1620
PUBLISHED: 2022-05-08
NULL Pointer Dereference in function vim_regexec_string at regexp.c:2729 in GitHub repository vim/vim prior to 8.2.4901. NULL Pointer Dereference in function vim_regexec_string at regexp.c:2729 allows attackers to cause a denial of service (application crash) via a crafted input.