Audit Trail Events from FlashLocks and Fobs
FlashLock System Events
Fob Access Events
Fob System Events
FlashLock Server Events
| Event | Description | |
| 4 | Fob access granted | * |
| 6 | Flash access granted | Access was granted by flash pattern |
| 7 | Lock opened | The FlashLock sensed the knob was turned away from the home position |
| 8 | Lock closed | The FlashLock sensed the knob was returned to the home position |
| 9 | Unknown flash pattern | The detected flash pattern did not match any of the current valid patterns |
| 10 | Device ID addition failed | An attempt to add a fob or CyberKey Flash via master fob failed. Note: This event is only possible from FlashLocks which have used a master fob. Master fobs are not supported by CyberAudit-Web. |
| 11 | Fob added by master fob | A fob ID was captured into the FlashLock's list of fob IDs following access from the master fob. Note: This event is only possible from FlashLocks which have used a master fob. Master fobs are not supported by CyberAudit-Web. |
| 12 | Fob removed by master fob | A fob ID was deleted from the FlashLock's list of fob IDs following access from the master fob. Note: This event is only possible from FlashLocks which have used a master fob. Master fobs are not supported by CyberAudit-Web. |
| 13 | Master ID captured | A master fob accessed an unprogrammed FlashLock. The FlashLock captured the FlashLock's access code. Note: This event is only possible from FlashLocks which have used a master fob. Master fobs are not supported by CyberAudit-Web |
| 14 | Flash code expired | The current flash code in the FlashLock is no longer valid because too much time has elapsed |
| 15 | Padlock opened | The FlashLock padlock sensed the knob was turned to an open position |
| 16 | Unprogrammed lock - flash access granted | This event indicates the lock has no valid flash access codes and should be returned for servicing |
| 17 | Out of access schedule for fob | The FlashLock found the fob in its list of fobs but the schedule indicates the fob may not open the FlashLock at this time. This event does not occur in FlashLocks programmed from CyberAudit-Web. |
| 18 | Fob not in access list | The FlashLock did not find the fob in its list of fobs. This event does not occur in FlashLocks programmed from CyberAudit-Web. |
| 19 | Lost fob - access denied | The fob was found in the FlashLock's list of lost fobs. |
| 20 | No flash access codes in lock | A programmed FlashLock will not grant access because it has no valid flash access codes in its memory. |
| 22 | Unprogrammed lock - fob access granted | This occurs when an unprogrammed fob attempts to access an unprogrammed FlashLock. |
| 256 | FlashLock Downloaded | The FlashLock Assistant app fetched the audit trail events from the FlashLock and sent them to the server. |
FlashLock Access Events
Fob Access Events
Fob System Events
FlashLock Server Events
| Event | Description | |
| -65 | Soft reset | A reset triggered internally or by command from a FlashLock communicator. |
| -66 | Low Battery | The FlashLock recorded a low battery condition following one of its hourly battery checks. |
| -67 | Critical Battery | The FlashLock recorded a critical battery condition. At this point, the FlashLock may not be able to open or communicate. |
| -68 | Power reset | A reset triggered by removing and restoring power to the FlashLock. This event occurs when removing and replacing the battery. |
| -25 | Event rollover | All event data memory has been written so the FlashLock will begin overwriting its oldest event records. |
| -30 | MF Reset KCAddr | The flash access pointer has been reset in the lock. This is a feature of a system using a master fob. Master fobs are not supported by CyberAudit-Web. |
| -31 | MF Clear FID | A fob ID has been removed from the access list in the FlashLock. This is a feature of a system using a master fob. Master fobs are not supported by CyberAudit-Web. |
The following events represent error conditions. If any occur, please contact your FlashLock supplier.
| Event | Description | |
| -16 | Format Data Flash | * |
| -19 | BadID | * |
| -28 | BadKCAddr | * |
| -29 | BadEvtAddr | * |
| -32 | Bad KC Param | * |
FlashLock Access Events
FlashLock System Events
Fob System Events
FlashLock Server Events
| Event | Description | |
| 130 | Fob ID added to FlashLock list | A fob was added to a FlashLock fob list when the FlashLock was in master fob 'add' mode. This operation requires the use of a master fob. Master fobs are not supported by CyberAudit-Web. |
| 131 | Fob ID removed from FlashLock List | A fob was removed from a FlashLock fob list by a master fob. This operation requires the use of a master fob. Master fobs are not supported by CyberAudit-Web. |
| 133 | Authorized to open | * |
| 135 | Before start or after stop of fob schedule | Access was denied because the attempted access was requested before the fob was to start working or after the fob has expired. |
| 137 | Out of schedule for fob | The fob found the lock ID in its lock list but the time of contact with the lock was not
during the valid operating time of the associated schedule for one of these reasons:
|
| 138 | Access denied - no permissions | The ID of the FlashLock was not found in the fob's lock list. |
| 140 | Hardware mismatch | Indicates a manufacturing difference between lock and key. This event should not normally occur. |
| 141 | Unprogrammed lock - authorized | An unprogrammed fob will gain access to an unprogrammed FlashLock |
| 142 | Fob authorization blocked by lock | The fob has been disabled by the lock because it was designated as lost and the FlashLock was designated as a disabling point. |
| 143 | Fob access denied by lock | The fob attempted to access the FlashLock but the FlashLock denied access. This would most likely occur if the access code used by the fob is not recognized by the FlashLock. |
FlashLock Access Events
FlashLock System Events
Fob Access Events
FlashLock Server Events
| Event | Description | |
| -1 | Soft Reset | A reset triggered internally or by command from a FlashLock communicator |
| -2 | Low battery | The fob's battery was below its threshold during one of the key's periodic reads or during a lock opening. |
| -3 | Dead battery | The battery voltage dropped below operating voltage during one of it periodic reads or during a lock opening. |
| -4 | Periodic battery check | The fob reads and records its battery level daily, after midnight local time. |
| -5 | Power reset | A reset triggered by removing and restoring power to the fob. This event occurs when removing and replacing the battery. |
| -24 | Events cleared | After downloading audit events from the fob, those events are removed from the fob's memory. |
| -27 | Event rollover | All event data memory has been written so the fob will begin overwriting its oldest event records. This should not occur on fobs that are regularly updated with FlashLock Assistant. |
The following events represent error conditions. If any occur, please contact your FlashLock supplier.
| Event | Description | |
| -18 | Format data flash | * |
| -21 | BadID | * |
| -34 | Bad KCParam | * |
| -35 | Bad KCAddr | * |
| -36 | Bad EventAddr | * |
| -37 | Bad IDAddr | * |
FlashLock Access Events
FlashLock System Events
Fob Access Events
Fob System Events
These audit events are generated by the CyberAudit-Web server during requests for flash access. They may be viewed in the audit trail for the selected person or in reports.
| Event | Description | |
| 400 | Flash Access request approved | The server has approved access and returned a flash pattern to the requester. |
| 401 | Flash Access request denied - access expired | * |
| 402 | Flash Access request denied - out of schedule | The request for access was denied because it did not occur
during the valid operating time of the associated schedule
for one of these reasons:
|
| 403 | Flash Access device approved | The cell phone, tablet, or other device which requested flash access was approved and sent a browser cookie. That cookie is also stored on the server and associated with a person. Any subsequent flash access requests by that person will require using that browser with that cookie. |
| 404 | Flash Access device denied | The cell phone, tablet, or other device which requested flash access was not approved because the cookie on file did not match the one sent from the device browser. The cookie on-file can be reset from the Reset Flash Device click menu on the people list page. |
| 405 | PIN accepted for Flash Access | The person requesting flash access successfully entered their PIN. |
| 406 | Bad PIN | PIN entered did not match PIN record on server |
| 429 | New PIN requested | The person associated with the flash access request requires a PIN but does not have a valid one in the system. |
| 419 | New PIN accepted | A user, prompted to enter a new PIN, successfully confirmed the PIN after entering it a second time. The ValidiKey will send the new PIN to CyberAudit-Web to update the People record. |
| 436 | Flash Access success reported | The Flash Access user responded Yes to the web page that asked whether they were able to open the FlashLock. |
| 437 | Flash Access failure reported | The Flash Access user responded No to the web page that asked whether they were able to open the FlashLock. |
| 438 | Browser cookie accepted | The user clicked Yes to accept the browser cookie. That person is now associated with the browser on a device. |
| 439 | Browser cookie declined | The user clicked No to decline the browser cookie. At this point there is no browser associated with that person. |
FlashLock Access Events
FlashLock System Events
Fob Access Events
Fob System Events
These events are generated by the server as a result of communications with FlashLock Assistant. They may be viewed in the audit trail for the portable link or in reports.
| Event | Description | |
| 407 | FA communicator - issue number requested | An unknown communicator (Android or PC) contacted the server. The server responded with a request for an issue number. |
| 408 | IR Encoder up-to-date | The server has verified the IR Encoder 10 has the correct firmware. |
| 409 | Connection made to known fob | The server has established a connection with a fob via FlashLock Assistant. The fob serial was found in the server database. |
| 410 | Connection made to known FlashLock | The server has established a connection with a FlashLock via FlashLock Assistant. The FlashLock serial was found in the server database. |
| 411 | Encoder firmware update requested | The server returned an updated firmware to FlashLock Assistant to load into the IR Encoder 10. |
| 412 | Encoder firmware updated | The firmware in the IR Encoder has been successfully updated. |
| 413 | Encoder firmware update failed | A firmware update for the IR Encoder 10 was attempted but failed. |
| 414 | Fob firmware update requested | The server returned an updated firmware to FlashLock Assistant to load into the fob. |
| 415 | Fob firmware updated | The firmware in the fob has been successfully updated. |
| 416 | Fob firmrmware update failed | A firmware update for the fob was attempted but failed |
| 417 | FlashLock firmware update requested | The server returned an updated firmware to FlashLock Assistant to load into the FlashLock. |
| 418 | FlashLock firmware updated | The firmware in the FlashLock has been successfully updated. |
| 420 | FlashLock firmware update failed | A firmware update for the FlashLock was attempted but failed. |
| 421 | Communicator issued | FlashLock Assistant returned a valid issue number. The communicator ID has been captured and saved in CyberAudit-Web and is now visible on the Portable Links listing page. |
| 422 | Communicator connected | A valid portable link connected to the server and is ready to communicate with a FlashLock or fob. |
| 423 | FlashLock configuration requested | The server has returned a configuration to load into the FlashLock. |
| 424 | FlashLock configured | The FlashLock configuration received from the server has been successfully loaded into the FlashLock. |
| 425 | FlashLock configure failed | The attempt to load a configuration into the FlashLock failed. |
| 426 | Fob configuration requested | The server returned a configuration to load into the fob. |
| 427 | Fob configured | The fob configuration received from the server has been successfully loaded into the fob. |
| 428 | Fob configure failed | The attempt to load a configuration into the fob failed. |
| 430 | New fob added | A new fob was added to CyberAudit-Web using the login number captured by FlashLock Assistant. |
| 431 | New FlashLock added | A new FlashLock was added to CyberAudit-Web using the login number captured by FlashLock Assistant. |
| 432 | Fob status captured | Battery voltage, event count, and other data was captured and recorded. The data may be viewed in the comm log for the fob. |
| 433 | FlashLock status captured | Battery voltage, event count, and other data was captured and recorded. The data may be viewed in the comm log for the FlashLock. |
| 434 | Connection made to unknown fob | The server has established a connection with a fob via FlashLock Assistant. It's serial number was not found in the server database. |
| 435 | Connection made to unknown FlashLock | The server has established a connection with a FlashLock via FlashLock Assistant. It's serial number was not found in the server database |
| 440 | FlashLock battery replacement | A FlashLock Assistant user reported replacing the battery in a FlashLock via the app. |
These events are generated by the Flash Access app or by server as a result of communications with the Flash Access app.
| Event | Description | |
| 441 | Flash Access Cache Update Requested | If the Flash Access app is allowed to store FlashLock permissions, This event will be recorded whenever the Flash Access app contacts the server for the latest set of FlashLocks and access permissions to store. |
| 442 | Offline Flash Access request approved | While offline, the Flash Access app found access permission for a FlashLock in its cache and generated the appropriate flashing pattern to open the lock. |
| 443 | Offline Flash Access request denied - access expired | An offline request to open a FlashLock was denied because the access permissions stored on the mobile device were expired. |
| 444 | Offline Flash Access request denied - out of schedule | An offline request to open a FlashLock was denied because the request occurred at a date or time that did not match the access times contained in the access permissions stored on the mobile device. |
| 445 | Offline PIN accepted for Flash Access | While offline, the Flash Access app prompted the user for a PIN and the correct PIN was captured and verified. |
| 446 | Offline Bad PIN | While offline, the Flash Access app prompted the user for a PIN but the one captured did not match the required PIN. |
| 447 | Offline Flash Access success reported | While offline, the user responded Yes when the Flash Access app asked whether they were able to open the FlashLock. |
| 448 | Offline Flash Access failure reported | While offline, the user responded No when the Flash Access app asked whether they were able to open the FlashLock. |
Additional links
