Self encrypting drives are supported in TrueNAS Community 24.10 but they won’t be in 25.04 : Managing Self-Encrypting Drives (SED) | TrueNAS Documentation Hub
UI management of Self-Encrypting Drives (SED) is an Enterprise-licensed feature in TrueNAS 25.04 (and later)
Depriving regular users of this feature is a particularly bad decision IMHO, security is important for everyone.
Feel free to protest.
Hey, I’m not 
up to speed on this decision but what I will say is that to be fair to iX they generally only remove features if those features are complex and could potentially cause issues for users if not managed properly. This may or may not be the case but that’s what I’ve seen over the years.
Any reason why ZFS encryption wouldn’t work for you?
Exactly. Unlike SED, it’s native to ZFS and not dependent on particular vendor features remaining enabled, etc. How secure is SED vs. ZFS encryption and what is the use case for SED vs. ZFS encryption?
FWIW, I prefer ZFS encryption because it protects data regardless of the type of drive I deposit it on.
I think SED’s main benefit over ZFS encryption, particular to TrueNAS, is to have a fully encrypted boot drive.
Which we never supported to begin with anyway. SED was only supported for data pools, not boot, and really only something we test / support with very specific drives on our appliance products.
I meant more in the context of “before you boot into TrueNAS”, suggesting that TrueNAS treats the boot-pool as it would any other drives, except that at a lower level the boot drive is using encryption via SED. (Installing to and booting from the drive, TrueNAS is agnostic to any “encryption”, even though the data is technically encrypted underneath.)
Yanking out the boot drive would make it unusable in another system without being able to unlock it.
If someone wants a fully encrypted space, including the OS, they cannot do this via ZFS (with TrueNAS), but it is possible with an SED drive.
The better way to protest is to describe your own use case and how this impacts you.
As indicated by @Johnny_Fartpants , we only remove features if they are causing issues. In this case, we do recommend ZFS encryption as its more portable and manageable. It doesn’t rely on drive vendors and their implementations. It also allows pools with mixed drive types to operate reliably.
This post title is a little misleading. TrueNAS continues to support SED: via the UI for specific drive hardware we validate with Enterprise appliances and using sedutil for COTS / community hardware, as the article says:
UI management of Self-Encrypting Drives (SED) is an Enterprise-licensed feature in TrueNAS 25.04 (and later). SED configuration options are not visible in the TrueNAS Community Edition. Community users wishing to implement SEDs can continue to do so using the command line sedutil-cli utility.
Hope that clarifies the situation.
