Cloud and Edge Computing

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 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 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-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 62714-3:2017 specifies the integration of geometry and kinematics information for the exchange between engineering tools in the plant automation area by means of AML.

The present document specifies the interfaces supported over the Or-Vnfm reference point of the Network Functions Virtualisation Management and Orchestration (NFV-MANO) architectural framework ETSI GS NFV-MAN 001 as well as the information elements exchanged over those interfaces.

The present document specifies the interfaces supported over the Or-Vnfm reference point of the Network Functions Virtualisation Management and Orchestration (NFV-MANO) architectural framework ETSI GS NFV-MAN 001 as well as the information elements exchanged over those interfaces.

The present document specifies functional requirements for both the Virtualised Infrastructure Manager (VIM) and the NFV Infrastructure (NFVI), for NFV acceleration from an infrastructure management perspective. This includes the controlling and management of acceleration resources, e.g. allocation, release and discovery of acceleration resources. The present document also identifies the corresponding impacts on VIM related specifications regarding functional requirements ETSI GS NFV-IFA 010 and reference points (ETSI GS NFV-IFA 005 and ETSI GS NFV-IFA 006).

The present document specifies performance benchmarking metrics for virtual switching, with the goal that the metrics will adequately quantify performance gains achieved through virtual switch acceleration conforming to the associated requirements specified herein. The acceleration-related requirements will be applicable to common virtual switching functions across usage models such as packet delivery into VNFs, network overlay and tunnel termination, stateful Network Address Translators (NAT), service chaining, load balancing and, in general, match-action based policies/flows applied to traffic going to/from the VMs. The present document will also provide deployment scenarios with applicability to multiple vendor implementations and recommendations for follow-on proof of concept activities.

The present document reviews virtualisation technologies and studies their impact on the NFV architectural framework and specifications. It also provides an analysis of the pros and cons of these technologies.

The present document provides requirements for the hypervisor domain as it pertains to an operator's network. It focuses on gaps between Network Functions Virtualisation (NFV) use cases and the industry state of art at the time of publication. Therefore requirements that are deemed to be supported by most hypervisor solutions at the time of publication are not repeated in the present document.

The present document specifies requirements for the purpose of Software Modifications, such that NFV service availability and continuity is maintained. All types of software related to Network Function Virtualisation (NFV) - e.g. Virtual Network Functions (VNF), Management and Orchestration (MANO) and Network Function Virtualisation Infrastructure (NFVI) as well as required controlling and supporting functionality will be addressed. Where applicable, external specifications may be referenced to avoid duplication of work. The present document contains normative provisions.