Edge Computing

Edge computing is strongly related to 5G and UPF is the data connection point between the MEC system and 5G Network architecture. The sinking of 5G network user plane brings threats such as illegal eavesdropping, which may seriously threaten the data security in edge computing. The edge node has unique features itself and whether in the physical environment or the network, the data security will be an important problem that the edge nodes need to face. Therefore, the recommendation analyses the edge computing data security mainly from these two aspects and provides relative data security challenges and threats and data security guidelines for Edge Computing. This recommendation could help to address the data security issues in Edge Computing implementation

IEC 62443-2-4:2015 specifies requirements for security capabilities for IACS service providers that they can offer to the asset owner during integration and maintenance activities of an Automation Solution. The contents of the corrigendum of August 2015 have been included in this copy.

IEC 62443-3-2:2020 establishes requirements for: a) defining a system under consideration (SUC) for an industrial automation and control system (IACS); b) partitioning the SUC into zones and conduits; c) assessing risk for each zone and conduit; d) establishing the target security level (SL-T) for each zone and conduit; and e) documenting the security requirements.

IEC 62443-3-3:2013 provides detailed technical control system requirements (SRs) associated with the seven foundational requirements (FRs) described in IEC 62443-1-1 including defining the requirements for control system capability security levels, SL-C(control system). These requirements would be used by various members of the industrial automation and control system (IACS) community along with the defined zones and conduits for the system under consideration (SuC) while developing the appropriate control system target SL, SL-T(control system), for a specific asset. The contents of the corrigendum of April 2014 have been included in this copy.

IEC TR 62443-2-3:2015(E) describes requirements for asset owners and industrial automation and control system (IACS) product suppliers that have established and are now maintaining an IACS patch management program. This Technical Report recommends a defined format for the distribution of information about security patches from asset owners to IACS product suppliers, a definition of some of the activities associated with the development of the patch information by IACS product suppliers and deployment and installation of the patches by asset owners. The exchange format and activities are defined for use in security related patches; however, it may also be applicable for non-security related patches or updates.

IEC/TR 62443-3-1:2009(E) provides a current assessment of various cybersecurity tools, mitigation counter-measures, and technologies that may effectively apply to the modern electronically based IACSs regulating and monitoring numerous industries and critical infrastructures. It describes several categories of control system-centric cybersecurity technologies, the types of products available in those categories, the pros and cons of using those products in the automated IACS environments, relative to the expected threats and known cyber vulnerabilities, and, most important, the preliminary recommendations and guidance for using these cybersecurity technology products and/or countermeasures.

The standard utilizes the advanced capabilities of the XMPP protocol, such as providing globally authenticated identities, authorization, presence, life cycle management, interoperable communication, IoT discovery and provisioning. Descriptive meta-data about devices and operations will provide sufficient information for infrastructural components, services and end-users to dynamically adapt to a changing environment. Key components and needs of a successful Smart City infrastructure will be identified and addressed. This standard does not develop Application Programming Interfaces (APIs) for existing IoT or legacy protocols.

The document provides a glossary of terms relating to the conceptual, architectural and functional elements within the scope of work on Multi-access Edge Computing. The purpose of this glossary is to ensure that all terminology defined in the document is used in a consistent way by all ETSI MEC deliverables as well as in wider industry discussions on Multi-access Edge Computing.

This document establishes terminology for Digital Twin (DT) and describes concepts in the field of Digital Twin, including the terms and definitions of Digital Twin, concepts of Digital Twin (e.g., Digital Twin ecosystem, lifecycle process for Digital Twin, and classifications of Digital Twin), Functional view of Digital Twin and Digital Twin stakeholders.

This document provides a standardized generic Digital Twin maturity model, definition of assessment indicators, guidance for a maturity assessment, and other practical classifications of Digital Twin capabilities, etc.

This Recommendation provides requirements for edge cloud. It introduces the overview of edge cloud management including advantages of edge cloud management and relationship with global management in distributed cloud. It describes the edge cloud management local functions and mode. Additionally, this Recommendation provides edge cloud management functional requirements derived from use cases.

On the basis of Y.FMC-AAEC-req, which specifies use cases and requirement of application addressing in edge computing, this draft Recommendation presents the framework and technical solutions of application addressing in edge computing in IMT-2020 network and beyond. The following aspects of application addressing in edge computing are addressed in this Recommendation: Framework of application addressing in edge computing Procedures of application addressing in edge computing Security considerations on application addressing in edge computing