Electronic voting is the use of digital systems to record, transmit, or tally ballots instead of only paper methods. In security terms, it depends on strong identity verification, tamper-resistant devices, cryptographic integrity, access controls, and auditable logs to preserve voter privacy, prevent manipulation, and support trustworthy election outcomes.
What Electronic Voting Means Operationally
Electronic voting replaces some or all paper handling with digital capture, transmission, or tabulation of ballots. That shift changes the security problem from physical ballot custody alone to a system that must preserve integrity, availability, secrecy, and auditability across devices, networks, and count processes.
Because the ballot becomes data, the design must resist unauthorized modification, replay, duplication, or deletion while still keeping a clear chain of evidence for recounts and disputes. The trust model is therefore broader than software alone, it also includes the devices, operators, election procedures, and independent verification mechanisms around the system.
Security Properties That Make It Viable
The most important properties are strong voter authentication or eligibility checks, tamper-resistant endpoints, cryptographic protection for ballot records, and strict access control around election administration functions. If any of those fail, the system can create errors that are difficult to detect after polls close.
Logging and separation of duties matter because election systems must support later review without exposing how any individual voted. Good designs balance verifiability with secrecy, so auditors can confirm that totals are sound without revealing private ballot choices.
Trust, Auditability, and Verifiable Counts
Electronic voting is not just about speed or convenience, it must produce evidence that observers, auditors, and the public can trust. That typically means keeping immutable or tightly protected records, maintaining a verifiable tally path, and preserving enough system history to explain discrepancies.
Independent verification is especially important when the vote is cast or counted on software the voter cannot personally inspect. External standards for identity, access, and audit controls can help here, including NIST SP 800-63 Digital Identity Guidelines for identity assurance and NIST SP 800-53 Rev 5 Security and Privacy Controls for access, logging, and system integrity expectations.
Common Failure Modes and Design Trade-offs
The main trade-off is between usability, accessibility, speed, and assurance. Systems that are easier for voters to use can still be fragile if they rely on weak endpoints, poor administrative separation, or opaque counting logic. Systems that are highly controlled can become harder to operate, more expensive to audit, or less accessible if the design is too rigid.
Electronic voting also increases dependence on software supply chains, configuration management, and secure deployment practices. That is why architectures often benefit from a defense-in-depth approach, including secure build and update processes, hardened devices, and clear rollback and recovery procedures. Broader governance controls such as NIST Cybersecurity Framework 2.0 and identity-focused controls in eIDAS 2.0, the EU Digital Identity Framework are relevant where election ecosystems depend on trusted authentication and cross-system assurance.
Risk and Threat Considerations
Electronic voting concentrates risk in a small set of systems that can affect many ballots at once. The central concerns are malicious modification of votes, credential abuse by insiders or administrators, endpoint compromise, and failures in the evidence trail that make later verification uncertain.
Failure mechanism: An attacker or insider can exploit weak authentication, poor privilege separation, vulnerable endpoints, or insecure update paths to alter ballot capture or tally logic without immediate detection.
Impact: The result can be ballot manipulation, loss of voter confidence, disputed outcomes, privacy exposure, or an inability to prove that the recorded totals match the intended votes.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
NIST SP 800-63, NIST SP 800-53 Rev 5 and NIST CSF 2.0 set the governance and control requirements practitioners need to meet.
| Framework | Control / Reference | Relevance |
|---|---|---|
| NIST SP 800-63 | Digital Identity Guidelines | Defines identity assurance needed for eligibility and authenticated voting flows. |
| Recommendation — Use phishing-resistant identity assurance for eligible voters and administrators. | ||
| NIST SP 800-53 Rev 5 | AU-2 — Event Logging | Electronic voting depends on auditable records of administrative and tally actions. |
| AC-6 — Least Privilege | Voting systems need tight privilege separation for ballot, tally, and admin functions. | |
| SI-7 — Software, Firmware, and Information Integrity | Integrity controls are central to preventing ballot or tally tampering. | |
| Recommendation — Log election administration and tally events with tamper-evident retention. Restrict election operator privileges to the minimum required task set. Verify software and firmware integrity before deployment and during operation. | ||
| NIST CSF 2.0 | PR.AA-05 — Access Permissions are Managed | Access control is central to protecting election administration and tally systems. |
| Recommendation — Manage and review election-system access permissions continuously. | ||
Practitioner Guidance
Why practitioners should care: Electronic voting is one of the few systems where integrity and public legitimacy matter as much as technical security. Small control failures can have outsized political and operational consequences, so ownership must be explicit and testing must be continuous.
What to watch for: Pay close attention to privilege boundaries, device hardening, tamper evidence, and post-election reconciliation. The most important question is not only whether the system functions, but whether it can still be trusted after an incident, outage, or dispute.
Practitioner takeaway: Treat electronic voting as a high-assurance trust system, not a standard software deployment, and design every control around verifiability, secrecy, and recoverable evidence.