{"id":17632,"date":"2020-02-04T10:45:31","date_gmt":"2020-02-04T18:45:31","guid":{"rendered":"http:\/\/www.palada.net\/index.php\/2020\/02\/04\/news-11367\/"},"modified":"2020-02-04T10:45:31","modified_gmt":"2020-02-04T18:45:31","slug":"news-11367","status":"publish","type":"post","link":"http:\/\/www.palada.net\/index.php\/2020\/02\/04\/news-11367\/","title":{"rendered":"The Iowa Caucus Tech Meltdown Is a Warning"},"content":{"rendered":"<p><img decoding=\"async\" src=\"https:\/\/media.wired.com\/photos\/5e3987e9e7120600088b1f5b\/master\/pass\/Biz-iowacaucus-1198463756.jpg\"\/><\/p>\n<p><strong>Credit to Author: Lily Hay Newman| Date: Tue, 04 Feb 2020 18:00:57 +0000<\/strong><\/p>\n<p class=\"byline bylines__byline byline--author\" itemprop=\"author\" itemtype=\"http:\/\/schema.org\/Person\"><span itemprop=\"name\"><span class=\"byline__name byline--with-bg\"><a class=\"byline__name-link\" href=\"\/contributor\/lily-hay-newman\">Lily Hay Newma<span class=\"link__last-letter-spacing\">n<\/span><\/a><\/span> <\/span><\/p>\n<p class=\"content-header__row content-header__dek\">The Iowa results will come in eventually, thanks to a paper trail. But it underscores just how much can go wrong when you lean on unnecessary, untested tech.<\/p>\n<p>After months of buildup, Monday\u2019s Iowa Caucus kicked off the 2020 primary elections\u2014and it didn\u2019t go great. Reporting of results was delayed by what Iowa democratic officials first called &quot;quality control&quot; efforts. In fact, a new, unvetted mobile app designed to help collect and relay voting tallies had failed due to technical and usability issues. The telephone hotline intended as a fail-safe was overwhelmed by calls from caucus leaders trying to report results and troubleshoot the app. It was, and as of publication continues to be, a mess. It&#x27;s also a warning.<\/p>\n<p>The good news first: There&#x27;s every indication that Iowa&#x27;s results will turn out just fine. The votes were all properly recorded, and a paper backup means that they can be verified. It was the reporting process that epically collapsed, necessitating extra time for collecting and tallying final results. It&#x27;s an annoyance, not a catastrophe.<\/p>\n<p>&quot;As part of our investigation, we determined with certainty that the underlying data collected via the app was sound,&quot; Iowa Democratic Party chair Troy Price said in a statement. &quot;While the app was recording data accurately, it was reporting out only partial data. We have determined that this was due to a coding issue in the reporting system. This issue was identified and fixed.&quot;<\/p>\n<p>But the things that went wrong in Iowa provide an <a href=\"https:\/\/www.wired.com\/story\/election-security-2020\/\">important lesson<\/a> that election officials have <a href=\"https:\/\/www.wired.com\/story\/time-about-up-to-secure-2018-midterm-elections\/\">precious little time left<\/a> to learn. Adding technology to the electoral process does not necessarily improve it; in fact, it often makes things more confusing. Worse still, the fallibility of tech makes it easy fodder for conspiracy theories, and a lack of faith in the democratic process. All of which has been on display in Iowa.<\/p>\n<p>Start with the app, developed by a company called Shadow that was funded chiefly by Acronym, a Democratic nonprofit founded in 2017 by former Clinton campaign staff. An Acronym spokesperson did not return a request for comment from WIRED, though the firm said in a statement that it is simply an investor in Shadow.<\/p>\n<p>&quot;People have to think carefully about what the impact is going to be when introducing tech into voting.&quot;<\/p>\n<p>Marian Schneider, Verified Voting<\/p>\n<p>All software has bugs, but a flaw in the core functionality\u2014reporting data\u2014is a major failure. This year, after confusion marred reporting in 2016 and 2008, caucus precinct leaders needed to relay more data than ever to Iowa Democratic officials, who tabulate the results. In addition to the final votes and delegates won, participants also collected data about how caucus-goers originally aligned themselves and how they realigned once it was clear which candidates had less than 15 percent of the vote. The app was intended to be simple way to collect all of this information and centralize it as quickly as possible. It had one job.<\/p>\n<p>In a way, the app had failed before Monday night&#x27;s caucus began. Rather than download it from an app store, precinct leaders had to side-load it onto their devices, a confusing process that many seem to have understandably not bothered with. Those who did install the app appear to have received little training on how to use it or even how to log in; it required a combination of security codes rather than a simple username and password. On top of that, the PINs that precinct leaders used to practice logging in to the app expired before the caucus began.<\/p>\n<p>Details about the app were also largely kept secret, an apparent attempt to create &quot;security through obscurity.&quot; Not even the Department of Homeland Security had a chance to review it. But the idea that it&#x27;s more difficult for hackers to attack a system they don&#x27;t know much about is deeply misguided. Attackers can get up to speed quickly, while leaving security researchers in the dark means there&#x27;s limited opportunity to catch bugs and vulnerabilities before the platform goes live. Nevada Democrats were planning to use the same app during their caucus in less than three weeks but <a class=\"external-link\" data-event-click=\"{&quot;element&quot;:&quot;ExternalLink&quot;,&quot;outgoingURL&quot;:&quot;https:\/\/www.businessinsider.com\/nevada-caucus-shadow-app-democratic-party-caucus-2020-2?&quot;}\" href=\"https:\/\/www.businessinsider.com\/nevada-caucus-shadow-app-democratic-party-caucus-2020-2?\" rel=\"nofollow noopener noreferrer\" target=\"_blank\">said on Tuesday<\/a> that they will not.<\/p>\n<p>\u201cI had heard concerns about the app, in particular that people didn\u2019t know much about it and that there was a lot of secrecy around it,\u201d says Lawrence Norden, deputy director of the Brennan Center&#x27;s Democracy Program at New York University School of Law. \u201cEven for the people who were supposed to be using it, there was very little training, and there was certainly no public testing of the app.\u201d<\/p>\n<p>Even worse, the Iowa Democrats&#x27; phone lines, which were supposed to be the fail-safe for the app, went down. Precinct leaders reported hours-long hold times and issues with their calls being disconnected. It seems that the hotline was expecting fewer calls than in previous years because of the app. Instead, the app actually increased call volume, as frustrated precinct managers tried to figure out what had gone wrong.<\/p>\n<p>Despite all of this, the results should be sound. Every caucus vote was recorded on paper, meaning that officials will be able to verify that their final digital tallies line up with the actual results.<\/p>\n<p>\u201cIn this case in Iowa I don\u2019t think anyone will need to doubt what the results are,\u201d says Marian Schneider, president of Verified Voting, a group that promotes election system best practices. \u201cThose were recorded; those were preserved according to the caucus procedures that they\u2019ve been following for a long time. But the reporting mechanism failed. People have to think carefully about what the impact is going to be when introducing tech into voting.\u201d<\/p>\n<p>Monday night\u2019s debacle underscores the stakes of debuting new technology in elections and the inherent risks of layering more tech into systems to solve problems rather than looking for their root cause.<\/p>\n<p>\u201cTechnology can help, but it usually comes with added risks,\u201d says Ben Adida, executive director VotingWorks, a nonprofit maker of voting machines. \u201cSo any introduction of technology should come with a cost-benefit analysis. And when we do introduce technology in the foundational layer of our democracy, it should be broadly vetted, load tested, security reviewed, and open source.\u201d None of which appears to have happened in Iowa.<\/p>\n<p>For years, the election security community has stressed the need for paper backups in normal voting machines. And yet a rush to embrace certain digital technologies has left many states around the country with at least some precincts that use voting machines without a paper backup. A <a class=\"external-link\" data-event-click=\"{&quot;element&quot;:&quot;ExternalLink&quot;,&quot;outgoingURL&quot;:&quot;https:\/\/www.brennancenter.org\/our-work\/analysis-opinion\/voting-machine-security-where-we-stand-few-months-new-hampshire-primary&quot;}\" href=\"https:\/\/www.brennancenter.org\/our-work\/analysis-opinion\/voting-machine-security-where-we-stand-few-months-new-hampshire-primary\" rel=\"nofollow noopener noreferrer\" target=\"_blank\">recent report<\/a> from the Brennan Center estimates that 16 million votes will be cast with no paper backup at all in the 2020 presidential election. If any of those counties run into problems similar to Iowa&#x27;s, they&#x27;ll have no fail-safe for confirming results.<\/p>\n<p>\u201cA lot of states already use internet voting. West Virginia is already using a mobile app for military and overseas voters,\u201d Verified Voting\u2019s Schneider says. The state plans to <a class=\"external-link\" data-event-click=\"{&quot;element&quot;:&quot;ExternalLink&quot;,&quot;outgoingURL&quot;:&quot;https:\/\/arstechnica.com\/tech-policy\/2020\/02\/west-virginia-poised-to-allow-smartphone-voting-for-disabled-voters\/&quot;}\" href=\"https:\/\/arstechnica.com\/tech-policy\/2020\/02\/west-virginia-poised-to-allow-smartphone-voting-for-disabled-voters\/\" rel=\"nofollow noopener noreferrer\" target=\"_blank\">expand app voting<\/a> to include disabled citizens as well. \u201cThis is a very cautionary tale for doing so. We shouldn\u2019t be doing that. I think this shows that we\u2019re not ready.\u201d<\/p>\n<p>&quot;Technology can help, but it usually comes with added risks.&quot;<\/p>\n<p>Ben Adida, VotingWorks<\/p>\n<p>Iowa will bounce back from its Monday mess. State officials said they&#x27;d have official results by 5 pm EST on Tuesday. But in an already turbulent election cycle, the meltdown shows how easy it would be to create instability by spreading misinformation or calling a voting system\u2019s integrity into question. On Monday night alone, rumors and conspiracy theories quickly popped up to fill the void as everyone\u2014from voters to politicians to the media\u2014awaited results they thought would come quickly. In elections, most of all, speed should not come at the cost of accuracy.<\/p>\n<p>\u201cImagine this operational failure where we don&#x27;t have individual voter-verified paper ballots to go back to,&quot; says VotingWorks\u2019 Adida. &quot;That would require nothing short of rerunning the election. But we have locally verified paper records of the caucus tallies, so we should all take a deep breath. We&#x27;re going to be OK.\u201d<\/p>\n<p><a href=\"https:\/\/www.wired.com\/story\/iowa-democratic-caucus-app-tech-meltdown-warning\" target=\"bwo\" >https:\/\/www.wired.com\/category\/security\/feed\/<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p><img decoding=\"async\" src=\"https:\/\/media.wired.com\/photos\/5e3987e9e7120600088b1f5b\/master\/pass\/Biz-iowacaucus-1198463756.jpg\"\/><\/p>\n<p><strong>Credit to Author: Lily Hay Newman| Date: Tue, 04 Feb 2020 18:00:57 +0000<\/strong><\/p>\n<p>The Iowa results will come in eventually, thanks to a paper trail. But it underscores just how much can go wrong when you lean on unnecessary, untested tech.<\/p>\n","protected":false},"author":4,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"colormag_page_container_layout":"default_layout","colormag_page_sidebar_layout":"default_layout","footnotes":""},"categories":[10378,10607],"tags":[714,21465],"class_list":["post-17632","post","type-post","status-publish","format-standard","hentry","category-security","category-wired","tag-security","tag-security-national-security"],"_links":{"self":[{"href":"http:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/posts\/17632","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/users\/4"}],"replies":[{"embeddable":true,"href":"http:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/comments?post=17632"}],"version-history":[{"count":0,"href":"http:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/posts\/17632\/revisions"}],"wp:attachment":[{"href":"http:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/media?parent=17632"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/categories?post=17632"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/tags?post=17632"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}