![..//assets/img/kb/date.png](..//assets/img/kb/date.png)
A set of logs is kept by CyberAudit-Web in response to certain events. Use this log for tracking check-out and check-in of the key, activities, and troubleshooting. It is available for each ValidiKey vault or station from the drop-down menu in the ValidiKey 2 or ValidiKey 20 listing pages.
Message | Description | Data | |
1 | Controller reset | The ValidiKey system board reset | |
2 | Controller connection lost | The ValidiKey system board stopped responding | |
3 | Controller connected | The ValidiKey system board is now operating | |
9 | Display connection lost | The ValidiKey display module stopped responding. On the ValidiKey 2 this also affects RFID scans. | |
10 | Display connected | The ValidiKey display module is now operating | |
16 | Illegal Key Ring Removed | A Key Ring was removed from the vault where no mission was checked out for it. | Key Ring serial, person |
17 | Key removed | A CyberKey was removed from one of the ValidiKey key sockets | serial number, socket number, operating mode |
34 | Door opened | The ValidiKey vault door was opened | |
35 | Door closed | The ValidiKey vault door was closed | |
94 | Operating parameters updated | The configuration of the ValidiKey changed as a result of a change on the server. | Data categories updated |
204 | Unknown keypad input | Less than 4 digits were entered and submitted from the ValidiKey keypad | Digits entered |
205 | Known mission input | A mission number entered at the keypad was found in the ValidiKey database | Person, number of digits entered |
206 | Unknown mission input | Four or more digits were submitted by the keypad but the ValidiKey did not find the number in its database. | Digits entered |
209 | Key configured | The CyberKey was programmed with access permissions for the person and mission. | key serial, person |
210 | Key configuration failed | There was an error programming the CyberKey | key serial, person, failure info |
212 | Vault Full | A person with a CyberKey checked-out on a Mission is attempting to return the key to the ValidiKey but there are no empty keyports available. | |
213 | No key available | A person with permission to check out a key from a vault cannot do so because there are no valid keys in the vault | person name |
214 | Sync with server failed | The periodic connection to the server was unsuccessful | failure code, failure detail |
215 | Valid key inserted | A known CyberKey that is in the list of valid CyberKeys for the ValidiKey vault. | person |
216 | Invalid key inserted | A known, invalid CyberKey was inserted or found in one of the Vault key ports. This includes CyberLock Programmers, Grand Masters, and CyberKeys with replaceable batteries older than the CK-IR7. | key serial |
217 | Unknown key inserted | A CyberKey was inserted that was neither in the list of known valid CyberKeys nor a known invalid key. | key serial |
218 | Key disabled | The ValidiKey cleared the progamming from the valid CyberKey just inserted. This checks in the mission associated with the key. | key serial, person name |
219 | 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. | Person, Number of digits entered |
220 | PIN verified | A person with a PIN successfully entered it when prompted. | Person, Number of digits entered |
221 | Bad PIN | A person with a PIN did not enter the PIN on record in the ValidiKey system. | Person, Number of digits entered |
222 | Known card scan | A known RFID card was scanned at the ValidiKey reader. | Person, card ID |
223 | Unknown card scan | An unknown RFID card was scanned at the ValidiKey reader. | Card ID |
224 | Out of schedule for vault | A person with permissions to the ValidiKey vault is not permitted to check out a key at the time the RFID card was scanned or the mission number was entered. | Person name |
225 | Key downloaded | The audit trail was captured from a CyberKey | serial number |
226 | CAW connection established | The periodic connection to the server was re-established. | |
227 | ValidiKey system startup | The ValidiKey system completed its startup process. | |
228 | Access granted | The door solenoid on a ValidiKey vault has been activated so the user may open the door. | person name |
229 | New PIN requested | The person associated with the RFID access card or mission number requires a PIN but does not have a valid one in the system. The ValidiKey has prompted the person to enter a new PIN. | person name |
230 | ValidiKey firmware update completed | One of the ValidiKey modules received an update | module name, new version |
231 | ValidiKey firmware update failure | ValidiKey failed to update the software running in one of its modules. | module name, failure description |
232 | Key firmware update completed | A CyberKey successfully received updated firmware | key serial, new version |
233 | Key firmware update failure | The ValidiKey failed to update one of the software components on a CyberKey | key serial, component name, failure description |
235 | Door left open | The ValidiKey vault door has been open without vault activity for longer than the alarm time set in the properties page of the ValidiKey 2 or ValidiKey 20. | |
236 | Admin session started | A designated manager of the ValidiKey 2 or the ValidiKey 20 entered the admin menu on the ValidiKey 2 or the ValidiKey 20. | person name |
237 | Admin door access granted | The ValidiKey granted access to a ValidiKey 2 or ValidiKey 20 Manager to insert a USB drive, to add or remove CyberKeys, or perform other activities from the Admin Menu. | person name |
238 | Network settings updated | A ValidiKey 2 or ValidiKey 20 manager changed network settings on the ValidiKey. | settings changed |
239 | Admin session closed | The manager logged out of the ValidiKey 2 or ValidiKey 20. | person name, logged out or timed out |
240 | Key records updated | The ValidiKey updated its cache from CyberAudit-Web | Number of records added and deleted |
241 | Card scan received | An RFID card was received while the ValidiKey was in unconfigured or factory mode. | |
242 | Clock updated | The ValidiKey adjusted its clock setting based on time received from the CyberAudit-Web server. | The number of seconds adjusted plus or minus |
243 | System updated from USB configuration | ||
244 | Settings updated from server | ||
246 | No permission for vault | This indicates no permission was granted to the vault in the Access Matrix. | |
247 | System restart | The ValidiKey 20 detected a high memory use condition and restarted to free memory. This should be infrequent. |