By Will Arthur, David Challener, Kenneth Goldman
A pragmatic consultant to TPM 2.0: utilizing the depended on Platform Module within the New Age of safety is a straight-forward primer for builders. It exhibits protection and TPM ideas, demonstrating their utilization in actual functions that the reader can test out.
Simply placed, this e-book is designed to empower and excite the programming group to move out and do cool issues with the TPM. The process is to ramp the reader up speedy and retain their curiosity. a realistic advisor to TPM 2.0: utilizing the depended on Platform Module within the New Age of safety explains safety innovations, describes TPM 2.0 structure, and gives coding examples in parallel starting with extremely simple innovations and straightforward code to hugely advanced options and code.
The ebook contains entry to a stay execution setting (secure, hosted virtualization) and actual code examples to get readers up and speaking to the TPM fast. The authors then aid the clients extend on that with genuine examples of priceless apps utilizing the TPM.
Read or Download A Practical Guide to TPM 2.0: Using the Trusted Platform Module in the New Age of Security PDF
Similar security books
La sécurité dans la maison (L'artisan de sa maison)
Assurer l. a. sécurité de son habitation est à los angeles portée de tous mais, grâce à ce petit livre pratique, on ne se laissera plus décourager par l. a. variété ou los angeles complexité des matériels disponibles. Qu'il s'agisse de remplacer une serrure ou d'installer un système de vidéosurveillance on saura quoi faire et remark.
This booklet constitutes the refereed court cases of the foreign Symposium on safeguard in Computing and Communications, SSCC 2013, held in Mysore, India, in August 2013. The 24 revised complete papers provided including 15 poster papers have been conscientiously reviewed and chosen from 111 submissions. The papers conceal all facets of safe computing and communique in networking and allotted structures similar to cloud-based facts facilities.
- Security Protocols: 11th International Workshop, Cambridge, UK, April 2-4, 2003, Revised Selected Papers
- Hacking del.icio.us
- The State of the Art in Intrusion Prevention and Detection
- Hackers Beware. Defending Your Network from the Wiley Hacker
- Substitute for Power: Wartime British Propaganda to the Balkans, 1939–44
- Disaster Management Handbook (Public Administration and Public Policy)
Extra resources for A Practical Guide to TPM 2.0: Using the Trusted Platform Module in the New Age of Security
Sample text
Use of the EK was gated by owner authorization. 2 specification). Additionally, keys could be locked to localities and values stored in PCRs. 2 could be locked to PCRs and particular localities, and to two different authorizations—one for reading and one for writing. But the only way the two authorizations could differ was if one of them were the owner authorization. Certified migratable keys had the same authorizations as other keys; but to complete the migration, a migration authority had to sign an authorization, and that authorization had to be checked by the TPM.
An example of how do this well is found in Microsoft’s BitLocker application, which first came out with Windows Vista Enterprise. Microsoft BitLocker Microsoft gave careful consideration to both of the previously described problems when it created the BitLocker application, originally embedded in the Enterprise edition of Vista. This program was used to do full-disk encryption of the hard disk on which Windows resided. To do this, early in the boot sequence BitLocker obtained a key from the TPM.
0 directly. 0, both basic and advanced. This chapter starts by looking at the various application interfaces that are used by programs to interface with the TPM hardware. Then you examine a number of applications that already use TPMs. Perhaps the most interesting part of the chapter—and one we hope you will help make out of date—is a short list of types of programs that should use TPMs but don’t. We follow up with some considerations that any programmer using a TPM must take into account, and a description of how some existing programs have handled them.