ITU-T M 3016-1998 TMN Security Overview - Series M TMN and Network Maintenance International Transmission Systems Telephone Circuits Telegraphy Facsimile and Leased Circuits - Tele.pdf

1、INTERNATIONAL TELECOMMUNICATION UN ION ITU-T TELECOMMUN CATION STAN DARD IZATI ON SECT0 R OF ITU M.3016 (06/98) SERIES M: TMN AND NETWORK MAINTENANCE: INTERNATIONAL TRANSMISSION SYSTEMS, TELEPHONE CIRCUITS, TELEGRAPHY, FACSIMILE - AND LEASED CIRCUITS Telecommunications management network TMN securit

2、y overview ITU-T Recommendation M.3016 (Previously CCITT Recommendation) STDe1TU-T RECMN M.301b-ENGL 1998 Y862591 Ob51833 539 m ITLJ-T M-SERIES RECOMMENDATIONS TMN AND NETWORK MAINTENANCE: INTERNATIONAL TRANSMISSION SYSTEMS, TELEPHONE CIRCUITS, TELEGRAPHY, FACSIMILE AND LEASED CIRCUITS Introduction

3、and general principles of maintenance and maintenance organization International transmission systems M.300-M.559 M. 10-M.299 International telephone circuits Common channel signalling systems International telegraph systems and phototelegraph transmission International leased group and supergroup l

4、inks International leased circuits Mobile telecommunication systems and services International public telephone network International data transmission systems Designations and information exchange M.560-M.759 M.760-M.799 M.800-M.899 M.900-M.999 M.1000-M.1099 M.1100-M.1199 M. 1 200-M. 1 299 M.1300-M

5、.1399 M. 1400-M. 1999 International transport network M.2000-M.2999 Telecommunications management network M300-M.3599 Integrated services digital networks Common channel signalling systems M. 3 600-M. 3999 M.4000-M.4999 For further details, please refer to ITU-T List of Recommendations. STD.ITU-T RE

6、CMN M-3016-ENGL L998 m 4862593 0651834 Y75 ITU-T RECOMMENDATION M.3016 TMN SECURITY OVERVIEW Summary This Recommendation provides an overview and framework that identifies security threats to a TMN and outlines how available security services can be applied within the context of the TMN functional a

7、rchitecture. Source IT-T Recommendation M.3016 was prepared by IT-T Study Group 4 (1997-2000) and was approved under the WTSC Resolution No. 1 procedure on the 26th of June 1998. Recommendation M.3016 (06/98) 1 - STD-ITU-T RECflN M.301b-ENGL 3998 = 4862593 Ob53835 303 FOREWORD ITU (International Tel

8、ecommunication Union) is the United Nations Specialized Agency in the field of telecommuni- cations. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of the ITU. The IT-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on

9、 them with a view to standardizing telecommunications on a worldwide basis. The World Telecommunication Standardization Conference (WTSC), which meets every four years, establishes the topics for study by the IN-T Snidy Groups which, in their turn, produce Recommendations on these topics. I The appr

10、oval of Recommendations by the Members of the 1TU-T is covered by the procedure laid down in WTSC Resolution No. 1. In some areas of information technology which fall within ITU-Ts purview, the necessary standards are prepared on a collaborative basis with IS0 and IEC. NOTE In this Recommendation, t

11、he expression “Administration“ is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. INTELLECTUAL PROPERTY RIGHTS The ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a cl

12、aimed Intellectual Property Right. The ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. As of the date of approval of this Recommendation, the

13、 ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database. O ITU 1998

14、All rights reserved. No part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from the ITU. 11 Recommendation M.3016 (06/98) . STD-ITU-T RECMN M.3036-ENGL 3998 4862593 0653836

15、248 m CONTENTS Introduction 1.1 Scope . 1.2 References . 1.3 Definitions . 1.4 Rationale . System description 2.2 Security domains . 2.1 Actors and roles Generic security objectives for TMN . ; . Legislation issues Threats and risks . Security requirements and services 6.1 Security requirements and

16、corresponding services . 4.1.1 Mapping functional requirements, threats and security objectives . 6.1.2 Description of functional requirements and the corresponding services . 6.2 Requirements on the management of security 6.3 Architectural requirements 6.4 Security services and OS1 layers . 6.4.1 u

17、ser authentication . 6.4.2 authentication (peer entity and data origin) . 6.4.3 access control 4.4.4 security alarm, audit trail and recovery . 6.4.5 integrity . . 6.4.4 confidentiality 6.4.7 non-repudiation . 6.5 Security management Appendix I . Legislation issues . 1.1 Introduction . 1.2 Applicabl

18、e legislation areas 1.3 Sources of legislation 1.4 Appendix II - Functional classes and security subprofiles Grouping of security measures 11.1.1 The use of FCs in the inter-domain case . 11.1.2 The use of FCs in the intra-domain case . 11.2 Functional classes . 11.3 Security profiles Possible conse

19、quences for TMN security standardization II . 1 Page 1 1 1 2 2 2 3 4 4 5 5 6 7 7 7 11 11 12 i? 12 12 12 12 13 13 14 14 14 14 15 15 14 16 16 16 16 18 Recommendation M.3016 (06/98) - . 111 Recommendation M.3016 TMN SECURITY OVERVIEW (Geneva, 1998) 1 Introduction 1.1 Scope This Recommendation provides

20、an overview and fiamework that identifies security threats to a TMN and outlines how available security services can be applied within the context of the TMN functional architecture, as described in Recommendation M.30 1 O. This Recommendation is generic in nature and does not identi or address the

21、requirements for a specific TMN interface. This Recommendation does not seek to define new security services but uses existing security services defined in other ITU-T Recommendations and IS0 Standards. It is envisaged that this Recommendation, along with Recommendation M.3400, will provide a basis

22、for future standardization of TMN security services in the ITU-T. 1.2 References The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were va

23、lid. All Recommendations and other references are subject to revision; all users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommenda

24、tions is regularly published. - - - ITU-T Recommendation M.3010 (1 996), Principles for a telecommunications management network, ITU-T Recommendation M.3400 (1997), TMN managementfunctions. ITU-T Recommendation X.509 (1997), Information technology - Open Systems Interconnection - The Directory: Auth

25、entication framework. ITU-T Recommendation X.741 (1995), Information technology - Open Systems Interconnection - Systems management: Objects and attributes for access control. CCITT Recommendation X.800 (1991), Security architecture for Open Systems Interconnection for CCITT applications. ITU-T Reco

26、mmendation X.802 (1995), Information technology - Lower layers security model. ITU-T Recommendation X.803 (1 994), Information technology - Open Systems Interconnection - Upper layers security model. ITU-T Recommendation X.810 (1995), Information technology - Open Sysems Interconnection - Security f

27、)-ameworks for open systems: Overview. ITU-T Recommendation X.812 (1 995), Information technology - Open Systems Interconnection - Security frameworks for open systems: Access control framework. ITU-T Recommendation X.813 (1996), Information technology - Open Systems Interconnection - Security frame

28、works for open systems: Non-repudiation fiamework. ITU-T Recommendation X.8 14 (1 995), Information technology - Open Systems Interconnection - Security frameworh for open systems: Confidentiality framework. ITU-T Recommendation X.8 15 (1 995), Information technology - Open Systems Interconnection -

29、 Security frameworks for open systems: Integrity framework. - - - - - - - - - Recommendation M.3016 (06/98) 1 STDmITU-T RECMN M-30Lb-ENGL I1998 E 4862593 0b5L838 010 - ITU-T Recommendation X.8 16 (1993, Information technoZ0g-y - Open Systems interconnection - Securify fiameworks for open systems: Se

30、curity audit and alarms fiamework. - ISOLEC 9979: 199 1, Data cryptographic techniques - Procedures for the registration of cryptographic algorithms. 1.3 Definitions 1.4 Rationale The requirement for securiv in TMN has originated from different sources: - Customers/subscribers need confidence in the

31、 network and the services offered, including correct billing. - The Public Community/Authorities demand security by Directives and Legislation, in order to ensure availability of services, fair competition and privacy protection. - Network Operators/Service Providers themselves need security to safe

32、guard their operation and business interests, and to meet their obligations to the customers and the public. A TMN is intended to manage the underlying telecommunications network; therefore, the security of the TMN is essential to the proper functioning of the telecommunications network. Furthermore

33、, the telecommunications network may incorporate security features that need to be managed by the TMN. Recommendation M.3400 enumerates those security management functions. TMN Security Standards should preferably be based upon internationally agreed security standards as it is beneficial to reuse r

34、ather than create new ones. The provisioning and usage of security services and mechanisms can be quite expensive relative to the value of the transactions being protected. It is therefore important to have the ability fo customize the security provided to the TMN transactions being protected. The s

35、ecurity services and mechanisms that are used for securing TMN transactions should be provided in a way that allows such customization. Due to the large number of possible combinations of security features, it is desirable to have security profiles (see Appendix 11) that cover a broad range of TMN s

36、ecurity applications. Standardization will facilitate reuse of solutions and products meaning that security can be introduced faster and at lower cost. Important benefits of standardized solutions for vendors and users of the systems alike are the economy of scale in product development and componen

37、t interoperation within a TMN system with regard to security. It is necessary to provide security services and mechanisms to protect TMN transactions among TMN entities (as defined in M.3010) against malicious attacks such as eavesdropping, spoofing, tampering with messages (modification, delay, del

38、etion, insertion, replay, re-routing, misrouting, or re-ordering of messages), repudiation or forgery. Protection includes prevention, detection and recovery from attacks, as well as management of security-related information. Standards should cover both intra-domain (43 and F) and inter-domain (X)

39、interfaces. 2 System description The objective of this Recommendation is an abstraction which makes it possible to avoid the many implementation details and to agree upon results that may be useful when later mapped on to specific implementations. The TMN is described in terms of a functional archit

40、ecture, an information architecture and a physical architecture (Recommendation M.301 O). It is recognized in Recommendation M.3010 that TMN building blocks may support other interfaces in addition to the Q, X and F. Similarly, the physical equipment may have other functionality in addition to that

41、associated with information received via Q, X and F. These additional interfaces and related functionality are outside of the TMN and therefore outside the scope of TMN security standardization. 2 Recornmendation M.3016 (06/98) STD-ITU-T RECMN M-30IIb-ENGL II998 W 48b2591 Ob51839 T57 W tg tm Figure

42、1M.3016 - TMN functional architecture 2.1 Actors and roles For the purpose of TMN security standardization, only technical security will be considered, which means that the relevant actors to consider are TMN users. A TMN user is a person or process applying TMN Management Services for the purpose o

43、f fulfilling management operations. TMN users can furilier be categorized dependent on whether they belong to the organization running the TMN (internal users) or whether they access the TMN as external users. Each time a TMN user accesses a Management Service, the ” user will take on a role. In som

44、e cases there will be a one-to-one relationship between a TMN user and a role, i.e. the TMN user will always stay in the same role. In other cases there will be a one-to-many relationship between a specific TMN user and the possible roles the TMN user can Play. The following gives a high-level class

45、ification of some common roles: - Network Operators (private or public); - Service Providers (Bearer Service Providers or Value Added Service Providers); - Service Subscribers/Service Customers; - Service End Users; - EquipmentSofiware Vendors; - Trusted Third Party. When securing the TMN, it is not

46、 enough to control the behaviour of known TMN users. One must also consider the possibility of an intruder attempting illegal access to the TMN. Some security measures require actors playing the role of a Trusted Third Party (TTP). An important security issue is how these actors should be allowed to

47、 interact with the TMN. 3 Recommendation M.3016 (06/98) STDmITU-T RECMN Mm301b-ENGL 1978 Y862591 0651890 779 = 2.2 Security domains Recommendation M.3010 introduces the concept of a Logical Layered Architecture (LLA) in which the management functionality is partitioned into layers. Each layer is con

48、cerned with a clearly bound subset of the total management activity. Each functional layer will be a separate management domain under the control of an Operation System Function (OSF), called an OSF-domain. Mediation Functions (MFs) and Network Element Functions (NEFS) controlled by the OSF will be

49、part of the OSF-domain. A TMN will as such be composed of one or several OSF domains, where the different OSF-domains can be either disjoint, interacting, overlapping or contained. A security domain is defined as a set of entities and parties that are subject to a single security policy and a single security administration. A normal assumption has been to consider a TMN as a single security domain. This will often be the case, but it might not be valid to make it a general assumption. In larger TMNs, consisting of many different management systems, different parts of the T