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.

Database Security
Authentication
Mobile
Privacy
Compliance
Careers and People
Identity & Access Management
Security Monitoring
Advanced Threats
Insider Threats
Vulnerability Management
Comments
Threat Intelligence's Big Data Problem
Threaded  |  Newest First  |  Oldest First
MattDevost
MattDevost,
 User Rank: Apprentice
3/17/2016 | 4:27:59 PM
An evolution, hopefully based on the fundamentals of intelligence
Look forward to tracking this new series.  The evolution of threat intelligence is an important topic as organizations migrate towards intelligence driven security programs.  Hopefully you spend a little time looking at the fundamentals of the intelligence process and how they need to be incorporated and evolved into the cyber security domain.  

Having built intel organizations at companies like iDEFENSE, iSIGHT, the Terrorism Research Center, and within 56 U.S. cities, this is a topic that I track closely.  Many organizations don't give enough attention to how they need to consume and act on intelligence to drive decisions.  It isn't just about how many feeds you can consume, but how those feeds fit into and drive an internal intelligence process that is iterative and has a robust feedback loop.
ecrutchlow
ecrutchlow,
 User Rank: Apprentice
3/21/2016 | 12:38:59 PM
Target Example Completely Wrong
Your use of Target was completely wrong. This was Target's first excuse for why they didn't catch this early, but as the story evolved the true events came out resulting in the CIO and the CEO resigning.

The FireEye device did detect and alert the subcontractor team in India and FireEye saw the alert as well. The subcontractor team was contacted immediately by FireEye and informed of the significance of the breach. In turn, the subcontractor notified Target and they did not act on the information. For a good write-up on the events, please look up the SANS report titled, "Case Study: Critical Controls that Could Have Prevented Target Breach"

The article is correct regarding the amount of data organizations must review. It's really the story of the boy who cried wolf one too many times. Except we have systems that cry wolf thousands of times a day. Solutions that can reduce the noise is essential. Security operations centers should be focusing on real events and not on vetting false-positives.
ACThomson
ACThomson,
 User Rank: Author
3/25/2016 | 9:20:15 AM
An opportunity for artificial intelligence
There are quite a number of startups appearing that are using artificial intelligence techniques to help manage this overload, allowing the most important threats to be prioratised.


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
Incorporating a Prevention Mindset into Threat Detection and Response
Threat detection and response systems, by definition, are reactive because they have to wait for damage to be done before finding the attack. With a prevention-mindset, security teams can proactively anticipate the attacker's next move, rather than reacting to specific threats or trying to detect the latest techniques in real-time. The report covers areas enterprises should focus on: What positive response looks like. Improving security hygiene. Combining preventive actions with red team efforts.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2022-1809
PUBLISHED: 2022-05-21
Access of Uninitialized Pointer in GitHub repository radareorg/radare2 prior to 5.7.0.
CVE-2022-31267
PUBLISHED: 2022-05-21
Gitblit 1.9.2 allows privilege escalation via the Config User Service: a control character can be placed in a profile data field, such as an emailAddress%3Atext '[email protected]\n\trole = "#admin"' value.
CVE-2022-31268
PUBLISHED: 2022-05-21
A Path Traversal vulnerability in Gitblit 1.9.3 can lead to reading website files via /resources//../ (e.g., followed by a WEB-INF or META-INF pathname).
CVE-2022-31264
PUBLISHED: 2022-05-21
Solana solana_rbpf before 0.2.29 has an addition integer overflow via invalid ELF program headers. elf.rs has a panic via a malformed eBPF program.
CVE-2022-31259
PUBLISHED: 2022-05-21
The route lookup process in beego through 1.12.4 and 2.x through 2.0.2 allows attackers to bypass access control. When a /p1/p2/:name route is configured, attackers can access it by appending .xml in various places (e.g., p1.xml instead of p1).