Around the world, our lives are increasingly dependent on technology. What should be the responsibilities of technologists regarding technological and nontechnological issues?
The challenge of ensuring election system integrity illustrates these points. The election process is an end-to-end phenomenon whose integrity depends on the integrity of every step in the process. Unfortunately, each of those steps represents various potential weak links that can be compromised in many ways, accidentally and intentionally, technologically or otherwise; each step must be safeguarded from the outset and auditable throughout the entire process.
Irregularities reported in the 2004 U.S. national election span the entire process, concerning voter registration, disenfranchisement and harassment of legitimate voters, absence of provisional ballots, mishandling of absentee ballots, extensive delays in certain precincts, and problems in casting and counting ballots for e-voting as well as other modes of casting and counting votes. Some machines could not be booted. Some machines lost votes because of programming problems, or recorded more votes than voters. Some touch-screen machines reportedly altered the intended vote from one candidate to another. The integrity of the voting technologies themselves is limited by weak evaluation standards, secret evaluations that are paid for by the vendors, all-electronic systems that lack voter-verified audit trails and meaningful recountability, unaudited post-certification software changes, even runtime system or data alterations, and human error and misuse. Other risks arise from partisan vendors and election officials. Furthermore, unusually wide divergences between exit polls and unaudited results created question in certain states. All of these concerns add to uncertainties about the integrity of the overall election processes.
Some of you may wonder why, with modern technology, the voting process cannot be more robust. Whether the potential weak links are mostly technological or not, the process can certainly be made significantly more trustworthy. Indeed, it seems to be better in many other countries than in the U.S.; for example, Ireland, India, and the Netherlands seem to be taking integrity challenges seriously. As technologists, we should be helping to ensure that is the case, for example, by participating in the standards process or perhaps by aiding the cause of the Open Voting Consortium. However, the end-to-end nature of the problems includes many people whose accidental or intentional behavior can alter the integrity of the overall process, and thus portends many nontechnological risks.
Similar concerns also arise in many other computer-related application areas, such as aviation, health care, defense, homeland security, law enforcement, intelligence, and so onwith similar conclusions. In each case, a relevant challenge is that of developing and operating end-to-end trustworthy environments capable of satisfying stringent requirements for human safety, reliability, system integrity, information security, and privacy, in which many technological and nontechnological issues must be addressed throughout the computer systems and operational practices. Overall, technologists need to provide adequate trustworthiness in our socially important information systems, by technological and other means. Research and development communities internationally have much to offer in achieving trustworthy computer-communication systems. However, they also have serious responsibilities to be aware of the other implications of the use of these systems.
©2005 ACM 0001-0782/05/0200 $5.00
Permission to make digital or hard copies of all or part of this work for personal or classroom use is granted without fee provided that copies are not made or distributed for profit or commercial advantage and that copies bear this notice and the full citation on the first page. To copy otherwise, to republish, to post on servers or to redistribute to lists, requires prior specific permission and/or a fee.
The Digital Library is published by the Association for Computing Machinery. Copyright © 2005 ACM, Inc.
No entries found