Recommendation ITU-T X.1712 specifies security threats and security requirements for key management in quantum key distribution networks (QKDNs), and then it specifies security measures of key management to meet the security requirements. This Recommendation provides support for design, implementation, and operation of key management in QKDN with approved security.
Recommendation ITU-T X.1043 analyses security threats to and defines security requirements for software-defined networking (SDN) based service function chaining. The corresponding security countermeasures are also given. This Recommendation aims to help understanding of security risks encountered when using the SDN-based service function chaining and implementation of secured SDN-based service function chains.
The objective of this Recommendation is to provide guidance on security requirements for trusted nodes in QKD networks. This Recommendation will identify the security threats and provide security requirements of trusted node, as well as some implementation examples to meet the requirements.
ITU-T Y.QKDN-qos-fa: "Functional architecture of QoS assurance for quantum key distribution networks"
ITU-T Y.QKDN_QoS_gen: "General aspects of QoS on the Quantum Key Distribution Network"
This recommendation specifies requirements of machine learning based QoS assurance for the quantum key distribution networks (QKDN). This recommendation first provides an overview of requirements of machine learning based QoS assurance for the QKDN. It describes a functional model of machine learning based QoS assurance and followed by associated high level and functional requirements of machine learning based QoS assurance.
To realize secure, stable, efficient, and robust operations of and services by a quantum key distribution (QKD) network as well as to manage a QKD network (QKDN) as a whole and support user network management, Recommendation ITU-T Y.3804 specifies functions and procedures for QKDN control and management based on the requirements specified in Recommendation ITU-T Y.3801.
The purpose of this Recommendation is to analyse, structure and suggest a method for establishing an incident management organization within a telecommunication organization involved in the provision of international telecommunications, where the flow and structure of an incident are focused. The flow and the handling are useful in determining whether an event is to be classified as an event, an incident, a security incident or a crisis. The flow also covers the critical first decisions that have to be made. Computer crime follows in the wake of the heavily increased use of computers in international telecommunications. Over the last years, computer crime has literally exploded, as confirmed by several international and national surveys. In the majority of countries, there are no exact figures on the number of computer break-ins or security incidents, especially those related to international telecommunications.Most telecommunication organizations or companies do not have any specialized organization for handling Information and Communication Networks (ICN) security incidents (although they may have a general crisis team for handling crises of any type). When an ICN security incident occurs it is handled ad hoc, i.e., the person who detects an ICN security incident takes the responsibility to handle it as best as (s)he can. In some organizations the tendency is to forget and cover up ICN security incidents as they may affect production, availability and revenues.Often, when an ICN security incident is detected, the person who detects it does not know who to report it to. This may result in the system or network's administrator deploying a workaround or quick fix just to get rid of the problem. They do not have the delegated authority, time or expertise to correct the system so that the ICN security incident does not recur. These are the main reasons why it is better to have a trained unit or group that can handle security incidents in a prompt and correct manner. Furthermore, many of the issues may be in areas as diverse as media relations, legal, law enforcement, market share, or financial.When reporting or handling an incident, the use of different taxonomies leads to misunderstanding. This may, in turn, result in an ICN security incident getting neither the proper attention, nor the prompt handling, that is needed in order to stop, contain and prevent the incident from recurring. This may lead to serious consequences for the affected organization (victim).To be able to succeed in incident handling and incident reporting, it is necessary to have an understanding of how incidents are detected, handled and resolved. By establishing a general structure for incidents (i.e., physical, administrative or organizational, and logical incidents) it is possible to obtain a general picture of the structure and flow of an incident. A uniform terminology is the base for a common understanding of words and terms.
Supplement 12 to ITU-T X-series Recommendations, in particular to Recommendation ITU-T X.1240, describes the basic concept and characteristics of mobile messaging spam. It also introduces and analyses current technologies on countering mobile messaging spam. In addition, this supplement proposes a general implementation framework for countering mobile messaging spam. The relative activities in different organizations are introduced in Appendix I.