RTCU Security Features

Top  Previous  Next

The security features are a collection of features in the RTCU devices that can be used to prevent unauthorized access to the device as well as protecting the data and communication against eavesdropping and tampering.

 

Network security with TLS

For NX32L devices, it is possible to enable network security through the use of the Transport Layer Security (TLS) protocol and X509 certificates.

The TLS protocol enables Client-Server applications to use encryption when communicating across a network.

TLS v1.2, v1.1 and 1.0 are supported

 

The SMTP, MQTT and raw TCP/IP sockets can be configured to use TLS.

 

Encrypted RTCU Communication Hub communication

TLS is fully supported using the RTCU Communication Hub and is the preferred approach for safe communication.
For non NX32L devices the communication can be encrypted by configuring an encryption key with the RTCU Communication Hub Settings dialog or sockSetGWParm.

 

Data encryption

Data encryption is achieved with the Advanced Encryption Standard (AES).

The AES is a specification for the encryption of electronic data established by the U.S. government.

A key length of 128 bit is supported. See rdEncrypt128 and rdDecrypt128 for more information.

 

Encrypted include files

To make it possible to share a parts of a project without providing access to the actual code, encrypted include files can be used.

 

Access restriction

It is possible to use passwords to restrict the access to the RTCU device.

Without the correct password, only type of device, the firmware version, serial number and debug messages can be read from the device.

For more information about passwords, see boardSetPassword and boardSetPasswordAlt.