{"id":4934,"date":"2018-08-29T14:36:17","date_gmt":"2018-08-29T12:36:17","guid":{"rendered":"https:\/\/www.boc.de\/watchguard-info-portal\/?p=4934"},"modified":"2018-10-24T14:09:38","modified_gmt":"2018-10-24T12:09:38","slug":"webblocker-server-version-1-0-jetzt-ab-fireware-12-2-verfuegbar","status":"publish","type":"post","link":"https:\/\/wordpress.boc.de\/watchguard-info-portal\/2018\/08\/webblocker-server-version-1-0-jetzt-ab-fireware-12-2-verfuegbar\/","title":{"rendered":"WebBlocker Server Version 1.0 jetzt ab Fireware 12.2 verf\u00fcgbar"},"content":{"rendered":"<p>Die WebBlocker Server Version 1.0 ist verf\u00fcgbar f\u00fcr VMware (v. 5.x. + und Hyper-V f\u00fcr Microsoft Windows 2008 R2, 2012 oder 2012 R2 64 Bit). Au\u00dferdem ist eine Firebox notwendig, die den WebBlocker On-Premises Server abfragen soll. Es werden nur Firmware Versionen ab 12.2 aufw\u00e4rts unterst\u00fctzt, d.h. nur f\u00fcr die T- und M-Modelle erh\u00e4ltlich. Die Firebox XTM-Series wird die Version 12.2 nicht mehr enthalten.<br \/>\n<!--more--><\/p>\n<p>Wer die entsprechende Lizenzierung f\u00fcr den WebBlocker Service besitzt kann ab sofort die zutreffenden Pakete im\u00a0<a href=\"https:\/\/watchguardsupport.secure.force.com\/software\/\" target=\"_blank\" rel=\"noopener\">WatchGuard Software Download Center\u00a0<\/a>herunterladen.<\/p>\n<p>Wie Sie den WebBlocker Server On-Premises installieren k\u00f6nnen beschreiben wir in diesem <a href=\"https:\/\/www.boc.de\/watchguard-info-portal\/2018\/08\/installation-des-webblocker-on-premises-servers\/\" target=\"_blank\" rel=\"noopener\">HOWTO-Blogartikel<\/a>.<\/p>\n<p>WatchGuards SurfControl Service geht am 30.11.2018 End-of-Life. F\u00fcr alle die sich bisher gegen die WebSense Cloud Abfrage und f\u00fcr den lokal installierten Surfcontrol Server entschieden haben, bedeutet das, dass alle gef\u00fchreten Lookups nach dem Datum auf &#8220;uncategorized&#8221; gestellt werden und die Migrationsoptionen ber\u00fccksichtigt werden m\u00fcssen um die Funktion der URL Kategorisierung beizubehalten. Wer weiterhin eine lokale Abfrage bevorzugt, bekommt nun mit dem WebBlocker Server Version 1.0 eine geeignete Nachfolge. Gr\u00fcnde f\u00fcr eine Nutzung des WebBlocker Servers k\u00f6nnen bspw. Datenschutz- oder Performancegr\u00fcnde sein, da die<span style=\"font-size: inherit;\">\u00a0Requests der abgefragten URLs nicht ins Internet in die Cloud wandern sondern auf einen eigenen Server (eben On-Premises).<\/span><\/p>\n<p>anbei die Original-Meldung von WatchGuard:<\/p>\n<blockquote><p><em>WatchGuard\u2019s SurfControl service will reach end-of-life on November 30, 2018. All lookups conducted against the SurfControl service will return \u201cuncategorized\u201d after this date and migration options will need to be considered to maintain URL categorization functionality.<\/em><br \/>\n<em>While the Firebox family of network security products provide an equivalent URL filtering capability with WebBlocker Cloud on our flagship UTM product, WatchGuard\u2019s Fireware roadmap for Q3 2018 also includes a standalone virtual WebBlocker Server instance that offers many of the benefits customers have previously enjoyed with WatchGuard\u2019s SurfControl service. The WebBlocker Server is\u00a0available for VMware (v. 5.x.+ and Hyper-V for Microsoft Windows 2008 R2, 2012, or 2012 R2 64-bit) and available for download by customers who have the appropriate WebBlocker subscription on Tuesday, August 28, 2018.<\/em><\/p>\n<p><em>WatchGuard customers who need on-premise URL filtering upon our Fireware 12.2 release have three options:<\/em><\/p>\n<ul>\n<li><em>Upgrade to Fireware 12.2 and use the WebBlocker cloud service for URL filtering<\/em><\/li>\n<li><em>Upgrade to Fireware 12.2 and use WebBlocker Server, available in August 2018<\/em><\/li>\n<li><em>Remain on current version of Fireware 12.1.x (or earlier) and leverage existing WebBlocker cloud service for URL filtering (as the SurfControl service will no longer be available after November 2018)<\/em><\/li>\n<\/ul>\n<p><em>Note: XTM customers will not be able to upgrade to Fireware 12.2, but can still use Fireware 12.1.x or earlier.<\/em><\/p>\n<p><em>After the Fireware 12.2 release, support for these new features will be as follows:<\/em><\/p>\n<ul>\n<li><em>WebBlocker Server will not be compatible with previous versions of Fireware 12.1.x<\/em><\/li>\n<li><em>WSM 12.2 will not be capable of managing SurfControl settings on devices that run 12.1.x or lower<\/em><\/li>\n<\/ul>\n<p><em>This offering for a virtual WebBlocker server helps to serve customer environments where regulatory compliance or even ISP constraints inhibit\u00a0the web connections that allow WebBlocker URL filtering to function as designed through the WatchGuard UTM.\u00a0<\/em><\/p>\n<h5><em>How can I get started?<\/em><\/h5>\n<p><em>Qualifying Firebox M-series and T-series appliances with active Basic Security or\u00a0Total Security Subscriptions can obtain this update without additional charge by downloading the applicable packages from the WatchGuard Software Download Center.<\/em><\/p><\/blockquote>\n","protected":false},"excerpt":{"rendered":"<p>Die WebBlocker Server Version 1.0 ist verf\u00fcgbar f\u00fcr VMware (v. 5.x. + und Hyper-V f\u00fcr Microsoft Windows 2008 R2, 2012 oder 2012 R2 64 Bit). Au\u00dferdem ist eine Firebox notwendig, die den WebBlocker On-Premises Server abfragen soll. Es werden nur Firmware Versionen ab 12.2 aufw\u00e4rts unterst\u00fctzt, d.h. nur f\u00fcr die T- und M-Modelle erh\u00e4ltlich. Die Firebox XTM-Series wird die Version 12.2 nicht mehr enthalten.<\/p>\n","protected":false},"author":4,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[445],"tags":[456,470,107],"class_list":["post-4934","post","type-post","status-publish","format-standard","hentry","category-aktuelle-nachrichten","tag-fireware-12-2","tag-on-premise","tag-webblocker"],"_links":{"self":[{"href":"https:\/\/wordpress.boc.de\/watchguard-info-portal\/wp-json\/wp\/v2\/posts\/4934"}],"collection":[{"href":"https:\/\/wordpress.boc.de\/watchguard-info-portal\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/wordpress.boc.de\/watchguard-info-portal\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/wordpress.boc.de\/watchguard-info-portal\/wp-json\/wp\/v2\/users\/4"}],"replies":[{"embeddable":true,"href":"https:\/\/wordpress.boc.de\/watchguard-info-portal\/wp-json\/wp\/v2\/comments?post=4934"}],"version-history":[{"count":5,"href":"https:\/\/wordpress.boc.de\/watchguard-info-portal\/wp-json\/wp\/v2\/posts\/4934\/revisions"}],"predecessor-version":[{"id":5448,"href":"https:\/\/wordpress.boc.de\/watchguard-info-portal\/wp-json\/wp\/v2\/posts\/4934\/revisions\/5448"}],"wp:attachment":[{"href":"https:\/\/wordpress.boc.de\/watchguard-info-portal\/wp-json\/wp\/v2\/media?parent=4934"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/wordpress.boc.de\/watchguard-info-portal\/wp-json\/wp\/v2\/categories?post=4934"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/wordpress.boc.de\/watchguard-info-portal\/wp-json\/wp\/v2\/tags?post=4934"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}