Citing the increased risk posed by mobile workers and wireless networking technology, Microsoft Corp. and VeriSign Inc. said that they are teaming up to help organizations secure Wi-Fi networks.<\/p>\n","protected":false},"excerpt":{"rendered":"
The two companies will collaborate to create a Wi-Fi security architecture based on Microsoft’s NAP (Network Access Protection) and VeriSign’s Unified Authentication platforms.<\/p>\n
The new architecture will help system administrators crack down on Wi-Fi-enabled computers that do not adhere to corporate security policies and facilitate use of multifactor authentication for accessing Wi-Fi networks, according to a statement.<\/p>\n
“Evil Twin” and other wireless spoofing attacks provide a rich set of tools for identity thieves and corporate espionage agents.<\/p>\n
Microsoft’s NAP combines client\/server technology with a new set of policy validation and enforcement APIs that allow administrators to quarantine client machines if they fail basic “health” tests, such as having up-to-date anti-virus definitions or operating system patches.<\/p>\n
VeriSign Unified Authentication is a technology platform for deploying and provisioning multifactor authentication technology such as smart cards, secure USB (Universal Serial Bus) tokens and one-time passwords.<\/p>\n
VeriSign said it will work with Microsoft so that networks using VeriSign Unified Authentication can issue health certificates to Windows desktop clients so that they can access NAP-protected networks, the companies said. VeriSign will also integrate its Unified Authentication platform with Microsoft’s Active Directory user directory technology and Internet Authentication Servers.<\/p>\n
Better integration will make management of user and device authentication credentials for Windows clients easier on Wi-Fi networks, the companies said.<\/p>\n
http:\/\/www.eweek.com\/article2\/0,1759,1788375,00.asp?kc=EWRSS03119TX1K0000594<\/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-1404","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\/1404","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=1404"}],"version-history":[{"count":1,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/1404\/revisions"}],"predecessor-version":[{"id":3891,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/1404\/revisions\/3891"}],"wp:attachment":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/media?parent=1404"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/categories?post=1404"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/tags?post=1404"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}