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.

No Silver Bullets for Security
Oldest First  |  Newest First  |  Threaded View
User Rank: Ninja
3/3/2015 | 10:13:45 AM
No Bullets for Security?
the title of your essay would better be: "No Bullets for Security?"

the reason is simple: if we keep on doing things the way we have we will continue to get the same results: hackers will makes fools of us all.

the first change that must be taken is to insist on secure operating software.   the operating software must not allow itself to be modified by the activity of an application program -- whether by error or by intent .  product liability law will be needed to insure this .

the next change that must be taken is to adopt the general practice of authenticating transmittals using public key encryption.   transmittals include everything from software distributions, to e/mail, and critical web pages.

next: the current practice of broadcasting x.509 certificates is not secure.    every computer user should establish his|her own public key so that critical certificates can be counter-signed.     what this means is broadcast certificates will be assigned only marginal trust and as such are not acceptable for financial procedures.    you have to countersign the certificate yourself to validate it -- in much the same way we have to call to activate a new credit card.

Credit Unions and similar financial organizations should provide key services to members so that public keys can be countersigned and uploaded onto key servers.    this is necessary so that critical services -- such as the IRS -- can validate critical transactions -- such as Forms 1040.

there is much to be done but it is critical to start at the beginning.   if we have some who resist doing things the Right Way we need to root these out, and discredit them .

Secure Computing in a Compromised Environment

in the electronic network environment we all need an identity that we can produce in public that will verify our documents and identity -- but which cannot be controlled by an imposter or hacker.     to do it all you need is a secure O/S and either PGP/Desktop or the GNU/Privacy Guard (GPG) .    the tools are available and the methods are known. now the question: are we serious about solving the problem ?   I think we need to get serious.
User Rank: Strategist
3/5/2015 | 8:20:06 PM
Re: No Bullets for Security?

Yes, we agree. We certainly cannot keep doing things the way we have been and expect to maintain secure environments.

We believe you have to do three things: 1) Harden the Devices, 2) Secure the Comms, and 3) Manage & Monitor. Your suggestions are great examples of addressing the first two. 

In addition, I'd suggest we not forget how important the monitoring and managing aspects to security are. However, the way we monitor and manage our networks will need to be scaled as the number of devices grow – this is done at that onset, by establishing policies that can be automatically enforced.

In looking at how things stand today, there's work to be done. And it's not an option, it is our duty to our customers and company.

User Rank: Apprentice
3/10/2015 | 1:52:21 PM
No Silver Bullets
Another essential component is "buy-in" both from Senior Mgmt and end-users. Unfortunately at present, the majority of regular technology users have no clue of the concept of Info/CyberSecurity- professionals ranging from recruiters and mid & top-level managers to board members, attorneys and physicians give that slack-jawed look whenever the subject is mentioned- they simply do not understand.

And the InfoSec community hasn't necessarily done the best in marketing the concept of Information Security and secure systems, so there's been very little trickle down to average end-users (those most responsible to utilizing all business systems). Recently it seems the government has stepped up efforts in its cybersecurity campaign messages, but it will take a while before the larger community starts getting it.

InfoSec practitioners can't do it alone- we all must join the fight if we are to win this battle.



7 Old IT Things Every New InfoSec Pro Should Know
Joan Goodchild, Staff Editor,  4/20/2021
Cloud-Native Businesses Struggle With Security
Robert Lemos, Contributing Writer,  5/6/2021
Defending Against Web Scraping Attacks
Rob Simon, Principal Security Consultant at TrustedSec,  5/7/2021
Register for Dark Reading Newsletters
White Papers
Cartoon Contest
Write a Caption, Win an Amazon Gift Card! Click Here
Latest Comment: Take me to your BISO 
Current Issue
2021 Top Enterprise IT Trends
We've identified the key trends that are poised to impact the IT landscape in 2021. Find out why they're important and how they will affect you today!
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
PUBLISHED: 2021-05-10
In YzmCMS 5.6, XSS was discovered in member/member_content/init.html via the SRC attribute of an IFRAME element because of using UEditor
PUBLISHED: 2021-05-10
In YzmCMS 5.6, stored XSS exists via the common/static/plugin/ueditor/ action parameter, which allows remote attackers to upload a swf file. The swf file can be injected with arbitrary web script or HTML.
PUBLISHED: 2021-05-10
Cross-site scripting (XSS) vulnerability in static/admin/js/kindeditor/plugins/multiimage/images/swfupload.swf in noneCms v1.3.0 allows remote attackers to inject arbitrary web script or HTML via the movieName parameter.
PUBLISHED: 2021-05-10
Cross-site scripting (XSS) vulnerability in admin/nav/add.html in noneCMS v1.3.0 allows remote authenticated attackers to inject arbitrary web script or HTML via the name parameter.
PUBLISHED: 2021-05-10
Cross-site scripting (XSS) vulnerability in admin/article/add.html in noneCMS v1.3.0 allows remote authenticated attackers to inject arbitrary web script or HTML via the name parameter.