TXT uses the TPM to run a system state hash in a special TPM register (that can't be modified from x86 code) - no other relation there. Anchor Cove can seal (a

TXT uses the TPM to run a system state hash in a special TPM register (that can't be modified from x86 code) - no other relation there. Anchor Cove can seal (against TPM) or verify (against a hard coded value in the CPU, probably using efuses). Given that choice, I'd prefer the TPM-way - at least that key can be replaced. The recent spread of TPM is mostly motivated by Windows 8 and its Connected Standby feature. CS requires a TPM 2.0 (by Logo Requirements, ie. "spec", not necessarily by implementation).