Honeywell Rapid Eye, Administrator'S Manual

Page: 204 / 294

204
Security for a Multi-Media System
Camera brightness. Video may be compromised when the brightness setting for a
camera is set too high or too low. Your PTZ cameras may be installed in a manner that they
can be turned away from the sun. See the
Rapid Eye™ Multi-Media Digital Video Recorder
Remote View Operator Guide .
Resetting the time/date. It can become complicated to analyze video after the time and
date of a Rapid Eye unit is changed. Recordings with incorrect time and date stamps could
be of no use in a court of law. You can trace events leading to such abuse of the unit, as
explained in
Tracing Events , page 210 . See also Unit Time Zone and Clock , page 64 .
Scheduling cameras to not record. See Scheduling Configuration , page 117 . This
feature is designed to efficiently use storage space. However, it can be abused to defeat
security. Use of the Boost button can override a camera that is not scheduled to record.
See
Figure 10-10 .
Countermeasures
An effective countermeasure strategy includes using Tamper Detection ( page 131 ) and
scheduling short Retrieval sessions on all cameras to check that Rapid Eye sites are
recording as they are configured to. One can also check if the environment has diminished
the effectiveness of a site. Verification can supplement tracing of events, as explained in
Tracing Events on page 210 . Boosted recording can override a unit to record a video feed
from a camera with recording turned OFF (see Figure 10-10 ).
Clearing Storage to Destroy Recorded Video and Deny Service
Clearing a unit’s storage or one of its streams destroys all recorded video and, during the
time that a unit is emptied (up to a few hours; see
Clearing Storage on page 141 ), the
Multi-Media unit cannot show live video, record video, send alarms, and so on. To do so
requires use of the Administrator account password.
Caution Honeywell recommends that you properly train users that have the right to
use the Clear Storage or Clear Stream buttons.
Compromising the Response to an Alarm
Scheduling alarms to not trigger. See Alarms and Scheduling on page 121 . This feature
is designed to control some obvious false alarms; but, it can be abused to defeat security.
Using more than one Multi db. Using a database, A, set to system password A with the
LVP utility, to create a site definition for units protected by system password B, can lead to
confusion if that user were to update security on the unit. The LVP utility does not change
the system password on the unit, updating security does. Updating security with another A
system password locks out all other View Operators who attempt to log on (using their
usual B database), thus jeopardizing their ability to respond to alarms and to make requests
for video clips/stills.