# Nitrokey HSM - Audit logs **URL:** \ **Category:** HSM\ **Created:** [January 29, 2023, 10:13pm UTC](https://support.nitrokey.com/t/nitrokey-hsm-audit-logs/4790 "2023-01-29T22:13:18Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![baovu](https://support.nitrokey.com/letter_avatar_proxy/v4/letter/b/67e7ee/32.png) [@baovu](https://support.nitrokey.com/u/baovu)\ **Post date:** [January 29, 2023, 10:13pm UTC](https://support.nitrokey.com/t/nitrokey-hsm-audit-logs/4790/1 "2023-01-29T22:13:18Z")
Is there a way to make the HSM produce audit logs in a non-volatile memory portion of the Nitrokey? Similar to how [Logs](https://developers.yubico.com/YubiHSM2/Concepts/Logs.html) does it. Each operation on the HSM is logged with a hash value, making verification of the logs possible. We would like to use nitrokey for our CA system but it’s lacking this feature. We’re happy to chat if there’s a way to make a custom firmware to do this. ---
**Author:** ![sc-hsm](https://support.nitrokey.com/user_avatar/support.nitrokey.com/sc-hsm/32/304_2.png) [@sc-hsm](https://support.nitrokey.com/u/sc-hsm)\ **Post date:** [January 30, 2023, 8:37am UTC](https://support.nitrokey.com/t/nitrokey-hsm-audit-logs/4790/2 "2023-01-30T08:37:11Z")
Without a clock it is difficult to implement an internal audit log. You could use the key counter for auditing, so that unauthorized key operations will not go undetected. ---
**Author:** ![baovu](https://support.nitrokey.com/letter_avatar_proxy/v4/letter/b/67e7ee/32.png) [@baovu](https://support.nitrokey.com/u/baovu)\ **Post date:** [January 30, 2023, 10:39am UTC](https://support.nitrokey.com/t/nitrokey-hsm-audit-logs/4790/3 "2023-01-30T10:39:22Z")
The YubiHSM actually doesn’t have a clock either. While the key counter does help with auditing, it doesn’t capture admin operations like changing the PIN or extracting the key.