1、 ETSI TS 132 376 V15.0.0 (2018-07) 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 15.0.0
2、Release 15) TECHNICAL SPECIFICATION ETSI ETSI TS 132 376 V15.0.0 (2018-07)13GPP TS 32.376 version 15.0.0 Release 15Reference RTS/TSGS-0532376vf00 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. ETSI 2018. All rights reserved. DE
8、CTTM, 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 its Members and of the 3GPP Organizational Partners. oneM2M logo is protected for the benefit of its Members. GSMand the G
9、SM logo are trademarks registered and owned by the GSM Association. ETSI ETSI TS 132 376 V15.0.0 (2018-07)23GPP TS 32.376 version 15.0.0 Release 15Intellectual Property Rights Essential patents IPRs essential or potentially essential to normative deliverables may have been declared to ETSI. The info
10、rmation 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“, which is available from the
11、 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 in ETSI SR 000 314 (or th
12、e updates on the ETSI Web server) which are, or may be, or may become, 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 indicate
13、d as being the property of ETSI, and conveys no right to use or reproduce 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 Technical Sp
14、ecification (TS) has been produced by ETSI 3rd Generation Partnership Project (3GPP). The present document may refer to technical specifications or reports using their 3GPP identities, UMTS identities or GSM identities. These should be interpreted as being references to the corresponding ETSI delive
15、rables. The cross reference between GSM, UMTS, 3GPP and ETSI identities can be found under http:/webapp.etsi.org/key/queryform.asp. 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 interp
16、reted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of provisions). “must“ and “must not“ are NOT allowed in ETSI deliverables except when used in direct citation. ETSI ETSI TS 132 376 V15.0.0 (2018-07)33GPP TS 32.376 version 15.0.0 Release 15Contents Intelle
17、ctual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 5g3Introduction 5g31 Scope 6g32 References 6g33 Definitions and abbreviations . 6g33.1 Definitions 6g33.2 Abbreviations . 7g34 Solution Set definitions 7g3Annex A (normative): CORBA Solution Set . 8g3A.1 Architectural featu
18、res . 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 Interceptor 10g3A.1.2.3 Request Interceptor Security Attributes 11g3A.1.3 Security Attributes Service Protocol 11g3A.1.3.1 Security Attribute Service context el
19、ement 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 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 Auth
20、entication . 14g3A.3.1.2 Authorization 14g3A.3.1.3 Activity Log 14g3A.3.2 Security Attributes Service Solution 15g3A.3.2.1 Authentication . 15g3A.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 “SecurityServ
21、iceConstDefs.idl“ . 17g3A.4.3 IDL specification file “SecurityServiceSystem.idl“ . 18g3A.5 Authentication mechanism . 19g3A.5.1 Basic authentication . 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 specifie
22、d security service 20g3A.6.1 General . 20g3A.6.2 Authentication 20g3A.6.2.1 Transport Layer based method 20g3A.6.2.2 Client Authentication layer based method 21g3ETSI ETSI TS 132 376 V15.0.0 (2018-07)43GPP TS 32.376 version 15.0.0 Release 15A.6.3 Authorization and Access Control 21g3A.6.4 (Message)
23、Integrity and Confidentiality Protection . 22g3A.6.5 Quotation from OMG CORBA CSIv2 3 Conformance Levels of Security . 22g3Annex B (normative): File integrity solution . 25g3B.1 Architectural features . 25g3B.1.1 Principles of IRP Security Services 25g3B.1.2 XML Signature Recommendation 25g3B.2 Mapp
24、ing . 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 Service Behaviour . 27g3B.3.1 File integrity solution . 27g3Annex C (informative): Change history . 28g3History 29g3ETSI ETSI TS 132 376 V15.0.0 (2018-07)53GP
25、P TS 32.376 version 15.0.0 Release 15Foreword This Technical Specification has been produced by the 3rdGeneration Partnership Project (3GPP). The 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 con
26、tents 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 as 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 d
27、ocument under change control. y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, 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
28、-family covering the 3rdGeneration Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication management; as identified below: 32.371: “Security Management concept and requirements“. 32.372: “Security services for Integration Reference Point (IRP); Information
29、Service (IS)“. 32.376: “Security services for Integration Reference Point (IRP); Solution Set (SS) definitions“. In 3GPP SA5 context, IRPs are 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 rel
30、ated Name Convention, which realize the functional capabilities over this interface. The basic structure of the IRPs is defined in 3GPP TS 32.101 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 o
31、peration invocation, notification, and file transfer. However, there are different types of intentional threats against the transaction between IRPManagers and IRPAgents. All the threats are potential risks of damage or degradation of telecommunication services, which operators should take measures
32、to reduce or eliminate to secure the telecommunication service, network, and data. The present document is applicable to the Interface IRP specifications. 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 V
33、15.0.0 (2018-07)63GPP TS 32.376 version 15.0.0 Release 151 Scope The present document specifies the Solution Set for the IRP whose semantics is specified in 3GPP TS 32.372 5 Security Service for IRP Information Service. This Solution Set specification is related to 3GPP TS 32.372 V14.0.X 5. Note tha
34、t within the present document there are several alternate solutions. Specific choices will to be made to counter identified security threats, and 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 f
35、ollowing documents contain provisions which, through reference in this text, constitute provisions of the present document. - References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. - For a specific reference, subsequent revisions do
36、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), 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: “Telecommu
37、nication management; Principles and high level requirements“. 2 3GPP TS 32.102: “Telecommunication management; Architecture“. 3 3GPP TS 32.301: “Telecommunication management; Configuration Management (CM); Notification Integration Reference Point (IRP): Requirements“. 4 3GPP TS 32.371 “Telecommunica
38、tion management; Security Management concept and requirements“. 5 3GPP TS 32.372: “Telecommunication management; Security services Integration Reference Point (IRP); Information Service (IS)“. 6 3GPP TS 32.311: “Telecommunication management; Generic Integration Reference Point (IRP) management; Requ
39、irements“. 7 OMG CORBA Specification 02-12-06 8 OMG CORBA Security Service Specification 02-03-11 http:/www.omg.org/technology/documents/corbaservices_spec_catalog.htm 9 SECP Security Service Protocol http:/www.omg.org/technology/documents/formal/omg_security.htm#SECP 10 XML-Signature Syntax and Pro
40、cessing http:/www.w3.org/TR/2002/REC-xmldsig-core-20020212/ 3 Definitions 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 (o
41、r “IRPVersion“): See 3GPP TS 32.311 6. ETSI ETSI TS 132 376 V15.0.0 (2018-07)73GPP TS 32.376 version 15.0.0 Release 153.2 Abbreviations For the purposes of the present document, the following abbreviations apply: CA Certificate Authority CM Configuration Management CORBA Common Object Request Broker
42、 Architecture (OMG) CSS Client Security Service EM Element Manager IDL Interface Definition Language (OMG) IOR Interoperable Object Reference IS Information Service NC Notification Channel (OMG) NE Network Element NV Name and Value pair OMG Object Management Group ORB Object Request Broker (OMG) QoS
43、 Quality of Service RI Request InterceptorSAS Security Attributes Service (OMG) SECP Security Protocol SS Solution Set TII Time-Independent Invocation TSS Target Security Service UML Unified Modelling Language (OMG) 4 Solution Set definitions This specification defines the following 3GPP Security Se
44、rvices for IRP Solution Set Definitions: - 3GPP Security Services for IRP CORBA SS (Annex A). - 3GPP Security Services for IRP File integrity solution (Annex B). ETSI ETSI TS 132 376 V15.0.0 (2018-07)83GPP TS 32.376 version 15.0.0 Release 15Annex A (normative): CORBA Solution Set This annex contains
45、 the CORBA Solution Set for Security Services whose semantics is specified in Security Services for IRP: Information Service (TS 32.372 5). A.1 Architectural features The overall architectural feature of Security Services is specified in 3GPP TS 32.372 5. This clause specifies features that are spec
46、ific 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 layer and Transport layer. Security Attributes which are attached to network management information are transferred between IRPManager and IRPAgent to addre
47、ss Authentication, Authorization, Activity Log and file integrity requirements. IRPManager ApplicationSecurity ServicesTransport layerIRPAgent ApplicationSecurity ServicesTransport layernetwork managementinformationattached Security AttributesFigure A.1: Principles of IRP Security Services The basic
48、 idea of these Security Services is as follows: Security Services on IRPManager side and Security Services on IRPAgent side cooperate to secure the Itf-N. When IRPManager and IRPAgent exchange network management information in a secured manner, the sender Security Service attaches Security Attribute
49、s to the network management information. The receiver analyses the received Security Attributes to determine if the received network management 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 Security Attributes Service (SAS) protocol. Both solutions need to define their respective Security Att
