Cisco Wednesday outlined its technology and pricing strategy for a new version of the Firewall Services Module that has so far been free for the Cisco Catalyst 6500 Series switches as a way to set up “virtual firewalls” at switching points.<\/p>\n","protected":false},"excerpt":{"rendered":"
According to Hoe, the Firewall Services Module 2.2 can be deployed and configured through any of three Cisco management consoles so that network managers can establish “logical firewalls” between Catalyst switching points, each with its own policy and rules.<\/p>\n
The PIX Device Manager v.40 would only support a single Cisco Catalyst 6500 Series Firewall Services Module.<\/p>\n
Firewall controls can be set based on IP address, protocols, and network access control lists, Hoe said. The Firewall Services Module is wholly separate from the module for IPSec VPN, which is also available for the Cisco Catalyst 6500 Series switches, as are modules for intrusion detection.<\/p>\n
In addition, Cisco also announced what amounts to a re-branding of the Riverhead Networks equipment, Guard and Detector, which Cisco gained in its acquisition of Riverhead this March for $39 million. Guard and Detector are used to monitor traffic flows and combat distributed denial-of-service (DoS) attacks that can flood networks with unneeded traffic so that legitimate traffic is obstructed.<\/p>\n
The Cisco Guard XT 5650 is a network appliance that compares traffic flows to profiles of normal traffic patterns, behavior and protocol compliance, among other features, and can be used to block attacks. The Cisco Traffic Anomaly Detector XT 5600 is used to identity a broad range of distributed DoS attacks and automate activation of the Cisco Guard XT 5650.<\/p>\n
More info: http:\/\/www.nwfusion.com\/news\/2004\/0602cisco.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-1307","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\/1307","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=1307"}],"version-history":[{"count":1,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/1307\/revisions"}],"predecessor-version":[{"id":3794,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/1307\/revisions\/3794"}],"wp:attachment":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/media?parent=1307"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/categories?post=1307"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/tags?post=1307"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}