National eID Card Deployment

How countries implement electronic identity cards.

| 4 min read

National eID Card Deployment

National electronic identity (eIDeIDIdentityNational ID with embedded chip.Click to view →) programmes represent some of the most complex smart card deployments on earth — combining cryptographic security, large-scale PKI, biometric enrolment, legal identity frameworks, and citizen-facing service integration into a single national programme. Dozens of countries have deployed eID cards, from Estonia's pioneering 2002 rollout to Germany's nPA, Belgium's eID, and India's Aadhaar-linked smart card initiatives.

eID Architecture and Components

A national eID system is not a single product but an ecosystem of interoperating components:

Component Function
eID Chip Stores identity data, certificates, and biometrics
Country Root CA Top of the PKI trust chain
Document Signer Signs chip data at personalisation
eID Server / Verification Service Online terminal authentication for e-services
eID Client (local software) Browser plugin or OS integration for online use
Enrolment Infrastructure Biometric capture, identity proofing, card personalisation
Revocation Service CRL / OCSP for certificate status

The card itself is a contact smart card (ISO 7816 compliant) with an optional contactless interface for border control (ISO 14443). It holds at minimum: a qualified electronic signature certificate, an authentication certificate, and often a civic identifier.

Use the cost-estimator to model the total cost of ownership across enrolment stations, CA infrastructure, card personalisation, and ongoing revocation services.

PKI Infrastructure for eID

The national PKI is the trust backbone of an eID scheme. A typical hierarchy:

Country Root CA (offline HSM, ceremony-based)
  └── Country Sub CA (online, issues to:)
        ├── Document Signing CA (personalisation)
        ├── Authentication CA (citizen certs)
        └── Qualified Signature CA (legal signature certs)

Common Criteria evaluation — typically EAL 4+ or EALEALSecuritySecurity evaluation depth rating (1-7).Click to view → 5+ — is required for the chip and often for the CA hardware (HSM). The Protection ProfileProtection ProfileSecuritySecurity requirements document for CC.Click to view → for electronic identity documents (BSI-CC-PP-0056 for German nPA) defines the precise security requirements against which vendors are evaluated.

CAC (US Common Access Card) and PIV (Personal Identity Verification) are the US government equivalents: PIVPIVIdentityUS federal identity card standard.Click to view → uses NIST SP 800-73 on top of standard smart card hardware, while the European eID ecosystem converges on the eIDAS Regulation framework.

Identity Verification and Enrolment

Stage Process Fraud Risk
Identity Proofing Document verification + biometric capture Impersonation fraud
Deduplication Biometric matching against existing database Multiple identity fraud
Personalisation Electrical and graphical personalisation Chip substitution
Activation PIN setting, certificate issuance Social engineering
Lifecycle Renewal, revocation, lost card replacement Revocation evasion

Electrical personalisation writes cryptographic keys and data to the chip during card manufacturing. Graphical personalisation laser-engraves the holder's photo and data into the card bodycard bodyHardwarePlastic substrate forming the card physical structure.Click to view →. Both processes are performed in certified secure facilities, with audit trails linking each card to its production batch and enrolment record.

Online Authentication with eID

The eID card's authentication certificate enables online service login — a qualified alternative to username/password. The flow:

  1. Citizen visits an e-government portal.
  2. The portal invokes the national eID protocol (e.g., German eID uses Extended Access Control with the eID Server acting as the online terminal).
  3. The eID Client on the citizen's computer or smartphone reads the card.
  4. The chip performs a cryptographic challenge-response with the eID Server.
  5. The server returns verified attributes (name, DOB, address) to the portal — without revealing the full identity document number.

This attribute-selective disclosure is a key privacy feature: a service requiring only age verification receives a boolean "over 18" rather than the full date of birth.

Privacy and Regulatory Considerations

Privacy Feature Implementation
Sector-specific identifiers Different pseudonyms per service sector (DE nPA)
Attribute minimisation Selective attribute release, not full data dump
No central audit log Card-to-service interaction not logged centrally
Biometric access control EAC limits fingerprint read to authorised terminals
GDPR compliance Data minimisation, purpose limitation, erasure rights

The eID and ePassport standards share significant technical infrastructure (both use PACEPACEApplicationStrong ePassport authentication protocol.Click to view →, EAC, and ICAO-compatible PKI) but serve different legal purposes — ePassportePassportApplicationPassport with embedded contactless chip.Click to view → for border control, eID for domestic civil services and e-government.

For the travel document variant, see the ePassport Technology Guide. For US government smart card specifics, consult the National eID Deployment Guide.

Frequently Asked Questions

Our guides cover a range of experience levels. Getting Started guides introduce smart card fundamentals. Security guides address Common Criteria certification and key management. Programming guides target developers working with APDU commands, JavaCard applets, and GlobalPlatform card management.