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


7 Tips for Infosec Pros Considering A Lateral Career Move
Kelly Sheridan, Staff Editor, Dark Reading,  1/21/2020
For Mismanaged SOCs, The Price Is Not Right
Kelly Sheridan, Staff Editor, Dark Reading,  1/22/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
IT 2020: A Look Ahead
Are you ready for the critical changes that will occur in 2020? We've compiled editor insights from the best of our network (Dark Reading, Data Center Knowledge, InformationWeek, ITPro Today and Network Computing) to deliver to you a look at the trends, technologies, and threats that are emerging in the coming year. Download it today!
Flash Poll
How Enterprises are Attacking the Cybersecurity Problem
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-2015-3154
PUBLISHED: 2020-01-27
CRLF injection vulnerability in Zend\Mail (Zend_Mail) in Zend Framework before 1.12.12, 2.x before 2.3.8, and 2.4.x before 2.4.1 allows remote attackers to inject arbitrary HTTP headers and conduct HTTP response splitting attacks via CRLF sequences in the header of an email.
CVE-2019-17190
PUBLISHED: 2020-01-27
A Local Privilege Escalation issue was discovered in Avast Secure Browser 76.0.1659.101. The vulnerability is due to an insecure ACL set by the AvastBrowserUpdate.exe (which is running as NT AUTHORITY\SYSTEM) when AvastSecureBrowser.exe checks for new updates. When the update check is triggered, the...
CVE-2014-8161
PUBLISHED: 2020-01-27
PostgreSQL before 9.0.19, 9.1.x before 9.1.15, 9.2.x before 9.2.10, 9.3.x before 9.3.6, and 9.4.x before 9.4.1 allows remote authenticated users to obtain sensitive column values by triggering constraint violation and then reading the error message.
CVE-2014-9481
PUBLISHED: 2020-01-27
The Scribunto extension for MediaWiki allows remote attackers to obtain the rollback token and possibly other sensitive information via a crafted module, related to unstripping special page HTML.
CVE-2015-0241
PUBLISHED: 2020-01-27
The to_char function in PostgreSQL before 9.0.19, 9.1.x before 9.1.15, 9.2.x before 9.2.10, 9.3.x before 9.3.6, and 9.4.x before 9.4.1 allows remote authenticated users to cause a denial of service (crash) or possibly execute arbitrary code via a (1) large number of digits when processing a numeric ...