Join Now

Interested companies are encouraged to review the Benefits of Membership and apply today!

Join Now

Glossary

Unfamiliar with a term used in this section? Check the TCG Glossary of TechnicalTerms for the definition.  


View Glossary

Resources

icon

Infrastructure Work Group Platform Trust Services Interface Specification (IF-PTS) Version 1.0

This specification defines the IF-PTS interface at the protocol data unit (PDU) level. Interoperability is achieved through compliance with PDU structure definition and proper message passing semantics.

November 2006 | Specifications | Add to Briefcase

icon

Infrastructure Work Group Platform Trust Services Interface Specification, Version 1.0

The Infrastructure Working Group (IWG) defines architecture and frameworks for interoperation of the trusted computing capabilities of platforms and devices useful in improving the security and assurance of computer systems.

November 2006 | Specifications | Add to Briefcase

icon

Infrastructure Work Group Reference Manifest (RM) Schema Specification, Version 1.0

The purpose of this document is to provide a detailed description of the TCG Infrastrcuture Working Group’s Reference Manifest (RM) schema, here after refered to as the RM schema. The RM schema is derived from the core integrity metadata XML schema [1].

November 2006 | Specifications | Add to Briefcase

icon

Infrastructure Work Group Simple Object Schema Specification, Version 1.0

This specification is integral to the TCG Infrastructure Working Group’s (IWG) reference architecture, and is directly related to the TCG’s Integrity Management Model. Specifically, the simple object XML schema defines the structure with which integrity measurements are included within integrity reports.

November 2006 | Specifications | Add to Briefcase

icon

TCG EFI Protocol Version 1.20, Revision 1.0

The purpose of this document is to define a standard interface to the TPM on an EFI platform. This standard interface is useful on any of the three example instantiations of an EFI platform shown in Figures 2-1, 2-2, and 2-3, as well as other instantiations.

June 2006 | Specifications | Add to Briefcase

icon

TCG EFI Platform Specification Version 1.20, Revision 1.0

This document is about the processes that boot an EFI platform and boot an OS on that platform. Specifically, this specification contains the requirements for measuring boot events into TPM PCRs and adding boot event entries into the Event Log.

June 2006 | Specifications | Add to Briefcase

icon

Server Work Group Itanium Architecture Based Server Specification, Version 1.0

This specification, combined with the TCG Generic Server Specification, the TCG ACPI Specification, the TCG EFI Protocol Specification, and the TCG EFI Platform Specification define requirements for a TCG-compliant Itanium Architecture based server system.

March 2006 | Specifications | Add to Briefcase

icon

TCG Design, Implementation, and Usage Principles (Best Practices)

The TCG Design, Implementation, and Usage Principles document, version 2.0 lays out the principles underlying the design of the TCG specifications.

December 2005 | Specifications | Add to Briefcase

icon

Server Work Group ACPI General Specification, Version 1.0

This specification defines the framework of necessary ACPI tables and basic methods to be used on a TCG compliant platform. The table and ACPI namespace objects provide enough information to the operating system to enable access to the TCG compliant hardware in a platform.

August 2005 | Specifications | Add to Briefcase

icon

PC Client Work Group Specific Implementation Specification for Conventional Bios Specification, Version 1.2

The Trusted Computing Group's architecture is a platform independent architecture to enhance trust on computing platforms. As such, the TCG Main Specification is general in specifying both hardware and software requirements. The goal of the TCG member companies is to ensure compatibility among implementations within each computing architecture. It is expected that companion implementation documents will be created for each architecture.

July 2005 | Specifications | Add to Briefcase