US 7,733,803 B2Grant
Systems and methods for modifying network map attributes
Issue Date:2010-06-08
•7 Claims
•18 Drawing Sheets
Abstract
The disclosed systems and methods provide a user interface for modifying host configuration data that has been automatically and passively determined and for adding or modifying other parameters associated with a host. A host data table can store various parameters descriptive of a host including the applicability of specific vulnerabilities. If it is determined that one or more hosts should not be identified as associated with a specific vulnerability, a graphical user interface can be used to modify the vulnerability parameter.
Metadata
Assignee
- Sourcefire, Inc.
Inventors
- William A. Vogel, III
- Dina L. Bruzek
Application Information
Application Number:US 11/272,034
Filing Date:2005-11-14
Priority Date:2005-11-14
Art Unit:2466
Classifications
IPC:
H04L12/28G06F7/04G06F12/14G06F12/16G06F17/30G08B23/00H04N7/16G06F15/173
Patent Drawings (18 sheets)
Description
Field of the Invention
[0001] Embodiments of the present invention relate to systems and methods for determining the characteristics of a computer network. More particularly, embodiments of the present invention relate to systems and methods for automatically and passively determining a host configuration of a computer network and providing a user interface for modifying the host configuration data.
Background
[0002] Computers and computer networks connecting such computers are vital components of modern society. Unfortunately, such computer networks are susceptible to attacks from internal and external hostile sources. Intrusion detection systems (IDSs) are used to prevent such attacks. Conventional IDSs operate by analyzing network traffic in terms of the traffic itself. They do not, however, consider the end points of that traffic. End points refer to the originators and recipients of message traffic. Such end points include, for example, clients and the servers. Analysis of end points can provide contextual information about the network such as host addresses and services. By not considering these end points, a vital piece of contextual information about the network is missed. Consequently, a substantial need exists for technologies that provide information about the end points of computer network traffic.
[0003] IDSs are less effective than they could be because they do not have contextual information about the computer network they are monitoring. For example, without contextual information, IDSs are susceptible to a computer network attack known as evasion. Evasion occurs when an attacker uses network endpoint information that the IDS does not have to evade detection by the IDS. A known method of evasion is insertion. Insertion can be used in networks having a routing infrastructure that handles packets of different sizes. For example, a routing link (router or some other device) may be attached to a network that supports a 1500 byte maximum size on one side of the device and 500 bytes on the other. If someone was trying to talk to a host on the other side of the device, the maximum packet size they could send is 500 bytes. This maximum is called the “Path MTU” (Maximum Transfer Unit). If an attacker knows this, they can transmit a large packet between two properly sized packets and get the IDS to accept the oversized packet, giving the IDS a bad model of the data that is actually arriving at the host.
[0004] Not only does the lack of contextual information make the IDS more susceptible to attack, but it also makes the IDS less efficient. One such inefficiency is that, without contextual information, the IDS may not be able to discern whether or not an attack can cause harm. Attacks can be directed to a particular service running on a target host. Without information about the services running on the target host, an IDS could mistakenly detect an attack even if that host is not running the targeted service. That is, the IDS would cause an alarm even though the attack would be harmless. Such an event is called a false positive. Large numbers of false positives can make it more difficult and expensive to locate genuine attacks that can harm a host on the network.
[0005] Some conventional techniques for providing contextual information to IDSs are known. One such technique is for a human to audit each host manually and gather all desired contextual information. This manual method has a number of disadvantages including that it is time consuming, prone to error, and makes maintenance more difficult. One reason for these drawbacks is that networks are dynamic in nature. Host computers in computer networks are added, removed, and reconfigured. If these changes are not meticulously documented, each computer on the network must be revisited periodically to insure that the contextual information is up to date.
[0006] Another conventional technique for providing contextual information to an IDS is an automatic discovery system. Conventional automatic discovery systems are active scanning systems that actively probe end hosts on a computer network and perform stimulus response tests on them to find and record vulnerabilities that exist on end hosts. Though not manual, active scanning systems also suffer from several problems. One problem is that active scanning can be destructive to the network. In testing for vulnerabilities, they can cause both routers and servers to malfunction or stop functioning. Another problem is that they may not provide information useful to an IDS because in many instances a one-to-one mapping does not exist between the information an active scanner provides and the information an IDS can use. Another problem is that active scanners only provide a snapshot of the network at the time when the scan is performed. This snapshot is problematic because a host may run a vulnerable service transiently. In such a case, the active scanning may be performed at a time when the vulnerable service is not running. As a result, the active scan would not cause an alarm despite the transient nature of the vulnerability.
[0007] While it is advantageous to automatically and passively determine a host configuration, there may be occasions when a passively determined map does not incorporate information that would be useful. For example, a certain version of a service may be known to have certain vulnerabilities while another version of the same service may not be vulnerable. In some cases, a patch may have been applied to a service running on a host thereby eliminating a known vulnerability. In cases such as these, it is advantageous to provide an interface by which a user can modify the data stored in the network map. It is a further advantage to allow a user to conveniently annotate network map data with a graphical user interface.
[0008] In view of the foregoing, it can be appreciated that a substantial need exists for systems and methods that can advantageously provide a user interface for modifying an automatically and passively determined host configuration of a computer network.
Summary of the Invention
[0009] One embodiment of the invention includes a method for assigning a vulnerability parameter to a device on a network by defining a vulnerability parameter for an operating system or service, storing the vulnerability parameter in a host map associated with a network device, providing a graphical user interface for viewing and modifying the vulnerability parameter, and storing the modified vulnerability parameter in the host map associated with the service or operating system.
[0010] Another embodiment of the invention includes a method for automatically and passively determining the characteristics of a network by reading one or more packets transmitted on the network, identifying a network device on the network using the one or more packets, recording an identity of the network device in a host map record associated with the network device, providing a graphical user interface for receiving a parameter from a user, and recording the user parameter in the host map record associated with the network device.
[0011] Another embodiment of the invention is a system for assigning a vulnerability parameter to a device on a network including a computer-readable medium for storing a vulnerability parameter for an operating system or service in a host map associated with a network device, a display for displaying a graphical user interface for viewing and modifying the vulnerability parameter assigned to the service or operating system, and a computer-readable medium for storing the modified vulnerability parameter in the host map associated with the service or operating system.
[0012] Another embodiment of the invention is a system for automatically and passively determining the characteristics of a network including a receiver for receiving one or more packets transmitted on the network and identifying a network device on the network using the one or more packets, a computer-readable medium for storing an identity of the network device in a host map, a display for displaying a graphical user interface for receiving a parameter from a user, and a computer-readable medium for storing the user parameter in the host map associated with the identified network device.
Brief Description of the Drawings
[0013] FIG. 1 illustrates an exemplary method for automatically and passively determining the characteristics of a network.
[0014] FIG. 2 illustrates an exemplary data structure for storing network device information or host information.
[0015] FIG. 3 illustrates an exemplary user interface for displaying user-defined host attributes.
[0016] FIG. 4 illustrates an exemplary user interface for adding and naming a new attribute and selecting its type.
[0017] FIG. 5 illustrates an exemplary user interface for defining an integer attribute with a range.
[0018] FIG. 6 illustrates an exemplary user interface for adding or selecting list items.
[0019] FIG. 7 illustrates an exemplary user interface for modifying an attribute in the attribute list.
[0020] FIG. 8 illustrates an exemplary interface for selecting an attribute from a list of user-defined attributes.
[0021] FIG. 9 illustrates an exemplary user interface including collapsed subsections.
[0022] FIG. 10 illustrates an exemplary interface for editing attributes in a table view.
[0023] FIG. 11 illustrates an exemplary vulnerability editor.
[0024] FIG. 12 illustrates an exemplary user interface for displaying “Invalid” or “Not Applicable” vulnerabilities.
[0025] FIG. 13 illustrates an exemplary interface for searching a criticality field.
[0026] FIG. 14 illustrates an exemplary interface for setting a criticality field.
[0027] FIG. 15 illustrates an exemplary interface for selecting the criticality level for a host.
[0028] FIG. 16 illustrates an exemplary interface for setting a criticality field.
[0029] FIG. 17 illustrates an exemplary text or notes field.
Detailed Description of the Invention
[0030] Embodiments of systems and methods for modifying a passively determined network characteristic database are described in this detailed description of the invention. In this detailed description, for purposes of explanation, numerous specific details are set forth to provide a thorough understanding of embodiments of the present invention. One skilled in the art can appreciate, however, that embodiments of the present invention may be practiced without these specific details. In other instances, structures and devices are shown in block diagram form. Furthermore, one skilled in the art can readily appreciate that the specific sequences in which methods are presented and performed are illustrative and it is contemplated that the sequences can be varied and still remain within the spirit and scope of embodiments of the present invention.
[0031] The present invention is applicable to IDSs, such as those described in the co-pending U.S. patent application Ser. No. 10/793,887, filed Mar. 8, 2004, titled “Methods and Systems for Intrusion Detection,” by Marc A. Norton and Daniel J. Roelker, which is herein incorporated by reference in its entirety. The present invention is also applicable to analysis of vulnerabilities, as described in the co-pending U.S. patent application Ser. No. 10/843,353, filed May 12, 2004, titled “Systems and Methods for Determining Characteristics of a Network and Analyzing Vulnerabilities,” by Martin Roesch, William Andrew Vogel, III, and Matt Watchinski, which is herein incorporated by reference in its entirety.
[0032] Embodiments of the present invention can be applied to passively determined network maps or characteristic databases. These systems are passive because they examine packets moving across a network; they do not perform active scans. They are automatic because they require little or no human intervention. Such passive systems operate by performing functions including: (1) identifying each network device on a network, (2) identifying operating system and services running on each network device, (3) recording, in real-time, any changes occurring on the network, and (4) gathering this information in a format that can be used by a network reporting mechanism. Exemplary network reporting mechanisms include IDSs and network management systems (NMSs).
[0033] Network reporting mechanisms can examine packets moving across a network in real-time, for characteristic information about the network. One such type of characteristic information is information related to a network device, or host, on the network. One skilled in the art can appreciate that a network device is any device with a network connection. Network devices include but are not limited to computers, printers, switches, game machines, and routers.
[0034] In response to network traffic, the identity of the network device is recorded. The identity is stored as a data structure in a file or database, for example. If a packet identifies a network device that has previously been recorded, the current information and the previous information are compared and any changes are recorded. If no changes have been found, no new information is recorded. In either case, the next packet is read.
[0035] FIG. 1 is a flowchart showing an exemplary method 100 for automatically and passively determining the characteristics of a network in accordance with an embodiment of the present invention.
[0036] In step 110 of method 100, a packet transmitted on a network is read.
[0037] In step 120, a network device is identified using the packet. A network device includes but is not limited to a computer, a printer, and a router. One skilled in the art can appreciate that a network device can also be referred to as a host.
[0038] In step 130, the identity of the network device is recorded. The identity is stored as a data structure in a file or database, for example. If a packet identifies a network device that has previously been recorded, the current information and the previous information are compared and changes can be recorded. If no changes have been found, no new information is recorded. In either case, method 100 returns to step 110 to read the next packet.
[0039] FIG. 2 is an exemplary data structure used to store network device information, or host information. This data structure is the host representative data structure. As non-limiting examples, the host information can includes the initiator Internet protocol (IP) address, a list of media access control (MAC) addresses with a time-to-live (TTL) parameter for each MAC address, a list of operating systems, a list of network protocols, a list of transport protocols, a list of transmission control protocol (TCP) service data structures, a list of user datagram protocol (UDP) service data structures, a virtual local area network (VLAN) tag, and a last seen time. The IP address, MAC address and TTL parameter of at least one network device on the network are typically included in each packet transmitted on the network. As a result, these pieces of host information are obtained by directly parsing the network and transport protocol fields of each packet.
Vulnerability Analysis
[0040] In some network monitoring systems, vulnerabilities are assigned to hosts discovered on a network. Vulnerabilities are known methods of maliciously gaining access to a host or host service, or maliciously attacking a host or host service. The vulnerabilities assigned to a host are derived from various sources and this information can be stored in the data structures discussed above for storing network device information. IDSs for example, can maintain vulnerability lists.
[0041] A list of potential vulnerabilities can be stored in a vulnerabilities database (VDB). When a host or host service is identified, one or more vulnerabilities from the VDB is mapped in real-time to the host or host service. These vulnerabilities can then be displayed in a graphical user interface, linked to the particular host or service. An administrator can use this information in connection with the patching specific systems or groups of systems.
[0042] In some cases, a discovered host can be actively scanned in order to refine the list of vulnerabilities for that host from a list of all possible vulnerabilities to a smaller set of core vulnerabilities. This elimination of vulnerabilities along with the lowering of the priority of vulnerabilities that have either already been patched on the target system or vulnerabilities that are not currently present due to the configuration of the service, allows the administrator to target efforts to resolve these vulnerabilities to identified problem areas.
[0043] The present invention permits the creation and modification of predefined and user-defined host attributes with predefined or user-defined values. It also provides the ability for the user to adjust these attribute values for any host manually. In some embodiments, the host attributes can be modified through a graphical user interface (GUI) provided through an application program interface (API). Through this interface, the user can have the ability to modify the network map and/or database through the graphical user interface. As non-limiting examples, the user can be provided with functions for (a) deletion of hosts and network subnets from the network map, (b) deletion of services from the network map, (c) marking of vulnerabilities as “not applicable,” (d) modification of a criticality field for host entries, and (e) text annotation of hosts.
Selective Marking of Vulnerability Mappings as “Not Applicable”
[0044] Users can mark vulnerabilities as “Not Applicable” for a particular host. Vulnerabilities that are “Not Applicable” can be tagged with a database field in the network device database indicating that they are invalid (or not applicable) for the specific host or service. As a result, the “Not Applicable” vulnerabilities can be displayed in a separate list in the host profile and an impact flag can be set based on these vulnerabilities. After a vulnerability has been marked as “Not Applicable,” the user can reactivate the vulnerability. Reactivation of a vulnerability unsets the database flag, causes the impact flag to use the vulnerability again, and causes display of the vulnerability in the “Valid” or “Applicable” vulnerabilities section in the user interface. An example user interface showing “Invalid” or “Not Applicable” vulnerabilities is shown in FIG. 12 .
[0045] In some embodiments, a vulnerability marked as “Not Applicable” can lose status as “Not Applicable” on the occurrence of one or more predefined events. For example, if a change to an operating system or service on an entity occurs that causes a new vulnerability lookup to be performed, the vulnerability can be remapped to the entity as a “Valid” vulnerability, if applicable. If an operating system change event occurs, the previous vulnerability list can also be deleted and a new vulnerability lookup can be performed. If a vulnerability exists for an operating system and is marked as “Invalid” before an operating system change event, the vulnerability can be remapped as a “Valid” vulnerability.
Multiple Vulnerability Modification
[0046] In some embodiments, vulnerabilities can be marked as “Not Applicable” for several hosts with one user action. In such embodiments, multiple hosts or services mapped with a particular vulnerability are searched and identified and all of them are marked as “Not Applicable” without requiring the user to manually select each host or service.
User-Defined Attributes
[0047] Some embodiments of the invention can include an interface for creating one or more attributes in the host profile and assigning values or data types to the attribute. For example, attributes can include (a) an operational criticality attribute with values such as high, medium, or low, (b) a location attribute for storing exemplary values such as “Rockville,” “Santa Clara,” “London”; (c) an room number attribute for storing integer values type in a predefined range such as 0 to 600.
Attribute Types
One or more of the following types of attributes may be edited by a user through a graphical user interface.
Text Attribute Type
[0048] This attribute type is a simple text field that can be appended to or included in the host profile. Removing special characters that may cause security issues from the attribute text value can be handled automatically. An exemplary text or notes field is shown in FIG. 17 .
Integer Range Type
[0049] This attribute type is defined as an integer between a user defined minimum and maximum. If the user attempts to assign an integer to this attribute that falls outside the defined range, an error can be returned. If the attribute definition is modified, any host attribute setting that falls outside the defined range can be deleted.
Value List Type
[0050] This attribute type is defined as a list of string values. At least one value can be defined per list. Each entry can contain an ID that can be used to identify the attribute value when it is assigned to a host. If the attribute is modified and an item is deleted, any host attribute setting with this item value can also be deleted. For example, if a “Location” list attribute exists, and a system is assigned to the “Rockville” location, if the “Rockville” location is deleted, the Location attribute is deleted from all hosts with the “Rockville” value.
IP Assigned Value List Type
[0051] This attribute type is similar to the Value List Type, except that each list item can be associated with a list of network definitions (IP address/netmask pair in CIDR notation), and the value of the attribute for a host can be set automatically based on its IP address. If the value for a specific list item is modified, other hosts having that value set can be updated automatically.
[0052] The network definitions can be evaluated from most-specific to least-specific. For example, if the networks 10.4.0.0/16 and 10.0.0.0/8 are specified for different levels, the host 10.4.12.68 can be assigned the value matched with the 10.4.0.0/16 network. If the IP ranges for list items are modified, then the attribute value settings for the hosts can be automatically re-evaluated.
Host Criticality
[0053] A server criticality field can be provided for hosts in the network map. This field can be added in both the database and memory map representations of hosts and can be a searchable field. An exemplary interface for searching this attribute is shown in FIG. 13 .
[0054] In one exemplary embodiment, the criticality category can contain four levels: none, low, medium, and high. The “none” level can be defined as the default level. When new hosts are added to the network map they can automatically be assigned this level. Users can change the level for individual hosts or apply a level change to selected hosts from the search results screen and/or the host view screen. Exemplary interfaces for setting the criticality field are shown in FIGS. 15 and 17 . As discussed in more detail below, the criticality field can also be used in a rule associated with one or more policies and responses.
[0055] From the host map view, the criticality of a specific host may be selected by a user. According to the exemplary interface shown in FIG. 15 , if the user clicks on a link, a pop-up can appear to allow the user to select the criticality level for the specific host.
Network Monitoring System Integration
[0056] Attribute definitions can contain Universal Unique Identifiers (UUIDs) to allow high availability peers and managed sensors to differentiate between locally and remotely generated attributes. As used herein, a high availability peer is a second system storing a second copy of a network map. In some embodiments, the network map stored for high availability can be synchronized between multiple peers hosting the map. Hosts assigned a value on one network monitoring system can be automatically assigned that value on a second high availability network monitoring system. In some embodiments, attributes that have been propagated to a second network entity can be modified on the second entity and propagated back to the first entity. Any of attributes and/or validity and applicability parameters described herein can be made available through high availability peers.
[0057] Users can be given the ability to define generic attributes that can be applied to all host profiles. The attributes can be usable in host searches and in connection with policies and responses. Features such as, but not limited to, adding, deleting and modifying attribute definitions, and setting and deleting attribute values for specific hosts can be performed through an API.
Policy and Response
[0058] When attributes are created, these values can be added to policy and response rules and search constraints. For the value list attribute type, users can be allowed to use the “is” and “is not” operators. For the integer range attribute type, users can be allowed to use mathematical operators such as =, <, and >. For text attributes, regular expression searches can be performed using operators such as “contains”, “starts with”, and “ends with.”
[0059] In further embodiments, an interface can be provided so that a user can (a) assign attributes and values to hosts in the host profile, (b) assign attributes to one or more hosts in a host table view, (c) automatically assign and automatically set attribute values to a host based on an IP address and when the host is detected, (d) set predefined host attributes for use in a policy and response rule as a host qualifier, and (e) manage user defined host attributes.
Graphical User Interface
[0060] The graphical user interface can provide the user with a vulnerability editor to mark a specific vulnerability as “not applicable” for one or more hosts. In some embodiments, the interface can include a search screen that includes “vulnerability ID” as a searchable field to facilitate location of hosts with a selected vulnerability. Some embodiments can include a user interface to support user-defined host attributes. Through the interface, the user can perform one or more of the following functions: (a) creating and modifying attribute definitions, (b) viewing and modifying attribute settings for specific hosts, and (c) organizing host displays based on attribute values.
Existing Attribute List
[0061] The attribute list screen displays user-defined attributes. Initially, the list may be empty. Activation of a “create” link can display a separate screen for creating new attributes. For existing attributes, the table can display a name, type, and automatically assign a setting for attributes. The interface can include two links in each row for modifying and deleting specific attributes: an “edit” link can display an interface for editing entries and a “delete” link can delete selected items and refresh the table display. One such exemplary interface is shown in FIG. 3 .
Add New Attribute
[0062] An add new attribute screen allows the user to name a new attribute, choose its type, and configure further settings based upon the type. As discussed above, exemplary types of attributes can include: text, integer, and list. In some embodiments, a limited set of the graphical user interface components for configuring the currently selected type are displayed. One such exemplary interface is shown in FIG. 4 .
[0063] The integer range type interface can display two new rows containing the minimum and maximum input fields for the integer range. One such exemplary interface is shown in FIG. 5 .
[0064] The list type can display two or more lists. One such exemplary interface is shown in FIG. 6 . The first list is the list of values for the attribute. When one of these values is selected, the second list can display the IP ranges that are automatically assigned that value. Values can be added to either list using input fields. Selected items can be deleted using the “X” in the top-right of each list area. When the user is finished configuring the new attribute, the “Save Attribute” button can be used to add the attribute. The user can return to the attribute list later by activating a “Return to Attribute List” link or button.
Modify Existing Attribute
[0065] When the user clicks on the modify link for a specific attribute in the attribute list, an interface for modifying an existing attribute can be presented. One such exemplary interface is shown in FIG. 7 . In some embodiments, a user is not permitted to change the type for an existing attribute. In such embodiments, the type is displayed as a label instead of a modifiable combination box. In some embodiments, controls employed in the new attribute interface can be used in the modify existing attribute interface.
Network Map View of Attributes
[0066] The attribute view can allow the user to choose an attribute from a list of user-defined attributes. The values for the selected attribute can then be displayed as the top-level elements in the network map tree. When the user expands one of these values, a list of host IPs that have that attribute value set can be displayed as child elements. Selection of one of these hosts can cause display the host profile view in the right-hand panel. One such exemplary interface is shown in FIG. 8 .
Attributes in the Host Profile
[0067] Host profile data can be viewed in any one of several graphical user interfaces. In some embodiments, editing of host attributes and vulnerabilities can be performed in separate popup windows. Attributes that have values set can also be displayed in a read-only host profile.
Collapsed Subsections
[0068] In some embodiments, displayed subsections, such as Services and Vulnerabilities can be expanded or collapsed. By default, they can be collapsed which can make the host profile less overwhelming and reduce its vertical size. The collapsed subsections can display a total element count in the title bar to inform user of the number of sub-elements without requiring expansion of each section. One such exemplary interface is shown in FIG. 9 .
Attribute Editor
[0069] An attribute editor can be used to edit attributes in the table view. The editor can be a popup window that allows the user to select an available attribute and set its value for the selected host. The popup can include of a presentation of available attributes. Once an attribute is selected, an appropriate edit field for that attribute can be displayed. As non-limiting examples, the fields can include a text-area for text attributes, a text-field for range attributes, and a box for list attributes. One such exemplary interface is shown in FIG. 10 .
Vulnerabilities Editor
[0070] The vulnerability editor can allow users to easily designate the vulnerabilities that are, and are not, applicable to the current host. In one embodiment, the window can consist of two select lists, side by side, with arrow buttons between them. To transfer vulnerabilities from one list to the other, the user can select the desired items and click one of the arrow buttons. When the user is finished arranging the lists, the “Save” button can be used to apply the changes. One such exemplary interface is shown in FIG. 11 .
Attribute Table View
[0071] An attribute table view can be used for searching, displaying, and reporting of attribute values and the hosts associated with those values. These attributes can be displayed in the host table view or in a separate table view. This table view can display columns for the attribute name, the IP address of hosts with attribute settings, and the value of those attributes.
[0072] A corresponding attribute search page can be provided for searching the attribute table view based on attribute name, value, and/or host IP address. Link buttons from the attribute table view to other table views can also be used for locating other information associated with a set of selected attributes.
[0073] In some embodiments, a “Set Attributes” button can be included in the interface. Selection of this button can cause display a popup window that allows the user to select an available attribute and set its value for hosts identified in the table view. The popup can include a combo-box of available attributes, and once an attribute is selected, an appropriate edit field for that attribute can be displayed such as a text-area for text attributes, a text-field for range attributes, or a combo-box for list attributes.
[0074] In accordance with an embodiment of the present invention, instructions adapted to be executed by a processor to perform a method are stored on a computer readable medium. The computer-readable medium can be a device that stores digital information. For example, a computer-readable medium includes a read-only memory (e.g., a Compact Disc-ROM (“CD-ROM”) as is known in the art for storing software. The computer-readable medium can be accessed by a processor suitable for executing instructions adapted to be executed. The terms “instructions configured to be executed” and “instructions to be executed” are meant to encompass any instructions that are ready to be executed in their present form (e.g., machine code) by a processor, or require further manipulation (e.g., compilation, decryption, or provided with an access code, etc.) to be ready to be executed by a processor.
[0075] Embodiments of the present invention relate to data communications via one or more networks. The data communications can be carried by one or more communications channels of the one or more networks. A network can include wired communication links (e.g., coaxial cable, copper wires, optical fibers, a combination thereof, and so on), wireless communication links (e.g., satellite communication links, terrestrial wireless communication links, satellite-to-terrestrial communication links, a combination thereof, and so on), or a combination thereof. A communications link can include one or more communications channels, where a communications channel carries communications.
[0076] In the foregoing detailed description, systems and methods in accordance with embodiments of the present invention have been described with reference to specific exemplary embodiments. Accordingly, the present specification and figures are to be regarded as illustrative rather than restrictive. The scope of the invention is to be further understood by the claims, and by their equivalents.
Claims
The invention claimed is:
1. A method for assigning a vulnerability parameter to a device on a network, comprising:
passively determining, responsive to a passively read packet, a vulnerability parameter for an operating system or service;
storing, responsive to the vulnerability parameter being passively determined, the vulnerability parameter in a host map associated with a network device;
providing a graphical user interface for viewing and modifying the vulnerability parameter which was passively determined; and
storing the modified vulnerability parameter in the host map, wherein
the vulnerability parameter is invalid or valid,
when the vulnerability parameter is invalid and a pre-defined change in the operating system or service occurs on the network device, a vulnerability lookup is performed for the changed operating system or service and the vulnerability parameter is mapped from invalid to valid based on the vulnerability lookup for the changed operating system or service,
wherein
the vulnerability parameter is associated with a universal unique identifier to distinguish between locally and remotely generated vulnerability parameters and is synchronized to a high availability peer, the vulnerability parameter being propagated from the host map to the high availability peer,
when the vulnerability parameter is modified at the high availability peer, the modified vulnerability parameter is propagated from the high availability peer back to the host map.
2. The method of claim 1, wherein the graphical user interface is provided through an application program interface.
3. The method of claim 1, wherein the graphical user interface provides a function for setting the vulnerability parameter for a plurality of selected hosts or services.
4. The method of claim 1, wherein the graphical user interface provides a function for deleting a host from a network map.
5. A method for assigning a vulnerability parameter to a device on a network, comprising:
passively determining, responsive to a passively read packet, a vulnerability parameter for an operating system or service;
storing, responsive to the vulnerability parameter being passively determined, the vulnerability parameter in a host map associated with a network device;
providing a graphical user interface for viewing and modifying the vulnerability parameter which was passively determined; and
storing the modified vulnerability parameter in the host map, wherein
the vulnerability parameter is associated with a universal unique identifier to distinguish between locally and remotely generated vulnerability parameters and is synchronized to a high availability peer, the vulnerability parameter being propagated from the host map to the high availability peer,
when the vulnerability parameter is modified at the high availability peer, the modified vulnerability parameter is propagated from the high availability peer back to the host map.
6. A system for assigning a vulnerability parameter to a device on a network, comprising:
a computer-readable medium for storing, responsive to a vulnerability parameter for an operating system or service being passively determined, the vulnerability parameter for the operating system or service in a host map associated with a network device;
a display configured to display a graphical user interface for viewing and modifying the vulnerability parameter which was passively determined, the vulnerability parameter being assigned to the service or operating system; and
a computer-readable medium for storing the modified vulnerability parameter in the host map, wherein
the vulnerability parameter is invalid or valid,
when the vulnerability parameter is invalid and a pre-defined change in the operating system or service occurs on the network device, a vulnerability lookup is performed for the changed operating system or service and the vulnerability parameter is mapped from invalid to valid based on the vulnerability lookup for the changed operating system or service,
wherein
the vulnerability parameter is associated with a universal unique identifier to distinguish between locally and remotely generated vulnerability parameters and is synchronized to a high availability peer, the vulnerability parameter being propagated from the host map to the high availability peer,
when the vulnerability parameter is modified at the high availability peer, the modified vulnerability parameter is propagated from the high availability peer back to the host map.
7. A system for assigning a vulnerability parameter to a device on a network, comprising:
a computer-readable medium for storing, responsive to a vulnerability parameter for an operating system or service being passively determined, the vulnerability parameter for the operating system or service in a host map associated with a network device;
a display configured to display a graphical user interface for viewing and modifying the vulnerability parameter which was passively determined, the vulnerability parameter being assigned to the service or operating system; and
a computer-readable medium for storing the modified vulnerability parameter in the host map, wherein
the vulnerability parameter is associated with a universal unique identifier to distinguish between locally and remotely generated vulnerability parameters and is synchronized to a high availability peer, the vulnerability parameter being propagated from the host map to the high availability peer,
when the vulnerability parameter is modified at the high availability peer, the modified vulnerability parameter is propagated from the high availability peer back to the host map.
Patent Citations (119)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| US4550436(A) | 1985-10-01 | Freeman | Applicant |
| US4570157(A) | 1986-02-01 | Kodaira | Applicant |
| US4857912(A) | 1989-08-01 | Everett et al. | Applicant |
| US4912748(A) | 1990-03-01 | Horii et al. | Applicant |
| US4985863(A) | 1991-01-01 | Fujisawa et al. | Applicant |
| US5193192(A) | 1993-03-01 | Seberger | Applicant |
| US5222081(A) | 1993-06-01 | Lewis et al. | Applicant |
| US5404488(A) | 1995-04-01 | Kerrigan et al. | Applicant |
| US5430842(A) | 1995-07-01 | Thompson et al. | Applicant |
| US5459841(A) | 1995-10-01 | Flora-Holmquist et al. | Applicant |
| US5497463(A) | 1996-03-01 | Stein et al. | Applicant |
| US5604910(A) | 1997-02-01 | Kojima et al. | Applicant |
| US5796942(A) | 1998-08-01 | Esbensen | Applicant |
| US5870554(A) | 1999-02-01 | Grossman et al. | Applicant |
| US5901307(A) | 1999-05-01 | Potter et al. | Applicant |
| US5917821(A) | 1999-06-01 | Gobuyan et al. | Applicant |
| US5919257(A) | 1999-07-01 | Trostle | Applicant |
| US5963942(A) | 1999-10-01 | Igata | Applicant |
| US5987473(A) | 1999-11-01 | Jorgensen | Applicant |
| US5995963(A) | 1999-11-01 | Nanba et al. | Applicant |
| US5999937(A) | 1999-12-01 | Ellard | Applicant |
| US6002427(A) | 1999-12-01 | Kipust | Applicant |
| US6141686(A) | 2000-10-01 | Jackowski et al. | Applicant |
| US6199181(B1) | 2001-03-01 | Rechef et al. | Applicant |
| US6219786(B1) | 2001-04-01 | Cunningham et al. | Applicant |
| US6320848(B1) | 2001-11-01 | Edwards et al. | Applicant |
| US6321338(B1) | 2001-11-01 | Porras et al. | Applicant |
| US6324656(B1) | 2001-11-01 | Gleichauf et al. | Applicant |
| US6334121(B1) | 2001-12-01 | Primeaux et al. | Applicant |
| US6343362(B1) | 2002-01-01 | Ptacek et al. | Applicant |
| US6393474(B1) | 2002-05-01 | Eichert et al. | Applicant |
| US6415321(B1) | 2002-07-01 | Gleichauf et al. | Applicant |
| US6477648(B1) | 2002-11-01 | Schell et al. | Applicant |
| US6487666(B1) | 2002-11-01 | Shanklin et al. | Applicant |
| US6499107(B1) | 2002-12-01 | Gleichauf et al. | Applicant |
| US6539381(B1) | 2003-03-01 | Prasad et al. | Applicant |
| US6587876(B1) | 2003-07-01 | Mahon et al. | Applicant |
| US6590885(B1) | 2003-07-01 | Jorgensen | Applicant |
| US6678734(B1) | 2004-01-01 | Haatainen et al. | Applicant |
| US6678824(B1) | 2004-01-01 | Cannon et al. | Applicant |
| US6711127(B1) | 2004-03-01 | Gorman et al. | Applicant |
| US6754826(B1) | 2004-06-01 | Challenger et al. | Applicant |
| US6766320(B1) | 2004-07-01 | Wang et al. | Applicant |
| US6772196(B1) | 2004-08-01 | Kirsch et al. | Applicant |
| US6789202(B1) | 2004-09-01 | Ko et al. | Applicant |
| US6851061(B1) | 2005-02-01 | Holland et al. | Applicant |
| US6957348(B1) | 2005-10-01 | Flowers et al. | Applicant |
| US6983323(B2) | 2006-01-01 | Cantrell et al. | Applicant |
| US6999998(B2) | 2006-02-01 | Russell | Applicant |
| US7032114(B1) | 2006-04-01 | Moran | Applicant |
| US7058821(B1) | 2006-06-01 | Parekh et al. | Applicant |
| US7065657(B1) | 2006-06-01 | Moran | Applicant |
| US7073198(B1) | 2006-07-01 | Flowers et al. | Applicant |
| US7076803(B2) | 2006-07-01 | Bruton et al. | Applicant |
| US7096503(B1) | 2006-08-01 | Magdych et al. | Applicant |
| US7113789(B1) | 2006-09-01 | Boehmke | Examiner |
| US7133916(B2) | 2006-11-01 | Schunemann | Applicant |
| US7134141(B2) | 2006-11-01 | Crosbie et al. | Applicant |
| US7152105(B2) | 2006-12-01 | McClure et al. | Applicant |
| US7181769(B1) | 2007-02-01 | Keanini et al. | Applicant |
| US7257630(B2) | 2007-08-01 | Cole et al. | Applicant |
| US7305708(B2) | 2007-12-01 | Norton et al. | Applicant |
| US7310688(B1) | 2007-12-01 | Chin | Applicant |
| US7313695(B2) | 2007-12-01 | Norton et al. | Applicant |
| US7315801(B1) | 2008-01-01 | Dowd et al. | Applicant |
| US7317693(B1) | 2008-01-01 | Roesch et al. | Applicant |
| US7363656(B2) | 2008-04-01 | Weber et al. | Applicant |
| US2001/0027485(A1) | 2001-10-01 | Ogishi et al. | Applicant |
| US2001/0034847(A1) | 2001-10-01 | Gaul, Jr. | Applicant |
| US2002/0035639(A1) | 2002-03-01 | Xu | Applicant |
| US2002/0066034(A1) | 2002-05-01 | Schlossberg | Applicant |
| US2002/0083344(A1) | 2002-06-01 | Vairavan | Applicant |
| US2002/0087716(A1) | 2002-07-01 | Mustafa | Applicant |
| US2002/0112185(A1) | 2002-08-01 | Hodges | Applicant |
| US2002/0123995(A1) | 2002-09-01 | Shibuya | Applicant |
| US2002/0165707(A1) | 2002-11-01 | Call | Applicant |
| US2003/0014662(A1) | 2003-01-01 | Gupta et al. | Applicant |
| US2003/0046388(A1) | 2003-03-01 | Milliken | Applicant |
| US2003/0065817(A1) | 2003-04-01 | Benchetrit et al. | Applicant |
| US2003/0083847(A1) | 2003-05-01 | Schertz et al. | Applicant |
| US2003/0093517(A1) | 2003-05-01 | Tarquini et al. | Applicant |
| US2003/0101353(A1) | 2003-05-01 | Tarquini et al. | Applicant |
| US2003/0140250(A1) | 2003-07-01 | Taninaka et al. | Applicant |
| US2003/0195874(A1) | 2003-10-01 | Akaboshi | Applicant |
| US2003/0212910(A1) | 2003-11-01 | Rowland et al. | Applicant |
| US2003/0229726(A1) | 2003-12-01 | Daseke et al. | Applicant |
| US2004/0015728(A1) | 2004-01-01 | Cole et al. | Applicant |
| US2004/0034773(A1) | 2004-02-01 | Balabine et al. | Applicant |
| US2004/0064726(A1) | 2004-04-01 | Girouard | Applicant |
| US2004/0073800(A1) | 2004-04-01 | Shah et al. | Applicant |
| US2004/0093582(A1) | 2004-05-01 | Segura | Applicant |
| US2004/0098618(A1) | 2004-05-01 | Kim et al. | Applicant |
| US2004/0123153(A1) | 2004-06-01 | Wright et al. | Applicant |
| US2004/0172234(A1) | 2004-09-01 | Dapp et al. | Applicant |
| US2004/0179477(A1) | 2004-09-01 | Lincoln et al. | Applicant |
| US2004/0193943(A1) | 2004-09-01 | Angelino et al. | Applicant |
| US2004/0221176(A1) | 2004-11-01 | Cole | Applicant |
| US2004/0268358(A1) | 2004-12-01 | Darling et al. | Applicant |
| US2005/0005169(A1) | 2005-01-01 | Kelekar | Applicant |
| US2005/0044422(A1) | 2005-02-01 | Cantrell et al. | Applicant |
| US2005/0108393(A1) | 2005-05-01 | Banerjee et al. | Applicant |
| US2005/0113941(A1) | 2005-05-01 | Ii et al. | Applicant |
| US2005/0114700(A1) | 2005-05-01 | Barrie et al. | Applicant |
| US2005/0160095(A1) | 2005-07-01 | Dick et al. | Applicant |
| US2005/0172019(A1) | 2005-08-01 | Williamson et al. | Applicant |
| US2005/0188079(A1) | 2005-08-01 | Motsinger et al. | Examiner |
| US2005/0229255(A1) | 2005-10-01 | Gula et al. | Applicant |
| US2005/0240604(A1) | 2005-10-01 | Corl, Jr. et al. | Applicant |
| US2005/0251500(A1) | 2005-11-01 | Vahalia et al. | Applicant |
| US2005/0268331(A1) | 2005-12-01 | Le et al. | Applicant |
| US2005/0268332(A1) | 2005-12-01 | Le et al. | Applicant |
| US2005/0273857(A1) | 2005-12-01 | Freund | Applicant |
| US2006/0174337(A1) | 2006-08-01 | Bernoth | Applicant |
| US2006/0265748(A1) | 2006-11-01 | Potok | Applicant |
| US2006/0294588(A1) | 2006-12-01 | Lahann et al. | Applicant |
| US2007/0192863(A1) | 2007-08-01 | Kapoor et al. | Applicant |
| US2007/0288579(A1) | 2007-12-01 | Schunemann | Applicant |
| US2008/0168561(A1) | 2008-07-01 | Durie et al. | Applicant |
| US2009/0028147(A1) | 2009-01-01 | Russell | Applicant |
Non-Patent Literature (114)
- Renaud Deraison, Jay Beale, Haroon Meer, Roelof Temmingh and Cherl Van Der Walt, Nessus Network Auditing, Sungress Publishing, Jul. 20, 2004, pp. 1-13.Examiner
- Renaud Deraison, Ron Gula and Todd Hayton, Passive Vulnerability Scanning: Introduction to NeVO, Tenable Network Security, May 30, 2004, pp. 1-13.Examiner
- International Preliminary Report on Patentability dated May 22, 2008 in corresponding PCT application No. PCT/US2006/043800.Applicant
- Office Action issued on Feb. 5, 2008 in connection with the related U.S. Appl. No. 10/843,375.Applicant
- Spitzner, Lance; Passive Fingerprinting, May 3, 2003; Focus on Intrusion Detection; pp. 1-4; obtained from http://www.ctillhq.com/pdfdb/000183/data.pdf.Applicant
- Lyon, Gordon; Remote OS detection via TCP/IP Stack Fingerprinting, Jun. 30, 2002; pp. 1-12; obtained from: http://web.archive.org/web/20021017063625/www.insecure.org/nmap/nmap-fingerprinting-article.html.Applicant
- U.S. Appl. No. 10/843,353, filed May 2004, Roesch et al., System and Method for Determining Characteristics of a Network and Analyzing Vulnerabilities.Applicant
- U.S. Appl. No. 10/843,373, filed May 2004, Roesch et al., Systems and Methods for Identifying the Services of a Network.Applicant
- U.S. Appl. No. 10/843,374, filed May 2004, Roesch et al., System and Methods for Determining Characteristics of a Network Based on Flow Analysis.Applicant
- U.S. Appl. No. 10/843,375, filed May 2004, Roesch et al., Systems and Methods for Determining Characteristics of a Network and Assessing Confidence.Applicant
- U.S. Appl. No. 10/843,398, filed May 2004, Roesch et al., Systems and Methods for Determining Characteristics of a Network.Applicant
- U.S. Appl. No. 10/843,459, filed May 2004, Roesch et al., Systems and Methods for Determining Characteristics of a Network and Enforcing Policy.Applicant
- U.S. Appl. No. 10/898,220, filed Jul. 2004, Norton et al., Methods and Systems for Multi-Pattern Searching.Applicant
- U.S. Appl. No. 10/951,796, filed Sep. 2004, Roelker et al., Intrusion Detection Strategies for Hypertext Transport Protocol.Applicant
- U.S. Appl. No. 11/272,033, filed Nov. 2005, Dempster et al., Systems and Methods for Identifying the Client Applications of a Network.Applicant
- U.S. Appl. No. 11/272,035, filed Nov. 2005, Gustafson et al., Intrusion Event Correlation with Network Discovery Information.Applicant
- U.S. Appl. No. 11/493,934, filed Jul. 2006, Roesch et al., Device, System and Method for Analysis of Fragments in a Fragment Train.Applicant
- U.S. Appl. No. 11/501,776, filed Aug. 2006, Roesch et al., Device System and Method for Analysis of Segments in a Transmission Control Protocol (TCP) Session.Applicant
- U.S. Appl. No. 11/711,876, filed Feb. 2007, Sturges et al., Device, System and Method for Timestamp Analysis of Segments in a Transmission Control Protocol (TCP) Session.Applicant
- U.S. Appl. No. 11/785,609, filed Apr. 2007, Norton et al., Methods and Systems for Multi-Pattern Searching.Applicant
- U.S. Appl. No. 11/905,980, filed Oct. 2007, Roesch, Device, System and Method for Use of Micro-Policies in Intrusion Detection/Prevention.Applicant
- U.S. Appl. No. 12/010,900, filed Jan. 2008, Norton et al., Methods and Systems for Multi-Pattern Searching.Applicant
- U.S. Appl. No. 12/149,196, filed Apr. 2008, Rittermann, Real-Time User Awareness for a Computer Network.Applicant
- U.S. Appl. No. 12/230,338, filed Aug. 2008, Sturges et al., Speed and Memory Optimization of Intrusion Detection System (IDS) and Intrusion Prevention System (IPS) Rule Processing.Applicant
- Aho et al., “Efficient String Matching: An Aid to Bibliographic Search,” Communications from the ACM (Jun. 1975), vol. 18, No. 6, pp. 333-340.Applicant
- Tarjan, et al., “Storing a Sparse Table,” Communications of the ACM (Nov. 1979), vol. 2, No. 11, pp. 606-620.Applicant
- T. Ptacek, et al., “Insertion, Evasion, and Denial of Service: Eluding Network Intrusion Detection”, Jan. 1998, pp. 1-63.Applicant
- N. Chase, “Active Server pp. 3.0 from Scratch” (Dec. 1999), Searching for products section, 13 pp.Applicant
- B. Krishnamurthy, “Web Protocols and Practice,” (May 1, 2001), pp. 518-520.Applicant
- U. Shankar and V. Paxson, Active Mapping: Resisting NIDS Evasion Without Alerting Traffic, Proc. IEEE Symposium on Security and Privacy. May 2003, pp. 1-18.Applicant
- D. Roelker, “HTTPS IDS Evasions Revisited” (Aug. 1, 2003) [online] (retrieved on Nov. 9, 2006). Retrieved from the Internet <URL: http://docs.idsresearch.org/http—ids—evasions.pdf>.Applicant
- Norton et al., “Multi-Patten Search Engine Aho-Corasick State Machine” (Mar. 17, 2004), Version 2.0, 36 pp.Applicant
- M. Norton, “Optimizing Pattern Matching for Intrusion Detection” (Jul. 4, 2004) [online] (retrieved on Nov. 9, 2006). Retrieved from the Internet <URL: http://docs.idsresearch.org/OptimizingPatternMatchingForIDS.pdf>.Applicant
- Norton et al., “Sourcefire Optimizing Pattern Matching for Intrusion Detection” (Sep. 2004), 14 pp.Applicant
- J. Novak, “Target-Based Fragmentation Reassembly” (Apr. 2005), Revision 2.0, pp. 1-32.Applicant
- S.Siddharth, “Evading NIDS, revisited” (Dec. 12, 2005).Applicant
- “Snort™ Users Manual 2.6.0,” The Snort Project (May 23, 2006), pp. 1-126.Applicant
- “Toupper()—convert lowercase character to uppercase,” http://www.mkssoftware.com, printed on Sep. 20, 2008 from http://web.archive.org, archive date Jun. 30, 2006, 2 pp.Applicant
- J. Novak et al., “Target-Based TCP Stream Reassembly” (Aug. 3, 2007), Revision 1.0, pp. 1-23, obtained from: http://www.snort/org/docs/stream5-modelAUg032007.pdf.Applicant
- “TaoSecurity—Dedicated to FreeBSD, network security monitoring, incident response, and network forensics,” (Oct. 1, 2007), obtained from: http://taosecurity.blogspot.com/2005/02/shmoocon-concludes-shmoocon-finished.html.Applicant
- Office Action issued by the U.S. Patent Office on Jul. 16, 2007 in connection with related U.S. Appl. No. 10/898,220.Applicant
- Office Action issued by the U.S. Patent Office on Sep. 6, 2007 in connection with related U.S. Appl. No. 10/843,374.Applicant
- Notice of Allowance issued by the U.S. Patent Office on Sep. 6, 2007 in connection with related U.S. Appl. No. 10/843,376.Applicant
- Office Action issued by the U.S. Patent Office on Sep. 26, 2007 in connection with related U.S. Appl. No. 10/843,353.Applicant
- Office Action issued by the U.S. Patent Office on Oct. 4, 2007 in connection with related U.S. Appl. No. 10/951,796.Applicant
- Notice of Allowance issued by the U.S. Patent Office on Oct. 5, 2007 in connection with related U.S. Appl. No. 10/793,887.Applicant
- Office Action issued by the U.S. Patent Office on Nov. 21, 2007 in connection with related U.S. Appl. No. 10/843,398.Applicant
- European Search Report issued by the European Patent Office on Nov. 22, 2007 in connection with European patent application No. 07014575.0-1244, which corresponds to related U.S. Appl. No. 11/493,934.Applicant
- International Search Report and Written Opinion of the International Searching Authority issued on Dec. 5, 2007 in connection with PCT application No. PCT/US05/25583, which corresponds to U.S. Appl. No. 10/951,796.Applicant
- European Search Report issued by the European Patent Office on Dec. 27, 2007 in connection with European patent application No. 07015003.2-2413, which corresponds to related U.S. Appl. No. 11/501,776.Applicant
- Office Action issued by the U.S. Patent Office on Jan. 10, 2008 in connection with related U.S. Appl. No. 10/843,373.Applicant
- Office Action issued by the U.S. Patent Office on Feb. 21, 2008 in connection with related U.S. Appl. No. 11/272,033.Applicant
- Office Action issued by the U.S. Patent Office on Mar. 12, 2008 in connection with related U.S. Appl. No. 10/843,459.Applicant
- Office Action issued by the U.S. Patent Office on Mar. 20, 2008 in connection with related U.S. Appl. No. 10/843,374.Applicant
- Final Office Action issued by the U.S. Patent Office on May 9, 2008 in connection with related U.S. Appl. No. 10/843,353.Applicant
- Final Office Action issued by the U.S. Patent Office on Jun. 4, 2008 in connection with related U.S. Appl. No. 10/843,398.Applicant
- International Search Report and Written Opinion of the International Searching Authority issued on Jun. 19, 2008 in connection with PCT application No. PCT/US05/25584, which corresponds to U.S. Appl. No. 10/898,220.Applicant
- Final Office Action issued by the U.S. Patent Office on Jun. 26, 2008 in connection with related U.S. Appl. No. 10/898,220.Applicant
- International Search Report and Written Opinion of the International Searching Authority issued on Jun. 30, 2008 in connection with PCT application No. PCT/US07/21351, which corresponds to U.S. Appl. No. 11/905,980.Applicant
- International Search Report and Written Opinion of the International Searching Authority issued on Jul. 2, 2008 in connection with PCT application No. PCT/US08/02454, which corresponds to U.S. Appl. No. 11/711,876.Applicant
- International Search Report and Written Opinion of the International Searching Authority issued on Jul. 7, 2008 in connection with PCT application No. PCT/US06/43820, which corresponds to U.S. Appl. No. 11/272,035.Applicant
- Final Office Action issued by the U.S. Patent Office on Jul. 17, 2008 in connection with related U.S. Appl. No. 10/843,459.Applicant
- Final Office Action issued by the U.S. Patent Office on Aug. 6, 2008 in connection with related U.S. Appl. No. 10/843,375.Applicant
- Notice of Allowance issued by the U.S. Patent Office on Aug. 18, 2008 in connection with related U.S. Appl. No. 11/272,033.Applicant
- International Search Report and Written Opinion of the International Searching Authority issued on Aug. 18, 2008 in connection with PCT application No. PCT/US08/05466, which corresponds to U.S. Appl. No. 12/149,196.Applicant
- Final Office Action issued by the U.S. Patent Office on Aug. 19, 2008 in connection with related U.S. Appl. No. 10/843,373.Applicant
- Final Office Action issued by the U.S. Patent Office on Aug. 20, 2008 in connection with related U.S. Appl. No. 10/843,353.Applicant
- International Search Report and Written Opinion of the International Searching Authority dated Oct. 9, 2007 in corresponding patent application No. PCT/US06/43800.Applicant
- Office Action issued by the U.S. Patent Office on Oct. 6, 2008 in connection with related U.S. Appl. No. 10/843,374.Applicant
- Notice of Allowance issued by the U.S. Patent Office on Oct. 15, 2008 in connection with related U.S. Appl. No. 10/951,796.Applicant
- Notice of Allowance issued by the U.S. Patent Office on Oct. 21, 2008 in connection with related U.S. Appl. No. 10/843,375.Applicant
- European Office Action issued by the European Patent Office on Nov. 28, 2008 in connection with European patent application No. 07 015 003.2-2413, which corresponds to related U.S. Appl. No. 11/501,776.Applicant
- Office Action issued by the U.S. Patent Office on Dec. 17, 2008 in connection with related U.S. Appl. No. 10/843,398.Applicant
- Office Action issued by the U.S. Patent Office on Jan. 16, 2009 in connection with related U.S. Appl. No. 10/843,353.Applicant
- Office Action issued by the U.S. Patent Office on Jan. 21, 2009 in connection with related U.S. Appl. No. 11/493,934.Applicant
- Notice of Allowance issued by the U.S. Patent Office on Jan. 21, 2009 in connection with related U.S. Appl. No. 10/898,220.Applicant
- Office Action issued by the U.S. Patent Office on Feb. 4, 2009 in connection with related U.S. Appl. No. 10/843,373.Applicant
- Office Action issued by the U.S. Patent Office on Feb. 9, 2009 in connection with related U.S. Appl. No. 10/843,459.Applicant
- International Preliminary Report on Patentability and Written Opinion of the International Searching Authority mailed on Mar. 3, 2009 in connection with PCT application No. PCT/US05/025584, which corresponds to related U.S. Appl. No. 10/898,220.Applicant
- International Preliminary Report on Patentability and Written Opinion of the International Searching Authority mailed on Mar. 17, 2009 in connection with corresponding PCT application No. PCT/US06/43820, which corresponds to related U.S. Appl. No. 11/272,035.Applicant
- Office Action issued by the U.S. Patent Office on Jul. 6, 2009 in connection with related U.S. Appl. No. 10/843,459.Applicant
- Office Action issued by the U.S. Patent Office on Jul. 7, 2009 in connection with related U.S. Appl. No. 10/843,398.Applicant
- Office Action issued by the U.S. Patent Office on Jul. 28, 2009 in connection with related U.S. Appl. No. 10/843,353.Applicant
- Office Action issued by the U.S. Patent Office on Jul. 30, 2009 in connection with related U.S. Appl. No. 11/493,934.Applicant
- Office Action issued by the U.S. Patent Office on Aug. 20, 2009 in connection with related U.S. Appl. No. 10/843,374.Applicant
- International Preliminary Report on Patentability mailed on Sep. 11, 2009 in connection with PCT application No. PCT/US08/002454, which corresponds to U.S. Appl. No. 11/711,876.Applicant
- Advisory Action issued by the U.S. Patent Office on Sep. 29, 2009 in connection with related U.S. Appl. No. 10/843,459.Applicant
- European Search Report issued by the European Patent Office on Oct. 12, 2009 in connection with European patent application No. 05773501.1-2201, which corresponds to related U.S. Appl. Nos. 10/898,220, 11/785,609 and 12/010,900.Applicant
- Final Office Action issued by the U.S. Patent Office on Oct. 29, 2009 in connection with related U.S. Appl. No. 11/501,776.Applicant
- International Preliminary Report on Patentability mailed on Nov. 12, 2009 in connection with PCT application No. PCT/US08/005466, which corresponds to U.S. Appl. No. 12/149,196.Applicant
- Advisory Action issued by the U.S. Patent Office on Dec. 2, 2009 in connection with related U.S. Appl. No. 10/843,398.Applicant
- Notice of Allowance issued by the U.S. Patent Office on Dec. 8, 2009 in connection with related U.S. Appl. No. 11/501,776.Applicant
- Final Office Action issued by the U.S. Patent Office on Dec. 9, 2009 in connection with related U.S. Appl. No. 11/272,035.Applicant
- Office Action issued by the U.S. Patent Office on Dec. 17, 2009 in connection with related U.S. Appl. No. 11/493,934.Applicant
- Full Band and Matrix Algorithms (Jun. 9, 2004), http://web.archive.org/web20040109154658/http://www.netlib.org/utk/Isi/pcwLSI/text/node150.html.Applicant
- International Preliminary Report on Patentability mailed on Apr. 7, 2009 in connection with PCT application No. PCT/US07/021351, which corresponds to U.S. Appl. No. 11/905/980.Applicant
- Office Action issued by the U.S. Patent Office on Apr. 28, 2009 in connection with related U.S. Appl. No. 11/501,776.Applicant
- Final Office Action issued by the U.S. Patent Office on May 13, 2009 in connection with related U.S. Appl. No. 10/843,374.Applicant
- International Search Report and Written Opinion of the International Searching Authority mailed on May 27, 2009 in connection with PCT application No. PCT/US09/02210, which corresponds to U.S. Appl. No. 12/230,338.Applicant
- Office Action issued by the U.S. Patent Office on Jun. 1, 2009 in connection with related U.S. Appl. No. 11/272,035.Applicant
- Notice of Allowance issued by the U.S. Patent Office on Jun. 11, 2009 in connection with related U.S. Appl. No. 10/843,373.Applicant
- Office Action issued by the U.S. Patent Office on Jun. 23, 2009 in connection with related U.S. Appl. No. 11/785,609.Applicant
- R. Gula, “Passive Vulnerability Detection. Techniques to passively find network security vulnerabilities,” Sep. 9, 1999 (5 pp.).Applicant
- R.P. Lippmann et al., “Passive Operating System Identification from TCP/IP Packet Headers,” Proceedings Workshop on Data Mining for Computer Security (DMSEC), Nov. 2003 (10 pp.).Applicant
- N. Brownlee, et al., “Methodology for Passive Analysis of a University Internet Link,” PAM2001 Passive and Active Measurement Workshop, Apr. 2001 (7 pp.).Applicant
- Notice of Allowance issued by the U.S. Patent Office on Jan. 7, 2010 in connection with related U.S. Appl. No. 10/843,353.Applicant
- Notice of Allowance issued by the U.S. Patent Office on Jan. 8, 2010 in connection with related U.S. Appl. No. 10/843,373.Applicant
- Office Action issued by the European Patent Office on Jan. 15, 2010 in connection with European patent application No. 05773501.1 -2201, which corresponds to related U.S. Appl. Nos. 10/898,220, 11/785,609 and 12/010,900.Applicant
- Advisory Action issued by the U.S. Patent Office on Feb. 24, 2010 in connection with related U.S. Appl. No. 11/272,035.Applicant
- Office Action issued by the U.S. Patent Office on Mar. 22, 2010 in connection with related U.S. Appl. No. 11/493,934.Applicant
- Notice of Allowance issued by the U.S. Patent Office on Mar. 5, 2010 in connection with related U.S. Appl. No. 11/785,609.Applicant
- Final Office Action issued by the U.S. Patent Office on Mar. 17, 2010 in connection with related U.S. Appl. No. 10/843,374.Applicant
- Office Action issued by the U.S. Patent Office on Mar. 16, 2010 in connection with related U.S. Appl. No. 11/272,035.Applicant
- International Search Report and Written Opinion of the International Searching Authority issued on Mar. 16, 2010 in connection with PCT application no. PCT/US09/59965, which corresponds to U.S. Appl. No. 12/575,612.Applicant