ETSI TS 132 376-2016 Digital cellular telecommunications system (Phase 2+) Universal Mobile Telecommunications System (UMTS) LTE Telecommunication management Security services for .pdf

《ETSI TS 132 376-2016 Digital cellular telecommunications system (Phase 2+) Universal Mobile Telecommunications System (UMTS) LTE Telecommunication management Security services for .pdf》由会员分享，可在线阅读，更多相关《ETSI TS 132 376-2016 Digital cellular telecommunications system (Phase 2+) Universal Mobile Telecommunications System (UMTS) LTE Telecommunication management Security services for .pdf（27页珍藏版）》请在麦多课文档分享上搜索。

1、 ETSI TS 1Digital cellular telecoUniversal Mobile TelTelecommSecurity services forSolutio(3GPP TS 32.3TECHNICAL SPECIFICATION132 376 V13.0.0 (2016communications system (Phaelecommunications System (LTE; munication management; for Integration Reference Pointion Set (SS) definitions .376 version 13.0.

2、0 Release 1316-02) hase 2+); (UMTS); int (IRP); 13) ETSI ETSI TS 132 376 V13.0.0 (2016-02)13GPP TS 32.376 version 13.0.0 Release 13Reference RTS/TSGS-0532376vd00 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 S

3、iret 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.etsi.org/standards-search The present document may be made available in electronic versions and/or in print.

4、 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 difference in contents between such versions and/or in print, the only prevailing document is the print of the Port

5、able 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 of status. Information on the current status of this and other ETSI documents is available at http:/portal

6、.etsi.org/tb/status/status.asp 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 mechan

7、ical, 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

8、Standards Institute 2016. 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. GSM and the GSM log

9、o are Trade Marks registered and owned by the GSM Association. ETSI ETSI TS 132 376 V13.0.0 (2016-02)23GPP TS 32.376 version 13.0.0 Release 13Intellectual Property Rights IPRs essential or potentially essential to the present document may have been declared to ETSI. The information pertaining to the

10、se 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 ETSI Secretariat. Latest

11、 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 the updates on the ETSI Web

12、 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 specifications or reports using their 3GPP identities, UMTS ide

13、ntities 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 terminology In the present document “shall“, “sha

14、ll 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 allowed in ETSI deliverables except when used in direc

15、t citation. ETSI ETSI TS 132 376 V13.0.0 (2016-02)33GPP TS 32.376 version 13.0.0 Release 13Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 5g3Introduction 5g31 Scope 6g32 References 6g33 Definitions and abbreviations . 7g33.1 Definitions 7g33.2 Abbreviati

16、ons . 7g34 Solution Set definitions 7g3Annex A (normative): CORBA Solution Set . 8 g3A.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 Interceptor 10g3A.1.2.3 Request Interceptor Security

17、 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 Solution Mapping . 13g3A.2.2.1 Security Attribut

18、e 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 . 15g3A.3.2.2 Authorization 15g3A.3.2.3 Activity Log 1

19、5g3A.4 Solution Set definitions 15g3A.4.1 IDL definition structure 15g3A.4.2 IDL specification “SecurityServiceConstDefs.idl“ . 16g3A.4.3 IDL specification file “SecurityServiceSystem.idl“ . 16g3A.5 Authentication mechanism . 16g3A.5.1 Basic authentication . 17g3A.5.2 Digest authentication 17g3A.5.3

20、 Kerberos and SPKM . 17g3A.5.4 OMG CORBA CSIv2 Conformance Level 0 of Security . 17g3A.6 Use of OMG specified security service 17g3A.6.1 General . 17g3A.6.2 Authentication 17g3ETSI ETSI TS 132 376 V13.0.0 (2016-02)43GPP TS 32.376 version 13.0.0 Release 13A.6.2.1 Transport Layer based method 18g3A.6.

21、2.2 Client Authentication layer based method 19g3A.6.3 Authorization and Access Control 19g3A.6.4 (Message) Integrity and Confidentiality Protection . 19g3A.6.5 Quotation from OMG CORBA CSIv2 3 Conformance Levels of Security . 20g3Annex B (normative): File integrity solution . 22g3B.1 Architectural

22、features . 22g3B.1.1 Principles of IRP Security Services 22g3B.1.2 XML Signature Recommendation 23g3B.2 Mapping . 23g3B.2.1 File integrity solution Mapping 23g3B.2.1.1 Security Attribute Mapping 23g3B.2.1.2 Operation Mapping . 23g3B.3 Itf-N Security Service Behaviour . 24g3B.3.1 File integrity solut

23、ion . 24g3Annex C (informative): Change history . 25g3History 26g3ETSI ETSI TS 132 376 V13.0.0 (2016-02)53GPP TS 32.376 version 13.0.0 Release 13Foreword This Technical Specification has been produced by the 3rdGeneration Partnership Project (3GPP). The contents of the present document are subject t

24、o 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 as follows: Version x.y.z where: x the first digit

25、: 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, etc. z the third digit is incremented when edit

26、orial 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; as identified below: 32.371: “Security Manageme

27、nt 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 introduced to address process interfaces at the I

28、tf-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.101 1 and 3GPP TS 32.102 2. IRP consists of IRPMan

29、ager 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 IRPManagers and IRPAgents. All the threats are p

30、otential 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 specifications. That is to say, it is only concerned

31、with the security aspects of operations/notifications/file deployed across the Itf-N. ETSI ETSI TS 132 376 V13.0.0 (2016-02)63GPP TS 32.376 version 13.0.0 Release 131 Scope The present document specifies the Solution Set for the IRP whose semantics is specified in 3GPP TS 32.372 5 Security Service f

32、or IRP Information Service. This Solution Set specification is related to 3GPP TS 32.372 V12.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, and to consider performance and cost criteria, i.e

33、. 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 either specific (identified by date of publication, e

34、dition 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), a non-specific reference implicitly refers to the lat

35、est 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: “Telecommunication management; Configuration Managemen

36、t (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 Reference Point (IRP); Information Service (IS)“. 6 3GP

37、P 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/corbaservices_spec_catalog.htm 9 SECP Security Service Protoc

38、ol 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 V13.0.0 (2016-02)73GPP TS 32.376 version 13.0.0 Release 133 Definitions and abbreviations 3.1 Definitions For the pur

39、poses 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 purposes of the present document, the following abbrev

40、iations 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 IS Information Service NC Notification Channel (OMG) NE

41、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 Invocation TSS Target Security Service UML Unified Modelli

42、ng 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 solution (Annex B) ETSI ETSI TS 132 376 V13.0.0 (2016-02)83GP

43、P TS 32.376 version 13.0.0 Release 13Annex 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 Architectural features The overall architectural feature of

44、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 layer and Transport layer. Security Attributes which are att

45、ached to network management information are transferred between IRPManager and IRPAgent to address Authentication, Authorization, Activity Log and file integrity requirements. IRPManager ApplicationSecurity ServicesTransport layerIRPAgent ApplicationSecurity ServicesTransport layernetwork management

46、informationattached 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 the Itf-N. When IRPManager and IRPAgent exchange network man

47、agement 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 information is authentic and authorized. The present documen

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

49、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 mechanism is defined in annex A of 3GPP TS 32.371 4. ETSI