Difference between revisions of "Hardware Protection"
From MgmtWiki
(→Problems) |
(→References) |
||
| Line 8: | Line 8: | ||
==References== | ==References== | ||
| + | <references> | ||
| + | |||
| + | ===Other Material=== | ||
* See wiki page [[Smart Phone]] for a discussion of hardware versus software protection within a modern ARM based [[Trusted Execution Environment]]. | * See wiki page [[Smart Phone]] for a discussion of hardware versus software protection within a modern ARM based [[Trusted Execution Environment]]. | ||
[[Category: Security]] | [[Category: Security]] | ||
[[Category: Best Practice]] | [[Category: Best Practice]] | ||
Revision as of 09:55, 8 October 2020
Full Title
Hardware Protection offered by Hardware Security Modules (HSM see FIPS 140) or management chips.
Context
- Latest version as of 2019-05-22 is FIPS 140-3, version 3.
- The TPM (Trusted Platform Module) version 1 was a purely hardware version of protection that was offered only as a stand alone chip. With version 2 defined as software, it can be (and is) included in any Trusted Execution Environment.
Problems
When hardware contains software, and particularly when it contains firmware, it no longer has the same level of protection that a purely hardware solution offers. For example the Apple T2 chip has been hacked and cannot be fixed in the field.[1]
References
<references>
Other Material
- See wiki page Smart Phone for a discussion of hardware versus software protection within a modern ARM based Trusted Execution Environment.
