Last I heard in 2019, this feature was only available on Linux systems, I am curious if this support has since been extended to Windows 10 platforms, such as 2004. Recent BIOS updates introduced "Memory Guard" aka TSME on non pro Ryzen chipsets... does enabling this reduce or increase security? Is SME enabled by default on systems that support TSME? I have read conflicting reports suggesting that enabling TSME disables SME extension support for per-VM encryption key support. Does SME protect against Rowhammer/Rambleed? TSME eliminates Rowhammer/Rambleed and similar zero day attack vectors.
What is the benefit of SME over TSME and visa versa? Is there any benefit to enabling TSME on top of SME? I can imagine it would be helpful on dual boot setups where UEFI is not enabled in certain o/s and IS enabled in others.
Here is some data I have gathered from https://en.wikichip.org/wiki/x86/sme
The SME extension attempts to defend against attacks by allowing the entirety of main memory to be encrypted as well as by enforcing full isolation between co-resident VMs. With the addition of SEV, this security can be extended to cloud users that can have fully private memory inaccessible to hypervisor or host software.
Transparent SME
Transparent SME (TSME) as the name implies is a stricter subset of SME that requires no software intervention. Under TSME, all memory pages are encrypted regardless of the C-bit value. TSME is designed for legacy OS and hypervisor software that cannot be modified. Note that when TSME is enabled, standard SME as well as SEV are still available. TSME and SME share a memory encryption key.
Update: with both TSME enabled and disabled, hwinfo64 reports SME is unavailable:
What is the benefit of SME over TSME and visa versa? Is there any benefit to enabling TSME on top of SME? I can imagine it would be helpful on dual boot setups where UEFI is not enabled in certain o/s and IS enabled in others.
Here is some data I have gathered from https://en.wikichip.org/wiki/x86/sme
The SME extension attempts to defend against attacks by allowing the entirety of main memory to be encrypted as well as by enforcing full isolation between co-resident VMs. With the addition of SEV, this security can be extended to cloud users that can have fully private memory inaccessible to hypervisor or host software.
Transparent SME
Transparent SME (TSME) as the name implies is a stricter subset of SME that requires no software intervention. Under TSME, all memory pages are encrypted regardless of the C-bit value. TSME is designed for legacy OS and hypervisor software that cannot be modified. Note that when TSME is enabled, standard SME as well as SEV are still available. TSME and SME share a memory encryption key.
Update: with both TSME enabled and disabled, hwinfo64 reports SME is unavailable:
Last edited: