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.

Vulnerabilities / Threats

5/18/2015
10:15 AM
Jeff Williams
Jeff Williams
Commentary
Connect Directly
Twitter
LinkedIn
Google+
RSS
E-Mail vvv

Why We Can't Afford To Give Up On Cybersecurity Defense

There is no quick fix, but organizations can massively reduce the complexity of building secure applications by empowering developers with four basic practices.

Comment  | 
Print  | 
Comments
Newest First  |  Oldest First  |  Threaded View
Joe Stanganelli
50%
50%
Joe Stanganelli,
User Rank: Ninja
5/23/2015 | 11:38:54 PM
Low-tech security culture
To speak of training and security culture, it really touches all levels of the organization -- and information security should be top of mind even in low-tech contexts.  (After all, social engineering is the skilled hacker's top choice when it comes to finding weaknesses.  All it takes is a slip-up during a phone call.)
macker490
50%
50%
macker490,
User Rank: Ninja
5/19/2015 | 8:18:08 AM
White List Thinking
We need a "Sea Change" to Whitelist Thinking.

it is necessary to authenticate many messages, certainly those dealing with money, -- or software.

The Essential Element to this change in thinking deals with the symmetric nature of our customary identification data.   Name, address, date of birth, Social Security Number -- even Company Letterhead Stationary -- can all be easily compromised in the digital world.   These keys -- once released in public -- are compromised forever.   In this they act like the symmetric keys used on basic encryption where the decryption key is the same as the encryption key: a shared secret.

The trouble is our traditional identification data are a shared secred -- with everyone in on it.   See KREBS essay on "Superget" -- a DarkWeb service selling these symmetric keys

this is why we need to move to the general use of PGP

PGP is based on asymmetric keys: the signing key is private and the authentication key is public.   This means you can produce an authenticated document in public -- without compromising your identity -- i.e. your private key

many detractors claim this is too complicated for ordinary people.  This is a myth that needs to be dispeled. As packaged technology it is no more difficult to use PGP than it is to use the PIN on a debit card to get cash from an ATM.   Practice using the ENIGMAIL plug-in for the Thunderbird eMail client.

There are two keys to progress in fighting hacking

1. use a secure operating system.   A secure operating system is one which will not allow itself to be compromised by the activity of an application program -- such as a web page.

2. authenticate transactions -- including software downloads, eMail, tax forms &c -- using PGP

Half-way measures have been ineffective.   It's time to recognize hacking as a problem that must be addressed in a serious manner.

 
BPID Security
50%
50%
BPID Security,
User Rank: Strategist
5/18/2015 | 8:11:52 PM
well done.
Thanks for a well considered and well written post.

 

As always we want easy. We don't want maintenance. We want things to work so we don't have to. So we buy cars with low maintenance and trade them out on a lease, our phones are disposable when the 32 year contract is up, and we expect internet security should work out of the box.

Jeff, it is just the way it is. Our entire modern culture is avoidance and avoiding responsibility.

Good article - excellent points, but it isn't about to change. We will continue to drive and talk on our cell phones and we will continue to ignore best practices in security and when there is a breach we will point fingers.


Thanks again. good post.
COVID-19: Latest Security News & Commentary
Dark Reading Staff 6/3/2020
Data Loss Spikes Under COVID-19 Lockdowns
Seth Rosenblatt, Contributing Writer,  5/28/2020
Abandoned Apps May Pose Security Risk to Mobile Devices
Robert Lemos, Contributing Writer,  5/29/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: This comment is waiting for review by our moderators.
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-10548
PUBLISHED: 2020-06-04
rConfig 3.9.4 and previous versions has unauthenticated devices.inc.php SQL injection. Because, by default, nodes' passwords are stored in cleartext, this vulnerability leads to lateral movement, granting an attacker access to monitored network devices.
CVE-2020-10549
PUBLISHED: 2020-06-04
rConfig 3.9.4 and previous versions has unauthenticated snippets.inc.php SQL injection. Because, by default, nodes' passwords are stored in cleartext, this vulnerability leads to lateral movement, granting an attacker access to monitored network devices.
CVE-2020-10546
PUBLISHED: 2020-06-04
rConfig 3.9.4 and previous versions has unauthenticated compliancepolicies.inc.php SQL injection. Because, by default, nodes' passwords are stored in cleartext, this vulnerability leads to lateral movement, granting an attacker access to monitored network devices.
CVE-2020-10547
PUBLISHED: 2020-06-04
rConfig 3.9.4 and previous versions has unauthenticated compliancepolicyelements.inc.php SQL injection. Because, by default, nodes' passwords are stored in cleartext, this vulnerability leads to lateral movement, granting an attacker access to monitored network devices.
CVE-2020-11094
PUBLISHED: 2020-06-04
The October CMS debugbar plugin before version 3.1.0 contains a feature where it will log all requests (and all information pertaining to each request including session data) whenever it is enabled. This presents a problem if the plugin is ever enabled on a system that is open to untrusted users as ...