BS ISO IEC 24759-2017 Information technology Security techniques Test requirements for cryptographic modules《信息技术 安全技术 密码模块试验要求》.pdf

《BS ISO IEC 24759-2017 Information technology Security techniques Test requirements for cryptographic modules《信息技术 安全技术 密码模块试验要求》.pdf》由会员分享，可在线阅读，更多相关《BS ISO IEC 24759-2017 Information technology Security techniques Test requirements for cryptographic modules《信息技术 安全技术 密码模块试验要求》.pdf（146页珍藏版）》请在麦多课文档分享上搜索。

1、Information technology Security techniques Test requirements for cryptographic modules BS ISO/IEC 24759:2017 BSI Standards Publication WB11885_BSI_StandardCovs_2013_AW.indd 1 15/05/2013 15:06Information technology Security techniques Test requirements for cryptographic modules Technologies de linfor

2、mation Techniques de scurit Exigences dessai pour modules cryptographiques INTERNATIONAL STANDARD ISO/IEC 24759 Reference number ISO/IEC 24759:2017(E) Third edition 2017-03 ISO/IEC 2017 National foreword This British Standard is the UK implementation of ISO/IEC 24759:2017. It supersedes BS ISO/IEC 2

3、4759:2014 which is withdrawn. The UK participation in its preparation was entrusted by Technical Committee IST/33, IT - Security techniques, to Subcommittee IST/33/3, Security Evaluation, Testing and Specification. A list of organizations represented on this committee can be obtained on request to i

4、ts secretary. This publication does not purport to include all the necessary provisions of a contract. Users are responsible for its correct application. The British Standards Institution 2017 Published by BSI Standards Limited 2017 ISBN 978 0 580 96250 9 ICS 35.030 Compliance with a British Standar

5、d cannot confer immunity from legal obligations. This British Standard was published under the authority of the Standards Policy and Strategy Committee on 30 June 2017. Amendments/corrigenda issued since publication Date Text affected BRITISH STANDARD BS ISO/IEC 24759:2017Information technology Secu

6、rity techniques Test requirements for cryptographic modules Technologies de linformation Techniques de scurit Exigences dessai pour modules cryptographiques INTERNATIONAL STANDARD ISO/IEC 24759 Reference number ISO/IEC 24759:2017(E) Third edition 2017-03 ISO/IEC 2017 BS ISO/IEC 24759:2017 ii ISO/IEC

7、 2017 All rights reserved COPYRIGHT PROTECTED DOCUMENT ISO/IEC 2017, 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

8、 on the internet or an intranet, without prior written permission. Permission can be requested from either ISO at the address below or ISOs 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

9、22 749 09 47 copyrightiso.org www.iso.org ISO/IEC 24759:2017(E) BS ISO/IEC 24759:2017 ii ISO/IEC 2017 All rights reserved COPYRIGHT PROTECTED DOCUMENT ISO/IEC 2017, Published in Switzerland All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized oth

10、erwise 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 ISOs member body in the country of the requester. ISO copyright offic

11、e Ch. de Blandonnet 8 CP 401 CH-1214 Vernier, Geneva, Switzerland Tel. +41 22 749 01 11 Fax +41 22 749 09 47 copyrightiso.org www.iso.org ISO/IEC 24759:2017(E)ISO/IEC 24759:2017(E)Foreword v 1 Scope . 1 2 Normative references 1 3 T erms and definitions . 1 4 Symbols and abbreviated terms . 1 5 Docum

12、ent organization . 1 5.1 General . 1 5.2 Assertions and security requirements . 2 6 Security requirements 2 6.1 General . 2 6.2 Cryptographic module specification 3 6.2.1 Cryptographic module specification general requirements . 3 6.2.2 Types of cryptographic modules 3 6.2.3 Cryptographic boundary .

13、 5 6.2.4 Modes of operations 13 6.3 Cryptographic module interfaces 17 6.3.1 Cryptographic module interfaces general requirements .17 6.3.2 Types of interfaces 20 6.3.3 Definition of interfaces 20 6.3.4 Trusted channel .30 6.4 Roles, services, and authentication 32 6.4.1 Roles, services, and authent

14、ication general requirements 32 6.4.2 Roles 33 6.4.3 Services .34 6.4.4 Authentication 42 6.5 Software/Firmware security .49 6.6 Operational environment .57 6.6.1 Operational environment general requirements 57 6.6.2 Operating system requirements for limited or non-modifiable operational environment

15、s 57 6.6.3 Operating system requirements for modifiable operational environments .58 6.7 Physical security .68 6.7.1 Physical security embodiments .68 6.7.2 Physical security general requirements .69 6.7.3 Physical security requirements for each physical security embodiment 75 6.7.4 Environmental fa

16、ilure protection/testing 86 6.8 Non-invasive security .89 6.9 Sensitive security parameter management .91 6.9.1 Sensitive security parameter management general requirements .91 6.9.2 Random bit generators 92 6.9.3 Sensitive security parameter generation .93 6.9.4 Sensitive security parameter establi

17、shment 94 6.9.5 Sensitive security parameter entry and output .94 6.9.6 Sensitive security parameter storage .98 6.9.7 Sensitive security parameter zeroisation 99 6.10 Self-tests .102 6.10.1 Self-test general requirements 102 6.10.2 Pre-operational self-tests .105 6.10.3 Conditional self-tests109 6.

18、11 Life-cycle assurance 119 6.11.1 Life-cycle assurance general requirements 119 6.11.2 Configuration management 119 ISO/IEC 2017 All rights reserved iii Contents Page BS ISO/IEC 24759:2017 ISO/IEC 24759:2017(E)6.11.3 Design 121 6.11.4 Finite state model121 6.11.5 Development .125 6.11.6 Vendor test

19、ing 129 6.11.7 Delivery and operation .130 6.11.8 End of life 131 6.11.9 Guidance documents 132 6.12 Mitigation of other attacks 133 6.13 Documentation requirements134 6.14 Cryptographic module security policy .134 6.15 Approved security functions .135 6.16 Approved sensitive security parameter gene

20、ration and establishment methods 135 6.17 Approved authentication mechanisms 135 6.18 Approved non-invasive attack mitigation test metrics 135 iv ISO/IEC 2017 All rights reserved BS ISO/IEC 24759:2017 ISO/IEC 24759:2017(E)6.11.3 Design 121 6.11.4 Finite state model121 6.11.5 Development .125 6.11.6

21、Vendor testing 129 6.11.7 Delivery and operation .130 6.11.8 End of life 131 6.11.9 Guidance documents 132 6.12 Mitigation of other attacks 133 6.13 Documentation requirements134 6.14 Cryptographic module security policy .134 6.15 Approved security functions .135 6.16 Approved sensitive security par

22、ameter generation and establishment methods 135 6.17 Approved authentication mechanisms 135 6.18 Approved non-invasive attack mitigation test metrics 135 iv ISO/IEC 2017 All rights reserved ISO/IEC 24759:2017(E) Foreword ISO (the International Organization for Standardization) and IEC (the Internati

23、onal 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

24、 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 joi

25、nt 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 ISO documents should be noted. This docu

26、ment 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 shall not be held responsible for identifying any or al

27、l 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

28、 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 ISOs adherence to the World Trade Organization (WTO) principles in the Technical Barriers

29、 to Trade (TBT) see the following URL: www .iso .org/ iso/ foreword .html. This document was prepared by ISO/IEC JTC 1, Information technology, Subcommittee SC 27, IT Security techniques. This third edition cancels and replaces the second edition (ISO/IEC 24759:2014), of which it constitutes a minor

30、 revision. It also incorporates the Technical Corrigendum ISO/IEC 24759:2014/Cor.1:2015. The main changes compared to the previous edition (plus other minor editorial modifications) are as follows: References to ISO/IEC 19790:2012 have been corrected throughout: 6.2.3.2: AS02.15, AS02.16, AS02.17 an

31、d AS02.18 modified; 6.3.3: AS03.04, AS03.07, AS03.10 and AS03.15 modified; 6.3.4: AS03.19 modified; 6.4.1: AS04.02 modified; 6.4.2; AS04.05, AS04.06 and AS04.07 modified; 6.4.3.1: AS04.11, AS04.13 and AS04.14; 6.4.3.2 and AS04.20; 6.4.4: AS04.39, AS04.40 and AS04.42 modified; 6.5: AS05.05, AS05.06,

32、AS05.07, AS05.08, AS05.13, AS05.17 and AS05.18 modified; 6.8: AS08.04 modified; 6.10.1: AS10.17 modified. ISO/IEC 2017 All rights reserved v BS ISO/IEC 24759:2017 ISO/IEC 24759:2017(E)vi ISO/IEC 2017 All rights reserved BS ISO/IEC 24759:2017 ISO/IEC 24759:2017(E)vi ISO/IEC 2017 All rights reserved I

33、nformation technology Security techniques Test requirements for cryptographic modules 1 Scope This document specifies the methods to be used by testing laboratories to test whether the cryptographic module conforms to the requirements specified in ISO/IEC 19790:2012. The methods are developed to pro

34、vide a high degree of objectivity during the testing process and to ensure consistency across the testing laboratories. This document also specifies the requirements for information that vendors provide to testing laboratories as supporting evidence to demonstrate their cryptographic modules conform

35、ity to the requirements specified in ISO/IEC 19790:2012. Vendors can use this document as guidance in trying to verify whether their cryptographic modules satisfy the requirements specified in ISO/IEC 19790:2012 before they apply to the testing laboratory for testing. 2 Normative references The foll

36、owing documents are referred to in the text in such a way that some or all of their content constitutes requirements 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/I

37、EC 19790:2012, Information technology Security techniques Security requirements for cryptographic modules 3 T erms an d definiti ons For the purposes of this document, the terms and definitions given in ISO/IEC 19790:2012 apply. ISO and IEC maintain terminological databases for use in standardizatio

38、n at the following addresses: IEC Electropedia: available at h t t p :/ www .electropedia .org/ ISO Online browsing platform: available at h t t p :/ www .iso .org/ obp 4 Symbols and abbreviated terms For the purposes of this document, the symbols and abbreviated terms given in ISO/IEC 19790:2012 ap

39、ply. 5 Document organization 5.1 General Clause 6 specifies the methods that shall be used by testing laboratories and the requirements for information that vendors shall provide to testing laboratories. Clause 6, besides a general subclause, 6.1, includes eleven subclauses corresponding to the elev

40、en areas of security requirements and six subclauses corresponding to the six annexes, Annex A to Annex F, of ISO/IEC 19790:2012. INTERNATIONAL ST ANDARD ISO/IEC 24759:2017(E) ISO/IEC 2017 All rights reserved 1 BS ISO/IEC 24759:2017 ISO/IEC 24759:2017(E) 5.2 Assertions and security requirements With

41、in each subclause, the corresponding security requirements from ISO/IEC 19790:2012 are divided into a set of assertions (i.e. statements that have to be true for the module to satisfy the requirement of a given area at a given level). All of the assertions are direct quotations from ISO/IEC 19790:20

42、12. The assertions are denoted by the form AS. where “requirement_number” is the number of the corresponding area specified in ISO/IEC 19790:2012 (i.e. one to twelve and A to F), and “sequence_number” is a sequential identifier for assertions within a subclause. After the statement of each assertion

43、, the security levels to which the assertion applies (i.e. levels 1 to 4) are listed in parentheses. Following each assertion is a set of requirements levied on the vendor. These requirements describe the types of documentation or explicit information that the vendor shall provide in order for the t

44、ester to verify conformity to the given assertion. These requirements are denoted by the form VE where “requirement_number” and “assertion_sequence_number” are identical to the corresponding assertion requirement number and sequence number, and “sequence_number” is a sequential identifier for vendor

45、 requirements within the assertion requirement. Also following each assertion and the requirements levied on the vendor is a set of requirements levied on the tester of the cryptographic module. These requirements instruct the tester as to what he or she shall do in order to test the cryptographic m

46、odule with respect to the given assertion. These requirements are denoted by the form TE where “requirement_number” and “assertion_sequence_number” are identical to the corresponding assertion requirement number and sequence number, and “sequence_number” is a sequential identifier for tester require

47、ments within the assertion requirement. A validation authority may modify, add, or delete VEs and/or TEs in this document. 5.3 Assertions with cross references For clarity in some assertions, cross references to ISO/IEC 19790:2012 or other assertions numbers have been put between curly brackets “ an

48、d ”. Those cross references are written in italics. 6 Security requirements 6.1 General NOTE 6.1 states general requirements to meet the assertions of the other subclauses in Clause 6, and ISO/IEC 19790:2012, Annex A to Annex F. 6.1 sets no assertion of itself and is not separately tested. AS01.01:

49、(General Levels 1, 2, 3, and 4) T his cla u s e s p e c i f ie s t he s e c u r it y r e qu i r e me nt s t h at shall be sa t isf i ed by t he c r y p t o g r aph ic modules compliance to ISO/IEC 19790:2012. AS01.02: (General Levels 1, 2, 3, and 4) A cryptographic module shall be tested against the requirements of each area addressed in this clause. NOTE The tests can be performed in one or more of the following manners.2 ISO/IEC 2017 All rights reserved BS I