User manual

Toolbox 32 User Manual 1.47d www.cse-semaphore.com/mykingfisher
Page
202
Recovering A Secured RTU
For the highest level of security, the security driver can be loaded in flash memory (as usual). However, if the
passwords are lost and the port security level is 2 or higher, it will not be possible to reconfigure the RTU and
it may not be possible to communicate with the RTU (if the security level is 5). The RTU can be recovered if
passwords are lost by downloading firmware locally into port 1 of the CPU. Alternatively, the security driver
can be loaded in SRAM (the recommended method). There are two reasons for this:
• If the user database is updated and the security driver is re-downloaded into SRAM, the RTU will keep
its configuration. When the driver is downloaded into flash memory, the RTU is cold started and loses its
configuration.
• If passwords are lost, it is possible to recover the system by removing the CPU battery link and clearing
the SRAM. This will erase the driver and allow full access to the RTU. If the driver is loaded into flash
memory, it will not be erased by removing the battery link and the RTU will remain password protected.
Security Audit Trail
Whenever an RTU receives a command to unlock one of its ports, an event log is generated (if the RTU has
memory configured for event logs) called System Log. The usertype of the event log is set to the index
number of the user who unlocked the port. The index number is the number, or order, of the user in the user
database (as displayed by the Kingfisher Security program or the users.dbf file). A value of 0 indicates the
first user in the list, 1 indicates the second user etc.