{"id":1493,"date":"2006-06-01T00:00:00","date_gmt":"2006-06-01T00:00:00","guid":{"rendered":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/2006\/06\/01\/protecting-the-wired-from-the-wireless\/"},"modified":"2021-12-30T11:39:29","modified_gmt":"2021-12-30T11:39:29","slug":"protecting-the-wired-from-the-wireless","status":"publish","type":"post","link":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/2006\/06\/01\/protecting-the-wired-from-the-wireless\/","title":{"rendered":"Protecting the Wired from the Wireless"},"content":{"rendered":"<p>Redwood City, California-based Network Chemistry says that its RFprotect Scanner is the first product to focus on helping businesses with a no-wireless policy use their Ethernet infrastructure to look for rogue access points and other wireless issues.  The new scanner is an appliance with a database of profiles of products that could potentially open up the wired network to unwanted wireless traffic, whether the cause is an innocent employee who just plugs in an AP to get some mobility in the office, or a more malicious problem.  RogueScanner will detect and identify rogues on a network, but does not block their use.  RogueScanner software is available for download now, for free.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>&#8220;If you look at the problems people want to solve, where the most pain is, it revolves around locating and remediating rogue APs and peer connections on the network,&#8221; says Brian de Haaff, Vice President of Product Management and Marketing at Network Chemistry.<\/p>\n<p>The company is also planning to release quarterly information called the Network Chemistry Wireless Threat Index, based on information gathered by its products and the Wireless Vulnerabilities &#038; Exploits (WVE) database it launched last year to catalog potential attacks on WLANs.   He says it will be the industry&#8217;s first ongoing index of enterprise WLAN threats.<\/p>\n<p>http:\/\/www.wi-fiplanet.com\/news\/article.php\/3608381<\/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-1493","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\/1493","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=1493"}],"version-history":[{"count":1,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/1493\/revisions"}],"predecessor-version":[{"id":3980,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/1493\/revisions\/3980"}],"wp:attachment":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/media?parent=1493"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/categories?post=1493"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/tags?post=1493"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}