ETSI GS NFV-SEC 014-2018 Network Functions Virtualisation (NFV) Release 3 NFV Security Security Specification for MANO Components and Reference points (V3 1 1).pdf

《ETSI GS NFV-SEC 014-2018 Network Functions Virtualisation (NFV) Release 3 NFV Security Security Specification for MANO Components and Reference points (V3 1 1).pdf》由会员分享，可在线阅读，更多相关《ETSI GS NFV-SEC 014-2018 Network Functions Virtualisation (NFV) Release 3 NFV Security Security Specification for MANO Components and Reference points (V3 1 1).pdf（15页珍藏版）》请在麦多课文档分享上搜索。

1、 ETSI GS NFV-SEC 014 V3.1.1 (2018-04) Network Functions Virtualisation (NFV) Release 3; NFV Security; Security Specification for MANO Components and Reference points Disclaimer The present document has been produced and approved by the Network Functions Virtualisation (NFV) ETSI Industry Specificati

2、on Group (ISG) and represents the views of those members who participated in this ISG. It does not necessarily represent the views of the entire ETSI membership. GROUP SPECIFICATION ETSI ETSI GS NFV-SEC 014 V3.1.1 (2018-04)2 Reference DGS/NFV-SEC014 Keywords interface, MANO, NFV, security ETSI 650 R

3、oute des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 Siret N 348 623 562 00017 - NAF 742 C Association but non lucratif enregistre la Sous-Prfecture de Grasse (06) N 7803/88 Important notice The present document can be downloaded from: http:/www.et

4、si.org/standards-search The present document may be made available in electronic versions and/or in print. The content of any electronic and/or print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any existing or perceived differenc

5、e in contents between such versions and/or in print, the only prevailing document is the print of the Portable Document Format (PDF) version kept on a specific network drive within ETSI Secretariat. Users of the present document should be aware that the document may be subject to revision or change

6、of status. Information on the current status of this and other ETSI documents is available at https:/portal.etsi.org/TB/ETSIDeliverableStatus.aspx If you find errors in the present document, please send your comment to one of the following services: https:/portal.etsi.org/People/CommiteeSupportStaff

7、.aspx Copyright Notification No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm except as authorized by written permission of ETSI. The content of the PDF version shall not be modified without the written authorization of

8、 ETSI. The copyright and the foregoing restriction extend to reproduction in all media. ETSI 2018. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTMand the ETSI logo are trademarks of ETSI registered for the benefit of its Members. 3GPPTM and LTETMare trademarks of ETSI registered for the benefit of

9、its Members and of the 3GPP Organizational Partners. oneM2M logo is protected for the benefit of its Members. GSMand the GSM logo are trademarks registered and owned by the GSM Association. ETSI ETSI GS NFV-SEC 014 V3.1.1 (2018-04)3 Contents Intellectual Property Rights 4g3Foreword . 4g3Modal verbs

10、terminology 4g31 Scope 5g32 References 5g32.1 Normative references 5g32.2 Informative references . 5g33 Definitions and abbreviations . 6g33.1 Definitions . 6g33.2 Abbreviations 6g34 NFV-MANO Functional Blocks and Reference points 6g34.0 Overview . 6g34.1 NFV Orchestrator 7g34.2 VNF Manager(s) . 8g3

11、4.3 Virtualised Infrastructure Manager(s) . 8g34.4 NFV Or-Vi reference point . 8g34.5 NFV Vi-Vnfm reference point 8g34.6 NFV Or-Vnfm reference point 8g35 Security Threats and Requirements 8g35.1 Analysis of components and reference points . 8g35.1.1 Fixed asset risks . 8g35.1.2 Data transfer risks 9

12、g35.2 Risk analysis and requirements . 9g36 Summary of Security Requirements . 10g3Annex A (informative): Authors Essential, or potentially Essential, IPRs notified to ETSI in respect of ETSI standards“, which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web serve

13、r (https:/ipr.etsi.org/). Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web server) which are, or may be, or may become

14、, essential to the present document. Trademarks The present document may include trademarks and/or tradenames which are asserted and/or registered by their owners. ETSI claims no ownership of these except for any which are indicated as being the property of ETSI, and conveys no right to use or repro

15、duce any trademark and/or tradename. Mention of those trademarks in the present document does not constitute an endorsement by ETSI of products, services or organizations associated with those trademarks. Foreword This Group Specification (GS) has been produced by ETSI Industry Specification Group (

16、ISG) Network Functions Virtualisation (NFV). Modal verbs terminology In the present document “shall“, “shall not“, “should“, “should not“, “may“, “need not“, “will“, “will not“, “can“ and “cannot“ are to be interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expre

17、ssion of provisions). “must“ and “must not“ are NOT allowed in ETSI deliverables except when used in direct citation. ETSI ETSI GS NFV-SEC 014 V3.1.1 (2018-04)5 1 Scope The present document provides the results of a simplified threat analysis for NFV-MANO functional blocks (NFVO, VNFM, VIM) and refe

18、rence points Or-Vnfm, Vi-Vnfm, Or-Vi based on the guidance given in ETSI GS NFV-SEC 006 5. The present document is structured such that clause 4 identifies the scope of the analysis, in the form of a target of evaluation, whilst the results of the threat analysis in the form of identified requiremen

19、ts that when implemented will counter or mitigate the threats are given in clause 5 of the present document. A summary is provided in clause 6 of the impact when the requirements are implemented. Threat analysis is a continual process and should be reviewed regularly. 2 References 2.1 Normative refe

20、rences References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. R

21、eferenced documents which are not found to be publicly available in the expected location might be found at https:/docbox.etsi.org/Reference. NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their long term validity. The following refere

22、nced documents are necessary for the application of the present document. 1 ETSI GS NFV-IFA 005: “Network Functions Virtualisation (NFV); Management and Orchestration; Or-Vi reference point - Interface and Information Model Specification“. 2 ETSI GS NFV-IFA 006: “Network Functions Virtualisation (NF

23、V); Management and Orchestration; Vi-Vnfm reference point - Interface and Information Model Specification“. 3 ETSI GS NFV-IFA 007: “Network Functions Virtualisation (NFV); Management and Orchestration; Or-Vnfm reference point - Interface and Information Model Specification“. 4 ETSI GS NFV-IFA 010: “

24、Network Functions Virtualisation (NFV); Management and Orchestration; Functional requirements specification“. 5 ETSI GS NFV-SEC 006: “Network Functions Virtualisation (NFV); Security Guide; Report on Security Aspects and Regulatory Concerns“. 2.2 Informative references References are either specific

25、 (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. NOTE: While any hyperlinks included in

26、 this clause were valid at the time of publication, ETSI cannot guarantee their long term validity. The following referenced documents are not necessary for the application of the present document but they assist the user with regard to a particular subject area. i.1 ETSI GS NFV 003: “Network Functi

27、ons Virtualisation (NFV); Terminology for Main Concepts in NFV“. i.2 ISO/IEC 15408-1/2/3 2005: “Information technology - Security techniques - Evaluation criteria for IT security“. ETSI ETSI GS NFV-SEC 014 V3.1.1 (2018-04)6 i.3 ISO/IEC 27000: “Information technology - Security techniques - Informati

28、on security management systems - Overview and vocabulary“. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in ETSI GS NFV 003 i.1 apply. 3.2 Abbreviations For the purposes of the present document, the abbreviations given in ET

29、SI GS NFV 003 i.1 apply. 4 NFV-MANO Functional Blocks and Reference points 4.0 Overview This clause provides an overview of NFV-MANO functional blocks and its associated reference points as identified in ETSI GS NFV-IFA 010 4. There are three main functional blocks associated with NFV-MANO: i) NFV O

30、rchestrator (NFVO); ii) VNF Manager (VNFM); and iii) Virtualised Infrastructure Manager (VIM). There are six reference points associated with MANO: i) Or-Vnfm reference point; ii) Or-Vi reference point; iii) Vi-Vnfm reference point; iv) Os-Ma-nfvo reference point; v) Ve-Vnfm-em reference point; and

31、vi) Ve-Vnfm-Vnf reference point. The Or-Vnfm, Or-Vi and Vi-Vnfm reference points are grouped as NFV-MANO internal reference points whereas the Os-Ma-nfvo, Ve-Vnfm-em and Ve-Vnfm-vnf reference point are grouped as NFV-MANO external reference points: i) The Or-Vnfm reference point is between NFVO and

32、VNFM. ii) The Or-Vi reference point is between NFVO and VNFM. iii) The Vi-Vnfm reference point is between the VIM and VNFM. iv) The Os-Ma-nfvo reference point is between OSS/BSS and NFVO. v) The Ve-Vnfm-em reference point is between EM and VNFM. vi) The Ve-Vnfm-vnf reference point is between VNF and

33、 VNFM. The present document provides a threat analysis for NFV-MANO functional blocks and internal NFV-MANO reference points, i.e. the Or-Vnfm, Vi-Vnfm, Or-Vi reference points. Threat analysis for the external NFV-MANO reference points, i.e. the Os-Ma-nfvo, Ve-Vnfm-em and Ve-Vnfm-Vnf reference point

34、s are for further study. ETSI ETSI GS NFV-SEC 014 V3.1.1 (2018-04)7 Figure 1: Visual interpretation of Target of Evaluation The external elements (EM, VNF, OSS/BSS) and their associated reference points are not considered in the present analysis. Figure 2: Examination of cardinality of relationships

35、 between MANO and VNFIs The cardinality of relations within MANO has an important impact on the security that may be offered. In simple terms a one-to-one relationship is more straightforward to make secure than a one-to-many or a many-to-many relationship. It is assumed for the purposes of the pres

36、ent document that there is a one-to-many relationship between the NFVO defined in ETSI GS NFV-IFA 010 4 and the VNFM, and similarly a one-to-many relationship between the VNMF and the VIM. The external relationship from MANO to instances of VNFs is also considered as one-to-many. 4.1 NFV Orchestrato

37、r The NFV Orchestrator (NFVO) is responsible for life cycle management of network services and VNF packages, validation and authorization of requests, policy management, and managing resources of NFV-PoPs via multiple VIMs and VNFMs. It also tracks the network services and the use of resources by us

38、ing different data repositories. For a detailed description of the NFV orchestrator and its functionalities, refer to clause 5.4.1 in ETSI GS NFV-IFA 010 4. ETSI ETSI GS NFV-SEC 014 V3.1.1 (2018-04)8 4.2 VNF Manager(s) VNF Manager (VNFM) is responsible for the lifecycle management of VNF instances.

39、Each VNF instance has an associated VNF manager. VNF manager functions are generic in nature and applicable to any type of VNF. The detail description of VNF managers and its functionalities are discussed in ETSI GS NFV-IFA 010 4. 4.3 Virtualised Infrastructure Manager(s) Virtualised Infrastructure

40、Manager (VIM) is responsible for controlling and managing the NFVI resources such as compute, storage and network resource of one or more NFVI-Point of Presence (PoPs). VIM exposes virtualised resource management interfaces/APIs to the VNFM and NFVO. The detail description of VIM and its functionali

41、ties are discussed in ETSI GS NFV-IFA 010 4. 4.4 NFV Or-Vi reference point The reference point Or-Vi is used to exchange information elements between NFV Orchestrator (NFVO) and Virtual Infrastructure Manager (VIM). The Or-Vi reference point supports the resource management operations. The detailed

42、description of Or-Vi reference point between NFVO and VIM are discussed in ETSI GS NFV-IFA 005 1. 4.5 NFV Vi-Vnfm reference point The reference point Vi-Vnfm is used to exchange information elements between Virtualised Infrastructure Manager (VIM) and VNF Manager (VNFM). Vi-Vnfm reference point also

43、 supports the resource management operations. The detailed discussion of Vi-Vnfm reference point between VIM and VNFM is in ETSI GS NFV-IFA 006 2. 4.6 NFV Or-Vnfm reference point The reference point Or-Vnfm is used to exchange information elements between NFV Orchestrator (NFVO) and VNF Manager (VNF

44、M). Or-Vnfm reference point supports the VNF lifecycle management operations. The detailed description of Or-Vnfm reference point between NFV Orchestrator and VNFM is in ETSI GS NFV-IFA 007 3. 5 Security Threats and Requirements 5.1 Analysis of components and reference points 5.1.1 Fixed asset risks

45、 As outlined in clause 4 the MANO entity consists of 3 discrete internal components (NFVO, VNFM, and VIM) each of which has to manage a set of fixed data assets. The MANO system is defined as an enclosed system thus all attackers are by definition insider attackers, having legitimate access to eleme

46、nts of the system. Mitigation against insider attacks is not trivial and may require a number of non-technical provisions consistent with the human resource aspects of the ISO/IEC 27000 i.3 series of guidelines or equivalent. The MANO functionality is realized in software only that is targeted to ge

47、neral purpose hardware. NOTE: There is scope for the realization of MANO to implement each of the internal components and their reference points by externalised interfaces and protocols which requires that the analysis of MANO is treated as if it were an open rather than an enclosed system. ETSI ETS

48、I GS NFV-SEC 014 V3.1.1 (2018-04)9 5.1.2 Data transfer risks As outlined in clause 4 there are a number of internal reference points that may be instantiated in interfaces. The interfaces may be instantiated as APIs within a single processing environment, as communications interfaces within a networ

49、ked environment, or as hybrid modes of API and network communications that may be used for support of Remote Procedure Calls or similar in a networked or other distributed processing environment. Similarly to clause 5.1 the only attacker considered is an inside attacker. 5.2 Risk analysis and requirements Security threats and requirements are presented in this clause with respect to NFV-MANO functional blocks (NFVO, VNFM and VIM), the associated NFV-MANO reference points (Or-Vi, Vi-Vnfm and Or-Vnfm) and any known means of implementi