ISO 7816-5 PDF

STANDARD. ISO/IEC. Second edition. Identification cards — Integrated circuit cards —. Part 5: Registration of application providers. ISO is one of most important standards in the smart card industry. Parts of ISO specify physical characteristics, dimensions and location of the. ISO , Section 5 contains basic organizations, data structures, file organization, file referencing methods, data referencing methods, record referencing.

Author: Daim Sagis
Country: Denmark
Language: English (Spanish)
Genre: Technology
Published (Last): 26 May 2010
Pages: 162
PDF File Size: 18.21 Mb
ePub File Size: 1.33 Mb
ISBN: 603-1-51355-881-8
Downloads: 28406
Price: Free* [*Free Regsitration Required]
Uploader: Mazubei

F I G U R E 2

Such a body carries 1 or 2 length fields; B1 is [part of] the first length field. The previous occurrence shall be the 78116-5 record with the specified identifier but in a smaller logical position than the current record. According to its abstract, it specifies the operating conditions of an integrated circuit card that provides a USB interface.

Each command message may carry a response descriptor template fixing the data objects required in response.

If L is not null, then the value field V consists of L consecutive bytes. For example, the last possible position of a template for cryptographic checksum is just before the first data object integrated in the computation.

ISO – important industry standard for integrated circuit cards

Alternately, using secret internal data, the card computes a data element cryptographic checksum or digital signature and inserts it in the data is to the outside world. An algorithm, a key and, possibly initial data may be selected for each security mechanism implicitly, i.


The length Le is null; therefore the Le field is empty. The response descriptor template, if present in the data ido of the command APDU, shall fix the structure of the corresponding response. Created inupdated in Between those two identifiers, the path consists of the identifiers of the successive parent DFs if any.

Organization, security and commands for 8716-5. An application protocol data unit APDU contains either a command message or a response message, sent from the interface device to the card or conversely.

When a file cannot be implicitly selected, it shall be possible to select it by at least one of the following methods:. It codes no class and no construction-type. The following additional rule is defined for linear structures and for cyclic structures: Consequently, the body consists of the Lc field followed by the data field.

Data objects for confidentiality are intended for carrying a cryptogram which plain value consists of one of the following 3 cases: The security attributes of file depend on:. Transparent structure — The EF is seen at the interface as io sequence of data units. Referencing by file identifier — Any file may be referenced by a file identifier coded on 2 bytes.

ISO/IEC – Wikipedia

isso If the concept of logical channels is applied, the file specify security status may is on the logical channel see 1. In order to iiso unambiguously any file by its identifier, all EFs and DFs immediately under a given DF shall have different 78166-5 identifiers.


This application contains information on cryptographic functionality. You may experience issues viewing this site in Internet Explorer 9, 10 or The logical organization of data in a card consists of following structural hierachy of dedicated files:. This page was last edited on 19 Aprilat The computation of a cryptographic checksum is performed in the following consecutive stages: Registration of application providers Status: That is, command interdependencies on one logical channel shall be independent of command interdependencies on another logical channel.

In this case, the card computes a string of concealing bytes and adds it by exclusive-or to data bytes received from or sent to the outside world. The card shall support at least one of the following four methods for structuring EFs: The following additional rules are defined for linear structures and for cyclic structures: The order of the file identifiers is always in the direction parent to child.

The previous occurrence shall be equvalent to the last occurrence. Each data field shall have one of the following three structures.