The whole article can be read here
Edit: Link to the article added and only parts of the article are kept. - Vysez
Cell aims to prevent attacks by having the hardware itself protect each individual application from other applications, and even from the OS. Any of Cell's eight synergistic processing elements (SPEs) can be booted, on-the-fly, in secure mode, so that the code and data stored in each SPE's local store is walled off from the rest of the system. This partitioning is enforced in various ways by Cell's hardware, with the end result being that the integrity of the code running on a secure SPE can be verified by the SPE; i.e. the SPE can check a thread at load-time and periodically during runtime to see if its code has been modified either in memory or in storage. Verified code can then be trusted to handle sensitive data, like digital media content.
Cell uses three primary security mechanisms and one auxiliary one to ensure code and data integrity at the hardware level. Here's a very brief rundown of these mechanisms; for more information check the paper linked above:
* Secure processing vault (SPV): An SPV is essentially an SPE running in secure mode. When in secure mode, the SPE's local store cannot be read from or written to by any other agent on the Cell's internal element interconnect bus (EIB). Only the SPE to which the local store is attached can access it. This means that encrypted data can be moved from main memory or storage into the secure local store, where the SPE can safely decrypt it out of sight of the rest of the system.
* Runtime secure boot: It does no good to create an SPV and move encrypted data into it if the code that's running on the secured SPE has been tampered with. Cell's runtime secure boot feature allows the SPE hardware to check periodically to ensure that the application it's running hasn't been modified. IBM is vague on exactly how this works, other than stating that it involves a hardware key and a cryptographic algorithm.
* Hardware root of secrecy: This feature is the heart of Cell's approach to software security. Cell stores a root key in hardware, and when an SPE boots in secure mode it must access that key in order to unseal the set of keys that it will use to decrypt the code and data that will go into its LS. Only an SPE running in secure mode with code that has been verified via runtime secure boot may ever access the root key.
* Hardware random number generator (RNG): Cell's hardware RNG can be used for a variety of cryptographic functions, and it will work in conjunction with the three previously described features. The paper suggests that it will be mainly used to timestamp messages so that replay attacks can be prevented.
The PS3's Achilles heel
A thorough and accurate evaluation of Cell's security mechanisms would be out of my league, even if it were possible given the information provided in the new paper (which it isn't). Nonetheless, I can draw a few significant conclusions from the general and somewhat spotty description provided by IBM.
First, IBM starts out the paper with an acknowledgment that Cell's security architecture is designed to thwart only software-based attacks. It's a truism in the infosec world that once an attacker has on-site, physical access to the hardware it's game over, so Cell sensibly doesn't even try to tackle that one. This being the case, I have one, hyphenated word for Sony headquarters: "mod-chip."
Because of Cell's high level of integration, where the bulk of the security architecture is on a single die, I'm not sure at the moment how mod-chipping will work on the PS3. However, it's a near certainty that someone will figure out how to compromise the box with a hardware modification of some sort. When a successful hardware-based attack is formulated, then Sony and IBM can't just release a patch that fixes the problem, and therein lies the weakness of hardware-based security.
...
Conclusions
...
If the PS3 were the only vehicle in the world for consuming Sony's and the *AA's digital content, then a perfectly secure, hacker-proof console design would ensure that none of that content leaks out onto the Internet in unsecured form. We all know, however, that this isn't the case. Sony will never see enough market penetration with the PS3 to profitably release PS3-only nongaming content. The company, like other content providers, will always have to deal with a multi-format, multi-platform world.
Thus the same songs, images, and movies that we'll see on the PS3 will also be made available on a wide variety of platforms with varying levels of security. All it takes is for one of those content delivery mechanisms to be compromised by someone with access to an Internet connection, and the cat is out of the bag. So in spite of Sony's best efforts with Blu-Ray and the PS3, consumers will always have the option of getting the same content for free off the Internet if Sony tries to price PS3 content too high or if they impose draconian usage restrictions.
source: Arstechnica (edit thanx for diamond G to point it out)
Edit: Link to the article added and only parts of the article are kept. - Vysez
Last edited by a moderator: