Data-at-Rest and Data-in-Transit Encryption Features on NI Linux Real-Time

Updated Aug 17, 2026

Reported In

Hardware

  • CompactRIO Controller
  • PXI Controller

Operating System

  • LabVIEW Real-Time (NI Linux Real-Time)

Issue Details

I want to know whether the NI Linux Real-Time controllers implement encryption for data at rest and data in transit. I need to understand what encryption capabilities are available by default and what options exist to secure stored data and network communications.

Solution

The NI Linux Real-Time controllers do not implement encryption for data at rest or data in transit by default. However, encryption can be enabled through software configuration and the use of supported security protocols.

For data at rest, it is possible to implement Linux Unified Key Setup (LUKS) encryption to protect data stored on the target using the Secured, Network-Attached Controller (SNAC) configuration. For additional information, please follow the steps below:

 

  1. Navigate to the NI Linux RT Secure Configuration Guide and NIST 800-171 Documentation
  2. Download the SNAC guide by clicking on SNAC.pdf under Assets as shown in the image below. 

This image shows how to download de SNAC PDF guide from the SNAC configuration GitHub page.

  1. Refer to the Optional SNAC Configuration Instructions section, which is part of the Chapter 21. Appendix 1: The Secured, Network-Attached ConfigurationNote: The SNAC configuration is only compatible with CompactRIO x64 and PXIe x64 devices, that support NI Linux Real-Time System Image 2025 Q2 and later. 

 

For data in transit, consider the following options:

  • Use secure communication protocols when developing LabVIEW applications. Configure communications over:
    • TLS (Transport Layer Security)
    • SFTP (SSH File Transfer Protocol)
    • SSH (Secure Shell)
    • WebDAV + HTTPS
  • Implement TLS or DTLS (Datagram Transport Layer Security) in non-LabVIEW applications to secure network communications.
These security mechanisms are not enabled automatically and must be configured as part of the application deployment and system hardening process.