# Driver Signing for Secure Boot environments

**URL:** <https://forums.balena.io/t/driver-signing-for-secure-boot-environments/375445>\
**Category:** Feature Requests\
**Tags:** security, balenacloud\
**Created:** [January 28, 2026, 4:23pm UTC](https://forums.balena.io/t/driver-signing-for-secure-boot-environments/375445 "2026-01-28T16:23:25Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![doctorray](https://avatars.discourse-cdn.com/v4/letter/d/a4c791/32.png) [@doctorray](https://forums.balena.io/u/doctorray)\
**Post date:** [January 28, 2026, 4:23pm UTC](https://forums.balena.io/t/driver-signing-for-secure-boot-environments/375445/1 "2026-01-28T16:23:25Z")

</div>

When utilizing secure boot and full disk encryption on GPT x86\_64 platforms, it’s not currently possible to use kernel drivers unless they are signed by a local MOK or other appropriate signing keys linked to the secure boot. For example, this prevents the use of nvidia drivers in these environments.
