It would be wrong for them to dictate how something is implemented. Not all vendors may have the necessary hardware capabilities built in and this would be the standards group doing the limitation. They cannot that, they have to allow the industry to do the elimination if necessary.
But conceptually you just need to implement the TPM spec. I'm not sure if the Trusted Computing Group spec for TPM mandates the TPM be implement in hardware or have hardware support. But I may be wrong.
As a society we tend to be reactionary. After we have been hit, we react and put better systems in place. Does anyone do backups before they have lost data? Does anyone install security software before they have been infected?
@Embedded Guy - Thanks for the comment and yes it was high level, but many of the topics we talked about could be a whole course on their own. I hope it sends people in the right direction to get more relevant information.
@mclaus - I woyulkd suggest, just as we do with credit cards, that an order and the card information are sent separately. That way at least two parts of the system have to be comproimised before damage can be done.
I appreciate the heads up on this Internet of Things concept. I realize it was a high level discussion, but it is nice to know that it is going on before it all hits the market (surprise!). Thanks Brian and Alex for great information!
There is - but since update in basically an automated process, we have essentially embedded a password into the code - a very bad practice. It is encrypted and known to only a few in our organization, but still it is probably vulnerable to being hacked if somebody were to work at it hard enough. We are planning to change to a dynamically generated key that will be provided via a newwork connection back to our central service organization - but we don't have that infrastructure quote ready yet.
There are ways to re-register the process code with the boot process. During updates, there is an API that get exercises to re-register the new process code. Updates to the boot image contain process registrations already.
We ensure that any code that runs on our system is known. The boot process gets the boot image from a known, encrypted, secure source. Any process code that is run after boot must be registered with the boot image and it;'s image much match the one that was registered.
Yes - we sell the 'the ability to treat patients' with our products to our customers over the web. They pay, we download a certain number of treatments into the system to allow them to deliver the treatments. Often we place the equipment of free, but make money by selling the tretments.
A group in China learned to hack the code that allowed download of treatment, as was selling that hack to our customers. Big problem, but we did finally get it resolved.
The streaming audio player will appear on this web page when the show starts at 2pm eastern today. Note however that some companies block live audio streams. If when the show starts you don't hear any audio, try refreshing your browser. The player "like" Firefox better than IE.
Replay available now: A handful of emerging network technologies are competing to be the preferred wide-area connection for the Internet of Things. All claim lower costs and power use than cellular but none have wide deployment yet. Listen in as proponents of leading contenders make their case to be the metro or national IoT network of the future. Rick Merritt, EE Times Silicon Valley Bureau Chief, moderators this discussion. Join in and ask his guests questions.