Patent Grant
10965702
The present invention relates generally to network monitoring, and more particularly, but not exclusively, to monitoring networks in a distributed network monitoring environment.
On most computer networks, bits of data arranged in bytes are packaged into collections of bytes called packets. These packets are generally communicated between computing devices over networks in a wired or wireless manner. A suite of communication protocols is typically employed to communicate between at least two endpoints over one or more networks. The protocols are typically layered on top of one another to form a protocol stack. One model for a network communication protocol stack is the Open Systems Interconnection (OSI) model, which defines seven layers of different protocols that cooperatively enable communication over a network. The OSI model layers are arranged in the following order: Physical (1), Data Link (2), Network (3), Transport (4), Session (5), Presentation (6), and Application (7).
Another model for a network communication protocol stack is the Internet Protocol (IP) model, which is also known as the Transmission Control Protocol/Internet Protocol (TCP/IP) model. The TCP/IP model is similar to the OSI model except that it defines four layers instead of seven. The TCP/IP model's four layers for network communication protocol are arranged in the following order: Link (1), Internet (2), Transport (3), and Application (4). To reduce the number of layers from four to seven, the TCP/IP model collapses the OSI model's Application, Presentation, and Session layers into its Application layer. Also, the OSI's Physical layer is either assumed or is collapsed into the TCP/IP model's Link layer. Although some communication protocols may be listed at different numbered or named layers of the TCP/IP model versus the OSI model, both of these models describe stacks that include basically the same protocols. For example, the TCP protocol is listed on the fourth layer of the OSI model and on the third layer of the TCP/IP model. To assess and troubleshoot communicated packets and protocols over a network, different types of network monitors can be employed. One type of network monitor, a “packet sniffer” may be employed to generally monitor and record packets of data as they are communicated over a network. Some packet sniffers can display data included in each packet and provide statistics regarding a monitored stream of packets. Also, some types of network monitors are referred to as “protocol analyzers” in part because they can provide additional analysis of monitored and recorded packets regarding a type of network, communication protocol, or application.
Generally, packet sniffers and protocol analyzers passively monitor network traffic without participating in the communication protocols. In some instances, they receive a copy of each packet on a particular network segment or VLAN from one or more members of the network segment. They may receive these packet copies through a port mirror on a managed Ethernet switch, e.g., a Switched Port Analyzer (SPAN) port, a Roving Analysis Port (RAP), or the like, or combinations thereof. Port mirroring enables analysis and debugging of network communications. Port mirroring can be performed for inbound or outbound traffic (or both) on single or multiple interfaces. In other instances, packet copies may be provided to the network monitors from a specialized network tap or from a software entity running on the client or server. In virtual environments, port mirroring may be performed on a virtual switch that is incorporated within the hypervisor.
In complex networks, network activity, such as, requests or responses directed to one device, server, service, or application may be responsible for causing related activity that may be associated with other devices, servers, services, or applications in the network. Correlating activity that is associated with different devices, servers, services, or applications may be difficult absent disadvantageous or intrusive monitoring mechanisms. Thus, it is with respect to these considerations and others that the present invention has been made.
Non-limiting and non-exhaustive embodiments of the present innovations are described with reference to the following drawings. In the drawings, like reference numerals refer to like parts throughout the various figures unless otherwise specified. For a better understanding of the described innovations, reference will be made to the following Detailed Description of Various Embodiments, which is to be read in association with the accompanying drawings, wherein:
Various embodiments now will be described more fully hereinafter with reference to the accompanying drawings, which form a part hereof, and which show, by way of illustration, specific exemplary embodiments by which the invention may be practiced. The embodiments may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein; rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the embodiments to those skilled in the art. Among other things, the various embodiments may be methods, systems, media or devices. Accordingly, the various embodiments may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. The following detailed description is, therefore, not to be taken in a limiting sense.
Throughout the specification and claims, the following terms take the meanings explicitly associated herein, unless the context clearly dictates otherwise. The phrase “in one embodiment” as used herein does not necessarily refer to the same embodiment, though it may. Furthermore, the phrase “in another embodiment” as used herein does not necessarily refer to a different embodiment, although it may. Thus, as described below, various embodiments may be readily combined, without departing from the scope or spirit of the invention.
In addition, as used herein, the term “or” is an inclusive “or” operator, and is equivalent to the term “and/or,” unless the context clearly dictates otherwise. The term “based on” is not exclusive and allows for being based on additional factors not described, unless the context clearly dictates otherwise. In addition, throughout the specification, the meaning of “a,” “an,” and “the” include plural references. The meaning of “in” includes “in” and “on.”
For example embodiments, the following terms are also used herein according to the corresponding meaning, unless the context clearly dictates otherwise.
As used herein the term, “engine” refers to logic embodied in hardware or software instructions, which can be written in a programming language, such as C, C++, Objective-C, COBOL, Java™, PHP, Perl, JavaScript, Ruby, VBScript, Microsoft .NET™ languages such as C #, or the like. An engine may be compiled into executable programs or written in interpreted programming languages. Software engines may be callable from other engines or from themselves. Engines described herein refer to one or more logical modules that can be merged with other engines or applications, or can be divided into sub-engines. The engines can be stored in non-transitory computer-readable medium or computer storage device and be stored on and executed by one or more general purpose computers, thus creating a special purpose computer configured to provide the engine.
As used herein, the term “session” refers to a semi-permanent interactive packet interchange between two or more communicating endpoints, such as network devices. A session is set up or established at a certain point in time, and torn down at a later point in time. An established communication session may involve more than one message in each direction. A session may have stateful communication where at least one of the communicating network devices saves information about the session history to be able to communicate. A session may also provide stateless communication, where the communication consists of independent requests with responses between the endpoints. An established session is the basic requirement to perform a connection-oriented communication. A session also is the basic step to transmit in connectionless communication modes.
As used herein, the terms “network connection,” and “connection” refer to communication sessions with a semi-permanent connection for interactive packet interchange between two or more communicating endpoints, such as network devices. The connection may be established before application data is transferred, and where a stream of data is delivered in the same or different order than it was sent. The alternative to connection-oriented transmission is connectionless communication. For example, the datagram mode of communication used by the Internet Protocol (IP) and the Universal Datagram Protocol (UDP) may deliver packets out of order, since different packets may be routed independently and could be delivered over different paths. Packets associated with a TCP protocol connection may also be routed independently and could be delivered over different paths. However, for TCP connections the network communication system may provide the packets to application endpoints in the correct order.
Connection-oriented communication may be a packet-mode virtual circuit connection. For example, a transport layer virtual circuit protocol such as the TCP protocol can deliver packets of data in order although the lower layer switching is connectionless. A connection-oriented transport layer protocol such as TCP can also provide connection-oriented communications over connectionless communication. For example, if TCP is based on a connectionless network layer protocol (such as IP), this TCP/IP protocol can then achieve in-order delivery of a byte stream of data, by means of segment sequence numbering on the sender side, packet buffering and data packet reordering on the receiver side. Alternatively, the virtual circuit connection may be established in a datalink layer or network layer switching mode, where all data packets belonging to the same traffic stream are delivered over the same path, and traffic flows are identified by some connection identifier rather than by complete routing information, which enables fast hardware based switching.
As used herein, the terms “session flow” and “network flow” refer to one or more network packets or a stream of network packets that are communicated in a session that is established between at least two endpoints, such as two network devices. In one or more of the various embodiments, flows may be useful if one or more of the endpoints of a session may be behind a network traffic management device, such as a firewall, switch, router, load balancer, or the like. In one or more of the various embodiments, such flows may be used to ensure that the packets sent between the endpoints of a flow may be routed appropriately.
Typically, establishing a TCP based connection between endpoints begins with the execution of an initialization protocol and creates a single bi-directional flow between two endpoints, e.g., one direction of flow going from endpoint A to endpoint B, the other direction of the flow going from endpoint B to endpoint A, where each endpoint is at least identified by an IP address and a TCP port.
Also, some protocols or network applications may establish a separate flow for control information that enables management of at least one or more flows between two or more endpoints. Further, in some embodiments, network flows may be half-flows that may be unidirectional.
As used herein, the terms “tuple,” or “tuple information” refer to a set of values that identify a source and destination of a network packet, which may, under some circumstances, be a part of a network connection. In one embodiment, a tuple may include a source Internet Protocol (IP) address, a destination IP address, a source port number, a destination port number, virtual LAN segment identifier (VLAN ID), tunnel identifier, routing interface identifier, physical interface identifier, or a protocol identifier. Tuples may be used to identify network flows (e.g., connection flows).
As used herein the term “related flows,” or “related network flows” as used herein are network flows that while separate they are operating cooperatively. For example, some protocols, such as, FTP, SIP, RTP, VOIP, custom protocols, or the like, may provide control communication over one network flow and data communication over other network flows. Further, configuration rules may define one or more criteria that are used to recognize that two or more network flows should be considered related flows. For example, configuration rules may define that flows containing a particular field value should be grouped with other flows having the same field value, such as, a cookie value, or the like.
As used herein, the terms “network monitor”, “network monitoring computer”, or “NMC” refer to an application (software, hardware, or some combination thereof) that is arranged to monitor or record flows of packets in a session that are communicated between at least two endpoints over at least one network. The NMC can provide information for assessing different aspects of these monitored flows. In one or more embodiments, the NMC may passively monitor network packet traffic without participating in the communication protocols. This monitoring may be performed for a variety of reasons, including troubleshooting and proactive remediation, anomaly detection, end-user experience monitoring, SLA monitoring, capacity planning, application lifecycle management, infrastructure change management, infrastructure optimization, business intelligence, security, and regulatory compliance. The NMC can receive network communication for monitoring through a variety of means including network taps, wireless receivers, port mirrors or directed tunnels from network switches, clients or servers including the endpoints themselves, or other infrastructure devices. In at least some of the various embodiments, the NMC may receive a copy of each packet on a particular network segment or virtual local area network (VLAN). Also, for at least some of the various embodiments, they may receive these packet copies through a port mirror on a managed Ethernet switch, e.g., a Switched Port Analyzer (SPAN) port, a Roving Analysis Port (RAP), or the like, or combination thereof. Port mirroring enables analysis and debugging of network communications. Port mirroring can be performed for inbound or outbound traffic (or both) on single or multiple interfaces.
The NMC may track network connections from and to end points such as a client or a server. The NMC may also extract information from the packets including protocol information at various layers of the communication protocol stack. The NMC may reassemble or reconstruct the stream of data exchanged between the endpoints. The NMC may perform decryption of the payload at various layers of the protocol stack. The NMC may passively monitor the network traffic or it may participate in the protocols as a proxy. The NMC may attempt to classify the network traffic according to communication protocols that are used.
The NMC may also perform one or more actions for classifying protocols that may be a necessary precondition for application classification. While some protocols run on well-known ports, others do not. Thus, even if there is traffic on a well-known port, it is not necessarily the protocol generally understood to be assigned to that port. As a result, the NMC may perform protocol classification using one or more techniques, such as, signature matching, statistical analysis, traffic analysis, and other heuristics. In some cases, the NMC may use adaptive protocol classification techniques where information used to classify the protocols may be accumulated or applied over time to further classify the observed protocols. In some embodiments, NMCs may be arranged to employ stateful analysis. Accordingly, for each supported protocols, an NMC may use network packet payload data to drive a state machine that mimics the protocol state changes in the client/server flows being monitored. The NMC may categorize the traffic where categories might include file transfers, streaming audio, streaming video, database access, interactive, gaming, and the like. The NMC may attempt to determine whether the traffic corresponds to known communications protocols, such as HTTP, FTP, SMTP, RTP, TDS, TCP, IP, and the like.
In addition, in one or more of the various embodiments, NMCs or NMC functionality may be implemented using hardware or software based proxy devices that may be arranged to intercept network traffic in the monitored networks rather than being restricted to passive (pass through) monitoring.
As used herein, the terms “layer” and “model layer” refer to a layer of one or more communication protocols in a stack of communication protocol layers that are defined by a model, such as the OSI model and the TCP/IP (IP) model. The OSI model defines seven layers and the TCP/IP model defines four layers of communication protocols.
For example, at the OSI model's lowest or first layer (Physical), streams of electrical/light/radio impulses (bits) are communicated between computing devices over some type of media, such as cables, network interface cards, radio wave transmitters, and the like. At the next or second layer (Data Link), bits are encoded into packets and packets are also decoded into bits. The Data Link layer also has two sub-layers, the Media Access Control (MAC) sub-layer and the Logical Link Control (LLC) sub-layer. The MAC sub-layer controls how a computing device gains access to the data and permission to transmit it. The LLC sub-layer controls frame synchronization, flow control and error checking. At the third layer (Network), logical paths are created, known as virtual circuits, to communicated data from node to node. Routing, forwarding, addressing, internetworking, error handling, congestion control, and packet sequencing are functions of the Network layer. At the fourth layer (Transport), transparent transfer of data between end computing devices, or hosts, is provided. The Transport layer is responsible for end to end recovery and flow control to ensure complete data transfer over the network.
At the fifth layer (Session) of the OSI model, connections between applications are established, managed, and terminated. The Session layer sets up, coordinates, and terminates conversations, exchanges, and dialogues between applications at each end of a connection. At the sixth layer (Presentation), independence from differences in data representation, e.g., encryption, is provided by translating from application to network format and vice versa. Generally, the Presentation layer transforms data into the form that the protocols at the Application layer (7) can accept. For example, the Presentation layer generally handles the formatting and encrypting/decrypting of data that is communicated across a network.
At the top or seventh layer (Application) of the OSI model, application and end user processes are supported. For example, communication partners may be identified, quality of service can be identified, user authentication and privacy may be considered, and constraints on data syntax can be identified. Generally, the Application layer provides services for file transfer, messaging, and displaying data. Protocols at the Application layer include FTP, HTTP, and Telnet.
To reduce the number of layers from seven to four, the TCP/IP model collapses the OSI model's Application, Presentation, and Session layers into its Application layer. Also, the OSI's Physical layer is either assumed or may be collapsed into the TCP/IP model's Link layer. Although some communication protocols may be listed at different numbered or named layers of the TCP/IP model versus the OSI model, both of these models describe stacks that include basically the same protocols.
As used herein, the term “entity” refers to an actor in the monitored network. Entities may include applications, services, programs, processes, network devices, network computers, client computers, or the like, operating in the monitored network. For example, individual entities may include, web clients, web servers, database clients, database servers, mobile app clients, payment processors, groupware clients, groupware services, or the like. In some cases, multiple entities may co-exist on or in the same network computer, process, application, compute container, or cloud compute instance.
As used herein, the term “observation port” refers to network taps, wireless receivers, port mirrors or directed tunnels from network switches, clients or servers, virtual machines, cloud computing instances, other network infrastructure devices or processes, or the like, or combination thereof. Observation ports may provide a copy of each network packet included in monitored wire traffic or monitored network traffic on a particular network segment or virtual local area network (VLAN). Also, for one or more of the various embodiments, observation ports may provide NMCs network packet copies through a port mirror on a managed Ethernet switch, e.g., a Switched Port Analyzer (SPAN) port, or a Roving Analysis Port (RAP).
As used herein the term, “injection attack” refers to a class of network borne attacks that usually involve the deliberate inclusion of untrusted, malicious or malformed code in inputs provided through otherwise trusted interfaces or APIs to a service in the hopes of causing degradation or exploitation of the targeted services or computers. In some cases, the malformed inputs may include computer executable code (or other data that a target may interpret as code or computer readable instructions) that an attacker hopes will be involuntarily executed on the targeted services or computers. For example, a SQL injection attack (described in more detail in the examples below) usually involves “injecting” untrusted SQL code into a request that may be provided to a server, in the hopes that the untrusted SQL code will be executed. There are many variants of injection attacks share the characteristic of attempting to inject untrusted content or computer readable instructions into a target via an otherwise trusted pathway.
As used herein, the term “correlation information” refers to information associated with one or more requests that may be determined from monitored network traffic. Correlation information may include, communication protocol information (e.g., one or more TCP field values, or the like), parameter or parameter values, URLs, some or all of the tuple information, or the like. In some cases, correlation information may include the some or all of payload or some or all of the network packet(s) associated with a request. Further, NMCs may associate different kinds of requests with different correlation information that includes different metrics, characteristics, or values. NMCs may be arranged to determine some or all of the correlation information based on configuration information.
As used herein the term, “configuration information” refers to information that may include rule based policies, pattern matching instructions (e.g., regular expressions), templates, scripts (e.g., computer readable instructions), or the like, that may be provided from various sources, including, configuration files, databases, user input, built-in defaults, or the like, or combination thereof.
The following briefly describes embodiments of the invention in order to provide a basic understanding of some aspects of the invention. This brief description is not intended as an extensive overview. It is not intended to identify key or critical elements, or to delineate or otherwise narrow the scope. Its purpose is merely to present some concepts in a simplified form as a prelude to the more detailed description that is presented later.
Briefly stated, various embodiments are directed to monitoring network traffic using one or more network computers or network monitoring computers (NMCs). In one or more of the various embodiments, NMCs may be arranged to determine one or more requests that may be provided to a server based on a first portion of network traffic.
In one or more of the various embodiments, one or more suspicious requests may be determined based on one or more characteristics of the one or more provided requests. In one or more of the various embodiments, the one or more characteristics of the one or more suspicious requests may include, one or more of contents of the one or more suspicious requests, a sender of the one or more suspicious requests, a target of the one or more suspicious requests, tuple information, time of day, network utilization, or a rate of requests sent or received.
In one or more of the various embodiments, one or more characteristics of the one or more suspicious requests maybe employed to provide correlation information associated with at least the one or more suspicious requests.
In one or more of the various embodiments, one or more dependent actions performed by the server may be determined.
In one or more of the various embodiments, one or more characteristics of the one or more dependent actions may be determined to evaluate the one or more dependent actions.
In one or more of the various embodiments, the result of the one or more dependent actions performed by the server maybe determined. In one or more of the various embodiments, determining the one or more dependent actions may include comparing identifier information in a payload of one or more actions with other identifier information included in a payload of the one or more requests such that an affirmative result indicates that the one or more actions are the one or more dependent actions.
In one or more of the various embodiments, in response to determining anomalous activity associated with the evaluation of the one or more dependent actions based on one or more correlations with the one or more suspicious requests, one or more reports that include information associated with the anomalous activity may be provided. In one or more of the various embodiments, determining the anomalous activity may include: determining one or more inconsistencies associated with the one or more suspicious requests, or the one or more dependent requests; and further determining the anomalous activity based on the one or more determined inconsistencies. Also, in one or more of the various embodiments, determining the anomalous activity may include: determining malformed information that may be included in the one or more dependent actions based on an association with other malformed information that is included in the one or more suspicious requests; and further determining the anomalous activity based on one or more of the malformed information or the other malformed information.
In one or more of the various embodiments, a source of the anomalous activity may be determined based on one or more of the correlation information, the one or more suspicious requests, the one or more dependent actions, or the one or more results associated with the one or more dependent actions. And, in one or more of the various embodiments, the source of the anomalous activity may be included in the one or more reports.
In one or more of the various embodiments, the anomalous activity may include an injection attack based on malformed information included in the one or more suspicious requests that may be associated with malformed structured query language (SQL) instructions that may be included in the one or more dependent actions.
In one or more of the various embodiments, the anomalous activity may include an injection attack that may be based on malformed information included in the one or more suspicious requests that may be associated with one or more of one or more malformed shell instructions, malformed command instructions, or malformed interprocess communication associated with the one or more dependent actions.
Illustrated Operating Environment
At least one embodiment of client computers 102-105 is described in more detail below in conjunction with
Computers that may operate as client computer 102 may include computers that typically connect using a wired or wireless communications medium such as personal computers, multiprocessor systems, microprocessor-based or programmable electronic devices, network PCs, or the like. In some embodiments, client computers 102-105 may include virtually any portable computer capable of connecting to another computer and receiving information such as, laptop computer 103, mobile computer 104, tablet computers 105, or the like. However, portable computers are not so limited and may also include other portable computers such as cellular telephones, display pagers, radio frequency (RF) devices, infrared (IR) devices, Personal Digital Assistants (PDAs), handheld computers, wearable computers, integrated devices combining one or more of the preceding computers, or the like. As such, client computers 102-105 typically range widely in terms of capabilities and features. Moreover, client computers 102-105 may access various computing applications, including a browser, or other web-based application.
A web-enabled client computer may include a browser application that is configured to send requests and receive responses over the web. The browser application may be configured to receive and display graphics, text, multimedia, and the like, employing virtually any web-based language. In one embodiment, the browser application is enabled to employ JavaScript, HyperText Markup Language (HTML), eXtensible Markup Language (XML), JavaScript Object Notation (JSON), Cascading Style Sheets (CSS), or the like, or combination thereof, to display and send a message. In one embodiment, a user of the client computer may employ the browser application to perform various activities over a network (online). However, another application may also be used to perform various online activities.
Client computers 102-105 also may include at least one other client application that is configured to receive or send content between another computer. The client application may include a capability to send or receive content, or the like. The client application may further provide information that identifies itself, including a type, capability, name, and the like. In one embodiment, client computers 102-105 may uniquely identify themselves through any of a variety of mechanisms, including an Internet Protocol (IP) address, a phone number, Mobile Identification Number (MIN), an electronic serial number (ESN), a client certificate, or other device identifier. Such information may be provided in one or more network packets, or the like, sent between other client computers, application server computer 116, network monitoring computer 118, or other computers.
Client computers 102-105 may further be configured to include a client application that enables an end-user to log into an end-user account that may be managed by another computer, such as application server computer 116, network monitoring computer 118, or the like. Such an end-user account, in one non-limiting example, may be configured to enable the end-user to manage one or more online activities, including in one non-limiting example, project management, software development, system administration, configuration management, search activities, social networking activities, browse various websites, communicate with other users, or the like. Further, client computers may be arranged to enable users to provide configuration information, policy information, or the like, to network monitoring computer 118. Also, client computers may be arranged to enable users to display reports, interactive user-interfaces, results provided by network monitor computer 118, or the like. Further, in some embodiments, client computers may be arranged to receive or host one or more investigative agents that may be gathering information associated with an anomaly that has been detected in the networks.
Wireless network 108 is configured to couple client computers 103-105 and its components with network 110. Wireless network 108 may include any of a variety of wireless sub-networks that may further overlay stand-alone ad-hoc networks, and the like, to provide an infrastructure-oriented connection for client computers 103-105. Such sub-networks may include mesh networks, Wireless LAN (WLAN) networks, cellular networks, and the like. In one embodiment, the system may include more than one wireless network.
Wireless network 108 may further include an autonomous system of terminals, gateways, routers, and the like connected by wireless radio links, and the like. These connectors may be configured to move freely and randomly and organize themselves arbitrarily, such that the topology of wireless network 108 may change rapidly.
Wireless network 108 may further employ a plurality of access technologies including 2nd (2G), 3rd (3G), 4th (4G) 5th (5G) generation radio access for cellular systems, WLAN, Wireless Router (WR) mesh, and the like. Access technologies such as 2G, 3G, 4G, 5G, and future access networks may enable wide area coverage for mobile computers, such as client computers 103-105 with various degrees of mobility. In one non-limiting example, wireless network 108 may enable a radio connection through a radio network access such as Global System for Mobil communication (GSM), General Packet Radio Services (GPRS), Enhanced Data GSM Environment (EDGE), code division multiple access (CDMA), time division multiple access (TDMA), Wideband Code Division Multiple Access (WCDMA), High Speed Downlink Packet Access (HSDPA), Long Term Evolution (LTE), and the like. In essence, wireless network 108 may include virtually any wireless communication mechanism by which information may travel between client computers 103-105 and another computer, network, a cloud-based network, a cloud instance, or the like.
Network 110 is configured to couple network computers with other computers, including, application server computer 116, network monitoring computer 118, client computers 102-105 through wireless network 108, or the like. Network 110 is enabled to employ any form of computer readable media for communicating information from one electronic device to another. Also, network 110 can include the Internet in addition to local area networks (LANs), wide area networks (WANs), direct connections, such as through a universal serial bus (USB) port, Ethernet port, other forms of computer-readable media, or any combination thereof. On an interconnected set of LANs, including those based on differing architectures and protocols, a router acts as a link between LANs, enabling messages to be sent from one to another. In addition, communication links within LANs typically include twisted wire pair or coaxial cable, while communication links between networks may utilize analog telephone lines, full or fractional dedicated digital lines including T1, T2, T3, and T4, or other carrier mechanisms including, for example, E-carriers, Integrated Services Digital Networks (ISDNs), Digital Subscriber Lines (DSLs), wireless links including satellite links, or other communications links known to those skilled in the art. Moreover, communication links may further employ any of a variety of digital signaling technologies, including without limit, for example, DS-0, DS-1, DS-2, DS-3, DS-4, OC-3, OC-12, OC-48, or the like. Furthermore, remote computers and other related electronic devices could be remotely connected to either LANs or WANs via a modem and temporary telephone link. In one embodiment, network 110 may be configured to transport information using one or more network protocols, such Internet Protocol (IP).
Additionally, communication media typically embodies computer readable instructions, data structures, program modules, or other transport mechanism and includes any information non-transitory delivery media or transitory delivery media. By way of example, communication media includes wired media such as twisted pair, coaxial cable, fiber optics, wave guides, and other wired media and wireless media such as acoustic, RF, infrared, and other wireless media.
One embodiment of application server computer 116 is described in more detail below in conjunction with
Illustrative Client Computer
Client computer 200 may include processor 202 in communication with memory 204 via bus 228. Client computer 200 may also include power supply 230, network interface 232, audio interface 256, display 250, keypad 252, illuminator 254, video interface 242, input/output interface 238, haptic interface 264, global positioning systems (GPS) receiver 258, open air gesture interface 260, temperature interface 262, camera(s) 240, projector 246, pointing device interface 266, processor-readable stationary storage device 234, and processor-readable removable storage device 236. Client computer 200 may optionally communicate with a base station (not shown), or directly with another computer. And in one embodiment, although not shown, a gyroscope may be employed within client computer 200 for measuring or maintaining an orientation of client computer 200.
Power supply 230 may provide power to client computer 200. A rechargeable or non-rechargeable battery may be used to provide power. The power may also be provided by an external power source, such as an AC adapter or a powered docking cradle that supplements or recharges the battery.
Network interface 232 includes circuitry for coupling client computer 200 to one or more networks, and is constructed for use with one or more communication protocols and technologies including, but not limited to, protocols and technologies that implement any portion of the OSI model for mobile communication (GSM), CDMA, time division multiple access (TDMA), UDP, TCP/IP, SMS, MMS, GPRS, WAP, UWB, WiMax, SIP/RTP, GPRS, EDGE, WCDMA, LTE, UMTS, OFDM, CDMA2000, EV-DO, HSDPA, or any of a variety of other wireless communication protocols. Network interface 232 is sometimes known as a transceiver, transceiving device, or network interface card (NIC).
Audio interface 256 may be arranged to produce and receive audio signals such as the sound of a human voice. For example, audio interface 256 may be coupled to a speaker and microphone (not shown) to enable telecommunication with others or generate an audio acknowledgement for some action. A microphone in audio interface 256 can also be used for input to or control of client computer 200, e.g., using voice recognition, detecting touch based on sound, and the like.
Display 250 may be a liquid crystal display (LCD), gas plasma, electronic ink, light emitting diode (LED), Organic LED (OLED) or any other type of light reflective or light transmissive display that can be used with a computer. Display 250 may also include a touch interface 244 arranged to receive input from an object such as a stylus or a digit from a human hand, and may use resistive, capacitive, surface acoustic wave (SAW), infrared, radar, or other technologies to sense touch or gestures.
Projector 246 may be a remote handheld projector or an integrated projector that is capable of projecting an image on a remote wall or any other reflective object such as a remote screen.
Video interface 242 may be arranged to capture video images, such as a still photo, a video segment, an infrared video, or the like. For example, video interface 242 may be coupled to a digital video camera, a web-camera, or the like. Video interface 242 may comprise a lens, an image sensor, and other electronics. Image sensors may include a complementary metal-oxide-semiconductor (CMOS) integrated circuit, charge-coupled device (CCD), or any other integrated circuit for sensing light.
Keypad 252 may comprise any input device arranged to receive input from a user. For example, keypad 252 may include a push button numeric dial, or a keyboard. Keypad 252 may also include command buttons that are associated with selecting and sending images.
Illuminator 254 may provide a status indication or provide light. Illuminator 254 may remain active for specific periods of time or in response to event messages. For example, when illuminator 254 is active, it may backlight the buttons on keypad 252 and stay on while the client computer is powered. Also, illuminator 254 may backlight these buttons in various patterns when particular actions are performed, such as dialing another client computer. Illuminator 254 may also cause light sources positioned within a transparent or translucent case of the client computer to illuminate in response to actions.
Further, client computer 200 may also comprise hardware security module (HSM) 268 for providing additional tamper resistant safeguards for generating, storing or using security/cryptographic information such as, keys, digital certificates, passwords, passphrases, two-factor authentication information, or the like. In some embodiments, hardware security module may be employed to support one or more standard public key infrastructures (PKI), and may be employed to generate, manage, or store keys pairs, or the like. In some embodiments, HSM 268 may be a stand-alone computer, in other cases, HSM 268 may be arranged as a hardware card that may be added to a client computer.
Client computer 200 may also comprise input/output interface 238 for communicating with external peripheral devices or other computers such as other client computers and network computers. The peripheral devices may include an audio headset, virtual reality headsets, display screen glasses, remote speaker system, remote speaker and microphone system, and the like. Input/output interface 238 can utilize one or more technologies, such as Universal Serial Bus (USB), Infrared, WiFi, WiMax, Bluetooth™, and the like.
Input/output interface 238 may also include one or more sensors for determining geolocation information (e.g., GPS), monitoring electrical power conditions (e.g., voltage sensors, current sensors, frequency sensors, and so on), monitoring weather (e.g., thermostats, barometers, anemometers, humidity detectors, precipitation scales, or the like), or the like. Sensors may be one or more hardware sensors that collect or measure data that is external to client computer 200.
Haptic interface 264 may be arranged to provide tactile feedback to a user of the client computer. For example, the haptic interface 264 may be employed to vibrate client computer 200 in a particular way when another user of a computer is calling. Temperature interface 262 may be used to provide a temperature measurement input or a temperature changing output to a user of client computer 200. Open air gesture interface 260 may sense physical gestures of a user of client computer 200, for example, by using single or stereo video cameras, radar, a gyroscopic sensor inside a computer held or worn by the user, or the like. Camera 240 may be used to track physical eye movements of a user of client computer 200.
GPS transceiver 258 can determine the physical coordinates of client computer 200 on the surface of the Earth, which typically outputs a location as latitude and longitude values. GPS transceiver 258 can also employ other geo-positioning mechanisms, including, but not limited to, triangulation, assisted GPS (AGPS), Enhanced Observed Time Difference (E-OTD), Cell Identifier (CI), Service Area Identifier (SAI), Enhanced Timing Advance (ETA), Base Station Subsystem (BSS), or the like, to further determine the physical location of client computer 200 on the surface of the Earth. It is understood that under different conditions, GPS transceiver 258 can determine a physical location for client computer 200. In one or more embodiment, however, client computer 200 may, through other components, provide other information that may be employed to determine a physical location of the client computer, including for example, a Media Access Control (MAC) address, IP address, and the like.
Human interface components can be peripheral devices that are physically separate from client computer 200, allowing for remote input or output to client computer 200. For example, information routed as described here through human interface components such as display 250 or keyboard 252 can instead be routed through network interface 232 to appropriate human interface components located remotely. Examples of human interface peripheral components that may be remote include, but are not limited to, audio devices, pointing devices, keypads, displays, cameras, projectors, and the like. These peripheral components may communicate over a Pico Network such as Bluetooth™, Zigbee™ and the like. One non-limiting example of a client computer with such peripheral human interface components is a wearable computer, which might include a remote pico projector along with one or more cameras that remotely communicate with a separately located client computer to sense a user's gestures toward portions of an image projected by the pico projector onto a reflected surface such as a wall or the user's hand.
A client computer may include web browser application 226 that is configured to receive and to send web pages, web-based messages, graphics, text, multimedia, and the like. The client computer's browser application may employ virtually any programming language, including a wireless application protocol messages (WAP), and the like. In one or more embodiment, the browser application is enabled to employ Handheld Device Markup Language (HDML), Wireless Markup Language (WML), WMLScript, JavaScript, Standard Generalized Markup Language (SGML), HyperText Markup Language (HTML), eXtensible Markup Language (XML), HTML5, and the like.
Memory 204 may include RAM, ROM, or other types of memory. Memory 204 illustrates an example of computer-readable storage media (devices) for storage of information such as computer-readable instructions, data structures, program modules or other data. Memory 204 may store BIOS 208 for controlling low-level operation of client computer 200. The memory may also store operating system 206 for controlling the operation of client computer 200. It will be appreciated that this component may include a general-purpose operating system such as a version of UNIX, or LINUX™, or a specialized client computer communication operating system such as Windows Phone™, or the Symbian® operating system. The operating system may include, or interface with a Java virtual machine module that enables control of hardware components or operating system operations via Java application programs.
Memory 204 may further include one or more data storage 210, which can be utilized by client computer 200 to store, among other things, applications 220 or other data. For example, data storage 210 may also be employed to store information that describes various capabilities of client computer 200. The information may then be provided to another device or computer based on any of a variety of methods, including being sent as part of a header during a communication, sent upon request, or the like. Data storage 210 may also be employed to store social networking information including address books, buddy lists, aliases, user profile information, or the like. Data storage 210 may further include program code, data, algorithms, and the like, for use by a processor, such as processor 202 to execute and perform actions. In one embodiment, at least some of data storage 210 might also be stored on another component of client computer 200, including, but not limited to, non-transitory processor-readable removable storage device 236, processor-readable stationary storage device 234, or even external to the client computer.
Applications 220 may include computer executable instructions which, when executed by client computer 200, transmit, receive, or otherwise process instructions and data. Applications 220 may include, for example, other client applications 224, web browser 226, or the like. Client computers may be arranged to exchange communications, such as, queries, searches, messages, notification messages, event messages, alerts, performance metrics, log data, API calls, or the like, combination thereof, with application servers or network monitoring computers.
Other examples of application programs include calendars, search programs, email client applications, IM applications, SMS applications, Voice Over Internet Protocol (VOIP) applications, contact managers, task managers, transcoders, database programs, word processing programs, security applications, spreadsheet programs, games, search programs, and so forth.
Additionally, in one or more embodiments (not shown in the figures), client computer 200 may include one or more embedded logic hardware devices instead of CPUs, such as, an Application Specific Integrated Circuit (ASIC), Field Programmable Gate Array (FPGA), Programmable Array Logic (PAL), or the like, or combination thereof. The embedded logic hardware devices may directly execute embedded logic to perform actions. Also, in one or more embodiments (not shown in the figures), client computer 200 may include one or more hardware microcontrollers instead of CPUs. In one or more embodiments, the microcontrollers may directly execute their own embedded logic to perform actions and access their own internal memory and their own external Input and Output Interfaces (e.g., hardware pins or wireless transceivers) to perform actions, such as System On a Chip (SOC), or the like.
Illustrative Network Computer
As shown in the figure, network computer 300 includes a processor 302 that may be in communication with a memory 304 via a bus 328. In some embodiments, processor 302 may be comprised of one or more hardware processors, or one or more processor cores. In some cases, one or more of the one or more processors may be specialized processors designed to perform one or more specialized actions, such as, those described herein. Network computer 300 also includes a power supply 330, network interface 332, audio interface 356, display 350, keyboard 352, input/output interface 338, processor-readable stationary storage device 334, and processor-readable removable storage device 336. Power supply 330 provides power to network computer 300.
Network interface 332 includes circuitry for coupling network computer 300 to one or more networks, and is constructed for use with one or more communication protocols and technologies including, but not limited to, protocols and technologies that implement any portion of the Open Systems Interconnection model (OSI model), global system for mobile communication (GSM), code division multiple access (CDMA), time division multiple access (TDMA), user datagram protocol (UDP), transmission control protocol/Internet protocol (TCP/IP), Short Message Service (SMS), Multimedia Messaging Service (MMS), general packet radio service (GPRS), WAP, ultra-wide band (UWB), IEEE 802.16 Worldwide Interoperability for Microwave Access (WiMax), Session Initiation Protocol/Real-time Transport Protocol (SIP/RTP), or any of a variety of other wired and wireless communication protocols. Network interface 332 is sometimes known as a transceiver, transceiving device, or network interface card (NIC). Network computer 300 may optionally communicate with a base station (not shown), or directly with another computer.
Audio interface 356 is arranged to produce and receive audio signals such as the sound of a human voice. For example, audio interface 356 may be coupled to a speaker and microphone (not shown) to enable telecommunication with others or generate an audio acknowledgement for some action. A microphone in audio interface 356 can also be used for input to or control of network computer 300, for example, using voice recognition.
Display 350 may be a liquid crystal display (LCD), gas plasma, electronic ink, light emitting diode (LED), Organic LED (OLED) or any other type of light reflective or light transmissive display that can be used with a computer. In some embodiments, display 350 may be a handheld projector or pico projector capable of projecting an image on a wall or other object.
Network computer 300 may also comprise input/output interface 338 for communicating with external devices or computers not shown in
Also, input/output interface 338 may also include one or more sensors for determining geolocation information (e.g., GPS), monitoring electrical power conditions (e.g., voltage sensors, current sensors, frequency sensors, and so on), monitoring weather (e.g., thermostats, barometers, anemometers, humidity detectors, precipitation scales, or the like), or the like. Sensors may be one or more hardware sensors that collect or measure data that is external to network computer 300. Human interface components can be physically separate from network computer 300, allowing for remote input or output to network computer 300. For example, information routed as described here through human interface components such as display 350 or keyboard 352 can instead be routed through the network interface 332 to appropriate human interface components located elsewhere on the network. Human interface components include any component that allows the computer to take input from, or send output to, a human user of a computer. Accordingly, pointing devices such as mice, styluses, track balls, or the like, may communicate through pointing device interface 358 to receive user input.
GPS transceiver 340 can determine the physical coordinates of network computer 300 on the surface of the Earth, which typically outputs a location as latitude and longitude values. GPS transceiver 340 can also employ other geo-positioning mechanisms, including, but not limited to, triangulation, assisted GPS (AGPS), Enhanced Observed Time Difference (E-OTD), Cell Identifier (CI), Service Area Identifier (SAI), Enhanced Timing Advance (ETA), Base Station Subsystem (BSS), or the like, to further determine the physical location of network computer 300 on the surface of the Earth. It is understood that under different conditions, GPS transceiver 340 can determine a physical location for network computer 300. In one or more embodiment, however, network computer 300 may, through other components, provide other information that may be employed to determine a physical location of the client computer, including for example, a Media Access Control (MAC) address, IP address, and the like.
In at least one of the various embodiments, applications, such as, operating system 306, network monitoring engine 322, inference engine 324, analysis engine 326, anomaly engine 327, web services 329, or the like, may be arranged to employ geo-location information to select one or more localization features, such as, time zones, languages, currencies, calendar formatting, or the like. Localization features may be used when interpreting network traffic, monitoring application protocols, user-interfaces, reports, as well as internal processes or databases. In at least one of the various embodiments, geo-location information used for selecting localization information may be provided by GPS 340. Also, in some embodiments, geolocation information may include information provided using one or more geolocation protocols over the networks, such as, wireless network 108 or network 111.
Memory 304 may include Random Access Memory (RAM), Read-Only Memory (ROM), or other types of memory. Memory 304 illustrates an example of computer-readable storage media (devices) for storage of information such as computer-readable instructions, data structures, program modules or other data. Memory 304 stores a basic input/output system (BIOS) 308 for controlling low-level operation of network computer 300. The memory also stores an operating system 306 for controlling the operation of network computer 300. It will be appreciated that this component may include a general-purpose operating system such as a version of UNIX, or LINUX™, or a specialized operating system such as Microsoft Corporation's Windows® operating system, or the Apple Corporation's IOS® operating system. The operating system may include, or interface with a Java virtual machine module that enables control of hardware components or operating system operations via Java application programs. Likewise, other runtime environments may be included.
Memory 304 may further include one or more data storage 310, which can be utilized by network computer 300 to store, among other things, applications 320 or other data. For example, data storage 310 may also be employed to store information that describes various capabilities of network computer 300. The information may then be provided to another device or computer based on any of a variety of methods, including being sent as part of a header during a communication, sent upon request, or the like. Data storage 310 may also be employed to store social networking information including address books, buddy lists, aliases, user profile information, or the like. Data storage 310 may further include program code, data, algorithms, and the like, for use by a processor, such as processor 302 to execute and perform actions such as those actions described below. In one embodiment, at least some of data storage 310 might also be stored on another component of network computer 300, including, but not limited to, non-transitory media inside processor-readable removable storage device 336, processor-readable stationary storage device 334, or any other computer-readable storage device within network computer 300, or even external to network computer 300. Data storage 310 may include, for example, network topology database 314, protocol information 316, or the like. In some embodiments, network topology database 314 may be a data store that contains information related to the topology of one or more network monitored by a NMC. And, protocol information 316 may store various rules or configuration information related to one or more network communication protocols, including application protocols, secure communication protocols, client-server protocols, peer-to-peer protocols, shared file system protocols, protocol state machines, or the like, that may be employed for protocol analysis, entity auto-discovery, anomaly detections, or the like, in a monitored network environment.
Applications 320 may include computer executable instructions which, when executed by network computer 300, transmit, receive, or otherwise process messages (e.g., SMS, Multimedia Messaging Service (MMS), Instant Message (IM), email, or other messages), audio, video, and enable telecommunication with another user of another mobile computer. Other examples of application programs include calendars, search programs, email client applications, IM applications, SMS applications, Voice Over Internet Protocol (VOIP) applications, contact managers, task managers, transcoders, database programs, word processing programs, security applications, spreadsheet programs, games, search programs, and so forth. Applications 320 may include network monitoring engine 322, inference engine 324, analysis engine 326, anomaly engine 327, web services 329, or the like, that may be arranged to perform actions for embodiments described below. In one or more of the various embodiments, one or more of the applications may be implemented as modules or components of another application. Further, in one or more of the various embodiments, applications may be implemented as operating system extensions, containers, modules, plugins, or the like.
Furthermore, in one or more of the various embodiments, network monitoring engine 322, inference engine 324, analysis engine 326, anomaly engine 327, web services 329, or the like, may be operative in a cloud-based computing environment. In one or more of the various embodiments, these applications, and others, that comprise a network monitoring computer may be executing within virtual machines or virtual servers that may be managed in a cloud-based based computing environment. In one or more of the various embodiments, in this context the applications may flow from one physical network computer within the cloud-based environment to another depending on performance and scaling considerations automatically managed by the cloud computing environment. Likewise, in one or more of the various embodiments, virtual machines or virtual servers dedicated to network monitoring engine 322, inference engine 324, analysis engine 326, anomaly engine 327, web services 329, or the like, may be provisioned and de-commissioned automatically.
Also, in one or more of the various embodiments, network monitoring engine 322, inference engine 324, analysis engine 326, anomaly engine 327, web services 329, or the like, may be located in virtual servers running in a cloud-based computing environment rather than being tied to one or more specific physical network computers. Likewise, in some embodiments, one or more of network monitoring engine 322, inference engine 324, analysis engine 326, anomaly engine 327, web services 329, or the like, may be configured to execute in a container-based environment.
Further, network computer 300 may also comprise hardware security module (HSM) 360 for providing additional tamper resistant safeguards for generating, storing or using security/cryptographic information such as, keys, digital certificates, passwords, passphrases, two-factor authentication information, or the like. In some embodiments, hardware security module may be employ to support one or more standard public key infrastructures (PKI), and may be employed to generate, manage, or store keys pairs, or the like. In some embodiments, HSM 360 may be a stand-alone network computer, in other cases, HSM 360 may be arranged as a hardware card that may be installed in a network computer.
Additionally, in one or more embodiments (not shown in the figures), network computer 300 may include one or more embedded logic hardware devices instead of CPUs, such as, an Application Specific Integrated Circuit (ASIC), Field Programmable Gate Array (FPGA), Programmable Array Logic (PAL), or the like, or combination thereof. The embedded logic hardware device may directly execute its embedded logic to perform actions. Also, in one or more embodiments (not shown in the figures), the network computer may include one or more hardware microcontrollers instead of CPUs. In one or more embodiments, the one or more microcontrollers may directly execute their own embedded logic to perform actions and access their own internal memory and their own external Input and Output Interfaces (e.g., hardware pins or wireless transceivers) to perform actions, such as System On a Chip (SOC), or the like.
Illustrative Logical System Architecture
NMC 408 may be arranged to receive network communication for monitoring through a variety of means including network taps, wireless receivers, port mirrors or directed tunnels from network switches, clients or servers including the endpoints themselves, virtual machine, cloud computing instances, other network infrastructure devices, or the like, or combination thereof. In at least some of the various embodiments, the NMC may receive a copy of each packet on a particular network segment or virtual local area network (VLAN). Also, for at least some of the various embodiments, NMCs may receive these packet copies through a port mirror on a managed Ethernet switch, e.g., a Switched Port Analyzer (SPAN) port, or a Roving Analysis Port (RAP). Port mirroring enables analysis and debugging of network communications. Port mirroring can be performed for inbound or outbound traffic (or both) on single or multiple interfaces. For example, in some embodiments, NMCs may be arranged to receive electronic signals over or via a physical hardware sensor that passively receives taps into the electronic signals that travel over the physical wires of one or more networks.
In one or more of the various embodiments, NMCs, such as, NMC 408, or the like, may be arranged to detect injection attacks using passive network monitoring in part by correlating network activity, such as, requests, actions, or responses that may be associated with injection attacks that may manifest themselves across different portions of a multi-tier service that may employ multiple servers to support the overall application or service.
In one or more of the various embodiments, NMCs may be arranged to monitor incoming client requests that may be provided to a frontend server, such as, a webserver or other accessible endpoint. Also, in some embodiments, the NMCs may be arranged to monitor the network traffic sent to one or more other monitored servers from the frontend server in response to incoming client requests. And, in one or more of the various embodiments, the NMCs may be arranged to monitor one or more actions associated with one or more monitored servers to determine if they may be related to the client request or other requests sent by the frontend server or other monitored servers.
For brevity and clarity, network traffic sent by clients to frontend servers may be referred herein as client requests. Network traffic sent from frontend servers to internal servers (e.g., application servers, middleware servers, or the like) may be referred herein as dependent requests because such requests may be sent by the frontend server in response to client requests. Similarly, network activity or actions associated with a dependent request may be referred to as dependent actions because they may be associated with one or more dependent requests. Likewise, in one or more of the various embodiments, network traffic sent from the frontend server to the client computer that provided the client request may be referred to as frontend responses. See,
In one or more of the various embodiments, while the untrusted code for an injection attack may be initially delivered via a client request sent to a frontend server, the untrusted code may be propagated to one or more other servers where it may be executed. Accordingly, in one or more of the various embodiments, NMCs may be arranged to correlate monitored network traffic to identify dependent requests, dependent actions, or dependent responses that may be associated with client requests (e.g., suspicious requests) that may have introduced the untrusted code. Thus, in some embodiments, NMCs may be arranged to evaluate whether an injection attack may be occurring based on two or more correlated requests, actions, or responses. In some embodiments, NMCs may be arranged to employ the correlated network traffic to improve threat detection or evaluation and reduce false positives, as described in more detail below.
In one or more of the various embodiments, NMCs, such as NMC 502 may be arranged to communicate with one or more capture agents, such as, capture agent 512, capture agent 514, or capture agent 514. In some embodiments, capture agents may be arranged to selectively capture network traffic or collect network traffic metrics that may be provided to NMC 502 for additional analysis.
In one or more of the various embodiments, capture agents may be NMCs that are distributed in various networks or cloud environments. For example, in some embodiments, a simplified system may include one or more NMCs that also provide capture agent services. In some embodiments, capture agents may be NMCs arranged to instantiate one or more capture engines to perform one or more capture or collection actions. Similarly, in one or more of the various embodiments, one or more capture agents may be instantiated or hosted separately from one or more NMCs.
In one or more of the various embodiments, capture agents may be selectively installed such that they may capture metrics for selected portions of the monitored networks. Also, in some embodiments, in networks that have groups or clusters of the same or similar entities, capture agents may be selectively installed on one or more entities that may be representative of entire groups or clusters pf similar entities. Thus, in some embodiments, capture agents on the representative entities may collect metrics or traffic that may be used to infer the metrics or activity associated with similarly situated entities that do not include a capture agent.
Likewise, in one or more of the various embodiments, one or more capture agents may be installed or activated for a limited time period to collect information that may be used to infer activity information about the monitored networks. Accordingly, in one or more of the various embodiments, these one or more capture agents may be removed or de-activated if sufficient activity information or network traffic has been collected.
In one or more of the various embodiments, system 500 may include one or more network entities, such as, entities 518, entities 520, or the like, that communicate in or over one or more of the monitored networks. Entities 518 and entities 520 are illustrated here as cloud environment compute instances (e.g., virtual machines), or the like. However, one of ordinary skill in the art will appreciate that entities may be considered to be various network computers, network appliances, routers, switches, applications, services, containers, or the like, subject to network monitoring by one or more NMCs. See also,
In this example, for one or more of the various embodiments, capture agents, such as capture agent 512 may be arranged to capture network traffic or network traffic metrics associated with one or more entities, such as, entities 518. Accordingly, in some embodiments, some or all of the information captured by capture agents may be provided to one or more NMCs, such as, NMC 502 for additional analysis. Also, in one or more of the various embodiments, capture agents or NMCs may be arranged to selectively store network traffic in a captured data store, such as, captured data store 522.
Accordingly, in this example, NMC 604 may be arranged to employ observation port 614 to monitor client requests provided to frontend server 606 by client computer 612. Also, in this example, NMC 604 may be arranged to employ observation port 616 to monitor network traffic exchanged between frontend server 606 and application server 608. And, in this example, NMC 604 may be arranged to employ observation port 618 to monitor network traffic exchanged between application server 608 and database server 610. Note, in some embodiments, observation ports 614, 616, or 618 may be the same observation port. For example, in some embodiments, if frontend server 606, application server 608, or database server 610, or the like, are on the same network or sub-network, NMC 604 may be arranged to monitor the network traffic exchanged between them by employing one observation port rather than employing three observation ports as shown here. In this example, the NMC 604 is arranged to simultaneously monitor network traffic that may be exchanged between the various servers in network 602 as well as the network traffic exchanged between frontend server 614 and client computer 612, or the like.
In this example, for some embodiments, client computer 612 may send a client request to frontend server 606, which may cause frontend server 606 to send one or more dependent requests to application server 608, which may in turn cause application server 608 to send one or more dependent requests to database server 610. Likewise, for example, database server 610 may perform one or more dependent actions based on one or more dependent requests that may include sending one or more dependent responses to application server 608 which in turn may trigger one or more dependent actions, such as sending one or more dependent responses to frontend server 606, which may in turn send one or more frontend responses to client computer 612.
Accordingly, in some embodiments, NMC 604 may be arranged to monitor and track the various dependent requests or dependent actions that may be associated with a given client request. In some embodiments, the format, application protocols, communication protocols, or the like, associated with some or all of the different requests or actions may be different depending on which client or server provides the requests or performs the actions. Accordingly, in some embodiments, NMCs may be arranged to monitor the network traffic exchanged between the servers or clients to determine correlations that may be used to identify one or more dependent requests or one or more dependent actions that may be associated with a client request.
In one or more of the various embodiments, as client requests are monitored, NMC 604 may be arranged to perform an initial evaluation or validation of incoming client requests to determine if the NMC should monitor other network traffic in the monitored network for dependent requests or dependent actions that may be associated with the incoming client request.
In one or more of the various embodiments, NMCs, such as, NMC 604, or the like, may be arranged to determine or select one or more portions of the client requests to evaluate them for susceptibility to injection attacks. In one or more of the various embodiments, NMCs may employ various initial criteria to determine if a client request should be validated for susceptibility to injection attacks. In some embodiments, criteria may include (or be based on) one or more characteristics of the requests, the client, the target of the request, tuple information (e.g., source network address information, destination network address, or the like), time of day, system or network utilization, rate of requests sent or received, or the like, or combination thereof. In some embodiments, an NMC may be arranged to employ a tiered or hierarchical validation (or filtering) process such that it may perform some preliminary validation on incoming requests before determining if they should be further validated for injection attack risk. In some embodiments, NMCs may be arranged to determine some or all of the criteria for determining whether to validate client requests based on rules or conditions that may be obtained from configuration information.
In one or more of the various embodiments, NMCs may be arranged to provide and store correlation information that may be associated with one or more the client requests. In some embodiments, correlation information may be collected for requests that may be determined to be associated with an elevated risk of injection attack. In some embodiments, correlation information may include one or more portions of the client requests, including, communication protocol information (e.g., one or more TCP field values, or the like), parameter or parameter values, URLs, query strings, HTTP information (e.g., cookies, header field values, user-agent strings, and so on), some or all of the tuple information, or the like. In some embodiments, the some or all the payload or some or all of the network packet(s) associated with a client request may be stored as correlation information. In some embodiments, NMCs may be arranged to associate different kinds of client requests with different correlation information such that different information, characteristics, or values may be associated with different client requests. In some embodiments, NMCs may be arranged to determine some or all of the correlation information based on configuration information.
In one or more of the various embodiments, in response to receiving a client request, a frontend server, such as, frontend server 606 may generate one or more dependent requests that may be directed to one or more other servers, such as, application server 608. For example, in some embodiments, the client request may be a HTTP request associated with a particular user or asset that may be managed or stored by another server.
For example, a process on frontend server 606 may parse the incoming request and determine that the client is requesting information that may be available on a different server. The client request may indicate that a user wants to view an invoice or other record that may be managed by application server 608. Accordingly, in this example, the frontend server may generate an appropriate dependent request and send it to an application server, such as, application server 608.
In one or more of the various embodiments, NMCs, such as, NMC 604 may be arranged to monitor network traffic sent by frontend servers to identify one or more requests that may be dependent on client requests. In some embodiments, requests provided by a frontend server may be subject to the filtering or validation to determine if they should be evaluated or otherwise considered dependent on a client request.
In some embodiments, NMCs may be arranged to employ some or all of the correlation information to identify one or more dependent requests. In some embodiments, this may include comparing the network traffic that may be associated with a request sent by another server with correlation information that is associated with one or more client requests. For example, in some embodiments, correlation information may be based on one or more values or features of the client request that would be likely to be included in dependent requests, such as, identifiers, keys, tuple information, application specific data, or the like.
Also, in some embodiments, NMCs may be arranged to update or modify the correlation information associated with the original client request based on information determined from the one or more dependent requests. In some embodiments, NMCs may be arranged to determine dependent requests based on pattern matching, templates, rules, conditions, or the like, that may be obtained from configuration information.
Further, in one or more of the various embodiments, application servers, such as, application server 608 may require information from one or more other servers to respond to one or more received dependent requests. For example, in some embodiments, application server 608 may need to retrieve information from database server 610 to respond to a dependent request received from frontend server 606.
In this example, for some embodiments, application server 608, or the like, may send one or more requests that may be dependent on one or more dependent requests sent by frontend server 606. Accordingly, in one or more of the various embodiments, an NMC may be arranged to perform one or more actions to filter or validate some or all of network traffic sent by application servers (or other intervening servers) to determine if the application server may be sending its own dependent requests to another server, such as, database server 610. Also, in some embodiments, NMCs may be arranged to update the correlation information associated with the initiating client request with information based on the dependent requests sent by an application server.
In some embodiments, in response to receiving a dependent request from application server 608, other servers, such as, database server 610 may be arranged to perform one or more actions that may be associated with the dependent request. In some embodiments, such actions may include sending responses to application server 608, or, in some cases, to other servers.
Accordingly, in one or more of the various embodiments, NMCs may be arranged to monitor network traffic that may be sent from other servers, such as, database server 610 to determine if one or more responses may be associated with one or more dependent requests. In some embodiments, NMCs may employ correlation information to determine if one or more responses may be dependent responses. This process may be considered similar to how dependent requests may be determined. However, in some embodiments, the correlation information used to make such determinations may vary from the correlation information used to identify dependent requests.
Similarly, in one or more of the various embodiments, NMCs may be arranged to monitor network traffic that may originate from other servers, including, application server 608, frontend server 606, or the like, to determine if there may be dependent actions, such as, dependent responses, or the like, that may be associated with an initial client request.
Also, in one or more of the various embodiments, NMCs may be arranged to evaluate or validate each identified dependent request or dependent action to determine a risk or likelihood of an association with an injection attack. Accordingly, in one or more of the various embodiments, the risk of an injection attack may be evaluated in view of some or all of the related dependent requests, some or all of the related dependent actions, some or all of the correlation information, or the like.
In some cases, injection attacks may pass through one or more servers before they are detected. Thus, in some embodiments, NMCs may be arranged to employ the stored correlation information to determine the one or more servers that may be associated with a chain of dependent requests that may be associated with a detected injection attack. For example, in some embodiments, if an injection attack is detected or confirmed by validating dependent requests arriving at database server 610 or by dependent actions performed by database server 610, the NMC, in this example, may determine that the client request sent by client computer 612 may be the source of the attack.
In contrast, in conventional monitoring environments, dedicated monitors may be limited to monitoring requests sent to particular servers or services, such as, web servers, database servers, application servers, or the like. Accordingly, conventional monitors may be limited because of the context necessary for identifying the chain of dependent requests or dependent responses provides is unavailable to conventional monitors. For example, while a conventional monitor may identify injection attacks against a database server by monitoring requests sent to the database server, the conventional monitor is disabled from determining related upstream requests or downstream responses that may be related to the attack that was detected at the database server.
Further, in some embodiments, NMCs may employ the correlation information to improve the likelihood of attack detection or reduce the number of false positives. Employing the correlation information to evaluate potential threats may enable NMCs to evaluate characteristics of some or all of the chained requests, actions, or responses so it may use stricter criteria that would otherwise be unavailable to a conventional monitoring system.
Thus, in some embodiments, NMCs may have an improved chance to detect actual injection attacks while at the same time the number of false positive detections may be reduced. For example, some conventional monitors may reduce the number of false positive detections by narrowing or otherwise restricting the detection criteria. However, this may cause the same monitor to miss more attacks. Likewise, for example, broadening the detection criteria used by a conventional monitor may disadvantageously increase the number of false positive reports.
In this example, for some embodiments, client computer 710 may send client request 718 to frontend server 704. In this example, in response to receiving client request 718, frontend server 704 may provide dependent request 720 to application server 706. And, in this example, in response to receiving dependent request 720, application server 706 may provide dependent request 722 to database server 708. Accordingly, in this example, database server 708 may provide a dependent response, such as, dependent response 724 to application server 706, which in turn may provide dependent response 726 to client computer 710.
In one or more of the various embodiments, as shown in this example, NMCs, such as, NMC 702 may be arranged to validate or evaluate one or more requests or responses in the monitored networking environment to determine correlation information that may be employed to identify one or more dependent requests (e.g., dependent request 720, dependent request 722, or the like) or one or more dependent responses (e.g., dependent response 726, dependent response 724, or the like) that may be associated with client requests, such as, client request 718.
In this example, client computer 810 may be communicating with frontend server 804. Also, in this example, NMC 802 may employ observation port 812, observation port 814, or observation port 816 to monitor network traffic that may be exchanged by the servers and client computers. Note, in this example, the observation ports are illustrated as being separate sources or channels. However, in some embodiments, one (or more) observation ports may be configured to monitor some or all of the network traffic in the monitored networking environment.
In this example, for some embodiments, client computer 810 may send client request 818 to frontend server 804. In this example, client request 818 is similar to client request 718 in
In this example, in response to receiving client request 818, frontend server 804 may provide dependent request 820 to application server 806. In this example, the injected untrusted code (e.g., from request portion 828) is being carried deeper into system 800. In this example, dependent request 820 differs from dependent request 718 in
And, in this example, in response to receiving dependent request 820, application server 806 may provide dependent request 822 to database server 808. In this example, dependent request 822 differs from the otherwise similar dependent request 722 in
Accordingly, in this example, database server may provide a dependent response, such as, dependent response 824 that includes all of the invoice records to application server 806, which in turn may provide dependent response 826 to client computer 810.
In this example, in some cases, at each stage of the injection attack, it is possible that one or more conventional monitors may raise one or more alarms associated with untrusted code that is introduced by client request 818. Thus, in some cases, for example, if each dependent request or dependent response associated with the injection attack is detected, conventional monitors may disadvantageously raise as many as five independent alarms for the injection attack. Alternatively, in some cases, conventional monitoring may fail to detect some of the compromised dependent requests or some of the compromised dependent responses making it difficult or impossible for system administrators or incident response teams to determine the extent of the penetration so they can perform effective remediation.
In contrast, in this example, for some embodiments, NMCs may be arranged to determine the link between the different stages of the injection attack that is introduced by client request 818 even if each stage of the attack does not raise an alarm. For example, if NMC 802 finally confirms the injection attack because it detects the large amount of data (e.g., all the invoice records) unexpectedly being provided to client computer 810, NMC 802 may be arranged to employ correlation information collected from one or more stages of the injection attack to provide notification information that enables system administrators or incident response teams to see the full extent of the injection attack. Accordingly, they may be enabled to take the proper remediation steps to resolve or otherwise recover from the attack.
Generalized Operations
In one or more of the various embodiments, the one or more NMCs may be arranged to determine the one or more portions of the network traffic that may include requests. In some embodiments, NMCs may be arranged to employ one or more filters or rules that are configured to determine which portions of the network traffic that may include one or more requests. In some embodiments, this may include monitoring one or more well-known or defined network addresses, ports, or the like.
Further, in one or more of the various embodiments, NMCs may be arranged to distinguish requests from other network traffic based on the communication protocol or application protocol that may be employed by the request providers (e.g., client computers, other servers, or the like). For example, many requests directed to web servers may be provided via communication protocol TCP/IP using HTTP application protocol directed to TCP port 80, or the like. Generally, in some embodiments, configuration information available to the one or more NMCs may define filters, rules, patterns, templates, or the like, that may be employed to determine one or more requests from other network traffic.
At block 904, in one or more of the various embodiments, the one or more NMCs may be arranged to perform one or more actions to validate the one or more requests. In one or more of the various embodiments, as described above, NMCs may be arranged to collect correlation information that may be associated with incoming requests. However, in one or more of the various embodiments, given that most or many requests may be inherently safe with respect to injection attacks, it may be disadvantageous to collect correlation information for every request.
In one or more of the various embodiments, because collecting correlation information consumes memory resources of the NMCs, validation may be employed to help preserve memory resources. Likewise, in one or more of the various embodiments, the actions performed by NMCs to determine dependent requests or dependent responses also consumes compute resources of the NMCs. Accordingly, in one or more of the various embodiments, it may be advantageous to exclude requests that are known to be safe from additional the processing that may be required for detecting injection attacks.
Accordingly, in one or more of the various embodiments, NMCs may be arranged to perform one or more actions to determine if incoming client requests may be susceptible to being associated with injection attacks. For example, in some embodiments, vanilla HTTP GET requests that do not include query parameters, or the like, may be determined to be safe with respect to injection attacks. Accordingly, for this example, such requests may be disregarded with respect to injection attacks. Whereas, for example, in some embodiments, requests that are include varying or multiple query parameters may be considered risky enough to justify the expenditure of additional resources to guard against injection attacks.
In one or more of the various embodiments, NMCs may be arranged to employ a variety of methods to validate requests, including, templates, masks, pattern matching, machine learning classifiers or models, regular expressions, rules, computer readable instructions, parsers, grammars, abstract syntax trees, or the like, or combination thereof, that may be provided to the NMC via configuration information.
In some embodiments, NMCs may be arranged to select one or more validation actions based on additional information, such as, communication protocols, application protocols, applications, historical information (e.g., behavior observed previously), user preferences, or the like. Further, in some embodiments, NMCs may be arranged to select one or more validation actions based on one or more performance metrics that may be associated with the monitored networks. For example, if the network traffic is low or the rate of incoming requests is below a defined threshold value, NMCs may be arranged to employ validation methods that may be more aggressive (e.g., more likely to classify an incoming request as suspicious) because current metrics may indicate that few requests will arrive so expending the resources to evaluate a higher percentage of the incoming requests for additional monitoring may not be disadvantageous.
At decision block 906, in one or more of the various embodiments, if one or more of requests may be determined to be suspicious, control may flow to block 908; otherwise, control may loop back to block 902. In some embodiments, suspicious requests may be requests that range from requests that are likely to be compromised by injection attacks to requests that it may be possible to compromise. For example, in some embodiments, an NMC may compare a client request against an application specific template tests or confirms that a particular query string parameter is restricted to holding numerical values, thus if the value for that query string parameter appears to be non-numeric, the request may be identified as suspicious. Likewise, in some embodiments, for example, a client request that includes any query string parameters may be considered suspicious if the client request is associated with a critical application, or an application that is known to be more susceptible to injection attacks than other applications.
At block 908, in one or more of the various embodiments, the one or more NMCs may be arranged to determine one or more dependent actions, including one or more dependent requests that may be sent from one or more servers to one or more other servers. As describe above, in some embodiments, NMCs may monitor network traffic sent by one or more servers in the monitored networking environment. Accordingly, in one or more of the various embodiments, NMCs may be arranged to employ correlation information associated with one or more suspicious requests sent by client computers to determine if the servers are performing actions that may be correlated with the one or more suspicious requests (e.g., suspicious client requests).
In one or more of the various embodiments, correlation information may include one or more fields, values, tuple information, cryptographic values, or the like, that may match or otherwise may be associated with the suspicious requests.
At decision block 910, in one or more of the various embodiments, if anomalous activity is detected by the one or more NMCs, control may flow to block 914; otherwise, control may loop back to block 902. In one or more of the various embodiments, NMCs may be arranged to evaluate dependent actions, including dependent requests or dependent responses to determine if they may be anomalous or if they may be associated with anomalous activity. In some embodiments, NMCs may be arranged to evaluate if there may be anomalous activity based on various tests, conditions, heuristics, machine learning classifiers or models, or the like, that may be defined or designated in configuration information. Thus, in some embodiments, different organizations may be enabled to select configuration information that aligns with their risk tolerance, usage patterns, applications, or the like.
At block 914, in one or more of the various embodiments, the one or more NMCs may be arranged to provide one or more alerts, notifications, or reports that may be associated with the anomalous activity that was detected. In some embodiments, depending on the type of anomalous activity, NMCs may be arranged to perform various actions, such as, sending notifications, raising alarms, generating reports, or the like. Next, control may be returned to a calling process.
At block 1004, in one or more of the various embodiments, the one or more NMCs may be arranged to validate the one or more requests based on one or more characteristics of the one or more requests. In one or more of the various embodiments, NMCs may be arranged to perform one or more actions to validate or evaluate the incoming requests to determine if the requests may be susceptible or at risk for being associated with an injection attack.
At decision block 1006, in one or more of the various embodiments, if one or more requests may be determined to be suspicious, control may flow to block 1008; otherwise, control may be returned to a calling process. For brevity and clarity, requests that are determined to meet the criteria of being susceptible to being associated with an injection attack are referred herein as suspicious requests to distinguish them from requests that are not considered susceptible to being associated with an injection attack. Note, referring to a request as a suspicious request is not intended to imply that it is actually associated with an injection attack. Rather, it should be understood, that suspicious requests are requests that have one or more characteristics that trigger the NMC to collect correlation information that may be associated with the suspicious request or to attempt to determine one or more dependent requests or dependent responses that may be associated with the suspicious request.
At block 1008, in one or more of the various embodiments, the one or more NMCs may be arranged to determine and store correlation information that may be associated with the one or more suspicious requests. In one or more of the various embodiments, NMCs may be arranged to perform one or more actions to identify one or more characteristics of the suspicious request that may be used as correlation information. In some embodiments, correlation information may be information that NMCs may use to determine if other network traffic, such as, requests or responses, may be associated with a suspicious request. Thus, in one or more of the various embodiments, if correlation information is determined or collected, it may be stored in a data store for later use.
In one or more of the various embodiments, the format, or contents of the correlation information may vary depending on the characteristics of the suspicious request. In some embodiments, the entire request may be considered correlation information. Also, in some embodiments, the one or more portions of the suspicious request may be considered correlation information. Also, in some embodiments, meta-data, such as, timestamps, or the like, may be included in the correlation information.
In one or more of the various embodiments, NMCs may be arranged to employ one or more rules, templates, masks, regular expressions, or the like, for generating correlation information based on a given suspicious request. In some embodiments, portions of the suspicious request may be extracted from the request payload extracted from the request and stored as correlation information.
At block 1010, in one or more of the various embodiments, the one or more NMCs may be arranged to monitor other network traffic that may be sent from the server associated with the one or more suspicious requests. As described above, NMCs may determine one or more actions performed by the server that received the client request, including one or more requests being sent by the server. In some embodiments, correlation information associated with one or more suspicious requests may be compared to one or more characteristics of the actions performed by other servers or requests being sent by other servers to identify dependent actions or dependent requests based on their correlation with suspicious requests.
At block 1012, in one or more of the various embodiments, the one or more NMCs may be arranged to validate the one or more dependent actions, including depending requests, if any. In some embodiments, NMCs may evaluate the one or more dependent requests to determine if they may be susceptible to an injection attack. Likewise, in some embodiments, NMCs may be arranged to evaluate the one or more dependent actions to determine if they may be associated with an injection attack As described above, for client requests, NMCs may be arranged to determine if one or more of the dependent actions have characteristics that may make more susceptible to injection attacks based on one or more evaluations.
At block 1014, in one or more of the various embodiments, the one or more NMCs may be arranged to determine and store correlation information that may be associated with the dependent actions. In one or more of the various embodiments, similar to generating correlation information for suspicious requests, NMCs may be arranged to update the correlation information that may be associated with one or more suspicious requests with information that may be derived from the dependent actions. In some embodiments, this may include storing information about dependent requests that may be employed to associate the dependent actions to one or more suspicious requests. Also, in some embodiments, the additional correlation information may be employed to associate the dependent actions to the other servers that may be associated with one or more of the dependent actions.
Also, in some embodiments, the additional correlation information may include tuple information, application protocol information, communication protocol information, or the like, that may enable an NMC to identify the application that may be associated with the dependent actions or dependent requests. Accordingly, in one or more of the various embodiments, NMCs may be arranged to employ the correlation information to trace the associations between the one or more dependent actions (including dependent requests) and the suspicious requests even though they may span multiple servers, networks, sub-networks, or the like.
In one or more of the various embodiments, NMCs may be arranged to employ correlation information collected from other dependent actions (including dependent requests) or suspicious requests to identify dependent actions that may be associated with the same injection attack. Accordingly, in one or more of the various embodiments, as more dependent actions are discovered, the strength of the correlation between the various requests associated with the same injection attack may increase. Next, in one or more of the various embodiments, control may be returned to a calling process.
At block 1104, in one or more of the various embodiments, the NMC may be arranged to determine one or more dependent actions that may be associated with the suspicious requests. Accordingly, in one or more of the various embodiments, the NMC may be arranged to determine additional correlation information that may be associated with the dependent actions, if any, and store it in a data store.
At decision block 1106, in one or more of the various embodiments, if a pending injection attack may be detected, control may flow to block 1110; otherwise, control may flow to decision block 1108. In one or more of the various embodiments, for each determined dependent actions, the NMC may be arranged to evaluate the collection of correlation information that may be associated with the client request determined in block 1102. In some embodiments, as NMCs collect correlation information associated with a suspicious request, they may have an increased opportunity to detect that a malicious injection attack may be pending.
In one or more of the various embodiments, NMCs may be arranged to take one or more actions as soon as a pending injection attack is confirmed. Accordingly, in one or more of the various embodiments, NMCs may be arranged to direct process 1100 to flow to block 1110 to perform one or more actions in response to the confirmed the pending injection attack.
At decision block 1108, in one or more of the various embodiments, if there are more dependent requests, control may loop back to block 1104; otherwise, control may be returned to a calling process.
At block 1110, in one or more of the various embodiments, the NMC may be arranged to provide one or more alerts or notifications that may be associated with the pending injection attack.
Next, control may be returned to a calling process.
It will be understood that each block of the flowchart illustration, and combinations of blocks in the flowchart illustration, can be implemented by computer program instructions. These program instructions may be provided to a processor to produce a machine, such that the instructions, which execute on the processor, create means for implementing the actions specified in the flowchart block or blocks. The computer program instructions may be executed by a processor to cause a series of operational steps to be performed by the processor to produce a computer-implemented process such that the instructions, which execute on the processor to provide steps for implementing the actions specified in the flowchart block or blocks. The computer program instructions may also cause at least some of the operational steps shown in the blocks of the flowchart to be performed in parallel. Moreover, some of the steps may also be performed across more than one processor, such as might arise in a multi-processor computer system. In addition, one or more blocks or combinations of blocks in the flowchart illustration may also be performed concurrently with other blocks or combinations of blocks, or even in a different sequence than illustrated without departing from the scope or spirit of the invention.
Accordingly, blocks of the flowchart illustration support combinations of means for performing the specified actions, combinations of steps for performing the specified actions and program instruction means for performing the specified actions. It will also be understood that each block of the flowchart illustration, and combinations of blocks in the flowchart illustration, can be implemented by special purpose hardware based systems, which perform the specified actions or steps, or combinations of special purpose hardware and computer instructions. The foregoing example should not be construed as limiting or exhaustive, but rather, an illustrative use case to show an implementation of at least one of the various embodiments of the invention.
Further, in one or more embodiments (not shown in the figures), the logic in the illustrative flowcharts may be executed using an embedded logic hardware device instead of a CPU, such as, an Application Specific Integrated Circuit (ASIC), Field Programmable Gate Array (FPGA), Programmable Array Logic (PAL), or the like, or combination thereof. The embedded logic hardware device may directly execute its embedded logic to perform actions. In one or more embodiments, a microcontroller may be arranged to directly execute its own embedded logic to perform actions and access its own internal memory and its own external Input and Output Interfaces (e.g., hardware pins or wireless transceivers) to perform actions, such as System On a Chip (SOC), or the like.
| Number | Name | Date | Kind |
|---|---|---|---|
| 5027269 | Grant | Jun 1991 | A |
| 5430727 | Callon | Jul 1995 | A |
| 5541995 | Normile | Jul 1996 | A |
| 5715464 | Crump et al. | Feb 1998 | A |
| 5787237 | Reilly | Jul 1998 | A |
| 5802599 | Cabrera et al. | Sep 1998 | A |
| 5835726 | Shwed et al. | Nov 1998 | A |
| 5857188 | Douglas | Jan 1999 | A |
| 5928363 | Ruvolo | Jul 1999 | A |
| 6141686 | Jackowski et al. | Oct 2000 | A |
| 6263049 | Kuhn | Jul 2001 | B1 |
| 6321338 | Porras et al. | Nov 2001 | B1 |
| 6385729 | DiGiorgio et al. | May 2002 | B1 |
| 6405250 | Lin et al. | Jun 2002 | B1 |
| 6412000 | Riddle et al. | Jun 2002 | B1 |
| 6526044 | Cookmeyer, II et al. | Feb 2003 | B1 |
| 6560636 | Cohen et al. | May 2003 | B2 |
| 6704311 | Chuah et al. | Mar 2004 | B1 |
| 6704874 | Porras et al. | Mar 2004 | B1 |
| 6765909 | Sen et al. | Jul 2004 | B1 |
| 6807156 | Veres et al. | Oct 2004 | B1 |
| 6807565 | Dodrill et al. | Oct 2004 | B1 |
| 6883015 | Geen et al. | Apr 2005 | B1 |
| 6901517 | Redmore | May 2005 | B1 |
| 6944599 | Vogel et al. | Sep 2005 | B1 |
| 6948060 | Ramanathan | Sep 2005 | B1 |
| 6968554 | Macdonald et al. | Nov 2005 | B1 |
| 6999729 | Wandel | Feb 2006 | B2 |
| 7042888 | Berggreen | May 2006 | B2 |
| 7089326 | Boucher et al. | Aug 2006 | B2 |
| 7133365 | Klinker et al. | Nov 2006 | B2 |
| 7143153 | Black et al. | Nov 2006 | B1 |
| 7177930 | LoPresti | Feb 2007 | B1 |
| 7181769 | Keanini et al. | Feb 2007 | B1 |
| 7193968 | Kapoor et al. | Mar 2007 | B1 |
| 7313141 | Kan et al. | Dec 2007 | B2 |
| 7424532 | Subbiah | Sep 2008 | B1 |
| 7474654 | Guru | Jan 2009 | B2 |
| 7480292 | Busi | Jan 2009 | B2 |
| 7509680 | Sallam | Mar 2009 | B1 |
| 7535906 | Engbersen et al. | May 2009 | B2 |
| 7543146 | Karandikar et al. | Jun 2009 | B1 |
| 7545499 | Overbeck et al. | Jun 2009 | B2 |
| 7580356 | Mishra et al. | Aug 2009 | B1 |
| 7594273 | Keanini et al. | Sep 2009 | B2 |
| 7602731 | Jain | Oct 2009 | B2 |
| 7606706 | Rubin et al. | Oct 2009 | B1 |
| 7609630 | Gobeil | Oct 2009 | B2 |
| 7619988 | Shimada et al. | Nov 2009 | B2 |
| 7639613 | Ghannadian et al. | Dec 2009 | B1 |
| 7644150 | Nucci et al. | Jan 2010 | B1 |
| 7660883 | Fowlow | Feb 2010 | B2 |
| 7724905 | Bleumer et al. | May 2010 | B2 |
| 7739497 | Fink et al. | Jun 2010 | B1 |
| 7774456 | Lownsbrough et al. | Aug 2010 | B1 |
| 7809829 | Kelly et al. | Oct 2010 | B2 |
| 7810151 | Guruswamy | Oct 2010 | B1 |
| 7817549 | Kasralikar et al. | Oct 2010 | B1 |
| 7849502 | Bloch et al. | Dec 2010 | B1 |
| 7864764 | Ma et al. | Jan 2011 | B1 |
| 7916652 | Lima et al. | Mar 2011 | B1 |
| 7936682 | Singh et al. | May 2011 | B2 |
| 7937755 | Guruswamy | May 2011 | B1 |
| 7975139 | Coulier | Jul 2011 | B2 |
| 7979555 | Rothstein et al. | Jul 2011 | B2 |
| 7979694 | Touitou et al. | Jul 2011 | B2 |
| 8040798 | Chandra et al. | Oct 2011 | B2 |
| 8079083 | Bennett et al. | Dec 2011 | B1 |
| 8102783 | Narayanaswamy et al. | Jan 2012 | B1 |
| 8107397 | Bagchi et al. | Jan 2012 | B1 |
| 8125908 | Rothstein | Feb 2012 | B2 |
| 8185953 | Rothstein et al. | May 2012 | B2 |
| 8352725 | O'Toole, Jr. | Jan 2013 | B1 |
| 8411677 | Colloff | Apr 2013 | B1 |
| 8457127 | Eastham et al. | Jun 2013 | B2 |
| 8533254 | Whitson, Jr. et al. | Sep 2013 | B1 |
| 8555383 | Marshall et al. | Oct 2013 | B1 |
| 8619579 | Rothstein et al. | Dec 2013 | B1 |
| 8627422 | Hawkes et al. | Jan 2014 | B2 |
| 8707440 | Gula et al. | Apr 2014 | B2 |
| 8782393 | Rothstein et al. | Jul 2014 | B1 |
| 8817655 | Szabo et al. | Aug 2014 | B2 |
| 8848744 | Rothstein et al. | Sep 2014 | B1 |
| 8861397 | Kind et al. | Oct 2014 | B2 |
| 8971196 | Degioanni et al. | Mar 2015 | B2 |
| 9036493 | Degioanni et al. | May 2015 | B2 |
| 9049216 | McCanne et al. | Jun 2015 | B2 |
| 9158604 | Christodorescu et al. | Oct 2015 | B1 |
| 9183573 | Tseng | Nov 2015 | B2 |
| 9189318 | Li et al. | Nov 2015 | B2 |
| 9191400 | Ptasinski et al. | Nov 2015 | B1 |
| 9203865 | Linden et al. | Dec 2015 | B2 |
| 9264268 | Arora et al. | Feb 2016 | B2 |
| 9338147 | Rothstein et al. | May 2016 | B1 |
| 9357410 | Nedeltchev et al. | May 2016 | B2 |
| 9380489 | Kotecha et al. | Jun 2016 | B2 |
| 9391866 | Martin | Jul 2016 | B1 |
| 9400872 | Hewinson | Jul 2016 | B2 |
| 9401925 | Guo et al. | Jul 2016 | B1 |
| 9426036 | Roy | Aug 2016 | B1 |
| 9430646 | Mushtaq et al. | Aug 2016 | B1 |
| 9461875 | Groat et al. | Oct 2016 | B2 |
| 9483742 | Ahmed | Nov 2016 | B1 |
| 9516053 | Muddu et al. | Dec 2016 | B1 |
| 9531736 | Torres et al. | Dec 2016 | B1 |
| 9565202 | Kindlund et al. | Feb 2017 | B1 |
| 9621523 | Rothstein et al. | Apr 2017 | B2 |
| 9660879 | Rothstein | May 2017 | B1 |
| 9692658 | Guo | Jun 2017 | B2 |
| 9715820 | Boss | Jul 2017 | B1 |
| 9729416 | Khanal | Aug 2017 | B1 |
| 10009793 | Wetterwald et al. | Jun 2018 | B2 |
| 10027689 | Rathor et al. | Jul 2018 | B1 |
| 10028167 | Calin et al. | Jul 2018 | B2 |
| 10038611 | Wu et al. | Jul 2018 | B1 |
| 10063434 | Khanal et al. | Aug 2018 | B1 |
| 10198667 | Ryan, Jr. | Feb 2019 | B2 |
| 10263883 | Kamble | Apr 2019 | B2 |
| 10264003 | Wu et al. | Apr 2019 | B1 |
| 10277618 | Wu et al. | Apr 2019 | B1 |
| 10320749 | Sengupta et al. | Jun 2019 | B2 |
| 10389574 | Wu et al. | Aug 2019 | B1 |
| 10411978 | Ball et al. | Sep 2019 | B1 |
| 10536475 | McCorkle, Jr. et al. | Jan 2020 | B1 |
| 10554665 | Badawy et al. | Feb 2020 | B1 |
| 10594718 | Deaguero et al. | Mar 2020 | B1 |
| 20020023080 | Uga et al. | Feb 2002 | A1 |
| 20020024964 | Baum et al. | Feb 2002 | A1 |
| 20020035604 | Cohen et al. | Mar 2002 | A1 |
| 20020055998 | Riddle et al. | May 2002 | A1 |
| 20020065912 | Catchpole et al. | May 2002 | A1 |
| 20020078382 | Sheikh et al. | Jun 2002 | A1 |
| 20020080720 | Pegrum et al. | Jun 2002 | A1 |
| 20020091844 | Craft | Jul 2002 | A1 |
| 20020097724 | Halme et al. | Jul 2002 | A1 |
| 20020107953 | Ontiveros et al. | Aug 2002 | A1 |
| 20020133586 | Shanklin et al. | Sep 2002 | A1 |
| 20020133622 | Pinto | Sep 2002 | A1 |
| 20020152209 | Merugu et al. | Oct 2002 | A1 |
| 20020156880 | Mokuya | Oct 2002 | A1 |
| 20020199098 | Davis | Dec 2002 | A1 |
| 20030014628 | Freed et al. | Jan 2003 | A1 |
| 20030084279 | Campagna | May 2003 | A1 |
| 20030093514 | Valdes et al. | May 2003 | A1 |
| 20030131116 | Jain et al. | Jul 2003 | A1 |
| 20030135667 | Mann et al. | Jul 2003 | A1 |
| 20030149887 | Yadav | Aug 2003 | A1 |
| 20030152094 | Colavito et al. | Aug 2003 | A1 |
| 20030156715 | Reeds, III et al. | Aug 2003 | A1 |
| 20030204621 | Poletto et al. | Oct 2003 | A1 |
| 20030212900 | Liu et al. | Nov 2003 | A1 |
| 20030214913 | Kan et al. | Nov 2003 | A1 |
| 20030233361 | Cady | Dec 2003 | A1 |
| 20040003094 | See | Jan 2004 | A1 |
| 20040047325 | Hameleers et al. | Mar 2004 | A1 |
| 20040049699 | Griffith et al. | Mar 2004 | A1 |
| 20040073512 | Maung | Apr 2004 | A1 |
| 20040088544 | Tariq et al. | May 2004 | A1 |
| 20040088557 | Malcolm et al. | May 2004 | A1 |
| 20040093414 | Orton | May 2004 | A1 |
| 20040093513 | Cantrell et al. | May 2004 | A1 |
| 20040146006 | Jackson | Jul 2004 | A1 |
| 20040162070 | Baral et al. | Aug 2004 | A1 |
| 20040199630 | Sarkissian et al. | Oct 2004 | A1 |
| 20040250059 | Ramelson et al. | Dec 2004 | A1 |
| 20050015455 | Liu | Jan 2005 | A1 |
| 20050015622 | Williams et al. | Jan 2005 | A1 |
| 20050050316 | Peles | Mar 2005 | A1 |
| 20050060427 | Phillips et al. | Mar 2005 | A1 |
| 20050066196 | Yagi | Mar 2005 | A1 |
| 20050086255 | Schran et al. | Apr 2005 | A1 |
| 20050091341 | Knight et al. | Apr 2005 | A1 |
| 20050091357 | Krantz et al. | Apr 2005 | A1 |
| 20050100000 | Faulkner | May 2005 | A1 |
| 20050125553 | Wu et al. | Jun 2005 | A1 |
| 20050125684 | Schmidt | Jun 2005 | A1 |
| 20050182833 | Duffie et al. | Aug 2005 | A1 |
| 20050193245 | Hayden et al. | Sep 2005 | A1 |
| 20050201363 | Gilchrist et al. | Sep 2005 | A1 |
| 20050210242 | Troxel et al. | Sep 2005 | A1 |
| 20050234920 | Rhodes | Oct 2005 | A1 |
| 20050251009 | Morita et al. | Nov 2005 | A1 |
| 20050262237 | Fulton et al. | Nov 2005 | A1 |
| 20060029096 | Babbar et al. | Feb 2006 | A1 |
| 20060045016 | Dawdy et al. | Mar 2006 | A1 |
| 20060045017 | Yamasaki | Mar 2006 | A1 |
| 20060075358 | Ahokas | Apr 2006 | A1 |
| 20060085526 | Gulland | Apr 2006 | A1 |
| 20060101068 | Stuhee et al. | May 2006 | A1 |
| 20060106743 | Horvitz et al. | May 2006 | A1 |
| 20060123477 | Raghavan et al. | Jun 2006 | A1 |
| 20060171333 | Shimada et al. | Aug 2006 | A1 |
| 20060174343 | Duthie et al. | Aug 2006 | A1 |
| 20060184535 | Kaluskar et al. | Aug 2006 | A1 |
| 20060188494 | Bach et al. | Aug 2006 | A1 |
| 20060191008 | Fernando et al. | Aug 2006 | A1 |
| 20060191009 | Ito et al. | Aug 2006 | A1 |
| 20060230452 | Field | Oct 2006 | A1 |
| 20060230456 | Nagabhushan et al. | Oct 2006 | A1 |
| 20060233349 | Cooper | Oct 2006 | A1 |
| 20070039051 | Duthie et al. | Feb 2007 | A1 |
| 20070043861 | Baron et al. | Feb 2007 | A1 |
| 20070067841 | Yegneswaran et al. | Mar 2007 | A1 |
| 20070077931 | Glinka | Apr 2007 | A1 |
| 20070088845 | Memon et al. | Apr 2007 | A1 |
| 20070110053 | Soni et al. | May 2007 | A1 |
| 20070143852 | Keanini et al. | Jun 2007 | A1 |
| 20070153689 | Strub et al. | Jul 2007 | A1 |
| 20070156886 | Srivastava | Jul 2007 | A1 |
| 20070156919 | Potti et al. | Jul 2007 | A1 |
| 20070157306 | Elrod et al. | Jul 2007 | A1 |
| 20070169190 | Kolton et al. | Jul 2007 | A1 |
| 20070188494 | Agutter et al. | Aug 2007 | A1 |
| 20070192863 | Kapoor et al. | Aug 2007 | A1 |
| 20070239639 | Loughmiller et al. | Oct 2007 | A1 |
| 20070245420 | Yong et al. | Oct 2007 | A1 |
| 20070256122 | Foo et al. | Nov 2007 | A1 |
| 20080022401 | Cameron | Jan 2008 | A1 |
| 20080031141 | Lean et al. | Feb 2008 | A1 |
| 20080034424 | Overcash et al. | Feb 2008 | A1 |
| 20080034425 | Overcash et al. | Feb 2008 | A1 |
| 20080059582 | Hartikainen et al. | Mar 2008 | A1 |
| 20080062995 | Kaas | Mar 2008 | A1 |
| 20080069002 | Savoor et al. | Mar 2008 | A1 |
| 20080103610 | Ebrom et al. | May 2008 | A1 |
| 20080130659 | Polland | Jun 2008 | A1 |
| 20080141275 | Borgendale et al. | Jun 2008 | A1 |
| 20080141374 | Sidiroglou et al. | Jun 2008 | A1 |
| 20080147818 | Sabo | Jun 2008 | A1 |
| 20080212586 | Wang et al. | Sep 2008 | A1 |
| 20080219261 | Lin et al. | Sep 2008 | A1 |
| 20080222717 | Rothstein et al. | Sep 2008 | A1 |
| 20080232359 | Kim et al. | Sep 2008 | A1 |
| 20080279111 | Atkins et al. | Nov 2008 | A1 |
| 20080282080 | Hyndman et al. | Nov 2008 | A1 |
| 20080294384 | Fok et al. | Nov 2008 | A1 |
| 20080307219 | Karandikar | Dec 2008 | A1 |
| 20080320297 | Sabo et al. | Dec 2008 | A1 |
| 20090010259 | Sirotkin | Jan 2009 | A1 |
| 20090034426 | Luft et al. | Feb 2009 | A1 |
| 20090063665 | Bagepalli et al. | Mar 2009 | A1 |
| 20090089326 | Balasubramanian | Apr 2009 | A1 |
| 20090109973 | Ilnicki | Apr 2009 | A1 |
| 20090168657 | Puri et al. | Jul 2009 | A1 |
| 20090220080 | Herne et al. | Sep 2009 | A1 |
| 20090225675 | Baum et al. | Sep 2009 | A1 |
| 20090228330 | Karras et al. | Sep 2009 | A1 |
| 20090245083 | Hamzeh | Oct 2009 | A1 |
| 20090268605 | Campbell et al. | Oct 2009 | A1 |
| 20090271469 | Benco et al. | Oct 2009 | A1 |
| 20090292954 | Jiang et al. | Nov 2009 | A1 |
| 20090296593 | Prescott | Dec 2009 | A1 |
| 20090316602 | Nandy et al. | Dec 2009 | A1 |
| 20090327695 | Molsberry et al. | Dec 2009 | A1 |
| 20100027432 | Gopalan et al. | Feb 2010 | A1 |
| 20100091770 | Ishikawa | Apr 2010 | A1 |
| 20100095367 | Narayanaswamy | Apr 2010 | A1 |
| 20100131755 | Zhu et al. | May 2010 | A1 |
| 20100135498 | Long et al. | Jun 2010 | A1 |
| 20100167713 | Hoffman | Jul 2010 | A1 |
| 20100191856 | Gupta et al. | Jul 2010 | A1 |
| 20100201573 | Lamming | Aug 2010 | A1 |
| 20100226301 | Lohmar et al. | Sep 2010 | A1 |
| 20100250928 | Goto | Sep 2010 | A1 |
| 20100268937 | Blom | Oct 2010 | A1 |
| 20100278056 | Meloche et al. | Nov 2010 | A1 |
| 20100281539 | Burns et al. | Nov 2010 | A1 |
| 20100299158 | Siegel | Nov 2010 | A1 |
| 20100316216 | Fukushirna et al. | Dec 2010 | A1 |
| 20100322248 | Ivanov | Dec 2010 | A1 |
| 20100332618 | Norton | Dec 2010 | A1 |
| 20110019574 | Malomsoky et al. | Jan 2011 | A1 |
| 20110055138 | Khanduja et al. | Mar 2011 | A1 |
| 20110073490 | Hayamizu et al. | Mar 2011 | A1 |
| 20110126259 | Krishnamurthi et al. | May 2011 | A1 |
| 20110173441 | Bagepalli et al. | Jul 2011 | A1 |
| 20110197276 | Dorrendorf et al. | Aug 2011 | A1 |
| 20110280149 | Okada | Nov 2011 | A1 |
| 20110296002 | Caram | Dec 2011 | A1 |
| 20110320394 | McKeown et al. | Dec 2011 | A1 |
| 20110321160 | Mohandas et al. | Dec 2011 | A1 |
| 20120016977 | Robertson et al. | Jan 2012 | A1 |
| 20120030731 | Bhargava et al. | Feb 2012 | A1 |
| 20120130745 | Jones | May 2012 | A1 |
| 20120131330 | Tonsing et al. | May 2012 | A1 |
| 20120166962 | Lunsford | Jun 2012 | A1 |
| 20120176917 | Matityahu et al. | Jul 2012 | A1 |
| 20120210385 | Cirstea et al. | Aug 2012 | A1 |
| 20120215328 | Schmelzer | Aug 2012 | A1 |
| 20120216282 | Pappu et al. | Aug 2012 | A1 |
| 20120233694 | Baliga et al. | Sep 2012 | A1 |
| 20120243533 | Leong | Sep 2012 | A1 |
| 20120278477 | Terrell et al. | Nov 2012 | A1 |
| 20120290711 | Upham et al. | Nov 2012 | A1 |
| 20120294305 | Rose et al. | Nov 2012 | A1 |
| 20120324585 | Beckett, III et al. | Dec 2012 | A1 |
| 20130007296 | Mukherjee et al. | Jan 2013 | A1 |
| 20130010608 | Ramachandran et al. | Jan 2013 | A1 |
| 20130042323 | Narayanaswamy | Feb 2013 | A1 |
| 20130064084 | Babbar et al. | Mar 2013 | A1 |
| 20130067034 | Degioanni et al. | Mar 2013 | A1 |
| 20130097203 | Bhattacharjee et al. | Apr 2013 | A1 |
| 20130103734 | Boldyrev et al. | Apr 2013 | A1 |
| 20130133032 | Li et al. | May 2013 | A1 |
| 20130166730 | Wilkinson | Jun 2013 | A1 |
| 20130176842 | Bauchot et al. | Jul 2013 | A1 |
| 20130188645 | Mack-Crane | Jul 2013 | A1 |
| 20130198512 | Rubin et al. | Aug 2013 | A1 |
| 20130212297 | Varga | Aug 2013 | A1 |
| 20130227259 | Kim | Aug 2013 | A1 |
| 20130232104 | Goyal et al. | Sep 2013 | A1 |
| 20130262655 | Desch nes | Oct 2013 | A1 |
| 20130305357 | Ayyagari et al. | Nov 2013 | A1 |
| 20130339514 | Crank et al. | Dec 2013 | A1 |
| 20130347018 | Limp et al. | Dec 2013 | A1 |
| 20140040451 | Agrawal | Feb 2014 | A1 |
| 20140068035 | Croy | Mar 2014 | A1 |
| 20140075536 | Davis | Mar 2014 | A1 |
| 20140077956 | Sampath et al. | Mar 2014 | A1 |
| 20140109168 | Ashley et al. | Apr 2014 | A1 |
| 20140142972 | Hosenfeld, Jr. | May 2014 | A1 |
| 20140149456 | Carr | May 2014 | A1 |
| 20140164584 | Joe et al. | Jun 2014 | A1 |
| 20140165207 | Engel et al. | Jun 2014 | A1 |
| 20140189093 | du Toit | Jul 2014 | A1 |
| 20140195797 | du Toit | Jul 2014 | A1 |
| 20140222998 | Vasseur et al. | Aug 2014 | A1 |
| 20140223325 | Melendez et al. | Aug 2014 | A1 |
| 20140258511 | Sima | Sep 2014 | A1 |
| 20140269777 | Rothstein | Sep 2014 | A1 |
| 20140304211 | Horvitz | Oct 2014 | A1 |
| 20140310392 | Ho | Oct 2014 | A1 |
| 20140317288 | Krueger | Oct 2014 | A1 |
| 20140344633 | Li | Nov 2014 | A1 |
| 20140351415 | Harrigan et al. | Nov 2014 | A1 |
| 20150006896 | Franck | Jan 2015 | A1 |
| 20150007314 | Vaughan | Jan 2015 | A1 |
| 20150023168 | Kotecha et al. | Jan 2015 | A1 |
| 20150058987 | Thure et al. | Feb 2015 | A1 |
| 20150063158 | Nedeltchev et al. | Mar 2015 | A1 |
| 20150074258 | Ferreira et al. | Mar 2015 | A1 |
| 20150074462 | Jacoby | Mar 2015 | A1 |
| 20150089034 | Stickle et al. | Mar 2015 | A1 |
| 20150096022 | Vincent et al. | Apr 2015 | A1 |
| 20150100780 | Rubin et al. | Apr 2015 | A1 |
| 20150106930 | Honda et al. | Apr 2015 | A1 |
| 20150121461 | Dulkin et al. | Apr 2015 | A1 |
| 20150134554 | Clais et al. | May 2015 | A1 |
| 20150134776 | Kruglick | May 2015 | A1 |
| 20150149828 | Mukerji et al. | May 2015 | A1 |
| 20150180759 | Fallon | Jun 2015 | A1 |
| 20150180890 | Ronen et al. | Jun 2015 | A1 |
| 20150188702 | Men et al. | Jul 2015 | A1 |
| 20150199613 | Ruiz et al. | Jul 2015 | A1 |
| 20150227859 | Ames, II | Aug 2015 | A1 |
| 20150229661 | Balabine et al. | Aug 2015 | A1 |
| 20150242627 | Lee et al. | Aug 2015 | A1 |
| 20150249512 | Adimatyam et al. | Sep 2015 | A1 |
| 20150269358 | Hesketh | Sep 2015 | A1 |
| 20150277802 | Oikarinen | Oct 2015 | A1 |
| 20150331771 | Conway | Nov 2015 | A1 |
| 20150341379 | Lefebvre | Nov 2015 | A1 |
| 20150350167 | Djakovic | Dec 2015 | A1 |
| 20150365438 | Carver et al. | Dec 2015 | A1 |
| 20160006766 | Joo | Jan 2016 | A1 |
| 20160026922 | Vasseur et al. | Jan 2016 | A1 |
| 20160028755 | Vasseur et al. | Jan 2016 | A1 |
| 20160036647 | Gonzalez et al. | Feb 2016 | A1 |
| 20160043919 | Connelly | Feb 2016 | A1 |
| 20160055335 | Herwono et al. | Feb 2016 | A1 |
| 20160056959 | Blom et al. | Feb 2016 | A1 |
| 20160093205 | Boyer | Mar 2016 | A1 |
| 20160119215 | Deschenes et al. | Apr 2016 | A1 |
| 20160127401 | Chauhan | May 2016 | A1 |
| 20160134659 | Reddy | May 2016 | A1 |
| 20160142435 | Bernstein et al. | May 2016 | A1 |
| 20160173556 | Park | Jun 2016 | A1 |
| 20160182274 | Kiesekamp et al. | Jun 2016 | A1 |
| 20160197949 | Nyhuis | Jul 2016 | A1 |
| 20160219066 | Vasseur et al. | Jul 2016 | A1 |
| 20160262044 | Calin et al. | Sep 2016 | A1 |
| 20160285752 | Joshi | Sep 2016 | A1 |
| 20160294870 | Banerjee | Oct 2016 | A1 |
| 20160301624 | Gonzalez et al. | Oct 2016 | A1 |
| 20160301709 | Hassanzadeh | Oct 2016 | A1 |
| 20160308725 | Tang | Oct 2016 | A1 |
| 20160357967 | Mulchandani | Dec 2016 | A1 |
| 20160359872 | Yadav et al. | Dec 2016 | A1 |
| 20160380885 | Jani | Dec 2016 | A1 |
| 20170048109 | Kant et al. | Feb 2017 | A1 |
| 20170076206 | Lastras-Montano et al. | Mar 2017 | A1 |
| 20170085590 | Hsu et al. | Mar 2017 | A1 |
| 20170093796 | Wang | Mar 2017 | A1 |
| 20170093891 | Mitchell | Mar 2017 | A1 |
| 20170097982 | Zhang et al. | Apr 2017 | A1 |
| 20170099196 | Barsheshet | Apr 2017 | A1 |
| 20170111272 | Liu | Apr 2017 | A1 |
| 20170118092 | Dixon et al. | Apr 2017 | A1 |
| 20170123886 | Vaideeswaran | May 2017 | A1 |
| 20170126472 | Margalit et al. | May 2017 | A1 |
| 20170126709 | Baradaran et al. | May 2017 | A1 |
| 20170134937 | Miller | May 2017 | A1 |
| 20170230270 | Padinhakara | Aug 2017 | A1 |
| 20170270105 | Ninan et al. | Sep 2017 | A1 |
| 20170279838 | Dasgupta et al. | Sep 2017 | A1 |
| 20170288974 | Yoshihira et al. | Oct 2017 | A1 |
| 20170289104 | Shankar | Oct 2017 | A1 |
| 20170289168 | Bar | Oct 2017 | A1 |
| 20170289847 | Wetterwald et al. | Oct 2017 | A1 |
| 20170310703 | Ackerman | Oct 2017 | A1 |
| 20170353437 | Ayyadevara | Dec 2017 | A1 |
| 20170353477 | Faigon et al. | Dec 2017 | A1 |
| 20170366526 | Wood | Dec 2017 | A1 |
| 20180013650 | Khanal et al. | Jan 2018 | A1 |
| 20180084011 | Joseph et al. | Mar 2018 | A1 |
| 20180091413 | Richards et al. | Mar 2018 | A1 |
| 20180109507 | Caldera et al. | Apr 2018 | A1 |
| 20180109557 | Yoo et al. | Apr 2018 | A1 |
| 20180131675 | Sengupta et al. | May 2018 | A1 |
| 20180131711 | Chen | May 2018 | A1 |
| 20180139227 | Martin et al. | May 2018 | A1 |
| 20180167310 | Kamble | Jun 2018 | A1 |
| 20180191755 | Monaco et al. | Jul 2018 | A1 |
| 20180198812 | Christodorescu et al. | Jul 2018 | A1 |
| 20180219879 | Pierce | Aug 2018 | A1 |
| 20180260715 | Yan et al. | Sep 2018 | A1 |
| 20180351970 | Majumder et al. | Dec 2018 | A1 |
| 20180375893 | Jordan et al. | Dec 2018 | A1 |
| 20190007283 | Kieviet | Jan 2019 | A1 |
| 20190012441 | Tuli et al. | Jan 2019 | A1 |
| 20190028357 | Kokkula | Jan 2019 | A1 |
| 20190052675 | Krebs | Feb 2019 | A1 |
| 20190102469 | Makovsky et al. | Apr 2019 | A1 |
| 20190121979 | Chari | Apr 2019 | A1 |
| 20190132359 | Kraenzel | May 2019 | A1 |
| 20190171725 | Shen et al. | Jun 2019 | A1 |
| 20190196912 | Didehban | Jun 2019 | A1 |
| 20190245734 | Wu | Aug 2019 | A1 |
| 20190245763 | Wu | Aug 2019 | A1 |
| 20190266999 | Chandrasekaran | Aug 2019 | A1 |
| 20190303198 | Kim | Oct 2019 | A1 |
| 20190372828 | Wu et al. | Dec 2019 | A1 |
| Number | Date | Country |
|---|---|---|
| 109542772 | Mar 2019 | CN |
| 1026867 | Aug 2000 | EP |
| 3089424 | Nov 2016 | EP |
| 3113443 | Apr 2017 | EP |
| 1020140093060 | Jul 2014 | KR |
| 2009015461 | Feb 2009 | WO |
| 2016144932 | Sep 2016 | WO |
| Entry |
|---|
| Official Communication for U.S. Appl. No. 12/326,672 dated Jun. 9, 2010, pp. 1-9. |
| Official Communication for U.S. Appl. No. 12/326,672 dated Dec. 23, 2010, pp. 1-15. |
| Official Communication for U.S. Appl. No. 12/326,672 dated Jun. 22, 2011, pp. 1-16. |
| Official Communication for U.S. Appl. No. 12/326,672 dated Oct. 24, 2011, pp. 1-9. |
| Lin, Mark, “An Overview of Session Hijacking at the Network and Application Levels,” Jan. 18, 2005, pp. 1-16. |
| U.S. Appl. No. 11/683,643, entitled “Detecting Anomalous Network Application Behavior”, by Jesse Abraham Rothstein and Arindum Mukerji, filed on Mar. 8, 2007, pp. 1-40. |
| U.S. Appl. No. 11/679,356, entitled “Capture and Resumption of Network Application Sessions”, by Jesse Abraham Rothstein and Arindum Mukerji, filed on Feb. 27, 2007, pp. 1-37. |
| Official Communication for U.S. Appl. No. 11/683,643 dated Apr. 28, 2010, pp. 1-35. |
| Official Communication for U.S. Appl. No. 11/683,643 dated Oct. 14, 2010, pp. 1-43. |
| Official Communication for U.S. Appl. No. 11/683,643 dated Aug. 25, 2011, pp. 1-43. |
| Official Communication for U.S. Appl. No. 11/683,643 dated Jan. 23, 2012, pp. 1-6. |
| Official Communication for U.S. Appl. No. 13/831,626, dated Sep. 3, 2013, pp. 1-17. |
| Official Communication for U.S. Appl. No. 13/831,673 dated Sep. 30, 2013, pp. 1-10. |
| Official Communication for U.S. Appl. No. 13/831,673 dated Mar. 6, 2014, pp. 1-12. |
| Official Communication for U.S. Appl. No. 13/831,673 dated May 22, 2014, pp. 1-5. |
| Official Communication for U.S. Appl. No. 14/518,996 dated Nov. 20, 2014, pp. 1-41. |
| Official Communication for U.S. Appl. No. 13/831,908 dated Jun. 25, 2014, pp. 1-15. |
| Official Communication for U.S. Appl. No. 14/500,893 dated Nov. 20, 2014, pp. 1-15. |
| Official Communication for U.S. Appl. No. 13/831,908 dated Apr. 9, 2014, pp. 1-3. |
| Official Communication for U.S. Appl. No. 13/831,908 dated Aug. 9, 2013, pp. 1-29. |
| Official Communication for U.S. Appl. No. 13/831,908 dated Jan. 13, 2014, pp. 1-31. |
| Official Communication for U.S. Appl. No. 14/107,631 dated Dec. 30, 2014, pp. 1-12. |
| Handel et al. “Hiding Data in the OSI Network Model,” Los Alamos, New Mexico, 1996, pp. 1-16. |
| Official Communication for U.S. Appl. No. 14/107,631 dated Feb. 20, 2014, pp. 1-16. |
| Official Communication for U.S. Appl. No. 14/107,631 dated Sep. 26, 2014, pp. 1-14. |
| Handley et al., “Network Intrusion Detection: Evasion, Traffic Normalization, and End-to-End Protocol Semantics,” 2011, International Computer Science Institute, pp. 1-17. |
| Information Sciences Institute, “Internet Protocol Darpa Internet Program Protocol Specification,” Sep. 1981, pp. 1-36. |
| Fuertes, “Evaluation of OSPF Extensions in MANET Routing,” Paris, 2007, pp. 1-192. |
| Parsons, “Moving Across the Internet: Code-Bodies, Code-Corpses, and Network Architecture,” May 9, 2010, pp. 1-20. |
| Zander et al., “Covert Channels and Countermeasures in Computer Network Protocols,” Dec. 2007, pp. 1-7. |
| Official Communication for U.S. Appl. No. 14/500,893 dated Feb. 18, 2015, pp. 1-11. |
| Official Communication for U.S. Appl. No. 14/107,580 dated Mar. 6, 2014, pp. 1-13. |
| Official Communication for U.S. Appl. No. 14/107,580 dated Sep. 15, 2014, pp. 1-15. |
| Official Communication for U.S. Appl. No. 14/107,580 dated Mar. 17, 2015, pp. 1-5. |
| Official Communication for U.S. Appl. No. 11/679,356 dated Jun. 22, 2009, pp. 1-21. |
| Official Communication for U.S. Appl. No. 11/679,356 dated Dec. 11, 2009, pp. 1-23. |
| Official Communication for U.S. Appl. No. 11/679,356 dated Feb. 22, 2010, pp. 1-3. |
| Official Communication for U.S. Appl. No. 11/679,356 dated Sep. 9, 2010, pp. 1-16. |
| Official Communication for U.S. Appl. No. 11/679,356 dated Mar. 4, 2011, pp. 1-15. |
| Official Communication for U.S. Appl. No. 15/014,932 dated Jun. 10, 2016, pp. 1-20. |
| Official Communication for U.S. Appl. No. 15/014,932 dated Dec. 14, 2016, pp. 1-26. |
| Digital Imaging and Communications in Medicine (DICOM), Part 6: Data Dictionary, PS 3.6-2011. 2011, http://dicom.nema.org/Dicom/2011 /11_06pu.pdf, pp. 1-255. |
| Health Level Seven, Version 2.6, Appendix A. Nov. 2007, https://www.hl7.org/special/committees/vocab/V26_Appendix_A.pdf, p. 1-216. |
| Official Communication for U.S. Appl. No. 15/207,213 dated Jun. 1, 2017, pp. 1-24. |
| Official Communication for U.S. Appl. No. 15/207,213 dated May 8, 2017, pp. 1-5. |
| Official Communication for U.S. Appl. No. 15/207,213 dated Feb. 23, 2017, pp. 1-24. |
| Official Communication for U.S. Appl. No. 15/207,213 dated Oct. 25, 2016, pp. 1-18. |
| Official Communication for U.S. Appl. No. 15/014,932 dated Aug. 1, 2017, pp. 1-27. |
| Official Communication for U.S. Appl. No. 15/690,135 dated Jan. 18, 2018, pp. 1-6. |
| Office Communication for U.S. Appl. No. 15/892,327 dated Apr. 23, 2018, pp. 1-35. |
| Official Communication for U.S. Appl. No. 16/107,509 dated Jun. 14, 2019, pp. 1-6. |
| Official Communication for U.S. Appl. No. 16/384,574 dated May 31, 2019, pp. 1-44. |
| Official Communication for U.S. Appl. No. 16/107,509 dated Oct. 26, 2018, pp. 1-44. |
| Official Communication for U.S. Appl. No. 16/107,509 dated Aug. 21, 2019, pp. 1-54. |
| Official Communication for U.S. Appl. No. 16/384,574 dated Oct. 8, 2019, pp. 1-60. |
| Official Communication for U.S. Appl. No. 16/543,243 dated Sep. 27, 2019, pp. 1-45. |
| Official Communication for U.S. Appl. No. 16/048,939 dated Dec. 5, 2019, pp. 1-15. |
| Official Communication for U.S. Appl. No. 16/565,109 dated Nov. 27, 2019, pp. 1-31. |
| Official Communication for U.S. Appl. No. 16/525,290 dated Oct. 31, 2019, pp. 1-17. |
| Official Communication for U.S. Appl. No. 16/532,275 dated Oct. 24, 2019, pp. 1-42. |
| Official Communication for U.S. Appl. No. 16/560,886 dated Dec. 6, 2019, pp. 1-45. |
| Official Communication for U.S. Appl. No. 14/500,893 dated Feb. 18, 2015, pp. 1-13. |
| Official Communication for U.S. Appl. No. 14/518,996 dated Apr. 20, 2015, pp. 1-53. |
| Official Communication for U.S. Appl. No. 14/500,893 dated Jun. 15, 2015, pp. 1-14. |
| Official Communication for U.S. Appl. No. 14/518,996 dated Jul. 21, 2015, pp. 1-28. |
| Official Communication for U.S. Appl. No. 14/695,690 dated Sep. 9, 2015, pp. 1-72. |
| Official Communication for U.S. Appl. No. 14/695,690 dated Feb. 24, 2016, pp. 1-32. |
| Official Communication for U.S. Appl. No. 15/150,354 dated Jul. 5, 2016, pp. 1-28. |
| Mozilla Developer Network, “NSS Key Log Format,” https://developer.mozilla.org/en-US/docs/Mozilla/Projects/NSS/Key_Log_Format, Jan. 8, 2010, p. 1. |
| European Search Report for EP Application No. 16166907 dated Sep. 14, 2016, pp. 1-7. |
| Official Communication for U.S. Appl. No. 15/150,354 dated Feb. 8, 2017, pp. 1-18. |
| Official Communication for U.S. Appl. No. 15/466,248 dated Jun. 5, 2017, pp. 1-90. |
| Official Communication for U.S. Appl. No. 15/466,248 dated Oct. 3, 2017, pp. 1-91. |
| Official Communication for U.S. Appl. No. 15/457,886 dated Jan. 5, 2018, pp. 1-20. |
| Official Communication for U.S. Appl. No. 15/466,248 dated Jan. 11, 2018, pp. 1-4. |
| European Exam Report for EP Application No. 16166907 dated Mar. 9, 2018, pp. 1-4. |
| Shaver, “Decrypting TLS Browser Traffic with Wireshark the easy way”, https://jimshaver.net/2015/02/11/decrypting-tls-browser-traffic-with-wireshark-the-easy-way/, Feb. 11, 2015, pp. 1-30. |
| Official Communication for U.S. Appl. No. 15/466,248 dated Mar. 8, 2018, pp. 1-108. |
| Official Communication for U.S. Appl. No. 15/457,886 dated Jul. 18, 2018, pp. 1-23. |
| Official Communication for U.S. Appl. No. 15/466,248 dated Jul. 11, 2018, pp. 1-299. |
| International Search Report and Written Opinion for PCT/US2017/068585 dated Jul. 4, 2018, pp. 1-11. |
| European Search Report for EP Application No. 17210995.1 dated Jul. 6, 2018, pp. 1-11. |
| Official Communication for U.S. Appl. No. 15/466,248 dated Oct. 18, 2018, pp. 1-303. |
| Official Communication for U.S. Appl. No. 15/457,886 dated Mar. 20, 2019, pp. 1-22. |
| Official Communication for U.S. Appl. No. 15/466,248 dated May 16, 2019, pp. 1-304. |
| Official Communication for U.S. Appl. No. 15/466,248 dated Sep. 10, 2019, pp. 1-39. |
| Official Communication for U.S. Appl. No. 15/971,843 dated Oct. 22, 2019, pp. 1-31. |
| Official Communication for U.S. Appl. No. 14/750,905 dated Sep. 22, 2015, pp. 1-10. |
| Official Communication for U.S. Appl. No. 14/750,905 dated Jan. 19, 2016, pp. 1-16. |
| Official Communication for U.S. Appl. No. 15/082,925 dated Sep. 13, 2016, pp. 1-8. |
| Official Communication for U.S. Appl. No. 15/289,760 dated Dec. 12, 2016, pp. 1-23. |
| Official Communication for U.S. Appl. No. 15/219,016 dated Nov. 22, 2016, pp. 1-13. |
| Official Communication for U.S. Appl. No. 15/356,381 dated Jan. 6, 2017, pp. 1-66. |
| Official Communication for U.S. Appl. No. 15/082,925 dated Feb. 1, 2017, pp. 1-16. |
| Official Communication for U.S. Appl. No. 15/219,016 dated Mar. 16, 2017, pp. 1-13. |
| Official Communication for U.S. Appl. No. 15/443,868 dated Apr. 27, 2017, pp. 1-14. |
| Official Communication for U.S. Appl. No. 15/585,887 dated Jun. 27, 2017, pp. 1-54. |
| Official Communication for U.S. Appl. No. 15/356,381 dated Jul. 3, 2017, pp. 1-49. |
| Official Communication for U.S. Appl. No. 15/675,216 dated Jun. 7, 2018, pp. 1-5. |
| Official Communication for U.S. Appl. No. 15/443,868 dated Aug. 11, 2017, pp. 1-21. |
| Official Communication for U.S. Appl. No. 15/675,216 dated Nov. 20, 2017, pp. 1-10. |
| Official Communication for U.S. Appl. No. 15/585,887 dated Nov. 28, 2017, pp. 1-29. |
| International Search Report and Written Opinion for PCT/US2018/030145 dated Aug. 10, 2018, pp. 1-12. |
| Svoboda et al., “Network Traffic Analysis with Deep Packet Inspection Method”, pp. 1-148. |
| International Search Report and Written Opinion for PCT/US2017/068586 dated Aug. 9, 2018, pp. 1-14. |
| European Search Report for EP Application No. 17210996 dated Jun. 13, 2018, pp. 1-7. |
| Official Communication for U.S. Appl. No. 15/855,769 dated Feb. 5, 2019, pp. 1-21. |
| Official Communication for U.S. Appl. No. 15/855,769 dated May 1, 2019, pp. 1-20. |
| Official Communication for U.S. Appl. No. 16/459,472 dated Aug. 14, 2019, pp. 1-24. |
| Official Communication for U.S. Appl. No. 15/585,887 dated Mar. 20, 2019, pp. 1-35. |
| Official Communication for U.S. Appl. No. 15/675,216 dated Aug. 28, 2018, pp. 1-21. |
| Office Communication for U.S. Appl. No. 16/718,050 dated Feb. 27, 2020, pp. 1-22. |
| Wade, Susan Marie, “SCADA Honeynets: The attractiveness of honeypots as critical infrastructure security tools for the detection and analysis of advanced threats” (2011). Graduate Theses and Dissertations. 12138. https://lib.dr.iastate.edu/etd/12138, pp. 1-67. |
| Office Communication for U.S. Appl. No. 16/525,290 dated Mar. 12, 2020, pp. 1-11. |
| Office Communication for U.S. Appl. No. 15/971,843 dated Mar. 26, 2020, pp. 1-14. |
| Office Communication for U.S. Appl. No. 16/048,939 dated Mar. 26, 2020, pp. 1-6. |
| Office Communication for U.S. Appl. No. 16/543,243 dated Apr. 7, 2020, pp. 1-22. |
| Office Communication for U.S. Appl. No. 16/532,275 dated Apr. 20, 2020, pp. 1-8. |
| Office Communication for U.S. Appl. No. 16/560,886 dated Apr. 22, 2020, pp. 1-10. |
| Office Communication for U.S. Appl. No. 16/565,109 dated May 8, 2020, pp. 1-19. |
| European Examination Report for European Patent Application No. 16166907.2 dated Dec. 19, 2019, pp. 1-6. |
| European Examination Report for European Patent Application No. 17210996.9 dated May 27, 2020, pp. 1-3. |
| Office Communication for U.S. Appl. No. 15/585,887 dated Aug. 28, 2020, pp. 1-30. |
| Office Communication for U.S. Appl. No. 16/679,055 dated Sep. 4, 2020, pp. 1-5. |
| Office Communication for U.S. Appl. No. 16/718,050 dated Sep. 4, 2020, pp. 1-23. |
| Office Communication for U.S. Appl. No. 16/525,290 dated Sep. 23, 2020, pp. 1-10. |
| International Search Report and Written Opinion for PCT/US2019/030015 dated Aug. 7, 2019, pp. 1-6. |
| International Search Report and Written Opinion for PCT/US2019/018097 dated May 28, 2019, pp. 1-9. |
| Office Communication for U.S. Appl. No. 15/014,932 dated May 15, 2018, pp. 1-27. |
| Office Communication for U.S. Appl. No. 15/891,273 dated Jun. 19, 2018, pp. 1-23. |
| Office Communication for U.S. Appl. No. 15/014,932 dated Jul. 16, 2018, pp. 1-16. |
| Office Communication for U.S. Appl. No. 15/690,135 dated May 22, 2018, pp. 1-7. |
| Office Communication for U.S. Appl. No. 15/984,197 dated Aug. 31, 2018, pp. 1-60. |
| Official Communication for U.S. Appl. No. 16/048,939 dated Sep. 19, 2018, pp. 1-36. |
| Official Communication for U.S. Appl. No. 15/891,311 dated Sep. 24, 2018, pp. 1-16. |
| Official Communication for U.S. Appl. No. 16/112,442 dated Nov. 6, 2018, pp. 1-44. |
| Official Communication for U.S. Appl. No. 15/014,932 dated Nov. 23, 2018, pp. 1-22. |
| Official Communication for U.S. Appl. No. 16/100,116 dated Nov. 15, 2018, pp. 1-44. |
| Official Communication for U.S. Appl. No. 15/891,273 dated Jan. 15, 2019, pp. 1-35. |
| Official Communication for U.S. Appl. No. 15/891,311 dated Jan. 29, 2019, pp. 1-8. |
| Official Communication for U.S. Appl. No. 16/174,051 dated Jan. 29, 2019, pp. 1-83. |
| Official Communication for U.S. Appl. No. 15/671,060 dated May 8, 2019, pp. 1-16. |
| Official Communication for U.S. Appl. No. 15/891,273 dated May 28, 2019, pp. 1-16. |
| Official Communication for U.S. Appl. No. 16/048,939 dated Jun. 20, 2019, pp. 1-8. |
| Official Communication for U.S. Appl. No. 16/100,116 dated May 30, 2019, pp. 1-13. |
| Official Communication for U.S. Appl. No. 16/107,509 dated Apr. 1, 2019, pp. 1-63. |
| Official Communication for U.S. Appl. No. 16/113,442 dated Jun. 5, 2019, pp. 1-7. |
| Official Communication for U.S. Appl. No. 15/675,216 dated Jan. 29, 2019, pp. 1-18. |
| Official Communication for U.S. Appl. No. 16/384,574 dated Jan. 13, 2020, pp. 1-23. |
| Official Communication for U.S. Appl. No. 16/107,509 dated Jan. 23, 2020, pp. 1-39. |
| Official Communication for U.S. Appl. No. 15/585,887 dated Jan. 22, 2020, pp. 1-34. |
| Official Communication for U.S. Appl. No. 16/384,697 dated Oct. 17, 2019, pp. 1-33. |
| Official Communication for U.S. Appl. No. 16/459,472 dated Feb. 3, 2020, pp. 1-18. |
| Official Communication for U.S. Appl. No. 16/679,055 dated Feb. 14, 2020, pp. 1-32. |
| Official Communication for U.S. Appl. No. 16/048,939 dated Feb. 18, 2020, pp. 1-6. |
| Number | Date | Country | |
|---|---|---|---|
| 20200382529 A1 | Dec 2020 | US |
