BS ISO IEC 27009-2016 Information technology Security techniques Sector-specific application of ISO IEC 27001 Requirements《信息技术 安全技术 ISO IEC 27001特定行业应用程序 要求》.pdf

1、BS ISO/IEC 27009:2016 Information technology Security techniques Sector- specific application of ISO/IEC 27001 Requirements BSI Standards Publication WB11885_BSI_StandardCovs_2013_AW.indd 1 15/05/2013 15:06BS ISO/IEC 27009:2016 BRITISH STANDARD National foreword This British Standard is the UK imple

2、mentation of ISO/IEC 27009:2016. The UK participation in its preparation was entrusted to Technical Committee IST/33/1, Information Security Management Systems. A list of organizations represented on this committee can be obtained on request to its secretary. This publication does not purport to inc

3、lude all the necessary provisions of a contract. Users are responsible for its correct application. The British Standards Institution 2016. Published by BSI Standards Limited 2016 ISBN 978 0 580 83471 4 ICS 03.120.20; 35.040 Compliance with a British Standard cannot confer immunity from legal obliga

4、tions. This British Standard was published under the authority of the Standards Policy and Strategy Committee on 30 June 2016. Amendments/corrigenda issued since publication Date T e x t a f f e c t e dBS ISO/IEC 27009:2016 Information technology Security techniques Sector-specific application of IS

5、O/IEC 27001 Requirements Technologies de linformation Techniques de scurit Application de lISO/IEC 27001 un secteur spcifique Exigences INTERNATIONAL STANDARD ISO/IEC 27009 Reference number ISO/IEC 27009:2016(E) First edition 2016-06-15 ISO/IEC 2016 BS ISO/IEC 27009:2016ii ISO/IEC 2016 All rights re

6、served COPYRIGHT PROTECTED DOCUMENT 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

7、 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 22 749 09 47 copyri

8、ghtiso.org www.iso.org ISO/IEC 27009:2016(E)BS ISO/IEC 27009:2016ISO/IEC 27009:2016(E)Foreword iv 1 Scope . 1 2 Normative references 1 3 Terms and definitions . 1 4 Overview of this International Standard . 1 4.1 General . 1 4.2 Structure of this International Standard 2 4.3 Expanding ISO/IEC 27001

9、requirements or ISO/IEC 27002 controls . . 3 5 Additional, refined or interpreted ISO/IEC 27001 requirements . 3 5.1 General . 3 5.2 Additional requirements 3 5.3 Refined requirements . 4 5.4 Interpreted requirements . 4 6 Additional or modified ISO/IEC 27002 guidance . 4 6.1 General . 4 6.2 Additio

10、nal guidance 4 6.3 Modified guidance 5 Annex A (normative) Template for developing sector-specific standards related to ISO/ IEC 27001:2013 or ISO/IEC 27002:2013 . 6 Bibliography 9 ISO/IEC 2016 All rights reserved iii Contents PageBS ISO/IEC 27009:2016ISO/IEC 27009:2016(E) Foreword ISO (the Internat

11、ional 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

12、 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

13、 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 t

14、he 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 a

15、nd 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

16、 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 ISOs adherence to the WTO principles in the Technical Barriers to

17、 Trade (TBT) see the following URL: Foreword - Supplementary information The committee responsible for this document is ISO/IEC JTC 1, Information technology, SC 27, IT Security techniques.iv ISO/IEC 2016 All rights reservedBS ISO/IEC 27009:2016INTERNATIONAL ST ANDARD ISO/IEC 27009:2016(E) Informati

18、on technology Security techniques Sector- specific application of ISO/IEC 27001 Requirements 1 Scope This International Standard defines the requirements for the use of ISO/IEC 27001 in any specific sector (field, application area or market sector). It explains how to include requirements additional

19、 to those in ISO/IEC 27001, how to refine any of the ISO/IEC 27001 requirements, and how to include controls or control sets in addition to ISO/IEC 27001:2013, Annex A. This International Standard ensures that additional or refined requirements are not in conflict with the requirements in ISO/IEC 27

20、001. This International Standard is applicable to those involved in producing sector-specific standards that relate to ISO/IEC 27001. 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

21、references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies. ISO/IEC 27000:2016, Information technology Security techniques Information security management systems Overview and vocabulary ISO/IEC 27001:2013, Inf

22、ormation technology Security techniques Information security management systems Requirements ISO/IEC 27002:2013, Information technology Security techniques Code of practice for information security controls 3 Terms and definitions For the purposes of this document, the terms and definitions given in

23、 ISO/IEC 27000 and the following apply. 3.1 interpretation explanation (in form of requirement or guidance) of an ISO/IEC 27001 requirement in a sector-specific context which does not invalidate any of the ISO/IEC 27001 requirements 3.2 refinement sector-specific specification of an ISO/IEC 27001 re

24、quirement which does not remove or invalidate any of the ISO/IEC 27001 requirements 4 Overview of this International Standard 4.1 General ISO/IEC 27001 is an International Standard that defines the requirements for establishing, implementing, maintaining and continually improving an information secu

25、rity management system. ISO/IEC 2016 All rights reserved 1BS ISO/IEC 27009:2016ISO/IEC 27009:2016(E) It states that its requirements are generic and are intended to be applicable to all organizations, regardless of type, size or nature. NOTE Management system standards within ISO are built in accord

26、ance with ISO/IEC Directives, Part 1, Consolidated ISO Supplement, 2016. 1 ISO/IEC 27002 is an International Standard that provides guidelines for information security management practices including the selection, implementation and management of controls taking into consideration the organizations

27、information security risk environment. The guidelines have a hierarchical structure that consists of clauses, control objectives, controls, implementation guidance and other information. The guidelines of ISO/IEC 27002 are generic and are intended to be applicable to all organizations, regardless of

28、 type, size or nature. The control objective and controls of ISO/IEC 27002 are listed in Annex A of ISO/IEC 27001:2013 in a normative form. ISO/IEC 27001:2013 requires an organization to “determine all controls that are necessary to implement the information security risk treatment option(s) chosen

29、(see 6.1.3 b)”, and “compare the controls determined in 6.1.3 b) above with those in Annex A and verify that no necessary controls have been omitted (see 6.1.3 c)”. While ISO/IEC 27001 and ISO/IEC 27002 are widely accepted in organizations, including commercial enterprises, government agencies and n

30、ot-for-profit organizations, there are emerging needs for sector- specific versions of these standards. Examples of standards which have been developed to address these sector-specific needs are: ISO/IEC 27010, 2Information security management for inter-sector and inter-organizational communications

31、; ISO/IEC 27011, 3Information security management guidelines for telecommunications organizations based on ISO/IEC 27002; ISO/IEC 27017, 4Code of practice for information security controls based on ISO/IEC 27002 for cloud services; and ISO/IEC 27018, 5Code of practice for protection of personally id

32、entifiable information (PII) in public clouds acting as PII processors. Organizations outside of ISO/IEC have also produced standards addressing sector-specific needs. Sector-specific standards should be consistent with the requirements of the information security management system. This Internation

33、al Standard provides requirements for how to add to, refine or interpret the requirements of ISO/IEC 27001 and how to add or modify the guidelines of ISO/IEC 27002 for sector-specific use. This International Standard assumes that all requirements from ISO/IEC 27001 that are not refined or interprete

34、d, and all controls in ISO/IEC 27002 that are not modified, will apply in the sector-specific context unchanged. 4.2 Structure of this International Standard Clause 5 provides requirements and guidance on how to define requirements that are additional to, refinement or interpretation of ISO/IEC 2700

35、1 requirements. Clause 6 provides requirements and guidance on how to provide control objectives, controls, implementation guidance or other information that are additional to or modify ISO/IEC 27002 content. Annex A contains a template which should be used for sector-specific standards related to I

36、SO/IEC 27001 and/or ISO/IEC 27002. Within this International Standard, the following concepts are used to adapt ISO/IEC 27001 requirements for a sector: Addition see 5.22 ISO/IEC 2016 All rights reservedBS ISO/IEC 27009:2016ISO/IEC 27009:2016(E) Refinement see 5.3 Interpretation see 5.4. Within this

37、 International Standard, the following concepts are used to adapt ISO/IEC 27002 guidance for a sector: Addition see 6.2 Modification see 6.3. NOTE Any sector-specific guidance that is developed following the requirements and guidance in this International Standard cannot be contained within a Techni

38、cal Report. The ISO/IEC Directives 1define a Technical Report as a document that does not contain requirements, and any sector-specific standard developed based on this International Standard, particularly Annex A, will contain at least a minimum set of requirements (see clause 4.1 of the template i

39、n A.2). 4.3 Expanding ISO/IEC 27001 requirements or ISO/IEC 27002 controls Sector-specific standards related to ISO/IEC 27001 may add requirements or guidance to those of ISO/IEC 27001 or ISO/IEC 27002. The addition may expand the requirements or guidance beyond information security into their secto

40、r-specific topic. EXAMPLE ISO/IEC 27018, Code of practice for protection of personally identifiable information (PII) in public clouds acting as PII processors uses such expansions. ISO/IEC 27018:2014, Annex A 5contains a set of controls aimed at the protection of personally identifiable information

41、 and, therefore, expands the scope of ISO/IEC 27018 5to cover PII protection in addition to information security. 5 Additional, refined or interpreted ISO/IEC 27001 requirements 5.1 General Figure 1 illustrates how sector-specific requirements are constructed in relationship to ISO/IEC 27001. Figure

42、 1 Construction of sector-specific requirements 5.2 Additional requirements Specification of additional requirements is permitted. EXAMPLE A sector which has additional requirements for an information security policy can add them to the requirements for the policy specified in ISO/IEC 27001:2013, 5.

43、2. No requirement that is added to those in ISO/IEC 27001 shall remove or invalidate any of the requirements defined in ISO/IEC 27001. Sector-specific additions to ISO/IEC 27001 requirements shall, where possible, follow the requirements and guidance set out in Annex A of this International Standard

44、. ISO/IEC 2016 All rights reserved 3BS ISO/IEC 27009:2016ISO/IEC 27009:2016(E) 5.3 Refined requirements Refinement of ISO/IEC 27001 requirements is permitted. NOTE Refinements do not remove or invalidate any of the requirements in ISO/IEC 27001 (see 3.2). Sector-specific refinements of ISO/IEC 27001

45、 requirements shall, where possible, follow the requirements and guidance set out in Annex A of this International Standard. EXAMPLE 1 A sector-specific standard could contain controls additional to ISO/IEC 27001:2013, Annex A. In this case, the requirements related to information security risk trea

46、tment in ISO/IEC 27001:2013, 6.1.3 c) and d) need to be refined to include the additional controls given in the sector-specific standard. Specification of a particular approach to meeting requirements in ISO/IEC 27001 is also permitted. EXAMPLE 2 A particular sector has a prescribed way to determine

47、 the competence of people working within the scope of the sectors-specific management system. This requirement could refine the general requirement in ISO/IEC 27001:2013, 7.2. 5.4 Interpreted requirements Interpretation of ISO/IEC 27001 requirements is permitted. NOTE Interpretations do not invalida

48、te any of the ISO/IEC 27001 requirements but explain them or place them into sector-specific context (see 3.1). Sector-specific interpretations of ISO/IEC 27001 requirements shall, where possible, follow the requirements and guidance set out in Annex A of this International Standard. 6 Additional or

49、 modified ISO/IEC 27002 guidance 6.1 General Figure 2 illustrates how ISO/IEC 27002 guidance can be added to or modified. Figure 2 Construction of sector-specific guidance Each control shall only contain one instance of the word “should”. NOTE In ISO/IEC 27001:2013, Information security risk treatment requires an organization to state controls that have been determined and justification of inclusions, and justification for ex