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
How Machine Learning, AI & Deep Learning Improve Cybersecurity
Machine intelligence is influencing all aspects of cybersecurity. Organizations are implementing AI-based security to analyze event data using ML models that identify attack patterns and increase automation. Before security teams can take advantage of AI and ML tools, they need to know what is possible. This report covers: -How to assess the vendor's AI/ML claims -Defining success criteria for AI/ML implementations -Challenges when implementing AI
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2022-3074
PUBLISHED: 2022-09-26
The Slider Hero WordPress plugin before 8.4.4 does not escape the slider Name, which could allow high-privileged users to perform Cross-Site Scripting attacks.
CVE-2022-3076
PUBLISHED: 2022-09-26
The CM Download Manager WordPress plugin before 2.8.6 allows high privilege users such as admin to upload arbitrary files by setting the any extension via the plugin's setting, which could be used by admins of multisite blog to upload PHP files for example.
CVE-2022-3098
PUBLISHED: 2022-09-26
The Login Block IPs WordPress plugin through 1.0.0 does not have CSRF check in place when updating its settings, which could allow attackers to make a logged in admin change them via a CSRF attack
CVE-2022-3119
PUBLISHED: 2022-09-26
The OAuth client Single Sign On WordPress plugin before 3.0.4 does not have authorisation and CSRF when updating its settings, which could allow unauthenticated attackers to update them and change the OAuth endpoints to ones they controls, allowing them to then be authenticated as admin if they know...
CVE-2022-3135
PUBLISHED: 2022-09-26
The SEO Smart Links WordPress plugin through 3.0.1 does not sanitise and escape some of its settings, which could allow high privilege users such as admin to perform Stored Cross-Site Scripting attacks even when the unfiltered_html capability is disallowed (for example in multisite setup)