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
Time To Turn The Tables On Attackers
Newest First  |  Oldest First  |  Threaded View
macker490
50%
50%
macker490,
User Rank: Ninja
11/20/2014 | 7:31:48 AM
Re: Two things,--
look up the meaning of "apoplectic" : Extremely angry; furious:

="the "NSA was apoplectic."

this explains why this critical technology has been diluted (x.509)  and is not well understood.     This needs to change.
macker490
50%
50%
macker490,
User Rank: Ninja
11/20/2014 | 7:27:17 AM
Two things,--
two things need to happen:

(1) use a secure operating system

(2) insist on authentication of transmittals


a Secure O/S will not allow itself to be modified by activity of an application program.

authentication is something that each user needs to be involved in: each of us needs to vett the x.509 certificates we want to trust and each of us needs to learn how to authenticate transmittals and then make a practice of insisting on authentication.

the need and method for authentication has been established since the '70s:

see: https://medium.com/stanford-select/keeping-secrets-84a7697bf89f

EXCERPT

A year earlier, Hellman had published "New Directions in Cryptography" with his student Whitfield Diffie, Gr. '78. The paper introduced the principles that now form the basis for all modern cryptography, and its publication rightfully caused a stir among electrical engineers and computer scientists. As Hellman recalled in a 2004 oral history, the nonmilitary community's reaction to the paper was "ecstatic." In contrast, the "NSA was apoplectic."
Marilyn Cohodas
50%
50%
Marilyn Cohodas,
User Rank: Strategist
11/16/2014 | 1:58:51 PM
Re: It's time to wake up.
The vision sounds great to me. But I'm wondering how, as a competitive industry, will security vendors unite to deliver that vision to their customers.
gmerriman112
100%
0%
gmerriman112,
User Rank: Strategist
11/15/2014 | 6:37:44 AM
It's time to wake up.
"In the years since we've been faced with the reality that as an industry we've reached a point of catastrophic failure."

It's nice to see someone state the ugly truth. I've been saying this for a while now, but most folks I talk to think I'm being alarmist. They think that we will all muddle through somehow.

Yet the pace of serious breaches quickens with every passing month. Most disturbing to me is that so many of these incidents are the result of bone-headed blunders by folks who are getting paid to know better. Also disturbing are the complaints from folks who do know better that their managers are unwilling to make the necessary investment to improve the situation.

I'm not a security expert; I don't have a solution to the problem. I can only hope that the folks who are in a position to do something will wake up before it is too late.
RetiredUser
100%
0%
RetiredUser,
User Rank: Ninja
11/13/2014 | 6:25:18 PM
FOSS Access to RSA Innovation
I completely agree with your vision and I feel this is a great step in the right direction.  One of the best ways to innovate across an industry is to share knowledge, make APIs available and demonstrate solid functionality across platforms.  I hope that part of this initiative includes a deeper relationship with the Free and Open Source Software (FOSS) communities.  One reason is that, because FOSS is so "cheap" many start-ups and established companies use it in an Enterprise setting.  However, this is not always the most secure way to operate, especially for IT shops using FOSS that aren't well-versed in security and haven't done all they can do to tighten access to their digital assets.  This doesn't necessarily mean free up all your source, and make "free" your tools; rather, developing that tight relationship with one of the most influential technical bodies in the Enterprise (FOSS) can mean better code coverage (even if the source isn't open, the FOSS community can be hard on new tools and technologies, often revealing vulnerabilities before any other group), and when the relationship is a good one, FOSS users might be more willing to spend money on a solution than simply roll out a free one.


Commentary
Ransomware Is Not the Problem
Adam Shostack, Consultant, Entrepreneur, Technologist, Game Designer,  6/9/2021
Edge-DRsplash-11-edge-ask-the-experts
How Can I Test the Security of My Home-Office Employees' Routers?
John Bock, Senior Research Scientist,  6/7/2021
News
New Ransomware Group Claiming Connection to REvil Gang Surfaces
Jai Vijayan, Contributing Writer,  6/10/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win an Amazon Gift Card! Click Here
Latest Comment: Google's new See No Evil policy......
Current Issue
The State of Cybersecurity Incident Response
In this report learn how enterprises are building their incident response teams and processes, how they research potential compromises, how they respond to new breaches, and what tools and processes they use to remediate problems and improve their cyber defenses for the future.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-31664
PUBLISHED: 2021-06-18
RIOT-OS 2021.01 before commit 44741ff99f7a71df45420635b238b9c22093647a contains a buffer overflow which could allow attackers to obtain sensitive information.
CVE-2021-33185
PUBLISHED: 2021-06-18
SerenityOS contains a buffer overflow in the set_range test in TestBitmap which could allow attackers to obtain sensitive information.
CVE-2021-33186
PUBLISHED: 2021-06-18
SerenityOS in test-crypto.cpp contains a stack buffer overflow which could allow attackers to obtain sensitive information.
CVE-2021-31272
PUBLISHED: 2021-06-18
SerenityOS before commit 3844e8569689dd476064a0759d704bc64fb3ca2c contains a directory traversal vulnerability in tar/unzip that may lead to command execution or privilege escalation.
CVE-2021-31660
PUBLISHED: 2021-06-18
RIOT-OS 2021.01 before commit 85da504d2dc30188b89f44c3276fc5a25b31251f contains a buffer overflow which could allow attackers to obtain sensitive information.