Log Management. Configuring Syslog

Similar documents
SecBlade Firewall Cards Log Management and SecCenter Configuration Example

IPv4 ACLs, identified by ACL numbers, fall into four categories, as shown in Table 1. Table 1 IPv4 ACL categories

H3C Firewall and UTM Devices Log Management with IMC Firewall Manager Configuration Examples (Comware V5)

Protection Against Distributed Denial of Service Attacks

HP High-End Firewalls

IPv6 Firewall Support for Prevention of Distributed Denial of Service Attacks and Resource Management

HP A-F1000-A-EI_A-F1000-S-EI VPN Firewalls

H3C SecPath Series High-End Firewalls

Zone-Based Firewall Logging Export Using NetFlow

Configuring ACL Logging

HP Load Balancing Module

Object Groups for ACLs

Configuring Logging for Access Lists

SecBlade Firewall Cards Attack Protection Configuration Example

Network Address Translation Bindings

Object Groups for ACLs

Static and Default Routes

Configuring Logging for Access Lists

Firewall Stateful Inspection of ICMP

ASA Access Control. Section 3

Interchassis Asymmetric Routing Support for Zone-Based Firewall and NAT

History Page. Barracuda NextGen Firewall F

HP 830 Series PoE+ Unified Wired-WLAN Switch Switching Engine

HP Load Balancing Module

H3C SecPath Series Firewalls and UTM Devices

IPv6 Commands: ipv6 h to ipv6 mi

Configuration and Operation of FTD Prefilter

Object Groups for ACLs

Junos Security. Chapter 4: Security Policies Juniper Networks, Inc. All rights reserved. Worldwide Education Services

Monitoring and Maintaining ARP Information

ipv6 mobile home-agent (global configuration)

ipv6 hello-interval eigrp

Testing and Troubleshooting

HP High-End Firewalls

Chapter 4 Software-Based IP Access Control Lists (ACLs)

HP Firewalls and UTM Devices

Configuring ACLs. ACL overview. ACL categories. ACL numbering and naming

H3C S9500 QoS Technology White Paper

Cisco Exam Troubleshooting and Maintaining Cisco IP Networks (TSHOOT) Version: 6.0 [ Total Questions: 79 ]

HP Load Balancing Module

Modular Policy Framework. Class Maps SECTION 4. Advanced Configuration

IP Addressing: Fragmentation and Reassembly Configuration Guide

Stateful Network Address Translation 64

Summer Webinar Series

Threat Detection. Detecting Threats. The following topics describe how to configure threat detection statistics and scanning threat detection.

Network Security 1. Module 8 Configure Filtering on a Router

HP Firewalls and UTM Devices

Restrictions for Disabling Flow Cache Entries in NAT and NAT64

Inspection of Router-Generated Traffic

Chapter 6 Global CONFIG Commands

Identity Firewall. About the Identity Firewall

CCNA Course Access Control Lists

Three interface Router without NAT Cisco IOS Firewall Configuration

Configuring Firepower Threat Defense interfaces in Routed mode

Configuring attack detection and prevention 1

Implementing Traffic Filters for IPv6 Security

Table of Contents. 1 Intrusion Detection Statistics 1-1 Overview 1-1 Displaying Intrusion Detection Statistics 1-1

Logging. About Logging. This chapter describes how to log system messages and use them for troubleshooting.

HP High-End Firewalls

Firewall Policy. Edit Firewall Policy/ACL CHAPTER7. Configure a Firewall Before Using the Firewall Policy Feature

Syslog Messages to and to

The IDP system generates logs for device events and security events. Table 1 summarizes options for viewing and managing logs.

Firepower Threat Defense Site-to-site VPNs

Configuring IP Services

Information about Network Security with ACLs

Object Groups for ACLs

Configuring Logging. Information About Logging CHAPTER

Cisco TelePresence Server on Virtual Machine

Enabling ALGs and AICs in Zone-Based Policy Firewalls

CCNA Discovery 3 Chapter 8 Reading Organizer

Configuring Network Address Translation

User FAQ for H3C Security Products

SecBlade Firewall Cards NAT Configuration Examples

Zone-Based Policy Firewall High Availability

Configuring Static and Dynamic NAT Translation

Lab Configure Cisco IOS Firewall CBAC on a Cisco Router

IP Addressing: Fragmentation and Reassembly Configuration Guide, Cisco IOS XE Release 3S (Cisco ASR 1000)

Using ping, tracert, and system debugging

VLAN Access Control Lists

Enabling ALGs and AICs in Zone-Based Policy Firewalls

HP 5820X & 5800 Switch Series Network Management and Monitoring. Configuration Guide. Abstract

OER uses the following default value if this command is not configured or if the no form of this command is entered: timer: 300

Monitoring. Ping CHAPTER

Configuring IPv6 basics

Table of Contents 1 IP Addressing Configuration IP Performance Configuration 2-1

Configuring attack detection and prevention 1

ipro-04n Security Configuration Guide

Flow-Based Redirect. Finding Feature Information

Access Rules. Controlling Network Access

Flow-Based Redirect. Finding Feature Information

Access Control List Enhancements on the Cisco Series Router

Configuring Static and Dynamic NAT Translation

Using Diagnostic Tools

HP A6600 Routers Network Management and Monitoring. Command Reference. Abstract

Extended ACL Configuration Mode Commands

Aruba 8320 Configuring ACLs and Classifier Policies Guide for ArubaOS- CX 10.00

Deploying Cisco ASA Firewall Solutions (FIREWALL v1.0)

VRF Aware Cisco IOS Firewall

H3C S5500-HI Switch Series

HP High-End Firewalls

Transcription:

Table of Contents Log Management 1 Configuring Syslog 1 Configuring User Logging 3 Configuring Flow Logging 3 Session Logging 6 Session Logging Overview 6 Configuring a Session Logging Policy 7 Setting Session Logging Thresholds 8 Log Report 9 Displaying System Logs 9 Displaying Connection Limit Logs 11 Displaying Attack Prevention Logs 12 Displaying Blacklist Logs 12 Displaying Inter-Zone Policy Logs 13 Displaying User Logs 14 i

Log Management The log management feature enables you to store the system messages or logs generated by actions such as packet filtering to the log buffer or send them to the log hosts. The analysis and archiving of the logs can enable you to check the security holes of the firewall, when and who try to disobey security policies, and the types of the network attacks. The real-time logs can also be used to detect the ongoing attacks. NOTE: After receiving an invalid packet, the device directly drops the packet and does not log it. Invalid packets include IP packets with header checksum errors, packets with invalid destination IP addresses, and raw IP packets with the protocol number of 1, 5, 17, or 58. You can execute the debug commands on the command line interface to view the detailed information. Configuring Syslog The syslog module allows you to set the related parameters of the information center. Acting as the system information hub, the information center classifies and manages the system information, offering a powerful support for network administrators and developers in monitoring the network performance and diagnosing network problems. The information center can output the log information to the Web interface for users to view the logs. Meanwhile, it can also output the log information to the specified syslog log host based on your configuration. Select Log Report > Syslog from the navigation tree to enter the page as shown in Figure 1. 1

Figure 1 Syslog Table 1 describes the syslog configuration items. Table 1 Syslog configuration items Log Buffer Size Clear Log Set the number of syslogs that can be stored in the log buffer. To clear the logs in the log buffer, click this button. Log Host IP Address Log Host 1 Log Host 2 Log Host 3 Log Host 4 Set the IPv4/IPv6 addresses, port number and the VPN instance (this option is available only when you specify a log host with an IPv4 address) of the syslog log hosts. The log information can be reported to the specified remote log hosts in the format of syslog, and you can specify up to four syslog log hosts. 2

Set the refresh period on the log information displayed on the log report Web interface. Refresh Period You can select manual refresh or automatic refresh: Manual: You need to refresh the Web interface when displaying log report information. Automatic: You can select to refresh the Web page every 10 seconds, 30 seconds, 1 minute, 5 minutes, or 10 minutes. Configuring User Logging User logs can be output in the following two formats, and you can select either one: Output to the information center of the device in the format of system information, and the information center then decides the output destination. Output to the specified userlog log host in UDP packets in binary format. Configuring Flow Logging NOTE: At present, flow logs refer to session logs only. To generate flow logs, you need to configure session logging. Introduction Flow logging records users access information to the external network. The device classifies and calculates flows through the 5-tuple information, which includes source IP address, destination IP address, source port, destination port, and protocol number, and generates user flow logs. Flow logging records the 5-tuple information of the packets and number of the bytes received and sent. With flow logging, administrators can track and record accesses to the network, facilitating the availability and security of the network. Two versions are available with flow logging: version 1.0 and version 3.0, which are slightly different in packet format. For details, see the following two tables. Table 2 Packet format in flow logging version 1.0 Field SourceIP DestIP SrcPort DestPort Source IP address Destination IP address TCP/UDP source port number TCP/UDP destination port number StartTime Start time of a flow, in seconds, counted from 1970/1/1 0:0 EndTime End time of a flow, in seconds, counted from 1970/1/1 0:0 Prot Operator Protocol carried over IP Indicates the reason why a flow has ended 3

Field Reserved For future applications Table 3 Packet format in flow logging version 3.0 Field Prot Operator IpVersion TosIPv4 SourceIP SrcNatIP DestIP DestNatIP SrcPort SrcNatPort DestPort DestNatPort Protocol carried over IP Indicates the reason why a flow has ended. IP packet version ToS field of the IPv4 packet Source IP address Source IP address after Network Address Translation (NAT) Destination IP address Destination IP address after NAT TCP/UDP source port number TCP/UDP source port number after NAT TCP/UDP destination port number TCP/UDP destination port number after NAT StartTime Start time of a flow, in seconds, counted from 1970/01/01 00:00. EndTime End time of a flow, in seconds, counted from 1970/01/01 00:00. InTotalPkg InTotalByte OutTotalPkg OutTotalByte Reserved1 Reserved2 Reserved3 Number of packets received Number of bytes received Number of packets sent Number of the bytes sent Reserved in version 0x02 (FirewallV200R001); In version 0x03 (FirewallV200R005), the first byte is the source VPN ID, the second byte is the destination VPN ID, and the third and forth bytes are reserved. For future applications For future applications Configuring flow logging Select Log Report > Userlog from the navigation tree to enter the page as shown in Figure 2. 4

Figure 2 Flow logging Table 4 describes the configuration items of flow logging. Table 4 Flow logging configuration items Version Source IP Address of Packets Set the version of flow logging, including 1.0 and 3.0. IMPORTANT: Configure the flow logging version according to the capacity of the log receiving device. If the log receiving device does not support flow logging of a certain version, the device cannot resolve the logs received. Set the source IP address of flow logging packets. After the source IP address is specified, when Device A sends flow logs to Device B, it uses the specified IP address instead of the actual egress address as the source IP address of the packets. In this way, although Device A sends out packets to Device B through different ports, Device B can judge whether the packets are sent from Device A according to their source IP addresses. This function also simplifies the configurations of ACL and security policy: If you specify the same source address as the source or destination address in the rule command in ACL, the IP address variance and the influence of interface status can be masked, thus filtering flow logging packets. You are recommended to use the IP address of the loopback interface as the source IP address of flow logging packets. Log Host Configura tion Log Host 1 Set the IPv4/IPv6 addresses, and port number and the VPN instance (this option is available only when you specify a log host with an IPv4 address) of the Userlog log host to encapsulate flow logs in UDP packets and send them to the specified userlog 5

Log Host 2 log host. The log host can analyze and display the flow logs to remotely monitor the device. You can specify up to two different userlog log hosts. IMPORTANT: To avoid collision with the common UDP port numbers, you are recommended to use a UDP port number in the range from 1025 to 65535. Set to output flow logs to the information center in the format of system information. Output flows logs to information center IMPORTANT: With this function enabled, flow logs will not be output to the specified userlog log host. Outputting flow logs to the information center occupies the storage space of the device. Therefore, you are recommended to output flow logs to the information center in case that there are a small amount of flow logs. Displaying flow logging statistics If you set to send flow logs in UDP packets to the specified userlog log host, you can view the related statistics, including the total number of flow logs sent to the log host, the total number of UDP packets and the total number of flow logs stored on the device cache. If you click the Statistics expansion button on the Flow Log page, you can view the information as shown in Figure 3. You can clear all the flow logging statistics of the device and the flow logs in the cache by clicking Reset. Figure 3 View flow logging statistics Session Logging Session Logging Overview Session logging records users access information, IP address translation information, and traffic information, and can output the records in a specific format to a log host, allowing administrators to perform security auditing. Session logging records an entry for a session if it reaches the specified threshold. Session logging supports two categories of thresholds: 6

Time threshold: When the lifetime of a session reaches this threshold, a log entry is output for the session. Traffic threshold: The traffic threshold can be in units of the number of bytes or the number of packets. When the traffic of a session reaches the specified number of bytes or packets, a log entry is output for the session. With the Output Log Entries for Session Creation and Output Log Entries for Session Deletion options, you can specify whether to output logs when a session is created or deleted. NOTE: For more information about session management, see Session Management. Session logs are output in the format of flow logs. To view session logs, you also need to configure flow logging. Perform the tasks in Table 5 to configure session logging. Table 5 Session logging configuration task list Task Configuring a Session Logging Policy Setting Session Logging Thresholds Remarks Required Configure a session logging policy, specifying the source zone and destination zone of the sessions and the ACL for filtering log entries. By default, no session logging policy exists. Required Configure the time threshold or/and traffic threshold for session logging. By default, both the time threshold and traffic threshold are 0, meaning that no session logging entries should be output. IMPORTANT: If both the time threshold and traffic threshold are configured, a log entry is output for the session when it reaches whichever threshold and the statistics of the session will be cleared. Configuring a Session Logging Policy Select Log Report > Session Log > Log Policy from the navigation tree to display existing session logging policies, as shown in Figure 4. Then, click Add to enter the session logging policy configuration page, as shown in Figure 5. Figure 4 Session logging policy list 7

Figure 5 Create a session logging policy Table 6 describes the configuration items for configuring a session logging policy. Table 6 Configuration items for configuring a session logging policy Source Zone Destination Zone ACL Specify the source zone and destination zone. You can configure an optional security zone through System > Zone. Specify the ACL for filtering log entries, and only log entries permitted by the ACL will be output. The rules of the specified ACL can be configured by selecting Firewall > ACL. Return to Session logging configuration task list. Setting Session Logging Thresholds Select Log Report > Session Log > Global Setup from the navigation tree to enter the page for configuring session log output, as shown in Figure 6. Figure 6 Global configuration page Table 7 describes the configuration items for configuring session log output. 8

Table 7 Configuration items for setting session logging thresholds Time Threshold Traffic Threshold Output Log Entries for Session Creation Output Log Entries for Session Deletion Set the time threshold for outputting session logging entries. With this argument set, log entries will be output for sessions whose lifetimes reach the specified time threshold. Set the traffic threshold for outputting session logging entries. It can be in number of packets or bytes. With the traffic threshold set, log entries will be output for sessions whose traffic reaches the specified threshold in number of bytes or packets. Set whether to output logs when a session is created. Set whether to output logs when a session is deleted. Return to Session logging configuration task list. Log Report The log report module allows you to view the log information on the device, and you can view the following logs through the Web interface: System logs Connection limit logs Attack prevention logs Blacklist logs Inter-zone policy logs User logs Displaying System Logs Select Log Report > Report > System Log from the navigation tree to enter the page as shown in Figure 7. 9

Figure 7 Operation log configuration page Table 8 describes the system log configuration items. Table 8 System log configuration items Time/Date Source Level Displays the time when the system logs are generated. Displays the module that generates the system logs. Displays the severity level of the system logs. For the detailed description of the severity levels, see Table 9. Displays the contents of the system logs. Table 9 System log severity level Severity level Value Emergency The system is unavailable. 0 Alert Information that demands prompt reaction 1 Critical Critical information 2 Error Error information 3 Warning Warnings 4 Notification Information Normal information that needs to be noticed Informational information to be recorded 5 6 10

Severity level Value Debug Information generated during debugging Note: A smaller value represents a higher severity level. 7 Displaying Connection Limit Logs Select Log Report > Report > Connection Limit Log from the navigation tree to enter the page as shown in Figure 8. Figure 8 Connection limit log configuration page Table 10 describes the connection limit log configuration items. Table 10 Connection limit log configuration items Time/Date Type Source Zone Source IP Destination Zone Destination IP Current Rate Current Connection TCP Percentage UDP Percentage ICMP Percentage Displays the time when the connection limit logs are generated. Displays the types of the traffic alarms: The number of source IP-based connections exceeds the upper limit or the number of destination IP-based connections exceeds the upper limit. Displays the source zone of the connection. Displays the source IP address of the connection. Displays the destination zone of the connection. Displays the destination IP address of the connection. Displays the rate of the current connection. Displays total number of the current connections. Displays the percentage of TCP packets to the total packets. Displays the percentage of UDP packets to the total packets. Displays the percentage of ICMP packets to the total packets. 11

Displaying Attack Prevention Logs Select Log Report > Report > Attack Prevention Log from the navigation tree to enter the page as shown in Figure 9. Figure 9 Attack prevention log configuration page Table 11 describes the attack prevention log configuration items. Table 11 Attack prevention log configuration items Time Type Interface Source IP Source MAC Destination IP Destination MAC Speed Displays the time when attacks are detected. Displays the attack type. Displays the interface that receives the attack packets. Displays the source IP address of the attack packets. Displays the source MAC address of the attack packets. Displays the destination IP address of the attack packets. Displays the destination MAC address of the attack packets. Displays the connection speed of the attacks. Displaying Blacklist Logs Select Log Report > Report > Blacklist Log from the navigation tree to enter the page as shown in Figure 10. 12

Figure 10 Blacklist log configuration page Table 12 describes the blacklist log configuration items. Table 12 Blacklist log configuration items Time/Date Mode Source IP Reason Hold Time Displays the time when the blacklist members are generated. Displays whether the blacklist members are newly added or removed. Displays the IP addresses of the blacklist members. Displays the reasons why the addresses are added to the blacklist, including manual add and automatic add: Automatic add means that the system automatically adds the source IP address to the blacklist. Manual add means that the blacklist is manually added through Web interface. Displays the hold time of the blacklist members. Displaying Inter-Zone Policy Logs Inter-zone logs are logs of the flows matching an inter-zone policy. To record inter-zone policy logs, you need to enable the Syslog function when configuring an inter-zone policy. For more information about the detailed configuration, see Inter-Zone Policy Configuration. Select Log Report > Report > InterZone Policy Log from the navigation tree to enter the page as shown in Figure 11. Figure 11 Inter-zone policy log configuration page Table 13 describes the inter-zone policy log configuration items. Table 13 Inter-zone policy log configuration items Start Time Displays the time when the flows are created. 13

End Time Source Zone Destination Zone Policy ID Action Protocol Type Flow Information Displays the time when the flows are removed. Displays the source zone of the flows. Displays the destination zone of the flows. Displays the ID of the inter-zone policy that the flows match. Displays the actions taken against the flows, permitted or denied. Displays the protocol type of the flows. Displays the flow information. If the protocol type is TCP or UDP, the displayed flow information is source IP address:source port-->destination IP address:destination port, for example, 1.1.1.2:1026-->1.1.2.10:69. If the protocol type is ICMP, the displayed flow information is source IP address-->destination IP address,icmp type (ICMP code), for example, 1.1.1.2-->1.1.2.10, echo(8). If the protocol type is another type except these three, the displayed flow information is source IP address-->destination IP address, for example, 1.1.1.2-->1.1.2.10. Displaying User Logs NOTE: To display user logs through the Web interface, you need to configure outputting user logs to the information center. Displaying flow logs Select Log Report > Report > Userlog from the navigation tree to enter the page for displaying flow logs. If you select the 1.0 radio box, the flow logging information will be displayed, as shown in Figure 12; if you select the 3.0 radio box, the flow logging 3.0 information will be displayed, as shown in Figure 13. Figure 12 Flow logging 1.0 log report 14

Figure 13 Flow logging 3.0 log report Table 14 and Table 15 describe the flow logging 1.0 and 3.0 configuration items respectively. Table 14 Flow logging 1.0 configuration items Time/Date Protocol Type Flow Information Start Time End Time Flow Action Displays the time and date when a flow log was generated. Displays the protocol type of a flow log. Displays flow information: If the protocol type is TCP or UDP, the displayed flow information is source IP address:source port-->destination IP address:destination port, for example, 1.1.1.2:1026-->1.1.2.10:69. If the protocol type is another type except TCP or UDP, the displayed flow information is source IP address-->destination IP address, for example, 1.1.1.2-->1.1.2.10. Displays the time when a flow was created. Displays the time when a flow was removed. Displays the operator field of a flow. (1)Normal over: The flow ended normally. (2)Aged for timeout: Timer timed out. (3)Aged for reset or config-change: Flow aging due to configuration change. (4)Aged for no enough resource: Flow aging due to insufficient resource. (5)Aged for no-pat of NAT: One to one NAT. In this case, only the source IP address, the source IP address after translation and the time fields are available. (6)Active data flow timeout: The life time of the flow reached the limit. (8)Data flow created: Record for the flow when it was created. (254)Other: Other reasons 15

Table 15 Flow logging 3.0 configuration items Time/Date Protocol Type Flow Information Received Packets/Bytes Send Packets/Bytes Source VPN Destination VPN Start Time End Time Flow Action Displays the time and date when a flow log was generated. Displays the protocol type of a flow. Displays the flow information. If the protocol type is TCP or UDP, the displayed flow information is source IP address:source port-->destination IP address:destination port, for example, 1.1.1.2:1026-->1.1.2.10:69. If the protocol type is another type except TCP or UDP, the displayed flow information is source IP address-->destination IP address, for example, 1.1.1.2-->1.1.2.10. Displays the number of received packets/bytes. Displays the number of sent packets/bytes. Displays the source VPN of the packets. Displays the destination VPN of the packets. Displays the time when a flow was created. Displays the time when a flow was removed. Displays the operator field of a flow. (1)Normal over: The flow ended normally. (2)Aged for timeout: Timer timed out (3)Aged for reset or config-change: Flow aging due to configuration change (4)Aged for no enough resource: Flow aging due insufficient resource (5)Aged for no-pat of NAT: One to one NAT. In this case, only the source IP address, the source IP address after translation and the time fields are available. (6)Active data flow timeout: The life time of the flow reached the limit. (8)Data flow created: Record for the flow when it was created. (254)Other: Other reasons 16