Manual

WI-I/O 9-x_WI-I/O-EX-1-S-x 2.16 Page 55
over-written.
• You can change the security key in the configuration files simply by entering a new security key in
the security key window. You will be prompted to confirm the new security key. If the
configuration files are password-protected, you will be asked for the password. Note that if you
change the security key, it will not match the security key previously loaded into existing modules.
• If you want to change a configuration, we recommend that you change the archived configuration,
and then download the configuration onto the module. The archived configuration already has the
valid security key.
• If you lose the archived configuration, you can upload the configuration from a module, but you
cannot upload a security key. That is, you can upload the module configuration, view it, change it
- but if you don’t know the original security key, the old key will be over-written when you
download the new configuration. This module will no longer communicate with other modules in
the system as the security key is different.
The security options provide security against a “hacker” in the following way:
 A hacker cannot listen-in to radio messages without the security key to decrypt the radio messages.
Similarly, a hacker cannot force outputs by transmitting a radio message to a module without the
security key.
 A hacker cannot access the security key from an installed module or from the configuration files.
 The archived configuration files cannot be changed, downloaded or uploaded without the
password.
Warning!!
These security options provide a high level of security, but no data-security system can provide
“100% protection”. But it does make it very difficult for someone to interfere with the WI-I/O
9-x system - difficult to the point where there would be many easier alternate ways to cause
malicious damage.
The password must be kept in a secure place. Security procedures need to be adopted. If staff
with access to the password leaves your organization, we recommend that the password be
changed.
We recommend that you use a random 8-character string for the security key and that you do not
record the key. It is not necessary to know what the security key is. The key will be recorded in
the archived configuration files, and therefore the configuration files should be held in a secure
place and backed up.
The security key does not prevent a hacker uploading a configuration from a module and
downloading with a new security key. This module will no longer operate with other modules in
the system. To prevent this, unauthorized access to modules must be prevented.
If you lose the configuration files, you can regenerate these by uploading the configuration from every
module in the system into a new project with a new security key. After uploading each module,
download the configuration with the new security key.