Firmware Updates Before Your Audit
Why updating hardware wallet firmware before an annual audit prevents documentation gaps and device health surprises.
Arriving at an audit session with outdated firmware is one of the most common issues we encounter. It does not block the audit, but it adds time and sometimes requires a follow-up appointment.
Why Firmware Matters for Documentation
Your reserve summary records the firmware version of each device at the time of audit. If a device runs firmware with known vulnerabilities, we note it in the summary with a recommendation to update. Accountants and successors reading the document later need to know whether the device was current.
Manufacturer Update Schedules
Ledger typically releases firmware updates quarterly. Trezor follows a similar cadence. Coldcard updates are less frequent but often include significant security patches. Check your manufacturer’s website thirty days before your scheduled audit.
The Update Process During Audit
We can guide you through a firmware update during the session if you bring your device and cable. Updates take fifteen to thirty minutes per device and require a stable connection. Plan for this additional time when booking.
Passphrase Considerations
If your device uses a passphrase (BIP39 extension word), verify you can access the wallet after updating firmware before your audit date. In rare cases, firmware updates reset device settings. Test with a small transaction or address verification a week before the session.
Documenting the Update
After updating, record the new firmware version in your personal notes. During the audit, we confirm the version on-device and include it in the reserve summary. This creates a clear timeline of device maintenance for future reference.