ISO/IEC 7816-15:2016/DAM 2:2025(en)
ISO/IEC JTC 1/SC 17
Secretariat: BSI
Date: 2025-11-05
Identification cards — Integrated circuit cards — Part 15: Cryptographic information application - Amendment 2 : Quantum safe cryptography
Cartes d'identification — Cartes à circuit intégré à contacts — Partie 15: Application des informations cryptographiques - Amendement 2 : Mise à jour pour le support de la cryptographie post quantique
© ISO/IEC 2025
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
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. In the field of information technology, ISO and IEC have established a joint technical committee, ISO/IEC JTC 1.
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).
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).
Any trade name used in this document is information given for the convenience of users and does not constitute an endorsement.
For an explanation on 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 the following URL: www.iso.org/iso/foreword.html.
This document was prepared by ISO/IEC JTC 1, Information technology, SC 17, Cards and personal identification.
Identification cards — Integrated circuit cards — Part 15: Cryptographic information application - Amendment 2: Quantum safe cryptography
Subclause 8.2.9, page 21
Add the following text at the end of the 2nd paragraph before Table 2 and after the ASN.1 definitions:
When used with quantum safe cryptography keys involved in key encapsulation algorithm, the usage component shall be set to encipher for KEM.Encapsulate() method, and to decipher for KEM.Decapsulate() method.
Subclause 8.10, page 42
Add the following at the end of the paragraph describing the 5th bullet point:
For quantum safe cryptography, the values of the supportedOperations component shall encode BIT STRING {encipher} or BIT STRING {decipher} to denote respectively KEM.Encapsulate() method or KEM.Decapsulate() method (see ISO/IEC 7816-8:2021/Amd.1:2023, 3.21); otherwise, quantum safe operations may be identified by AlgorithmInfo.algRef denoting card capabilities, and be triggered at card interface, using APDU e.g. with MSE nesting quantum safe crypography algorithm reference in a CRT
|
Subclause 8.10, page 41
Change the definition of ProfileIndication component as follows:
ProfileIndication ::= CHOICE {
profileOID OBJECT IDENTIFIER,
profileName UTF8String,
profilePath Path,
... -- For future extensions
}
Subclause 8.10, page 42
Add the following at the end of the paragraph describing the bullet point CIAInfo.profileIndication:
The encoding of profilePath CHOICE allows for referencing the quantum safe cryptography templates for discoverability DO‘7F78’ and DO‘7F79’ from within ISO/IEC 7816-4 structures e.g. an application DF, an EF or a constructed DO; these templates describe respectively the way to combine single keys (e.g. for QSC hybrid signature, for compound key signature), and how Key Encapsulation Mechanism variants can be triggered by the IFD (e.g. KEM with or without authentication). Use of profilePath to reference a proprietary profile is out of scope.
Subclause 8.4.1, page.27
Add at the end of the text from ISO/IEC 7816-15:2016/Amd.1:2018 under the two ASN.1 definitions the following:
The othergenericPrivateKey CHOICE may reference quantum safe cryptography key templates DO‘7F75’ (private key) or DO’7F76’ (private key template nesting common parameters) by encoding ReferencedValue as Path.
NOTE As per ISO/IEC 7816-8:2021/Amd.1:2023, a quantum safe cryptography common parameters template DO’7F77’ can be referenced from within either a template DO’7F75’ or DO’7F76’.
Subclause 8.5.1, page 29
Add at the end of the text from ISO/IEC 7816-15:2016/Amd.1:2018 under the two ASN.1 definitions the following:
The othergenericPublicKey CHOICE may reference quantum safe cryptography key templates DO‘7F75’ (public key) or DO’7F76’ (public key template nesting common parameters) by encoding ReferencedValue as Path.
NOTE As per ISO/IEC 7816-8:2021/Amd.1:2023, a quantum safe cryptography common parameters template DO’7F77’ can be referenced from within either a template DO’7F75’ or DO’7F76’
Clause Annex A.10, page 57
Change the definition of ProfileIndication component as follows:
ProfileIndication ::= CHOICE {
profileOID OBJECT IDENTIFIER,
profileName UTF8String,
profilePath Path,
... -- For future extensions
}
Subclause 8.8.1, page 34
Add the following after the last paragraph:
If nested in EF.DCOD, a quantum safe cryptography parameterized configuration template that is a proprietary one shall be encoded as an opaqueDO entry of which the interpretation is left to applications accessing it; if it is a quantum safe cryptography parameterized configuration template DO’7F78’ or DO’7F79’, it shall be encoded as an ISO/IEC 7816-4 compliant entry iso7816DO where the referenced cryptographic data object is the template to be retrieved, e.g. by a ’GET DATA’ command, and where the direct choice of ObjectValue shall be used, and its CIO-OPAQUE.&Type value shall be the template’s tag (i.e. DO’7F78’ or DO’7F79’)
