Digital voting is the use of electronic systems to collect, record, and verify ballots. The security challenge is to preserve voter privacy while ensuring authenticity, integrity, and auditability. A viable design must protect against coercion, impersonation, tampering, and disputes over whether a vote was cast correctly.
Expanded Definition
Digital voting is more than replacing paper with screens. In secure elections, it includes ballot capture, cryptographic protection, voter authentication, tallying, dispute handling, and records that can be independently audited. The design challenge is to preserve ballot secrecy while proving the system behaved correctly, which is why election security guidance emphasizes trust boundaries, verifiability, and resilience rather than simple access control. For broader governance context, the NIST Cybersecurity Framework 2.0 is useful for organizing risks around identify, protect, detect, respond, and recover outcomes.
In the NHI and IAM domain, digital voting matters because election workflows increasingly depend on service accounts, device identities, signing keys, and backend automation that can impersonate trusted components. Definitions vary across vendors on whether digital voting includes supervised kiosk voting, internet voting, or end-to-end verifiable systems, so the term should be read in context. The most common misapplication is treating digital voting as a pure user-interface problem, which occurs when designers ignore the identity, cryptographic, and audit controls that determine whether a ballot can be trusted.
Examples and Use Cases
Implementing digital voting rigorously often introduces tradeoffs between usability, accessibility, and the strength of election assurance, requiring organisations to weigh fast participation against stronger verification and audit requirements.
- Remote voting systems for controlled environments, where authenticated voters submit ballots through a networked portal and the backend must prevent replay, tampering, and vote substitution.
- In-person electronic ballot marking, where a device records selections but the election still depends on paper or cryptographic audit trails to resolve disputes.
- End-to-end verifiable voting, where cryptographic proofs allow observers to confirm that recorded ballots were included in the tally without exposing voter identity.
- Election administration platforms, where privileged service accounts, signing keys, and automation pipelines must be governed like high-value NHIs, similar to the failure modes described in the CI/CD pipeline exploitation case study.
- Ballot storage and export workflows, where misconfigured repositories or shared systems can expose election artifacts, echoing patterns seen in Millions of Misconfigured Git Servers Leaking Secrets.
For implementation patterns, election operators often compare their assurance model with controls used in the NIST Cybersecurity Framework 2.0, then map the same thinking to identity, logging, and recovery requirements.
Why It Matters in NHI Security
Digital voting exposes a concentrated set of NHI risks because the systems that count, verify, and publish results are only as trustworthy as the identities behind them. A malicious or compromised service account can alter tallies, suppress ballots, or interfere with audit logs without ever touching a human voter credential. That is why election infrastructure must treat signing keys, API tokens, administrator sessions, and automation identities as critical control points, not implementation details.
The operational stakes are high: NHI Mgmt Group reports that 80% of identity breaches involved compromised non-human identities such as service accounts and API keys, underscoring how often trust failures begin with machine credentials. In digital voting, one weak integration or mismanaged secret can undermine the chain of custody for the entire election. The Ultimate Guide to NHIs also shows that 97% of NHIs carry excessive privileges, a pattern that is especially dangerous when those identities can affect ballot storage, audit exports, or administrative override functions.
Organisations typically encounter the seriousness of digital voting only after a recount, audit challenge, or public dispute, at which point identity integrity becomes operationally unavoidable to address.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
OWASP Agentic AI Top 10 and OWASP Non-Human Identity Top 10 address the attack and risk surface, while NIST CSF 2.0, NIST Zero Trust (SP 800-207) and NIST SP 800-63 set the governance and control requirements practitioners need to meet.
| Framework | Control / Reference | Relevance |
|---|---|---|
| NIST CSF 2.0 | PR.AC | Digital voting depends on strong identity and access control across ballot, admin, and audit systems. |
| NIST Zero Trust (SP 800-207) | PA, RA, SP | Zero Trust principles apply to voting infrastructure that cannot trust network location alone. |
| NIST SP 800-63 | IAL/AAL/FAL | Identity assurance levels inform how strongly voters and election staff should be authenticated. |
| OWASP Agentic AI Top 10 | A1 | Automated election workflows can behave like agents and must be constrained against unsafe actions. |
| OWASP Non-Human Identity Top 10 | NHI-02 | Voting systems rely on secrets, signing keys, and service accounts that require strict governance. |
Restrict election system access, authenticate privileged users, and monitor all privileged activity end to end.
Related resources from NHI Mgmt Group
- Why can blockchain make digital voting more reliable in high-trust use cases?
- What is the difference between identity forensics and standard digital forensics?
- How should organisations govern access across many APIs in a digital transformation programme?
- Why does digital transformation make identity governance harder?
