Denied Access events in CyberLocks
By default, CyberLocks do not record events where the key is not permitted access. This includes events such as:
- Out of schedule for lock
- Key expired or out of schedule
- Access Denied - No Permissions
- Access count expended
CyberLocks always record these events:
- Key Disabled
- Access code failed
CyberKeys always record No Access events in their audit trail. They are recorded as events such as Out of Schedule for Lock, Access Denied - No Permissions, and others. If this option is selected, keys in this subsystem will also write an Access Denied event to the lock's audit trail.
Caution: When a CyberKey writes the Access Denied event to the lock, it invokes a Tamper Delay in the lock. The Tamper Delay increases the amount of time a key must be kept in contact with a lock prior to it unlocking. With each succeeding Tamper Delay, the CyberLock imposes a longer delay responding to a CyberKey. With each succeeding Access Denied event the Tamper Delay increases, up to as long as 15 seconds with Generation 1 CyberLocks or no more than 2 seconds on Generation 2 CyberLocks. A CyberLock with a long Tamper Delay may cause unsuspecting key holders to conclude that the CyberLock is "dead" because of its lack of response. If this feature is enabled, it is important to train keyholders about Tamper Delay.
To clear the Tamper Delay, use a key with known access to the CyberLock and hold it in the CyberLock until it opens.
Tamper Delay in Generation 2 CyberLocks does not exceed 2 seconds.
Note: With the exception of lost key or fob events, CyberLock Blue does not record access denied events except lost key or fob events.
