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
7 Ways To Fine-Tune Your Threat Intelligence Model
Newest First  |  Oldest First  |  Threaded View
cemal.dikmen
50%
50%
cemal.dikmen,
User Rank: Author
1/15/2017 | 8:11:20 AM
Question
lack of suitable technologies (525%). Did you mean 52%???
RetiredUser
50%
50%
RetiredUser,
User Rank: Ninja
1/5/2017 | 11:04:41 PM
Re: $5.8 billion
Michael, I think that makes sense if you look at the breakdown.  Keep in mind that this is a wide-ranging examination and as we in the tech world know, costs are in every nook and cranny.

The scope of the report looks at the whole threat intelligence security market and covers all the solutions below:
  • Security Information And Event Management (SIEM)
  • Log Management
  • Identity and Access Management (IAM)
  • Security and Vulnerability Management (SVM)
  • Risk Management
  • Incident Forensics

That's already quite a bit of annual $$ right there per solution.  Then the service breakdown below is also considered. 
  • Managed Services
    • Advance Threat Monitoring
    • Security Intelligence Feeds
  • Professional Services
    • Consulting Services
    • Training and Support

Considering the projection covers SMBs and Large Enterprises, all the major verticals and the North America, European, Asia-Pacific, Middle East & Africa, and Latin America markets, I actually wonder if the $$ assessment won't be found wanting by that time.

I understand your intitial doubt, but I work for a company that just spent about $25M on technology over the last couple years, not including budget for Security to secure that tech.  That's one major company in one major vertical in Tech.

I think the numbers are starting to look pretty solid with the scope in mind, and knowing the threat activity that is out there now and what we've seen in the past. 
michaelfillin
50%
50%
michaelfillin,
User Rank: Apprentice
1/5/2017 | 4:37:49 PM
$5.8 billion
$5.8 billion, really ? Can't trust that


Mobile Banking Malware Up 50% in First Half of 2019
Kelly Sheridan, Staff Editor, Dark Reading,  1/17/2020
Active Directory Needs an Update: Here's Why
Raz Rafaeli, CEO and Co-Founder at Secret Double Octopus,  1/16/2020
New Attack Campaigns Suggest Emotet Threat Is Far From Over
Jai Vijayan, Contributing Writer,  1/16/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
The Year in Security: 2019
This Tech Digest provides a wrap up and overview of the year's top cybersecurity news stories. It was a year of new twists on old threats, with fears of another WannaCry-type worm and of a possible botnet army of Wi-Fi routers. But 2019 also underscored the risk of firmware and trusted security tools harboring dangerous holes that cybercriminals and nation-state hackers could readily abuse. Read more.
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-2019-20391
PUBLISHED: 2020-01-22
An invalid memory access flaw is present in libyang before v1.0-r3 in the function resolve_feature_value() when an if-feature statement is used inside a bit. Applications that use libyang to parse untrusted input yang files may crash.
CVE-2019-20392
PUBLISHED: 2020-01-22
An invalid memory access flaw is present in libyang before v1.0-r1 in the function resolve_feature_value() when an if-feature statement is used inside a list key node, and the feature used is not defined. Applications that use libyang to parse untrusted input yang files may crash.
CVE-2019-20393
PUBLISHED: 2020-01-22
A double-free is present in libyang before v1.0-r1 in the function yyparse() when an empty description is used. Applications that use libyang to parse untrusted input yang files may be vulnerable to this flaw, which would cause a crash or potentially code execution.
CVE-2019-20394
PUBLISHED: 2020-01-22
A double-free is present in libyang before v1.0-r3 in the function yyparse() when a type statement in used in a notification statement. Applications that use libyang to parse untrusted input yang files may be vulnerable to this flaw, which would cause a crash or potentially code execution.
CVE-2019-20395
PUBLISHED: 2020-01-22
A stack consumption issue is present in libyang before v1.0-r1 due to the self-referential union type containing leafrefs. Applications that use libyang to parse untrusted input yang files may crash.