The Trusted Computing Group’s (TCG) specification, which is scheduled to make its debut at Interop in Las Vegas, offers a way to conduct integrity checks of desktop computers, such as requiring anti-virus or software patch updates before granting network access.<\/p>\n","protected":false},"excerpt":{"rendered":"
While this capability exists in some products, the Trusted Network Connect (TNC) specification is the first attempt to define an open standard for it.<\/p>\n
Some consortium members, including Funk Software, HP and iPass, will show how the specification works through software interoperability demonstrations over an HP ProCurve Switch-based LAN.<\/p>\n
“Interoperability is important to minimize the ways we have to do this, which today requires custom development with anti-virus vendors and others,” says Barbara Nelson, director of advanced technology at iPass, which makes software called Endpoint Policy Management to check desktops for missing anti-virus and software patches. At this week’s demonstration, iPass plans to show how its desktop Endpoint Policy Management software can collect TNC-related information about anti-virus and patch updates on a desktop.<\/p>\n
Paul Crandell, network security program manager at HP, says TCG will work to further develop the basic TNC architecture so that more-complex policy decisions associated with remediation can be enforced through network equipment.<\/p>\n
Dan Ratner, director of product management at Meetinghouse, says the company expects to include TNC in its Aegis client and server authentication products by the fourth quarter.<\/p>\n
http:\/\/www.networkworld.com\/news\/2005\/050205-trusted-computing.html<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3],"tags":[],"class_list":["post-1411","post","type-post","status-publish","format-standard","hentry","category-product"],"_links":{"self":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/1411","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/comments?post=1411"}],"version-history":[{"count":1,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/1411\/revisions"}],"predecessor-version":[{"id":3898,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/1411\/revisions\/3898"}],"wp:attachment":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/media?parent=1411"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/categories?post=1411"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/tags?post=1411"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}