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
How I Would Secure The Internet With $4 Billion
Newest First  |  Oldest First  |  Threaded View
AnthonyE396
AnthonyE396,
 User Rank: Apprentice
6/20/2015 | 12:53:35 AM
Re: Is $4 Billion enough?
Maybe before you spend 4 $Billion you should secure your own site OWASP and not send clear text passwords back to subscribers who then have to change all their account details

JUST SAYING
BobP756
BobP756,
 User Rank: Apprentice
6/2/2015 | 9:53:40 AM
Question: Open-sourced development frameworks
"Imagine a trove of open-source development frameworks that can be leveraged to ensure security from the inception of any new product."

If this type of framework is an internet security solution:

1.  Why hasn't it been done already?

2. Is there anything in existence that approaches this solution?
Marilyn Cohodas
Marilyn Cohodas,
 User Rank: Strategist
6/1/2015 | 4:29:47 PM
Re: Is $4 Billion enough?
LOL! Very funny.
BertrandW414
BertrandW414,
 User Rank: Strategist
6/1/2015 | 2:20:21 PM
Re: Is $4 Billion enough?
Sorry Marilyn, the answer to that question is classified. ;-)
Sonatype
Sonatype,
 User Rank: Apprentice
6/1/2015 | 1:59:53 AM
In an Ideal World ...
"I would hire a large, senior team of security-minded developers and assessment professionals to focus on providing security services for the most popular open source software."

This would be great, wouldn't it? Unfortunately this isn't the case for most developers. We definitely agree that security has not been properly prioritized during the development of applications and other technologies. In the interim, what we can do is have development teams utilize repository managers that ensure only high quality open source components are used in applications - by identifying and remediate faulty components throughout the application's life cycle.
jmanico
jmanico,
 User Rank: Apprentice
5/30/2015 | 12:05:00 AM
Re: Is $4 Billion enough?
Hello and thank you for commenting. The comment from RyanSepe is spot on. While the 4 billion dollar figure is an arbitrary number, it points to the scale and effort needed for this effort to succeed. Thank you again for reading this article and taking the time to comment.
Marilyn Cohodas
Marilyn Cohodas,
 User Rank: Strategist
5/29/2015 | 1:37:55 PM
Re: Is $4 Billion enough?
True, Ryan. It could be just an arbitrary number, but I'm wondering of the $4B is related to an estimate of what someone in Congress estimates to be the cost of the  information-sharing program. I should have been a little clearer in my comment. But then again , it is Friday!
RyanSepe
RyanSepe,
 User Rank: Ninja
5/29/2015 | 1:31:07 PM
Re: Is $4 Billion enough?
I think the exact number is arbitrary. Most likely just wanted a high enough number to get the point across that security in itself is its own business. I see many validate points within this article however they have their downsides as well. Focusing on open source areas provides more visiblity. Which is a proponent and detriment in itself. More people to help, more people to destroy. The work force to analyze the overall frameworks would need to be massive.
Marilyn Cohodas
Marilyn Cohodas,
 User Rank: Strategist
5/29/2015 | 12:59:40 PM
Is $4 Billion enough?
Interesting point of view, Jim. But I'm curious about where you came up with the $4 billion dollar figure.


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
The 10 Most Impactful Types of Vulnerabilities for Enterprises Today
Managing system vulnerabilities is one of the old est - and most frustrating - security challenges that enterprise defenders face. Every software application and hardware device ships with intrinsic flaws - flaws that, if critical enough, attackers can exploit from anywhere in the world. It's crucial that defenders take stock of what areas of the tech stack have the most emerging, and critical, vulnerabilities they must manage. It's not just zero day vulnerabilities. Consider that CISA's Known Exploited Vulnerabilities (KEV) catalog lists vulnerabilitlies in widely used applications that are "actively exploited," and most of them are flaws that were discovered several years ago and have been fixed. There are also emerging vulnerabilities in 5G networks, cloud infrastructure, Edge applications, and firmwares to consider.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2023-1142
PUBLISHED: 2023-03-27
In Delta Electronics InfraSuite Device Master versions prior to 1.0.5, an attacker could use URL decoding to retrieve system files, credentials, and bypass authentication resulting in privilege escalation.
CVE-2023-1143
PUBLISHED: 2023-03-27
In Delta Electronics InfraSuite Device Master versions prior to 1.0.5, an attacker could use Lua scripts, which could allow an attacker to remotely execute arbitrary code.
CVE-2023-1144
PUBLISHED: 2023-03-27
Delta Electronics InfraSuite Device Master versions prior to 1.0.5 contains an improper access control vulnerability in which an attacker can use the Device-Gateway service and bypass authorization, which could result in privilege escalation.
CVE-2023-1145
PUBLISHED: 2023-03-27
Delta Electronics InfraSuite Device Master versions prior to 1.0.5 are affected by a deserialization vulnerability targeting the Device-DataCollect service, which could allow deserialization of requests prior to authentication, resulting in remote code execution.
CVE-2023-1655
PUBLISHED: 2023-03-27
Heap-based Buffer Overflow in GitHub repository gpac/gpac prior to 2.4.0.