LabVIEW Shared Variables Network Publish Default Access Control Lacks Localhost Restriction

When a LabVIEW Shared Variable is published to the network, the developer must manually configure read and write access lists to prevent unintended exposure. The default publish settings do not restrict the variable to the local host, and the interface does not provide an automatic “localhost‑only” option. This leaves a permission boundary that depends on the user remembering to adjust the access lists or enable authentication for each variable.

The goal is to determine whether the Shared Variable Engine can be configured to enforce a localhost‑only binding by default, or to apply a blanket restriction that overrides the per‑variable access lists when no explicit network range is specified.

• Can the publish tab be preset to limit access to 127.0.0.1 or ::1 for all newly created shared variables?
• Is there a project‑wide or LabVIEW‑wide setting that forces the Shared Variable Engine to ignore external interfaces unless a specific IP range is added?
• If the “Require authentication” checkbox is enabled, does it implicitly restrict connections to the local machine, or must an access list still be defined?