WSM User Guide - WatchGuard Technologies

WSM User Guide - WatchGuard Technologies WSM User Guide - WatchGuard Technologies

watchguard.com
from watchguard.com More from this publisher
12.07.2015 Views

Activating Intrusion Prevention (IPS)Updating GAV signatures or the GAV engine manuallyGateway AntiVirus can be configured to update signatures and the GAV engine automatically. You canalso update signatures or the GAV engine manually. If the signatures or engine on the Firebox are notcurrent, you are not protected from the latest viruses and attacks. To update the services manually:1 Start Firebox System Manager.2 Click the Security Services tab.Security service status appears.3 Click Update for the service you want to update. You must type your configuration passphrase.The Firebox downloads the most recent available signature update or the most recent available engine for GatewayAntiVirus. You see information about the update in Traffic Monitor.If no updates are available, the Update button is not active.Updating the antivirus softwareBecause there are new types of attacks all the time, you must regularly update your antivirus software.When it is necessary, WatchGuard releases updates to the antivirus database and to the antivirus software.When we release an update, you get an e-mail message from LiveSecurity. You have access to allupdates while your Gateway AntiVirus subscription is active.To download software updates, log in to your LiveSecurity® account at:www.watchguard.com/supportActivating Intrusion Prevention (IPS)Hackers use many methods to attack computers on the Internet. The function of these attacks is tocause damage to your network, get sensitive information, or use your computers to attack other networks.These attacks are known as intrusions.You use Intrusion Prevention Service to find and stop attacks with the WatchGuard proxies. The Firebox®Intrusion Prevention Service examines DNS, FTP, HTTP, and SMTP traffic. It uses the TCP proxy to scanother TCP-based traffic.Before you use IPS in a proxy policy, you must run the Activate Intrusion Prevention wizard to activatethe feature and create a basic configuration. To do this:1 From WatchGuard System Manager, select the Firebox that will use IPS.2 Select Tools > Policy Manager.You can also click the Policy Manager icon on the WatchGuard System Manager toolbar.314 WatchGuard System Manager

Activating Intrusion Prevention (IPS)3 From Policy Manager, select Tasks > Intrusion Prevention > Activate.The Activate Intrusion Prevention wizard starts.4 Click Next.5 Click through the wizard and add the information it asks for. The wizard shows different screensdepending on if you already have proxy policies in your configuration. I f you do not, the wizardhelps you create a proxy policy. You can then use the wizard again to configure IPS, or see theinstructions in the subsequent section. The screens are:Select proxy policies to enableThis screen shows a list of proxy policies that are already defined on your Firebox. From the list,select the proxy policies you want to enable IPS for. Any policies that have IPS already enabled aregrayed out.Create new proxy policiesThis screen shows the proxy types whose corresponding policies do not currently exist. If, forexample, you have already created an SMTP policy, it does not appear in the list.To create a policy, select the corresponding check box. If you select SMTP, enter the mail server IPaddress. This wizard creates a default SMTP policy, which is a static NAT policy. To create this defaultSMTP policy, you must have at least one external interface with a static IP address or PPPoE. Onlyone policy is created even if you have more than one external interface. The To field of the policy isa static NAT entry (the static IP address of the first external interface to the specified mail service IPaddress). If this default policy does not meet your requirements, you can create an SMTP policy inPolicy Manager before you run this wizard.Select Advanced Intrusion Prevention settings (HTTP and TCP only)If you use the wizard to add an HTTP or TCP policy, you can select protection against InstantMessaging (IM), Peer-to-Peer (P2P), and Spyware.User Guide 315

Activating Intrusion Prevention (IPS)3 From Policy Manager, select Tasks > Intrusion Prevention > Activate.The Activate Intrusion Prevention wizard starts.4 Click Next.5 Click through the wizard and add the information it asks for. The wizard shows different screensdepending on if you already have proxy policies in your configuration. I f you do not, the wizardhelps you create a proxy policy. You can then use the wizard again to configure IPS, or see theinstructions in the subsequent section. The screens are:Select proxy policies to enableThis screen shows a list of proxy policies that are already defined on your Firebox. From the list,select the proxy policies you want to enable IPS for. Any policies that have IPS already enabled aregrayed out.Create new proxy policiesThis screen shows the proxy types whose corresponding policies do not currently exist. If, forexample, you have already created an SMTP policy, it does not appear in the list.To create a policy, select the corresponding check box. If you select SMTP, enter the mail server IPaddress. This wizard creates a default SMTP policy, which is a static NAT policy. To create this defaultSMTP policy, you must have at least one external interface with a static IP address or PPPoE. Onlyone policy is created even if you have more than one external interface. The To field of the policy isa static NAT entry (the static IP address of the first external interface to the specified mail service IPaddress). If this default policy does not meet your requirements, you can create an SMTP policy inPolicy Manager before you run this wizard.Select Advanced Intrusion Prevention settings (HTTP and TCP only)If you use the wizard to add an HTTP or TCP policy, you can select protection against InstantMessaging (IM), Peer-to-Peer (P2P), and Spyware.<strong>User</strong> <strong>Guide</strong> 315

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!