US 7,181,769 B1Grant
Network security system having a device profiler communicatively coupled to a traffic monitor
Issue Date:2007-02-20
•18 Claims
•10 Drawing Sheets
Abstract
A system and method for providing distributed security of a network. Several device profilers are placed at different locations of a network to assess vulnerabilities from different perspectives. The device profiler identifies the hosts on the network, and characteristics such as operating system and applications running on the hosts. The device profiler traverses a vulnerability tree having nodes representative of characteristics of the hosts, each node having an associated set of potential vulnerabilities. Verification rules can verify the potential vulnerabilities. A centralized correlation server, at a centrally accessible location in the network, stores the determined vulnerabilities of the network and associates the determined vulnerabilities with attach signatures. Traffic monitors access the attack signatures and monitor network traffic for attacks against the determined vulnerabilities.
Metadata
Assignee
- nCircle Network Security, Inc.
Inventors
- Timothy D. Keanini
- Martin A. Quiroga
- Brian W. Buchanan
- John S. Flowers
Application Information
Application Number:US 10/456,837
Filing Date:2003-06-06
Priority Date:2000-08-25
Art Unit:2131
Classifications
IPC:
G06F12/14H04L9/00
Patent Drawings (10 sheets)
Description
Cross-Reference to Related Applications
[0001] This application claims the benefit of U.S. Provisional Application No. 60/388,078, filed on Jun. 11, 2002, which is incorporated herein by reference; and is a continuation-in-part of U.S. patent application Ser. No. 09/757,963 filed on Jan. 10, 2001 now U.S. Pat. No. 6,957,348, Ser. No. 09/757,872 filed on Jan. 10, 2001 and Ser. No. 09/648,211 filed on Aug. 25, 2000 now U.S. Pat. No. 7,073,198, which are also incorporated herein by reference.
Background of the Invention
[0002] 1. Field of the Invention
[0003] This invention pertains in general to a computer network security system and, more specifically, to profiling a network for vulnerabilities and monitoring exploitations of those vulnerabilities.
[0004] 2. Background Art
[0005] Computer networks are vulnerable to many threats that can inflict damage resulting in significant losses. These threats can stem from a number of sources including malicious acts, environmental hazards, hardware and software failure, and user error. A goal of network security is to protect the confidentiality, integrity, and availability of information stored electronically in a network from these threatening sources.
[0006] Several conventional resources are available to protect a network from information losses. Firewalls are used to enforce a boundary between two or more networks by filtering network traffic passing through the firewall according to a security policy. Vulnerability detection tools perform examinations of a network to determine weaknesses that might allow attacks. Also, separate intrusion detection tools monitor a network for malicious traffic.
[0007] One problem with conventional resources is that firewalls are inadequate to fully protect a network since they traditionally only provide protection against malicious traffic passing through the firewall. The network may still be vulnerable through entry points that do not pass through the firewall.
[0008] Furthermore, vulnerability detection tools and intrusion detection tools are inherently complicated to configure and typically lack interoperability. Consequentially, security engineers need to know what types of attack signatures to look for, how to look for them, and how to respond to a detected attack. Vulnerability detection tools inaccurately assess system vulnerabilities due to limited information about the system. Likewise, intrusion detection tools generate many false positives and operate inefficiently by failing to leverage off of the limited information gathered by the vulnerability detection tools.
[0009] Therefore, there is a need for network protection that does not suffer from these problems. Preferably, the solution to this need will include vulnerability detection aspects to non-invasively detect vulnerabilities and allow the intrusion detection aspects to leverage off of the vulnerability assessment aspects.
Summary of Invention
[0010] The present invention meets these needs by identifying, monitoring, and updating verified vulnerabilities in a network before a malicious attack on the vulnerabilities.
[0011] The system of the present invention includes a device profiler, a centralized correlation server, and at least one traffic monitor communicatively coupled through a network. The device profiler determines vulnerabilities of hosts on the network and transmits the vulnerabilities to the centralized correlation server. The centralized correlation server gathers the resulting vulnerabilities and sends attack signatures for exploits of the vulnerabilities to the traffic monitor. The traffic monitor monitors network traffic to detect traffic matching the attack signatures. The system periodically rescans the network in order to ensure that the traffic monitor is monitoring for only current vulnerabilities. Thus, the present invention enables effective monitoring and reduces false positives by monitoring for only exploits of vulnerabilities known to currently exist on the network.
[0012] The device profiler includes a control module communicating with an identification subsystem for identifying characteristics of a host such as applications and/or operating systems running on the host. A high-level sensor examines OSI (Open Systems Interconnection) layer 5, layer 6 and/or layer 7 aspects of the host to determine running applications and other characteristics of the host. A low-level sensor examines responses to anomalous data packets sent to the host to determine an operating system and other characteristics of the host. In one embodiment, the low-level sensor examines OSI layer 3 and 4 aspects of the host.
[0013] To determine potential vulnerabilities, the control module traverses at least one vulnerability tree having nodes representative of the characteristics of the host, wherein each node has an associated set of potential vulnerabilities. The control module determines a set of potential vulnerabilities by summing the vulnerabilities at each traversed node. The control module determines whether the vulnerabilities actually exist on the host and sends a list of the verified vulnerabilities to the centralized correlation server.
[0014] The centralized correlation server, preferably coupled to the network at a centrally accessible location, includes a network profiling module that stores rules for identifying host characteristics and distributes the rules to the device profiler. Additionally, the network profiling module stores the resulting determined vulnerabilities.
[0015] The centralized correlation server also includes a network monitoring module that associates the determined vulnerabilities with attack signatures. The network monitoring module is further adapted to send the attack signatures to the traffic monitor according to a monitoring location. In one embodiment, the centralized correlation server receives determined vulnerabilities from a plurality of device profilers and sends attack signatures to a plurality of traffic monitors distributed to locations around the network.
[0016] An event daemon module in the centralized correlation server performs actions to block malicious activity in response to detecting potential vulnerabilities or an attack thereon. For example, the event daemon module configures the firewall to prevent or block an attack.
[0017] A traffic monitor monitors network traffic for attack signatures corresponding to the determined vulnerabilities to detect malicious activity. In one embodiment, the traffic monitor associates attack signatures with the specific destination (e.g., IP address and/or port) having the corresponding vulnerability. The traffic monitor does not signal an attack unless the attack matches the attack signature of an exploit of a vulnerability and is directed to a destination known to have the vulnerability.
Brief Description of the Drawings
[0018] FIG. 1 is a high-level block diagram illustrating a system 100 according to an embodiment of the present invention.
[0019] FIG. 2 is a block diagram illustrating a more detailed view of the exemplary LAN 110 of FIG. 1 .
[0020] FIG. 3 is a block diagram illustrating a device profiler 165 according to an embodiment of the present invention.
[0021] FIG. 4 is a block diagram illustrating an example of a vulnerability tree 400 according to an embodiment of the present invention.
[0022] FIG. 5 is a block diagram illustrating a node 500 in the vulnerability tree 400 according to an embodiment of the present invention.
[0023] FIG. 6 is a block diagram illustrating a centralized correlation server 175 according to an embodiment of the present invention.
[0024] FIG. 7 is a block diagram illustrating a more detailed view of the network profiling module 620 of FIG. 6 .
[0025] FIG. 8 is a block diagram illustrating a more detailed view of the network monitoring module of FIG. 6 .
[0026] FIG. 9 is a flow chart illustrating a traffic monitor 185 according to an embodiment of the present invention.
[0027] FIG. 10 is a flow chart illustrating a method of profiling a host 191 to detect potential vulnerabilities as performed by the device profiler 165 according to an embodiment of the present invention.
[0028] FIG. 11 is a flow chart illustrating a method of providing network security to a distributed network as performed by the centralized correlation server 175 according to an embodiment of the present invention.
[0029] FIG. 12 is a flow chart illustrating a method of performing a set of actions to block exposure to a vulnerability by the event daemon module 820.
[0030] FIG. 13 is a flow chart illustrating a method of monitoring a distributed network as performed by the traffic monitor 185 according to an embodiment of the present invention.
[0031] The figures depict an embodiment of the present invention for purposes of illustration only. One skilled in the art will readily recognize from the following description that alternative embodiments of the structures and methods illustrated herein may be employed without departing from the principles of the invention described herein.
Detailed Description of the Preferred Embodiments
[0032] FIG. 1 is a high-level block diagram illustrating a system 100 according to an embodiment of the present invention. The system 100 comprises a WAN (wide area network) 130, such as the Internet, in communication with an enterprise network 115. The WAN 130 facilitates data transfers between geographically dispersed network hosts, such as computers. The connections to the WAN 130 may be wired and/or wireless, packet and/or circuit switched, and use network protocols such as IEEE 802.11, Ethernet, Asynchronous Transfer Mode, or the like. In a packet-based network, a communications protocol, such as TCP/IP (Transmission Control Protocol/Internet Protocol), encapsulates data into packets having headers. A packet's header contains information relating to routing, error-correction and packet identification, among other things. One of ordinary skill in the art will recognize numerous variations of networking encompassed within the present invention that are not specifically disclosed herein.
[0033] The enterprise network 115 includes a LAN 110 (Local Access Network) with hosts 191a,b and a DMZ 120 (DeMilitarized Zone). In this embodiment, device profilers 165a–c are coupled to the WAN 130, the LAN 110, and the DMZ 120, and a traffic monitor 185a is coupled to the router 140.
[0034] The LAN 110 allows hosts 191a,b to communicate with each other and with other hosts on the DMZ 120 and WAN 130 through a firewall 150 and a router 140. The LAN 110 may be implemented as an independent network, or as a subset of a larger network such as the WAN 130. Further embodiments of the LAN 110 are discussed below.
[0035] The hosts 191a,b serve as pass through points or endstations for data packets on the WAN 130, LAN 110, or another network. The hosts 191a,b (and other hosts described below) may be a computer, computer peripheral, telephone, or other device able to connect to a network. The hosts have characteristics such as a network address, open ports, and software executing on the host including an operating system and applications. The hosts 191a,b run the operating system and the operating system runs applications, both of which may be of a certain version and patch level. Likewise, both the operating system and the applications are vulnerable to malicious activity. The hosts 191a,b typically have a hard drive or other data storage module holding information or other resources that can be compromised by malicious activity.
[0036] Applications executing on the hosts 191a,b may include software programs, firmware code, and the like. Some applications performing network services run on open ports of the host 191a,b. A port is a logical communication path that allows applications on the network to communicate. Individual ports on the hosts 191a,b are identified by a number. Certain applications typically run on certain port numbers. For example, an HTTP (HyperText Transport Protocol) server application typically runs on port 80 of the hosts 191a,b.
[0037] The DMZ 120 allows a host 191c to communicate with the hosts 191a,b on the LAN 110 and other hosts 191 on the WAN 130 through the router 140. However, communications with the WAN 130 occur without passing through the firewall 150, which means that hosts on the DMZ can provide services utilizing network traffic that would be blocked by the firewall 150, but are also more susceptible to malicious traffic. The host 191c interacts with the WAN 180 by running applications responsive to requests from WAN hosts 191 such as HTTP, FTP (File Transfer Protocol), DNS (Domain Name System) and/or email servers. Additionally, the host 191c interacts with the LAN 110 by serving as a proxy for network interactions for LAN hosts 191a,b with the WAN 130. As will be recognized by one of ordinary skill in the art, alternative network configurations of the DMZ 120 such as a DMZ 120 placed between the LAN 110 and the firewall 150, and a DMZ 120 placed between the router 140 and the firewall 150, are also encompassed within the present invention.
[0038] The router 140 determines network routing paths for data packets traveling between devices connected to the WAN 130 and the enterprise network 115 based on tables of available routes and their conditions. Specifically, the router 140 forwards incoming data packets to addresses on the LAN 110 and the DMZ 120 and forwards outgoing data packets to addresses in the WAN 130. The router 140 may be a conventional network router implemented in hardware or software as an independent module, or in combination with other modules such as the firewall 150 or a switch.
[0039] The firewall 150 restricts certain network traffic according to a configured firewall policy to prevent or block malicious attacks on the enterprise network 115 in response to detecting a vulnerability or an attack thereon. Thus, hosts 191a,b behind the firewall 150 may not be accessible from the WAN 130. Under a very restrictive policy, the firewall 150 may effectively isolate the LAN 110 from the WAN 130 by blocking all incoming and outgoing network traffic. Under a less restrictive policy, the firewall 150 may allow outgoing network traffic and corresponding responses from the WAN 130. In network configurations with the DMZ 120 located behind the firewall 150 with respect to the WAN 130, the policy may allow incoming requests to pass through certain ports, for example, port 80 for HTTP requests. The firewall 150 may be a conventional firewall implemented in hardware or software, as an independent module, or in combination with other modules, for example, the router 140 or a host 191.
[0040] The device profilers 165a–c collect data about the enterprise network 115 for vulnerability analyses. Preferably, the multiple device profilers 165 are distributed around the enterprise network 115 at locations that offer different perspectives of vulnerabilities. In the illustrated embodiment, the device profilers 165a–c are connected to the WAN 130, the LAN 110 and the DMZ 120 in order to generate a more accurate portrait of network vulnerabilities in comparison to a single point of data collection. Further embodiments of the device profilers 165a–c are discussed below.
[0041] A centralized correlation server 175, preferably located in the DMZ 120, maintains centralized control of network security for the enterprise network 115. For example, the centralized correlation server 175 maintains a centralized database of potential vulnerabilities, maintains a centralized database of actual vulnerabilities identified by the device profilers 165a–c, and communicates with both device profilers 165 and traffic monitors 185. Thus, the centralized correlation server 175 is preferably located in the DMZ 130 or at another point in the system 100 where it can communicate with each device profiler 165 and traffic monitor 185. In other embodiments, the centralized correlation server 175 is located in the router 140 or the WAN 130. Further embodiments of the centralized correlation server 175 are discussed below.
[0042] The traffic monitor 185a examines network traffic for exploitations of vulnerabilities of the enterprise network 115. One or more traffic monitors 185 are deployed in the system 100, preferably at locations where they can monitor most or all of the network traffic. By communicating with the network security centralized correlation server 175, the traffic monitor 185a accesses vulnerability information particular to its location such as associated attack signatures from the centralized correlation server 175. When an attack is identified, the traffic monitor 185a notifies the centralized correlation server 175, which contains a set of actions to perform in response to the attack. In one embodiment, the traffic monitor 185b is coupled to the WAN 130 side of the router 140. In another embodiment, the traffic monitor 185b is coupled to the LAN 110 side of the router 140. Further embodiments of the traffic monitor 185 are discussed below.
[0043] FIG. 2 is a block diagram illustrating a more detailed view of the exemplary LAN 110 of FIG. 1 . The LAN 110 includes a device profiler 165d, a traffic monitor 185b, a subnet 1 117a, a subnet 2 117b, and a subnet 3 117c, each of which is coupled to a switch 142a.
[0044] The switch 142a may be a conventional switch for sending network traffic received from the router 140 to the appropriate subnet 117, and network traffic received from the subnets 117a–c to a different subnet 117 or to the router 142a.
[0045] The device profiler 165d is placed at a location that allows it to determine vulnerabilities of the LAN 110 from inside the firewall 150. Because the firewall 150 limits access to hosts 191 inside its purview, the ability to recognize these hosts 191 and their characteristics depends on from which side of the firewall 150 the assessment is made. From its location, the device profiler 165d communicates with the subnets 117a–c without being affected by the access policies of the firewall 150. Thus, the device profiler 165d inside the firewall 150 can identify vulnerabilities that may not be apparent to device profilers 165 located outside of the firewall 150.
[0046] The traffic monitor 185b is also placed at a location between the firewall 150 and the switch 142a that allows it to examine network traffic for exploitations of vulnerabilities of the LAN 110. In the illustrated embodiment, the traffic monitor 185b is coupled to the span port of the switch 142a so that it can examine all data packets traveling between the LAN 110 and the WAN 130. In another embodiment permitting examination of the same traffic, the traffic monitor 185b is coupled to a port on the router 140 coupled to the LAN 110. In yet another embodiment, the traffic monitor 185b is coupled to ports on the switch 142a that are coupled to the subnets 117a–c.
[0047] In the illustrated embodiment, subnet 1 117a includes a single host 191a. In contrast, subnet 2 117b includes a device profiler 165e and multiple hosts 191b–d coupled to a switch 142a. The device profiler 165e within subnet 2 117b is positioned to detect vulnerabilities on hosts 191b–d within the subnet 117.
[0048] Subnet 3 117c includes a device profiler 165f, a traffic monitor 185c, and two hosts networked via a direct connection. The first host 191e is coupled to the switch 142a and the second host 191f is coupled to the first host 191e. The device profiler 165f is placed at a location that allows it to determine vulnerabilities of the host 191f from a location between the hosts 191e, f unaffected by any policies other than the host 191f itself. The traffic monitor 185c is placed at a location that allows it to monitor network traffic from a location between the hosts 191e, f.
[0049] FIG. 3 is a block diagram illustrating a device profiler 165 according to an embodiment of the present invention. The device profiler 165 preferably comprises an I/O module 310, a control module 320, and an identification subsystem 330. The I/O module 310 allows the device profiler 165a to communicate with other devices on the network such as hosts 191, the centralized correlation server 175, and traffic monitors 185. In another embodiment, the I/O module 310 generates data packets to send to hosts 191 according to instructions from the control module 320 and/or identification subsystem 330. Depending on the embodiment, the I/O module 310 may be a network interface card or other hardware, a software module, or a combination of both.
[0050] The control module 320 manages the vulnerability identification process and controls the general operation of the device profiler 165. In operation, the control module 320 identifies hosts 191 on the network and characteristics of the hosts 191 and use the characteristics to determine the host's vulnerabilities. In one embodiment, the control module 320 uses ping requests to identify hosts on the network and TCP connection attempts to identify open ports of the hosts. Based on this information, the control module 320 sends messages to the identification subsystem 330 instructing it to carry out various analyses to identify and verify vulnerabilities of hosts 191 on the network. Ultimately, the control module 320 generates and sends a list of these vulnerabilities to the centralized correlation server 175.
[0051] The identification subsystem 330 detects vulnerabilities in hosts 191 on the network using identification and verification processes. The identification subsystem 330 includes a low-level sensor 345, an high-level sensor 355, and a rules database module 365. Other embodiments have different and/or additional modules for detecting vulnerabilities than the ones described herein.
[0052] The high-level sensor 355 identifies applications and other characteristics of the hosts 191 by analyzing how the hosts 191 interact at the higher layers of the OSI (Open System Interconnection) stack. For example, telnet applications typically run on port 23. Responsive to port 23 being open, the high-level sensor 355 attempts to open a telnet session on the port and sends a command line instruction to which the telnet application identifies itself by name, version and/or patch level. One embodiment of the high-level sensor 355 analyzes layer 5, layer 6 and layer 7 OSI stack interactions. These layers respectively correspond to the session layer, the presentation layer, and the application layer.
[0053] The low-level sensor 345 identifies operating systems running on hosts 191 and/or other characteristics by sending anomalous data packets to the hosts and analyzing the lower level OSI stack characteristics of packets received in response. In one embodiment, the low-level sensor analyzes the layer 3 and 4 characteristics. Layer 3 corresponds to the network layer and layer 4 corresponds to the transport layer of the OSI stack. The low-level sensor 345 generates and sends data packets based on a set of rules. The rules and packets are designed to generate a response from a host 191 that provides information about the operating system or other characteristics of the host 191.
[0054] In one embodiment, the data packets are anomalous data packets relative to normal data packets that conform to standards. For example, normal packets may adhere to RFC (Request For Comment) protocols promulgated by the Internet Engineering Task Force. The host 191 typically responds to normal data packets with normal responses. By contrast, the host 191 may have unique responses to anomalous data packets deviating from the RFC standard. The response can be compared to operating system fingerprints, or templates of known responses, to identify the operating system, version and/or patch level. In one embodiment, the low-level sensor 345 follows-up one or a set of data packets with another or another set of data packets based on responses to the preceding data packets. Several illustrative responses to probes are set forth in U.S. patent application Ser. No. 09/648,211.
[0055] The rules database module 365 holds rules utilized by the control module 320, the low-level sensor 345, and the high-level sensor 355 to identify characteristics of the hosts 191. These rules include control logic for operating the high-355 and low-level 345 sensors to determine the host's characteristics. In one embodiment, the rules database module 365 also stores potential vulnerabilities of hosts in one or more tree-like data structures, referred to as “vulnerability trees” 400 (e.g., an application vulnerability tree and an operating system vulnerability tree). The control module 320 is adapted to fire rules in the rules database module 365 that use the high-355 and/or low-level sensors 345 to determine the host's characteristics and use these characteristics to traverse the vulnerability tree 400 and identify potential vulnerabilities at each host 191. In one embodiment, the rules database module 365 also stores rules to verify the potential vulnerabilities. The rules database module 365 is preferably configured to receive occasional rule updates from the centralized correlation server 175.
[0056] FIG. 4 is a block diagram illustrating an example of a vulnerability tree 400 according to an embodiment of the present invention. In general, a vulnerability tree 400 has multiple nodes arranged in a tree structure, such that there is a root node and multiple child nodes. Intermediate nodes in the tree have a parent node and a descendant node, and can also have one or more peer nodes at an equal depth from the root node. Each node represents a characteristic of the host, and the nodes are arranged so that each child node represents a more specific identification of the characteristic than the node's parent. In addition, each node also identifies a set of vulnerabilities that a host having the characteristic represented by the node might possess. To determine potential vulnerabilities of a host, the control module 320 traverses the nodes of the vulnerability tree and identifies the lowest level (i.e., farthest descendant from the root) node corresponding to the characteristics of the host. The potential vulnerabilities of the host are the sum of the vulnerabilities of the lowest node and its parent nodes. The rules database module 365 may hold multiple vulnerability trees applicable to the hosts 191 on the network 115. In one embodiment, there is a vulnerability tree for potential applications running on a host and another vulnerability tree for potential operating systems running on the host. Other embodiments can have other types of vulnerability trees and/or other arrangements of vulnerability data.
[0057] The illustrated vulnerability tree 400 stores vulnerabilities associated with particular applications executing on a host 191. Each node is associated with an application, application version and/or patch version and has an associated list of zero or more vulnerabilities that might be possessed by the host 191 executing the application. A child node (e.g., node 424 is child node of node 414) represents a more specific identification of the application, such as a specific type, version and/or patch level and has a list of zero or more vulnerabilities unique to that node. As such, the total list of vulnerabilities that a given application may possess is determined by identifying the applicable lowest-level child node and summing that node's vulnerability list with the vulnerability lists of any parent nodes.
[0058] The exemplary vulnerability tree of FIG. 4 has four levels and is used to identify vulnerabilities associated with the application running on an open port of the host 191. The top level is an application type level 410 and has separate nodes for FTP, HTTP, and Telnet. The next level is an application level 420. In this example, the vulnerability tree is expanded for the HTTP application type 414. Thus, the applications level has two nodes corresponding to specific HTTP applications, namely Apache 422 and IIS (Internet Information Server) 424. The next level is a version level 430, which in this example includes nodes for versions 1.0 432, 2.0 434 and 3.0 436 of IIS. The next level is the patch level 440 and it includes nodes for the possible patch levels of the application versions. In this example, the vulnerability tree includes Service Pack 1 and Service Pack 2 patch level nodes 442, 444.
[0059] FIG. 5 is a block diagram illustrating an example of a node 500 in a vulnerability tree 400. The node 500 of FIG. 5 is for an application vulnerability tree. Nodes in other types of vulnerability trees can differ from the one described herein. The application node 500 includes node application detection rules 510, zero or more node vulnerabilities 520, and an optional node operating system weight 530.
[0060] The node application detection rules 510 are rules used by the control module 320 to determine whether the host 191 has the characteristics represented by the node. These rules 510 contain deterministic logic such as Boolean conditions that are applied against the characteristics of the host 191 as measured by the high-355 and/or low-level 345 sensors. A rule is satisfied if the host has the characteristic described by the rule. In one embodiment, each application detection rule has a weight. The weight represents the probability that a host satisfying the rule has the characteristic represented by the node. For example, a highly-dispositive rule has a large weight while a less dispositive rule has a smaller weight. The weight for a node is the sum of the weights of its satisfied rules.
[0061] In one embodiment, the control module 320 traverses the application vulnerability tree by evaluating the application detection rules of the one or more child nodes from its present position in the tree and thereby generating a weight for each child node. The control module 320 traverses to the child node having the highest weight. In one embodiment, if none of the weights of the child nodes exceed a threshold, the control module 320 implements a searching procedure to determine if it has incorrectly traversed the tree.
[0062] This technique allows the control module 320 to detect applications executing on non-standard ports. For example, if an email application is executing on the port normally used for web servers, the control module might initially traverse down the portion of the application tree 400 for identifying characteristics of web servers. At some point, many of the characteristics described by the nodes would not apply to the host 191 due to the application being an email application instead of a web server, causing the weights of the child nodes to fall below the threshold. At this point, the control module 320 searches other portions of the application tree (and/or evaluates nodes of other vulnerability trees) in order to identify nodes that better represent the host's 191 characteristics.
[0063] The node vulnerabilities 520, if there are any associated with a node, are vulnerabilities that a host 191 having the characteristics represented by the node might possess. In one embodiment, the vulnerabilities 520 of a node are the vulnerabilities unique to the specific characteristic represented by the node. In this embodiment, therefore, the total vulnerabilities of the host (for a given tree) is the sum of the lowest child node and its parent nodes. In other embodiments, the node vulnerabilities are stored in different representations.
[0064] The operating system weight 530, if any, indicates the probability that a host 191 having the node characteristic is also running a certain operating system. In one embodiment, the operating system weight 520 indicates a particular node in the operating system vulnerability tree and a weight to add to that node. Nodes representing characteristics that are compatible with a single operating system (e.g., IIS is only compatible with Windows) have a relatively high operating system weight 530 because presence of the characteristic is highly correlative to presence of the operating system and vice-versa.
[0065] The vulnerability tree for operating systems is similar to the application vulnerability tree 400 described above. For example, a top level of the tree can represent an operating system family (e.g., Unix, Windows, and MacOS) and descending levels can represent specific operating systems in each family (e.g., specific to Widows is XP, NT, 2000), operating system versions (e.g., specific to NT is 3.5 and 4.0), and patch levels (specific to 3.5 is Service Pack 1 and Service Pack 2).
[0066] FIG. 6 is a block diagram illustrating a centralized correlation server 175 according to an embodiment of the present invention. The centralized correlation server 175 comprises an I/O module 610, a network profiling module 620, and a monitoring module 530.
[0067] The I/O module 610 allows the centralized correlation server 175 to communicate with other devices on the network such as the device profilers 165 and the traffic monitors 185. In one embodiment the I/O module 610 provides I/O functionality to a user through a user interface. The user may, for example, manipulate the configuration information or receive messages from the centralized correlation server 175 regarding the operation and status of the system 100. Depending on the embodiment, the I/O module 610 may be a network interface card or other hardware, a software module, or a combination of both.
[0068] The network profiling module 620 stores the information used by device profilers 165 to identify vulnerabilities and also stores the vulnerabilities of the system 100 detected by the device profilers 165. In one embodiment, the network profiling module 620 generates an abstract view of the configuration of the enterprise network 115 from the information collected from the individual device profilers 191. Advantageously, the network profiling module 620 leverages from individual data points to provide improved network security services.
[0069] The network monitoring module 630 stores the information used by the traffic monitors 185 to monitor network traffic for attacks on identified vulnerabilities and also stores attack signatures correlating to vulnerabilities of the system 100. In one embodiment, the networking monitoring module 530 sends each traffic monitor 185 the attack signatures for all of the vulnerabilities in the system 100. In one embodiment, the network monitoring module 630 sends traffic monitors 185 attack signatures for only vulnerabilities of hosts 191 accessible to the traffic monitored by the traffic monitor 185.
[0070] FIG. 7 is a block diagram illustrating a more detailed view of the network profiling module 620 of FIG. 6 . The network profiling module 620 comprises a low-level sensor rules database 610, a high-level sensor rules database 620, a vulnerability rules database 730, and an identified vulnerabilities module 740. In some embodiments, some or all of these databases can be combined. Advantageously, the rules are stored in a central location for updates, which can then be distributed downstream to the device profilers 165.
[0071] The high-level sensor rules database 710 stores rules used by the high-level sensors 355 of device profilers 365 to identify applications executing on hosts 191 and other characteristics of the hosts 191. The high-level sensor rules database 710 holds rules for sending data to the host 191 that will identify characteristics of the host 191 when analyzed at layers 5–7. For example, a telnet application may respond directly to an inquiry for self-identification.
[0072] The low-level sensor rules database 720 stores rules used by the low-level sensors 345 of the device profilers 165 for identifying operating systems or other characteristics of the hosts 191. These rules include information for generating anomalous data packets and analyzing the responses to the packets received from the hosts 191 in order to identify operating systems and applications on the host 191.
[0073] The vulnerability rules database 730 stores rules used by the control module 320 to identify and verify potential vulnerabilities at the device profilers 165. These rules include the vulnerability trees and rules for using the sensors to traverse the trees, as well as rules for using the sensors to verify the presence of the specific vulnerabilities identified by the trees. The identified vulnerabilities module 740 stores data describing the vulnerabilities of hosts 191 on the network identified by the device profilers 165.
[0074] FIG. 8 is a block diagram illustrating a more detailed view of the network monitoring module 630 of FIG. 6 . The network monitoring module 630 comprises an attack signatures module 810 and an event daemon module 820.
[0075] The attack signatures module 810 stores attack signatures for identifying network traffic indicative of attacks exploiting vulnerabilities of hosts 191 on the network. The attack signatures may be logical rules tested against network traffic. The attack signatures module 810 is configured to generate a subset of attack signatures corresponding to vulnerabilities identified by the device profilers 165 and send the attack signatures to the traffic monitors 185 in the system 100. In one embodiment, the attack signatures are sent to traffic monitors 185 based on their locations in the system 100.
[0076] The event daemon module 820 performs a set of actions to block a host's exposure to its vulnerabilities. In one embodiment the event daemon module 820 responds to a notification of vulnerabilities from the device profiler 165. In another embodiment, the event daemon module 820 responds to a notification of a real-time attack from the traffic monitor 185. The blocking actions may include configuring a firewall to halt communication between the enterprise network 115 and the WAN 130, closing open ports on the host 191, and/or preventing the operating systems and/or applications from executing programs.
[0077] The event daemon module 820 may also send an alert to a network administrator or log the attack. In another embodiment, the event daemon module 820 logs attacks. New information may be compared to previous information in identifying multi-faceted attacks to the enterprise network 115. In still another embodiment, the event daemon 720 sends a message to the user indicating the type and location of an attack.
[0078] FIG. 9 is a block diagram illustrating an embodiment of the traffic monitor 185 according to the present invention. The traffic monitor comprises an I/O module 910, an attack signatures module 920, a rule parsing module 830, and a traffic sniffing module 840.
[0079] The I/O module 910 allows the traffic monitor 185 to communicate with other devices on the network such as the centralized correlation server 175. In implementation, the I/O module 910 may be a network interface card or other hardware, a software module, or a combination of both.
[0080] The attack signatures module 920 stores attack signatures received from the centralized correlation server 175. In one embodiment, the attack signatures module 810 generates subsets of attack signatures valid for each potential destination of traffic monitored by the traffic monitor 185. For example, one subset contains attack signatures valid for a particular IP address and port number. The subset contains the attack signatures of exploits attacking the vulnerabilities known to be present at that specific IP address and port.
[0081] The traffic sniffing module 840 monitors network traffic to detect traffic corresponding to attack signatures in the attack signatures module 920. The traffic sniffing module 840 analyzes network traffic to identify patterns matching the attack signatures. Preferably, the traffic sniffing module 840 uses the subsets of attack signatures to monitor for only exploits of vulnerabilities present at the destination of the traffic. Thus, the traffic sniffing module 840 will ignore an attack signature directed to a destination (e.g., IP address and/or port) that is not vulnerable to the exploit. Additionally, the traffic sniffing module 930 is configured to send a notification message to the centralized correlation server 175 in response to detecting an attack signature.
[0082] FIG. 10 is a flow chart illustrating a method of profiling a host 191 to detect potential vulnerabilities as performed by the device profiler 165 according to an embodiment of the present invention. The control module 320 identifies 1010 hosts on the enterprise network 115 by periodically testing for responses over a range of addresses available in the network, for example, by sending ping requests to each address. In one embodiment, the centralized correlation server 175 notifies device profilers 165 of known hosts on the enterprise network 115. The control module 320 identifies 1020 open ports on the host 191 by periodically port scanning the host 191, for example, by sending TCP connection requests to each port.
[0083] The control module 320 identifies 1030 an application running on an open port by using the high and/or low-level 355, 345 sensors to traverse the nodes of the application vulnerability tree. As part of this process, the control module 320 uses the operating system weights of traversed nodes to identify a starting point in the operating system tree (e.g., the node having the highest weight value). This starting point is typically one to two levels below the root node of the tree. The control module 320 uses the high and/or low-level 355, 345 sensors to traverse the operating system tree from the starting point to identify 1040 an operating system running on the host 191. The control module 320 identifies 1050 the total set of vulnerabilities for the host 191 from the vulnerability trees. Next, the control module 320 uses the sensors 345, 355 to verify 1060 the existence of the vulnerabilities on the host 191.
[0084] The method 1000 is iterative 1095, so the device profiler 165 is scanning constantly or at intervals according to the above process. In another embodiment, the method 1000 is repeated in response to a change in a host 191, the network configuration, or otherwise.
[0085] FIG. 11 is a flow chart illustrating a method of providing distributed security in a network as performed by the centralized correlation server 175 according to an embodiment of the present invention. The centralized correlation server 175 receives 1110 verified vulnerabilities and locations of device profilers 165 in the system 100 stores them in the identified vulnerabilities module 740.
[0086] In preparing information for distribution, the attack signatures module 810 associates 1120 verified vulnerabilities with attack signatures used to monitor for attacks on the vulnerabilities. The centralized correlation server 175 receives 1130 locations of traffic monitors 185 on the system 100. Next, the centralized correlation server 175 sends 1140 the attack signatures for the verified vulnerabilities to the traffic monitors 185 based on the traffic monitors' 185 locations.
[0087] The centralized correlation server 175 repeats the discussed steps 1110, 1120, 1130, 1140 to update attack signatures at relevant traffic monitors.
[0088] FIG. 12 is a flow chart illustrating a method of performing a set of actions to block exposure to a vulnerability by the event daemon module 820. In response to receiving 1210 a notification related to vulnerabilities sent by the device profiler 165, the event daemon module 820 performs a set of actions such as configuring 1220 the firewall 150 to prevent the attack. The notification may be sent directly by the device profiler 165, or indirectly such as from the identified vulnerability module 740. In one embodiment, the notification is sent to block vulnerabilities that have a high probability of being attacked, or that have a high consequence as a result of being attacked.
[0089] In response to receiving 1230 notification of malicious activity from a traffic monitor 185, the centralized correlation server 175 performs a set of actions such as configuring the firewall 150 in real-time to block the attack. The event daemon module 820 may also send 1250 an alert to a network administrator or log the attack.
[0090] FIG. 13 is a flow chart illustrating a method of monitoring a distributed network as performed by the traffic monitor 185 according to an embodiment of the present invention. The traffic monitor 185 sends 1310 a network location to the centralized correlation server 175. The centralized correlation server 175 returns 1320 attack signatures preferably derived at least in part from device profiler's 165 location or likelihood to examine network traffic containing a specific attack signature.
[0091] The traffic monitor 185 analyzes 1330 network traffic for attack signatures. In one embodiment, the traffic monitor 185 determines the destination (e.g., IP address and/or port number) of the traffic, determines the attack signatures associated with that destination, and indicates an attack if the network traffic matches an associated attack signature. In response to detecting malicious activity 1350, the traffic monitor 185 notifies 1240 the event daemon module 820 in the centralized correlation server 175. Otherwise, the traffic monitor 185 constantly examines network traffic.
[0092] In summary, the system 100 is configured pre-incident to an attack on vulnerabilities present on the hosts 191. Accordingly, the traffic monitors 185 and the firewall 150 more effectively and efficiently protect the hosts 191 from malicious activity by leveraging off of information collected from device profilers 165 through the centralized correlation server 175. Additionally, the system configuration is constantly updated to reflect changes inside the network and additional threats from the outside.
[0093] The above description is included to illustrate the operation of the preferred embodiments and is not meant to limit the scope of the invention. The scope of the invention is to be limited only by the following claims. From the above discussion, many variations will be apparent to one of ordinary skill in the art that would yet be encompassed by the spirit and scope of the invention.
Claims
Certificate of Correction present
The claims shown below may not include correction changes. Use the corrected PDF for authoritative text.
We claim:
1. A distributed computer network security system for detecting an attack on a host on a network having a plurality of hosts, the system comprising:
a device profiler communicatively coupled with the network, the device profiler for identifying characteristics of a host from the plurality of hosts on the network and determining vulnerabilities of the host based on the characteristics according to a tree-structured vulnerability table; and
a traffic monitor, communicatively coupled with the network and the device profiler, and cooperative with the device profiler, for monitoring the network for traffic indicative of an attack on the host, from the plurality of hosts on the network, exploiting one of the determined vulnerabilities of the host, wherein a determined vulnerability pertains to a specific location and wherein the traffic monitor monitors for exploits of the determined vulnerability directed to the location and ignores exploits of the determined vulnerability directed to locations to which the determined vulnerability does not pertain.
2. The system of claim 1, wherein the device profiler comprises:
an identification subsystem for sending data packets to the host and determining the characteristics of the host based on the host's response to the data packets.
3. The system of claim 2, wherein the identification subsystem comprises:
an high-level sensor for sending data packets to the host and analyzing responses of the host with respect to at least one of layer 5, layer 6 and layer 7 of the Open Systems Interconnection model to determine characteristics of the host.
4. The system of claim 3, wherein the determined characteristics comprise an application executing on the host.
5. The system of claim 2, further comprising:
a control module for generating a list of vulnerabilities of the host based on the characteristics determined by the identification subsystem.
6. The system of claim 5, wherein the control module is adapted to use the characteristics determined by the identification subsystem to traverse the tree-structured vulnerability table, the vulnerability table having nodes associated with the characteristics of the host, each node having an associated set of vulnerabilities.
7. The system of claim 6, wherein a node representing an application further comprises an operating system weight indicative of an operating system executing on the host.
8. The system of claim 6, wherein the control module is adapted to determine a set of vulnerabilities of the host by summing the vulnerabilities associated with traversed nodes.
9. A distributed computer network security system for detecting an attack on a host on a network having a plurality of hosts, the system comprising:
a device profiler communicatively coupled with the network, the device profiler for identifying characteristics of a host from the plurality of hosts on the network and determining vulnerabilities of the host based on the characteristics according to a tree-structured vulnerability table;
a traffic monitor, communicatively coupled with the network and the device profiler, and cooperative with the device profiler, for monitoring the network for traffic indicative of an attack on the host, from the plurality of hosts on the network, exploiting one of the determined vulnerabilities of the host; and
a centralized correlation server, communicatively coupled with the network at a centrally accessible location, the device profiler and the traffic monitor, the centralized correlation server for receiving the determined vulnerabilities from the device profiler, identifying signatures of network traffic indicating attacks exploiting the determined vulnerabilities, and sending the signatures to the traffic monitor.
10. The system of claim 9, wherein the network has a plurality of locations and each location provides a different perspective of the host, and wherein there are a plurality of device profilers coupled to the network at a network location, each device profiler determining vulnerabilities of the host from the device profiler's perspective at the network location.
11. The system of claim 10, wherein the centralized correlation server further comprises a vulnerability verification rules database for storing rules to non-intrusively verify the identified vulnerabilities.
12. The system of claim 10, wherein the centralized correlation server further comprises an identified vulnerabilities module for storing a plurality of determined vulnerabilities received from the plurality of device profilers, identifying signatures of network traffic indicating attacks exploiting determined vulnerabilities, and sending the attack signatures to the traffic monitor.
13. The system of claim 12, wherein one or more traffic monitors are at selected locations on the network, and wherein the centralized correlation server sends the traffic monitor attack signatures for only vulnerabilities exploitable from the perspective of the traffic monitor.
14. The system of claim 9, wherein the centralized correlation server comprises:
an event module for, in response to receiving a notification related to one of the determined vulnerabilities, performing a set of actions to block exposure to the vulnerability.
15. The system of claim 14, further comprising:
a firewall adapted to selectively restrict network traffic to the host, wherein the event module is adapted to configure the firewall to restrict traffic that exploits the determined vulnerability.
16. A distributed computer network security system for detecting an attack on a host on a network having a plurality of hosts, the system comprising:
a device profiler communicatively coupled with the network, the device profiler for identifying characteristics of a host from the plurality of hosts on the network and determining vulnerabilities of the host based on the characteristics according to a tree-structured vulnerability table, the device profiler including a low-level sensor for sending anomalous data packets to the host and determining the characteristics based on the host's response to the anomalous data packets; and
a traffic monitor, communicatively coupled with the network and the device profiler, and cooperative with the device profiler, for monitoring the network for traffic indicative of an attack on the host, from the plurality of hosts on the network, exploiting one of the determined vulnerabilities of the host.
17. The system of claim 16, wherein the low-level sensor is adapted to determine the characteristics of the host by analyzing responses of the host with respect to at least one of layer 3 and layer 4 of the Open Systems Interconnection model.
18. The system of claim 16, wherein the determined characteristics comprise an operating system version and patch level of the host.
Patent Citations (89)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| US5136523(A) | 1992-08-01 | Landers | Applicant |
| US5278901(A) | 1994-01-01 | Shieh et al. | Applicant |
| US5388211(A) | 1995-02-01 | Hornbuckle | Applicant |
| US5440723(A) | 1995-08-01 | Arnold et al. | Applicant |
| US5557742(A) | 1996-09-01 | Smaha et al. | Applicant |
| US5699403(A) | 1997-12-01 | Ronnen | Applicant |
| US5796942(A) | 1998-08-01 | Esbensen | Applicant |
| US5798706(A) | 1998-08-01 | Kraemer et al. | Applicant |
| US5802320(A) | 1998-09-01 | Baehr et al. | Applicant |
| US5850516(A) | 1998-12-01 | Schneier | Examiner |
| US5892903(A) | 1999-04-01 | Klaus | Applicant |
| US5919257(A) | 1999-07-01 | Trostle | Applicant |
| US5923646(A) | 1999-07-01 | Mandhyan | Applicant |
| US5925126(A) | 1999-07-01 | Hsieh | Applicant |
| US5931946(A) | 1999-08-01 | Terada et al. | Applicant |
| US5958015(A) | 1999-09-01 | Dascalu | Applicant |
| US5961644(A) | 1999-10-01 | Kurtzberg et al. | Applicant |
| US5987611(A) | 1999-11-01 | Freund | Applicant |
| US5991881(A) | 1999-11-01 | Conklin et al. | Applicant |
| US6006328(A) | 1999-12-01 | Drake | Applicant |
| US6044402(A) | 2000-03-01 | Jacobson et al. | Applicant |
| US6088804(A) | 2000-07-01 | Hill et al. | Applicant |
| US6101606(A) | 2000-08-01 | Diersch et al. | Applicant |
| US6185689(B1) | 2001-02-01 | Todd, Sr. et al. | Applicant |
| US6199181(B1) | 2001-03-01 | Rechef et al. | Applicant |
| US6263444(B1) | 2001-07-01 | Fujita | Applicant |
| US6269447(B1) | 2001-07-01 | Maloney et al. | Applicant |
| US6279113(B1) | 2001-08-01 | Vaidya | Applicant |
| US6282546(B1) | 2001-08-01 | Gleichauf et al. | Applicant |
| US6298445(B1) | 2001-10-01 | Shostack et al. | Applicant |
| US6301668(B1) | 2001-10-01 | Gleichauf et al. | Applicant |
| US6321338(B1) | 2001-11-01 | Porras et al. | Applicant |
| US6324656(B1) | 2001-11-01 | Gleichauf et al. | Applicant |
| US6330562(B1) | 2001-12-01 | Boden et al. | Applicant |
| US6343362(B1) | 2002-01-01 | Ptacek et al. | Applicant |
| US6347376(B1) | 2002-02-01 | Attwood et al. | Applicant |
| US6359557(B2) | 2002-03-01 | Bilder | Applicant |
| US6363489(B1) | 2002-03-01 | Comay et al. | Applicant |
| US6370648(B1) | 2002-04-01 | Diep | Applicant |
| US6408391(B1) | 2002-06-01 | Huff et al. | Applicant |
| US6415321(B1) | 2002-07-01 | Gleichauf et al. | Applicant |
| US6470384(B1) | 2002-10-01 | O'Brien et al. | Applicant |
| US6473800(B1) | 2002-10-01 | Jerger et al. | Applicant |
| US6477651(B1) | 2002-11-01 | Teal | Applicant |
| US6484203(B1) | 2002-11-01 | Porras et al. | Examiner |
| US6484315(B1) | 2002-11-01 | Ziese | Applicant |
| US6490626(B1) | 2002-12-01 | Edwards et al. | Applicant |
| US6502135(B1) | 2002-12-01 | Munger et al. | Examiner |
| US6574737(B1) | 2003-06-01 | Kingsford et al. | Examiner |
| US6578147(B1) | 2003-06-01 | Shanklin et al. | Examiner |
| US6584569(B2) | 2003-06-01 | Reshef et al. | Applicant |
| US6609205(B1) | 2003-08-01 | Bernhard et al. | Examiner |
| US6611869(B1) | 2003-08-01 | Eschelbeck et al. | Examiner |
| US6687833(B1) | 2004-02-01 | Osborne et al. | Examiner |
| US6704873(B1) | 2004-03-01 | Underwood | Examiner |
| US6708212(B2) | 2004-03-01 | Porras et al. | Applicant |
| US6711127(B1) | 2004-03-01 | Gorman et al. | Applicant |
| US6718535(B1) | 2004-04-01 | Underwood | Examiner |
| US6735169(B1) | 2004-05-01 | Albert et al. | Applicant |
| US6735702(B1) | 2004-05-01 | Yavatkar et al. | Examiner |
| US6771597(B2) | 2004-08-01 | Makansi et al. | Applicant |
| US6775657(B1) | 2004-08-01 | Baker | Applicant |
| US6778524(B1) | 2004-08-01 | Augart | Examiner |
| US6789216(B2) | 2004-09-01 | Zagorski et al. | Applicant |
| US6816973(B1) | 2004-11-01 | Gleichauf et al. | Examiner |
| US6826172(B1) | 2004-11-01 | Augart | Examiner |
| US6889168(B2) | 2005-05-01 | Hartley et al. | Examiner |
| US6952779(B1) | 2005-10-01 | Cohen et al. | Examiner |
| US6990591(B1) | 2006-01-01 | Pearson | Applicant |
| US2002/0133721(A1) | 2002-09-01 | Adjaoute | Applicant |
| US2004/0015719(A1) | 2004-01-01 | Lee et al. | Examiner |
| US2004/0044912(A1) | 2004-03-01 | Connary et al. | Applicant |
| US2005/0204404(A1) | 2005-09-01 | Hrabik et al. | Examiner |
| US2006/0010389(A1) | 2006-01-01 | Rooney et al. | Examiner |
| US2006/0021034(A1) | 2006-01-01 | Cook | Examiner |
| US2006/0021045(A1) | 2006-01-01 | Cook | Examiner |
| US2006/0069671(A1) | 2006-03-01 | Conley et al. | Applicant |
| US2006/0143710(A1) | 2006-06-01 | Desai et al. | Applicant |
| US2006/0195905(A1) | 2006-08-01 | Fudge | Examiner |
| EP1160646(A2) | 2001-12-01 | Examiner | |
| WO1/31420(A2) | 2001-05-01 | Applicant | |
| WO1/84270(A2) | 2001-11-01 | Applicant | |
| WO184270(A2) | 2001-11-01 | Examiner | |
| WO2/19661(A2) | 2002-03-01 | Applicant | |
| WO227443(A2) | 2002-04-01 | Examiner | |
| WO2/45380(A2) | 2002-06-01 | Applicant | |
| WO2/061544(A2) | 2002-08-01 | Applicant | |
| WO3/084181(A1) | 2003-10-01 | Applicant | |
| WO3/100617(A1) | 2003-12-01 | Applicant |
Non-Patent Literature (27)
- Anonymous, Microsoft Computer Dictionary, 2002, Microsoft Press, Fifth Edition, p. 291.Examiner
- Yurcik, William, Controlling Intrusion Detection Systems by Generating False Positives: Squealing Proof-of-Concept, 2002, IEEE, pp. 134-135.Examiner
- Skaggs et al, Network Vulnerability Analysis, 2002, IEEE, pp. 493-495.Examiner
- Phipatanasuphorn et al, Vulnerability of Sensor Networks to Unauthorized Traversal and Monitoring, 2004, IEEE, pp. 364-369.Examiner
- Bace, Rebecca, An Introduction To Intrusion Detection & Assessment, ICSA, Inc., 1999, pp. 1-38.Applicant
- Fyodor, Remote OS Detection Via TCP/IP Stack FingerPrinting, Oct. 18, 1998, pp. 1-10.Applicant
- Ristenbatt, Martin P., Methodology For Network Communication Vulnerability Analysis, IEEE, 1988, pp. 493-499.Applicant
- Skaggs, B., et al., Network Vulnerability Analysis, IEEE, 2002, pp. 493-495.Applicant
- Thatcher, Michelle, Keeping Your Technology Secure, Technology & Learning, Apr. 2002, pp. 38, 40, 42 and 44.Applicant
- Abstract, W. Erhard, et al., “Network Traffic Analysis and Security Monitoring with UniMon”, Proceeding of the IEEE Conference on High Performance Switching and Routing, 2000, ATM 2000, pp. 439-446 (Jun. 2000).Applicant
- Abstract, Dept. of Comput. Sci., California Univ., Davis, CA, USA, “A Methodology For Testing Intrusion Detection Systems”, IEEE Transactions on Software Engineering, vol. 22, Issue 10, pp. 719-729 (Oct. 1996).Applicant
- Abstract, Mounji A. Le Charlier, et al., “Distributed Audit Trail Analysis”, Proceeding of the Symposium on Network and Distributed System Security, 1995, pp. 102-112 (Feb. 16-17, 1995).Applicant
- Abstract, L.T. Heberlein, et al., “A Network Security Monitor” Proceeding of the 990 IEEE Computer Society Symposium on Research in Security and Privacy, pp. 296-304, (May 7-9, 1990).Applicant
- Abstract, Xinzhou Quin et al., “Integrating Intrusion Detection and Network Management”, Network Operation and Management Symposium, 2002. NAOMS 2002. 2002 IEEE/IFIP, pp. 329-344 (Apr. 15-19, 2002).Applicant
- Abstract, D.G. Schwartz et al., “A Case-Based Approach To Network Intrusion Detection”, Proceeding of the 5th International Conference on Information Fusion, 2002. vol. 2 pp. 1084-1089 (Jul. 8-11, 2002).Applicant
- Abstract, “Open Source Security: Opportunity or Oxymoron?” Computer, vol. 35, Issue 3, pp. 18-21 (Mar. 2002).Applicant
- Abstract, Liu Dihua, et al. “Data Mining For Intrusion Detection”, Proceedings ICII 2001—Beijing 2001 International Conference on Info-Tech and Info-Net, 2001, vol. 5, pp. 7-12, (Oct. 29-Nov. 2001).Applicant
- Abstract, Kai Hwang & M. Gangadharan, “Micro-Firewalls for Dynamic Network Security With Distributed Intrusion Detection”, NCA 2001 IEEE International Symposium on Network Computing and Applications, 2001. pp. 68-79, (Oct. 8-10, 2001).Applicant
- Abstract, Wenke Lee Stolfo, et al., “Real Time Data Mining-Based Intrusion Detection”, Proceedings DARPA Information Survivability Conference & Expositon II, 2001, DISCEX '01. vol. 1, pp. 89-100 (Jun. 12-14, 2001).Applicant
- Abstract, J. Burns, et al., Automatic Management Of Network Security Policy, Proceedings DARPA Information Survivability Conference & Exposition II 2001, DISCEX '01. vol. 2, pp. 12-26, (Jun. 12-14, 2001).Applicant
- Abstract, Heberlein, et al. “A Network Security Monitor”, 1990, Proceedings Research in Security & Privacy 1990 IEEE Computer Society Symposium on, pp. 296-304, (May 7-9, 1990).Applicant
- “Microsoft Computer Dictionary Fifth Edition,” 2002, 6 pages.Applicant
- Anderson, Teresa, “Hunting for Holes,” Security Management, Arlington, Apr. 1996, 2 pages.Applicant
- Breyfogle, Stacey, “Don't Stop at Your Servers,” Software Magazine, Englewood, Jan. 1998, pp. 1-3.Applicant
- Johnson, Johna Till, “Simulated Attack for Real Network Security,” Data Communications, Nov. 2, 1995, pp. 31-32.Applicant
- Goseva-Popstojanova, K., et al., “Characterzing Intrusion Tolerant Systems Using a State Transition Model,” 2001, pp. 211-221, IEEE.Applicant
- Merideth, M. G., et al., “Elephant Network Intrusion Detection Systems that Don't Forget,” Proceedings of the 38th Hawaii International Conference on System Sciences, 2005, pp. 1-10, IEEE.Applicant