Introduction

Fireware How To
Logging and Notification
How do I read Fireware log messages?

Introduction
Understanding the log messages the Firebox sends to the log file is a critical function for a Firebox administrator. The log messages give you important information about the flow of traffic through your network. The log messages are also a key component in troubleshooting problems that occur in your network. This document explains the types of log messages the Firebox generates. It gives examples of traffic and alarm log messages for Fireboxes using Fireware appliance software. For a list of Fireware event log messages, go to the Reference Guide and review the Log Messages chapter.

Types of Log Messages

The WatchGuard Firebox X Core and Firebox X Peak send log messages to a WatchGuard Log Server. They can also send log messages to a syslog server or keep logs locally on the Firebox. It is your decision to send logs to any or all of these locations. You can see log messages in real time using the WatchGuard System Manager Traffic Monitor. You can also show the logs in the LogViewer. The log messages are kept in an XML file with a .wgl.xml extension in the WatchGuard directory on the Log Server. If it becomes necessary, you can open this file using any XML tool to see log messages. The Firebox sends four types of log messages: Traffic logs Alarm logs Event logs Diagnostic logs

Traffic logs
The Firebox sends traffic logs as it applies packet filter and proxy rules to traffic passing through the Firebox.

Alarm logs
Alarm logs are sent when an alarm condition is met. The Firebox sends the alarm to the Traffic Monitor and Log Server and triggers the specified action. Some alarms are set in your Firebox configuration. For example, you can use Policy Manager to configure an alarm to occur when a certain threshold is met. Other alarms are set by default. The Firebox sends an alarm log when a network connection on one of the Firebox interfaces fails. This cannot be changed in your configuration. The Firebox never sends more than 10 alarms in 15 minutes for the same set of conditions. There are eight categories of alarm logs: System, IPS, AV, Policy, Proxy, Probe, Denial of service, and Traffic.

Event logs
Event logs are created because of Firebox user activity. Events that cause event logs include: Firebox start up/shut down Firebox and VPN authentication Process start up/shut down Problems with the Firebox hardware components Any task done by the Firebox administrator

Diagnostic logs

Diagnostic logs are more detailed log messages sent by the Firebox that you can use to help troubleshoot problems. You can select the level of diagnostic logging to see in your traffic monitor, or write to your log file. You can configure the diagnostic log level from Policy Manager: select Setup > Logging > Advanced Diagnostics. The available levels are off, low, medium, high, and advanced. We do not recommend that you set the logging level to advanced unless you are working with a technical support team to diagnose a problem, as it can cause the log file to fill up very quickly.

Traffic Logs
Most of the logs shown in Traffic Monitor are traffic logs. Traffic logs show the traffic that moves through your Firebox and how the packet filter and proxy policies were applied. Traffic Monitor shows all of the log messages from the Firebox that are recorded in your log file.

Packet Filter Logs

Packet filter logs contain a set number of fields. Here is an example of the XML output of a packet filter log message. The information will look different when you see the same log message in Traffic Monitor or LogViewer. Below the example, there is an explanation for each field that appears.
FWAllow d="2005-01-25T23:12:12" orig="HQFirebox" disp="Allow" pri="1" policy="SSHoutgoing-05" src_ip="192.168.130.59" dst_ip="10.10.171.98" pr="ssh" src_port="56952" dst_port="22" src_intf="1-Trusted" dst_intf="0-External" rc="100" msg="firewall pass, mss not exceeding 1460, idle timeout=43205 sec" pckt_len="60" ttl="63" log_type="tr"/

FWAllow Each packet filter log message starts with FWDeny or FWAllow. This header shows whether the packet was allowed or denied by the Firebox. d="2005-01-25T23:12:12" The date and time the event occurred, adjusted according to the time zone setting in Policy Manager: select Setup > System. orig="HQFirebox" The name or IP address (if no name is available) of the Firebox writing the log message. disp="Allow" The packet disposition. Can be deny or allow. pri="1" The priority of the log. The priority is used only for Net IQ reporting and is set to 1 (critical mode), 4 (warning mode), or 6 (normal allowed traffic). policy=ssh-outgoing-05 The name of the policy in Policy Manager that handled this packet. src_ip=192.168.30.159 The source IP address of this packet. dst_ip=10.10.171.98 The destination IP address for this packet. pr="ssh" The protocol used in this packet. src_port="56952" The source port for this packet. dst_port="22" The destination port for this packet.

Traffic Logs

src_intf="1-Trusted" The number of the source interface for this packet, and the name you have given the source interface for this packet (as defined in Policy Manager: select Network > Configuration). A source interface of trusted indicates that this packet originated behind the trusted interface of the Firebox. A source interface of external shows that the packet has come from outside the Firebox. dst_intf="0-External" The number of the destination interface for this packet, and the name you have given for the destination interface for this packet (as defined in Policy Manager: select Network > Configuration). rc="100" Return code for the packet. This information is used in Historical Reporting. msg=firewall pass, mss not exceeding 1460, idle timeout=43205 sec The message field. pckt_len="60" The length of the packet, in bytes. ttl="63" The packet time to live, in seconds. log_type="tr" The type of log message. All traffic logs use the tr log type.

Traffic logs showing NAT

A traffic log can also include fields that show how NAT (network address translation) was handled for this packet. An example log showing the ports the Firebox used to apply NAT to a packet is:
<FWAllow d="2005-02-02T09:46:53" orig="HQFirebox" disp="Allow" pri="1" policy="WGFirebox-Mgmt-outgoing-01" src_ip="192.168.1.15" dst_ip="172.16.1.45" pr="WatchGuard" src_port="2154" dst_port="4105" src_intf="1-Trusted" dst_intf="0-External" src_ip_nat="10.1.1.6" src_port_nat="15013" rc="100" msg="firewall pass, mss not exceeding 1460, idle timeout=43205 sec" pckt_len="48" ttl="128" log_type="tr"/>

Proxy Logs
When the Firebox processes an event that is handled by a proxy, it writes more than one log message. The first entry shows the same information as a packet filter log, but includes two more fields: proxy_act The name of the proxy action handling this packet. A proxy action is a set of rules for a proxy that can be applied to more than one policy. rule_name The name of the specific proxy rule handling this packet. content_type The type of content in the packet that is filtered by the proxy rule. Other log messages that the Firebox writes when an event is handled by a proxy contain a variable number of fields. Here is an example of a group of log messages created by a user request handled by a proxy:
<ProxyMatch d="2005-02-01T23:35:16" orig="HQFirebox" proc_id="cfm[1497]" disp="Allow" pri="6" policy="HTTP-proxy-01" src_ip="192.168.1.124" dst_ip="66.35.250.151" pr="tcp/ http" src_port="4345" dst_port="80" src_intf="1-Trusted" dst_intf="0-External" src_ip_nat="250.168.43.6" src_port_nat="13419" rc="590" msg="ProxyAllow: HTTP Header content type match" proxy_act="HTTP-Client.2" rule_name="text/*" content_type="text/ xml" log_type="tr"/> <ProxyHTTPReq d="2005-02-01T23:35:16" orig="HQFirebox" proc_id="cfm[1497]" disp="Allow" pri="6" policy="HTTP-proxy-01" src_ip="192.168.1.124" dst_ip="66.35.250.151" pr="tcp/http" src_port="4345" dst_port="80" src_intf="1Trusted" dst_intf="0-External" src_ip_nat="250.168.43.6" src_port_nat="13419" rc="525" msg="HTTP Request" proxy_act="HTTP-Client.2" op="GET" dstname="poli-

tics.slashdot.org" arg="/politics.rss" sent_bytes="345" rcvd_bytes="2727" log_type="tr"/> <ProxyConnEnd d="2005-02-01T23:35:16" orig="HQFirebox" proc_id="cfm[1497]" disp="Allow" pri="6" policy="HTTP-proxy-01" src_ip="192.1681.124" dst_ip="66.35.250.151" pr="tcp/http" src_port="4345" dst_port="80" src_intf="1Trusted" dst_intf="0-External" src_ip_nat="250.168.43.6" src_port_nat="13419" rc="523" msg="Conn End" proxy_act="HTTP-Client.2" log_type="tr"/>

Each proxy has its own set of messages. The tables here show the log messages each proxy can write to the log file, and the secondary fields for each log message.

SMTP Proxy Traffic Log Messages

Text in Message Field Associated Fields
SMTP GREETING hostname rule_name SMTP AUTH authtype rule_name SMTP HEADER header SMTP FROM ADDRESS address length response new_address header SMTP TO ADDRESS address new_address length response SMTP CONTENT TYPE content_type rule_name sender recipient SMTP Command keyword response SMTP FILENAME file_name rule_name sender recipients SMTP TIMEOUT timeout SMTP AV VIRUS virus filename content_type sender recipient SMTP AV TOO BIG filename type SMTP AV ERROR filename error sender recipient 4

Message Meaning Value that appears in associated field(s)

There is an invalid message in HELO state hostname sent in SMTP greeting name of rule matched in ruleset The AUTH type used matches a configured proxy rule AUTH type used name of rule matched in ruleset The SMTP header matches a configured proxy rule. header name The sender e-mail address matches a configured proxy rule the sender e-mail address (from envelope) length in bytes of address response code returned to client new address, if address rewrite used if header rewrite feature is used The recipient e-mail address matches a configured proxy rule recipient e-mail address (from envelope) new address, if address rewrite used length in bytes of address response code returned to client The content type matches a configured proxy rule the content type found by the SMTP proxy name of rule matched in ruleset sender e-mail address (from envelope) recipient e-mail addresses (from envelope) The full SMTP command as received from the SMTP client values include EXPN, HELP, NOOP, etc. response code returned to client The filename matches a configured proxy rule the file name name of rule matched in ruleset sender e-mail address (from envelope) recipient e-mail addresses (from envelope) The connection idle timeout was reached number of seconds configured to time-out The SMTP proxy found a virus the name of the virus found the filename the content type of the virus found sender e-mail address (from envelope) recipient e-mail addresses (from envelope) An attachment was too big to scan the filename the content type of the attachment The SMTP cannot finish an antivirus scan, usually because an attachment was encrypted file name description of error sender e-mail address (from envelope) recipient e-mail addresses (from envelope)

Traffic Logs

SMTP Proxy Traffic Log Messages

Text in Message Field Associated Fields
SMTP REQ rcvd_bytes sent_bytes sender recipient SMTP MESSAGE FORMAT header mime_error sender recipients SMTP IPS MATCH ips_msg signature_id SMTP TOO MANY RECIPIENTS num_recipients SMTP RESPONSE SIZE TOO LONG headers_size SMTP LINE LENGTH TOO LONG line_length SMTP MESSAGE SIZE TOO LONG size SMTP HEADERS SIZE TOO LONG headers_size

Message Meaning Value that appears in associated field(s)

Auditing information about an SMTP request size of message before proxying size of message after proxying sender e-mail address (from envelope) recipient e-mail addresses (from envelope) The SMTP header uses a format that is not correct header with improper format description of format error sender e-mail address (from envelope) recipient e-mail addresses (from envelope) The SMTP proxy found an IPS signature match description of the signature that matched the signature ID of the rule that matched The number of e-mail addresses in the TO field is larger than the configured limit number of recipients The SMTP server sent a response that is too long total size of message headers (up to when log emitted; full headers can be larger) The SMTP client or server has sent a line that is longer than the configured limit total size of header line (up to when log emitted; full line can be larger) The SMTP client sent a message larger than the configured limit size in bytes of message received (up to when log emitted; full message can be larger) The SMTP client sent a header section that is larger than the SMTP limit total size of message headers (up to when log emitted; full headers can be larger)

DNS Proxy Traffic Log Messages

Text in Message Field Associated Fields
DNS INVALID NUMBER OF QUESTIONS DNS OVERSIZED QUERY NAME DNS COMPRESSED QUERY NAME DNS PARSE ERROR DNS NOT INTERNET CLASS query_class DNS DENIED OPCODE rulename query_opcode DNS DENIED QUERY TYPE rulename query_type DNS UNDERSIZED QUESTION DNS OVERSIZED QUESTION DNS TIMEOUT DNS UNDERSIZED ANSWER

Message Meaning Value that appears in associated field(s)

There is more than one RRs inquiry in one DNS request The total DNS query frame size is larger than the DNS protocol limit The client used a DNS compression scheme in the query name The DNS request or response is not in the correct format. The DNS query is not in IP protocol format name or number of its class The opcode matches a configured proxy rule name of rule matched in ruleset name of the denied opcode (IQUERY, STATUS, UPDATE) The query type matches a configured proxy rule name of rule matched in ruleset name of denied type (a, MX, NS) The name component of the DNS query is too small The name component of the DNS query is too large There is no response to a DNS query before the connection time-out occurred The DNS response is too small

DNS Proxy Traffic Log Messages

Text in Message Field Associated Fields
DNS INVALID RESPONSE DNS QUESTION NOT ALLOWED rulename query_type question DNS REQ rulename query_type question DNS IPS MATCH ips_msg signature_id

Message Meaning Value that appears in associated field(s)

The DNS response does not match the request The query type matches a configured proxy rule name of rule matched in ruleset name of denied type (a, MX, NS) name in query Auditing information for the DNS proxy name of rule matched in ruleset name of denied type (a, MX, NS) name in query The DNS proxy found an IPS signature match description of the signature that matched the signature ID of the rule that matched

FTP Proxy Traffic Log Messages

Text in Message Field Associated Fields
FTP USERNAME TOO LONG length FTP PASSWORD TOO LONG length FTP FILENAME TOO LONG length FTP COMMAND TOO LONG length FTP BAD COMMAND rule_name command FTP BAD DOWNLOAD rule_name file_name FTP BAD UPLOAD rule_name file_name FTP TIMEOUT FTP REQ command FTP REQUEST FORMAT command FTP IPS MATCH ips_msg signature_id

Message Meaning Value that appears in associated field(s)

Username is longer than the configured limit length of line Password line is longer than the configured limit length of line Filename line is longer than the configured limit length of line Command line is longer than the configured limit length of line The command matched a configured proxy rule name of rule matched in ruleset the command requested The file name or name pattern matches a configured proxy rule name of rule matched in ruleset name of file being blocked The file name or name pattern matches a configured proxy rule name of rule matched in ruleset name of file being blocked There was no response to an FTP request before the IP-level idle connection time-out Auditing information for the FTP proxy the command requested The command in the FTP request is not in the correct format the command requested The FTP proxy found an IPS signature match description of the signature that matched the signature ID of the rule that matched

Traffic Logs

HTTP Proxy Traffic Log Messages

Text in Message Field Associated Fields
HTTP INTERNAL ERROR HTTP SERVER RESPONSE TIMEOUT HTTP CLIENT REQUEST TIMEOUT HTTP CLOSE COMPLETE TIMEOUT HTTP START LINE OVERSIZE HTTP REQUEST LINE PARSE ERROR line HTTP STATUS LINE PARSE ERROR line HTTP HEADER LINE OVERSIZE line HTTP HEADER BLOCK OVERSIZE line HTTP HEADER BLOCK PARSE ERROR HTTP REQUEST URL PATH MISSING line HTTP REQUEST URL MATCH rulename dstname arg HTTP CHUNK SIZE LINE OVERSIZE line HTTP CHUNK SIZE INVALID line HTTP CHUNK CRLF TAIL MISSING line HTTP FOOTER LINE OVERSIZE line HTTP FOOTER BLOCK OVERSIZE line HTTP FOOTER BLOCK PARSE ERROR HTTP BODY CONTENT TYPE MATCH rulename HTTP HEADER MALFORMED line HTTP HEADER CONTENT LENGTH INVALID HTTP HEADER TRANSFER ENCODING INVALID HTTP HEADER TRANSFER ENCODING MATCH rulename encoding The total length of all headers for a request or response is greater than the configured limit. header line that exceeded the limit The HTTP header block is not in the correct format. The HTTP request does not include a URL path. request line that caused error The HTTP request includes a URL specified in the proxy ruleset. name of rule matched in ruleset host name from requested URL path and query-string from requested URL The line setting the size of the next response data chunk has a value that is too big. request line that caused error The line setting the size of the next response data chunk has an invalid value. request line that caused error The carriage-return/line-feed (CRLF) at the end of a data chunk is not there. the line that caused the error The length of an individual footer line is greater than the configured limit. request line that exceeded the limit The total length of all footers for a request or response is greater than the configured limit. footer line that exceeded the limit The HTTP footer block is not in the correct format. The content type in the response body matches a type configured in the proxy rule set. name of rule matched in ruleset An individual HTTP header is not in the correct format. the line with the malformed header The Content-Length response header value is not a valid number. The response header includes illegal or unsupported transfer encoding. The response header includes transfer encoding that matches the configured proxy rule set. name of rule matched in ruleset Transfer-Encoding header value The HTTP server did not send a response before the configured timeout The HTTP client did not send a request before the configured time-out The remote host did not promptly complete the closing of the TCP connection. The first line of the HTTP request or response is larger than the configured limit (maximum header line length). The first line of the HTTP request is not in the correct format. header line that caused error The first line of the HTTP response is not in the correct format. status line that caused error The length of an individual header is greater than the configured limit. header line that exceeded the limit

Message Meaning Value that appears in associated field(s)

HTTP Proxy Traffic Log Messages

Text in Message Field Associated Fields
HTTP HEADER CONTENT TYPE MISSING HTTP HEADER CONTENT TYPE MATCH rulename content_type HTTP REQUEST VERSION MATCH rulename line HTTP REQUEST METHOD MATCH rulename method HTTP HEADER MATCH rulename header HTTP HEADER COOKIE DOMAIN MATCH rulename domain HTTP REQUEST HOST MISSING HTTP HEADER AUTH SCHEME MATCH rulename scheme HTTP REQUEST METHOD UNSUPPORTED method HTTP REQUEST PORT MISMATCH

Message Meaning Value that appears in associated field(s)

The Content-Type response header, which sets the response body MIME type, is missing or has an empty value. The Content-Type response header, which sets the response body MIME type, matches the configured proxy rule set. name of rule matched in ruleset value of content-type header The request protocol version (such as HTTP/1.1) matches the configured proxy rule set. name of rule matched in ruleset request line that caused error The HTTP request method matches the configured proxy rule set. name of rule matched in ruleset request method that caused error The individual HTTP header (name and value) matches the configured proxy rule set. name of rule matched in ruleset header line that matched The domain included in the Set-Cookie response header, or if none, then the host set in the request, matches the configured proxy rule set. (This feature is used to prevent cookies from a specified Web site.) name of rule matched in ruleset domain parameter from Set-Cookie response header or (if not present in cookie) hostname in requested URL The server host name is not included in the request line or in the host request header. The WWW-Authenticate response header incudes an authentication scheme that matches the configured proxy rule set. name of rule matched in ruleset scheme parameter from WWW-Authorize response header The request includes a method not currently supported. This can result from the use of an HTTP-based protocol with additional nonHTTP methods. request method that caused error The destination TCP port of the connection does not match the TCP port used in the header. Can indicate an attempt to get access to an outside proxy server. An HTTP request was denied by WebBlocker. comma delimited list of WebBlocker categories which match host name from requested URL path and query-string from requested URL The WebBlocker server is not responding. name of ProtocolHandler Helper explanation of problem The URL component of the HTTP request start line is too big. Auditing information about an HTTP request. HTTP request method hostname from requested URL path and query-string from requested URL The HTTP header matches an IPS signature. description of the signature that matched the signature ID of the rule that matched The HTTP body matches an IPS signature. description of the signature that matched the signature ID of the rule that matched Auditing information for an HTTP request that has a very large response.

HTTP REQUEST CATEGORIES cats dstname arg HTTP SERVICE UNAVAILABLE service details HTTP REQUEST URL PATH OVERSIZE HTTP REQ op dstname arg HTTP HEADER IPS MATCH ips_msg signature_id HTTP BODY IPS MATCH ips_msg signature_id HTTP BYTECOUNT UPDATE

Alarm Logs

TCP Proxy Traffic Log Messages

Text in Message Field Associated Fields
TCP REQ outgoing_msg TCP IPS MATCH ips_msg signature_id

Message Meaning Value that appears in associated field(s)

the mode the handler is in. TCP proxy found an IPS signature match. description of the signature that matched the signature ID of the rule that matched

Alarm Logs
Alarm logs are sent when an alarm condition is met. The Firebox sends the alarm log to the Traffic Monitor and Log Server and triggers the specified action. Some alarms are set in your Firebox configuration. For example, you can use Policy Manager to configure an alarm to occur when a certain threshold is met. Other alarms are set by default. The Firebox sends an alarm log when a network connection on one of the Firebox interfaces fails. This cannot be changed in your configuration. The Firebox never sends more than 10 alarms in 15 minutes for the same set of conditions. There are eight categories of alarm logs: System, IPS, AV, Policy, Proxy, Probe, Denial of service, and Traffic. There is a table below for each category of alarms, showing the format of the alarm log messages in each category.

Policy Alarms
Default Name
Policy

Message Format
alarm_name=WGRD_PM_BP_Alar m, alarm id, timestamp, message, policy name, source IP, destination IP, protocol, source port, destination port, source interface, destination interface, log_type=al

Example Message
alarm_name="WGRD_PM_BP_Alar m" alarm_id="4001" time="Wed Mar 2 07:41:21 2005 (PST)" msg="Block" policy="WGRD_PM_BP_Policy" src_ip="24.56.20.79" dst_ip="192.168.30.164" pr="tcp/ sun-rpc" src_port="1727" dst_port="111" src_intf="0External" dst_intf="2-Optional-1" log_type="al"/

Caused By
These alarms are caused by events associated with each policy.

Proxy Alarms
Default Name
Proxy

Message Format
alarm_name=Proxy, alarm_id, time, message, source IP, destination IP, protocol, source port, destination port, source interface destination interface, log_type=al

Example Message
alarm_name="Proxy" alarm_id="6001" time="Tue Aug 3 00:49:35 2004 (PST)" msg="ProxyAllow/HTTP Request method match" src_ip="192.168.1.102" dst_ip="16.0.0.107" pr="tcp/smtp" src_port="1384" dst_port="25" src_intf="PPTP" dst_intf="1Trusted" log_type="al"/

Caused By
These alarms are caused by events associated with each proxy action.

System Alarms
Default Name
System

Message Format
alarm _name detected, message_string.

Example Message
System detected. [1401-0512@H] user abc failed to log in from 192.168.228.226. System detected. [1401-0202@H] Number of IPSec tunnels 2500 reaches max IPSec tunnels allowed.

Caused By
These alarms are triggered by system events.

Denial of Service (DoS) Alarms

Default Name
DOS

Message Format
alarm_name detected. message_string.

Example Message
NOTE: The content of this alarm message is based on what DOS event triggered it. See the examples below. SYN-Attack detected. TCP SYN attack detected on interface 1. UDP-Flood detected. UDP Flood attack detected on interface 1. ICMP-Flood detected. ICMP Flood attack detected on interface 1. Ping-of-Death detected. PING-OFDEATH attack detected on interface 1. Source-Route detected. SOURCEROUTE attack detected on interface 1. IPSec-Flood detected. IPSEC Flood attack detected on interface 1.

Caused By
These alarms are triggered by any DOS events.

SYNAttack UDPFlood ICMPFlood Ping-ofDeath SourceRoute

alarm _name detected. TCP SYN attack detected on interface interface_number. alarm _name detected. UDP Flood attack detected on interface interface_number. alarm_name detected. ICMP Flood attack detected on interface interface_number. alarm_name detected, PING-OFDEATH attack detected on interface interface_number. alarm_name detected. SOURCEROUTE attack detected on interface interface_number. alarm_name detected. IPSEC Flood attack detected on interface interface_number. alarm_name detected. IKE Flood attack detected on interface interface_number. alarm_name detected. Denial-ofService attacks (>threshold) from source IP address/subnet mask detected on interface interface_number. alarm_name detected. Denial-ofService attacks (>threshold) for destination IP address/subnet mask detected on interface interface_number.

These alarms are triggered by SYN attacks. These alarms are triggered by UDP Flood attacks. These alarms are triggered by ICMP Flood attacks. These alarms are triggered by Ping-ofDeath attacks. These alarms are triggered by SourceRoute attacks. These alarms are triggered by high severity level and IPSec Flood attacks. These alarms are triggered by IKE Flood attacks. These alarms are triggered by Distributed Denial of Service Source attacks.

IPSecFlood

IKE-Flood

IKE-Flood detected. IKE Flood attack detected on interface 1.

DDOSAttack-Src

DDOS-Attack-Src detected. Denialof-Service attacks (.50) from source 192.168.226.226/255.255.255.255 detected on interface 1.

DDOSAttackDest

DDOS-Attack-Src detected. Denialof-Service attacks (.50) for destination 192.168.226.226/ 255.255.255.255 detected on interface 1.

These alarms are triggered by Distributed Denial of Service Destination attacks.

10

Alarm Logs

Denial of Service (DoS) Alarms

Default Name
Port-Scan

Message Format
alarm_name detected. message_string.

Example Message
Port-Scan detected. Port scan threshold 300 reached, 300 ports scanned by 192.168.228.226 in 10 seconds. IP-Scan detected. IP scan threshold 300 reached, 300 IPs scanned by 192.168.228.226 in 10 seconds. IP-Spoofing detected. IP source spoofing detected, src_intf=30, src_ip=192.168.228.226. Tear-Drop detected. TEAR-DROP attack detected on interface 1.

Caused By
These alarms are triggered by Port Space Probe attacks.

IP-Scan

alarm_name detected. message_string. alarm_name detected. message_string. alarm_name detected. TEAR-DROP attack detected on interface interface_number.

These alarms are triggered by Address Space Probe attacks. These alarms are triggered by IP Spoofing attacks. These alarms are triggered by Tear-Drop attacks.

IPSpoofing Tear-Drop

Traffic Alarms
Default Name
Traffic

Message Format
alarm _name detected, message_string.

Example Message
NOTE: The content of this alarm message is based on what traffic event triggered the alarm. See the examples below. ESP-Auth-Error detected. ESP Authentication error, policy_id=2, local_ip=10.10.10.10, peer_ip=192.168.228.226, spi=12345678, sa_id=1000, interface=1, the first 80 bytes are A0 B1 C2.........

Caused By
These alarms are triggered by any traffic events. These alarms are triggered by the traffic event ESP-AUTH_ERR.

ESP-AuthError

alarm_name detected. ESP Authentication error, policy_id=policy_id_number, local_ip=local_IP_address, peer_ip=peer_IP_address, spi=spi, sa_id=ID_of_SA, interface=interface_number, the first (x) bytes are list_of_first x number of bytes. alarm_name detected. AH Authentication error, policy_id=policy_id_number, local_ip=local_IP_address, peer_ip=peer_IP_address, spi=spi, sa_id=ID_of_SA, interface=interface_number, the first (x) bytes are list_of_first x number of bytes.

AH-AuthError

AH-Auth-Error detected. AH Authentication error, policy_id=2, local_ip=10.10.10.10, peer_ip=192.168.228.226, spi=12345678, sa_id=1000, interface=1, the first 80 bytes are A0 B1 C2.........

These alarms are triggered by the traffic event AH_AUTH_ERR.

Traffic Alarms
Default Name
ESPReplayError

Message Format
alarm_name detected. ESP replay error, policy_id=policy_id_number, local_ip=local_IP_address, peer_ip=peer_IP_address, spi=spi, sa_id=ID_of_SA, interface=interface_number, the first (x) bytes are list_of_first x number of bytes. alarm_name detected. AH replay error, policy_id=policy_id_number, local_ip=local_IP_address, peer_ip=peer_IP_address, spi=spi, sa_id=ID_of_SA, interface=interface_number, the first (x) bytes are list_of_first x number of bytes. alarm_name detected. Invalid SPI %d(0x%x) detected on interface interface_number, the first (x) bytes are list_of_first x number of bytes. alarm_name detected. Policy error detected on interface interface_number, the first (x) bytes are list_of_first x number of bytes.

Example Message
ESP-Replay-Error detected. ESP replay error, policy_id=2, local_ip=10.10.10.10, peer_ip=192.168.228.226, spi=12345678, sa_id=1000, interface=1, the first 80 bytes are A0 B1 C2.........

Caused By
These alarms are triggered by the traffic event ESP_REPLAY_ERROR.

AHReplayError

AH-Replay-Error detected. AH replay error, policy_id=2, local_ip=10.10.10.10, peer_ip=192.168.228.226, spi=12345678, sa_id=1000, interface=1, the first 80 bytes are A0 B1 C2.........

These alarms are triggered by the traffic event AP_REPLAY_ERROR.

InvalidSPI

Invalid-SPI detected. Invalid SPI 12345678 (0xBC614E) detected on interface 1, the first 80 bytes are A0 B1 C2........ Other-Policy-Error detected. Policy error detected on interface 1, the first 80 bytes are A0 B1 C2............

These alarms are triggered by the traffic event INVALID_SPI. These alarms are triggered by the traffic event OTHER_AUTH_ERROR.

OtherPolicyError

Probe Alarms
Default Name
Any Probe Alarm

Message Format
Operator [Probe probe_name: probe_value (value) alarm_cond_op_name threshold (threshold)]

Example Message
NOTE: The content of this alarm message is based on the event that triggered the alarm. See the examples below. [Probe Link Status: 0.00 (value) becomes 0.00 (threshold)] OR [Probe Link Status: 1.00 (value) becomes 0.00 (threshold)] OR [Probe Link Status: 0.00 (value) becomes 0.00 (threshold)]

Caused By
These alarms are triggered by counter values.

LinkDown

These alarms are triggered by interface counters.

Gateway AntiVirus Service Alarms

Default Name
AV

Message Format
alarm_name-AV alarm id, timestamp, message, source IP, destination IP, protocol, source port, destination port, source interface, destination interface, virus name, sender, log_type=al

Example Message
alarm_name="AV" alarm_id="6001" time="Mon Aug 2 22:20:44 2004 (PST)" msg="SMTP Filename" src_ip="192.168.1.102" dst_ip="16.0.0.107" pr="tcp/smtp" src_port="1384" dst_port="25" src_intf="PPTP" dst_intf="1Trusted" virus="Eicar-TestSignature" sender="phillip@sjcqa.com" log_type="al"/

Caused By
These alarms are caused by events associated with each AV rule of the SMTP proxy action.

12

Event Logs

Intrusion Prevention Service Alarms

Default Name
IPS

Message Format
alarm_name=IPS, alarm id, timestamp, message, source IP, destination IP, protocol, source port, destination port, source interface, destination interface, IPS message, signature category, signature ID, log_type=al

Example Message
alarm_name="IPS" alarm_id="3001" time="Wed Aug 4 00:58:33 2004 (PST)" msg="IPS" src_ip="16.0.0.1" dst_ip="16.0.1.107" pr="tcp/http" src_port="4110" dst_port="80" src_intf="1-Trusted" dst_intf="0External" ips_msg="WEB-ATTACKS kill command attempt" signature_cat="http-request" signature_id="1335" log_type="al"/

Caused By
These alarms are caused by different protocol types.

Event Logs
Event logs are created because of Firebox user activity. Events that cause event logs include: Firebox start up/shut down Firebox and VPN authentication Process start up/shut down Problems with the Firebox hardware components Any task done by the Firebox administrator On a Firebox using Fireware appliance software, there are seven product components, including 27 different log modules, that create event and diagnostic log messages to send to the log server. The function of each log module is shown in the table that follows.

Description of Log Modules

Product Component VPN Log Module
IKE PPTP

Function
Internet Key Exchange daemon. Diagnose the configuration and operation of VPN tunnels. Point to Point Tunneling Protocol daemon. Diagnose the daemon that manages PPTP for VPN tunnels. Virtual Router Redundancy Protocol daemon. Diagnose the module that manages the virtual router for High Availability. High Availability Manager. Diagnose the module that manages High Availability operations. Transport (HA) Protocol. Diagnose the module that manages the High Availability transport protocol. DHCP client. Diagnose the module that gets IP addresses for DHCP clients. DHCP server. Diagnose the module that DHCP servers use to give IP addresses to clients. DHCP relay. Diagnose the module that relays DHCP requests to another server. Point to Point protocol daemon. Diagnose the daemon that gives you PPP protocol support for PPPoE and PPTP. Point to Point Protocol over Ethernet daemon. Diagnose the daemon that manages PPPoE. Connection Framework Manager. Diagnose the service that manages proxy protected connections.

High Availability

VRRP

HAM TPDAEMON

Dynamic IP

DHCLIENT DHCPD DHCRELAY PPP

PPPoE (shows in the log file as ADSL)

Proxy

CFM

Description of Log Modules

Product Component Log Module
SM

Function
Session Manager. Diagnose the module that converts network packet streams into TCP connections and UDP connections. Hypertext Transfer Protocol proxy. Diagnose the process that analyzes HTTP connections. Simple Mail Transfer Protocol proxy. Diagnose the process that analyzes SMTP connections. File Transfer Protocol proxy. Diagnose the process that analyzes FTP connections. Domain Name Service proxy. Diagnose the analysis service for DNS connections. WebBlocker Server daemon. Diagnose the module that gives you the list of Web sites to block. AntiVirus Server. Diagnose the server that supports AV detection. Configuration Maintenance Manager. Diagnose the module that manages device configuration. Simple Network Management Protocol daemon. Diagnose the module that can query for SNMP MIB and can send SNMP traps to the user. Monitoring Agent. Diagnose Alarm Manager, the module that collects alarms and determines the alarm response. Management Information Agent. Diagnose the module that captures appliance statistics. Monitor daemon. Diagnose the daemon that monitors the network link. Web server. Diagnose the device Web server that supports Web authentication and WSM. Dynamic VPN Control Protocol Client daemon. Diagnose the daemon that manages devices under DVCP control. Policy Management Module. Diagnose the module that manages and controls packet filter policies. Authentication Domain Manager. Diagnose the module that authenticates packet filters and VPN tunnels.

HTTP SMTP FTP DNS WEBBLOCKER AV

Management

CMM SNMP

MA

MIA MONITORD Webs (GOAHEAD) DVCPCD

Packet Filter Authentication

PMM ADM

Frequently Asked Questions About This Procedure

Is there a way to see the XML DTD or schema? XML Document Type Definition (DTD) and schemas define and order the elements and attributes used in an XML document. We provide a DTD and a schema for the Firebox XML log file in the FAQ section of www.watchguard.com/support. The information can help you use the data in the log file with third-party reporting or analysis tools. Is there a list of all the log messages generated by the Firebox? As part of its user documentation set, we supply a log catalog that includes the majority of the event logs produced by the Firebox. You can find this log catalog in the Reference Guide at: http://www.watchguard.com/help/docs/v82ReferenceGuide.pdf

SUPPORT:

COPYRIGHT 2006 WatchGuard Technologies, Inc. All rights reserved. WatchGuard, the WatchGuard logo, Firebox, and Core are registered trademarks or trademarks of WatchGuard Techwww.watchguard.com/support nologies, Inc. in the United States and/or other countries. U.S. and Canada +877.232.3531 All Other Countries +1.206.613.0456

14