Forming a cryptographically protected connection

EP4466828A1Pending Publication Date: 2024-11-27SIEMENS AG
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
EP2023713320
Authority / Receiving Office
EP · EP
Patent Type
Applications
Current Assignee / Owner
Priority Date
2022-04-06
Filing Date
2023-03-14
Publication Date
2024-11-27

AI Technical Summary

Technical Problem

Existing solutions for initial setup of security configurations in industrial LoT devices require complex manual interactions, reliance on specific security infrastructures, and online connectivity, making them cumbersome and limited in industrial application scenarios, particularly in admissibility checks for device access.

Method used

A method for forming a cryptographically protected connection between a device and a unit by sending a connection request with protected device connection information and authentication information, which indicates previous connections, allowing indirect inference of authorization information for access, enabling automated admissibility checks without explicit setup.

Benefits of technology

This method simplifies the setup process by allowing indirect inference of authorization information, reducing manual interactions, and enhancing security through tamper-proof verification of previous connections, making it suitable for various deployment scenarios without relying on centralized security infrastructures.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 1.1
    Figure 1.1
Patent Text Reader

Abstract

The invention relates to a method for forming a first cryptographically protected connection of a device (D) to a unit (E), having the following steps: - the device (D) transmitting a connection request (Req), wherein the connection request (Req) is assigned cryptographically protected device connection information (CD-A) and device authentication information (DA), wherein the device connection information (CD-A) indicates which at least one second connection from the device (D) to at least one second device existed earlier in time, wherein the device authentication information (DA) authenticates the device (D), and - forming the first cryptographically protected connection of the device (D) to the unit (E) on the basis of a result of a check (P-AR) on the device connection information (CD-A) and the device authentication information (DA). The invention furthermore relates to a corresponding method from the perspective of the unit (E). The invention furthermore relates to the associated device (D) and to the associated unit (E).
Need to check novelty before this filing date? Find Prior Art

Description

[0001] Description

[0002] Establishing a cryptographically protected connection

[0003] BACKGROUND OF THE INVENTION

[0004] Field of the invention

[0005] The present invention relates to two corresponding methods for establishing a cryptographically protected connection between a device and a unit, wherein one method is described from the perspective of the device and one method is described from the perspective of the unit. The invention also relates to the associated device and the associated unit.

[0006] Description of the state of the art

[0007] The simple, initial setup of a security configuration on a device, particularly an industrial IoT device or a mobile device, is a fundamental objective. This is also referred to as provisioning, onboarding, bootstrapping, or pairing. There are conflicting requirements here: On the one hand, it should be as automated as possible and require no or minimal user interaction. On the other hand, however, it should be possible to tightly control which devices are accepted as permissible devices in a critical environment, particularly an industrial environment. Furthermore, the solution should be flexible and applicable in different deployment scenarios without being dependent on a specific centralized security infrastructure, particularly that of a mobile provider or an association of mobile providers, or a specific PKI infrastructure.

[0008] Previous solutions for initial setup protect the setup process itself, ensuring only authorized setup. However, these solutions require complex manual or administrative interactions, particularly to enter or load sufficiently strong authorization information, such as a password or onboarding token, for each setup process separately. Or they require a security infrastructure that provides the corresponding security information. Even in this case, however, the corresponding information must be set up. Online connectivity to public networks (Internet) may also be necessary. Such solutions are therefore cumbersome and sometimes only of limited use in typical industrial application scenarios (Industrial IoT).

[0009] The technical implementation of automated admissibility checks is particularly challenging when initially setting up a security configuration, as there is no or only a minimal security configuration as a basis for the admissibility check. However, admissibility checks during device access are also relevant in a variety of other application scenarios, such as access to a cloud service, edge server, another IoT device, or access to a communications network, especially Wi-Fi, 5G, and / or Ethernet.

[0010] The object of the invention is to provide a solution for improved device authentication, particularly in connection with setting up a security configuration on a device. In general, there is a need for an improved way to verify the legitimacy of access.

[0011] SUMMARY OF THE INVENTION

[0012] The invention results from the features of the independent claims. Advantageous further developments and refinements are the subject of the dependent claims. Embodiments, possible applications, and advantages of the invention emerge from the following description and the drawings. The invention relates to a method for forming a first cryptographically protected connection between a device and a unit. From the perspective of the device to be connected, the method comprises the following steps:

[0013] - Sending a connection request by the device, wherein the connection request is associated with cryptographically protected device connection information and device authentication information, wherein the device connection information indicates which at least one second connection from the device to at least one second device existed earlier, wherein the device authentication information authenticates the device and

[0014] - Establishing the first cryptographically protected connection of the device to the unit depending on a result of checking the device connection information and the device authentication information.

[0015] One aspect of the invention thus consists in cryptographically confirming information that indicates with which other second devices the device to be connected was previously connected.

[0016] When the device accesses, in particular a unit such as a cloud service, an edge device, a control unit, another IoT device, a communication network, when accessing an onboarding network, a provisioning server or a device management server, the device connection information to the previously connected second devices is provided in a tamper-proof manner.

[0017] This has the advantage that authorization information which permits specific access by this device, in particular to a unit such as a provisioning server for carrying out a provisioning process, does not have to be explicitly set up for a specific device. Instead, this information can be inferred indirectly. If, as part of the defined procedure, a device to be put into operation is connected to other, i.e. second, devices, which can also be referred to as components, in accordance with the defined procedure, this implicitly results in the authorization to permit certain logical accesses, in particular for automatic provisioning of security credentials on the device by a provisioning server.

[0018] In a further development of the invention, the device connection information additionally indicates to which at least one second device the at least one connection to the device to be connected currently still exists. The respective second connection can thus be terminated or still exist at the time of confirmation.

[0019] In a further development of the invention, the device connection information includes:

[0020] - an identifier, in particular relating to a device manufacturer, device type and / or device serial number, and / or

[0021] - an authentication credential, in particular a certificate, a cryptographic key and / or a password hash of the at least one second device to which the at least one second connection existed.

[0022] The device to be connected determines the device connection information, especially if the second connection is established, and saves it itself or passes it to an external storage for storage.

[0023] In a further development of the invention, the connection request is additionally assigned additional information, which in particular indicates:

[0024] - at what time and / or

[0025] - over what period of time and / or

[0026] - via which device interface and / or in combination with which at least one third connection the at least one second connection existed.

[0027] The additional information can be stored locally by the device itself, in particular in a flash memory or in a security element of the device. Alternatively, the information can also be stored by the device in an external memory, in particular a removable memory module, such as an SD card, a database, or a distributed database (e.g., distributed ledger, blockchain), preferably in the form of a cryptographically protected transaction data structure. Information stored in an external memory preferably further comprises identification information of the device, e.g., an identifier or an authentication credential of the device.

[0028] In a further development of the invention, the device connection information is:

[0029] - the device and / or

[0030] - provided to an external unit.

[0031] The device connection information is preferably provided by the device itself, which provides this information together with an access or associated with an access. Device connection information can alternatively or additionally be provided by a connected device, by a separate unit, in particular a web service, or by a distributed database.

[0032] In a further development of the invention, the cryptographically protected connection between the device and the unit is also established depending on a second piece of device connection information, wherein the first piece of device connection information and the second piece of device connection information are checked for consistency. This is particularly advantageous when the device connection information is provided by the device and an external unit.

[0033] In this variant, multiple pieces of device connection information provided by different sources are checked for consistency. Thus, a previous second connection can only be considered valid if it is confirmed not only by the device itself, but also by the previously connected second device, or if it is additionally confirmed by a distributed database. This has the advantage of achieving a higher level of security.

[0034] In a further development of the invention, the second device is:

[0035] - a peripheral device and / or

[0036] - an extension module and / or

[0037] - a tool of a machine tool and / or

[0038] - an IoT device and / or

[0039] - a second device is formed which is mechanically connected to the device and which preferably cannot be removed without destruction.

[0040] Some connected second devices can therefore also be permanently connected to the accessing device, in particular be permanently installed in it, in particular in an internal expansion slot or slot or possibly also be glued, cast in or soldered.

[0041] In a further development of the invention, the unit is as:

[0042] - a server and / or

[0043] - a cloud service and / or

[0044] - an edge device and / or

[0045] - a control unit and / or

[0046] - a control function and / or

[0047] - another, third device, in particular a second IoT device and / or - a communication network and / or

[0048] - an onboarding network and / or

[0049] - a provisioning server and / or

[0050] - a device management server was trained.

[0051] The access originating from the device and thus the first cryptographically protected connection can in particular concern one of the following cases:

[0052] - Network access authentication (WLAN, 5G cellular, IEEE 802.IX)

[0053] - Authentication to Provisioning Server, Device Management Server

[0054] - Authentication to control computer / control function (virtualized control computer, e.g. on Industrial Edge Device)

[0055] - Authentication to other devices, edge devices, backend cloud

[0056] In a further development of the invention, rules are used to check the connection request, based on which:

[0057] - an admission or

[0058] - a decision is made to allow the formation of the first cryptographically protected connection of the device with the unit to a limited extent.

[0059] Depending on which other, second devices the affected accessing device was previously connected to, access is permitted, modified, i.e. permitted with restrictions, or rejected.

[0060] In particular, the establishment of the first cryptographically protected connection, and thus access, can be permitted if the accessing device was connected to a specific other device within a predefined time window. In general, to determine the admissibility of access, it is possible to evaluate which other, second devices the accessing device was connected to, when, for how long, at which location, and in what order.

[0061] This eliminates the need to explicitly set up authorization information for a specific device, allowing a specific access by an entity, especially to a provisioning server to perform a provisioning process. Instead, this information can be inferred indirectly. All that's required is to define rules that correspond to the usual, permissible procedures for commissioning a device in a specific application environment.

[0062] The preceding connection of the device via the second connection to one or more second devices can be carried out in particular in the following ways:

[0063] - Connecting peripheral devices via a local interface, e.g. USB, SPI, RS232, SD card interface

[0064] - Establishing a power transfer with a power supply unit (in particular USB Power Delivery or a wireless / inductive power supply such as a wireless Qi charging interface).

[0065] - Connecting expansion modules (e.g., connected expansion modules of an industrial component such as a programmable logic controller (PLC) connected via a backplane bus). The expansion module can, in particular, be a communication module (e.g., an SG communication module).

[0066] - Attaching or mounting a tool on a machine tool (e.g. milling head, drill)

[0067] - Connections to a network (connection to a mobile network, e.g. a public mobile network, a 5G campus network, a 5G network slice, a specific WLAN network with network access authentication, a specific enterprise network with IEEE 802. IX network access control,

[0068] - Cryptographically protected, authenticated connection with servers, cloud services, other devices via a communication network (Internet, enterprise network, factory network, campus network).

[0069] In a further development of the invention

[0070] - Sending the connection request to the unit and / or

[0071] - The unit checking the device connection information and / or the device authentication information.

[0072] Alternatively, the above steps can be performed by another unit, such as another server.

[0073] In a further development of the invention, the device authentication information is embodied as a device fingerprint of the second device. Preferably, the second device, with which the second connection is to be established, can cryptographically authenticate itself to the first device, as is known, for example, from USB 3.0 or PCIe.

[0074] Furthermore, it is possible for the second device to be identified based on a device fingerprint, i.e., based on an indirect device-specific property, in particular an analog property of the device interface, which depends on the physical properties of the electronic interface components used or which result from manufacturing tolerances, in particular deviations of resistances, capacitances, and inductances from their nominal values. Frequency dependence can be taken into account.

[0075] Preferably, the device that establishes the first connection to the unit can authenticate itself cryptographically, such as TLS, DTLS, IPsec / IKEv2, MACsec or OPC UA.

[0076] In a further development of the invention, the device authentication information is cryptographically protected, in particular by a cryptographic signature. In one variant, it can also be protected by a symmetric cryptographic checksum, i.e., a message authentication code (MAC), or be designed as a verifiable credential or verifiable presentation.

[0077] The invention also comprises a device for carrying out the method according to the invention described above, comprising:

[0078] - A transmitting unit configured to transmit the connection request, wherein the connection request is assigned the cryptographically protected device connection information and the device authentication information, wherein the device connection information indicates the at least one second connection from the device to the at least one second device, which existed earlier, wherein the device authentication information authenticates the device and

[0079] - A connection unit, designed to form the first cryptographically protected connection of the device to the unit depending on the result of checking the device connection information and the device authentication information, wherein in particular the formation of the cryptographically protected connection of the device (D) to the unit (E) also takes place depending on a second device connection information, wherein the first device connection information (CD-A) and the second device connection information are checked for consistency.

[0080] The invention also includes a method for forming a first cryptographically protected connection of a unit to a device, from the perspective of the unit, comprising the steps of:

[0081] - Receiving a connection request from the device, wherein the connection request is associated with cryptographically protected device connection information and device authentication information, wherein the device connection information indicates which at least one second connection from the device to at least one second device existed earlier, wherein the device authentication information authenticates the device and

[0082] - Forming the first cryptographically protected connection of the unit to the device depending on a result of checking the device connection information and the device authentication information, wherein in particular the formation of the cryptographically protected connection of the device (D) to the unit (E) also takes place depending on a second device connection information, wherein the first device connection information (CD-A) and the second device connection information are checked for consistency.

[0083] The invention also comprises a unit for carrying out the method according to the invention described above, comprising:

[0084] - A receiving unit, designed to receive a connection request from the device, wherein the connection request is assigned the cryptographically protected device connection information and the device authentication information, wherein the device connection information indicates the at least one second connection from the device to the at least one second device, which existed earlier in time, wherein the device authentication information authenticates the device and

[0085] - A connection unit, designed to form the first cryptographically protected connection of the unit to the device depending on the result of the checking of the device connection information and the device authentication information, wherein in particular the formation of the cryptographically protected connection of the device (D) to the unit (E) also takes place depending on a second device connection information, wherein the first device connection information (CD-A) and the second device connection information are checked for consistency.

[0086] In summary, the invention offers the advantage that authorization information that allows specific access by the device, in particular to a unit such as a provisioning server for performing a provisioning process, does not need to be explicitly configured for a specific device. Instead, this information can be inferred indirectly.

[0087] BRIEF DESCRIPTION OF THE DRAWINGS

[0088] The special features and advantages of the invention will become apparent from the following explanations of several embodiments based on the schematic drawing.

[0089] It shows

[0090] Fig. 1 is a schematic representation of a device and a unit for carrying out the method according to the invention.

[0091] DETAILED DESCRIPTION OF THE INVENTION

[0092] Fig. 1 shows a device D for carrying out the method according to the invention from the perspective of the device D and a unit E for carrying out the corresponding method according to the invention from the perspective of the unit E.

[0093] The device is shown in Fig. 1 as an industrial IoT device D (Device) with an app execution environment RTE (Runtime Environment) for executing applications App. Furthermore, the following are:

[0094] - an operating system OS (operating system),

[0095] - a processor CPU,

[0096] - a first memory unit RAM,

[0097] - a second storage unit Flash,

[0098] - an input / output unit I / O for connecting sensors and / or actuators or extension modules and

[0099] - a network interface NWIF (network N interface) is provided.

[0100] Furthermore, a power management unit PMU (Power Management Unit) is provided, which is connected to an external power supply PS (Power Supply).

[0101] An external 5G communication modem 5G-M and an AI accelerator AIA (artificial intelligence accelerator), e.g. a hardware-based inference engine, are connected via IO interfaces (10: input / output).

[0102] An app can submit an application programming interface (API) (App Request, AR) to the app execution environment (RTE). The app can be present on the device, e.g., as part of device firmware, or it can be an app downloaded and installed onto the device.

[0103] According to the invention, the app execution environment (RTE) manages information about previously and / or currently connected second devices (Connected Device Monitor and Ledger CDML). The device connection information of connected second devices, which can also be referred to as components, is preferably provided directly by the second device, i.e., the component, e.g., information about the manufacturer, device type, and serial number.

[0104] Preferably, a second device, i.e., a component, can be cryptographically authenticated, as is known, for example, from USB 3.0 or PCIe. Furthermore, it is possible for a connected component to be identified based on a device fingerprint, i.e., based on an indirect device-specific property (e.g., analog properties of the device interface, which depend on the physical properties of the electronic interface components used, resulting from manufacturing tolerances, e.g., deviations of resistances, capacitances, inductances, from their nominal value).

[0105] Preferably, the device, ie the industrial IoT device D, can authenticate itself cryptographically, such as TLS, DTLS, IPsec / IKEv2, MACsec or OPC UA.

[0106] This information (optionally filtered and pre-processed) is cryptographically protected and confirmed (CD-Attest) by creating cryptographically protected device connection information, also referred to as connected device attestation information (CD-A), which is created using an attestation key. Furthermore, the device can authenticate itself using a device authentication key (D-Auth). The two keys are preferably different; however, a common key can generally be used for device authentication and connected device attestation. This functionality can be implemented using a secure element (e.g., crypto controller, security processor, trusted platform module), a trusted execution environment (Trusted Execution Environment), or a confidential computing enclave (e.g., Intel SGX enclave).It is possible to use a common secure element, a common trusted execution environment, or a common confidential computing enclave for device authentication and connected device attestation. It is also possible to use separate secure elements, separate trusted execution environments, or separate confidential computing enclaves for device authentication and connected device attestation. This has the advantage that device authentication and connected device attestation are separated from each other, thus achieving a particularly high level of tamper protection.

[0107] The request message Req is transmitted to the unit E, in particular another device E or a service E. In addition to the actual request AR of the app, it includes the device authentication information DA and the inventive connected device attestation information CD-A, which describes which other, second devices were previously connected to the device D to be connected, in particular via a local device interface. The connected device attestation information CD-A and the device authentication information D are checked CD-AC, DC (check) by the device E or service E to which the connection is to be made, and depending on this, the request Req is processed in the request handler RH P-AR (Process AR), rejected P-AR, or modified P-AR, i.e. processed to a limited extent P-AR.

[0108] The request Req preferably comprises the three elements: the app's request AR, the device authentication information DA, and the connected device attestation information CD-A. However, it is also possible for these three elements to be referenced, e.g., by means of a URI or a cryptographic identifier, in particular a cryptographic hash value of the respective element. In particular, the connected device attestation information CD-A according to the invention can also be transmitted or provided separately so that it can be assigned to a request Req, in particular by including a reference to the connected device attestation information CD-A in the request message.

[0109] The device authentication information DA can also be app-specific device authentication information. For example, the device D can use different device authentication keys for different apps. Depending on the app from which a request AR originates, a device authentication key assigned to the respective app is selected or determined and used to generate the device authentication information.

[0110] The device authentication information DA of the request message can be a digital signature. The digital signature can protect the request message, which includes the request AR and the attestation or attestation reference. It is also possible for the device authentication information and the attestation or attestation reference to be used in an authentication and key agreement to establish a cryptographically protected, authenticated transmission channel over which the request AR is transmitted.

[0111] The request may in particular concern:

[0112] - Registration of the device in a device database (as an authorized device)

[0113] - Issuing a credential (digital certificate, security token) for the requesting device

[0114] - Generate and provide a cryptographic key for the requesting device

[0115] - Formation of a blockchain transaction (distributed ledger, distributed database) by an accessing blockchain oracle (i.e. the accessing device realizes a

[0116] Bloc kchain client / Bloc kchain wallet)

[0117] - Establishment of a network access connection (e.g. PDP context or PDU session of a mobile radio system) to a network infrastructure (network access control, 3GPP 5G Primary Authentication)

[0118] - Requesting a network access connection (e.g. PDP context or PDU session of a mobile system) to access a slice of the network infrastructure (e.g. 3GPP 5G Secondary Authentication)

[0119] - Requesting an app download, firmware updates

[0120] - Providing or requesting a sensor measurement value that records a physical quantity of a technical system (e.g. temperature, force, pressure, speed of movement, flow velocity, flow rate, speed, torque)

[0121] - Providing or requesting a control command to control an actuator in order to influence a technical system (e.g. machine tool, drive, heating element).

[0122] - Providing or requesting recipe data or project planning data for the configuration of a control unit, a machine or a system.

[0123] Although the invention has been illustrated and described in detail by the embodiments, the invention is not limited by the disclosed examples and other variations can be derived therefrom by a person skilled in the art without departing from the scope of the invention.

Claims

Patent claims 1. Method for establishing a first cryptographically protected connection between a device (D) and a unit (E), comprising the steps: - Sending a connection request (Req) by the device (D), wherein the connection request (Req) is associated with a cryptographically protected device connection information (CD-A) and a device authentication information (DA), wherein the device connection information (CD-A) indicates which at least one second connection from the device (D) to at least one second device existed earlier in time, and wherein the device authentication information (DA) authenticates the device (D) and - Establishing the first cryptographically protected connection of the device (D) with the unit (E) depending on the result of a check (P-AR) of the device connection information (CD-A) and the device authentication information (DA), wherein the establishment of the cryptographically protected connection of the device (D) with the unit (E) is also dependent on a second device connection information, wherein the first device connection information (CD-A) and the second device connection information are checked for consistency.

2. Method according to claim 1, wherein the device connection information (CD-A) additionally indicates to which at least one second device the at least one second connection currently exists.

3. Method according to one of the preceding claims, wherein the device connection information (CD-A): - an identifier, in particular relating to a device manufacturer, device type and / or device serial number, and / or - an authentication credential, in particular a certificate, a cryptographic key and / or a exhibits the password hash of at least one second device to which at least one second connection existed.

4. Method according to one of the preceding claims, wherein the connection request (req) is additionally assigned supplementary information which, in particular, specifies: at what time and / or - over what period of time and / or - via which device interface and / or in combination with which at least one third connection the at least one second connection existed.

5. Method according to any one of the preceding claims, wherein the device connection information (CD-A) is from: - the device (D) and / or - is provided to an external unit.

6. Method according to any one of the preceding claims, wherein the second device is: - a peripheral device and / or - an extension module and / or - a tool of a machine tool and / or - an IoT device and / or - a second device is formed that is mechanically connected to the device (D).

7. Method according to any one of the preceding claims, wherein the unit (E) is: - a server (E) and / or - a cloud service (E) and / or - an edge device (E) and / or - a control unit (E) and / or - a control function (E) and / or - a third device (E), in particular a second IoT device (E) and / or - a communication network (E) and / or - an onboarding network (E) and / or - a provisioning server (E) and / or - a device management server (E) is trained.

8. A method according to any of the preceding claims, wherein rules are used for checking (P-AR) the connection request (reg), based on which: - an admission or - a limited permit is granted for the formation of the first cryptographically protected connection between the device (D) and the unit (E).

9. Method according to any one of the preceding claims, wherein: The connection request (req) is sent to the unit (E) and / or The unit (E) checks (P-AR) the device connection information (CD-A) and / or the device authentication information (DA).

10. Method according to any of the preceding claims, wherein the device authentication information (DA) is configured as a device fingerprint of the device (D).

11. Method according to any of the preceding claims, wherein the device authentication information (DA) is cryptographically protected, in particular by a cryptographic signature.

12. Device (D) for carrying out a method according to any one of claims 1 to 11, comprising: - A transmitting unit configured to send the connection request (reg), wherein the connection request (rea) is associated with the cryptographically protected device connection information (CD-A) and the device authentication information (DA), wherein the device connection information (CD-A) indicates the at least one second connection from the device (D) to the at least one second device that existed earlier, and wherein the device authentication information (DA) authenticates the device (D) and - A connection unit configured to establish the first cryptographically protected connection of the device (D) with the unit (E) depending on the result of the check (P-AR) of the device connection information (req) and the device authentication information (DA), wherein the establishment of the cryptographically protected connection of the device (D) with the unit (E) also occurs depending on a second device connection information, wherein the first device connection information (CD-A) and the second device connection information are checked for consistency.

13. Method for establishing a first cryptographically protected connection between a unit (E) and a device (D), comprising the steps: - Receiving a connection request (req) from the device (D), wherein the connection request (req) is associated with a cryptographically protected device connection information (CD-A) and a device authentication information (DA), wherein the device connection information (CD-A) indicates that at least one second connection from the device (D) to at least one second device existed earlier in time, and wherein the device authentication information (DA) authenticates the device (D) and - Establishing the first cryptographically protected connection of the unit (E) with the device (D) depending on the result of a check (P-AR) of the device connection information (CD-A) and the device authentication information (DA), wherein the establishment of the cryptographically protected connection of the device (D) with the unit (E) also takes place depending on a second device connection information, wherein the first device connection information (CD-A) and the second device connection information are checked for consistency.

14. Unit (E) for carrying out a method according to claim 13, comprising: - A receiving unit configured to receive a connection request (reg) from the device (D), wherein the connection request (req) is associated with the cryptographically protected device connection information (CD-A) and the device authentication information (DA), wherein the device connection information (CD-A) indicates the at least one second connection from the device (D) to the at least one second device that existed earlier, and wherein the device authentication information (DA) authenticates the device (D) and - A connection unit configured to establish the first cryptographically protected connection of the unit (E) with the device depending on the result of checking (P-AR) the device connection information (CD-A) and the device authentication information (DA), wherein the establishment of the cryptographically protected connection of the device (D) with the unit (E) is also dependent on a second device connection information , where the first device connection information (CD-A) and the second device connection information are checked for consistency.