l Networks that are accessible to many individuals
Some options to secure your datalogger from mistakes or tampering include:
l Sending the latest operating system to the datalogger. See Updating the operating system
(p. 109) for more information.
l Disabling unused services and securing those that are used. This includes disabling HTTP,
HTTPS, FTP, Telnet, and Ping network services (Device Configuration Utility > Deployment
> Network Services tab). These services can be used to discover your datalogger on an IP
network.
NOTE:
FTP, Telnet, and Ping services are disabled by default.
l Setting security codes (see following information under "Security Codes").
l Setting a PakBus/TCP password. The PakBus TCP password controls access to PakBus
communication over a TCP/IP link. PakBusTCP passwords can be set in Device
Configuration Utility.
l Disabling FTP or setting an FTP username and password in Device Configuration Utility.
l Setting a PakBus encryption (AES-128) key in Device Configuration Utility. This forces
PakBus data to be encrypted during transmission.
l Disabling HTTP/HTTPS or creating a .csipasswd file to secure HTTP/HTTPS (see
Creating a .csipasswd file (p. 103) for more information).
l Enabling HTTPS and disabling HTTP. To prevent data collection via the web interface, both
HTTP and HTTPS must be disabled.
l Tracking Operating System, Run, and Program signatures.
l Encrypting program files if they contain sensitive information (see CRBasic help
FileEncrypt() instruction or use the CRBasic Editor File menu, Save and Encrypt
option).
l Hiding program files for extra protection (see CRBasic help FileManage() instruction).
l Monitoring your datalogger for changes by tracking program and operating system
signatures, as well as CPU, USR, and CRD file contents.
l Securing the physical datalogger and power supply under lock and key.
WARNING:
All security features can be subverted through physical access to the datalogger. If absolute
security is a requirement, the physical datalogger must be kept in a secure location.
8. Maintaining your datalogger 101
To Next Page
Loading...
