{"id":1423,"date":"2005-05-19T00:00:00","date_gmt":"2005-05-19T00:00:00","guid":{"rendered":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/2005\/05\/19\/f5-buys-watchfire-firewall\/"},"modified":"2021-12-30T11:39:21","modified_gmt":"2021-12-30T11:39:21","slug":"f5-buys-watchfire-firewall","status":"publish","type":"post","link":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/2005\/05\/19\/f5-buys-watchfire-firewall\/","title":{"rendered":"F5 buys Watchfire firewall"},"content":{"rendered":"<p>F5 Networks has acquired the web application firewall business of security firm Watchfire for an undisclosed sum.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>The two firms said that they would work together to migrate AppShield customers to F5&#8217;s TrafficShield application firewall product, a technology F5 acquired when it bought MagniFire WebSystems last year.<\/p>\n<p>The deal gives F5 access to over 250 AppShield customers.  By adding AppShield to F5, Watchfire can concentrate on its core web application security scanning business, AppScan, and online risk management platform, WebXM.  F5&#8217;s director of marketing in Europe said components of Watchfire&#8217;s technology would be brought into F5&#8217;s TrafficShield.<\/p>\n<p>F5 has created a dedicated professional services team to manage the transition for AppShield users and partners over to TrafficShield.  Appshield users will continue to receive support from Watchfire for the duration of their current maintenance agreements, he said.<\/p>\n<p>http:\/\/www.xatrix.org\/article3801.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-1423","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\/1423","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=1423"}],"version-history":[{"count":1,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/1423\/revisions"}],"predecessor-version":[{"id":3910,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/1423\/revisions\/3910"}],"wp:attachment":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/media?parent=1423"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/categories?post=1423"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/tags?post=1423"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}