Yes, it is. You do have to have some infrastructure you trust somewhere to validate an attestation report from the confidential VM.

&#x2F;proc&#x2F;cpuinfo shows the current microcode version

but is it possible to verify that the cloud provider has applied the update?

There are microcode updates for this already <a href="https:&#x2F;&#x2F;www.amd.com&#x2F;en&#x2F;resources&#x2F;product-security&#x2F;bulletin&#x2F;amd-sb-3034.html" rel="nofollow">https:&#x2F;&#x2F;www.amd.com&#x2F;en&#x2F;resources&#x2F;product-security&#x2F;bulletin&#x2F;a...</a>

The premise of attestation is supposed to be that you can use hardware even though it&#x27;s in the physical possession of someone you don&#x27;t trust. It&#x27;s a terrible idea, because vulnerabilities are found on a regular basis and the party you&#x27;re not supposed to be trusting is then already in possession of your sensitive data when the next one is published. The premise should be abandoned and the parties attempting to get anyone to rely on it should be lampooned and run out of town.Not having a multi-tenant system is something else. There you&#x27;re trying to be protected from other customers, not the provider. Excluding other tenants still wouldn&#x27;t protect you against the provider, especially on systems with proprietary and potentially exploitable ring -1 hardware they could already be silently in control of even when the entire machine is allocated to you.Meanwhile for anything on the scale of an organization, having physical possession of the machine yourself isn&#x27;t that expensive. People got hoodwinked when virtualization first came around because they compared the cost of having a mostly-idle physical server for each of their applications to having that many cloud VMs, and the cloud VMs were cheaper, but that isn&#x27;t the right comparison. You don&#x27;t compare having 100 physical machines to having 100 VMs, even if people used to use 100 physical machines for that in 2005. You compare it to having three physical machines that can each run 100 VMs, and then having physical possession of your own hardware is frequently less expensive.

A hostile tenant is insufficient if you read the summary. You need a malicious hypervisor (ie your cloud provider) or a way to escape the sandbox and attack the hypervisor. Both attacks are highly unlikely in practice

A lot more expensive and this is required for any classified data. I honestly don&#x27;t think you can truly securely share a CPU with a hostile tenant because their are just too many side-channels.

I wonder how much more expensive it is to rent the whole physical machine at all times for confidential computing purposes, compared to the losses incurred by a breach.

I guess the reason you provided is the answer to the question.

What purpose does the &quot;news&quot; of finding another way to break &quot;confidential computing&quot; serve, other than proliferate the incorrect assumption that there even was a working concept beforehand?

The only purpose of SEV is to protect a guest against the person who controls the hypervisor.So this is a threat against SEV.

Requires an already compromised hypervisor &#x2F; UEFI. Yawn.

If there is a vulnerability in a system you control, you can mitigate it until it can be patched, or if necessary disable access to it until it can be patched.If there is a vulnerability in a system controlled by an untrusted party that already has your sensitive data on it, you&#x27;re pwned.

A vulnerability is a trick? All complex systems have them, but eventually they will all be formally verified and secure. Progress marches on. Unless you’d rather make your own processors along with the moonshine in your shed, of course.

More evidence that &quot;confidential computing&quot; is just a trick to convince people to hand over control of their computing to &quot;someone else&#x27;s machine&quot;. Never trusted the clown, and never will.

Fabricked: Misconfiguring Infinity Fabric to Break AMD SEV-SNP