Join our Newsletter — 33% off our NHI Course

Could app attestation stop automated voter fraud at the API edge?

 

(@nhi-mgmt-group)
Member Moderator
Joined: 2 years ago
Posts: 20218
Topic starter  

TL;DR: Mobile election registration APIs can be abused when they do not verify app integrity and device authenticity, according to Approov. Device trust has to move into the request path before identity workflows accept high-risk enrolment traffic.

Editorial analysis by NHI Mgmt Group, based on content published by Approov: “Defending Democracy: How Mobile App Attestation Blocked Automated Voter Fraud”.

By the numbers:

  • 100% of emulator-based, fraudulent registration attempts were automatically blocked.

Key questions

Q: Why do bot controls alone miss some mobile API abuse?

A: Bot controls detect automation patterns, but they do not always prove the request came from a legitimate app on a trusted device.

Q: How should security teams govern mobile registration APIs in high-trust workflows?

A: Teams should govern mobile registration APIs as identity-critical services.

Q: What breaks when mobile APIs cannot verify the originating device?

A: When a mobile API cannot verify the originating device, automated clients can mimic legitimate users and submit fraudulent requests at scale.

Practitioner guidance

  • Implement app attestation for voter-facing workflows Require server-side proof that the request came from an unmodified official app on a trusted device before the API processes registration or ballot requests.
  • Add bot filtering to the outer API layer Use network-level controls to block emulator traffic, scripted requests, and abnormal request bursts before they reach identity enrolment endpoints.
  • Separate high-trust registration flows from general mobile traffic Place additional verification on workflows that can create, modify, or activate citizen records so automation cannot blend into normal app usage.

Bottom line: Mobile registration channels can be abused when APIs accept traffic without verifying app integrity and device authenticity.

Glossary terms: App Attestation, Device Trust, Access Provenance

Explore further

View Full Forum →  |  NHI Foundation Course →  |  Our Services →  |  Read the full analysis →


This topic was modified 2 weeks ago by NHI Mgmt Group

   
Quote
(@mr-nhi)
Member Moderator
Joined: 6 months ago
Posts: 20698
 

Election APIs need request provenance, not just authentication: a valid session token is not enough when automation can replay requests from emulators or repackaged apps. The real control question is whether the server can trust the originating app instance and device state before accepting the transaction. That makes attestation a governance mechanism for election integrity, not a niche mobile feature. Practitioners should treat provenance checks as part of the access decision.

A few things that frame the scale:

A question worth separating out:

Q: What should teams do when a citizen-facing API is targeted by automated registration abuse?

A: Containment should focus on the request path, not only on downstream records. Tighten app attestation, enforce bot filtering, raise verification for high-risk enrolment actions, and review whether synthetic traffic has already altered authoritative data. If the workflow creates or modifies identity records, treat it as a priority control gap rather than a routine abuse event.

👉 Read our full editorial: Election registration APIs need device trust, not just bot filtering


This post was modified 2 weeks ago by NHI Mgmt Group

   
ReplyQuote
Share:

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.