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


COVID-19: Latest Security News & Commentary
Dark Reading Staff 6/1/2020
Stay-at-Home Orders Coincide With Massive DNS Surge
Robert Lemos, Contributing Writer,  5/27/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
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
CVE-2020-13757
PUBLISHED: 2020-06-01
Python-RSA 4.0 ignores leading '\0' bytes during decryption of ciphertext. This could conceivably have a security-relevant impact, e.g., by helping an attacker to infer that an application uses Python-RSA, or if the length of accepted ciphertext affects application behavior (such as by causing exces...
CVE-2020-13758
PUBLISHED: 2020-06-01
modules/security/classes/general.post_filter.php/post_filter.php in the Web Application Firewall in Bitrix24 through 20.0.950 allows XSS by placing %00 before the payload.
CVE-2020-9291
PUBLISHED: 2020-06-01
An Insecure Temporary File vulnerability in FortiClient for Windows 6.2.1 and below may allow a local user to gain elevated privileges via exhausting the pool of temporary file names combined with a symbolic link attack.
CVE-2019-15709
PUBLISHED: 2020-06-01
An improper input validation in FortiAP-S/W2 6.2.0 to 6.2.2, 6.0.5 and below, FortiAP-U 6.0.1 and below CLI admin console may allow unauthorized administrators to overwrite system files via specially crafted tcpdump commands in the CLI.
CVE-2020-13695
PUBLISHED: 2020-06-01
In QuickBox Community Edition through 2.5.5 and Pro Edition through 2.1.8, the local www-data user has sudo privileges to execute grep as root without a password, which allows an attacker to obtain sensitive information via a grep of a /root/*.db or /etc/shadow file.