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

TNC IF-MAP Binding for SOAP Specification

The Trusted Network Connect Working Group (TNC-WG) has defined an open solution architecture that enables network operators to enforce policies regarding the security state of endpoints in order to determine whether to grant access to a requested network infrastructure. Part of the TNC architecture is IF MAP, a standard interface between the Metadata Access Point and other elements of the TNC architecture. This document defines and specifies IF MAP.

July 2010 | Specifications | Add to Briefcase

icon

Storage Application Note: Encrypting Drives Compliant with Opal SSC

This document provides examples of the communication between a host and a storage device implementing the TCG Storage Security Subsystem Class: Opal SSC and the TCG Storage Architecture Core Specification.

February 2010 | Specifications | Add to Briefcase

icon

Storage Work Group Storage Security Subsystem Class: Opal

The Storage Workgroup specifications provide a comprehensive architecture for putting Storage Devices under policy control as determined by the trusted platform host, the capabilities of the Storage Device to conform with the policies of the trusted platform, and the life cycle state of the Storage Device as a Trusted Peripheral.

February 2010 | Specifications | Add to Briefcase

icon

TNC IF-M: TLV Binding Specification

The Trusted Network Connect Work Group (TNC-WG) has defined an open solution architecture that enables network operators to enforce policies regarding the security state of endpoints in order to determine whether to grant access to a requested network infrastructure.

January 2010 | Specifications | Add to Briefcase

icon

Mobile Reference Architecture v1.0, Revision 5: Normative Requirements Check-list

1. This is an informative document, intended to catalogue the normative requirements of the "TCG Mobile Reference Architecture." Please note that in case of any discrepancies, the Mobile Reference Architecture specification is definitive, and overrides the information contained herein.

June 2009 | Specifications | Add to Briefcase

icon

TCG Physical Presence Interface Specification

The Physical Presence Interface utilizes the industry-standard Advanced Configuration and Power Interface (ACPI) to provide a communication mechanism between the OS and the BIOS, enabling the OS and the BIOS to cooperate to provide a simple and straightforward platform user experience for administering the TPM without sacrificing security.

June 2009 | Specifications | Add to Briefcase

icon

Federated TNC Version 1.0, Revision 26

Federated TNC standardizes the expression of endpoint posture information, and the methods of its communication between security domains, using the OASIS Security Assertion Mark-up Language (SAML).

May 2009 | Specifications | Add to Briefcase

icon

Federated Trusted Network Connect (TNC) FAQ

Frequently Asked Questions for Federated TNC Version 1.0 Specification.

May 2009 | Specifications | Add to Briefcase

icon

TNC Architecture for Interoperability Specification

The TNC architecture focuses on interoperability of network access control solutions and on the use of trusted computing as the basis for enhancing security of those solutions. Integrity measurements are used as evidence of the security posture of the endpoint so access control solutions can evaluate the endpoint's suitability for being given access to the network.

May 2009 | Specifications | Add to Briefcase

icon

TNC Clientless Endpoint Support Profile Version 1.0, Revision 13

The TNC Clientless Endpoint Support Profile addresses the devices that regularly attach to a network but lack a TNC client. Examples include printers, VoIP handsets and HVAC systems. These devices, which are increasingly common in the enterprise, creates a management headache when deploying authentication across the network.

May 2009 | Specifications | Add to Briefcase