2 High Level Security Drivers ITU Plenipotentiary Conference (PP-02)Intensify efforts on securityWorld Telecommunications Standardization Assembly (WTSA-04)Security robustness of protocolsCombating/Countering spamWorld Summit on the Information Society (WSIS-05)Cyber security
3 ITU-T Study GroupsITU-T work is divided up between Study Groups (SGs).SG 2: Operational aspects of service provision, networks and performanceSG 4: Telecommunication managementSG 5: Protection against electromagnetic environment effectsSG 6 Outside Plant and related indoor installationsSG 9 Integrated broadband cable networks and television and sound transmissionSG 11 Signaling requirements and protocolsSG 12 Performance and quality of serviceSG 13 Next Generation NetworksSG 15: Optical and other transport networksSG 16: Multimedia services, systems and terminalsSG 17: Security, languages and telecommunication software*SG 19: Mobile Telecommunications Networks*SG17 is the Lead Study Group on telecommunication security.
4 Overview of ITU-T Security Standardization Collaboration is key factor
5 WP 2/17 Security Questions (2005-2008) Telecom Systems UsersQ8/17Telebiometrics*Multimodal Model Fwk*System Mechanism*Protection Procedure*X.1081Telecom SystemsQ5/17Q7/17Secure Communication Services*Mobile Secure Communications *Home Network Security*Security Web Services *X.1121, X.1122Security Management*ISM Guideline for Telecom*Incident Management*Risk Assessment Methodology*etc…*X.1051Security Architecture & Framework*Architecture, Model, Concepts, Frameworks, *etc…*X.800 series *X.805Q9/17Cyber Security *Overview of Cyber-security *Vulnerability Information Sharing * Incident Handling OperationsQ6/17Countering spam*Technical anti-spam measuresQ17/17NewQ4/17Communications System Security *Vision, Coordination, Roadmap, Compendia…
6 Highlights of what’s new since GSC-10 Two new ITU-T Questions:Q.15/13, NGN securityQ.17/17, Countering spam by technical means38 security Recommendations are under development in Study Group 17Other SGs are developing security Recommendations for specific technologies – for example 5 on NGN securityFocus Group on Security Baseline For Network OperatorsNew Horizons for Security Standardization WorkshopSecurity standards roadmapCybersecurity web portal
7 Q.15/13 – NGN SecurityRecognizing that security is one of the defining features of NGN, it is essential to put in place a set of standards that will guarantee, to the maximum degree possible, the security of the telecommunications infrastructure as PSTNs evolve to NGNs.The NGN Security studies must address and develop network architectures that:- Provide for maximal network and end-user resource protection- Allow for highly-distributed intelligence end-to-end- Allow for co-existence of multiple networking technologies- Provide for end-to-end security mechanisms- Provide for security solutions that apply over multiple administrative domains
8 Q.17/17 – Combating spam by technical means Spam has become a widespread problem causing a complex range of problems to users, service providers, and network operators around the globe. While spam was originally used to send unsolicited commercial messages, increasingly spam messages are being used to spread viruses, worms, and other malicious code that negatively impact the security and stability of the global telecommunication network. Spam may include the delivery of phishing and spyware. It is a global problem that requires a multifaceted, comprehensive approach.Study items to be considered include, but are not limited to:- What risks does spam pose to the telecommunication network?- What technical factors associated with the telecommunication network contribute to the difficulty of identifying the sources of spam?- How can new technologies lead to opportunities to counter spam and enhance the security of the telecommunication network?- Do advanced telecommunication network technologies (for example, SMS, instant messaging, VoIP) offer unique opportunities for spam that require unique solutions?- What technical work is already being undertaken within the IETF, in other fora, and by private sector entities to address the problem of spam?- What telecommunication network standardization work, if any, is needed to effectively counter spam as it relates to the stability and robustness of the telecommunication network?
9 SG 17 Security Recommendations under development (1/3) Summaries of all Study Group 17 Recommendations under development are available on the Study Group 17 web page at:Communications Systems Security ProjectX.sbno, Security baseline for network operatorsSecurity Architecture and FrameworkX.805+, Division of the security features between the network and the usersX.805nsa, Network security certification based on ITU-T Recommendation X.805X.ngn-akm, Framework for authentication and key management for link layer security of NGNX.pak, Password-authenticated key exchange (PAK)X.spn, Framework for creation, storage, distribution and enforcement of security policies for networks
10 SG 17 Security Recommendations under development (2/3) Cyber SecurityX.cso, Overview of cybersecurityX.sds, Guidelines for Internet Service Providers and End-users for Addressing the Risk of Spyware and Deceptive SoftwareX.cvlm, Guidelines on Cybersecurity Vulnerability Life-cycle ManagementX.vds, A vendor-neutral framework for automatic checking of the presence of vulnerabilities information updateSecurity ManagementX.1051 (R), Information security management guidelines for telecommunications based on ISO/IEC 27002X.rmg, Risk management guidelines for telecommunicationsX.sim, Security incident management guidelines for telecommunicationsTelebiometricsX.bip, BioAPI interworking protocolX.physiol, Telebiometrics related to human physiologyX.tai, Telebiometrics authentication infrastructureX.tpp-1, A guideline of technical and managerial countermeasures for biometric data securityX.tpp-2, A guideline for secure and efficient transmission of multi-modal biometric dataX.tsm-1, General biometric authentication protocol and profile on telecommunication systemsX.tsm-2, Profile of telecomunication device for Telebiometrics System Mechanism (TSM)
11 SG 17 Security Recommendations under development (2/3) Secure Communication ServicesX.crs, Correlative reacting system in mobile networkX.homesec-1, Framework of security technologies for home networkX.homesec-2, Certificate profile for the device in the home networkX.homesec-3, User authentication mechanisms for home network serviceX.msec-3, General security value added service (policy) for mobile data communicationX.msec-4, Authentication architecture in mobile end-to-end data communicationX.p2p-1, Requirements of security for peer-to-peer and peer-to-multi peer communicationsX.p2p-2, Security architecture and protocols for peer to peer networkX.sap-1, Guideline on secure password-based authentication protocol with key exchangeX.sap-2, Secure communication using TTP serviceX.websec-1, Security Assertion Markup Language (SAML) – X.1141 now in AAP Last CallX.websec-2, eXtensible Access Control Markup Language (XACML) – X.1142 now in AAP Last CallX.websec-3, Security architecture for message security in mobile web servicesCountering spam by technical meansX.csreq, Requirement on countering spamX.fcs, Technical framework for countering spamX.gcs, Guideline on countering spamX.ocsip, Overview of countering spam for IP multimedia applicationX.tcs, Technical means for countering spam
12 SG 13 Security Recommendations under development NGN SecuritySecurity Requirements for NGN Release 1*Guidelines for NGN Security Release 1*Authentication requirements for NGN Release 1AAA Service for Network Access to NGNSecurity considerations for Pseudowire (PWE) technology* Continuation of the work originated in the ITU-T Focus Group on NGN
13 Focus Group: Security Baseline for Network Operators Established October 2005 by SG 17Objectives:Define a security baseline against which network operators can assess their network and information security posture in terms of what security standards are available, which of these standards should be used to meet particular requirements, when they should be used, and how they should be appliedDescribe a network operator’s readiness and ability to collaborate with other entities (operators, users and law enforcement authorities) to counteract information security threatsProvide meaningful criteria that can be used by network operators against which other network operators can be assessed, if required.Next StepSurvey network operators by means of a questionnaire
14 New Horizons for Security Standardization Workshop Workshop held in Geneva 3-4 October 2005ObjectivesProvide an overview of key international security standardization activities;Seek to identify primary security concerns and issues;Determine which issues are amenable to a standards-based solution;Identify which SDOs are are best equipped to do so; andConsider how SDOs can collaborate to improve the timeliness and effectiveness of security standards and avoid duplication of effort.Results reported under following topics:What are the crucial problems in ICT security standardization?Meta issues and need for a global framework;Standards Requirements and Priorities;Liaison and information sharing;User issues;Technology and threat issues;Focus for future standardization work;Process issues;Follow-on issuesReport available at
15 ICT Security Standards Roadmap Four Part RoadmapPart 1 contains information about organizations working on ICT security standardsPart 2 is a database of existing security standardsPresently includes ITU-T, ISO/IEC JTC1 and IETF standardsWill be expanded to include other standardsPart 3 will be a list of standards in developmentPart 4 will identify future needs and proposed new standardsPublicly available under Special Projects and Issues at:We invite you to use the Roadmap, provide feedback and help us develop it to meet your needs
16 The ITU Global Cybersecurity Gateway LIVE at:Provides an easy-to-use information resource on national, regional and international cybersecurity-related activities and initiatives worldwide.
17 Structure of the Cybersecurity Gateway The portal is geared towards four specific audiences: “Citizens”; “Businesses”; “Governments”, “International Organizations”Database information collected within five main themes:Information sharing of national approaches, good practices and guidelines;Developing watch, warning and incident response capabilities;Technical standards and industry solutions;Harmonizing national legal approaches and international legal coordination and enforcement;Privacy, data and consumer protection.Additional information resources on the following topics: spam, spyware, phishing, scams and frauds, worms and viruses, denial of service attacks, etc.
19 Some useful web resources ITU-T Home pageStudy Group 17LSG on SecurityRecommendationsITU-T LighthouseITU-T WorkshopsSecurity RoadmapCybersecurity Portal
20 Closing Observations Security is everybody's business Collaboration with other SDOs is necessarySecurity needs to be designed in upfrontSecurity must be an ongoing effortSystematically addressing vulnerabilities (intrinsic properties of networks/systems) is key so that protection can be provided independent of what the threats (which are constantly changing and may be unknown) may beX.805 is helpful here
21 Additional details on security work in ITU-T Study Groups: - Study Group Study Group 4 - Study Group 9 - Study Group Study Group Study Group 19
23 Study Group 17: Security, languages and telecommunication software SG 17 is the Lead Study Group on telecommunication security - It is responsible for coordination of security across all Study Groups.Subdivided into three Working Parties (WPs)WP1 - Open systems technologies;WP2 - Telecommunications security; andWP3 - Languages and telecommunications softwareMost (but not all) security Questions are in WP2Summaries of all draft Recommendations under development in SG 17 are available on the SG 17 web page at
24 Current SG 17 security-related Questions Working Party 1:1/17 End-to-end Multicast Communications with QoS Managing Facility2/17 Directory services, Directory systems, and public- key/attribute certificates3/17 Open Systems Interconnection (OSI)16/17 Internationalized Domain Names (IDN)Working Party 2:4/17 Communications Systems Security Project5/17 Security Architecture and Framework6/17 Cyber Security7/17 Security Management8/17 Telebiometrics9/17 Secure Communication Services17/17 Countering spam by technical meansNote: a short description of the work of each of these Questions is contained under the ITU-T SG17 section of the Security Roadmap (see later slide).
25 ITU-T SG 17 Question 4 Communications Systems Security Project Security WorkshopICT Security RoadmapFocus Group on Security Baseline For Network Operators
26 New Horizons for Security Standardization Workshop Workshop held in Geneva 3-4 October 2005Hosted by ITU-T SG17 as part of security coordination responsibilityISO/IEC JTC1 played an important role in planning the program and in providing speakers/panelists.Speakers, panelists, chairs from:ITU-TISO/IECIETFConsortia – OASIS, 3GPPRegional SDOs – ATIS, ETSI, RAIS
27 Workshop ObjectivesProvide an overview of key international security standardization activities;Seek to find out from stakeholders (e.g., network operators, system developers, manufacturers and end-users) their primary security concerns and issues (including possible issues of adoption or implementation of standards);Try to determine which issues are amenable to a standards-based solution and how the SDOs can most effectively play a role in helping address these issues;Identify which SDOs are already working on these issues or are best equipped to do so; andConsider how SDOs can collaborate to improve the timeliness and effectiveness of security standards and avoid duplication of effort.
28 Workshop Results Excellent discussions, feedback and suggestions Documented in detail in the Workshop reportResults are reported under following topics:What are the crucial problems in ICT security standardization?Meta issues and need for a global framework;Standards Requirements and Priorities;Liaison and information sharing;User issues;Technology and threat issues;Focus for future standardization work;Process issues;Follow-on issuesThe report is available on-line at:
29 ICT Security Standards Roadmap (An SG 17 Work-in-progress) Part 1 contains information about organizations working on ICT security standardsPart 2 is database of existing security standardsPart 3 will be a list of standards in developmentPart 4 will identify future needs and proposed new standards
30 Roadmap accessPart 2 includes ITU-T, ISO/IEC JTC1 and IETF standards. It will be expanded to include other standards (e.g. regional and consortia specifications).It will also be converted to a Database format to allow searching and to allow organizations to manage their own dataPublicly available under Special Projects and Issues at:We invite you to use the Roadmap, provide feedback and help us develop it to meet your needs
31 Other Q.4/17 projects www.itu.int/ITU-T/publications/index.html Security in Telecommunications and Information Technology – an overview of existing ITU-T Recommendations for secure telecommunications.Security compendium:catalogue of approved ITU-T Recommendations related to telecommunication securityextract of ITU-T approved security definitionslisting of ITU-T security related QuestionsWe are in the process of establishing a Security Experts Network (SEN) to maintain on-going dialogue on key issues of security standardization.
32 Focus Group: Security Baseline for Network Operators Established October 2005 by SG 17Objectives:Define a security baseline against which network operators can assess their network and information security posture in terms of what security standards are available, which of these standards should be used to meet particular requirements, when they should be used, and how they should be appliedDescribe a network operator’s readiness and ability to collaborate with other entities (operators, users and law enforcement authorities) to counteract information security threatsProvide meaningful criteria that can be used by network operators against which other network operators can be assessed, if required.Next StepSurvey network operators by means of a questionnaire
33 ITU-T SG 17 Question 5 Security Architecture and Framework Brief description of Q.5MilestonesDraft Recommendations under development
34 Brief description of Q.5/17 MotivationThe telecommunications and information technology industries are seeking cost-effective comprehensive security solutions that could be applied to various types of networks, services and applications. To achieve such solutions in multi-vendor environment, network security should be designed around the standard security architectures and standard security technologies.Major tasksDevelopment of a comprehensive set of Recommendations for providing standard security solutions for telecommunications in collaboration with other Standards Development Organizations and ITU-T Study Groups.Maintenance and enhancements of Recommendations in the X.800 series:X.800, X.802, X.803, X.805, X.810, X.811, X.812, X.813, X.814, X.815, X.816, X.830, X.831, X.832, X.833, X.834, X.835, X.841, X.842 and X.843
35 Q.5/17 MilestonesITU-T Recommendation X.805, Security Architecture for Systems Providing End-to-end Communications, was published in 2003.ISO Standard , Network security architecture, was developed in collaboration between ITU-T Q.5/17 and ISO/IEC JTC 1 SC 27 WG 1. The Standard is technically aligned with X.805. It was published in 2006.
36 ITU-T Recommendation X.805 X.805 defines a network security architecture for providing end-to-end network security. The architecture can be applied to various kinds of networks where the end-to-end security is a concern and independently of the network’s underlying technology.
37 Q.5/17 Draft Recommendations 1/2 Applications and further development of major concepts of ITU-T Recommendation X.805X.805+, Division of the security features between the network and the users. This Recommendation specifies division of security features between the networks and users. It provides guidance on applying concepts of the X.805 architecture to securing service provider’s, application provider’s networks and the end user’s equipment.X.805nsa, Network security certification based on ITU-T Recommendation X This Recommendation describes the methodology, processes and controls required for network security certification based on ITU-T Recommendation X.805, Security Architecture for Systems Providing End-to-End Communications.
38 Q.5/17 Draft Recommendations 2/2 Standardization in support of Authentication Security Dimension (defined in X.805)X.pak, Password-authenticated Key Exchange Protocol (PAK). This Recommendation specifies a password-based protocol for authentication and key exchange, which ensures mutual authentication of both parties in the act of establishing a symmetric cryptographic key via Diffie-Hellman exchange.X.ngn-akm, Framework for authentication and key management for link layer security of NGN. This Recommendation establishes a framework for authentication and key management for securing the link layer of NGN. It also provides guidance on selection of the EAP methods for NGN.Standardization of network security policiesX.spn, Framework for creation, storage, distribution, and enforcement of security policies for networks. This Recommendation establishes security policies that are to drive security controls of a system or service. It also specifies a framework for creation, storage, distribution, and enforcement of policies for network security that can be applied to various environmental conditions and network devices.
39 ITU-T SG 17 Question 6 Cyber Security MotivationObjectivesScopeCurrent area of focusDraft Recommendations under development
40 Q.6/17 MotivationNetwork connectivity and ubiquitous access is central to today’s IT systemsWide spread access and loose coupling of interconnected IT systems is a primary source of widespread vulnerabilityThreats such as: denial of service, theft of financial and personal data, network failures and disruption of voice and data telecommunications are on the riseNetwork protocols in use today were developed in an environment of trust.Most new investments and development is dedicated to building new functionality and not on securing that functionalityAn understanding of cybersecurity is needed in order to build a foundation of knowledge that can aid in securing the networks of tomorrow
41 Q.6/17 ObjectivesPerform actions in accordance with Lead Study Group (LSG) responsibility with the focus on cybersecurityWork with Q.1 of SG 2 on a definition of CybersecurityIdentify and develop standards required for addressing the challenges in cybersecurity, within the scope of Q.6/17Provide assistance to other ITU-T Study Groups in applying relevant cybersecurity Recommendations for specific security solutions. Review project-oriented security solutions for consistency.Maintain and update existing Recommendations within the scope of Q.6/17.Coordinate security activities with other ITU-T SGs, ISO/IEC JTC 1 eg. SC6, SC27 and SC37), and consortia as appropriate.Provide awareness on new security technologies related to cybersecurity
42 Q.6/17 Scope Definition of Cybersecurity Security of Telecommunications Network InfrastructureSecurity Knowledge and Awareness of Telecom Personnel and UsersSecurity Requirements for Design of New Communications Protocol and SystemsCommunications relating to CybersecuritySecurity Processes – Life-cycle Processes relating to Incident and VulnerabilitySecurity of Identity in Telecommunication NetworkLegal/Policy Considerations
43 Q.6/17 Current Area of Focus Work with SG 2 on the definition and requirements of cybersecurity.Collaborate with Q5,7,9,17/17 and SG 2 in order to achieve better understanding of various aspects of network security.Collaborate with IETF, OASIS, ISO/IEC JTC1, W3C, APEC-TEL and other standardization bodies on cybersecurity.Work on framework for secure network operations to address how telecommunications network providers secure their infrastructure and maintain secure operations.Work on Recommendation for standardization of vulnerability data definition.Study new cybersecurity issues – How should ISPs deal with botnets, evaluating the output of appropriate bodies when available.Call for contributions for the outstanding questions identified in the revised scope.
44 Q.6/17 Draft Recommendations 1/2 Overview of Cybersecurity (X.cso)This Recommendation provides a definition for Cybersecurity. The Recommendation provides a taxonomy of security threats from an operator point of view. Cybersecurity vulnerabilities and threats are presented and discussed at various network layers.Various Cybersecurity technologies that are available to remedy the threats include: Routers, Firewalls, Antivirus protection, Intrusion detection systems, Intrusion protection systems, Secure computing, Audit and Monitoring. Network protection principles such as defence in depth, access and identity management with application to Cybersecurity are discussed. Risk Management strategies and techniques are discussed including the value of training and education in protecting the network. A discussion of Cybersecurity Standards, Cybersecurity implementation issues and certification are presented.A vendor-neutral framework for automatic checking of the presence of vulnerabilities information update (X.vds)This Recommendation provides a framework of automatic notification on vulnerability information. The key point of the framework is that it is a vendor-neutral framework. Once users register their software, updates on the vulnerabilities and patches of the registered software will automatically be made available to the users. Upon notification, users can then apply
45 Q.6/17 Draft Recommendations 2/2 Guidelines for Internet Service Providers and End-users for Addressing the Risk of Spyware and Deceptive Software (X.sds)This Recommendation provides guidelines for Internet Service Providers (ISP) and end-users for addressing the risks of spyware and deceptive software. The Recommendation promotes best practices around principles of clear notices, and users’ consents and controls for ISP web hosting services. The Recommendation also promotes best practices to end-users on the Internet to secure their computing devices and information against the risks of spyware and deceptive softwareGuidelines on Cybersecurity Vulnerability Life-cycle Management(X.cvlm)The Recommendation provides a framework for the provision of monitoring, discovering, responding and post-analysis of vulnerabilities. Service providers can use this Recommendation to complement their existing Information Security Management System process in the aspect of regular vulnerability assessment, vulnerability management, incident handling and incident management.
46 ITU-T SG 17 Question 7 Security Management Systems TasksRecommendations plannedRevised X.1051Approach for revised X.1051
47 Q.7/17 TasksInformation Security Management Guidelines for telecommunications (Existing X.1051, Information security management system – Requirements for telecommunications (ISMS-T) ) ・Maintain and revise Recommendation X.1051, “Information Security Management Guidelines for telecommunications based on ISO/IEC27002”. ・Jointly develop a guideline of information security management with ISO/IEC JTC 1/SC 27.Risk Management Methodology ・Study and develop a methodology of risk management for telecommunications in line with Recommendation X ・Produce and consent a new ITU-T Recommendation for risk management methodology.Incident Management ・Study and develop a handling and response procedure on security incidents for the telecommunications in line with Recommendation X ・Produce and consent a new ITU-T Recommendation for incident management methodology and procedures.
48 Recommendations planned in Q.7/17 (Security Management) X.1050: To be proposedX.1051: In revision process Information Security Management Guidelines for Telecommunications based on ISO/IEC 27002X.1052: To be proposedX.1053: To be proposed (Implementation Guide for Telecoms)X.1054: To be proposed (Measurements and metrics for Telecommunications)X.1055 :In the first stage of development Risk Management Guidelines for TelecommunicationsX.1056: In the first stage of development Security Incident Management Guidelines for TelecommunicationsX.1057: To be proposed (Identity Management for Telecoms)
49 Information security management guidelines for Telecommunications (Revised X.1051) Information Assetsfor TelecomSecurity policyOrganising information securityAsset managementHuman resources securityPhysical & environmentalsecurityCommunications & operations managementAccess controlInformation systems acquisition, development and maintenanceInformation security incident managementBusiness continuity managementCompliance
50 Q.7/17 Approach to develop revised Recommendation X.1051 CONTROLImplementation requirements for TelecomISMS ProcessExisting X.1051CONTROLImplementation guidanceOther informationISO/IEC (2005)CONTROLImplementation guidance for TelecomOther informationRevised X.105127002
51 ITU-T SG 17 Question 8 Telebiometrics ObjectivesStudy areas on Biometric ProcessesX.1081 and draft Recommendations under development
52 Q.8/17 Objectives 1）To define telebiometric multimodal model framework 2）To specify biometric authentication mechanism in open network3）To provide protection procedures and countermeasures for telebiometric systems
53 Q.8/17 Study areas on Biometric Processes SensorsX.1081X.physiolSafety conformitytsm:TelebiometricsSystem Mechanismtpp:Protection ProceduresMatchingApplicationYes/NoScoreNWExtractionNW:NetworkDecisionAcquisition(Capturing)StorageX.tai: Telebiometrics Authentication InfrastructureX.bip: BioAPI Interworking Protocol
54 Q.8/17 Recommendations 1/4X.1081 – The telebiometric multimodal model framework – A framework for the specification of security and safety aspects of telebiometricsThis Recommendation defines a telebiometric multimodal model that can be used as a framework for identifying and specifying aspects of telebiometrics, and for classifying biometric technologies used for identification (security aspects).X.physiol – Telebiometrics related to human physiologyThis Recommendation gives names and symbols for quantities and units concerned with emissions from the human body that can be detected by a sensor, and with effects on the human body produced by the telebiometric devices in his environments.
55 Q.8/17 Recommendations 2/4X.tsm-1 – General biometric authentication protocol and profile on telecommunication systemThis Recommendation defines communication mechanism and protocols of biometric authentication for unspecified end‑users and service providers on open network.X.tsm-2 – Profile of telecomunication device for Telebiometrics System Mechanism (TSM)This Recommendation defines the requirements, security profiles of client terminals for biometric authentication over the open network.
56 Q.8/17 Recommendations 3/4X.tai – Telebiometrics authentication infrastructureThis Recommendation specifies a framework to implement biometric identity authentication with certificate issuance, management, usage and revocation.X.bip – BioAPI interworking protocolThis Recommendation is common text of ITU-T and ISO/IEC JTC1 SC37. It specifies the syntax, semantics, and encodings of a set of messages ("BIP messages") that enable BioAPI-conforming application in telebiometric systems.
57 Q.8/17 Recommendations 4/4X.tpp-1 – A guideline of technical and managerial countermeasures for biometric data securityThis Recommendation defines weakness and threats in operating telebiometric systems and proposes a general guideline of security countermeasures from both technical and managerial perspectives.X.tpp-2 – A guideline for secure and efficient transmission of multi-modal biometric dataThis Recommendation defines threat characteristics of multi-modal biometric system, and provides cryptographic methods and network protocols for transmission of multi-modal biometric data.
58 Secure Communication Services ITU-T SG 17 Question 9Secure Communication ServicesFocusPosition of each topicMobile securityHome network securityWeb services securitySecure applications services
59 Q.9/17 FocusDevelop a set of standards of secure application services, includingMobile security Under studyHome network security Under studyWeb Services security Under studySecure application services Under studyPrivacy protection for RFID and multimedia content and digital Identity management To be studiedSecurityAuthentication - to know who is accessing your dataPrivacy - to protect your data from intrusionEncryption - to secure the data from misuse or abuseBiometrics - 'what you are‘replace ‘what you know' - items, such as PIN numbersaugment 'what you have‘ - forms of identification, such as cardsX.509Public-key and attribute certificate frameworksX.842Guidelines for the use and management of Trusted Third Party servicesX.843Specification of TTP services to support the application of digital signaturesRecommendation X.509Information technology - The Directory: Public-key and attribute certificate frameworksThis Recommendation defines a framework for public-key certificates and attribute certificates. These frameworks may be used to profile application to Public Key Infrastructure (PKI) and Privilege Management Infrastructures (PMI). Also, this Recommendation defines a framework for the provision of authentication services by Directory to its users. It describes two level of authentication: simple authentication, using a password as a verification of clamed identity; and strong authentication, involving credentials formed using cryptographic techniques.ApprovedInformation technology – Security techniques – Guidelines for the use and management of Trusted Third Party servicesThis Recommendation provides guidance for the use and management of Trusted Third Party (TTP) services, a clear definition of the basic duties and services provided, their description and their purpose, and the roles and liabilities of TTPs and entities using their services. This Recommendation identifies different major categories of TTP services including time stamping, non-repudiation, key management, certificate management, and electronic notary public.Q13/7Information technology – Security techniques – Specification of TTP services to support the application of digital signaturesThis Recommendation defines the services required to support the application of digital signatures for non repudiation of creation of a document. Since this implies integrity of the document and authenticity of the creator, the services described can also be combined to implement integrity and authenticity services.
60 Secure application services Position of each topicWeb Services securityApplication ServerHomeNetworkMobile TerminalMobile NetworkOpen NetworkHome networksecurityMobile securitySecure application services
61 Q.9/17 - Mobile SecurityX.1121, Framework of security technologies for mobile end-to-end data communications – Approved 2004X.1122, Guideline for implementing secure mobile systems based on PKI – Approved 2004X.msec-3, General security value added service (policy) for mobile data communicationDevelops general security service as value added service for secure mobile end-to-end data communication.X.msec-4, Authentication architecture in mobile end-to-end data communicationConstructs generic authentication architecture for mobile data communication between mobile users and application servers.X.crs, Correlative reacting system in mobile networkDevelops the generic architecture of a correlative reactive system to protect the mobile terminal against Virus, worms, Trojan-Horses or other network attacks to both the mobile network and its mobile users.
62 Q.9/17 - Home network security X.homesec-1, Framework for security technologies for home networkFramework of security technologies for home networkDefine security threats and security requirements, security functions, security function requirements for each entity in the network, and possible implementation layerX.homesec-2, Certificate profile for the device in the home networkDevice certificate profile for the home networkDevelops framework of home network device certificate.X.homesec-3, User authentication mechanisms for home network serviceUser authentication mechanisms for home network service.Provides the user authentication mechanism in the home network, which enables various authentication means such as password, certificate, biometrics and so on.
63 Q.9/17 - Web Services security X.websec-1, Security Assertion Markup Language (SAML)Security assertion markup languageAdoption of OASIS SAML v2.0 into ITU-T Recommendation X Consented April 2006Define XML-based framework for exchanging security information.The security information expressed in the form of assertions about subjects, where a subject is an entity (either human or computer) that has an identity in some security domain.X.websec-2, eXtensible Access Control Markup Language (XACML)eXtensible Access Control Markup LanguageAdoption of OASIS XACML v2.0 into ITU-T Recommendation X Consented April 2006Provides an XML vocabulary for expressing access control policies and the syntax of the language and the rules for evaluating policies.X.websec-3, Security architecture for message security in mobile Web ServicesDevelops a guideline on message security architecture and service scenarios for securing messages for mobile Web Services.
64 Q.9/17 - Secure applications services X.sap-1, Guideline on strong password authentication protocolsGuideline on secure password-based authentication protocol with key exchange.Define a set of requirements for password-based protocol with key exchange and a selection guideline by setting up criteria that can be used in choosing an optimum authentication protocol for each application.X.sap-2, Secure communication using TTP serviceSecure end-to-end data communication techniques using TTP servicesSpecifies secure end-to-end data communication techniques using TTP services that are services defined in X.842 or other services.X.p2p-1, Anonymous authentication architecture in community communicationRequirements of security for peer-to-peer and peer-to-multi peer communicationsInvestigates threat analysis for P2P and P2MP communication services and describes security requirements for secure P2P and P2MP communication services.X.p2p-2, Security architecture and protocols for peer to peer networkSecurity architecture and protocols for peer to peer networkDescribes the security techniques and protocols in the P2P environment.
65 Countering spam by technical means ITU-T SG 17 Question 17Countering spam by technical meansObjectivesSet of Recommendations
66 Q.17/17 ObjectivesThe aim of this Question is to develop a set of Recommendations on countering spam by technical means for ITU-T, taking into account the need for collaboration with ITU-T other Study Groups and cooperation with other SDOs. The Question focuses particularly on technical requirement, frameworks and new technologies for countering spam. Guidelines on countering spam by technical means are also studied.
67 Requirement on countering spam (X.csreq) Draft Q.17/17 Set of RecommendationsGuideline on countering spam (X.gcs) DraftFramework Recommendations:IP multimedia application area (TBD)Technical framework for countering spam (X.fcs) DraftOverview of countering spam for IP multimedia application (X.ocsip) DraftTechnology Recommendations:Technical means for countering spam (X.tcs) TBDOther SDOsRequirement on countering spam (X.csreq) DraftTechnical means for countering IP multimedia spam (X.tcs) TBD
68 Q.17/17 Brief Summaries of draft Recommendations under development 1/2 X.csreq, Requirement on countering spam This Recommendation provides the general characteristics of spam, elicits generic objectives and provides an overview of the technical requirements on countering spam. In addition, this Recommendation provides checklist to evaluate the solution on countering spam.X.fcs, Technical framework for countering spamThis Recommendation specifies the technical framework for network structure for the countering spam. Functions inside the framework are defined. It also includes the commonsensible characteristics of spam, the universal rules of judgement and the common methods of countering spam.
69 Q.17/17 Brief Summaries of draft Recommendations under development 2/2 X.gcs, Guideline on countering spam (X.gcs)This Recommendation specifies technical issues on countering spam. It provides the current technical solutions and related activities from various SDOs and relevant organizations on countering spam. It will be used as a basis for further development of technical Recommendations on countering spam.X.ocsip, Overview of countering spam for IP multimedia application This Recommendation specifies basic concepts, characteristics, and effects of spam in IP multimedia applications such as IP Telephony, video on demand, IP TV, instant messaging, multimedia conference, etc. It will provide basis and guideline for developing further technical solutions on countering spam.
70 Security Work in other ITU-T Study Groups SG 4 – Security of Management planeSG 9 – IPCablecomSG 13 – NGN securitySG 16 – Multimedia securitySG 19 – Security in IMT-2000
72 SG 4: Security of the Management Plane (M.3016 series) Approved last year, the M.3016 series is viewed as a key aspect of NGN Management; it is includedin the NGN Management Roadmap issued by the NGNMFGIn M.3060 on the Principles of NGN ManagementThe M.3016 series consists of 5 parts:M : OverviewM : RequirementsM : ServicesM : MechanismsM : Profile proformaThe role of M is unique in that it provides a template for other SDOs and forums to indicate for their membership what parts of M.3016 are mandatory or optional
74 SG 9: IPCablecom Evolution Enhance cable’s existing IP service environment to accelerate the convergence of voice, video, data, and mobilityDefine an application agnostic architecture that allows cable operators to rapidly innovate new servicesProvide a suite of Recommendations that define the elements and interfaces needed to facilitate multi-vendor interoperabilityIncorporate leading communications technologies from the IETF and 3GPP IMS
75 SG 9: IPCablecom Evolution OSS evolves to support new clients and servicesOperationalSupport SystemsProvisioning, Management,Security, AccountingApplicationsVoice, Video, IMPresence, WirelessIPCablecomNetworkSignaling Framework,Subscriber DataPolicy ControlNAT TraversalNew capabilities added to support additional clients and servicesIPCablecom expands to support other servicesPSTNCMSGatewayOperationalSupport SystemsProvisioning, Management,Security, AccountingTelephony was the first serviceManaged IP NetworkCMTSDOCSIS®
76 SG 9: Targeted Applications Enhanced Cable Voice and Video IP TelephonySupport for new media and client types (e.g., video telephony, soft clients)Call treatment based on presence, device capability, identityMaintain support for cable telephony features enabled by current IPCablecom RecommendationsFixed-mobile Convergence over CableSupport for dual mode cellular/WiFi handsets over DOCSISCall handover between IPCablecom VoIP networks and cellular networksIntegrated features and call control between cellular and VoIP platformsCable Cross-Platform FeaturesCross platform notification, messaging (e.g., Caller-ID on TV)Third-party call control features, such as ‘Click to dial’
77 SG 9: Design Approach Incorporate new IP communication technologies Focus on the Session Initiation Protocol (SIP) and supporting protocolsLeverage the 3GPP IMS as a service delivery platformDevelop a modular and extensible architecture that allows new services to be added without impacting the core IPCablecom infrastructureEnsure backward compatibility with existing IPCablecom RecommendationsSupport a wide variety of client devices
78 SG 9: IPCablecom Security Requirements Under Consideration Support a range of authentication schemesUICCs (similar to SIM card)Digital Certificates (existing IPCablecom EMTAs)SIP digest (software clients)Support a range of secure signaling optionsIPsecTLSDisabledSupport secure configuration before registrationSupport TLS for intra-domain securityMinimize changes to IMSReuse existing standards
79 SG 9: DOCSIS Base Line Privacy Plus The primary goals of DOCSIS BPI+ are to provide privacy of customer traffic, integrity of software downloads, and prevent theft of service.DOCSIS BPI+ provides a number of tools to support these goals:Traffic encryption for privacy/confidentiality.Secure Software Download to assure a valid CM image.Configuration file authentication to help secure the provisioning process.Focus is on the link layer between the CMTS and CM. Security outside the DOCSIS network is provided by applications and other networks.
80 SG 9: DOCSIS BPI+ Security Algorithms A Cable Modem Terminations System (CMTS) authenticates cable modems (CM) using X.509 certificates and RSA public key cryptography.Subscriber Traffic encryption3DES used for key exchangeDES used for traffic encryption. AES being considered for future DOCSIS versions.SW download image validation is performed using X.509 certificates and digital signatures using RSA public key cryptography.Message integrity checks (MIC) with keyed MD5 hash used for CM configuration file security.This information must be identified for each feature. There can be multiple slides for each feature. Please do not if possible combine multiple features into one slide.
82 SG 13: NGN Security Outline Why NGN security?The ITU-T work on NGN SecurityRelationship to other SDOsOutput of the NGN Focus GroupRecent developments—starting the SG 13 Security workTop NGN security issues that need resolutionSecurity is among the key differentiators of the NGN. It is also among its biggest challenges!..
83 SG 13: Why Security? (Threat examples) Provider’s perspectiveTheft of serviceDenial of serviceDisclosure of network topologyNon-audited configuration changesAdditional related risks to the PSTN…Subscriber’s perspectiveEavesdropping, theft of PIN codesTele-spamIdentity theftInfection by viruses, worms, and spywareLoss of privacy (call patterns, location, etc.)Flooding attacks on the end pointIn NGN, known IP security vulnerabilities can make PSTN vulnerable, too!
84 SG 13: The ITU-T work on NGN Security SG 13: Lead Study Group on the NGN standardization. (Question 15/13 is responsible for X.805-based NGN security)SG 17: Lead Study Group on Telecommunication Security—the fundamental X.800 series, PKI, etc.SG 4: Lead Study Group on Telecommunication Management—Management Plane securitySG 11: Lead Study Group on signaling and protocols—security of the Control and Signaling planesSG 16: Lead Study Group on multimedia terminals, systems and applications—Multimedia securityFGNGN has concluded; its work has moved to SG 13
85 Collaboration of ITU-T with other bodies on NGN security Recommendations ISO/IEC JTC1SC 27, …ATISITU-TSG 13, 17, 4, 11, 16 …IETF3GPP3GPP2Fora(such as OASIS)ETSITISPANTIASG 13 is the Lead Study Group for NGNSG 17 is the Lead Study Group for Security
86 SG 13: Question 15, NGN security Question 15 (NGN security) of SG 13 – ITU-T lead study group for NGN and satellite matters - will continue standards work started by FGNGN WG 5.Q.15/13 major tasks are:Lead the NGN-specific security project-level issues within SG 13 and with other Study Groups. Recognizing SG 17’s overall role as the Lead Study Group for Telecommunication Security, advise and assist SG 17 on NGN security coordination issues.Apply the X.805 Security architecture for systems providing end-to-end communication within the context of an NGN environmentEnsure thatthe developed NGN architecture is consistent with accepted security principlesEnsure that AAA principles are integrated as required throughout the NGN
87 SG 13: FGNGN output: Security Requirements for NGN Release 1 (highlights) Security requirements for the Transport StratumNGN customer network domainCustomer network to IP-Connectivity Access Network (IP-CAN) interfaceCore network functionsNGN customer network to NGN customer network interfaceSecurity requirements for the Service StratumIMS securityTransport domain to NGN core network interfaceOpen service platforms and applications securityVoIPEmergency Telecommunication Services and Telecommunications for Disaster Relief
88 SG 13: FGNGN output: Guidelines for NGN Security Release 1 (highlights) GeneralGeneral principles and guidelines for building secure Next Generation NetworksDetailed examination of IMS access security and NAT and firewall traversalNGN Security ModelsSecurity Associations model for NGNSecurity of the NGN subsystemsIP-Connectivity Access NetworkIMS Network domain and IMS-to-non-IMS network securityIMS accessFramework for open platform for services and applications in NGNEmergency Telecommunications Service (ETS) and Telecommunications for Disaster Relief (TDR) SecurityOverview of the existing standard solutions related to NAT and firewall traversal
89 SG 13: Focus of the current work of Question 15, NGN security Security Requirements for NGN Release 1Authentication requirements for NGN Release 1AAA Service for Network Access to NGNGuidelines for NGN Security Release 1Security considerations for Pseudowire (PWE) technologyAt the heart of securing network protocols, the biggest challenge is authentication.
90 SG 13: Major Issues for NGN Security Standardization Key distribution (for end-users and network elements) and Public Key Infrastructure“Network privacy”—topology hiding and NAT/Firewall traversal for real-time applicationsConvergence with IT securityManagement of security functions (e.g., policy)Guidelines on the implementation of the IETF protocols (e.g., IPsec options)Security for supporting access: DSL, WLAN, and cable access scenariosGuidelines for handling 3GPP vs. 3GPP2 differences in IMS SecurityBoth—network assets and network traffic—must be protected.Proper management procedures will help prevent attacks from within.
93 Question 25/16 “Multimedia Security in Next-Generation Networks” (NGN-MM-SEC) Study Group 16 concentrates on Multimedia systems.Q.25/16 focuses on the application-security issues of MM applications in next generation networksStandardizes Multimedia SecuritySo far Q.25 has been standardizing MM-security for the “1st generation MM/pre-NGN?-systems”:H.323/H.248-based systems.
95 H.235 V4 Subseries Recommendations Major restructuring of H.235v3 Amd1 and annexes in stand-alone subseries RecommendationsH.235.x subseries specify scenario-specific MM-security procedures as H.235-profiles for H.323Some new parts addedSome enhancements and extensionsIncorporated correctionsApproved in Sept. 2005
96 H.323 Security Recommendations (1) H “Security framework for H-series (H.323 and other H.245-based) multimedia systems”Overview of H.235.x subseries and common procedures with baseline textH "Baseline Security Profile”Authentication & integrity for H signaling using shared secretsH "Signature Security Profile”Authentication & integrity for H signaling using X.509 digital certificates and signatures
97 H.323 Security Recommendations (2) H "Hybrid Security Profile"Authentication & integrity for H signaling using an optimized combination of X.509 digital certificates, signatures and shared secret key management; specification of an optional proxy-based security processorH "Direct and Selective Routed Call Security"Key management procedures in corporate and in interdomain environments to obtain key material for securing H call signaling in GK direct-routed/selective routed scenariosenhancedextended
98 H.323 Security Recommendations (3) H "Framework for secure authentication in RAS using weak shared secrets"Secured password (using EKE/SPEKE approach) in combination with Diffie-Hellman key agreement for stronger authentication during H signalingH "Voice encryption profile with native H.235/H.245 key management"Key management and encryption mechanisms for RTPenhancedmodified
99 H.323 Security Recommendations (4) H "Usage of the MIKEY Key Management Protocol for the Secure Real Time Transport Protocol (SRTP) within H.235"Usage of the MIKEY key management for SRTPH "Key Exchange for SRTP using secure Signalling Channels"SRTP keying parameter transport over secured signaling channels (IPsec, TLS, CMS)H "Security Gateway Support for H.323"Discovery of H.323 Security Gateways (SG = H.323 NAT/FW ALG) and key management for H signaling
100 Other SG16 MM-SEC Results H (2003) “H Directory Services Architecture for H.235”An LDAP schema to represent H.235 elements (PWs, certificates, ID information)H.530 (Revision 2003) “Symmetric security procedures for H.323 mobility in H.510”Authentication, access control and key management in mobile H.323-based corporate networks
101 Q.5/16 (H.300 NAT/FW Traversal) Results (1) H “Traversal of H.323 signalling across FWs and NATs”H.323 protocol enhancements and new client/server proxies to allow H.323 signalling protocols traverse NATs & FWs; H.323 endpoints can remain unchangedH “NAT & FW traversal procedures for RTP in H.323 systems”uses multiplexed RTP media mode and symmetric RTP in conjunction with H as a short-term solution
102 More Q.5/16 Results (2)Technical Paper “Requirements for Network Address Translator and Firewall Traversal of H.323 Multimedia Systems”Documentation of scenarios and requirements for NAT & FW traversal in H.323Technical Paper “Firewall and NAT traversal Problems in H.323 Systems”An analysis of scenarios and various problems encountered by H.323 around NAT & FW traversal
103 New Q.25/16 items under current study (1) Draft H.460.spn “Security protocol negotiation”Goal: Negotiate security protocols (IPsec or TLS) for H.323 signaling)(Draft) H.FSIC “Federated Architecture for Secure Internet Conferencing”Goal: Define a generic protocol independent security profile for globally scalable security conferencing using trust federations.
104 New Q.25/16 items under current study (2) Study Anti-DDoS (Denial-of-Service) countermeasures for (H.323-based) NAT/FW proxy and MM applicationsSecurity for MM-QoS (H.mmqos.security)MM security aspects of Vision H.325 “Next-generation Multimedia Terminals and Systems”Goal: MM-security for H.325, MM security for Audiovisual on Demand services, Multimedia Conferencing, Distant learning,...
105 New Q.25/16 items under current study (3) Study Multimedia-Security aspects of Digital Rights Management (MM-DRM)What does MM-DRM mean?Understand DRM security needs for MM content of MM applications (e.g. IPTV,…)Contributions are solicited.Which other groups are active/interested in this area?
106 Ongoing Q.5/16 work items Draft H.proxy Goal: Specify signaling & media client/server proxies connected with a (UDP) tunneling protocol for H.323 NAT & FW traversal
107 SG 16: SummaryMultimedia systems and applications as being studied by SG16 face important security challenges:MM-security and NAT/FW traversalQ.25/16 and Q.5/16 are addressing these issues and have provided various RecommendationsThe work continues in the scope of NGN-Multimedia Security.
109 Security Work in SG 19 (1/3)Q.1/19 Service and network capability requirements and network architecturePDNR Q.FNAB “Functional Network Architecture for Systems Beyond IMT-2000” has included security requirements from the beginning, building on existing material in related domainsQ.2/19 Mobility managementSecurity is included as a fundamental component of the analysis mobility management mechanisms in Q-series Supplement 47 “Technical Report on NNI Mobility Management Requirements”Currently progressing, on the same basis and jointly with Q.6/13:Rec.MMR Mobility Management Requirements (Stage 1)Rec.MMF Mobility Management Framework (Stage 2)Rec.LMF Location Mobility Management Framework (Stage 2)Rec.HMF Handover Management Framework (Stage 2)
110 Security Work in SG 19 (2/3)Q.3/19 Identification of existing and evolving IMT-2000 systemsQ.1741 and Q.1742 series of Recommendations include security as a key aspect of its referencing Recommendations for IMT-2000 (3G) Family Members identified in its Q.1741.x (3GPP) and Q.1742.x (3GPP2) series Recommendations, including:an evaluation of perceived threatsa list of security requirements to address the threatssecurity objectives and principlesa defined security architecture (i.e., security features and mechanisms)cryptographic algorithm requirementslawful interception requirementslawful interception architecture and functionsAdditional information in backup charts
111 Security in SG 19 Work (3/3)Q.4/19 Preparation of a handbook on IMT-2000Next edition of “Handbook of evolving IMT-2000 Systems (Core Network Aspects)” in progress includes a new chapter “Safety and security issues for IMT-2000”Q.5/19 Convergence of evolving IMT-2000 networks with evolving fixed networksIncludes security consideration for such areas as user identification and authentication, including IMS security (see Q.3/19)
112 ITU-T SSG & SG 19 Rec. Q.1741-series Q IMT-2000 references to release 1999 of GSM evolved UMTS core network with UTRAN access networkQ IMT-2000 references to release 4 ...Q IMT-2000 references to release 5 ...Q IMT-2000 references to release 6 ...Includes references to the 3GPP security specifications as TS : Service aspects; Service principles, TS : Security Architecture, TS : Lawful interception requirements, TS : Lawful interception Architecture and Functions, TS : Handover interface for Lawful Interception (LI), TS : Network Domain Security – MAP, TS : Access security for IP-based services, TS : Security; Network Domain Security (NDS); IP network layer security, TS , .206, .207, .208 and .909: Specification of the MILENAGE Algorithm Set
113 ITU-T SSG & SG 19 Rec. Q.1742-series Q IMT-2000 references to ANSI-41 evolved core network with cdma2000 access networkQ IMT-2000 references (...as of 11 July 2002) to ...Q IMT-2000 references (...as of 30 June 2003) to ...Q IMT-2000 references (...as of 30 June 2004) to ...“The 3GPP2 Steering Committee found that the Packet Data Surveillance Feature (also known as Packet Data Intercept, Legal Surveillance, Lawful Surveillance, or Electronic Surveillance) was regional in nature and should be left to the appropriate SDOs to develop, with 3GPP2 consulting as requested.”