Join our Newsletter — 33% off our NHI Course
Home› Glossary› Identity Beyond IAM› Remote Electronic Voting
Identity Beyond IAM

Remote Electronic Voting

← Back to Glossary
By NHI Mgmt Group Updated November 3, 2026 Domain: Identity Beyond IAM

Remote electronic voting is a voting model that allows eligible citizens to cast a ballot from outside a physical polling place, often through a secure mobile or web channel. It is used to improve participation for rural, overseas, and mobility challenged voters while preserving election controls.

What Remote Electronic Voting Is and How It Changes the Voting Model

Remote electronic voting moves ballot casting away from the polling place and into a digital channel, usually web-based or mobile. That changes the trust model: election integrity now depends not only on voter eligibility and tallying rules, but also on device trust, session integrity, communications security, and the resilience of the platform that receives and records the vote.

It is typically justified by accessibility and participation goals, especially for voters who cannot easily reach a polling station. At the same time, the design has to preserve core election properties such as eligibility, one-person-one-vote, ballot secrecy, and a verifiable count.

Security Properties Remote Voting Must Preserve

The security bar is higher than for ordinary online transactions because elections need both correctness and public confidence. A remote voting system must resist impersonation, ballot manipulation, double voting, coercion amplification, and hidden changes to the recorded vote, while still allowing eligible citizens to complete the process successfully.

Strong identity assurance helps, but identity alone is not enough. A well-authenticated voter can still be exposed to malware on the endpoint, malicious network conditions, or a compromised voting application, so the system must assume that some part of the client environment may be untrusted.

That is why election systems usually combine cryptographic protections, strict workflow controls, auditability, and operational separation between voter authentication and ballot secrecy. The exact mix varies by jurisdiction, because no single technical model solves every election-risk trade-off.

How Organisations Evaluate Exposure and System Readiness

Before a remote voting channel is deployed, election owners need a clear inventory of the end-to-end flow: who can vote remotely, what devices and platforms are allowed, where the ballot is transmitted, and which components store eligibility, transaction, and audit data. Exposure also depends on whether the service is internet-facing, whether third-party components are involved, and how the system handles outages or degraded service.

Readiness checks should include vendor review, code and configuration review, and threat modelling of the full vote path. For identity assurance and authentication design, the NIST SP 800-63 Digital Identity Guidelines provide a useful reference point for assessing how strongly a voter is verified before ballot access is granted.

For broader control design, election operators often rely on principles that map to least privilege, logging, change control, and resilience. The NIST Cybersecurity Framework 2.0 is useful as a cross-functional structure for governance, protection, detection, response, and recovery, while the NIST Privacy Framework is helpful where voter data minimisation and sensitive-data handling are part of the design.

Remediation, Monitoring, and Post-Event Assurance

When remote voting is used, the biggest operational weakness is often not one dramatic failure but a chain of small ones, such as weak authentication fallback, a vulnerable web component, a misconfigured update path, or insufficient visibility into abnormal voting patterns. Controls need to make the system recoverable, not just available.

That means maintaining incident response procedures, immutable or tamper-evident logs where feasible, and a way to review whether ballots, eligibility records, or administrative actions were altered after submission. If a weakness is found after voting has begun, compensating controls may be needed immediately, including temporary restriction of the remote channel, manual verification checks, or re-validation of affected records.

The post-event phase matters as much as the live service. Election owners should be able to determine whether suspicious activity affected access, ballot submission, or tally integrity, and whether any supporting infrastructure, such as web endpoints or administrative consoles, needs follow-up hardening before the next election cycle.

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 CSF 2.0 and OWASP ASVS set the technical controls, while ISO/IEC 27001:2022 and NIS2 define the regulatory obligations.

FrameworkControl / ReferenceRelevance
NIST SP 800-63Digital Identity GuidelinesDefines assurance choices for verifying remote voters before ballot access.
Recommendation — Use phishing-resistant authentication and the appropriate assurance level for voter identity proofing.
NIST CSF 2.0GV.RM-01 — Risk Management StrategyRemote voting requires election-specific risk decisions and tolerance setting.
PR.AA-05 — Identity Management, Authentication, and Access ControlRemote ballot access depends on strong voter authentication and access enforcement.
DE.CM-01 — Networks and Services Monitored to Find Anomalies and Indicators of CompromiseRemote voting needs monitoring for abnormal access, submission, and service behavior.
Recommendation — Set explicit risk tolerance for remote voting and review it against integrity and availability threats. Enforce strong authentication and tightly control ballot access paths for eligible voters. Monitor voting infrastructure for anomalous access, abuse, and service degradation during election windows.
ISO/IEC 27001:2022A.5.15 — Access controlRemote voting relies on controlled access to voter and election administration functions.
A.8.15 — LoggingAuditability is essential for remote voting integrity and post-event review.
Recommendation — Restrict access to election administration and ballot-handling functions on a least-privilege basis. Log authentication, ballot submission, and administrative actions for later integrity review.
OWASP ASVSV6 — AuthenticationRemote voting depends on robust user authentication before ballot submission.
V7 — Session ManagementRemote voting sessions must prevent hijack, replay, and unauthorized reuse.
V16 — Security Logging and Error HandlingRemote voting needs trustworthy logs and safe failure handling for audit and recovery.
Recommendation — Require strong authentication controls that match the sensitivity of voter access. Protect voting sessions against fixation, theft, and reuse across the voting flow. Record security-relevant events and fail safely without exposing sensitive voting details.
NIS2Cybersecurity risk-management measuresIf remote voting is operated as a critical public service, resilience and incident handling matter materially.
Recommendation — Build governance, resilience, and incident-handling measures proportional to the service’s public impact.

Practitioner Guidance

Governance implication: remote electronic voting should be treated as a high-assurance public trust service, not as a normal citizen portal. That means ownership must sit with the election authority, with clear accountability for authentication policy, ballot secrecy, platform operations, and independent verification.

What to watch for: the most important warning sign is any gap between what the system can technically verify and what voters or auditors can independently trust. If that gap widens, the system may still be functional, but confidence in the election outcome can deteriorate quickly.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Reviewed and updated by the NHIMG editorial team on November 3, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org