Abstract:
A system, method and computer program product are provided for processing accounting information. In use, accounting information is received over a network. After receiving the accounting information, at least a portion of the accounting information that occurs during a surge in network traffic is discarded, based on at least one attribute of the accounting information. Further, at least a portion of the accounting information is processed, based on at least one attribute of the accounting information. Still yet, after the processing, at least a portion of remaining accounting information is allowed to pass to subsequent processing. To this end, the portion of the accounting information that is discarded is done so to prevent an overload of the subsequent processing.

Description:
RELATED APPLICATION(S) 
   The present application is a continuation of an application filed Aug. 7, 2001 under Ser. No. 09/924,391, now U.S. Pat. No. 7,099,940 which, in turn, claims the priority of a provisional application filed Aug. 7, 2000 under Ser. No. 60/223,129, which is incorporated herein by reference for all purposes. 

   FIELD OF THE INVENTION 
   The present invention relates to network accounting, and more particularly to processing network accounting information for the purpose of dealing with network attacks and/or other network conditions. 
   BACKGROUND OF THE INVENTION 
   Network accounting involves the collection of various types of information pertaining to the data communications over a network, and sending and receiving information over a network. Examples of such information may include, but is not limited to a communication session&#39;s source, destination, user name, duration, time, date, type of server, volume of data transferred, etc. Armed with such accounting information, various services may be provided that require network usage metering of some sort. 
   Networks are often subject to various attacks wherein a perpetrator attempts to infiltrate a system. During a denial of service (Dos) attack, a network failure is likely to occur as a result of data being transmitted over the network. Accompanying such attacks is a surge in the amount of accounting information that is generated by various devices. Such accounting information is collected and sent to the back-end systems such as Operation and Business Support Systems (OSS/BSS). Overwhelmed by the overload situation, back-end systems may fail leading to the loss of valuable network accounting information and loss of service revenue ultimately. 
   For instance, if a computer attempts an attack, i.e. syn or fin, on a network, it will scan a plurality of ports. There are generally 65,536 ports to scan for a network device, and all this takes place over a very short period of time, typically several seconds. In general, the amount of network traffic generated by these attacks is negligible (as the data associated with attacks is generally of control and management nature that is short and can often be encapsulated in a small data packet), but the amount of accounting data created is large as accounting data is generated for events happening in the network. For instance, it would create 65,536 log entries in a firewall log, or up to 131,072 NetFlow flows, for each host that it attempts to attack. If a ping attack is used, then a plurality of Internet Protocol (IP) addresses is scanned in a similar fashion. 
   By way of background, a port is a “logical connection end-point” that associates a communication channel with entities running on a server or a client. Typical entities may be a program or an application executed on the client or server. A communication channel may be established as TCP connections using the Internet Protocol. Higher-layer applications that use TCP/IP such as the Web protocol, HTTP, have ports with pre-assigned numbers. These are known as “well-known ports” that have been assigned by the Internet Assigned Numbers Authority (IANA). Other application processes are given port numbers dynamically for each connection. When a service (server program) initially is started, it is said to bind to its designated port number. As any client program wants to use that server, it also must request to bind to the designated port number. Port numbers are from 0 to 65535. Ports 0 to 1023 are reserved for use by certain privileged services. For the HTTP service, port 80 is defined as a default and it does not have to be specified in the Uniform Resource Locator (URL). 
   A port scan is a series of messages sent by someone attempting to break into a computer to learn which computer network services, each associated with a “well-known” port number, the computer provides. Port scanning, a favorite approach of computer hackers, gives the assailant an idea where to probe for network weaknesses. Essentially, a port scan consists of sending a message to each port, one at a time. The kind of response received indicates whether the port is used and can therefore be probed for weakness. 
   Exemplary Types of Port Scans Include: 
   
       
       
         
           Vanilla—An attempt to connect to all ports (there are 65,536) 
           Strobe—An attempt to connect to only selected ports (typically, under 20) 
           Stealth scan—Several techniques for scanning that attempt to prevent the request for connection being logged 
           FTP Bounce Scan—Attempts that are directed through an FTP server to disguise the cracker&#39;s location 
           Fragmented Packets—Scans by sending packet fragments that can get through simple packet filters in a firewall 
           UDP—Scans for open UDP ports 
           Sweep—Scans the same port on a number of computers 
         
       
     
  
   Unwanted accounting information surges can also occur as a result of situations other than network attacks. For example, information may be collected from unreliable sources. Further, a storage capacity of a system may be inadequate. In still other situations, some information may be deemed pertinent, while other data may be deemed expendable. 
   There is therefore a need for a technique of identifying attacks and/or other network conditions; and more importantly, preventing the propagation of large amounts of accounting information to back-end systems which may in turn result in undesired failure in the network accounting process. 
   SUMMARY 
   A system, method and computer program product are provided for processing accounting information. In use, accounting information is received over a network. After receiving the accounting information, at least a portion of the accounting information that occurs during a surge in network traffic is discarded, based on at least one attribute of the accounting information. Further, at least a portion of the accounting information is processed, based on at least one attribute of the accounting information. Still yet, after the processing, at least a portion of remaining accounting information is allowed to pass to subsequent processing. To this end, the portion of the accounting information that is discarded is done so to prevent an overload of the subsequent processing. 

   
     BRIEF DESCRIPTION OF THE DRAWINGS 
       FIG. 1  illustrates an exemplary network on which one embodiment of the present invention may be implemented; 
       FIG. 2  shows a representative hardware environment associated with the host, devices, etc. shown in the network diagram of  FIG. 1 ; 
       FIG. 3  is a schematic diagram illustrating the various components used for processing network accounting information in accordance with one embodiment of the present invention; 
       FIG. 4  is a flowchart showing one method of processing network accounting information; 
       FIG. 5  illustrates a data structure that may be used while processing network accounting information in accordance with the method of  FIG. 4 ; and 
       FIG. 6  is a flowchart showing a generalized method of processing network accounting information for the purpose of defending against network attacks and dealing with heavy network traffic. 
   

   DETAILED DESCRIPTION 
     FIG. 1  illustrates an exemplary network framework  100  on which one embodiment of the present invention may be implemented. As shown, various network components may be provided including a router  102  for routing information between various portions of the network. In one embodiment, such network may include the Internet using a communication protocol such as TCP/IP. It should be noted, however, that the network may include any type of network including, but not limited to a wide area network (WAN), local area network (LAN), and metropolitan area network (MAN) etc. 
   Further provided is a host  104  coupled to the router  102  for sending information thereto and receiving information therefrom. A firewall  106  may also be coupled to the router  102  for controlling access to a plurality of interconnected devices  108 . While various network components have been disclosed, it should be understood that the present invention may be implemented in the context of any type of network architecture and in any type of network device such as proxy servers, mail servers, hubs, directory servers, application servers, etc. 
     FIG. 2  shows a representative hardware environment associated with the various devices, i.e. host, device, etc. shown in the network diagram of  FIG. 1 . Such figure illustrates a typical hardware configuration of a workstation in accordance with a preferred embodiment having one or more central processing unit  210 , such as microprocessors, and a number of other units interconnected via a system bus  212 . The workstation shown in  FIG. 2  includes a Random Access Memory (RAM)  214 , Read Only Memory (ROM)  216 , an I/O adapter  218  for connecting peripheral devices such as disk storage units  220  to the bus  212 , a user interface adapter  222  for connecting a keyboard  224 , a mouse  226 , a speaker  228 , a microphone  232 , and/or other user interface devices such as a touch screen (not shown) to the bus  212 , communication adapter  234  for connecting the workstation to a communication network  235  (e.g., a data processing network) and a display adapter  236  for connecting the bus  212  to a display device  238 . It should be noted the foregoing architecture is set forth for illustrative purposes only. Other application specific integrated circuit (ASIC) architectures may also be used as well as any other desired frameworks, per the desires of the user. 
   The workstation may have resident thereon an operating system such as the Microsoft Windows NT or Windows/95 Operating System (OS), the IBM OS/2 operating system, the MAC OS, or UNIX operating system. It will be appreciated that a preferred embodiment may also be implemented on platforms and operating systems other than those mentioned. A preferred embodiment may be written using JAVA, C, and/or C++ language, or other programming languages, along with an object oriented programming methodology. Object oriented programming (OOP) has become increasingly used to develop complex applications. 
   During use of the various components shown in  FIGS. 1 and 2 , accounting information relating to network traffic and sessions is collected and tracked by the various hosts  104  and devices  108  at an accounting ingress point  110 . Examples of such information may include, but are not limited to a session&#39;s source, destination, user name, duration, time, date, type of server, volume of data transferred, etc. Armed with such accounting information, various services and business applications, i.e. billing, security, etc. may be provided that require network usage metering of some sort. 
     FIG. 3  is a schematic diagram illustrating the various exemplary components used for processing network accounting information at a network component such as those disclosed during reference to  FIG. 1 . As shown, an analysis module  300  is included for receiving accounting information, or data, for analyzing the same. Such analysis may include the identification of trends relating to various attributes associated with the received accounting information. Examples of such attributes include source address, destination address, end point port number or equivalent, protocol type, user identification, number of input IP packets, number of IP packets in a session or flow, time of the reception of an IP packet, etc. Additional information relating to the manner in which such functionality is accomplished will be set forth in greater detail during reference to  FIGS. 4 and 5 . 
   With continuing reference to  FIG. 3 , an update module  302  is coupled to the analysis module  300  for maintaining aggregations that are established after a trend is detected. The aggregations are a plurality of records with common attributes. In particular, an aggregation may refer to a plurality of records with the identical subset of attributes (representing some aspect of the record). Both the update module  302  and the analysis module  300  feed an accounting module  304  for monitoring the network accounting information. Also coupled to the update module  302  and the analysis module  300  is an alarm module  306  for providing alerts upon certain criteria being met. Additional information relating to the manner in which such functionality is accomplished will be set forth in greater detail during reference to  FIGS. 4 and 5 . 
   It should be noted that the foregoing architecture is set forth for illustrative purposes only, and should not be construed as limiting in any manner. In particular, the functionality set forth hereinafter may be implemented in the context of any desired feasible framework. 
     FIG. 4  is a flowchart showing one method  400  of processing network accounting information in accordance with one embodiment of the present invention. Initially, in operation  402 , accounting information, or data, is received by the analysis module  300 . Thereafter, in operation  404 , a real-time comparison is performed on each packet or aspects of accounting information. Such comparison involves various attributes and statistics of the received accounting information, and various aggregations of accounting information that were previously identified. 
   Based on the foregoing comparison, it is determined in decision  406  whether the accounting information is associated with a currently existing aggregation. For example, one current aggregation may include a plurality of packets of accounting information which indicate that a plurality of successive ports and/or Internet Protocol (IP) addresses have been scanned. If a packet that is just received indicates a scan of a next successive port and/or IP address within a short amount of time (i.e., a threshold of x sec(s).), it is determined that such accounting information is associated with such aggregation. As yet another example, one aggregation may include a plurality of packets received at a rate which exceeds a predetermined amount. 
   If it is determined in decision  406  that the accounting information is not associated with a current aggregation, trend information is nevertheless maintained, as indicated in operation  408 . The purpose of this is to evaluate whether additional aggregations are warranted. As shown in  FIG. 4 , it is decided in decision  412  whether the trend warrants the establishment of another aggregation. Decision  412  may be made by applying a set of rules to the trend information. For example, if a predetermined number of successive ports are scanned within a short amount of time, one of the rules may dictate that an additional aggregation is warranted. It should be noted that decisions on whether to establish a new aggregation may be based on statistical analysis, neural network and pattern recognition techniques. 
   Further, various levels of certainty or confidence level may be established into which the trend is to be fit. In such embodiment, the decision  412  as to whether a trend warrants an additional aggregation may depend on the level of certainty associated with the trend. This may optionally be implemented using statistical analysis, and fuzzy logic, etc. 
   If it is determined in decision  412  that a new aggregation is warranted, the trend information is used to generate the additional aggregation. See operation  414 . If, however, it is determined in decision  412  that a new aggregation is not warranted, the received accounting data is used by the accounting module  304  for accounting purposes, as indicated in operation  415 . 
   In order to generate the additional aggregation in operation  414 , the packets or records of accounting information which exhibit the trend are represented using a data structure in the form of a table.  FIG. 5  illustrates a data structure  500  that may be used while processing network accounting information in accordance with operation  414  of  FIG. 4 . As shown, aspects of the accounting information are stored including an identifier  502 , a key  504 , and an attribute metric  506 . The identifier  502  uniquely identifies a packet or a record of accounting information that exhibit one trend; the key  504  represents one aspect or attribute of the packet or record that can be defined for trend analysis; the attribute metric  506  may be a array containing all the relevant attributes of the packet or record for trend analysis. It should be noted that the data structure  500  may also be employed while maintaining trend information in operation  408 . 
   When trend information is used to generate an aggregation in operation  414 , some of the accounting information in the data structure  500  associated with the trend may already be used earlier in operation  415 . Accordingly, there may optionally be a mechanism for preventing redundant use of such accounting information. 
   If it is determined in decision  406  that the accounting information is indeed associated with a current aggregation, various commands may be generated by the update module  302  for starting, stopping, and updating aggregations in the accounting module  304 . Note operation  416 . The start command signifies that an aggregation has started, as indicated by an associated trend. Further, the stop command indicates that an aggregation has ceased. 
   As additional accounting information is received, the update command may be sent to the accounting module  304  in order to update a current aggregation. In the context of the example set forth hereinabove, the aggregation may be updated to include the additional scan of the successive port and/or Internet Protocol (IP) address. 
   Upon an aggregation being started, stopped, updated by the receipt of the start, stop, and update command by the accounting module  304 , respectively, alarms may be generated by the alarm module  306 . Note operation  418 . It should be noted that these alarms may be issued in response to any one or more of the various commands for the purpose alarming the service providers or operators of network under attach and/or other network conditions. 
   Further, in operation  420 , information may be discarded and/or aggregated in order to prevent the accounting information from causing an overload condition. This prevents the failure of back-end systems. In order to prevent total loss of accounting information that is generated, a summary may be generated by the accounting module  304  at various stages, or states, of the aggregation. For instance, upon the receipt of the stop command, a summary record may be generated. Table 1 illustrates an exemplary summary record of accounting information. 
   
     
       
             
             
           
         
             
                 
               TABLE 1 
             
             
                 
                 
             
           
           
             
                 
               A &lt;type of attack&gt; attack from &lt;host&gt; started at 
             
             
                 
               &lt;start&gt; lasted &lt;duration&gt; seconds and scanned 
             
             
                 
               through &lt;IP range&gt; and &lt;Port range&gt;. 
             
             
                 
                 
             
           
        
       
     
   
   The summary record of Table 1 may thus consolidate hundreds of thousands of NetFlow flows or records from a log into a single record. This summarized record may then be used by the accounting module  304  for accounting purposes, as indicated in operation  424 . By handling the accounting of the summarized record instead of the raw data as in operation  415 , the mediation/billing process is capable of preventing overflow in back-end accounting systems. 
     FIG. 6  is a flowchart showing a generalized method  600  in which the method  400  of  FIG. 4  processes network accounting information for the purpose of defending against network attacks and dealing with heavy network traffic. With reference to  FIG. 6 , accounting information is first received utilizing a network in operation  602 . During use, at least one aspect of the received accounting information is monitored. Note operation  604 . It should be noted that such aspects may be monitored by an internal or external tool/mechanism. In other words, the various operations may be carried out by different tools or mechanisms. In the case of using an external tool/mechanism, an indication of a particular aspect of the received accounting information may be received for identification purposes. 
   Thereafter, appropriate actions may be invoked to present possible overloading of accounting system and back-end systems. For example, at least a portion of the accounting information is discarded and/or aggregated based on the monitored or identified aspect, as indicated in operation  606 . 
   In one embodiment, the monitoring step may include detecting a scan of a plurality of ports and/or Internet Protocol (IP) addresses. Further, such step may include monitoring a rate of receipt of the accounting information. More particularly, such step may include detecting whether a rate of receipt of the accounting information exceeds a predetermined amount. In other words, the foregoing aspect of the accounting information may be any parameter, attribute, characteristic, etc. that indicates an attack and/or a potential overload of an accounting system. 
   While various embodiments have been described above, it should be understood that they have been presented by way of example only, and not limitation. Thus, the breadth and scope of a preferred embodiment should not be limited by any of the above-described exemplary embodiments, but should be defined only in accordance with the following claims and their equivalents.