Data logger security

Data logger security concerns include:

  • Collection of sensitive data
  • Operation of critical systems
  • Networks that are accessible to many individuals

Some options to secure your data logger from mistakes or tampering include:


All security features can be subverted through physical access to the data logger. If absolute security is a requirement, the physical data logger must be kept in a secure location.


Transport Layer Security (TLS) is an internet communications security protocol. TLS settings are necessary for server applications, not for client applications.

Example server application instructions include:

  • HTTPS server
  • DNP3()

Example client application instructions include:

  • HTTPGet(), HTTPPut() and HTTPPost()
  • EmailRelay()
  • EmailSend() and EmailRecv()
  • FTPClient()

Use the Device Configuration Utility to enable and set up TLS. See Deployment > Datalogger > TLS tab.

Security codes

The data logger employs a security scheme that includes three levels of security. Security codes can effectively lock out innocent tinkering and discourage wannabe hackers on all communication links. However, any serious hacker with physical access to the data logger or to the communications hardware can, with only minimal trouble, overcome the five-digit security codes. Security codes are held in the data logger ClosedSettings EditorAn editor for observing and adjusting settings. Settings Editor is a feature of LoggerNet|Connect, PakBus Graph, and Device Configuration Utility..

The preferred methods of enabling security include the following:

Alternatively, in CRBasic the SetSecurity() instruction can be used. It is only executed at program compile time. This is not recommended because deleting SetSecurity() from a CRBasic program is not equivalent to SetSecurity(0,0,0). Settings persist when a new program is downloaded that has no SetSecurity() instruction.

Up to three levels of security can be set. Valid security codes are 1 through 65535 ( 0 confers no security). Security 1 must be set before Security 2. Security 2 must be set before Security 3. If any one of the codes is set to 0, any security code level greater than it will be set to 0. For example, if Security 2 is 0 then Security 3 is automatically set to 0. Security codes are unlocked in reverse order: Security 3 before Security 2, Security 2 before Security 1.

Functions affected by security codes

Function Security code 1 set Security code 2 set Security code 3 set
data logger program Cannot change or retrieve All communications prohibited

Settings editor
and Status table

Writable variables cannot be changed
Setting clock unrestricted Cannot change or set
Public table unrestricted Writable variables cannot be changed
Collecting data unrestricted unrestricted

See Security(1), Security(2), Security(3) for the related fields in the Settings Editor.

For additional information on data logger security, see: