Download (PDF, 589 KB, Datei ist nicht barrierefrei

Download (PDF, 589 KB, Datei ist nicht barrierefrei Download (PDF, 589 KB, Datei ist nicht barrierefrei

personalausweisportal.de
from personalausweisportal.de More from this publisher

Innovations for<br />

an eID Architecture<br />

in Germany<br />

www.bsi.bund.de


thE BsI<br />

the German Federal Office for Information Security<br />

(Bundesamt für Sicherheit in der Informationstechnik - BSI)<br />

is Germany’s central It security service provider: a neutral,<br />

independent authority for issues relating to It security in the<br />

information society. the BsI provides information on risks<br />

and threats relating to the use of information and communication<br />

technology, develops security guidelines, advises<br />

manufacturers, d<strong>ist</strong>ributors and users. the BsI primarily<br />

advises public admin<strong>ist</strong>rations on the national, state and<br />

local levels, but also seeks to exchange information with<br />

businesses and private users.<br />

Contents<br />

ContEnts<br />

1. The new identity card – secure, standardized<br />

proof of identity in the digital world 4<br />

2. User-oriented requirements for the<br />

identification function of the new identity card 6<br />

3. Application software for users – AusweisApp 8<br />

4. Security mechanisms for the identification<br />

function of the new ID card 9<br />

4.1 Password Authenticated Connection<br />

Establishment (PACE) 10<br />

4.2 Extended Access Control (EAC),<br />

readers and EAC box 11<br />

4.3 Passive Authentication (PA) 14<br />

4.4 Public Key Infrastructures (PKI)<br />

for electronic identity documents 15<br />

4.4.1 Country Signing Certificate Authority (CSCA) 15<br />

4.4.2 Country Verifying Certificate Authority (CVCA) 16<br />

5. The eID server – interface for web applications 19<br />

6. Revocation management in the new<br />

German identity card 20<br />

7. References 23<br />

Imprint 24<br />

2 3


IDEntIFICAtIon FunCtIon IDEntIFICAtIon FunCtIon<br />

1. The new identity card – secure,<br />

standardized proof of identity<br />

in the digital world<br />

starting november 1 st , 2010, the new identity card will be<br />

introduced in Germany as an electronic, multi-functional<br />

card in credit-card format, valid as a travel document and as<br />

proof of identity both personally and in the electronic world.<br />

this identity card implements an innovative concept based<br />

on a contactless interface that is already in use for electronic<br />

passports world-wide.<br />

the new identity card not only represents a modern<br />

sovereign document that will significantly improve the<br />

identification of persons e.g. when crossing borders. the<br />

ID card will also be equipped with additional electronic<br />

functions, in par ticular electronic ID (eID) and the optional<br />

Qualified Electronic signature (QEs), which offer users<br />

significant advantages. these functionalities enable individuals<br />

to positively identify themselves online and issue<br />

legally binding electronic declarations of will. they are thus<br />

a key instrument for enabling legally valid contacts to be<br />

con cluded over the Internet, and are intended to promote<br />

streamlined eGovernment and eBusiness services.<br />

the introduction of the identification function of the new<br />

identity card entailed preparing, developing and deploying<br />

a soph<strong>ist</strong>icated It infrastructure and embedding it in a complex<br />

overall system with more than 60 million participating<br />

individuals. this required firstly that the associated organizational,<br />

legal and technical prerequisites be created. the<br />

German ID Card Act [PAuswG 2010] sets out the general legal<br />

framework for identity documentation and electronic proof<br />

of identity; the corresponding regulation [PAuswV 2010]<br />

defines in particular the requirements for security and data<br />

protection of the eID infrastructure. these are augmented<br />

by close to 20 technical Guidelines and protection profiles<br />

promulgated by the Federal office for Information security<br />

(BsI), which are published in binding form in the German<br />

Federal Gazette. some of these requirements are explained<br />

as examples in this brochure.<br />

the infrastructure of the new identity card is intended to<br />

realize a trustworthy and efficient identity management.<br />

the combination of a sovereign identity document with<br />

eID functionality for eBusiness and eGovernment will also<br />

provide users with a secure identity in the electronic world<br />

and afford them better protection against many types of<br />

cybercrime, such as phishing and identity theft.<br />

Particular priority was placed on data protection, data<br />

security and preserving information self-determination. All<br />

disclosures and transmissions are reliably protected using<br />

internationally recognized and established encryption processes.<br />

As part of the eID function, user data are exchanged<br />

only between the provider of the service and the holder of<br />

the identity document.<br />

Biometrically relevant data, i.e. photo, where applicable<br />

fingerprints, eye color, height and personal signature, are<br />

never transmitted to service providers or via the Internet.<br />

only sovereign authorities possess the authorization and the<br />

technical means to query such sensitive information.<br />

4 5


DAtA ProtECtIon DAtA ProtECtIon<br />

2. User-oriented requirements for the<br />

identification function of the new<br />

identity card<br />

As a protective function for the personal data stored on<br />

the ID card chip, legal requirements stipulate that all<br />

institutions that want to access some or all of this data<br />

must possess an appropriate authorization. Before such<br />

an authorization is issued, government authorities review<br />

which data the service provider (e.g. an online retailer, or<br />

also public offices) absolutely requires for his pur poses,<br />

and whether he is trustworthy. the authorization is always<br />

issued for only a limited period and can be re voked.<br />

technically, the authorization is implemented using<br />

authorization certificates whose status is queried at terminal<br />

authorization.<br />

Before the new ID card releases data to a service provider<br />

with an authorization certificate, the service provider must<br />

display his certificate, and thus also the data he is allowed to<br />

read. the holder of the identity card always has the option of<br />

restricting the read authorization to less data.<br />

the ID card holder must then enter a six-digit personal<br />

identi fication number (PIn). If the electronic verification of<br />

the authorization certificate is positive, the data are released.<br />

All data are transmitted in encrypted form.<br />

the read authorization can be restricted so that for example,<br />

only age-related information can be queried. there is also a<br />

pseudonym function that enables users to log onto and be<br />

recognized by a service provider such as an Internet forum<br />

without revealing any personal data to the service provider.<br />

this function is card- and service-specific: in other words,<br />

service providers who compare their databases cannot<br />

determine whether the pseudonyms reg<strong>ist</strong>ered there belong<br />

to one and the same person.<br />

In the event that the new identity card is lost, the eIDfunctionality<br />

can be revoked using a personal password<br />

(revocation management, see chapter 6). If the personal<br />

identification number is entered incorrectly three times, its<br />

reactivation requires a PIn un blocking key (PuK).<br />

If desired, the card’s eID functionality can be disabled by the<br />

issuing authority.<br />

A QEs function can also be activated on the new identity<br />

card. using this signature, it is possible to fulfill requirements<br />

for the written form under contract law by electronic means.<br />

the electronic certificates required for this process can be<br />

purchased from commercial providers.<br />

6 7


IntErFACEs<br />

3. Application software for<br />

users – AusweisApp<br />

In order to use their new identity card on line, users require<br />

a software that serves as the interface between the ID, the<br />

card reader and the service provider’s eID server. this software,<br />

called “AusweisApp” (“Ausweis” is the German word<br />

for “ID document”), will be available free of charge on a<br />

web portal of the German Federal Min<strong>ist</strong>ry of the Interior<br />

(https://www.ausweisapp.bund.de) for the operating<br />

systems Windows, Linux and Mac os.<br />

In addition to utilizing the identification function of the<br />

new ID cards, AusweisApp also enables qualified electronic<br />

signature with multiple signature cards, both conventional<br />

contact type cards and contactless devices like the new<br />

ID card. Functions of the German health card are also<br />

supported.<br />

AusweisApp is an implementation of the technical Guideline<br />

eCard-API Framework [tr-03112], which defines easy-touse,<br />

uniform interfaces for communication between card<br />

readers, cards and applications (web-based and local).<br />

4. Security mechanisms for the<br />

identification function of the<br />

new ID card<br />

the security mechanisms and resulting It infrastructures for<br />

the new ID card ensure protection of personal data, proof of<br />

the authenticity of the identity document and proof against<br />

forgery.<br />

special attention has been given to solutions for securing the<br />

contactless interface between the ID card and the terminal –<br />

which, among other things, must meet the requirements for<br />

qualified electronic signatures.<br />

the following protocols and other measures for achieving<br />

the aforementioned security objectives were developed<br />

under the active leadership and participation of the BsI.<br />

8 9<br />

Abbreviation<br />

Full name Purpose<br />

PACE Password<br />

Authen ticated<br />

Connection<br />

Establishment<br />

EAC Extended Access<br />

Control<br />

CA: Chip<br />

Authentication<br />

TA: Terminal<br />

Authentication<br />

PA Passive<br />

Authentication<br />

RI Restricted<br />

Identification<br />

sECurIty<br />

Access control, protects the<br />

RF chip from being read at a<br />

d<strong>ist</strong>ance.<br />

Extended access control,<br />

comprising two subprotocols.<br />

Establishment of a secure link and<br />

detection of “cloned” RF chips.<br />

Authentication of terminal<br />

device for reading sensitive data<br />

from RF chip.<br />

Validation of authenticity and<br />

integrity of the data on the RF chip.<br />

Generation of chip- and providerspecific<br />

pseudonyms.


sECurIty<br />

PKI Public Key<br />

Infrastructure<br />

CSCA: Country<br />

Signing Certificate<br />

Authority<br />

CVCA: Country<br />

Verifying Certificate<br />

Authority<br />

Hierarchy of digital certificates.<br />

Hierarchy of digital certificates<br />

for signing data in electronic<br />

identity documents.<br />

Hierarchy of digital certificates<br />

for read authorization of<br />

electronic identity documents.<br />

4.1 Password Authenticated Connection<br />

Establishment (PACE)<br />

Password Authenticated Connection Establishment (PACE)<br />

ensures that the contactless rF chip in the new identity<br />

card cannot be read without explicit access, and that data<br />

are exchanged with the terminal device in encrypted form<br />

[Bender 2008].<br />

the password that can be used for PACE depends on the<br />

authorization certificate of the reader (terminal) device used.<br />

usually, this is the six-digit personal identification number<br />

(PIn), which is known only to the holder of the identity card.<br />

For reader devices with authorization certificates for<br />

sovereign use, e.g. border control, either a Machine<br />

readable Zone (MrZ) printed on the back of the new<br />

identity card or the six-digit card access number (CAn)<br />

printed on the front is sufficient.<br />

4.2 Extended Access Control (EAC),<br />

readers and EAC box<br />

Extended Access Control (EAC) comprises an array of<br />

protocols that are always executed in a specific order,<br />

depending on which electronic identity document is to be<br />

read [tr-03110].<br />

the EAC protocols include Chip Authentication (CA)<br />

and terminal Authentication (tA). the two protocols are<br />

executed together with Password Authenticated Connection<br />

Establishment (PACE) and Passive Authentication (PA).<br />

the purpose of Chip Authentication is to confirm that<br />

the chip is a real chip (and not a forgery or a clone) and to<br />

establish a secure connection between the chip and the<br />

reader, or between the chip and the service provider in the<br />

case of online authentication.<br />

Chip Authentication is based on Diffie-hellman key exchange,<br />

in which the reader or terminal device uses an<br />

ephemeral key pair and the chip a static pair. the chip’s<br />

public key is signed during the process of generating it<br />

(Passive Authentication – see section 4.3).<br />

the use of the signed key verifies the authenticity of the chip;<br />

at the same time, a strongly-encrypted and authenticated<br />

end-to-end channel is established between the chip and – in<br />

the case of online authentication – the service provider.<br />

the advantage of PACE is that the length of the password<br />

All data on the new identity card are treated as confidential<br />

has no effect on the security level of the encryption. In other<br />

and must be protected against being read by unauthorized<br />

words, even when the CAn or PIn are used, which are short<br />

persons. the terminal Authentication (tA) protocol was<br />

compared to the MrZ, the data on the rF chip of the electro-<br />

developed for this purpose. sensitive data can only be read<br />

nic identity card are strongly protected during transmission.<br />

when this protocol has been successfully executed on the<br />

reader. the rF chip in the identity document is designed so<br />

that it enables reading of specific data only when the reader<br />

10 11<br />

sECurIty


sECurIty<br />

device (terminal) can demonstrate an explicit read authorization<br />

for these specific data (e.g. only date of birth). the<br />

Country Verifying Certificate Authority certificate (CVCA<br />

certificate) is stored on the rF chip to verify this authorization.<br />

this certificate forms the root of the Country Verifier<br />

Public Key Infrastructure (CV-PKI), a hierarchy of authorization<br />

certificates for reading sensitive data from identity<br />

documents.<br />

In Terminal Authentication, the reader (terminal) transmits<br />

its read authorization to the rF chip in the form of a<br />

terminal certificate. It also transmits the CVCA certificate<br />

and all certificates in the hierarchy between these two<br />

certificates. this enables the rF chip to verify the authenticity<br />

and integrity of the terminal’s certificate. A positive<br />

result requires that each of the subsequent certificates in the<br />

hierarchy is signed with the private key of its predecessor,<br />

starting with the CVCA certificate. the rF chip “knows” that<br />

this certificate is trustworthy because it was stored on the rF<br />

chip when it was manufactured.<br />

once the authenticity and integrity of the terminal<br />

certificate transmitted by the reader has been established,<br />

the rF chip must verify that this certificate was really issued<br />

for this device. to this end, the rF chip transmits a random<br />

number to the reader, which signs it with a private key<br />

belonging to the terminal certificate. the reader device<br />

then transmits the signed random number back to the<br />

rF chip. using the terminal device’s public key, which<br />

is contained in the terminal certificate, the rF chip can<br />

verify the signature of the random number and determine<br />

whether the possesses has the private key that matches the<br />

certificate.<br />

EAC box<br />

Key component for ID card amendment<br />

Reg<strong>ist</strong>ration office PC<br />

Authorization PKI<br />

Each reader that wants to access the data of the electronic<br />

identity card requires corresponding authorization certificates,<br />

each with their own private and public keys, which<br />

must be renewed regularly via a PKI. the EAC box provides<br />

these functions in an encapsulated form in an evaluated<br />

and certified environment and communicates with external<br />

components and services via standardized interfaces<br />

[tr-03131].<br />

once the electronic identity card has been introduced, the<br />

EAC box will be used as a reader device for changing address<br />

data on the eID at municipal reg<strong>ist</strong>ration offices. Further<br />

uses in addition to this scenario are conceivable (e.g. border<br />

control).<br />

12 13<br />

<br />

Flow control<br />

Crypto<br />

protocols<br />

Stored<br />

certificates<br />

and keys<br />

EAC box core<br />

sECurIty<br />

Card<br />

reader<br />

Display<br />

PIN pad<br />

Specification: BSI Technical Guideline TR-03131 “EAC-Box Architecture and Interfaces”<br />

Protection profile: “CC Protection Profile for Inspection Systems”<br />

Secure channel


sECurIty<br />

4.3 Passive Authentication (PA)<br />

the purpose of Passive Authentication (PA) is to validate the<br />

authenticity and integrity of the data on the rF chip of the<br />

identity document.<br />

In the course of manufacturing the electronic identity<br />

document, the data stored on the rF chip are digitally<br />

signed. this process uses something called a document<br />

signing certificate, which in turn is signed with the Country<br />

signing Certificate Authority certificate (CsCA certificate)<br />

of the issuing nation and is available only to the officially<br />

authorized ID manufacturer. this certificate forms the<br />

bedrock of the Country signing Certificate Authority<br />

Public Key Infrastructure (CsCA-PKI), a hierarchy of<br />

certificates that verify the integrity of data on identity<br />

documents.<br />

When an identity document is read, Passive Authentication<br />

verifies the signature of the data stored on the rF chip<br />

and traces it back to the CsCA certificate. this enables it to<br />

determine whether the data in the identity document were<br />

written on the rF chip by the officially authorized ID manufacturer<br />

and that their integrity is not compromised.<br />

4.4 Public Key Infrastructures (PKI)<br />

for electronic identity documents<br />

the new identity card requires two Public Key Infrastructures<br />

(PKI): one PKI for verifying the authenticity of<br />

electronic identity documents (Passive Authentication), the<br />

Country signing Certificate Authority (CsCA); and one PKI<br />

to protect the fingerprints on electronic identity documents<br />

(terminal Authentication), the Country Verifying Certificate<br />

Authority (CVCA). technical Guideline tr-03128 describes<br />

the basic functionalities and requirements of these infrastructures.<br />

4.4.1 Country Signing Certificate Authority (CSCA)<br />

InFrAstruCturEs<br />

the Country signing Certificate Authority (CsCA) is operated<br />

by the BsI. this authority generates the German root certificates<br />

(CsCA certificates) on a regular basis, which in turn serve<br />

as the source for the private keys of the document signing certificates<br />

of the passport or ID card manufacturer. the passport<br />

or ID card manufacturer uses the private keys of the document<br />

signing certificates to sign files on the electronic identity<br />

document that represent the document’s data. the document<br />

signing certificate is also electronically stored on the identity<br />

document.<br />

using the root certificate, it is possible to verify whether an<br />

electronic identity document was really created on behalf of<br />

the issuing nation, and whether the data have been changed<br />

in any way since production. this is realized using Passive<br />

Authentication.<br />

to enable the authenticity and integrity of German electronic<br />

identity documents to be verified at border control points in<br />

other countries, and passports of other countries to be tested<br />

14 15


InFrAstruCturEs<br />

at the German border for their authenticity and integrity,<br />

the various nations must exchange their root certificates in a<br />

secure manner. this is achieved either via diplomatic pouches<br />

or via the ICAo Public Key Directory (ICAo-PKD).<br />

4.4.2 Country Verifying Certificate Authority (CVCA)<br />

the BsI also operates the Country Verifying Certificate<br />

Authority (CVCA). this authority generates the German root<br />

certificates on a regular basis; the private keys of these certificates<br />

are used to sign the document verifier certificate of<br />

the document verifier instances (DV instances).<br />

the DV instances are responsible for issuing the certificates<br />

authorizing the reading of electronic identity documents,<br />

and also define the individual read rights, i.e. what information<br />

can be read from the identity documents. this authorization<br />

is verified by the rF chip of the electronic identity<br />

document on reading during terminal Authentication.<br />

CVCA Public Key Infrastructure<br />

for citizen applications of the new identity card<br />

CVCA<br />

“ePass”<br />

CVCA<br />

DV(s)<br />

CVCA<br />

“ePass”<br />

“ePass”<br />

“ePass”<br />

CVCA<br />

Inspection<br />

CVCA<br />

“ePass”<br />

“ePass”<br />

authorities<br />

BSI<br />

VfB<br />

CVCA - Country Verifying Certificate Authority<br />

DV - Document Verifier<br />

VfB - Issuing Unit for Terminal certificates<br />

CVCA<br />

CVCA<br />

BerCa(s) “ePass”<br />

“ePass”<br />

CVCA<br />

Service<br />

CVCA<br />

“ePass”<br />

“ePass”<br />

providers<br />

CVCA<br />

“eID”<br />

DV<br />

“eID”<br />

Identity CVCA<br />

CVCA<br />

“ePass” card “ePass”<br />

authority<br />

CVCA<br />

“eSign”<br />

DV<br />

“QES”<br />

Verified CVCA<br />

CVCA<br />

signature “ePass”<br />

“ePass”<br />

terminal<br />

BerCA - Certification Authority for eID service providers<br />

QES - Qualified Electronic Signature<br />

CVCA Public Key Infrastructure<br />

in international context<br />

Country A Country B<br />

InFrAstruCturEs<br />

Authorization certificates are issued solely to control<br />

authorities (e.g. Federal Police) and reg<strong>ist</strong>ry offices (to enable<br />

citizens to check the correctness of data) . these certificates<br />

are also required to read fingerprints.<br />

the diagram “CVCA Public Key Infrastructure for citizen<br />

applications of the new identity card” illustrates the<br />

spectrum of variants of national authorization certificates<br />

for the new identity card. In addition to applications for<br />

sovereign purposes, and for electronic identification, the<br />

CVCA also supports the qualified electronic signature.<br />

the new identity card also requires that authorization<br />

certificates be issued for the control authorities of other<br />

nations that are empowered to access the sovereign functions<br />

of the new identity card. this authorization is issued<br />

separately for each nation.<br />

16 17<br />

Terminal<br />

Terminal<br />

Terminal<br />

CVCA CVCA<br />

DV DV DV DV<br />

Terminal<br />

Terminal<br />

Terminal<br />

Terminal<br />

Terminal<br />

Terminal<br />

Terminal<br />

Terminal<br />

Terminal


sECurIty FEAturEs<br />

to sum up, the array of cryptographic protocols described<br />

above offer protection against a range of attacks:<br />

PACE has the advantage that the length of the password<br />

has no effect on the security level of encryption.<br />

this means that even when the CAn or PIn are used,<br />

which are short compared to the MrZ, the data on<br />

the rF chip of the electronic identity card are strongly<br />

protected during transmission.<br />

PACE protects cards against being accessed “in<br />

passing” and creates an encrypted, integrity-secure<br />

channel between the card and the reader.<br />

PACE also enables entry/verification of a PIn, thus<br />

tying authentication to the person and providing<br />

protection against unauthorized use of the new<br />

identity card.<br />

terminal Authentication ensures that the reader/<br />

service provider can perform only authorized access<br />

operations. the read rights for the various data fields<br />

are granted separately.<br />

Chip Authentication creates a secure end-to-end<br />

channel between the chip and the service provider.<br />

together with Passive Authentication, Chip Authentication<br />

also verifies the authenticity of the chip.<br />

the integrity and authenticity of the read data are<br />

implicitly ensured through authentication of the<br />

chip.<br />

5. The eID server – interface for<br />

web applications<br />

eID sErVEr<br />

to simplify the use of the electronic identification function<br />

in web applications, an eID server is required. the eID<br />

server provides a simple interface for web applications,<br />

encapsulating the complexity of the electronic identification<br />

function. the guideline tr-03130 specifies the interface used<br />

by web applications and the corresponding data formats for<br />

exchanging information.<br />

the eID server as a hardware and software component<br />

establishes communication with AusweisApp and handles<br />

the communication for requesting terminal authorization<br />

certificates (DVCA certificates), revocation l<strong>ist</strong>s and CsCA<br />

certificates.<br />

the eID server is realized as a logically independent server, so<br />

that it can be used by multiple web applications (principals);<br />

it can also e.g. be operated remotely by a third party. to preserve<br />

the confidentiality and integrity of the processed data,<br />

the data must be encrypted and signed for transfer between<br />

eID server<br />

The steps of the electronic identification process<br />

➀ Citizen selects authentication using<br />

electronic ID on service provider’s<br />

website.<br />

➁ The webserver of the service provider<br />

transmits the parameters necessary for<br />

establishing the connection.<br />

➂ The browser starts the local AusweisApp<br />

application.<br />

➃ AusweisApp establishes a secure channel<br />

to the eID server of the service provider<br />

and authentication commences.<br />

18 19<br />

Citizen<br />

Browser<br />

➂<br />

AusweisApp<br />

➀<br />

➁<br />

➃<br />

CA - Certification Authority<br />

PKD - Public Key Directory<br />

Service provider<br />

Webserver<br />

eID server<br />

CA, PKD,<br />

revocation<br />

l<strong>ist</strong>s


EVoCAtIon MAnAGEMEnt<br />

the eID server and application server when transmitted via a<br />

public network.<br />

6. Revocation management in the new<br />

German identity card<br />

to prevent abuse of stolen or lost identity cards, the card<br />

holder must be able to block or cancel them via revocation<br />

management [Bender 2010].<br />

Currently, chip cards, e.g. cards for the qualified electronic<br />

signature, are cancelled by means of a chip-specific public<br />

key that can be compared with a revocation l<strong>ist</strong> – in other<br />

words, a global, chip-specific feature. however, a chipspecific<br />

feature is always person-related, as it uniquely<br />

identifies the chip and consequently the card holder.<br />

such a mechanism would thus undermine the data<br />

protection-friendly design of the eID function, in which only<br />

those data from the chip are transmitted that are necessary<br />

for the service. For example, an online service that only<br />

requires proof of age for age-restricted services must not be<br />

able to use a unique revocation attribute to cross-reference<br />

these data with a service that receives name, address and<br />

similar data from the identify document (this is particularly<br />

important for the pseudonym).<br />

one solution to this conflict is to use service-specific revocation<br />

l<strong>ist</strong>s, i.e. every identity card transmits a service- and<br />

card-specific revocation attribute to the service provider<br />

during the electronic identification process, which the provider<br />

then checks against his individual, i.e. service-specific<br />

revocation l<strong>ist</strong>.<br />

For each service that uses the eID function of the new identity<br />

card, a service-specific revocation l<strong>ist</strong> is generated from a<br />

global revocation l<strong>ist</strong>. A service- and card-specific attribute<br />

sent to the service provider from the chip of the identity card<br />

during the eID function can then be compared with a specific<br />

revocation l<strong>ist</strong> in order to identify cancelled IDs.<br />

the use of service- and card-specific revocation attributes<br />

ensures that service providers cannot exploit these to<br />

recognize identity documents across services. this applies<br />

analogously for the revocation service: this central authority<br />

is unable to derive the service- and card-specific revocation<br />

attributes from the revocation key without the ass<strong>ist</strong>ance of<br />

the service providers and the authorization CAs – it is not possible<br />

to trace identity cards via the revocation mechanism.<br />

the use of revocation passwords and checksums also promotes<br />

data protection.<br />

Revocation management<br />

Overview<br />

Lost and stolen l<strong>ist</strong><br />

ID card authority<br />

Revocation<br />

password for entry<br />

in reg<strong>ist</strong>er of IDs Hotline<br />

Berechtigungs-CA<br />

Berechtigungs-CA<br />

Authorization CA<br />

Dienstanbieter<br />

Dienstanbieter<br />

Service provider<br />

rEVoCAtIon MAnAGEMEnt<br />

20 21<br />

Police<br />

Loss reported<br />

Revocation<br />

initiated<br />

Loss reported<br />

Revocation<br />

initiated<br />

Citizen<br />

Revocation initiated<br />

with revocation password<br />

Revocation password<br />

in PIN letter<br />

ID manufacturer<br />

Revocation initiated<br />

with revocation checksum<br />

General revocation l<strong>ist</strong><br />

Service provicer-specific revocation l<strong>ist</strong><br />

eID revocation service


EVoCAtIon MAnAGEMEnt<br />

A revocation key is required for generating service-specific<br />

revocation l<strong>ist</strong>s. to ensure that the process complies with the<br />

security requirements described above, this key has a length<br />

of 256 bits – something the identity card holder will certainly<br />

be unable to memorize.<br />

Cancellation of lost identity cards must be possible at any<br />

time: seven days a week, 24 hours a day, and especially while<br />

travelling as well. one solution would be to store the personal<br />

data of the card holder required for identification in the<br />

revocation service, together with the revocation key, which<br />

would in practice be equivalent to a nation-wide reg<strong>ist</strong>ry of<br />

persons.<br />

the methods used in the identity card take a different<br />

approach: only the hash value (revocation checksum)<br />

corresponding to the last and first names, date of birth and<br />

cancellation password are stored with the revocation key.<br />

this implementation permits effective cancellation of<br />

identity cards without requiring a central reg<strong>ist</strong>ry holding<br />

personal data.<br />

7. References<br />

rEFErEnCEs<br />

[PAuswG 2010] German ID Card Act (Gesetz über Personalausweise<br />

und den elektronischen Identitätsnachweis – Personalausweisgesetz<br />

– PAuswG), 17 August 2010, German Federal<br />

Law Gazette (Bundesanzeiger) I, p. 1346<br />

[PAuswV 2010] German ID Card Regulation (Verordnung über<br />

Personalausweise und den elektronischen Identitätsnachweis<br />

– PAuswV), 2010, German Federal Law Gazette (Bundesanzeiger)<br />

I<br />

[Bender 2008] Jens Bender, Dennis Kügler, Marian Margraf,<br />

Ingo naumann, Sicherheitsmechanismen für kontaktlose<br />

Chips im deutschen elektronischen Personalausweis, DuD •<br />

Datenschutz und Datensicherheit 3 | 2008, p. 173-177<br />

[Bender 2010] Jens Bender, Dennis Kügler, Marian Margraf,<br />

Ingo naumann, Das Sperrmanagement im neuen deutschen<br />

Personalausweis, DuD • Datenschutz und Datensicherheit 5 |<br />

2010, p. 295-298<br />

[tr-03110] BsI technical Guideline, Advanced Security Mechanisms<br />

for Machine Readable Travel Documents (BsI tr-03110)<br />

[tr-03112] BsI technical Guideline, eCard-API-Framework (BsI<br />

tr-03112)<br />

[tr-03128] BsI technical Guideline, EAC-PKI‘n für den elektronischen<br />

Personalausweis, Rahmenkonzept für den Aufbau und<br />

den Betrieb von Document Verifiern (BsI tr-03128)<br />

[tr-03130] BsI technical Guideline, eID-Server (BsI tr-03130)<br />

[tr-03131] BsI technical Guideline, EAC-Box Architecture and<br />

Interfaces (BsI tr-03131)<br />

22 23


Published by<br />

Federal office for<br />

Information security (BsI)<br />

Godesberger Allee 185 - 189<br />

53175 Bonn, Germany<br />

Version<br />

september 2010<br />

Editorial<br />

teletrust Deutschland e.V.,<br />

Berlin, Germany<br />

Design / Production<br />

Kesberg Consulting,<br />

Bonn, Germany<br />

Printing<br />

Buersche Druckerei neufang KG,<br />

Gelsenkirchen, Germany<br />

Photos<br />

German Federal Min<strong>ist</strong>ry of the Interior<br />

(cover pictures), German Federal office<br />

for Information security (graphics)

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!