l
Monitoring your data logger for changes by tracking program and operating system
signatures, as well as CPU, USR, and CRD file contents.
l
Securing the physical data logger and power supply under lock and key.
WARNING:
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.
8.2.1 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 Settings Editor.
The preferred methods of enabling security include the following:
l
Device Configuration Utility: Security codes are set on the Deployment> Datalogger tab.
l
Network Planner: Security codes can be set as data loggers are added to the network.
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.
8. CR6 maintenance
112
