Digital public identity gaps are limiting access and trust

At a glance

What this is: Seamfix argues that digital public infrastructure fails when citizens cannot reliably prove identity, pushing governments toward mobile enrolment, liveness checks, OCR, and deduplication.

Why it matters: Public-sector identity teams need to treat verification as a service-delivery control, because exclusion, fraud, and duplicate records all degrade trust in downstream access decisions.

Context

Digital public infrastructure depends on identity proofing that can work at scale, not just in urban offices with specialist hardware. When enrolment is slow, duplicate records persist, or fraud checks are weak, the result is not only administrative friction but uneven access to services and weaker trust in government systems.

This article sits at the intersection of identity verification, fraud prevention, and public-sector governance. The central issue is whether a government can validate people remotely, consistently, and with enough assurance to support inclusion without turning the enrolment process into a barrier in itself.

Key questions

Q: How should governments design remote identity proofing without weakening assurance?

A: Governments should define which identity checks must be mandatory, which may be automated, and which require human review before issuance. Remote proofing works when the evidence chain is preserved, the policy is explicit, and the approval authority remains with the issuer rather than the platform operator.

Q: Why do weak identity verification controls create trust problems in public services?

A: Weak verification lets fraudulent or duplicate records enter the registry, which can distort eligibility, create duplicated benefits, and undermine confidence in the system. Once citizens or administrators see that records are unreliable, trust falls even when the underlying service is otherwise functional.

Q: What do organisations get wrong about large-scale biometric enrolment?

A: They often measure success by enrolment volume and forget the lifecycle after capture. The harder questions are whether the identifier remains linked to the right person, whether consent and revocation are handled properly, and whether the person can still access services after disruption. Scale without lifecycle control creates brittle identity infrastructure.

Q: How do organisations keep digital identity systems inclusive without weakening assurance?

A: They separate access from infrastructure scarcity by using evidence checks that work on widely available devices, then add governance for deduplication, exception handling, and fraud detection. Inclusion and assurance are compatible only when the operating model is designed for both.

Technical breakdown

Why identity proofing fails in last-mile DPI enrolment

Digital public infrastructure often inherits the limits of legacy enrolment models. If proofing depends on fixed offices, costly scanners, or repeated paperwork, the control fails where access is most needed. In remote settings, the problem is not only hardware availability but the mismatch between verification design and operating reality. A system that cannot collect trustworthy evidence on a standard mobile device will always struggle to scale beyond urban centres.

Practical implication: Design proofing flows that can operate on commodity devices and under field conditions, not only in central offices.

How liveness detection and image quality checks reduce fraud

Liveness detection aims to distinguish a real person from a spoofing attempt such as a photo, replay, or mask. Image quality checks raise the chance that the captured face or fingerprint can be matched reliably at the point of enrolment rather than failing later in the workflow. Together, these controls shift some trust decisions to capture time, which is where bad data is cheapest to reject. In DPI, that matters because one weak capture can propagate into every downstream entitlement decision.

Practical implication: Move fraud rejection and quality validation into the capture step so weak identity evidence does not enter the registry.

Why deduplication is a governance control, not just a database task

Deduplication is the process of finding and merging duplicate records so one person maps to one authoritative identity record. In public-sector identity systems, that is a governance control because duplicate identities can lead to duplicated benefits, conflicting service histories, and poor accountability across agencies. The challenge is not only matching records but deciding which source is authoritative and how exceptions are handled when confidence is low.

Practical implication: Treat deduplication as part of identity governance, with defined source-of-truth rules and review paths for uncertain matches.

Threat narrative

Attacker objective: The objective is to obtain or sustain access through fraudulent identity records while avoiding rejection at enrolment or later deduplication checks.

1. Entry occurs when enrolment systems rely on poor-quality identity evidence or reusable paper documents that can be copied, reused, or spoofed at the point of capture.
2. Credential_harvested becomes identity record harvesting when duplicate or fraudulent enrolments create multiple entries for the same person or a fabricated applicant.
3. Escalation follows when those weak records are accepted into service workflows, allowing false beneficiaries or bad data to influence access decisions across departments.
4. Impact is weakened trust in public services, higher manual review cost, and service delivery errors that reach genuine citizens and administrators alike.

Breaches seen in the wild

• Poland ArcGIS password leak 2023: An ArcGIS login emailed in 2020 was published from stolen mail in 2023 and still worked, exposing Polish military and infrastructure maps.
• United Nations breach 2021: Sakura Samurai used exposed Git credentials to reach 100,000+ UNEP staff records, then reported the flaw through the UN disclosure programme.

Read and download The State of NHI & AI Agent Breach Report 2026, covering 200+ breaches impacting Non-Human Identities including AI Agents.

NHI Mgmt Group analysis

Digital identity exclusion is a governance failure, not a user inconvenience. When public services depend on proofing models that assume urban access, specialist hardware, or repeated document submission, the system bakes inequality into the control design. That is an identity governance problem because access decisions become contingent on where a citizen lives and what equipment is available. Practitioners should measure proofing reach as a service-control issue, not only a transformation metric.

Fraud controls in DPI belong at the point of capture. If liveness detection and image-quality validation sit too far downstream, weak evidence enters the registry and multiplies remediation work later. The article’s emphasis on AI-assisted capture reflects a broader truth in identity programmes: rejection is cheapest when the evidence is first collected. Public-sector teams should treat capture-time assurance as a core control surface.

Deduplication is the named concept that DPI programmes too often underestimate. A single-source-of-truth registry only works when duplicate records are actively governed, not merely stored and reconciled later. In multi-agency environments, deduplication failure creates entitlement drift, reporting errors, and trust erosion across the service stack. Practitioners should treat duplicate identity suppression as an operational control with clear ownership and exception handling.

Remote enrolment expands the attack surface as well as the citizen base. Mobile-first proofing reduces infrastructure barriers, but it also increases reliance on capture quality, device integrity, and consistent policy enforcement in the field. That means the trust model moves away from the office counter and into distributed, lower-control environments. Public-sector identity teams need governance that assumes variability at the edge, not uniformity.

NHI and agentic identity lessons still matter here because the control pattern is the same. Whether the subject is a human citizen or an automated identity workflow, the system must know what was proven, when it was proven, and how confidently the result can be reused. In both cases, lifecycle governance and evidence quality determine whether access remains defensible. Practitioners should align proofing, deduplication, and lifecycle review into one accountable identity model.

What this signals

Digital public identity should be treated as a trust architecture, not a single onboarding step. Once governments start reusing proofing results across services, the quality of the initial capture determines the reliability of downstream access, casework, and benefit delivery. Practitioners should map where identity evidence is created, reused, and challenged, then tighten governance at those handoff points.

Remote enrolment increases inclusion only when evidence quality is controlled at the edge. If the field process cannot reject weak captures early, the burden shifts to back-office correction and manual review. That trade-off quickly erodes both scale and citizen confidence, especially in programmes that need to serve rural or last-mile populations.

Deduplication is the control that keeps public identity programmes from turning into record accumulation. Without authoritative merge rules, multiple identities for the same person can persist across departments and service lines. Public-sector teams should treat duplicate suppression as an operating discipline tied to accountability, auditability, and service integrity.

For practitioners

• Design mobile-first proofing workflows Support enrolment on standard smartphones and tablets so field teams can operate without specialised scanners or fixed offices.
• Move fraud checks to capture time Validate liveness, image quality, and document authenticity before records enter the identity repository, so bad evidence is rejected early.
• Govern deduplication as an identity control Define authoritative sources, merge rules, and exception review paths so duplicate records do not become parallel identities.
• Measure exclusion and rework rates Track how often applicants are delayed, rejected, or sent back for re-capture, then use those signals to identify where proofing is too brittle.
• Document last-mile trust assumptions Record where connectivity, device quality, and operator training can affect the reliability of enrolment evidence, especially in remote regions.

Key takeaways

• Digital public infrastructure becomes brittle when identity proofing depends on office-based processes that do not work for rural or last-mile populations.
• Fraud controls, image-quality checks, and deduplication are not separate tasks, they are part of the same governance chain that protects trust in public identity.
• Public-sector teams should measure identity proofing by how well it expands access without multiplying manual review, duplicate records, or eligibility disputes.

Key terms

• Identity proofing: The process of verifying that a person is who they claim to be before granting or restoring access. In higher-risk recovery paths, proofing can include stronger evidence checks such as government ID validation or liveness-based facial verification so the assurance level matches the sensitivity of the request.
• Liveness Detection: Liveness detection is the mechanism that checks whether a biometric sample comes from a real, present person rather than a spoof such as a photo, screen, or mask. In identity programmes, it is a core defence against presentation attacks and should be tested under realistic operating conditions.
• Deduplication: Deduplication is the process of identifying repeated applicants or identities across programmes so the same person or entity is not approved multiple times without detection. It is a fraud and governance control that helps expose synthetic identity patterns, reuse, and hidden overlap across customer populations.
• Digital Infrastructure: Digital infrastructure is the underlying technology and process foundation that supports online services, transactions, and identity workflows. It includes the systems, standards, and operational capabilities needed for secure digital interactions. For onboarding and KYC, it determines how reliably organisations can verify users, exchange data, and scale services across channels.

Deepen your knowledge

NHI Foundation Level course, the industry's only accredited NHI security programme, covers NHI governance, identity lifecycle, and secrets management in a way that helps practitioners connect identity assurance to operational control. It is suitable for security and identity teams that need a common language for governance, verification, and lifecycle oversight.