1、 ETSI TS 132 376 V14.0.0 (2017-04) Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); LTE; Telecommunication management; Security services for Integration Reference Point (IRP); Solution Set (SS) definitions (3GPP TS 32.376 version 14.0.0
2、Release 14) TECHNICAL SPECIFICATION ETSI ETSI TS 132 376 V14.0.0 (2017-04)13GPP TS 32.376 version 14.0.0 Release 14Reference RTS/TSGS-0532376ve00 Keywords GSM,LTE,UMTS ETSI 650 Route 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 5
3、62 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.etsi.org/standards-search The present document may be made available in electronic versions and/or in print. The content of
4、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 difference in contents between such versions and/or in print, the only prevailing document is the print of the Portable Document Fo
5、rmat (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 of status. Information on the current status of this and other ETSI documents is available at https:/portal.etsi.org/TB/ET
6、SIDeliverableStatus.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.aspx Copyright Notification No part may be reproduced or utilized in any form or by any means, electronic or mechanical,
7、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 ETSI. The copyright and the foregoing restriction extend to reproduction in all media. European Telecommunications Standa
8、rds Institute 2017. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTMand the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members. 3GPPTM and LTE are Trade Marks of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. oneM2M logo is protected
9、for the benefit of its Members GSM and the GSM logo are Trade Marks registered and owned by the GSM Association. ETSI ETSI TS 132 376 V14.0.0 (2017-04)23GPP TS 32.376 version 14.0.0 Release 14Intellectual Property Rights IPRs essential or potentially essential to the present document may have been d
10、eclared to ETSI. The information pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found in ETSI SR 000 314: “Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respect of ETSI standards“, wh
11、ich is available from the ETSI Secretariat. Latest updates are available on the ETSI Web server (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
12、in ETSI SR 000 314 (or the updates on the ETSI Web server) which are, or may be, or may become, essential to the present document. Foreword This Technical Specification (TS) has been produced by ETSI 3rd Generation Partnership Project (3GPP). The present document may refer to technical specification
13、s or reports using their 3GPP identities, UMTS identities or GSM identities. These should be interpreted as being references to the corresponding ETSI deliverables. The cross reference between GSM, UMTS, 3GPP and ETSI identities can be found under http:/webapp.etsi.org/key/queryform.asp. Modal verbs
14、 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 expression of provisions). “must“ and “must not“ are NOT allo
15、wed in ETSI deliverables except when used in direct citation. ETSI ETSI TS 132 376 V14.0.0 (2017-04)33GPP TS 32.376 version 14.0.0 Release 14Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 5g3Introduction 5g31 Scope 6g32 References 6g33 Definitions and ab
16、breviations . 7g33.1 Definitions 7g33.2 Abbreviations . 7g34 Solution Set definitions 7g3Annex A (normative): CORBA Solution Set . 8g3A.1 Architectural features . 8g3A.1.1 Principles of IRP Security Services 8g3A.1.2 Request Interceptor. 9g3A.1.2.1 Client-side Interceptor 10g3A.1.2.2 Server-side Int
17、erceptor 10g3A.1.2.3 Request Interceptor Security Attributes 11g3A.1.3 Security Attributes Service Protocol 11g3A.1.3.1 Security Attribute Service context element 11g3A.1.3.2 CORBA Security Service . 12g3A.2 Mapping . 12g3A.2.1 RI Solution Mapping 12g3A.2.1.1 Security Attribute Mapping 12g3A.2.2 SAS
18、 Solution Mapping . 13g3A.2.2.1 Security Attribute Mapping 13g3A.3 Itf-N Security Service Behaviour . 14g3A.3.1 Request Interceptor Solution 14g3A.3.1.1 Authentication . 14g3A.3.1.2 Authorization 14g3A.3.1.3 Activity Log 14g3A.3.2 Security Attributes Service Solution 15g3A.3.2.1 Authentication . 15g
19、3A.3.2.2 Authorization 15g3A.3.2.3 Activity Log 15g3A.4 Solution Set definitions 16g3A.4.1 IDL definition structure 16g3A.4.2 IDL specification “SecurityServiceConstDefs.idl“ . 17g3A.4.3 IDL specification file “SecurityServiceSystem.idl“ . 18g3A.5 Authentication mechanism . 19g3A.5.1 Basic authentic
20、ation . 19g3A.5.2 Digest authentication 19g3A.5.3 Kerberos and SPKM . 19g3A.5.4 OMG CORBA CSIv2 Conformance Level 0 of Security . 19g3A.6 Use of OMG specified security service 20g3A.6.1 General . 20g3A.6.2 Authentication 20g3A.6.2.1 Transport Layer based method 20g3ETSI ETSI TS 132 376 V14.0.0 (2017
21、-04)43GPP TS 32.376 version 14.0.0 Release 14A.6.2.2 Client Authentication layer based method 21g3A.6.3 Authorization and Access Control 21g3A.6.4 (Message) Integrity and Confidentiality Protection . 22g3A.6.5 Quotation from OMG CORBA CSIv2 3 Conformance Levels of Security . 22g3Annex B (normative):
22、 File integrity solution . 25g3B.1 Architectural features . 25g3B.1.1 Principles of IRP Security Services 25g3B.1.2 XML Signature Recommendation 26g3B.2 Mapping . 26g3B.2.1 File integrity solution Mapping 26g3B.2.1.1 Security Attribute Mapping 26g3B.2.1.2 Operation Mapping . 26g3B.3 Itf-N Security S
23、ervice Behaviour . 27g3B.3.1 File integrity solution . 27g3Annex C (informative): Change history . 28g3History 29g3ETSI ETSI TS 132 376 V14.0.0 (2017-04)53GPP TS 32.376 version 14.0.0 Release 14Foreword This Technical Specification has been produced by the 3rdGeneration Partnership Project (3GPP). T
24、he contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number a
25、s follows: Version x.y.z where: x the first digit: 1 presented to TSG for information; 2 presented to TSG for approval; 3 or greater indicates TSG approved document under change control. y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates
26、, etc. z the third digit is incremented when editorial only changes have been incorporated in the document. Introduction The present document is part of a TS-family covering the 3rdGeneration Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication management
27、; as identified below: 32.371: “Security Management concept and requirements“. 32.372: “Security services for Integration Reference Point (IRP); Information Service (IS)“. 32.376: “Security services for Integration Reference Point (IRP); Solution Set (SS) definitions“. In 3GPP SA5 context, IRPs are
28、introduced to address process interfaces at the Itf-N interface. The Itf-N interface is built up by a number of Integration Reference Points (IRPs) and a related Name Convention, which realize the functional capabilities over this interface. The basic structure of the IRPs is defined in 3GPP TS 32.1
29、01 1 and 3GPP TS 32.102 2. IRP consists of IRPManager and IRPAgent. Usually there are three types of transaction between IRPManager and IRPAgent, which are operation invocation, notification, and file transfer. However, there are different types of intentional threats against the transaction between
30、 IRPManagers and IRPAgents. All the threats are potential risks of damage or degradation of telecommunication services, which operators should take measures to reduce or eliminate to secure the telecommunication service, network, and data. The present document is applicable to the Interface IRP spec
31、ifications. That is to say, it is only concerned with the security aspects of operations/notifications/file deployed across the Itf-N. ETSI ETSI TS 132 376 V14.0.0 (2017-04)63GPP TS 32.376 version 14.0.0 Release 141 Scope The present document specifies the Solution Set for the IRP whose semantics is
32、 specified in 3GPP TS 32.372 5 Security Service for IRP Information Service. This Solution Set specification is related to 3GPP TS 32.372 V13.0.X 5. Note that within the present document there are several alternate solutions. Specific choices will to be made to counter identified security threats, a
33、nd to consider performance and cost criteria, i.e. an implementation is not expected to have to support every option for every deployment. 2 References The following documents contain provisions which, through reference in this text, constitute provisions of the present document. - References are ei
34、ther specific (identified by date of publication, edition number, version number, etc.) or non-specific. - For a specific reference, subsequent revisions do not apply. - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document)
35、, a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document. 1 3GPP TS 32.101: “Telecommunication management; Principles and high level requirements“. 2 3GPP TS 32.102: “Telecommunication management; Architecture“. 3 3GPP TS 32.301:
36、 “Telecommunication management; Configuration Management (CM); Notification Integration Reference Point (IRP): Requirements“. 4 3GPP TS 32.371 “Telecommunication management; Security Management concept and requirements“. 5 3GPP TS 32.372: “Telecommunication management; Security services Integration
37、Reference Point (IRP); Information Service (IS)“. 6 3GPP TS 32.311: “Telecommunication management; Generic Integration Reference Point (IRP) management; Requirements“. 7 OMG CORBA Specification 02-12-06 8 OMG CORBA Security Service Specification 02-03-11 http:/www.omg.org/technology/documents/corbas
38、ervices_spec_catalog.htm 9 SECP Security Service Protocol http:/www.omg.org/technology/documents/formal/omg_security.htm#SECP 10 XML-Signature Syntax and Processing http:/www.w3.org/TR/2002/REC-xmldsig-core-20020212/ ETSI ETSI TS 132 376 V14.0.0 (2017-04)73GPP TS 32.376 version 14.0.0 Release 143 De
39、finitions and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in 3GPP TS 32.101 1, 3GPP TS 32.102 2, 3GPP TS 32.301 3 and the following apply: IRP document version number string (or “IRPVersion“): See 3GPP TS 32.311 6. 3.2 Abbreviations For the
40、 purposes of the present document, the following abbreviations apply: CA Certificate Authority CM Configuration Management CORBA Common Object Request Broker Architecture (OMG) CSS Client Security Service EM Element Manager IDL Interface Definition Language (OMG) IOR Interoperable Object Reference I
41、S Information Service NC Notification Channel (OMG) NE Network Element NV Name and Value pair OMG Object Management Group ORB Object Request Broker (OMG) QoS Quality of Service RI Request InterceptorSAS Security Attributes Service (OMG) SECP Security Protocol SS Solution Set TII Time-Independent Inv
42、ocation TSS Target Security Service UML Unified Modelling Language (OMG) 4 Solution Set definitions This specification defines the following 3GPP Security Services for IRP Solution Set Definitions: - 3GPP Security Services for IRP CORBA SS (Annex A). - 3GPP Security Services for IRP File integrity s
43、olution (Annex B). ETSI ETSI TS 132 376 V14.0.0 (2017-04)83GPP TS 32.376 version 14.0.0 Release 14Annex A (normative): CORBA Solution Set This annex contains the CORBA Solution Set for Security Services whose semantics is specified in Security Services for IRP: Information Service (TS 32.372 5). A.1
44、 Architectural features The overall architectural feature of Security Services is specified in 3GPP TS 32.372 5. This clause specifies features that are specific to the CORBA Solution. A.1.1 Principles of IRP Security Services As shown in figure A.1, the Security Services are between IRP Application
45、 layer and Transport layer. Security Attributes which are attached to network management information are transferred between IRPManager and IRPAgent to address Authentication, Authorization, Activity Log and file integrity requirements. IRPManager ApplicationSecurity ServicesTransport layerIRPAgent
46、ApplicationSecurity ServicesTransport layernetwork managementinformationattached Security AttributesFigure A.1: Principles of IRP Security Services The basic idea of these Security Services is as follows: Security Services on IRPManager side and Security Services on IRPAgent side cooperate to secure
47、 the Itf-N. When IRPManager and IRPAgent exchange network management information in a secured manner, the sender Security Service attaches Security Attributes to the network management information. The receiver analyses the received Security Attributes to determine if the received network management
48、 information is authentic and authorized. The present document specifies two alternative CORBA solutions for attaching Security Attributes over Itf-N. They use different CORBA mechanisms to transfer the Security Attributes. One uses The CORBA Request Interceptor while the other uses the CORBA Securi
49、ty Attributes Service (SAS) protocol. Both solutions need to define their respective Security Attributes. The Security Attributes used by the Interceptor mechanism and the mechanism itself are defined by the present document. The ones used by the CORBA SAS protocol are defined in CORBA SAS 7. In addition to the above two alternate mechanisms, the present document also specify a third alternative called Virtual Private Network (VPN) to secure the network management information exchanged between IRPManager and IRPAgent. Such mechanis
