Replies to post #207994 on Wave Systems Corp. (fka WAVXQ)

[wavedreamer]

Micro,

I'm unfamiliar with their product but it looks to me to be running further up the software stack at the OS level that has been securely partitioned from other OS's by the LynuxWorks Type 1 hypervisor (bare metal). Any product that serves as a defense in the OS is good because the malicious code could be trying to break out of the virtual environment to migrate to the hypervisor.

Will it stop all attacks (I have no idea) but I think when ever a PC boots up the whole Idea around a Trusted Boot is to have each component in the boot sequence be measured before launch. The TPM holds the hash measurements of a trusted state of the software (hypervisor is software usually less than 10K of code)and in the thumb nail diagram I showed you the other day the launch can be aborted if the measured launch fails. If that happens what does the person do next? Well that's where Wave has a solution, they can self heal the hypervisor/Master Boot Record if they have been compromised by using the SED. A trusted known copy of the Hypervisor code/Master Boot Record are stored in secure partitions of the drive. When you think about it if the corporate IT department needed to update the hypervisor on each client Wave could do that by using Intels AMT (active management technology)to gain access to the SED and update the Hypervisor:))))

We want Citrix to do what those robust military EAL 6+ hypervisor companies do all ready by using the TPM in Intel’s TXT Technology for a trusted Boot of the Xen Client Hypervisor. Right now they say don't enable the TPM (they say they will support it in a future edition but right now Wave does not need such a large company saying don't use the TPM with our product. JMO