ISO/IEC 23220-1:2023
(Main)Cards and security devices for personal identification — Building blocks for identity management via mobile devices — Part 1: Generic system architectures of mobile eID systems
Cards and security devices for personal identification — Building blocks for identity management via mobile devices — Part 1: Generic system architectures of mobile eID systems
This document specifies generic system architectures and generic life-cycle phases of mobile eID systems in terms of building blocks for mobile eID system infrastructures. It standardizes interfaces and services for mdoc apps and mobile verification applications. It is applicable to entities involved in specifying, architecting, designing, testing, maintaining, administering and operating a mobile eID system in parts or entirely.
Cartes et dispositifs de sécurité pour l’identification des personnes — Blocs fonctionnels pour la gestion des identités via les dispositifs mobiles — Partie 1: Architectures génériques des systèmes d'identification électronique mobiles
General Information
Standards Content (Sample)
INTERNATIONAL ISO/IEC
STANDARD 23220-1
First edition
2023-02
Cards and security devices for
personal identification — Building
blocks for identity management via
mobile devices —
Part 1:
Generic system architectures of
mobile eID systems
Cartes et dispositifs de sécurité pour l’identification des personnes —
Blocs fonctionnels pour la gestion des identités via les dispositifs
mobiles —
Partie 1: Architectures génériques des systèmes d'identification
électronique mobiles
Reference number
© ISO/IEC 2023
© ISO/IEC 2023
All rights reserved. Unless otherwise specified, or required in the context of its implementation, no part of this publication may
be reproduced or utilized otherwise in any form or by any means, electronic or mechanical, including photocopying, or posting on
the internet or an intranet, without prior written permission. Permission can be requested from either ISO at the address below
or ISO’s member body in the country of the requester.
ISO copyright office
CP 401 • Ch. de Blandonnet 8
CH-1214 Vernier, Geneva
Phone: +41 22 749 01 11
Email: copyright@iso.org
Website: www.iso.org
Published in Switzerland
ii
© ISO/IEC 2023 – All rights reserved
Contents Page
Foreword .iv
Introduction .v
1 Scope . 1
2 Normative references . 1
3 Terms and definitions . 1
4 Abbreviated terms . 6
5 Design and privacy principles of mobile document systems . 7
5.1 Design principles . 7
5.2 Privacy and security principles . 8
5.2.1 General . 8
5.2.2 Data minimization . 8
5.2.3 Consent and choice: . 8
5.2.4 Accuracy and quality . 8
5.2.5 Information security . . 9
6 General life-cycle phases and components of mobile document systems .9
6.1 Life-cycle phases of mobile document systems . 9
6.2 Components of a mobile document system . 10
6.2.1 Operational modes of components . . 10
6.2.2 Components of mobile document systems . 11
7 Generic system architectures of mobile document systems in installation phase .13
8 Generic system architectures of mobile document systems in issuing phase .15
8.1 Source of user attributes .15
8.2 Generic sub-phases of issuing phase. 15
8.3 System architectures in sub-phases user identification and mID-discovery . 16
8.4 Architectures in sub-phase issuance . 18
8.5 Monitoring service in issuing phase . 20
9 On-site identification system architecture in operational phase .21
9.1 General sub-phases of on-site identification system architecture . 21
9.2 On-site identification system architecture with local attribute storage . 21
9.3 On-site identification system architecture with remote attribute storage .22
10 Remote identification system architecture in operational phase .23
10.1 General .23
10.2 Remote identification system architecture with local attribute storage .23
10.3 Remote identification system architecture with remote attribute storage .25
Annex A (informative) Examples of deployment options for issuers in issuing phase .28
Annex B (informative) Examples of deployment options in installation phase .35
Annex C (informative) Examples of holder enrolment .39
Annex D (informative) Examples of additional physical factor(s) of authentication .43
Bibliography .47
iii
© ISO/IEC 2023 – All rights reserved
Foreword
ISO (the International Organization for Standardization) and IEC (the International Electrotechnical
Commission) form the specialized system for worldwide standardization. National bodies that are
members of ISO or IEC participate in the development of International Standards through technical
committees established by the respective organization to deal with particular fields of technical
activity. ISO and IEC technical committees collaborate in fields of mutual interest. Other international
organizations, governmental and non-governmental, in liaison with ISO and IEC, also take part in the
work.
The procedures used to develop this document and those intended for its further maintenance
are described in the ISO/IEC Directives, Part 1. In particular, the different approval criteria
needed for the different types of document should be noted. This document was drafted in
accordance with the editorial rules of the ISO/IEC Directives, Part 2 (see www.iso.org/directives or
www.iec.ch/members_experts/refdocs).
Attention is drawn to the possibility that some of the elements of this document may be the subject
of patent rights. ISO and IEC shall not be held responsible for identifying any or all such patent
rights. Details of any patent rights identified during the development of the document will be in the
Introduction and/or on the ISO list of patent declarations received (see www.iso.org/patents) or the IEC
list of patent declarations received (see https://patents.iec.ch).
Any trade name used in this document is information given for the convenience of users and does not
constitute an endorsement.
For an explanation of the voluntary nature of standards, the meaning of ISO specific terms and
expressions related to conformity assessment, as well as information about ISO's adherence to
the World Trade Organization (WTO) principles in the Technical Barriers to Trade (TBT) see
www.iso.org/iso/foreword.html. In the IEC, see www.iec.ch/understanding-standards.
This document was prepared by Joint Technical Committee ISO/IEC JTC 1, Information technology,
Subcommittee SC 17, Cards and security devices for personal identification.
A list of all parts in the ISO/IEC 23220 series can be found on the ISO and IEC websites.
Any feedback or questions on this document should be directed to the user’s national standards
body. A complete listing of these bodies can be found at www.iso.org/members.html and
www.iec.ch/national-committees.
iv
© ISO/IEC 2023 – All rights reserved
Introduction
Electronic ID-Applications (eID-Apps) are commonly used in badges and ID-Cards with integrated
circuits and allow users to complete electronic identification, authentication or optionally to create
digital signatures. Many different application areas have an essential need for these mechanisms
and use different means to provide these features (e.g. health system with health assurance cards or
health professional cards, financial sector with payment cards, government ID with national ID cards,
electronic passports or driver's licenses, educational systems with student cards or library cards, in
the company sector with employee cards and in the personal sector with member cards).
Mobile devices (e.g. mobile phones or smart phones, wearable devices) are a central part of the daily life
for many individuals. They are not only used for communication, but also for emailing, access to social
media, gaming, shopping, banking, and storing private content such as photos, videos and music. They
are used today as a personal device for business and private applications. With the ubiquity of mobile
devices in day-to-day activities there is a strong demand from users to have eID-Apps or services with
identification/authentication mechanisms on their mobile equipment, i.e. an mdoc app.
An mdoc app can be deployed to provide a number of different digital ID-documents. Additionally, it can
reside among other eID-Apps on a mobile device. Moreover, users can possess more than one mobile
device holding an mdoc app, which leads to enhanced mechanisms for the management of credentials
and attributes.
The technical preconditions for the deployment of mdoc apps exist and they are partly standardized
to support security and privacy on a mobile device. Examples for containers of eID-App solutions are
the software-based Trusted Execution Environment (TEE), hardware-based secure elements such as
universal integrated circuit card (UICC), embedded or integrated UICC (eUICC or iUICC), embedded
secure elements, secure memory cards with cryptographic module [17] or other dedicated internal
security devices residing on the mobile device, as well as solutions with server-based security means.
As mdoc apps can be located on different forms of mobile devices featuring different security means,
they must be as generic as possible to be adoptable to different variants of trusted eID-Management.
This diversity leads also to different levels of security, trust and assurance. Trusted eID-Management
thereby implies the (remote) administration and use of one or several security elements (e.g. in form of
an intelligent network), credentials and user attributes with different levels of security suitable to their
capability and power.
Access to the mdoc app by the external world must be performed by the available transmission channels.
Typical local communication channels are Bluetooth Low Energy (BLE), Near Field Communication
(NFC), Wi-Fi aware, whereas remote communication is typically an internet connection over mobile
networks and Wi-Fi networks. The way of identification and choice of the transmission interface and
protocols is an essential part for a trusted eID-Management.
Those mdoc apps are used in different areas of daily life and are the focus of different standardization
activities. This document aims at delivering mechanisms and protocols usable by other standards to
provide interoperability and interchangeability. With these basics in mind, future mdoc apps can be
derived and may extend the ISO/IEC 23220 series.
The ISO/IEC 23220 series builds upon existing standards comprising four main features:
a) secure channel establishment;
b) API call serialization method;
c) data element naming convention;
d) payload transport over communication channel protocols, which are constitutive of the
interoperability pillars.
v
© ISO/IEC 2023 – All rights reserved
In addition, it adds means to establish Trust on First Use (TOFU).
NOTE The ISO/IEC 23220 series inherits and enhances the functionality that was adopted by mobile driving
licence applications whereby ensuring backward compatibility with ISO/IEC 18013-5.
Other parts in the ISO/IEC 23220 series specify the following:
1)
— generic data formats (see ISO/IEC TS 23220-2);
2)
— protocols and services for issuing phase (see
...
FINAL
INTERNATIONAL ISO/IEC
DRAFT
STANDARD FDIS
23220-1
ISO/IEC JTC 1/SC 17
Cards and security devices for
Secretariat: BSI
personal identification — Building
Voting begins on:
2022-11-02 blocks for identity management via
mobile devices —
Voting terminates on:
2022-12-28
Part 1:
Generic system architectures of
mobile eID systems
RECIPIENTS OF THIS DRAFT ARE INVITED TO
SUBMIT, WITH THEIR COMMENTS, NOTIFICATION
OF ANY RELEVANT PATENT RIGHTS OF WHICH
THEY ARE AWARE AND TO PROVIDE SUPPOR TING
DOCUMENTATION.
IN ADDITION TO THEIR EVALUATION AS
Reference number
BEING ACCEPTABLE FOR INDUSTRIAL, TECHNO-
ISO/IEC FDIS 23220-1:2022(E)
LOGICAL, COMMERCIAL AND USER PURPOSES,
DRAFT INTERNATIONAL STANDARDS MAY ON
OCCASION HAVE TO BE CONSIDERED IN THE
LIGHT OF THEIR POTENTIAL TO BECOME STAN-
DARDS TO WHICH REFERENCE MAY BE MADE IN
NATIONAL REGULATIONS. © ISO/IEC 2022
ISO/IEC FDIS 23220-1:2022(E)
FINAL
INTERNATIONAL ISO/IEC
DRAFT
STANDARD FDIS
23220-1
ISO/IEC JTC 1/SC 17
Cards and security devices for
Secretariat: BSI
personal identification — Building
Voting begins on:
blocks for identity management via
mobile devices —
Voting terminates on:
Part 1:
Generic system architectures of
mobile eID systems
© ISO/IEC 2022
All rights reserved. Unless otherwise specified, or required in the context of its implementation, no part of this publication may
be reproduced or utilized otherwise in any form or by any means, electronic or mechanical, including photocopying, or posting on
the internet or an intranet, without prior written permission. Permission can be requested from either ISO at the address below
or ISO’s member body in the country of the requester.
RECIPIENTS OF THIS DRAFT ARE INVITED TO
ISO copyright office
SUBMIT, WITH THEIR COMMENTS, NOTIFICATION
OF ANY RELEVANT PATENT RIGHTS OF WHICH
CP 401 • Ch. de Blandonnet 8
THEY ARE AWARE AND TO PROVIDE SUPPOR TING
CH-1214 Vernier, Geneva
DOCUMENTATION.
Phone: +41 22 749 01 11
IN ADDITION TO THEIR EVALUATION AS
Reference number
Email: copyright@iso.org
BEING ACCEPTABLE FOR INDUSTRIAL, TECHNO
ISO/IEC FDIS 232201:2022(E)
Website: www.iso.org
LOGICAL, COMMERCIAL AND USER PURPOSES,
DRAFT INTERNATIONAL STANDARDS MAY ON
Published in Switzerland
OCCASION HAVE TO BE CONSIDERED IN THE
LIGHT OF THEIR POTENTIAL TO BECOME STAN
DARDS TO WHICH REFERENCE MAY BE MADE IN
ii
© ISO/IEC 2022 – All rights reserved
NATIONAL REGULATIONS. © ISO/IEC 2022
ISO/IEC FDIS 23220-1:2022(E)
Contents Page
Foreword .iv
Introduction .v
1 Scope . 1
2 Normative references . 1
3 Terms and definitions . 1
4 Abbreviated terms . 6
5 Design and privacy principles of mobile document systems . 7
5.1 Design principles . 7
5.2 Privacy and security principles . 8
5.2.1 General . 8
5.2.2 Data minimization . 8
5.2.3 Consent and choice: . 8
5.2.4 Accuracy and quality . 8
5.2.5 Information security . . 9
6 General life-cycle phases and components of mobile document systems .9
6.1 Life-cycle phases of mobile document systems . 9
6.2 Components of a mobile document system . 10
6.2.1 Operational modes of components . . 10
6.2.2 Components of mobile document systems . 11
7 Generic system architectures of mobile document systems in installation phase .13
8 Generic system architectures of mobile document systems in issuing phase .15
8.1 Source of user attributes .15
8.2 Generic subphases of issuing phase. 15
8.3 System architectures in sub-phases user identification and mID-discovery . 16
8.4 Architectures in subphase issuance . 18
8.5 Monitoring service in issuing phase . 20
9 On-site identification system architecture in operational phase .21
9.1 General sub-phases of on-site identification system architecture . 21
9.2 On-site identification system architecture with local attribute storage . 21
9.3 On-site identification system architecture with remote attribute storage .22
10 Remote identification system architecture in operational phase .23
10.1 General .23
10.2 Remote identification system architecture with local attribute storage .23
10.3 Remote identification system architecture with remote attribute storage .25
Annex A (informative) Examples of deployment options for issuers in issuing phase .28
Annex B (informative) Examples of deployment options in installation phase .35
Annex C (informative) Examples of holder enrolment .39
Annex D (informative) Examples of additional physical factor(s) of authentication .43
Bibliography .47
iii
© ISO/IEC 2022 – All rights reserved
ISO/IEC FDIS 23220-1:2022(E)
Foreword
ISO (the International Organization for Standardization) and IEC (the International Electrotechnical
Commission) form the specialized system for worldwide standardization. National bodies that are
members of ISO or IEC participate in the development of International Standards through technical
committees established by the respective organization to deal with particular fields of technical
activity. ISO and IEC technical committees collaborate in fields of mutual interest. Other international
organizations, governmental and nongovernmental, in liaison with ISO and IEC, also take part in the
work.
The procedures used to develop this document and those intended for its further maintenance
are described in the ISO/IEC Directives, Part 1. In particular, the different approval criteria
needed for the different types of document should be noted. This document was drafted in
accordance with the editorial rules of the ISO/IEC Directives, Part 2 (see www.iso.org/directives or
www.iec.ch/members_experts/refdocs).
Attention is drawn to the possibility that some of the elements of this document may be the subject
of patent rights. ISO and IEC shall not be held responsible for identifying any or all such patent
rights. Details of any patent rights identified during the development of the document will be in the
Introduction and/or on the ISO list of patent declarations received (see www.iso.org/patents) or the IEC
list of patent declarations received (see https://patents.iec.ch).
Any trade name used in this document is information given for the convenience of users and does not
constitute an endorsement.
For an explanation of the voluntary nature of standards, the meaning of ISO specific terms and
expressions related to conformity assessment, as well as information about ISO's adherence to
the World Trade Organization (WTO) principles in the Technical Barriers to Trade (TBT) see
www.iso.org/iso/foreword.html. In the IEC, see www.iec.ch/understandingstandards.
This document was prepared by Joint Technical Committee ISO/IEC JTC 1, Information technology,
Subcommittee SC 17, Cards and security devices for personal identification.
A list of all parts in the ISO/IEC 23220 series can be found on the ISO and IEC websites.
Any feedback or questions on this document should be directed to the user’s national standards
body. A complete listing of these bodies can be found at www.iso.org/members.html and
www.iec.ch/nationalcommittees.
iv
© ISO/IEC 2022 – All rights reserved
ISO/IEC FDIS 23220-1:2022(E)
Introduction
Electronic ID-Applications (eID-Apps) are commonly used in badges and ID-Cards with integrated
circuits and allow users to complete electronic identification, authentication or optionally to create
digital signatures. Many different application areas have an essential need for these mechanisms
and use different means to provide these features (e.g. health system with health assurance cards or
health professional cards, financial sector with payment cards, government ID with national ID cards,
electronic passports or driver's licenses, educational systems with student cards or library cards, in
the company sector with employee cards and in the personal sector with member cards).
Mobile devices (e.g. mobile phones or smart phones, wearable devices) are a central part of the daily life
for many individuals. They are not only used for communication, but also for emailing, access to social
media, gaming, shopping, banking, and storing private content such as photos, videos and music. They
are used today as a personal device for business and private applications. With the ubiquity of mobile
devices in day-to-day activities there is a strong demand from users to have eID-Apps or services with
identification/authentication mechanisms on their mobile equipment, i.e. an mdoc app.
An mdoc app can be deployed to provide a number of different digital ID-documents. Additionally, it can
reside among other eIDApps on a mobile device. Moreover, users can possess more than one mobile
device holding an mdoc app, which leads to enhanced mechanisms for the management of credentials
and attributes.
The technical preconditions for the deployment of mdoc apps exist and they are partly standardized
to support security and privacy on a mobile device. Examples for containers of eID-App solutions are
the software-based Trusted Execution Environment (TEE), hardware-based secure elements such as
universal integrated circuit card (UICC), embedded or integrated UICC (eUICC or iUICC), embedded
secure elements, secure memory cards with cryptographic module [17] or other dedicated internal
security devices residing on the mobile device, as well as solutions with server-based security means.
As mdoc apps can be located on different forms of mobile devices featuring different security means,
they must be as generic as possible to be adoptable to different variants of trusted eID-Management.
This diversity leads also to different levels of security, trust and assurance. Trusted eID-Management
thereby implies the (remote) administration and use of one or several security elements (e.g. in form of
an intelligent network), credentials and user attributes with different levels of security suitable to their
capability and power.
Access to the mdoc app by the external world must be performed by the available transmission channels.
Typical local communication channels are Bluetooth Low Energy (BLE), Near Field Communication
(NFC), Wi-Fi aware, whereas remote communication is typically an internet connection over mobile
networks and Wi-Fi networks. The way of identification and choice of the transmission interface and
protocols is an essential part for a t
...
Deleted:
Deleted: 2022-06-30¶
ISO/IEC TC JTC1/SC17 N
Deleted: 2021-09-21
Date 2022-10
Deleted: DIS
ISO/IEC FDIS 23220-1:2022(E)
Deleted: 2021
ISO/IEC TC JTC1/SC 17/WG 4
Secretariat: BSI
Cards and security devices for personal identification — Building blocks for
identity management via mobile devices — Part 1: Generic system architectures
of mobile eID systems
Cartes et dispositifs de sécurité pour l’identification personnelle — Briques techniques
pour l’identification par dispositifs mobiles
ISO/IEC FDIS 23220-1:2022(E)
Deleted:
Deleted: DIS
Deleted: 2021
Deleted: 2016
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or
utilized otherwise in any form or by any means, electronic or mechanical, including photocopying,
or posting on the internet or an intranet, without prior written permission. Permission can be
requested from either ISO at the address below or ISO’s member body in the country of the
requester.
ISO copyright office
Ch. de Blandonnet 8 • CP 401
CH-1214 Vernier, Geneva, Switzerland
Tel. + 41 22 749 01 11
Fax + 41 22 749 09 47
copyright@iso.org
www.iso.org
Deleted: ii © ISO/IEC 2021 – All rights reserved¶
ii © ISO/IEC 2022 – All rights reserved
ISO/IEC FDIS 23220-1:2022(E) Deleted: DIS
Deleted: 2021
Contents
Deleted: 5
Foreword . v
Introduction . vi Deleted: 6
1 Scope . 7
2 Normative references . 7
3 Terms and definitions . 7
4 Symbols and abbreviations . 13
5 Design and privacy principles of mobile eID-Systems . 13
5.1 Design principles . 13
5.2 Privacy and security principles . 14
6 General life-cycle phases and components of mobile eID-Systems . 15
6.1 Life-cycle phases of mobile eID-Systems . 15
6.2 Components of a mobile eID-System . 16
7 Generic system architectures of mobile eID-Systems in installation phase . 18
8 Generic system architectures of mobile eID-Systems in issuing phase . 20
8.1 Source of user attributes . 20
8.2 Generic sub-phases of issuing phase . 21
8.3 System architectures in sub-phases user identification and mID-discovery . 22
8.4 Architectures in sub-phase issuance . 24
8.5 Monitoring service in issuing phase . 25
9 On-site identification system architecture in operational phase . 26
9.1 General sub-phases of on-site identification system architecture . 26
9.2 On-site identification system architecture with local attribute storage . 26
9.3 On-site identification system architecture with remote attribute storage . 27
10 Remote identification system architecture in operational phase . 28
10.1 Remote identification system architecture with local attribute storage . 28
10.2 Remote identification system architecture with remote attribute storage . 29
Annex A (informative) Examples of deployment options for Issuers in issuing phase . 32
A.1 General . 32
A.2 Deployment example for issuing with local user attribute storage . 32
A.3 Deployment example for issuing with remote attribute storage . 33
A.4 Deployment example for issuing with ID-Provisioning Entity . 33
A.5 Deployment example for issuing with user identification service operated by issuer. 34
A.6 Deployment example for issuing with Open Firmware Loader . 35
A.7 Deployment example for installation phase with JavaCard Applets onto eSE . 36
A.8 Deployment example for installation phase with JavaCard Applets onto eUICC . 37
Annex B (informative) Identity proofing . 39
Deleted: © ISO/IEC 2021 – All rights reserved iii¶
© ISO/IEC 2022 – All rights reserved iii
ISO/IEC FDIS 23220-1:2022(E)
Deleted:
Deleted: DIS
Deleted: 2021
B.1 Introduction . 39
B.2 Identity derivation based on secure electronic identity documents . 39
B.2.1 General . 39
B.2.2 Authentication of the identity data of the user . 39
B.2.3 Binding between the identity data and the user . 40
B.3 Identity derivation using secure identity documents . 40
B.3.1 General . 40
B.3.2 Optical authentication of secure identity document . 40
B.3.3 Binding between the secure identity documents and the user . 41
B.4 Security prospective: attended vs. unattended identity derivation . 41
B.5 Example of enrolment procedure with additional physical factor of authentication . 41
Annex C (informative) Additional physical factor(s) of authentication . 43
C.1 Introduction . 43
C.2 Electronic MRTD . 43
C.3 Electronic identity card. 43
C.4 Secure identity document with optical authentication features . 45
C.5 Biometric authentication . 45
Bibliography . 47 Deleted: ¶
Deleted: iv © ISO/IEC 2021 – All rights reserved¶
iv © ISO/IEC 2022 – All rights reserved
ISO/IEC FDIS 23220-1:2022(E) Deleted: DIS
Deleted: 2021
Foreword
ISO (the International Organization for Standardization) and IEC (the International Electrotechnical
Commission) form the specialized system for worldwide standardization. National bodies that are
members of ISO or IEC participate in the development of International Standards through technical
committees established by the respective organization to deal with particular fields of technical activity.
ISO and IEC technical committees collaborate in fields of mutual interest. Other international
organizations, governmental and non-governmental, in liaison with ISO and IEC, also take part in the
work.
The procedures used to develop this document and those intended for its further maintenance are
described in the ISO/IEC Directives, Part 1. In particular, the different approval criteria needed for the
different types of document should be noted. This document was drafted in accordance with the
editorial rules of the ISO/IEC Directives, Part 2 (see www.iso.org/directives or
www.iec.ch/members_experts/refdocs).
Attention is drawn to the possibility that some of the elements of this document may be the subject of
patent rights. ISO and IEC shall not be held responsible for identifying any or all such patent rights.
Details of any patent rights identified during the development of the document will be in the
Introduction and/or on the ISO list of patent declarations received (see www.iso.org/patents) or the
IEC list of patent declarations received (see https://patents.iec.ch).
Any trade name used in this document is information given for the convenience of users and does not
constitute an endorsement.
For an explanation of the voluntary nature of standards, the meaning of ISO specific terms and
expressions related to conformity assessment, as well as information about ISO's adherence to the
World Trade Organization (WTO) principles in the Technical Barriers to Trade (TBT) see
www.iso.org/iso/foreword.html. In the IEC, see www.iec.ch/understanding-standards.
This document was prepared by Joint Technical Committee ISO/IEC JTC 1, Information technology,
Subcommittee SC 17, Cards and security devices for personal identification.
A list of all parts in the ISO/IEC 23220 series can be found on the ISO and IEC websites.
Any feedback or questions on this document should be directed to the user’s national standards body. A
complete listing of these bodies can be found at www.iso.org/members.html and www.iec.ch/national-
committees.
Deleted: ¶
Deleted: © ISO/IEC 2021 – All rights reserved v¶
© ISO/IEC 2022 – All rights reserved v
ISO/IEC FDIS 23220-1:2022(E)
Deleted:
Deleted: DIS
Deleted: 2021
Introduction
Electronic ID-Applications (eID-Apps) are commonly used in badges and ID-Cards with integrated Deleted: today
circuits and allow users to complete electronic identification, authentication or optionally to create
digital signatures. Many different application areas have an essential need for these mechanisms and
use different means to provide these features (e.g. health system with health assurance cards or health
Deleted: governmental
professional cards, financial sector with payment cards, government ID with national ID cards,
electronic passports or driver's licenses, educational systems with student cards or library cards, in the
Deleted: -Cards
company sector with employee cards and in the personal sector with member cards).
Deleted: private
Deleted: any kind of
Mobile devices (e.g. mobile phones or smart phones, wearable devices) are a central part of the daily life
for many individuals. They are not only used for communication, but also for emailing, access to social
media, gaming, shopping, banking, and storing private content such as photos, videos and music. They Deleted: of
are used today as a personal device for business and private applications. With the ubiquity of mobile
devices in day-to-day activities there is a strong demand from users to have eID-Apps or services with Deleted:
identification/authentication mechanisms on their mobile equipment, i.e. an mdoc app.
An mdoc app can be deployed to provide a number of different digital ID-documents. Additionally, it can Deleted: may
reside among other eID-Apps on a mobile device. Moreover, users can possess more than one mobile
device holding an mdoc app, which leads to enhanced mechanisms for the management of credentials
and attributes.
The technical preconditions for the deployment of mdoc apps exist and they are partly standardized to
support security and privacy on a mobile device. Examples for containers of eID-App solutions are the
software-based Trusted Execution Environment (TEE), hardware-based secure elements such as
universal integrated circuit card (UICC), embedded or integrated UICC (eUICC or iUICC), embedded
Deleted: (SOURCE: NIST SP 800-157: Guidelines for Derived PIV
secure elements, secure memory cards with cryptographic module [17] or other dedicated internal
Credentials)[
security devices residing on the mobile device, as well as solutions with server-based security means.
As mdoc apps can be located on different forms of mobile devices featuring different security means,
they must be as generic as possible to be adoptable to different variants of trusted eID-Management.
This diversity leads also to different levels of security, trust and assurance. Trusted eID-Management
thereby implies the (remote) administration and use of one or several security elements (e.g. in form of
an intelligent network), credentials and user attributes with different levels of security suitable to their
capability and power.
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.