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
Hacking The Polls: Where US Voting Processes Fall Short
Newest First  |  Oldest First  |  Threaded View
Joe Stanganelli
50%
50%
Joe Stanganelli,
User Rank: Ninja
9/29/2016 | 7:50:36 AM
Re: Pah.
@Jeff: Yes, don't get me wrong.  I do think the "IT" of it has a lot of problems, but you are totally right that the process is just as much (if not more) to blame.  For instance, bureaucratic government approaches for vetting updates to proprietary voting systems keep said voting systems vulnerable for longer.

As for Internet voting, studies have demonstrated that it doesn't encourage non-voters to vote; it simply adds a layer of convenience for people who have already decided to vote.

All of this said (and more), there's a serious ROI issue with e-voting in any form because of the security perils.

( I roundly criticized e-voting security a couple of years ago here: enterprisenetworkingplanet.com/netsecur/hack-early-hack-often-the-perils-of-electronic-voting.html )

Jeff.schilling
50%
50%
Jeff.schilling,
User Rank: Author
9/29/2016 | 3:07:20 AM
Re: Pah.
Joe,  Thank you for your comments.  I think no matter what process we adopt in each of the states, we need to focus on securing that process.  Many folks want to blame the IT systems for being unsecure.  However, in most cases, it is the process itself that is not secure.  Our payment card industry is a perfect example to illustrate that point.  We never really changed the process of how we manage credit payments at the point of sale, we just put it in "electrons."  We are starting to see many innovations in that space now to keep you from having to show your credit card at the point of sale.  I think the voting process needs the same innovative look.
Jeff.schilling
50%
50%
Jeff.schilling,
User Rank: Author
9/29/2016 | 3:00:47 AM
Re: Why is This Suddenly an Issue?
Agree this is not a new risk, but there has not been any real effort to address this wicked problem.  That is what I was calling out in the article.  I know there is not a lot of trust in a federal program for electronic voting and that is not what I am proposing.  I am proposing that some of the "have not" states who can't seem to put the investment needed to get their voting processess secure, pool their resources in "state to state" agreeements.  
geriatric
50%
50%
geriatric,
User Rank: Moderator
9/28/2016 | 1:27:37 PM
Why is This Suddenly an Issue?
There have been grave concerns with electronic voting ever since this turkey was foisted on the public. The lack of an audit trail, the ability to 'flip' votes, and machines delivered with votes already cast have littered the headlines for decades. But NOW it's a problem? I'll leave the answer to this question to rational, reasonable beings. Seems rather obvious to me.

We need to figure out how to authenticate a paper vote first.

And from a security perspective, a decentralized system is more secure than a Federally-controlled national system. Right now, there are vulnerabilities, but no way to hack the entire system to produce a desired outcome. If all the eggs are in one basket, it will be much simpler.
Joe Stanganelli
50%
50%
Joe Stanganelli,
User Rank: Ninja
9/28/2016 | 11:40:48 AM
Pah.
The NIST standards are a helpful tool -- but they are FAR from a helpful salve (particularly considering how the NIST Cybersecurity Framework is a bit M&M-security-focused...with much less focus on what to do during and after an initial breach and much more focus on initial prevention).

Frankly, we need to perfect the sanctity and security of old-fashioned in-person voting before we move forward with more e-voting measures.


Navigating Security in the Cloud
Diya Jolly, Chief Product Officer, Okta,  12/4/2019
SOC 2s & Third-Party Assessments: How to Prevent Them from Being Used in a Data Breach Lawsuit
Beth Burgin Waller, Chair, Cybersecurity & Data Privacy Practice , Woods Rogers PLC,  12/5/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: Our Endpoint Protection system is a little outdated... 
Current Issue
Navigating the Deluge of Security Data
In this Tech Digest, Dark Reading shares the experiences of some top security practitioners as they navigate volumes of security data. We examine some examples of how enterprises can cull this data to find the clues they need.
Flash Poll
Rethinking Enterprise Data Defense
Rethinking Enterprise Data Defense
Frustrated with recurring intrusions and breaches, cybersecurity professionals are questioning some of the industrys conventional wisdom. Heres a look at what theyre thinking about.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-4095
PUBLISHED: 2019-12-10
IBM Cloud Pak System 2.3 is vulnerable to cross-site request forgery which could allow an attacker to execute malicious and unauthorized actions transmitted from a user that the website trusts. IBM X-Force ID: 158015.
CVE-2019-4244
PUBLISHED: 2019-12-10
IBM SmartCloud Analytics 1.3.1 through 1.3.5 could allow a remote attacker to gain unauthorized information and unrestricted control over Zookeeper installations due to missing authentication. IBM X-Force ID: 159518.
CVE-2019-4521
PUBLISHED: 2019-12-10
Platform System Manager in IBM Cloud Pak System 2.3 is potentially vulnerable to CVS Injection. A remote attacker could execute arbitrary commands on the system, caused by improper validation of csv file contents. IBM X-Force ID: 165179.
CVE-2019-4663
PUBLISHED: 2019-12-10
IBM WebSphere Application Server - Liberty is vulnerable to cross-site scripting. This vulnerability allows users to embed arbitrary JavaScript code in the Web UI thus altering the intended functionality potentially leading to credentials disclosure within a trusted session. IBM X-Force ID: 171245...
CVE-2019-19251
PUBLISHED: 2019-12-10
The Last.fm desktop app (Last.fm Scrobbler) through 2.1.39 on macOS makes HTTP requests that include an API key without the use of SSL/TLS. Although there is an Enable SSL option, it is disabled by default, and cleartext requests are made as soon as the app starts.