Method and system for granting access rights to control application of industrial automation system

By using software containers and application management systems to control application loading and authentication in industrial automation systems, the problem of difficulty in granting access rights in the prior art is solved, and secure access to target devices and cloud computing systems is achieved, satisfying the satisfaction of Strict safety requirements.

CN119072691AActive Publication Date: 2024-12-03SIEMENS AG
View PDF 10 Cites 0 Cited by

Patent Information

Application Number
CN202380030126.0
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2022-03-25
Filing Date
2023-02-27
Publication Date
2024-12-03
Estimated Expiration
2043-02-27

AI Technical Summary

Technical Problem

In industrial automation systems, existing control applications often do not support the identity authentication process required by the target system, resulting in difficulty in granting access, especially for older or third-party provider control applications, token-based The method also does not have the ability to identify components that access the target system.

Method used

The software container can be loaded and executed on the host operating system, and the application management system is used for monitoring and configuration, and ensure access using password authentication and digital signatures. The software container can be migrated and executed on multiple devices. Manage the system to record and authorize data flows to ensure access to trust paths.

Benefits of technology

Implement independent access rights grants to any target device or application in industrial automation systems, ensuring secure interaction, especially in cloud computing systems, meeting strict security requirements, and avoiding the need for authentication by controlling the application itself. Functional requirements.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119072691A_ABST
    Figure CN119072691A_ABST
Patent Text Reader

Abstract

The invention relates to granting access rights to a control application of an industrial automation system. In this case, the first control application (113, 123) is provided by a software container which is loaded into and executed in a container runtime environment (112, 122) installed on the host operating system (111, 121). A first control application is monitored and configured by an application management system (200). In addition, the first control application is authenticated by the application management system. Executing directly on the host operating system (111, 121) and cryptographically authenticating the second control application (114, 124). A data stream (11) from the first control application and the second control application to the target device (103, 301) and / or the target application is authenticated after successful authentication by means of an at least temporarily valid access key (12) inserted into the data stream.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The invention relates to a method for granting access rights to a control application of an industrial automation system and a system suitable for executing the method. Background Art

[0002] Industrial automation systems usually include a large number of automation devices that are interconnected via industrial communication networks to control systems, machines or equipment as part of production or process automation. Due to the strict time requirements in industrial automation systems, real-time communication protocols such as PROFINET, PROFIBUS, Real-time Ethernet or Time Sensitive Networking (TSN) are mainly used for communication between automation devices. In particular, control services or applications can be automatically distributed according to the load of the currently available hosts or virtual machines of the industrial automation system.

[0003] WO 2021 / 104632 A1 relates to a method for recording data packets from a first container within a container cluster. Each container is assigned a plurality of network interfaces for transmitting data packets. Once a first connection for transmitting a data packet via a first network interface assigned to the first container is detected, an identifier assigned to the first container is inserted into a data stream assigned to the first connection. The inserted identifier can be used to identify the first container for recording data packets from it.

[0004] An earlier European patent application with application number 21212849.0 describes a method for providing control applications, wherein the control applications are each provided via a sequential control component that can be loaded into a sequential control environment formed by a server device and can be executed there. The control applications that require a selected security authorization are each assigned a label as a safety critical control application. For the control applications that are assigned a label as a safety critical control application, at least one expiration condition of the selected security authorization is defined. The sequential control environment monitors the occurrence of corresponding sequential conditions during the execution of the sequential control component of the control application. When the corresponding execution condition occurs, the execution of the sequential control component is terminated.

[0005] From US 2019 / 182295 A1 a method for granting access rights to a control application is known, wherein the control application is provided using a software container, which is loaded into a container runtime environment installed on a host operating system and executed there. An application management system is used to monitor and configure the control application. After successful authentication via a web proxy, the data flow from the control application to the target device or target application is authorized using an access key inserted in the data flow.

[0006] In industrial automation systems, there are many control applications that have to authenticate themselves to other systems or system components. Problems often arise with existing (especially older) control applications or control applications from third-party providers, because they do not support the authentication process required by the target system. This often means that the control application has to laboriously adapt to the required authentication process or even deactivate authentication. Token-based approaches are also not a solution to this problem, because such approaches usually do not identify the component accessing the target system. Summary of the invention

[0007] The object of the invention is to create a method for granting access rights to control applications, which method enables access to any target device or target application in an industrial automation system independently of the authentication method supported by the respective control application, and to provide a suitable device for executing the method.

[0008] According to the invention, this object is achieved by a method having the features specified in claim 1 and by a system having the features specified in claim 10. Advantageous further developments are specified in the dependent claims.

[0009] According to the method for granting access rights to a control application of an industrial automation system of the present invention, a first control application is first provided by a software container, which is loaded into a container runtime environment installed on a host operating system and executed there. An application management system is used to monitor and configure the first control application. In addition, the first control application is authenticated using the application management system. The second control application is executed directly on the host operating system and is password authenticated. In particular, neither the first control application nor the second control application has or performs an authentication function.

[0010] According to the present invention, the software container for the first control application can be migrated from an automation device with a container runtime environment to another automation device with a container runtime environment for execution there, or can be executed simultaneously on multiple automation devices with a container runtime environment. In addition, the application management system records the creation, deletion or change of the software container and registers the software container with the respective execution state of the software container. The creation, deletion or change of the software container includes the allocation or release of resources in the corresponding automation device with a container runtime environment. In this way, the first control application can be consistently orchestrated by the application management system and authorized for their data flows.

[0011] According to the invention, after successful authentication, the data flow of the first control application and the second control application to the target device or target application is authorized by means of an at least temporarily valid access key inserted into the data flow. The access key is advantageously inserted into the corresponding data flow by an assigned injector component separate from the first control application and the second control application. The first control application and the second control application are authenticated for the respective designated injector component. In addition, the data flow is preferably only authorized for the first control application and the second control application, which can be trusted, respectively, via a trust path and provided by a trust entity.

[0012] In contrast to the methods known in the prior art, in which communication connections are primarily protected by passwords and can in principle be used by any application, the present invention identifies trusted control applications in order to authorize access to critical resources on this basis. In particular, the control application itself does not have to include or provide an authentication function.

[0013] Advantageously, the second control application is cryptographically authenticated using a digital signature, a calculated process identifier or on the operating system side. A root key for authentication during the commissioning process of the automation device on which the second control application is installed can be transferred to the respective automation device. Such a root key is required on the respective automation device for successful authentication of the second control application. For example, the root key can be exchanged continuously during operation of the automation device, so that the invention can also meet strict security requirements.

[0014] According to another embodiment of the present invention, the first control application and the second control application are installed on an automation device, which is included in a secure subnet assigned to the industrial automation system. In this case, access to the first control application and the second control application from outside the secure subnet occurs only after authorization by the application management system. This ensures secure interaction of the first control application and the second control application, in particular with the cloud computing system.

[0015] Furthermore, it can be advantageously provided that the first control application and the second control application authenticate themselves to the injector component assigned to the application management system in order to access the cloud computing system outside the secure subnet. After successful authentication, the injector component assigned to the application management system inserts an at least temporarily valid access key into the data flow from the first control application and the second control application to the cloud computing system. These access keys are then used to securely and effectively authorize the first control application and the second control application to access the cloud computing system.

[0016] The system according to the present invention is provided for performing the method according to the aforementioned embodiment and comprises a plurality of automation devices which are designed and configured to provide a first control application via a software container which can be loaded into a container runtime environment installed on a host operating system and can be executed there. In addition, the selected automation devices are designed and configured to execute a second control application directly on the host operating system and cryptographically authenticate.

[0017] In addition, the system according to the invention comprises an application management system which is designed and configured to monitor, configure and authenticate the first control application. Furthermore, the system is designed and configured to authorize, after successful authentication, the data flow from the first control application and the second control application to the target device or target application, respectively, by means of an at least temporarily valid access key inserted in the data flow. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] The present invention will be explained in more detail below using embodiments with reference to the accompanying drawings.

[0019] The figure shows a system with multiple automation devices, an application management system, and a cloud computing system. DETAILED DESCRIPTION

[0020] The system shown in the figure comprises a plurality of automation devices 101-103, an application management system 200 and a cloud computing system 301. The automation devices 101-103 and the application management system 200 comprise a secure subnet 100, which is assigned to the industrial automation system. The secure subnet 100 is connected to the cloud computing system 301 via a wide area network 300, which in particular provides an Internet communication connection. A firewall system is preferably provided for the secure subnet 100, which can be integrated into the application management system 200, for example. The cloud computing system 301 comprises at least one server, by means of which IT infrastructure such as storage space, computing power or application software is provided as a service, in particular for the automation devices 101-103 or for the application management system 200.

[0021] The automation devices 101-103 can be, for example, operating and monitoring stations, programmable logic controllers, RFID readers or machine image processing systems. In addition to the automation devices 101-103, the safety subnet 100 can also include network infrastructure devices such as switches or routers. The network infrastructure devices are particularly used to connect programmable logic controllers, input / output units (I / O modules) or operating and monitoring stations of industrial automation systems.

[0022] Each programmable logic controller comprises, for example, a communication module, a central unit and at least one input / output unit. The input / output unit is used to exchange control and measurement variables between the programmable logic controller and the machine or device 110, 120, 130 controlled by the programmable logic controller. The central unit is used in particular to determine suitable control variables from the captured measurement variables. In principle, the input / output unit can also be designed as a local peripheral module arranged remotely from the programmable logic controller.

[0023] The automation devices 101-103 are designed and configured to provide a first control application 113, 123 by means of a software container, which can be loaded into a container runtime environment 112, 122 installed on a host operating system 111, 121 and can be executed in the container runtime environment. The first control application 113, 123 can in particular implement functions of the automation device, such as control and monitoring functions, or other time-critical services.

[0024] In the present embodiment, the first control application 113, 123 is monitored and configured with the aid of the application management system 200. The application management system 200 detects the creation, deletion or modification of software containers and records the respective execution state of the software containers. The creation, deletion or modification of software containers respectively includes, in particular, the allocation or release of corresponding resources in the automation device 101-102 with the container runtime environment 112, 122.

[0025] Application management system 200 also includes an image repository 213 for providing stored images for software containers. Alternatively or additionally, stored images for software containers can be retrieved from a storage and provisioning system (e.g., DockerHub or other container registry) that is read or write accessible by a large number of users.

[0026] In particular, the software container for the first control application 113, 123 can be migrated from an automation device 101, 102 with a container runtime environment 112, 122 to a different automation device 102, 101 with a container runtime environment 122, 112 to execute the software container there, or can be executed simultaneously on multiple automation devices 101-103 with container runtime environments 112, 122. Preferably, the software container is designed and configured to run in isolation from other software containers or container groups (e.g., container clusters) within a container runtime environment on a corresponding host operating system 111, 121. Advantageously, the software container uses the kernel of the host operating system 111, 121 and other software containers running on the corresponding automation device. In principle, other micro-virtualization concepts such as snapshots can also be used for software containers as an alternative to Docker containers.

[0027] In this embodiment, the container runtime environment is a container engine, which is used to create, delete or link virtual resources. In addition to software containers, virtual resources also include virtual communication networks and connections assigned to them. In particular, the container runtime environment can include a Docker engine or a Snap Core running on the corresponding automation device 101-102.

[0028] Furthermore, the automation devices 101-102 are designed and configured to execute and cryptographically authenticate the second control applications 114, 124 directly on the respective host operating systems 111, 121. On the other hand, the first control applications 113, 123 are authenticated by means of the application management system 200. In particular, the first control applications 113, 123 and the second control applications 114, 124 do not have or perform an authentication function.

[0029] The second control applications 114, 124 can be authenticated cryptographically, for example, by means of a digital signature, a calculated process identifier or by the operating system itself. In the present exemplary embodiment, a root key on the respective automation device 101-102 is required for successful authentication of the second control applications 114, 124. Preferably, the root key 14 is transmitted to the automation devices 101, 102 and stored there in a key repository 115, 125 for authentication during the commissioning process of the respective automation device 101-102, on which at least one second control application 114, 124 is installed. The root key 14 can be transmitted to the automation devices 101-102, for example, by the application management system 200. Advantageously, the root key 14 is respectively exchanged continuously during the operation of the automation devices 101-102.

[0030] After successful authentication, the data stream 11 from the first control application and the second control application to the target device 103 or the corresponding target application is authenticated by means of an at least temporarily valid access key 12 inserted into the data stream 11. The data stream 11 is only authenticated for the first control application 113-114 and the second control application 123-124 that can be trusted via a trust path or provided by a trust entity, in particular provided by the application management system 200. The access key 12 is inserted into the corresponding data stream 11 by an assigned injector component 201-202 that is separate from the first control application 113, 123 and the second control application 114, 124. The first control application 113, 123 and the second control application 114, 124 are authenticated for the respectively assigned injector component 201-202.

[0031] The application management system 200 in this embodiment further includes an injector component 212 and an application management component 211. The injector component 212 ensures that access to the first control application 113, 123 and the second control application 114, 124 from outside the secure subnet 100 can be achieved only after being authenticated by the application management system 200. To this end, the application management system 200, for example, inserts the access key 32 into the access request of the cloud computing system 301, wherein the access to the first control application 113, 123 and the second control application 114, 124 is authenticated by the access key 32.

[0032] In particular, the first control application and the second control application are authenticated with respect to the injector component 212 of the application management system 200 in order to access the cloud computing system 301 outside the secure subnet 100. In addition, after successful authentication, the injector component 212 of the application management system 200 inserts at least temporarily valid access keys 12 into the data flow 11 from the first control application and the second control application to the cloud computing system 301. With the aid of these access keys 12, the access of the first control application and the second control application to the cloud computing system 301 is authenticated.

Claims

1. A method for granting access rights to a control application of an industrial automation system, in, - providing a first control application (113, 123) by means of a software container, the software container being loaded into a container runtime environment (112, 122) installed on a host operating system (111, 121) and being executed in the container runtime environment, - the software container for the first control application can be respectively migrated from one automation device having a container runtime environment to another automation device having a container runtime environment in order to execute the software container in the other automation device, and / or the software container can be simultaneously executed on a plurality of automation devices having a container runtime environment, - monitoring and configuring said first control application by means of an application management system (200), - the application management system detects the creation, deletion and / or modification of the software container and registers the software container with the respective execution state of the software container, and wherein the creation, deletion and / or modification of the software container respectively comprises allocating or releasing resources in the corresponding automation device having the container runtime environment, - authenticating said first control application by means of said application management system, - executing directly on the host operating system (111, 121) and cryptographically authenticating the second control application (114, 124), After successful authentication, the data flow (11) from the first control application and the second control application to the target device (103, 301) and / or the target application is authenticated by means of an at least temporarily valid access key (12) inserted into the data flow.

2. The method according to claim 1, in, The data flow (11) is authenticated only for trusted first control applications (113, 123) and second control applications (114, 124) provided via a trusted path and / or by a trusted entity (200).

3. The method according to any one of claims 1 or 2, in, The access key (12) is inserted into the corresponding data stream (11) via an allocated injector component (201, 202, 212) separate from the first control application (113, 123) and the second control application (114, 124), respectively, and wherein the first control application and the second control application are authenticated for the corresponding allocated injector component.

4. The method according to any one of claims 1 to 3, in, The second control application is cryptographically authenticated by means of a digital signature, a calculation process identifier and / or by the operating system itself.

5. The method according to claim 4, in, For authentication during a commissioning process of an automation device (101-102) equipped with the second control application (114, 124), a root key (14) is transferred to the respective automation device, wherein the root key is required on the respective automation device in order to successfully authenticate the second control application.

6. The method according to claim 5, in, The root keys are respectively exchanged continuously during the operation of the automation device.

7. The method according to any one of claims 1 to 6, in, The first control application and the second control application each do not have and / or do not perform an authentication function.

8. The method according to any one of claims 1 to 7, in, The first control application and the second control application are installed on an automation device (101-102), which includes a security subnet (100) assigned to the industrial automation system, and wherein access to the first control application and the second control application from outside the security subnet is only enabled by the application management system (200) after authentication.

9. The method according to claim 8, in, In order to access a cloud computing system (301) outside the secure subnet (100), the first control application (113, 123) and the second control application (114, 124) are authenticated to an injector component (212) assigned to the application management system (200), wherein, after successful authentication, the injector component assigned to the application management system inserts an access key (12) that is at least temporarily valid into a data flow (11) from the first control application and the second control application to the cloud computing system, and wherein access to the cloud computing system by the first control application and the second control application is securely and effectively authorized with the aid of the access key.

10. A system for performing the method according to any one of claims 1 to 9, the system comprising: a plurality of automation devices (101-102) designed and configured to provide a first control application (113, 123) by means of a software container, the software container being loadable into a container runtime environment (112, 122) installed on a host operating system (111, 121) and being executable in the container runtime environment, in, The selected automation device is designed and configured to execute directly on the host operating system and cryptographically authenticate a second control application (114, 124), - an application management system (200) designed and configured for monitoring, configuring and authenticating said first control application, wherein the software container for the first control application is respectively transferable from one automation device having a container runtime environment to another automation device having a container runtime environment in order to execute the software container on the other automation device and / or is simultaneously executable on a plurality of automation devices having a container runtime environment, - wherein the application management system is designed and configured to detect the creation, deletion and / or modification of software containers and to register the software containers with their respective execution states, wherein the creation, deletion and / or modification of the software containers respectively includes allocating or releasing resources in the corresponding automation device having the container runtime environment, -Wherein, the system is designed and configured to, after successful authentication, authenticate the data flow (11) from the first control application and the second control application to the target device (103, 301) and / or the target application, respectively, by means of an at least temporarily valid access key (12) inserted into the data flow.

Citation Information

Patent Citations

  • A method of capturing packets from a container in a cluster background

    WO2021104632A1

  • Methods and apparatus for containerized secure computing resources

    CN110383240A

  • Method and system for providing security information for an application container for an industrial edge device

    CN112241533A

  • Container application authentication method and system, computing device and readable storage medium

    CN112988333A

  • Methods and systems for executing a software application using a container

    US10922090B1