1、 International Telecommunication Union ITU-T Y.2701TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (04/2007) SERIES Y: GLOBAL INFORMATION INFRASTRUCTURE, INTERNET PROTOCOL ASPECTS AND NEXT-GENERATION NETWORKS Next Generation Networks Security Security requirements for NGN release 1 ITU-T Recommendat
2、ion Y.2701 ITU-T Y-SERIES RECOMMENDATIONS GLOBAL INFORMATION INFRASTRUCTURE, INTERNET PROTOCOL ASPECTS AND NEXT-GENERATION NETWORKS GLOBAL INFORMATION INFRASTRUCTURE General Y.100Y.199 Services, applications and middleware Y.200Y.299 Network aspects Y.300Y.399 Interfaces and protocols Y.400Y.499 Num
3、bering, addressing and naming Y.500Y.599 Operation, administration and maintenance Y.600Y.699 Security Y.700Y.799 Performances Y.800Y.899 INTERNET PROTOCOL ASPECTS General Y.1000Y.1099 Services and applications Y.1100Y.1199 Architecture, access, network capabilities and resource management Y.1200Y.1
4、299 Transport Y.1300Y.1399 Interworking Y.1400Y.1499 Quality of service and network performance Y.1500Y.1599 Signalling Y.1600Y.1699 Operation, administration and maintenance Y.1700Y.1799 Charging Y.1800Y.1899 NEXT GENERATION NETWORKS Frameworks and functional architecture models Y.2000Y.2099 Qualit
5、y of Service and performance Y.2100Y.2199 Service aspects: Service capabilities and service architecture Y.2200Y.2249 Service aspects: Interoperability of services and networks in NGN Y.2250Y.2299 Numbering, naming and addressing Y.2300Y.2399 Network management Y.2400Y.2499 Network control architect
6、ures and protocols Y.2500Y.2599 Security Y.2700Y.2799 Generalized mobility Y.2800Y.2899 For further details, please refer to the list of ITU-T Recommendations. ITU-T Rec. Y.2701 (04/2007) i ITU-T Recommendation Y.2701 Security requirements for NGN release 1 Summary ITU-T Recommendation Y.2701 provid
7、es security requirements for next generation networks (NGNs) and its interfaces (e.g., UNIs, NNIs and ANIs) by applying ITU-T Rec. X.805, Security architecture for systems providing end-to-end communications to ITU-T Recs Y.2201, NGN release 1 requirements and Y.2012, Functional requirements and arc
8、hitecture of the NGN release 1. The requirements are to provide network-based security of end user communications across multiple-network administrative domains. Security of customer assets and information in the customer domain (e.g., user network), and the use of peer-to-peer application capabilit
9、ies on customer equipment are not within the scope of this Recommendation. This Recommendation uses trust model based on network elements (physical boxes). NGN providers will be deploying network elements that support the functional entities defined in ITU-T Rec. Y.2012. The bundling of these functi
10、onal entities to a given network element will vary, depending on the vendor. Therefore, this Recommendation will not attempt to show a strict and fixed bundling between logical functional entities and physical network elements. The requirements in this Recommendation should be treated as a minimum s
11、et of security requirements, and NGN providers are encouraged to take additional measures beyond those specified in Recommendations for NGN security. Source ITU-T Recommendation Y.2701 was approved on 27 April 2007 by ITU-T Study Group 13 (2005-2008) under the WTSA Resolution 1 procedure. ii ITU-T R
12、ec. Y.2701 (04/2007) FOREWORD The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and
13、tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Rec
14、ommendations on these topics. The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. In some areas of information technology which fall within ITU-Ts purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. NOTE In this Recom
15、mendation, the expression “Administration“ is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure e.g. interoperab
16、ility or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words “shall“ or some other obligatory language such as “must“ and the negative equivalents are used to express requirements. The use of such words does not suggest that com
17、pliance with the Recommendation is required of any party. INTELLECTUAL PROPERTY RIGHTS ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validi
18、ty 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, ITU had not received notice of intellectual property, protected by patents, which may be requir
19、ed to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at http:/www.itu.int/ITU-T/ipr/. ITU 2008 All rights reserved. No part of this publication may be reproduced
20、, by any means whatsoever, without the prior written permission of ITU. ITU-T Rec. Y.2701 (04/2007) iii CONTENTS Page 1 Scope 1 1.1 X.805 principles . 1 1.2 Assumptions . 2 1.3 Overview 3 2 References. 3 3 Definitions and abbreviations. 4 3.1 Terms defined elsewhere 4 3.2 Terms defined in this Recom
21、mendation. 4 3.3 Abbreviations and acronyms 5 4 Security threats and risks 6 5 Security trust model 8 5.1 Single network trust model. 8 5.2 Peering network trust model. 10 6 Security architecture . 10 6.1 Functional NGN architecture reference 10 6.2 Mapping to NGN functional architecture. 12 6.3 Ide
22、ntification of NGN resources for security protection 14 7 Objectives and requirements. 18 7.1 General security objectives. 18 7.2 Objectives for security across multiple network provider domains . 19 7.3 Requirements specific for security dimensions 19 8 Specific security requirements 21 8.1 Common
23、security requirements for NGN elements . 21 8.2 Requirements for NGN elements in the trusted zone. 24 8.3 Requirements for NGN border elements in the “trusted-but-vulnerable“ domain 24 8.4 Requirements for TE border elements in the “un-trusted“ domain 26 8.5 Security recommendations for terminal equ
24、ipment in the “un-trusted“ domain 26 Appendix I Security objectives and guidelines for interconnection of emergency telecommunications services 27 I.1 Background. 27 I.2 Scope/purpose. 27 I.3 General objectives 27 I.4 General security capabilities. 29 I.5 Authentication, authorization and access con
25、trol. 29 I.6 Confidentiality and privacy 29 iv ITU-T Rec. Y.2701 (04/2007) Page I.7 Data integrity 30 I.8 Communication 30 I.9 Availability. 30 Bibliography. 31 ITU-T Rec. Y.2701 (04/2007) 1ITU-T Recommendation Y.2701 Security requirements for NGN release 1 1 Scope This Recommendation provides secur
26、ity requirements for next generation networks (NGNs) against security threats. It is achieved by applying the principles of ITU-T X.805, Security architecture for systems providing end-to-end communications to ITU-T Y.2201, NGN release 1 requirements and ITU-T Y.2012, Functional requirements and arc
27、hitecture of the NGN release 1. The requirements are to protect the following in a multi-network environment: network and service provider infrastructure and its assets (e.g., NGN assets and resources such as network elements, systems, components, interfaces, and data and information), its resources
28、, its communications (i.e., signalling, management and data/bearer traffic) and its services; NGN services and capabilities (e.g., voice, video and data services); end user communication and information (e.g., private information). The requirements are to provide network-based security of end user c
29、ommunications across multiple-network administrative domains. Security of customer assets and information in the customer domain (e.g., user network), and the use of peer-to-peer application capabilities on customer equipment are not within the scope of this Recommendation. The requirements specifie
30、d in this Recommendation are applicable to an NGN, including user-to-network interfaces (UNIs), network-to-network interfaces (NNIs) and application-to-network interfaces (ANIs) in a multi-network environment. NGN service providers will be deploying “network elements“ that support the functional ent
31、ities defined in ITU-T Y.2012. The bundling of these functional entities to a given network element will vary, depending on the vendor. Therefore, this Recommendation will not attempt to show a strict and fixed bundling between logical functional entities and physical network elements. The requireme
32、nts in this Recommendation should be treated as a minimum set of requirements for NGN security and should not be considered to be exhaustive. Therefore, an NGN provider may need to take additional measures beyond those specified in Recommendations for NGN security. In addition, the requirements in t
33、his Recommendation cover some of the technical aspects of what is generally known as IdM (“identity management“). A working definition of IdM is “management by NGN providers of trusted attributes of an entity such as: a subscriber, a device or a provider“. This is not intended to indicate positive v
34、alidation of a person. Administrations may require NGN providers to take into account national regulatory and national policy requirements in implementing this Recommendation. 1.1 X.805 principles ITU-T X.805 defines the following security dimensions: access control; authentication; non-repudiation;
35、 data confidentiality; communication security; data integrity; ITU-T Rec. Y.2701 (04/2007) 2 availability; privacy. It also identifies the following security threats. AccesscontrolInfrastructure securityServices securityEnd-user planeControl planeManagement planeTHREATSVULNERABILITIES8 Security dime
36、nsionsATTACKSDataconfidentialityCommunicationsecurityDataintegrityAvailabilityPrivacyAuthenticationNon-repudiation DestructionDisclosureSecurity layersApplications securityFigure 1 Security architecture of X.805 (Figure 3/X.805) These security dimensions and security threats stated above are conside
37、red as the base of this Recommendation. This Recommendation does not further define or distinguish the use of the X.805 security layers (applications, services, or infrastructure) and compliance with this standard does not require such a distinction. This Recommendation does make reference to a dist
38、inction between management, control, and user plane traffic, but cautions the reader that the utilization of that classification varies depending on the layer in a protocol stack that is under consideration. Therefore, additional standards will need to be referenced to determine compliance with such
39、 distinctions. This standard provides recommendations concerning application of the security dimensions, but does not infer completeness for use as a security assessment for NGN networks. 1.2 Assumptions This Recommendation is based on the following assumptions: 1) The bundling of functional entitie
40、s, as defined in ITU-T Y.2012, to a given network element will vary, depending on the vendor. 2) Each NGN provider has specific responsibilities within its domain for security. For example, implementing applicable security services and practices to: a) protect itself; b) assure end-to-end security i
41、s not compromised within its network; and c) assure high availability of NGN communications. 3) Each network domain will establish and enforce policies for service level agreements (SLAs) to assure the security of its domain and the security of the network interconnections. It is assumed that the SL
42、As would specify security services, mechanisms and practices to be implemented to protect the interconnected networks and the communications (signalling/control traffic, bearer traffic and management traffic) across UNIs, ANIs and NNIs. ITU-T Rec. Y.2701 (04/2007) 34) This Recommendation addresses n
43、etwork-based security, which is a layered architecture, consisting of perimeter security to trusted domains, physical security of provider equipment, and potentially the use of encryption. 1.3 Overview This Recommendation is organized as follows: Clause 2 (References) This clause provides normative
44、references. Clause 3 (Definitions and abbreviations) This clause provides definitions and abbreviations used in this Recommendation. Clause 4 (Security threats and risks) This clause highlights security threats and risks assumed for the NGN environment. Assumed security threats and risks are used as
45、 guidance to develop requirements for security and to identify security capabilities and procedures to be supported. Clause 5 (Security trust model) This clause describes a trust model for NGN security. The trust model can be used to develop trust relations for UNI, ANI and NNI connectivity and desi
46、gn of security architecture. Clause 6 (Security architecture) This clause describes the relationship between the functional NGN architecture defined in ITU-T Y.2012 and composite security architectures. Clause 7 (Objectives and requirements) This clause describes security objectives and general requ
47、irements for NGNs to be used as the basis to define security requirements for NGNs. Clause 8 (Specific security requirements) This clause provides specific security requirements as defined in clause 7. Appendix I Security objectives and requirements for emergency telecommunications services (ETS). B
48、ibliography. This Recommendation is defined to provide a base for NGN security. Various companion Recommendations for specific security areas, e.g., authenticaition and authorization, certificate management, identity management, among others, are to be provided in the future. 2 References The follow
49、ing 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 valid. All Recommendations and other references are subject to revision; 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 Recommendations
