{"id":1317,"date":"2004-07-19T00:00:00","date_gmt":"2004-07-19T00:00:00","guid":{"rendered":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/2004\/07\/19\/cisco-fortifies-wlan-security\/"},"modified":"2021-12-30T11:39:09","modified_gmt":"2021-12-30T11:39:09","slug":"cisco-fortifies-wlan-security","status":"publish","type":"post","link":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/2004\/07\/19\/cisco-fortifies-wlan-security\/","title":{"rendered":"Cisco Fortifies WLAN Security"},"content":{"rendered":"<p>Cisco Systems Inc. is preparing to introduce products to its WLAN line that add support for AES, among other security and management features.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>While Cisco is not the first wireless LAN provider to embrace Advanced Encryption Standard, its support will bring peace of mind to many IT managers who have standardized on the leading enterprise WLAN provider&#8217;s technology&#8212;especially those required to offer government-caliber security for their wireless networks.<\/p>\n<p>By year&#8217;s end, Cisco will introduce &#8220;Kodiak,&#8221; an 802.11a radio module for the popular Aironet AP1200 access point, according to sources familiar with the San Jose, Calif., company&#8217;s plans.  Kodiak supports the IEEE 802.11i security protocol, ratified last month, which is based largely on AES.  There will be two versions of the module, one with an integrated antenna and one with connectors for remote antennas, the sources said.<\/p>\n<p>Cisco also will introduce software that supports AES for Kodiak and for its 802.11g AP1100 and AP1200 access points.  AES is a federally approved encryption standard based on 128-bit keys generated by the Rijndael algorithm, resulting in stronger encryption than either TKIP (Temporal Key Integrity Protocol) or the more common WEP (Wired Equivalent Privacy).  AES can be difficult to implement on an existing WLAN, especially for campuses with hundreds of access points.<\/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-1317","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\/1317","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=1317"}],"version-history":[{"count":1,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/1317\/revisions"}],"predecessor-version":[{"id":3804,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/1317\/revisions\/3804"}],"wp:attachment":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/media?parent=1317"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/categories?post=1317"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/tags?post=1317"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}