Trusted Network Connect

Trusted Network Connect (TNC) is an open architecture for Network Access Control, promulgated by the Trusted Network Connect Work Group (TNC-WG) of the Trusted Computing Group (TCG).

History
The TNC architecture was first introduced at the RSA Conference in 2005. TNC was originally a network access control standard with a goal of multi-vendor endpoint policy enforcement.

In 2009 TCG announced expanded specifications which extended the specifications to systems outside of the enterprise network. Additional uses for TNC which have been reported include Industrial Control System (ICS), SCADA security, and physical security.

Specifications
Specifications introduced by the TNC Work Group:
 * TNC Architecture for Interoperability
 * IF-IMC - Integrity Measurement Collector Interface
 * IF-IMV - Integrity Measurement Verifier Interface
 * IF-TNCCS - Trusted Network Connect Client-Server Interface
 * IF-M - Vendor-Specific IMC/IMV Messages Interface
 * IF-T - Network Authorization Transport Interface
 * IF-PEP - Policy Enforcement Point Interface
 * IF-MAP - Metadata Access Point Interface
 * CESP - Clientless Endpoint Support Profile
 * Federated TNC

TNC Vendor Adoption
A partial list of vendors who have adopted TNC Standards:


 * ArcSight
 * Aruba Networks
 * Avenda Systems
 * Enterasys
 * Extreme Networks
 * Fujitsu
 * IBM
 * Pulse Secure


 * Juniper Networks
 * Lumeta
 * McAfee
 * Microsoft
 * Nortel
 * ProCurve
 * strongSwan
 * Wave Systems

Also, networking by
 * Cisco
 * HP
 * Symantec
 * Trapeze Networks
 * Tofino

TNC Customer Adoption
The U.S. Army has planned to use this technology to enhance the security of its computer networks.

The South Carolina Department of Probation, Parole, and Pardon Services has tested a TNC-SCAP integration combination in a pilot program.