Join Now
Interested companies are encouraged to review the Benefits of Membership and apply today!
Join NowGlossary
Unfamiliar with a term used in this section? Check the TCG Glossary of TechnicalTerms for the definition.
View Glossary
Learn More
Trusted Network Connect
The Trusted Network Connect (TNC) Work Group has defined and released an open architecture and a growing set of standards for endpoint integrity. The TNC architecture enables network operators to enforce policies regarding endpoint integrity at or after network connection. The standards ensure multi-vendor interoperability across a wide variety of endpoints, network technologies, and policies.
September 13, 2010 - IF-MAP Enables Real-Time Information Sharing for Security, in the Cloud and Elsewhere. TCG's IF-MAP, or Metadata Access Protocol, is based on a powerful publish/subscribe model. IF-MAP is being used today to support network security applications using equipment from different vendors, and is expected to be used in cloud computing to enable real-time communication among devices including network infrastructure devices and servers. It also has been used to integrate physical security devices, supervisory control and data acquisition (SCADA) networks and unified communications platforms.
April 26, 2010 - Trusted Computing Group Announces First Certified Products for Trusted Network Connect Security Standards. IT buyers looking for products to ensure endpoint integrity and network security now can find the first certified products supporting the widely implemented Trusted Network Connect specifications from the Trusted Computing Group.
April 27, 2010 - Trusted Computing Group Demonstrates Unifed Security Based On Trusted Network Connect Network Security Standards at Interop Las Vegas. Trusted Computing Group (TCG) members Infoblox, Juniper Networks, Lumeta, OpenSEA Alliance and HP Networking showcased network security around the enterprise in a series of demonstrations, "TNC Everywhere: Unified Security", at Interop Las Vegas 2010 in booth # 1163.
TNC IF-MAP Metadata for Network Security
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 Metadata for Network Security.
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.
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.
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).
Federated Trusted Network Connect (TNC) FAQ
Frequently Asked Questions for Federated TNC Version 1.0 Specification.
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.
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.
TNC IF-T Binding to TLS Version 1.0, Revision 16
IF-T is the “transport” layer protocol that is responsible for carrying the TNC’s protocol messages over the network. Because it’s the lowest TNC protocol layer, it needs to be able to operate over different network technologies so that TNC can perform assessments on different kinds of networks.
The TNC IF-TNCCS Version 1.2 specification defines the IF-TNCCS protocol, which is used to communicate integrity measurements between a TNC Client and a TNC Server. Architects, designers, developers, and technologists interested in the development, deployment, and interoperation of trusted systems will find this document necessary in providing a specific mechanism for communicating integrity information.
Trusted Network Connect (TNC) Clientless Endpoint Security Profile FAQ
Frequently Asked Questions for Trusted Network Connect (TNC) Clientless Endpoint Security Profile