ISO 13492-2007 Financial services - Key management related data element - Application and usage of ISO 8583 data elements 53 and 96《金融服务 数据元的密钥管理 ISO 8583数据元53和.pdf

《ISO 13492-2007 Financial services - Key management related data element - Application and usage of ISO 8583 data elements 53 and 96《金融服务 数据元的密钥管理 ISO 8583数据元53和.pdf》由会员分享，可在线阅读，更多相关《ISO 13492-2007 Financial services - Key management related data element - Application and usage of ISO 8583 data elements 53 and 96《金融服务 数据元的密钥管理 ISO 8583数据元53和.pdf（18页珍藏版）》请在麦多课文档分享上搜索。

1、 Reference number ISO 13492:2007(E) ISO 2007INTERNATIONAL STANDARD ISO 13492 Second edition 2007-12-15 Financial services Key management related data element Application and usage of ISO 8583 data elements 53 and 96 Services financiers lment de donnes li la gestion des cls Application et utilisation

2、 des lments de donnes 53 et 96 de lISO 8583ISO 13492:2007(E) PDF disclaimer This PDF file may contain embedded typefaces. In accordance with Adobes licensing policy, this file may be printed or viewed but shall not be edited unless the typefaces which are embedded are licensed to and installed on th

3、e computer performing the editing. In downloading this file, parties accept therein the responsibility of not infringing Adobes licensing policy. The ISO Central Secretariat accepts no liability in this area. Adobe is a trademark of Adobe Systems Incorporated. Details of the software products used t

4、o create this PDF file can be found in the General Info relative to the file; the PDF-creation parameters were optimized for printing. Every care has been taken to ensure that the file is suitable for use by ISO member bodies. In the unlikely event that a problem relating to it is found, please info

5、rm the Central Secretariat at the address given below. COPYRIGHT PROTECTED DOCUMENT ISO 2007 All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without

6、 permission in writing from either ISO at the address below or ISOs member body in the country of the requester. ISO copyright office Case postale 56 CH-1211 Geneva 20 Tel. + 41 22 749 01 11 Fax + 41 22 749 09 47 E-mail copyrightiso.org Web www.iso.org Published in Switzerland ii ISO 2007 All rights

7、 reservedISO 13492:2007(E) ISO 2007 All rights reserved iiiContents Page Foreword iv Introduction.v 1 Scope1 2 Normative references1 3 Terms and definitions .1 4 Abbreviated terms .2 5 Data representation.3 6 Requirements for key management related data element 4 6.1 Introduction4 6.2 Data element s

8、tructure4 6.3 Key-set identifier concepts.5 7 Security related control information usage (data element 53) .5 7.1 Format.5 7.2 Assignment of key-set identifiers9 8 Key management data (data element 96)9 Bibliography10 ISO 13492:2007(E) iv ISO 2007 All rights reservedForeword ISO (the International O

9、rganization for Standardization) is a worldwide federation of national standards bodies (ISO member bodies). The work of preparing International Standards is normally carried out through ISO technical committees. Each member body interested in a subject for which a technical committee has been estab

10、lished has the right to be represented on that committee. International organizations, governmental and non-governmental, in liaison with ISO, also take part in the work. ISO collaborates closely with the International Electrotechnical Commission (IEC) on all matters of electrotechnical standardizat

11、ion. International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 2. The main task of technical committees is to prepare International Standards. Draft International Standards adopted by the technical committees are circulated to the member bodies for voting

12、. Publication as an International Standard requires approval by at least 75 % of the member bodies casting a vote. Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights. ISO shall not be held responsible for identifying any or all such p

13、atent rights. ISO 13492 was prepared by Technical Committee ISO/TC 68, Financial services, Subcommittee SC 2, Security management and general banking operations. This second edition cancels and replaces the first edition (ISO 13492:1998), which has been technically revised. ISO 13492:2007(E) ISO 200

14、7 All rights reserved vIntroduction This International Standard describes the structure and contents of a key management related data element that can be conveyed in electronically transmitted messages within the financial services environment to support the secure management of cryptographic keys,

15、where the financial services environment involves the communications between a card-accepting device and an acquirer, and between an acquirer and a card issuer. Key management of keys used in an Integrated Circuit Card (ICC) and the related data elements are not covered in this International Standar

16、d. This International Standard provides compatibility with the existing ISO standard on bank card originated messages (see ISO 8583). INTERNATIONAL STANDARD ISO 13492:2007(E) ISO 2007 All rights reserved 1Financial services Key management related data element Application and usage of ISO 8583 data e

17、lements 53 and 96 1 Scope This International Standard describes a key management related data element that can be transmitted either in transaction messages to convey information about cryptographic keys used to secure the current transaction, or in cryptographic service messages to convey informati

18、on about cryptographic keys to be used to secure future transactions. This International Standard addresses the requirements for the use of the key management related data element within ISO 8583, using the following two ISO 8583 data elements: security related control information (data element 53),

19、 or key management data (data element 96). However, these data elements can be usefully employed in other messaging formats, given that the transportation of key management related data is not limited to ISO 8583. This International Standard is applicable to either symmetric or asymmetric cipher sys

20、tems. Key management procedures for the secure management of the cryptographic keys within the financial services environment are described in ISO 11568. Security related data, such as PIN data and MACs, are described in ISO 9564 and ISO 16609, respectively. 2 Normative references The following refe

21、renced documents are indispensable for the application of this document. For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies. ISO/IEC 7812-1, Identification cards Identification of issuers Part

22、 1: Numbering system ISO/IEC 7812-2, Identification cards Identification of issuers Part 2: Application and registration procedures ISO 8583-1, Financial transaction card originated messages Interchange message specifications Part 1: Messages, data elements and code values 3 Terms and definitions Fo

23、r the purposes of this document, the terms and definitions given in ISO 8583-1 and the following apply. 3.1 asymmetric cipher cipher in which the encipherment key and the decipherment key are different and it is computationally infeasible to deduce the (private) decipherment key from the (public) en

24、cipherment key ISO 13492:2007(E) 2 ISO 2007 All rights reserved3.2 cipher pair of operations that effect transformations between plaintext and ciphertext under the control of a parameter called a key NOTE The encipherment operation transforms data (plaintext) into an unintelligible form (ciphertext)

25、. The decipherment operation restores the original text. 3.3 cryptographic algorithm set of rules for the transformation of data using a cryptographic key EXAMPLE The transformation of plaintext to ciphertext and vice versa (i.e. a cipher); generation of keying material; digital signature computatio

26、n or validation. 3.4 cryptographic key key parameter that determines the operation of a cryptographic algorithm 3.5 cryptographic service message message for transporting cryptographic keys or related information used to control a keying relationship 3.6 derived unique key per transaction key manage

27、ment method which uses a unique key for each transaction and prevents the disclosure of any past key used by the transaction-originating TRSM NOTE The unique Transaction Keys are derived from a base derivation key using only non-secret data transmitted as part of each transaction. 3.7 primary key ke

28、y for a transaction from which other keys for the transaction are produced NOTE This can be done by means of variants or transformations. 3.8 symmetric cipher cryptographic algorithm using the same secret cryptographic key for both encipherment and decipherment 3.9 transaction message message used t

29、o convey information related to a financial transaction 4 Abbreviated terms AES Advanced Encryption Standard BCD Binary Coded Decimal CAID Card Acceptor Identifier CBC Cipher Block Chaining DEA Data Encryption Algorithm ISO 13492:2007(E) ISO 2007 All rights reserved 3DID Device Identifier DUKPT Deri

30、ved Unique Key per Transaction ECB Electronic Code Book ECIES Elliptic Curve Integrated Encryption Scheme GID Group Identifier IIC Institution Identification Code IIN Issuer Identification Number KSN Key Serial Number MAC Message Authentication Code PIN Personal Identification Number RSA The Rivest,

31、 Shamir and Adleman Public Key Cryptosystem TC Transaction Counter TDEA Triple Data Encryption Algorithm TRSM Tamper Resistant Security Module 5 Data representation Data fields described in this International Standard are represented as shown in Table 1. Table 1 Data representation Abbreviation Defi

32、nition a Alphabetic data elements contain a single character per byte. The permitted characters are alphabetic only (a to z and A to Z, upper and lower case). an Alphanumeric data elements contain a single character per byte. The permitted characters are alphabetic (a to z and A to Z, upper and lowe

33、rcase) and numeric (0 to 9). ans Alphanumeric special data elements contain a single character per byte. b These data elements consist of either unsigned binary numbers or bit combinations that are defined elsewhere in the specification. Example: a field defined as “b 2” has a length of two bytes su

34、ch that a value of 19 is stored as Hex 00 13. LL Length of variable data element that follows, 01 through 99. LLL Length of variable data element that follows, 001 through 999. n Numeric data elements consist of two numeric digits (having values in the range Hex 0 9) per byte. These digits are right

35、 justified and padded with leading hexadecimal zeroes. Other specifications sometimes refer to this data format as Binary Coded Decimal (“BCD”) or unsigned packed. Example: a field defined as “n 12” has a length of six bytes such that a value of 12345 is stored as Hex 00 00 00 01 23 45. ISO 13492:20

36、07(E) 4 ISO 2007 All rights reserved6 Requirements for key management related data element 6.1 Introduction The key management related data element is constructed from the concatenation of two ISO 8583-1 message elements, data element 53 Security related control information, and data element 96 Key

37、management data. It conveys information about the associated transactions cryptographic key(s) and is divided into subfields including a control field, a key-set identifier and additional optional information. The control field identifies the key management scheme and associated structure of the rem

38、ainder of the data element. The use of key-set identifiers provides a standardized way to uniquely identify the institution and key- set for a given operation. For key management messages, the key-set identifier specifies the key-set that will be affected by the current operation (e.g. load key-set

39、2 with key contained in data element 96). For financial transaction messages containing encrypted data, the key-set identifier specifies the key-set that was used. Key management related information that does not change from one transaction to the next need not be conveyed with every transaction. Ra

40、ther, it may be implicitly known, or it may be installed concurrent with, and stored in association with, the corresponding key. Examples of information that need not be explicitly identified in the key management related data element include the following: key management technique used for the tran

41、sactions keys (e.g. static key, unique key per transaction); format of enciphered or authenticated data (e.g. PIN block format); encipherment algorithm used; number of different keys used with the transaction and the purpose of each such key. 6.2 Data element structure The key management related dat

42、a element has two possible forms, as illustrated in Figure 1: Form 1, e.g. key change see Figure 1 a); Form 2, e.g. key selection see Figure 1 b). Data element 53 Data element 96 LL Security related control information LLL Key Management data a) Form 1 Data element 53 LL Security related control inf

43、ormation b) Form 2 Figure 1 Possible forms of data element structure In the construction in Figure 1 a), data element 53 is used to convey control information for the key data contained in data element 96. In the construction in Figure 1 b), data element 53 is used to convey selection information re

44、garding the keys used to protect the current financial transaction message (of which this data element forms a part). ISO 13492:2007(E) ISO 2007 All rights reserved 56.3 Key-set identifier concepts A key-set identifier is a number that uniquely identifies a key-set, where a key-set is a group of rel

45、ated keys that are all different but have certain characteristics in common, most notably those listed below. All are managed using the same key management method. The same high level key is used to encipher (for database storage) or derive all keys of the set. The remainder of the key management re

46、lated data element (beyond the key-set identifier) is identically structured for all keys of the set, and is interpreted using the same logic. Associated with any given key-set is logic (e.g. computer software) at the acquiring host that may interpret the key management related data element to deter

47、mine what key(s) is (are) to be used with that transaction, and how each such key is to be used. 7 Security related control information usage (data element 53) 7.1 Format 7.1.1 General Data Element 53 is used to indicate which of the possible key-sets are to be used or affected by the key management

48、 message. As an option, this field may also include information concerning the algorithm and mode of operation used in the encryption of the associated key management data field. The defined values for these subfields are shown in the following tables. The construction of this data element is depend

49、ant upon the key management scheme in which the data element is used. Two formats are illustrated: in Table 2, format A as used for fixed and master/session key, and in Table 3, format B for Derived Unique Key Per Transaction (DUKPT) key management scheme, as defined in ANSI X9.24-1. ISO 13492:2007(E) 6 ISO 2007 All rights reservedTable 2 Data element 53 Structure format A Length bytes Field name Description Encoding Required 1 Control Identifies the key man