Data Logger Security; Device Configuration Utility Security Check - Campbell CR300 Series Product Manual

If TimeIsBetween
NextScan
EndProg
Downloading operating systems over communications requires much of the available CR300
series memory. If the intent is to load operating systems via a communications link and have a
default.CR300 file in the CR300 series, the default.CR300 program should not allocate
significant memory, as might happen by allocating a large USR: drive. Also, do not auto-allocate
DataTable()
tables in
small fixed table sizes. Refer to
information about sending the operating system.

20.2 Data logger security

Data logger security concerns include:
Collection of sensitive data
l
Operation of critical systems
l
Networks that are accessible to many individuals
l

20.2.1 Device Configuration Utility Security Check

A Security Check is provided through Device Configuration Utility, starting with version 2.29. This
check helps you identify areas where security can be improved.
All suggestions shown in Device Configuration Utility are optional and no changes will be made
unless you make them. For example, Device Configuration Utility uses a simple set of criteria to
suggest a strong password. If you have your own criteria, you can use it. Because every
deployment can be different, Device Configuration Utility will provide you with the information
you need to ensure your data logger security is optimized for your application.
In general, green, blue, and red icons indicate password strength.
Green: strong password
l
Blue: weak password
l
Red: no password set
l
A strong password has the following:
Eight or more characters
l
One upper case letter
l
default.CR300
CRBasic Example 2:
(15,45,60,Sec) Then
instructions; if it is necessary to use
Sending an operating system to a remote data
example
SW12(1)
DataTable()
instructions, set
logger (p. 165) for
20. Installation 144