> It merely removes OS-side support for it and resets configuration to non-exploitable state.
How do we know that the vulnerability is in the OS-side? Has this been established yet?
How do we know that the vulnerability is in the OS-side? Has this been established yet?
Unprovisioning AMT seems to be the essential part and I am curious if the other steps serve any real purpose.
The Mitigation Guide goes on to say: "Systems that are vulnerable [...] should be unprovisioned using the tools used to initially configure them [...] As an example, the Intel AMT Configuration Utility [...]"
So ACUConfig is just an example and specifically not the Intel recommended way. OP doesn't say that.
"Systems that are vulnerable [...] should be unprovisioned using the tools used to initially configure them [...]"