WatchGuard Firebox System 7.0 User Guide

WatchGuard Firebox System 7.0 User Guide WatchGuard Firebox System 7.0 User Guide

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

Chapter 12: Setting Up Logging and NotificationLogging and notification are crucial to an effective networksecurity policy. Together, they make it possible to monitoryour network security, identify both attacks and attackers,and take action to address security threats and challenges.WatchGuard logging and notification features are bothflexible and powerful. You can configure your firewall tolog and notify a wide variety of events, including specificevents that occur at the level of individual services. Formore information on logging, see the following collectionof FAQs:https://support.watchguard.com/advancedfaqs/log_main.aspDeveloping Logging and Notification PoliciesWhen creating a logging policy, you spell out what getslogged and when an event or series of events warrantssending out a notification to the on-duty administrator.Developing these policies simplifies the setup of individualservices in the WatchGuard Firebox System. If you havefully mapped out a policy, you can more easily delegateconfiguration duties and ensure that individual efforts donot contradict the overall security stance or logging andnotification policies.Logging policySpecifically, the logging policy delineates:• Which events to log• Which service events to log• Which servers are allocated as log hosts• How large a log file is allowed to become and howoften a new log file is createdIn general, you want to log only the events that might indicatea potential security threat, and ignore events thatwould waste bandwidth and server storage space. Thisgenerally translates into logging spoofs, IP options, probes,200 WatchGuard Firebox System

Developing Logging and Notification Policiesand denied packets, and not logging allowed packets.Allowed packets should not be indicative of a securitythreat. Furthermore, allowed traffic usually far exceeds thevolume of denied traffic and would slow response times aswell as causing the log file to grow and turn over tooquickly.WatchGuard provides the option to log allowed events primarilyfor diagnostic purposes when setting up or troubleshootingan installation. Or, you might have a situationsuch as a very specialized service that uses an obscure,very high port number, and the service is intended for useonly by a small number of people in an organization. Inthat case you might want to log all traffic for that service soyou can monitor or review that service activity.Not all denied events need to be logged. For example, ifincoming FTP denies all incoming traffic from any sourceoutside to any destination inside, there is little point in loggingincoming denied packets. All traffic for that service inthat direction is blocked.Notification policyThe most important events that should trigger notificationare IP options, port space probes, address space probes,and spoofing attacks. These are configurable in the DefaultPacket Handling dialog box, described in “Default PacketHandling” on page 178.Other notifications depend on your Firebox configurationand how much time is available for interacting with it. Forexample, if you set up a simple configuration that enablesonly a few services and denies most or all incoming traffic,only a few circumstances warrant notification. On the otherhand, if you have a large configuration with many services;with many allowed hosts or networks for incoming traffic;popular protocols to specific, obscure ports; and several filteredservices added of your own design; you will need toset up a large, complex notification scheme. This type ofconfiguration is more vulnerable to attack. Not only areUser Guide 201

Chapter 12: Setting Up Logging and NotificationLogging and notification are crucial to an effective networksecurity policy. Together, they make it possible to monitoryour network security, identify both attacks and attackers,and take action to address security threats and challenges.<strong>WatchGuard</strong> logging and notification features are bothflexible and powerful. You can configure your firewall tolog and notify a wide variety of events, including specificevents that occur at the level of individual services. Formore information on logging, see the following collectionof FAQs:https://support.watchguard.com/advancedfaqs/log_main.aspDeveloping Logging and Notification PoliciesWhen creating a logging policy, you spell out what getslogged and when an event or series of events warrantssending out a notification to the on-duty administrator.Developing these policies simplifies the setup of individualservices in the <strong>WatchGuard</strong> <strong>Firebox</strong> <strong>System</strong>. If you havefully mapped out a policy, you can more easily delegateconfiguration duties and ensure that individual efforts donot contradict the overall security stance or logging andnotification policies.Logging policySpecifically, the logging policy delineates:• Which events to log• Which service events to log• Which servers are allocated as log hosts• How large a log file is allowed to become and howoften a new log file is createdIn general, you want to log only the events that might indicatea potential security threat, and ignore events thatwould waste bandwidth and server storage space. Thisgenerally translates into logging spoofs, IP options, probes,200 <strong>WatchGuard</strong> <strong>Firebox</strong> <strong>System</strong>

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

Saved successfully!

Ooh no, something went wrong!