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).[1][2][3]
History
The TNC architecture was first introduced at the RSA Conference in 2005.[4] TNC was originally a network access control standard with a goal of multi-vendor endpoint policy enforcement.[5]
In 2009 TCG announced expanded specifications which extended the specifications to systems outside of the enterprise network.[6] Additional uses for TNC which have been reported include Industrial Control System (ICS), SCADA security,[7][8] and physical security.[9]
Specifications
Specifications introduced by the TNC Work Group:[10]
- TNC Architecture for Interoperability
- IF-IMC - Integrity Measurement Collector Interface
- IF-IMV - Integrity Measurement Verifier Interface[11]
- IF-TNCCS - Trusted Network Connect Client-Server Interface[12]
- IF-M - Vendor-Specific IMC/IMV Messages Interface
- IF-T - Network Authorization Transport Interface[13]
- IF-PEP - Policy Enforcement Point Interface[14]
- IF-MAP - Metadata Access Point Interface
- CESP - Clientless Endpoint Support Profile
- Federated TNC[6]
TNC Vendor Adoption
A partial list of vendors who have adopted TNC Standards:[15]
|
|
Also, networking by
TNC Customer Adoption
The U.S. Army has planned to use this technology to enhance the security of its computer networks.[16]
The South Carolina Department of Probation, Parole, and Pardon Services has tested a TNC-SCAP integration combination in a pilot program.[17]
See also
References
- ↑
- ↑ "Wireless Infrastructure Advice, Discussion, Community". Network Computing. Retrieved 2017-05-03.
- ↑
- ↑
- ↑ Vijayan, Jaikumar (2005-05-09). "Vendor Group Adds Net Access Specs". Computerworld. Retrieved 2017-05-03.
- 1 2 "Trusted Computing Group Widens Security Specs Beyond Enterprise Networks". Darkreading.com. Retrieved 2017-05-03.
- ↑ "Not your Father's Control System | Tofino Industrial Security Solution". Tofinosecurity.com. Retrieved 2017-05-03.
- ↑
- ↑
- ↑
- ↑
- ↑ "TCG Trusted Network Connect : TNC IF-TNCCS: Protocol Bindings for SoH" (PDF). Opus1.com. Retrieved 2017-05-03.
- ↑
- ↑
- ↑
- ↑
- ↑ Jackson, William (2010-09-28). "Speed of cybersecurity rises with combination of Trusted Network Connect and Security Content Automation Protocols". Fcw.com. Retrieved 2017-05-03.
Sources
- Dornan, Andy. “'Trusted Network Connect' Puts Hardware Security Agent In Every PC”, “Information Week Magazine”, UBM Techweb Publishing.
- Vijayan, Jaikumar. “Vendor Group Adds Net Access Specs”, “Computer World Magazine”, IDG Publishing.
- Higgins, Kelly Jackson. “Trusted Computing Group Widens Security Specs Beyond Enterprise Networks”, “Dark Reading”, UBM Techweb Publishing.
- Townsend, Mark. “Naked endpoints on your net, and what to do about them”, “SC Magazine”, Haymarket Media.
- Fang, Juan and Zeng, Hongli. “The Model of Trusted Network Connect Based on Credibility of the Hierarchy”, nswctc, vol. 2, pp.454-457, 2010 Second International Conference on Networks Security, Wireless Communications and Trusted Computing, 2010.
- Howard, Scott (2010-06)(“Securing SCADA and Control Networks”, “urunkoruma.com”.