Identification cards - Integrated circuit cards - Part 15: Cryptographic information application

ISO/IEC 7816-15:2016 specifies an application in a card. This application contains information on cryptographic functionality. This part of ISO/IEC 7816 defines a common syntax and format for the cryptographic information and mechanisms to share this information whenever appropriate. The objectives of this part of ISO/IEC 7816 are to - facilitate interoperability among components running on various platforms (platform neutral), - enable applications in the outside world to take advantage of products and components from multiple manufacturers (vendor neutral), - enable the use of advances in technology without rewriting application-level software (application neutral), and - maintain consistency with existing, related standards while expanding upon them only where necessary and practical. It supports the following capabilities: - storage of multiple instances of cryptographic information in a card; - use of the cryptographic information; - retrieval of the cryptographic information, a key factor for this is the notion of "Directory Files", which provides a layer of indirection between objects on the card and the actual format of these objects; - cross-referencing of the cryptographic information with DOs defined in other parts of ISO/IEC 7816 when appropriate; - different authentication mechanisms; - multiple cryptographic algorithms (the suitability of these is outside the scope of this part of ISO/IEC 7816). ISO/IEC 7816-15.2016 does not cover the internal implementation within the card and/or the outside world. It is not mandatory for implementations complying with this International Standard to support all options described. In case of discrepancies between ASN.1 definitions in the body of the text and the module in Annex A, Annex A takes precedence.

Cartes d'identification — Cartes à circuit intégré à contacts — Partie 15: Application des informations cryptographiques

General Information

Status
Published
Publication Date
08-May-2016
Current Stage
9093 - International Standard confirmed
Start Date
08-Oct-2021
Completion Date
30-Oct-2025

Relations

Effective Date
25-Apr-2020
Effective Date
09-Nov-2013
Effective Date
09-Nov-2013
Effective Date
09-Nov-2013

Overview

ISO/IEC 7816-15:2016 - "Identification cards - Integrated circuit cards - Part 15: Cryptographic information application" defines a standardized, platform-neutral application for storing, organizing and sharing cryptographic information on smart cards (integrated circuit cards). The standard specifies a common syntax and file formats (ASN.1-based) for cryptographic information objects (CIOs), directory files and related mechanisms to enable vendor-neutral, application-neutral and interoperable use of keys, certificates and authentication objects across multiple platforms.

Key objectives:

  • Facilitate interoperability among components on different platforms
  • Enable multi-vendor product integration
  • Allow technological evolution without rewriting application-level software
  • Maintain consistency with related standards while expanding only where needed

Note: ISO/IEC 7816-15:2016 does not mandate internal card implementation details and implementations are not required to support every option. In case of ASN.1 discrepancies, Annex A (ASN.1 module) takes precedence.

Key Topics and Technical Requirements

  • Cryptographic Information Objects (CIOs): Common classes and attributes for private/public keys, secret keys, certificates, authentication objects and opaque data containers.
  • File structure and Directory Files: Mechanisms such as EF.DIR and DF.CIA provide indirection for locating and retrieving cryptographic objects on the card.
  • ASN.1 Syntax and Encoding: Information syntax defined in ASN.1 (with encoding guidelines and a normative ASN.1 module in Annex A).
  • Storage & Retrieval: Support for multiple instances of cryptographic information and cross-referencing with data objects from other parts of ISO/IEC 7816.
  • Access Control & Authentication: Definitions for access restrictions and multiple authentication mechanisms to protect keys and sensitive objects.
  • Algorithm Agnostic: Support for multiple cryptographic algorithms (suitability of algorithms is out of scope).
  • Extensibility: Cross-referencing and object identifiers to integrate with other ISO/IEC 7816 data objects and external applications.

Practical Applications and Who Uses It

ISO/IEC 7816-15 is used by:

  • Smart card and secure element manufacturers (key and certificate storage formats)
  • System integrators and software developers building card-based authentication, digital signature and secure ID systems
  • Government agencies and credential issuers for eIDs, passports and national ID programs
  • Payment, telecom and IoT solutions that require secure on-card cryptography and standardized object management
  • Certificate Authorities and Public Key Infrastructure (PKI) implementers integrating card-based credentials

Benefits include improved interoperability across vendors, simplified integration of cryptographic services, and predictable object access and protection models.

Related Standards

  • Other parts of the ISO/IEC 7816 series (file structure, data object definitions and APDU conventions) provide complementary specifications for card file systems and command interfaces.
  • Annex A of ISO/IEC 7816-15 contains the normative ASN.1 module and takes precedence for encoding definitions.
Standard

ISO/IEC 7816-15:2016 - Identification cards -- Integrated circuit cards

English language
117 pages
sale 15% off
Preview
sale 15% off
Preview
Standard

ISO/IEC 7816-15:2016 - Identification cards -- Integrated circuit cards

English language
117 pages
sale 15% off
Preview
sale 15% off
Preview

Frequently Asked Questions

ISO/IEC 7816-15:2016 is a standard published by the International Organization for Standardization (ISO). Its full title is "Identification cards - Integrated circuit cards - Part 15: Cryptographic information application". This standard covers: ISO/IEC 7816-15:2016 specifies an application in a card. This application contains information on cryptographic functionality. This part of ISO/IEC 7816 defines a common syntax and format for the cryptographic information and mechanisms to share this information whenever appropriate. The objectives of this part of ISO/IEC 7816 are to - facilitate interoperability among components running on various platforms (platform neutral), - enable applications in the outside world to take advantage of products and components from multiple manufacturers (vendor neutral), - enable the use of advances in technology without rewriting application-level software (application neutral), and - maintain consistency with existing, related standards while expanding upon them only where necessary and practical. It supports the following capabilities: - storage of multiple instances of cryptographic information in a card; - use of the cryptographic information; - retrieval of the cryptographic information, a key factor for this is the notion of "Directory Files", which provides a layer of indirection between objects on the card and the actual format of these objects; - cross-referencing of the cryptographic information with DOs defined in other parts of ISO/IEC 7816 when appropriate; - different authentication mechanisms; - multiple cryptographic algorithms (the suitability of these is outside the scope of this part of ISO/IEC 7816). ISO/IEC 7816-15.2016 does not cover the internal implementation within the card and/or the outside world. It is not mandatory for implementations complying with this International Standard to support all options described. In case of discrepancies between ASN.1 definitions in the body of the text and the module in Annex A, Annex A takes precedence.

ISO/IEC 7816-15:2016 specifies an application in a card. This application contains information on cryptographic functionality. This part of ISO/IEC 7816 defines a common syntax and format for the cryptographic information and mechanisms to share this information whenever appropriate. The objectives of this part of ISO/IEC 7816 are to - facilitate interoperability among components running on various platforms (platform neutral), - enable applications in the outside world to take advantage of products and components from multiple manufacturers (vendor neutral), - enable the use of advances in technology without rewriting application-level software (application neutral), and - maintain consistency with existing, related standards while expanding upon them only where necessary and practical. It supports the following capabilities: - storage of multiple instances of cryptographic information in a card; - use of the cryptographic information; - retrieval of the cryptographic information, a key factor for this is the notion of "Directory Files", which provides a layer of indirection between objects on the card and the actual format of these objects; - cross-referencing of the cryptographic information with DOs defined in other parts of ISO/IEC 7816 when appropriate; - different authentication mechanisms; - multiple cryptographic algorithms (the suitability of these is outside the scope of this part of ISO/IEC 7816). ISO/IEC 7816-15.2016 does not cover the internal implementation within the card and/or the outside world. It is not mandatory for implementations complying with this International Standard to support all options described. In case of discrepancies between ASN.1 definitions in the body of the text and the module in Annex A, Annex A takes precedence.

ISO/IEC 7816-15:2016 is classified under the following ICS (International Classification for Standards) categories: 35.240.15 - Identification cards. Chip cards. Biometrics. The ICS classification helps identify the subject area and facilitates finding related standards.

ISO/IEC 7816-15:2016 has the following relationships with other standards: It is inter standard links to ISO/IEC 7816-15:2016/Amd 1:2018, ISO/IEC 7816-15:2004/Amd 1:2007, ISO/IEC 7816-15:2004/Amd 2:2008, ISO/IEC 7816-15:2004. Understanding these relationships helps ensure you are using the most current and applicable version of the standard.

ISO/IEC 7816-15:2016 is available in PDF format for immediate download after purchase. The document can be added to your cart and obtained through the secure checkout process. Digital delivery ensures instant access to the complete standard document.

Standards Content (Sample)


FINAL
INTERNATIONAL ISO/IEC
DRAFT
STANDARD FDIS
7816-15
ISO/IEC JTC 1/SC 17
Identification cards — Integrated
Secretariat: BSI
circuit cards —
Voting begins
on: 2015-12-07
Part 15:
Voting terminates
Cryptographic information application
on: 2016-02-07
Cartes d’identification — Cartes à circuit intégré à contacts —
Partie 15: Application des informations cryptographiques
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 7816-15:2015(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 2015

ISO/IEC FDIS 7816-15:2015(E)
© ISO/IEC 2015, Published in Switzerland
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
ii © ISO/IEC 2015 – All rights reserved

ISO/IEC FDIS 7816-15
Contents Page
Introduction . vi
1 Scope . 1
2 Normative references . 1
3 Terms and definitions . 2
4 Symbols and abbreviated terms . 5
4.1 Symbols . 5
4.2 Abbreviated terms . 5
5 Conventions . 7
6 Cryptographic information objects . 7
6.1 General . 7
6.2 CIO classes . 7
6.3 Attributes . 8
6.4 Access restrictions . 8
7 CIO files . 8
7.1 Overview . 8
7.2 IC card requirements . 8
7.3 Card file structure . 8
7.4 EF.DIR . 9
7.5 Contents of DF.CIA . 11
7.5.1 Overview . 11
7.5.2 CIAInfo EF . 11
7.5.3 EF.OD . 12
7.5.4 CIO directory files . 12
7.5.5 DF.CIA selection . 13
8 Information syntax in ASN.1 . 13
8.1 Guidelines and encoding conventions . 13
8.2 Basic ASN.1 defined types . 14
8.2.1 Identifier . 14
8.2.2 Reference . 14
8.2.3 Label . 14
8.2.4 CredentialIdentifier . 14
8.2.5 ReferencedValue and Path . 15
8.2.6 ObjectValue . 16
8.2.7 PathOrObjects . 16
8.2.8 CommonObjectAttributes . 17
8.2.9 CommonKeyAttributes . 20
8.2.10 CommonPrivateKeyAttributes . 21
8.2.11 CommonPublicKeyAttributes . 22
8.2.12 CommonSecretKeyAttributes . 22
8.2.13 GenericKeyAttributes . 23
8.2.14 KeyInfo. 23
8.2.15 CommonCertificateAttributes . 23
8.2.16 GenericCertificateAttributes . 24
8.2.17 CommonDataContainerObjectAttributes . 24
8.2.18 CommonAuthenticationObjectAttributes . 25
8.2.19 CIO type . 25
8.3 CIOChoice type . 25
8.4 Private key information objects . 26
8.4.1 PrivateKeyChoice . 26
Error! Reference source not found. i

ISO/IEC FDIS 7816-15
8.4.2 Private RSA key attributes .26
8.4.3 Private elliptic curve key attributes .27
8.4.4 Private Diffie-Hellman key attributes .27
8.4.5 Private DSA key attributes .27
8.4.6 Private KEA key attributes .27
8.4.7 Generic private key information objects .28
8.5 Public key information objects .28
8.5.1 PublicKeyChoice .28
8.5.2 Public RSA key attributes .28
8.5.3 Public elliptic curve key attributes .28
8.5.4 Public Diffie-Hellman key attributes .29
8.5.5 Public DSA key attributes .29
8.5.6 Public KEA key attributes .30
8.5.7 Generic public key information objects .30
8.6 Secret key information objects .30
8.6.1 SecretKeyChoice .30
8.6.2 Algorithm independent key attributes .30
8.6.3 GenericSecretKey type .31
8.7 Certificate information objects .31
8.7.1 CertificateChoice .31
8.7.2 X.509 certificate attributes .31
8.7.3 X.509 attribute certificate attributes.31
8.7.4 SPKI certificate attributes .32
8.7.5 PGP (Pretty Good Privacy) certificate attributes .32
8.7.6 WTLS certificate attributes .32
8.7.7 ANSI X9.68 domain certificate attributes .32
8.7.8 Card verifiable certificate attributes .33
8.7.9 Generic certificate attributes .33
8.8 Data container information objects .33
8.8.1 DataContainerObjectChoice .33
8.8.2 Opaque data container object attributes .33
8.8.3 ISO/IEC 7816 data object attributes .33
8.8.4 Data container information objects identified by OBJECT IDENTIFIERS .34
8.9 Authentication information objects .34
8.9.1 AuthenticationObjectChoice .34
8.9.2 Password attributes .34
8.9.3 Biometric reference data attributes .37
8.9.4 Authentication objects for external and internal authentication .39
8.10 Cryptographic information file, EF.CIAInfo .40
Annex A (normative) ASN.1 module .43
Annex B (informative) CIA example for cards with digital signature and authentication
functionality .59
B.1 General .59
B.2 CIOs .59
B.3 Access control .60
Annex C (informative) Example topologies .62
Annex D (informative) Examples of CIO values and their encodings .67
D.1 General .67
D.2 EF.OD .67
D.2.1 ASN.1 value notation .67
D.2.2 ASN.1 description, tags, lengths and values .68
D.2.3 Hexadecimal DER-encoding .68
D.3 EF.CIAInfo .68
D.3.1 ASN.1 value notation .68
D.3.2 ASN.1 description, tags, lengths and values .69
D.3.3 Hexadecimal DER-encoding .69
D.4 EF.PrKD .69
D.4.1 ASN.1 value notation .69
ii Error! Reference source not found.

ISO/IEC FDIS 7816-15
D.4.2 ASN.1 description, tags, lengths and values. 70
D.4.3 Hexadecimal DER-encoding . 71
D.5 EF. CD . 72
D.5.1 ASN.1 value notation . 72
D.5.2 ASN.1 description, tags, lengths and values. 73
D.5.3 Hexadecimal DER-encoding . 73
D.6 EF.AOD . 74
D.6.1 ASN.1 value notation . 74
D.6.2 ASN.1 description, tags, lengths and values. 75
D.6.3 Hexadecimal DER-encoding . 76
D.7 EF.DCOD . 76
D.7.1 ASN.1 value notation . 76
D.7.2 ASN.1 description, tags, lengths and values. 77
D.7.3 Hexadecimal DER-encoding of DCOD . 77
D.8 Application template (within the EF.DIR) . 78
D.8.1 ASN.1 value notation . 78
D.8.2 ASN.1 description, tags, lengths and values in ApplicationTemplate . 78
D.8.3 Hexadecimal DER-encoding of ApplicationTemplate . 78
D.9 GeneralizedTime encoding guidelines . 78
Annex E (informative) Examples of the use of the cryptographic information application . 80
E.1 General . 80
E.2 Encoding of a private key . 80
E.2.1 Cryptographic information application example description . 80
E.2.2 ASN.1 encoding of an RSA private key . 80
E.2.3 Code encoding and decoding from the ASN.1 . 81
E.2.4 BER encoding . 84
E.3 Encoding of a protected data container . 86
E.3.1 Cryptographic information application example description . 86
E.3.2 ASN.1 encoding of the protected data container object . 86
E.3.3 Code from the ASN.1 for encoding and decoding BER . 87
E.3.4 BER encoding . 95
E.4 Encoding of a certificate . 95
E.4.1 Cryptographic information application example description . 95
E.4.2 ASN.1 Encoding of an X.509 certificate . 95
E.4.3 Code from the ASN.1 for encoding and decoding BER . 97
E.4.4 BER encoding . 103
E.5 Encoding of the ESIGN cryptographic information application . 107
E.5.1 Cryptographic information application example description . 107
E.5.2 ASN.1 encoding of the IAS cryptographic information application . 107
E.5.3 Code from the ASN.1 for encoding a decoding BER . 115
E.5.4 BER encoding . 115
Bibliography . 118

Error! Reference source not found. iii

ISO/IEC FDIS 7816-15
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 meaning of ISO specific terms and expressions related to conformity assessment,
as well as information about ISO's adherence to the WTO principles in the Technical Barriers to Trade (TBT)
see the following URL: Foreword - Supplementary information
The committee responsible for this document is ISO/IEC JTC 1, Information technology, Subcommittee SC 17,
Cards and personal identification.
This second edition cancels and replaces the first edition (ISO/IEC 7816-15:2004), which has been technically
revised. It also incorporates the Amendments ISO/IEC 7816-15:2004/Amd. 1:2007 and ISO/IEC 7816-
15:2004/Amd. 2:2008 and the Technical Corrigendum ISO/IEC 7816-15:2004/Cor. 1:2004.
ISO/IEC 7816 consists of the following parts, under the general title Identification cards — Integrated circuit
cards:
— Part 1: Cards with contacts — Physical characteristics
— Part 2: Cards with contacts — Dimensions and location of the contacts
— Part 3: Cards with contacts — Electrical interface and transmission protocols
— Part 4: Organization, security and commands for interchange
— Part 5: Registration of application providers
— Part 6: Interindustry data elements for interchange
— Part 7: Interindustry commands for Structured Card Query Language (SCQL)
— Part 8: Commands and mechanisms for security operations
— Part 9: Commands for card management
iv Error! Reference source not found.

ISO/IEC FDIS 7816-15
— Part 10: Electronic signals and answer to reset for synchronous cards
— Part 11: Personal verification through biometric methods
— Part 12: Cards with contacts — USB electrical interface and operating procedures
— Part 13: Commands for application management in a multi-application environment
— Part 15: Cryptographic information application
Error! Reference source not found. v

ISO/IEC FDIS 7816-15
Introduction
Integrated circuit cards with cryptographic functions can be used for secure identification of users of
information systems, as well as for other core security services such as non-repudiation with digital signatures
and distribution of enciphering keys for confidentiality. The objective of this part of ISO/IEC 7816 is to provide
a framework for such services based on available International Standards. A main goal has been to provide a
solution that may be used in large-scale systems with several issuers of compatible cards, providing for
international interchange. It is flexible enough to allow for many different environments while still preserving
the requirements for interoperability.
A number of data structures have been provided to manage private keys and key fragments to support a
public key certificate infrastructure and flexible management of user and entity authentication.
This part of ISO/IEC 7816 is based on PKCS #15 v1.1 (see Reference [9]). The relationship between these
documents is as follows:
 a common core is identical in both documents;
 those components of PKCS #15 which do not relate to IC cards have been removed.
This part of ISO/IEC 7816 includes enhancements to meet specific IC card requirements.
vi Error! Reference source not found.

FINAL DRAFT INTERNATIONAL STANDARD ISO/IEC FDIS 7816-15

Identification cards — Integrated circuit cards — Part 15:
Cryptographic information application
1 Scope
This part of ISO/IEC 7816 specifies an application in a card. This application contains information on
cryptographic functionality. This part of ISO/IEC 7816 defines a common syntax and format for the
cryptographic information and mechanisms to share this information whenever appropriate.
The objectives of this part of ISO/IEC 7816 are to
 facilitate interoperability among components running on various platforms (platform neutral),
 enable applications in the outside world to take advantage of products and components from multiple
manufacturers (vendor neutral),
 enable the use of advances in technology without rewriting application-level software (application neutral),
and
 maintain consistency with existing, related standards while expanding upon them only where necessary
and practical.
It supports the following capabilities:
 storage of multiple instances of cryptographic information in a card;
 use of the cryptographic information;
 retrieval of the cryptographic information, a key factor for this is the notion of “Directory Files”, which
provides a layer of indirection between objects on the card and the actual format of these objects;
 cross-referencing of the cryptographic information with DOs defined in other parts of ISO/IEC 7816 when
appropriate;
 different authentication mechanisms;
 multiple cryptographic algorithms (the suitability of these is outside the scope of this part of
ISO/IEC 7816).
This part of ISO/IEC 7816 does not cover the internal implementation within the card and/or the outside world.
It is not mandatory for implementations complying with this International Standard to support all options
described.
In case of discrepancies between ASN.1 definitions in the body of the text and the module in
Annex A, Annex A takes precedence.
2 Normative references
The following documents, in whole or in part, are normatively referenced in this document and are
indispensable for its application. For dated references, only the edition cited applies. For undated
references, the latest edition of the referenced document (including any amendments) applies.
Error! Reference source not found. 1

ISO/IEC FDIS 7816-15
ISO 9564-1, Final services — Personal Identification Number (PIN) management and security — Part 1: Basic
principles and requirements for PINs in card-based system
ISO/IEC 7816 (all parts), Identification cards — Integrated circuit cards with contacts
ISO/IEC 8824-1, Information technology — Abstract Syntax Notation One (ASN.1): Specification of basic
notation
ISO/IEC 8824-2, Information technology — Abstract Syntax Notation One (ASN.1): Information object
specification
ISO/IEC 8824-3, Information technology — Abstract Syntax Notation One (ASN.1): Constraint specification
ISO/IEC 8824-4, Information technology — Abstract Syntax Notation One (ASN.1): Parameterization of ASN.1
specifications
ISO/IEC 8825-1, Information technology — ASN.1 encoding rules: Specification of Basic Encoding Rules
(BER), Canonical Encoding Rules (CER) and Distinguished Encoding Rules (DER)
ISO/IEC 9594-8, Information technology — Open Systems Interconnection — The Directory — Part 8: Public-
key and attribute certificate frameworks
ANSI X9.42-2001, Public Key Cryptography for the Financial Services Industry: Agreement of Symmetric Keys
Using Discrete Logarithm Cryptography
ANSI X9.62-1998, Public Key Cryptography for the Financial Services Industry: The Elliptic Curve Digital
Signature Algorithm (ECDSA)
3 Terms and definitions
For the purposes of this document, the following terms and definitions apply.
3.1
absolute path
path that starts with the file identifier ’3F00’
3.2
application
data structures, data elements and program modules needed for performing a specific functionality
[SOURCE: ISO/IEC 7816-4:2013, 3.3, modified]
3.3
application identifier
data element that identifies an application in a card
Note 1 to entry: Adapted from ISO/IEC 7816-4.
3.4
application provider
entity providing the components required for performing an application in the card
[SOURCE: ISO/IEC 7816-4:2013, 3.7, modified]
3.5
authentication information object
cryptographic information object that provides information about authentication related data
EXAMPLE A password.
2 Error! Reference source not found.

ISO/IEC FDIS 7816-15
3.6
authentication object directory file
elementary file containing authentication information objects
3.7
binary coded decimal
number representation where a number is expressed as a sequence of decimal digits and each decimal digit
is encoded as a four bit binary number
3.8
cardholder
person to whom the card was issued
3.9
card issuer
organization or entity that issues cards
3.10
certificate directory file
elementary file containing certificate information objects
3.11
certificate information object
cryptographic information object that provides information about a certificate
3.12
command
message that initiates an action and solicits a response from the card
3.13
cryptographic information application
application in a card that contains information on cryptographic information objects, other security data
elements and their intended use
3.14
cryptographic information object
structured information contained in a CIA, which describes a cryptographic data element
EXAMPLE A public key or a certificate.
3.15
data container information object
cryptographic information object that provides information about a data container
EXAMPLE A file.
3.16
data container object directory file
elementary file containing data container information objects
3.17
dedicated file
structure containing file control information, and, optionally, memory available for allocation
[SOURCE: ISO/IEC 7816-4:2013, 3.19]
Error! Reference source not found. 3

ISO/IEC FDIS 7816-15
3.18
Directory
DIR file
optional elementary file containing a list of applications supported by the card and optional related data
elements
[SOURCE: ISO/IEC 7816-4:2013, 3.22, modified]
3.19
elementary file
set of data units or records or data objects sharing the same file identifier and the same security attribute(s)
[SOURCE: ISO/IEC 7816-4:2013, 3.23, modified]
3.20
file identifier
data element (two bytes) used to address a file
[SOURCE: ISO/IEC 7816-4:2013, 3.27]
3.21
function
process accomplished by one or more commands and resultant actions
3.22
master file
unique dedicated file representing the root in a card using a hierarchy of dedicated files
[SOURCE: ISO/IEC 7816-4:2013, 3.33, modified]
Note 1 to entry: The MF has file identifier ‘3F00’.
3.23
message
string of bytes transmitted by the interface device to the card or vice versa, excluding transmission-oriented
characters
3.24
object directory file
mandatory elementary file containing information about other CIA directory files
3.25
password
data that may be required by the application to be presented to the card by its user for authentication purpose
[SOURCE: ISO/IEC 7816-4:2013, 3.37]
3.26
path
concatenation of file identifiers without delimitation
[SOURCE: ISO/IEC 7816-4:2013, 3.38]
3.27
private key directory file
elementary file containing private key information objects
4 Error! Reference source not found.

ISO/IEC FDIS 7816-15
3.28
private key information object
cryptographic information object that provides information about a private key
3.29
provider
authority who has or who obtained the right to create a dedicated file in the card
[SOURCE: ISO/IEC 7816-4:2013, 3.41]
3.30
public key directory file
elementary file containing public key information objects
3.31
public key information object
cryptographic information object that provides information about a public key
3.32
record
string of bytes referenced and handled by the card within an elementary file of record structure
[SOURCE: ISO/IEC 7816-4:2013, 3.43]
3.33
relative path
path that starts with the file identifier of the current DF
3.34
secret key directory file
elementary file containing secret key information objects
3.35
secret key information object
cryptographic information object that provides information about a secret key
3.36
template
set of data objects forming the value field of a constructed data object
Note 1 to entry: Adapted from ISO/IEC 7816-6.
4 Symbols and abbreviated terms
4.1 Symbols
DF.x dedicated file x, where x is the acronym of the file
EF.x elementary file x, where x is the acronym of the file
‘0’ to ‘9’ and ‘A’ to ‘F’ hexadecimal digits

4.2 Abbreviated terms
For the purposes of this part of ISO/IEC 7816, the following abbreviated terms apply.
AID application identifier
Error! Reference source not found. 5

ISO/IEC FDIS 7816-15
AOD authentication object directory
BCD binary-coded decimal
CD certificate directory
CDE cryptographic data element
CIA cryptographic information application
CIO cryptographic information object
C-RP command –response pair
CV card-verifiable
DCOD data container object directory
DDO discretionary data object
DF dedicated file
DH Diffie-Hellman
DSA digital signature algorithm
EC elliptic curve
EF elementary file
IDO interindustry data object, as defined in ISO/IEC 7816-6
IFD interface device
KEA key exchange algorithm
MF master file
OD object directory
PKCS public-key cryptography standard
PrKD private key directory
PuKD public key directory
RSA Rivest-Shamir-Adleman
SKD secret key directory
SPKI simple public key infrastructure
UCS universal multiple-octet coded character set (see ISO/IEC 10646)
URL uniform resource locator
UTC coordinated universal time
UTF-8 UCS transformation format 8
6 Error! Reference source not found.

ISO/IEC FDIS 7816-15
WTLS wireless application protocol transport layer security
5 Conventions
This part of ISO/IEC 7816 presents ASN.1 notation in the bold Helvetica typeface. When ASN.1 types and
values are referenced in normal text, they are differentiated from normal text by presenting them in the bold
Helvetica typeface. The names of commands, typically referenced when specifying information exchanges
between cards and IFDs, are differentiated from normal text by displaying them in Courier.
If the items in a list are numbered (as opposed to using “–” or letters), then the items shall be considered steps
in a procedure.
6 Cryptographic information objects
6.1 General
This part of ISO/IEC 7816 provides
 descriptions of objects describing cryptographic information contained in the card,
 descriptions of the intended use of this information,
 ways to retrieve this information (when appropriate),
 an abstract syntax for the information which provides the basis for encodings, and
 an object model for the information.
The information, which also may include access control information, is described in the form of CIOs.
6.2 CIO classes
This part of ISO/IEC 7816 defines four classes of CIOs as follows:
 cryptographic key information objects;
 certificate information objects;
 data container information objects;
 authentication information objects.
The logical structure of these CIOs is shown in Figure 1. The object class of cryptographic key information
objects has three subclasses: private key, secret key, and public key information objects. CIOs inherit
attributes from higher-level classes and may be instantiated on cards.

Error! Reference source not found. 7

Cryptographic
ISO/IEC FDIS 7816-15
Information Object
Certificate
Cryptographic
Authentication
Data Container
Information
Key Information  Information
Information
Object
Object Object
Object
Pass-
Private  CV X.509 Biometric
Secret  Public  Other Data  External
Data
word
Key Certificate  Certificate  Data
Certificate  File Authent.
Key Key Object
Info
Info Info Info
Info  Info Info Info
Info Info Info
Object Object Object Object
Object Object  Object Object
Object  Object  Object
Figure 1 — CIO class hierarchy
6.3 Attributes
All CIOs have a number of attributes. Type-specific attributes are always present. Group-specific attributes
and attributes common to all CIOs may be inherited as shown in Figure 2. Attributes are defined in Clause 8.

Type-specific
Common CIO Class-specific Sub-class-specific
CIO Attributes
Attributes CIO Attributes CIO Attributes
Figure 2 — Attribute inheritance concept
6.4 Access restrictions
CDEs can be private, meaning that they are protected against unauthorized access, or public. Access (read,
write, etc.) to private CDEs is described by authentication information objects (which also includes
authentication procedures). Conditional access (from a cardholder’s perspective) is achieved with knowledge-
based user information, biometric user information, or cryptographic means. Public CDEs are not protected
from read-access.
7 CIO files
7.1 Overview
A CIO is contained in an elementary file, and refers, in general, to a CDE; a CIO may in some cases contain
the CDE directly. A dedicated file (DF.CIA) contains CIO elementary files. Certain CIO files may be present
under other dedicated files, in which case, they are referenced to from the DF.CIA.
7.2 IC card requirements
Cards shall comply with the appropriate parts of ISO/IEC 7816, when using
 hierarchic logical file systems,
 direct or indirect application selection,
 access control mechanisms,
 read operations, and
 cryptographic operations.
7.3 Card file structure
A typical card supporting this part of ISO/IEC 7816 will have the following layout:
8 Error! Reference source not found.

ISO/IEC FDIS 7816-15
MF
DF.CIA EF.DIR
EF.CIAInfo
EF.OD
EF.AOD EF.PrKD EF.CD EF.PuKD EF.SKD EF.DCOD

NOTE 1 For the purpose of this part of ISO/IEC 7816, EF.DIR is only needed on cards that do not support application
selection using AID as DF name as defined in ISO/IEC 7816-4 or when multiple CIAs reside on a single card.
NOTE 2 Square element files are mandatory for this part of ISO/IEC 7816 (see Table 1). MF may not be seen at the
interface (see ISO/IEC 7816-4).
Figure 3 — Example contents of DF.CIA
Other possible topologies are discussed in Annex C. The contents and purpose of each file and directory are
described below.
7.4 EF.DIR
This file (file identifier: ‘2F00’) shall, if present, contain one or several application templates as defined in
ISO/IEC 7816-4. The application template (tag ‘61’) for a CIA shall at least contain the following IDOs:
 application identifier (tag ‘4F’), value defined in 7.5.5;
 path (tag ‘51’), value supplied by application provider; if Path is missing, it denotes a virtual DF.CIA the
CIO files of which are hosted by an application, either implicitly known or defined by the CIODDO (tag
‘73’).
 CIODDO (tag ‘73’) conditional, with odfPath and ciaInfoPath reference CIOs; it shall be present if Path is
missing.
Other IDOs from ISO/IEC 7816-4 may, at the application provider’s discretion, be present as well. In particular,
it is recommended that application providers
...


INTERNATIONAL ISO/IEC
STANDARD 7816-15
Second edition
2016-05-15
Identification cards — Integrated
circuit cards —
Part 15:
Cryptographic information application
Cartes d’identification — Cartes à circuit intégré à contacts —
Partie 15: Application des informations cryptographiques
Reference number
©
ISO/IEC 2016
© ISO/IEC 2016, Published in Switzerland
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
ii © ISO/IEC 2016 – All rights reserved

Contents Page
Foreword . iv
Introduction . vi
1 Scope . 1
2 Normative references . 2
3 Terms and definitions . 2
4 Symbols and abbreviated terms . 5
4.1 Symbols . 5
4.2 Abbreviated terms . 5
5 Conventions . 7
6 Cryptographic information objects . 7
6.1 General . 7
6.2 CIO classes . 7
6.3 Attributes . 8
6.4 Access restrictions . 8
7 CIO files . 8
7.1 Overview . 8
7.2 IC card requirements . 8
7.3 Card file structure . 9
7.4 EF.DIR . 9
7.5 Contents of DF.CIA . 11
7.5.1 Overview . 11
7.5.2 CIAInfo EF . 11
7.5.3 EF.OD . 12
7.5.4 CIO directory files . 12
7.5.5 DF.CIA selection . 13
8 Information syntax in ASN.1 . 14
8.1 Guidelines and encoding conventions . 14
8.2 Basic ASN.1 defined types . 14
8.2.1 Identifier. 14
8.2.2 Reference . 14
8.2.3 Label . 14
8.2.4 CredentialIdentifier . 14
8.2.5 ReferencedValue and Path . 15
8.2.6 ObjectValue . 16
8.2.7 PathOrObjects . 17
8.2.8 CommonObjectAttributes . 17
8.2.9 CommonKeyAttributes . 21
8.2.10 CommonPrivateKeyAttributes . 22
8.2.11 CommonPublicKeyAttributes. 23
8.2.12 CommonSecretKeyAttributes . 23
8.2.13 GenericKeyAttributes . 24
8.2.14 KeyInfo. 24
8.2.15 CommonCertificateAttributes . 24
8.2.16 GenericCertificateAttributes . 25
8.2.17 CommonDataContainerObjectAttributes . 25
8.2.18 CommonAuthenticationObjectAttributes . 25
8.2.19 CIO type . 26
8.3 CIOChoice type . 26
© ISO/IEC 2016 – All rights reserved i

8.4 Private key information objects . 27
8.4.1 PrivateKeyChoice . 27
8.4.2 Private RSA key attributes . 27
8.4.3 Private elliptic curve key attributes . 27
8.4.4 Private Diffie-Hellman key attributes . 28
8.4.5 Private DSA key attributes . 28
8.4.6 Private KEA key attributes . 28
8.4.7 Generic private key information objects . 28
8.5 Public key information objects . 29
8.5.1 PublicKeyChoice. 29
8.5.2 Public RSA key attributes . 29
8.5.3 Public elliptic curve key attributes . 29
8.5.4 Public Diffie-Hellman key attributes . 30
8.5.5 Public DSA key attributes . 30
8.5.6 Public KEA key attributes . 30
8.5.7 Generic public key information objects . 31
8.6 Secret key information objects . 31
8.6.1 SecretKeyChoice . 31
8.6.2 Algorithm independent key attributes . 31
8.6.3 GenericSecretKey type . 31
8.7 Certificate information objects . 31
8.7.1 CertificateChoice . 31
8.7.2 X.509 certificate attributes . 32
8.7.3 X.509 attribute certificate attributes. 32
8.7.4 SPKI certificate attributes . 32
8.7.5 PGP (Pretty Good Privacy) certificate attributes . 33
8.7.6 WTLS certificate attributes . 33
8.7.7 ANSI X9.68 domain certificate attributes . 33
8.7.8 Card verifiable certificate attributes . 33
8.7.9 Generic certificate attributes . 34
8.8 Data container information objects . 34
8.8.1 DataContainerObjectChoice . 34
8.8.2 Opaque data container object attributes . 34
8.8.3 ISO/IEC 7816 data object attributes . 34
8.8.4 Data container information objects identified by OBJECT IDENTIFIERS . 34
8.9 Authentication information objects . 35
8.9.1 AuthenticationObjectChoice . 35
8.9.2 Password attributes . 35
8.9.3 Biometric reference data attributes . 38
8.9.4 Authentication objects for external and internal authentication . 40
8.10 Cryptographic information file, EF.CIAInfo . 40
Annex A (normative) ASN.1 module . 43
Annex B (informative) CIA example for cards with digital signature and authentication
functionality . 59
B.1 General . 59
B.2 CIOs . 59
B.3 Access control . 60
Annex C (informative) Example topologies . 62
Annex D (informative) Examples of CIO values and their encodings . 67
D.1 General . 67
D.2 EF.OD . 67
D.2.1 ASN.1 value notation . 67
D.2.2 ASN.1 description, tags, lengths and values . 68
D.2.3 Hexadecimal DER-encoding . 68
D.3 EF.CIAInfo . 68
D.3.1 ASN.1 value notation . 68
D.3.2 ASN.1 description, tags, lengths and values . 69
D.3.3 Hexadecimal DER-encoding . 69
ii © ISO/IEC 2016 – All rights reserved

D.4 EF.PrKD . 69
D.4.1 ASN.1 value notation . 69
D.4.2 ASN.1 description, tags, lengths and values. 70
D.4.3 Hexadecimal DER-encoding . 71
D.5 EF. CD . 72
D.5.1 ASN.1 value notation . 72
D.5.2 ASN.1 description, tags, lengths and values. 73
D.5.3 Hexadecimal DER-encoding . 73
D.6 EF.AOD . 74
D.6.1 ASN.1 value notation . 74
D.6.2 ASN.1 description, tags, lengths and values. 74
D.6.3 Hexadecimal DER-encoding . 76
D.7 EF.DCOD. 76
D.7.1 ASN.1 value notation . 76
D.7.2 ASN.1 description, tags, lengths and values. 77
D.7.3 Hexadecimal DER-encoding of DCOD . 77
D.8 Application template (within the EF.DIR) . 78
D.8.1 ASN.1 value notation . 78
D.8.2 ASN.1 description, tags, lengths and values in ApplicationTemplate . 78
D.8.3 Hexadecimal DER-encoding of ApplicationTemplate . 78
D.9 GeneralizedTime encoding guidelines . 78
Annex E (informative) Examples of the use of the cryptographic information application . 80
E.1 General . 80
E.2 Encoding of a private key . 80
E.2.1 Cryptographic information application example description . 80
E.2.2 ASN.1 encoding of an RSA private key . 80
E.2.3 Code encoding and decoding from the ASN.1 . 81
E.2.4 BER encoding . 84
E.3 Encoding of a protected data container . 86
E.3.1 Cryptographic information application example description . 86
E.3.2 ASN.1 encoding of the protected data container object . 86
E.3.3 Code from the ASN.1 for encoding and decoding BER . 87
E.3.4 BER encoding . 95
E.4 Encoding of a certificate . 95
E.4.1 Cryptographic information application example description . 95
E.4.2 ASN.1 Encoding of an X.509 certificate . 95
E.4.3 Code from the ASN.1 for encoding and decoding BER . 97
E.4.4 BER encoding . 103
E.5 Encoding of the ESIGN cryptographic information application . 107
E.5.1 Cryptographic information application example description . 107
E.5.2 ASN.1 encoding of the IAS cryptographic information application . 107
E.5.3 Code from the ASN.1 for encoding a decoding BER . 115
E.5.4 BER encoding . 115
Bibliography . 117
© ISO/IEC 2016 – All rights reserved iii

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 meaning of ISO specific terms and expressions related to conformity assessment,
as well as information about ISO's adherence to the WTO principles in the Technical Barriers to Trade (TBT)
see the following URL: Foreword - Supplementary information
The committee responsible for this document is ISO/IEC JTC 1, Information technology, Subcommittee SC 17,
Cards and personal identification.
This second edition cancels and replaces the first edition (ISO/IEC 7816-15:2004), which has been technically
revised. It also incorporates the Amendments ISO/IEC 7816-15:2004/Amd. 1:2007 and ISO/IEC 7816-
15:2004/Amd. 2:2008 and the Technical Corrigendum ISO/IEC 7816-15:2004/Cor. 1:2004.
ISO/IEC 7816 consists of the following parts, under the general title Identification cards — Integrated circuit
cards:
— Part 1: Cards with contacts — Physical characteristics
— Part 2: Cards with contacts — Dimensions and location of the contacts
— Part 3: Cards with contacts — Electrical interface and transmission protocols
— Part 4: Organization, security and commands for interchange
— Part 5: Registration of application providers
— Part 6: Interindustry data elements for interchange
— Part 7: Interindustry commands for Structured Card Query Language (SCQL)
— Part 8: Commands and mechanisms for security operations
— Part 9: Commands for card management
iv © ISO/IEC 2016 – All rights reserved

— Part 10: Electronic signals and answer to reset for synchronous cards
— Part 11: Personal verification through biometric methods
— Part 12: Cards with contacts — USB electrical interface and operating procedures
— Part 13: Commands for application management in a multi-application environment
— Part 15: Cryptographic information application
© ISO/IEC 2016 – All rights reserved v

Introduction
Integrated circuit cards with cryptographic functions can be used for secure identification of users of
information systems, as well as for other core security services such as non-repudiation with digital signatures
and distribution of enciphering keys for confidentiality. The objective of this part of ISO/IEC 7816 is to provide
a framework for such services based on available International Standards. A main goal has been to provide a
solution that may be used in large-scale systems with several issuers of compatible cards, providing for
international interchange. It is flexible enough to allow for many different environments while still preserving
the requirements for interoperability.
A number of data structures have been provided to manage private keys and key fragments to support a
public key certificate infrastructure and flexible management of user and entity authentication.
This part of ISO/IEC 7816 is based on PKCS #15 v1.1 (see Reference [9]). The relationship between these
documents is as follows:
 a common core is identical in both documents;
 those components of PKCS #15 which do not relate to IC cards have been removed.
This part of ISO/IEC 7816 includes enhancements to meet specific IC card requirements.
vi © ISO/IEC 2016 – All rights reserved

INTERNATIONAL STANDARD ISO/IEC 7816-15:2016(E)

Identification cards — Integrated circuit cards — Part 15:
Cryptographic information application
1 Scope
This part of ISO/IEC 7816 specifies an application in a card. This application contains information on
cryptographic functionality. This part of ISO/IEC 7816 defines a common syntax and format for the
cryptographic information and mechanisms to share this information whenever appropriate.
The objectives of this part of ISO/IEC 7816 are to
 facilitate interoperability among components running on various platforms (platform neutral),
 enable applications in the outside world to take advantage of products and components from multiple
manufacturers (vendor neutral),
 enable the use of advances in technology without rewriting application-level software (application neutral),
and
 maintain consistency with existing, related standards while expanding upon them only where necessary
and practical.
It supports the following capabilities:
 storage of multiple instances of cryptographic information in a card;
 use of the cryptographic information;
 retrieval of the cryptographic information, a key factor for this is the notion of “Directory Files”, which
provides a layer of indirection between objects on the card and the actual format of these objects;
 cross-referencing of the cryptographic information with DOs defined in other parts of ISO/IEC 7816 when
appropriate;
 different authentication mechanisms;
 multiple cryptographic algorithms (the suitability of these is outside the scope of this part of
ISO/IEC 7816).
This part of ISO/IEC 7816 does not cover the internal implementation within the card and/or the outside world.
It is not mandatory for implementations complying with this International Standard to support all options
described.
In case of discrepancies between ASN.1 definitions in the body of the text and the module in Annex A,
Annex A takes precedence.
© ISO/IEC 2016 – All rights reserved 1

2 Normative references
The following documents, in whole or in part, are normatively referenced in this document and are
indispensable for its application. For dated references, only the edition cited applies. For undated
references, the latest edition of the referenced document (including any amendments) applies.
ISO 9564-1, Final services — Personal Identification Number (PIN) management and security — Part 1: Basic
principles and requirements for PINs in card-based system
ISO/IEC 7816 (all parts), Identification cards — Integrated circuit cards with contacts
ISO/IEC 8824-1, Information technology — Abstract Syntax Notation One (ASN.1): Specification of basic
notation
ISO/IEC 8824-2, Information technology — Abstract Syntax Notation One (ASN.1): Information object
specification
ISO/IEC 8824-3, Information technology — Abstract Syntax Notation One (ASN.1): Constraint specification
ISO/IEC 8824-4, Information technology — Abstract Syntax Notation One (ASN.1): Parameterization of ASN.1
specifications
ISO/IEC 8825-1, Information technology — ASN.1 encoding rules: Specification of Basic Encoding Rules
(BER), Canonical Encoding Rules (CER) and Distinguished Encoding Rules (DER)
ISO/IEC 9594-8, Information technology — Open Systems Interconnection — The Directory — Part 8: Public-
key and attribute certificate frameworks
ANSI X9.62, Public Key Cryptography for the Financial Services Industry: The Elliptic Curve Digital Signature
Algorithm (ECDSA)
3 Terms and definitions
For the purposes of this document, the following terms and definitions apply.
3.1
absolute path
path that starts with the file identifier ’3F00’
3.2
application
data structures, data elements and program modules needed for performing a specific functionality
[SOURCE: ISO/IEC 7816-4:2013, 3.3, modified]
3.3
application identifier
data element that identifies an application in a card
Note 1 to entry: Adapted from ISO/IEC 7816-4.
3.4
application provider
entity providing the components required for performing an application in the card
[SOURCE: ISO/IEC 7816-4:2013, 3.7, modified]
2 © ISO/IEC 2016 – All rights reserved

3.5
authentication information object
cryptographic information object that provides information about authentication related data
EXAMPLE A password.
3.6
authentication object directory file
elementary file containing authentication information objects
3.7
binary coded decimal
number representation where a number is expressed as a sequence of decimal digits and each decimal digit
is encoded as a four bit binary number
3.8
cardholder
person to whom the card was issued
3.9
card issuer
organization or entity that issues cards
3.10
certificate directory file
elementary file containing certificate information objects
3.11
certificate information object
cryptographic information object that provides information about a certificate
3.12
command
message that initiates an action and solicits a response from the card
3.13
cryptographic information application
application in a card that contains information on cryptographic information objects, other security data
elements and their intended use
3.14
cryptographic information object
structured information contained in a CIA, which describes a cryptographic data element
EXAMPLE A public key or a certificate.
3.15
data container information object
cryptographic information object that provides information about a data container
EXAMPLE A file.
3.16
data container object directory file
elementary file containing data container information objects
3.17
dedicated file
structure containing file control information, and, optionally, memory available for allocation
© ISO/IEC 2016 – All rights reserved 3

[SOURCE: ISO/IEC 7816-4:2013, 3.19]
3.18
Directory
DIR file
optional elementary file containing a list of applications supported by the card and optional related data
elements
[SOURCE: ISO/IEC 7816-4:2013, 3.22, modified]
3.19
elementary file
set of data units or records or data objects sharing the same file identifier and the same security attribute(s)
[SOURCE: ISO/IEC 7816-4:2013, 3.23, modified]
3.20
file identifier
data element (two bytes) used to address a file
[SOURCE: ISO/IEC 7816-4:2013, 3.27]
3.21
function
process accomplished by one or more commands and resultant actions
3.22
master file
unique dedicated file representing the root in a card using a hierarchy of dedicated files
[SOURCE: ISO/IEC 7816-4:2013, 3.33, modified]
Note 1 to entry: The MF has file identifier ‘3F00’.
3.23
message
string of bytes transmitted by the interface device to the card or vice versa, excluding transmission-oriented
characters
3.24
object directory file
mandatory elementary file containing information about other CIA directory files
3.25
password
data that may be required by the application to be presented to the card by its user for authentication purpose
[SOURCE: ISO/IEC 7816-4:2013, 3.37]
3.26
path
concatenation of file identifiers without delimitation
[SOURCE: ISO/IEC 7816-4:2013, 3.38]
3.27
private key directory file
elementary file containing private key information objects
4 © ISO/IEC 2016 – All rights reserved

3.28
private key information object
cryptographic information object that provides information about a private key
3.29
provider
authority who has or who obtained the right to create a dedicated file in the card
[SOURCE: ISO/IEC 7816-4:2013, 3.41]
3.30
public key directory file
elementary file containing public key information objects
3.31
public key information object
cryptographic information object that provides information about a public key
3.32
record
string of bytes referenced and handled by the card within an elementary file of record structure
[SOURCE: ISO/IEC 7816-4:2013, 3.43]
3.33
relative path
path that starts with the file identifier of the current DF
3.34
secret key directory file
elementary file containing secret key information objects
3.35
secret key information object
cryptographic information object that provides information about a secret key
3.36
template
set of data objects forming the value field of a constructed data object
Note 1 to entry: Adapted from ISO/IEC 7816-6.
4 Symbols and abbreviated terms
4.1 Symbols
DF.x dedicated file x, where x is the acronym of the file
EF.x elementary file x, where x is the acronym of the file
‘0’ to ‘9’ and ‘A’ to ‘F’ hexadecimal digits

4.2 Abbreviated terms
For the purposes of this part of ISO/IEC 7816, the following abbreviated terms apply.
AID application identifier
© ISO/IEC 2016 – All rights reserved 5

AOD authentication object directory
BCD binary-coded decimal
CD certificate directory
CDE cryptographic data element
CIA cryptographic information application
CIO cryptographic information object
C-RP command –response pair
CV card-verifiable
DCOD data container object directory
DDO discretionary data object
DF dedicated file
DH Diffie-Hellman
DSA digital signature algorithm
EC elliptic curve
EF elementary file
IDO interindustry data object, as defined in ISO/IEC 7816-6
IFD interface device
KEA key exchange algorithm
MF master file
OD object directory
PKCS public-key cryptography standard
PrKD private key directory
PuKD public key directory
RSA Rivest-Shamir-Adleman
SKD secret key directory
SPKI simple public key infrastructure
UCS universal multiple-octet coded character set (see ISO/IEC 10646)
URL uniform resource locator
UTC coordinated universal time
UTF-8 UCS transformation format 8
6 © ISO/IEC 2016 – All rights reserved

WTLS wireless application protocol transport layer security
5 Conventions
This part of ISO/IEC 7816 presents ASN.1 notation in the bold Helvetica typeface. When ASN.1 types and
values are referenced in normal text, they are differentiated from normal text by presenting them in the bold
Helvetica typeface. The names of commands, typically referenced when specifying information exchanges
between cards and IFDs, are differentiated from normal text by displaying them in Courier.
If the items in a list are numbered (as opposed to using “–” or letters), then the items shall be considered steps
in a procedure.
6 Cryptographic information objects
6.1 General
This part of ISO/IEC 7816 provides
 descriptions of objects describing cryptographic information contained in the card,
 descriptions of the intended use of this information,
 ways to retrieve this information (when appropriate),
 an abstract syntax for the information which provides the basis for encodings, and
 an object model for the information.
The information, which also may include access control information, is described in the form of CIOs.
6.2 CIO classes
This part of ISO/IEC 7816 defines four classes of CIOs as follows:
 cryptographic key information objects;
 certificate information objects;
 data container information objects;
 authentication information objects.
The logical structure of these CIOs is shown in Figure 1. The object class of cryptographic key information
objects has three subclasses: private key, secret key, and public key information objects. CIOs inherit
attributes from higher-level classes and may be instantiated on cards.
© ISO/IEC 2016 – All rights reserved 7

Cryptographic
Information Object
Certificate
Cryptographic
Authentication
Data Container
Information
Key Information
Information
Information
Object
Object
Object
Object
Private  X.509 Pass-
CV Other Data  Biometric  External
Secret  Public   Data
Certificate  word
Key Certificate  Certificate  File Data Authent.
Key Key Object
Info Info
Info Info Info
Info Info Info  Info Info Info

Object Object
Object Object Object
Object  Object  Object Object  Object
Object
Figure 1 — CIO class hierarchy
6.3 Attributes
All CIOs have a number of attributes. Type-specific attributes are always present. Group-specific attributes
and attributes common to all CIOs may be inherited as shown in Figure 2. Attributes are defined in Clause 8.

Type-specific
Common CIO Class-specific Sub-class-specific
CIO Attributes
Attributes CIO Attributes CIO Attributes
Figure 2 — Attribute inheritance concept
6.4 Access restrictions
CDEs can be private, meaning that they are protected against unauthorized access, or public. Access (read,
write, etc.) to private CDEs is described by authentication information objects (which also includes
authentication procedures). Conditional access (from a cardholder’s perspective) is achieved with knowledge-
based user information, biometric user information, or cryptographic means. Public CDEs are not protected
from read-access.
7 CIO files
7.1 Overview
A CIO is contained in an elementary file, and refers, in general, to a CDE; a CIO may in some cases contain
the CDE directly. A dedicated file (DF.CIA) contains CIO elementary files. Certain CIO files may be present
under other dedicated files, in which case, they are referenced to from the DF.CIA.
7.2 IC card requirements
Cards shall comply with the appropriate parts of ISO/IEC 7816, when using
 hierarchic logical file systems,
 direct or indirect application selection,
 access control mechanisms,
 read operations, and
 cryptographic operations.
8 © ISO/IEC 2016 – All rights reserved

7.3 Card file structure
A typical card supporting this part of ISO/IEC 7816 will have the following layout:

MF
DF.CIA EF.DIR
EF.CIAInfo
EF.OD
EF.AOD EF.PrKD EF.CD EF.PuKD EF.SKD EF.DCOD

NOTE 1 For the purpose of this part of ISO/IEC 7816, EF.DIR is only needed on cards that do not support application
selection using AID as DF name as defined in ISO/IEC 7816-4 or when multiple CIAs reside on a single card.
NOTE 2 Square element files are mandatory for this part of ISO/IEC 7816 (see Table 1). MF may not be seen at the
interface (see ISO/IEC 7816-4).
Figure 3 — Example contents of DF.CIA
Other possible topologies are discussed in Annex C. The contents and purpose of each file and directory are
described below.
7.4 EF.DIR
This file (file identifier: ‘2F00’) shall, if present, contain one or several application templates as defined in
ISO/IEC 7816-4. The application template (tag ‘61’) for a CIA shall at least contain the following IDOs:
‘4F’), value defined in 7.5.5;
 application identifier (tag
‘51’), value supplied by application provider; if Path is missing, it denotes a virtual DF.CIA the
 path (tag
CIO files of which are hosted by an application, either implicitly known or defined by the CIODDO (tag
‘73’).
 CIODDO (tag ‘73’) conditional, with odfPath and ciaInfoPath reference CIOs; it shall be present if Path is
missing.
Other IDOs from ISO/IEC 7816-4 may, at the application provider’s discretion, be present as well. In particular,
it is recommended that application providers include both the “Discretionary data objects” data object (tag ‘73’)
and the “Application label” data object (tag ‘50’). The application label shall contain a UTF-8 encoded label for
the application, chosen by the application provider. The “Discretionary data objects” data object shall, if
present, contain a DER-encoded (ISO/IEC 8825-1:1998) value of the ASN.1 type CIODDO:
CIODDO ::= SEQUENCE {
providerId  OBJECT IDENTIFIER OPTIONAL,
odfPath  Path OPTIONAL,
ciaInfoPath [0] Pa
...

Questions, Comments and Discussion

Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.

Loading comments...