Patent Grant
11223651
The present invention relates generally to the field of network security, and more particularly to programmatic counter measures to isolate suspicious activity and elicit information about said activity.
Network security covers a variety of computer networks, both public and private, that are used in everyday jobs; conducting transactions and communications among businesses, government agencies and individuals. Networks can be private, such as within a company, and other networks might be open to public access. Network security is involved in organizations, enterprises, and other types of institutions.
Big data is a term associated with the harvest and analysis of large data-sets to be utilized to extract useful information in the fields the data is related to. Current usage of big data tends to involve predictive analytics to predict individual user behavior, financial market trends, and other valuable predictions in various industries. Analysis of large data sets can lead to the discovery of correlations between various factors that may otherwise seem entirely independent from a human perspective alone.
In computers and computer networks an attack is any attempt to expose, alter, disable, destroy, steal or gain unauthorized access to, or make unauthorized use of, a computer asset. A cyber-attack is any type of offensive maneuver that targets computer information systems, infrastructures, computer networks, and/or personal computer devices. An attacker is a suspicious person, or process, that attempts to access data, functions or other restricted areas of a system without prior authorization.
According to an aspect of the present invention, there is a method, computer program product and/or system for use with a plurality of server computers grouped into a plurality of management instances, including at least a first management instance, where each management instance includes at least one server computer, that performs the following operations (not necessarily in the following order): (i) receiving, by the first management instance, a first resource request from a first external client over a computer network; (ii) determining, by machine logic, that the first resource request is related to a suspected cyberattack; (iii) creating a second management instance, with the second management instance tasked exclusively with processing resource requests determined to be related to suspected cyberattacks according to a set of isolation rules; (iv) redirecting the first resource request to the second management instance, including notifying the first external client that the first resource request has been redirected to the second management instance; (v) processing the first resource request according to the set of isolation rules; (vi) outputting a resource request response, with the resource request response based, at least in part, on the set of isolation rules; and (vii) collecting a suspected cyber attacker data set based, at least in part, on the outputted resource request response.
Embodiments of the present invention describe technology for isolating suspicious activity on a plurality of servers for the purpose of mitigating damage (for example, unauthorized access to server data) to a network of computers and eliciting information about any suspicious clients involved in the suspicious activity. A suspicious client is identified, isolated, and permitted to continue interacting with the computer network to elicit information about the activity (for example, the identify of a suspicious client). Suspicious activity may be defined by one or more entities with authorized access to a network and determined using conventional techniques. The suspicious activity is isolated to prevent the suspicious client(s) from unauthorized and/or harmful actions on the network. The suspicious client(s) are permitted to resume network requests, in isolation, to covertly elicit information about the suspicious activity. Any data collected about the suspicious activity and/or suspicious client(s) are output, during and/or after the suspicious client(s) have disconnected from the network, for analysis. This Detailed Description section is divided into the following sub-sections: (i) The Hardware and Software Environment; (ii) Example Embodiment; (iii) Further Comments and/or Embodiments; and (iv) Definitions.
The present invention may be a system, a method, and/or a computer program product. The computer program product may include a computer readable storage medium (or media) having computer readable program instructions thereon for causing a processor to carry out aspects of the present invention.
The computer readable storage medium can be a tangible device that can retain and store instructions for use by an instruction execution device. The computer readable storage medium may be, for example, but is not limited to, an electronic storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, a semiconductor storage device, or any suitable combination of the foregoing. A non-exhaustive list of more specific examples of the computer readable storage medium includes the following: a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), a static random access memory (SRAM), a portable compact disc read-only memory (CD-ROM), a digital versatile disk (DVD), a memory stick, a floppy disk, a mechanically encoded device such as punch-cards or raised structures in a groove having instructions recorded thereon, and any suitable combination of the foregoing. A computer readable storage medium, as used herein, is not to be construed as being transitory signals per se, such as radio waves or other freely propagating electromagnetic waves, electromagnetic waves propagating through a waveguide or other transmission media (e.g., light pulses passing through a fiber-optic cable), or electrical signals transmitted through a wire.
Computer readable program instructions described herein can be downloaded to respective computing/processing devices from a computer readable storage medium or to an external computer or external storage device via a network, for example, the Internet, a local area network, a wide area network and/or a wireless network. The network may comprise copper transmission cables, optical transmission fibers, wireless transmission, routers, firewalls, switches, gateway computers and/or edge servers. A network adapter card or network interface in each computing/processing device receives computer readable program instructions from the network and forwards the computer readable program instructions for storage in a computer readable storage medium within the respective computing/processing device.
Computer readable program instructions for carrying out operations of the present invention may be assembler instructions, instruction-set-architecture (ISA) instructions, machine instructions, machine dependent instructions, microcode, firmware instructions, state-setting data, or either source code or object code written in any combination of one or more programming languages, including an object oriented programming language such as Smalltalk, C++ or the like, and conventional procedural programming languages, such as the “C” programming language or similar programming languages. The computer readable program instructions may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider). In some embodiments, electronic circuitry including, for example, programmable logic circuitry, field-programmable gate arrays (FPGA), or programmable logic arrays (PLA) may execute the computer readable program instructions by utilizing state information of the computer readable program instructions to personalize the electronic circuitry, in order to perform aspects of the present invention.
Aspects of the present invention are described herein with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer readable program instructions.
These computer readable program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks. These computer readable program instructions may also be stored in a computer readable storage medium that can direct a computer, a programmable data processing apparatus, and/or other devices to function in a particular manner, such that the computer readable storage medium having instructions stored therein comprises an article of manufacture including instructions which implement aspects of the function/act specified in the flowchart and/or block diagram block or blocks.
The computer readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other device to cause a series of operational steps to be performed on the computer, other programmable apparatus or other device to produce a computer implemented process, such that the instructions which execute on the computer, other programmable apparatus, or other device implement the functions/acts specified in the flowchart and/or block diagram block or blocks.
The flowchart and block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of instructions, which comprises one or more executable instructions for implementing the specified logical function(s). In some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be accomplished as one step, executed concurrently, substantially concurrently, in a partially or wholly temporally overlapping manner, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems that perform the specified functions or acts or carry out combinations of special purpose hardware and computer instructions.
An embodiment of a possible hardware and software environment for software and/or methods according to the present invention will now be described in detail with reference to the Figures.
Sub-system 102 is, in many respects, representative of the various computer sub-system(s) in the present invention. Accordingly, several portions of sub-system 102 will now be discussed in the following paragraphs.
Sub-system 102 may be a laptop computer, tablet computer, netbook computer, personal computer (PC), a desktop computer, a personal digital assistant (PDA), a smart phone, or any programmable electronic device capable of communicating with the client sub-systems via network 114. Program 300 is a collection of machine readable instructions and/or data that is used to create, manage and control certain software functions that will be discussed in detail, below, in the Example Embodiment sub-section of this Detailed Description section.
Sub-system 102 is capable of communicating with other computer sub-systems via network 114. Network 114 can be, for example, a local area network (LAN), a wide area network (WAN) such as the Internet, or a combination of the two, and can include wired, wireless, or fiber optic connections. In general, network 114 can be any combination of connections and protocols that will support communications between server and client sub-systems.
Sub-system 102 is shown as a block diagram with many double arrows. These double arrows (no separate reference numerals) represent a communications fabric, which provides communications between various components of sub-system 102. This communications fabric can be implemented with any architecture designed for passing data and/or control information between processors (such as microprocessors, communications and network processors, etc.), system memory, peripheral devices, and any other hardware components within a system. For example, the communications fabric can be implemented, at least in part, with one or more buses.
Memory 208 and persistent storage 210 are computer-readable storage media. In general, memory 208 can include any suitable volatile or non-volatile computer-readable storage media. It is further noted that, now and/or in the near future: (i) external device(s) 214 may be able to supply, some or all, memory for sub-system 102; and/or (ii) devices external to sub-system 102 may be able to provide memory for sub-system 102.
Program 300 is stored in persistent storage 210 for access and/or execution by one or more of the respective computer processors 204, usually through one or more memories of memory 208. Persistent storage 210: (i) is at least more persistent than a signal in transit; (ii) stores the program (including its soft logic and/or data), on a tangible medium (such as magnetic or optical domains); and (iii) is substantially less persistent than permanent storage. Alternatively, data storage may be more persistent and/or permanent than the type of storage provided by persistent storage 210.
Program 300 may include both machine readable and performable instructions and/or substantive data (that is, the type of data stored in a database). In this particular embodiment, persistent storage 210 includes a magnetic hard disk drive. To name some possible variations, persistent storage 210 may include a solid state hard drive, a semiconductor storage device, read-only memory (ROM), erasable programmable read-only memory (EPROM), flash memory, or any other computer-readable storage media that is capable of storing program instructions or digital information.
The media used by persistent storage 210 may also be removable. For example, a removable hard drive may be used for persistent storage 210. Other examples include optical and magnetic disks, thumb drives, and smart cards that are inserted into a drive for transfer onto another computer-readable storage medium that is also part of persistent storage 210.
Communications unit 202, in these examples, provides for communications with other data processing systems or devices external to sub-system 102. In these examples, communications unit 202 includes one or more network interface cards. Communications unit 202 may provide communications through the use of either or both physical and wireless communications links. Any software modules discussed herein may be downloaded to a persistent storage device (such as persistent storage device 210) through a communications unit (such as communications unit 202).
I/O interface set 206 allows for input and output of data with other devices that may be connected locally in data communication with worker server 200. For example, I/O interface set 206 provides a connection to external device set 214. External device set 214 will typically include devices such as a keyboard, keypad, a touch screen, and/or some other suitable input device. External device set 214 can also include portable computer-readable storage media such as, for example, thumb drives, portable optical or magnetic disks, and memory cards. Software and data used to practice embodiments of the present invention, for example, program 300, can be stored on such portable computer-readable storage media. In these embodiments the relevant software may (or may not) be loaded, in whole or in part, onto persistent storage device 210 via I/O interface set 206. I/O interface set 206 also connects in data communication with display device 212.
Display device 212 provides a mechanism to display data to a user and may be, for example, a computer monitor or a smart phone display screen.
The programs described herein are identified based upon the application for which they are implemented in a specific embodiment of the invention. However, it should be appreciated that any particular program nomenclature herein is used merely for convenience, and thus the invention should not be limited to use solely in any specific application identified and/or implied by such nomenclature.
The descriptions of the various embodiments of the present invention have been presented for purposes of illustration, but are not intended to be exhaustive or limited to the embodiments disclosed. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the described embodiments. The terminology used herein was chosen to best explain the principles of the embodiments, the practical application or technical improvement over technologies found in the marketplace, or to enable others of ordinary skill in the art to understand the embodiments disclosed herein.
Processing begins at operation S255, where shared queue data store mod 302 receives a first request through a first request server 116 of
Processing proceeds to operation S260 of
Processing proceeds to operation S265 of
Processing proceeds to operation S270 of
Processing proceeds to operation S275 of
Processing proceeds to operation S280 of
Processing proceeds to operation S285 of
Data may also be accumulated about confederates of the suspicious client. In this simplified embodiment, second client 112 of
Processing proceeds to operation S290 of
Some embodiments of the present invention recognize the following facts, potential problems and/or potential areas for improvement with respect to the current state of the art: (i) a server accessible to outside communication is often attacked, to either: (a) disable the server, or (b) cause the server to perform unauthorized and/or harmful work; (ii) server attacks are especially dangerous when the server manages real computing resources to host thousands of servers, a level of privilege typically unavailable to the majority of servers; and (iii) current solutions (e.g. firewalls) are designed to end the attack and/or insulate the server from the current attack or attacks that closely resemble the current attack in a very narrow sense.
Some embodiments of the present invention may include one, or more, of the following features, characteristics and/or advantages: (i) counter-attack against attackers in order to gather information from attackers for such purposes as: (a) identify attackers, and (b) identify confederates, (c) detect future attacks in a more sophisticated manner, (d) establish defense mechanisms to deter future attacks, (e) establish defense mechanisms to prevent future attacks, and (f) counter-attack measures are accomplished while expeditiously rendering the original attack moot; (ii) a Management Application Instance (MAI) comprises: (a) Request Servers that receive requests from clients, (b) Worker Servers that process requests, (c) Response Servers that respond to requests, and (d) Shared Queues that are a communication mechanism used for internal communication among all servers that comprise an MAI, where all servers may place or remove an item from the queue (e.g. for reading); (iii) a single MAI may contain any number of any server type, and any number of shared queues; (iv) various MAI configurations may be used, such as: (a) two MAIs (MAI A and MAI B), (b) MAI A comprises two request servers (one public, one private), three worker servers, two response servers, and one shared queue (PUBLIC), (c) MAI B comprises zero request servers, two worker servers, and one shared queue (PUBLIC), and (d) PUBLIC is a shared queue accessible to all servers on MAIs A and B; (v) By default, a request to MAI A is processed completely by MAI A; (vi) Each MAI has the capability of “pushing” information to its clients; (vii) “Pushing” information includes the capability to inform clients that the MAI's public request location has moved, this capability are typically used in situations such as: (a) hardware and/or software upgrades, (b) hardware and/or software failures, and (c) load balancing; (viii) MAI B workers constantly monitor PUBLIC; (ix) If MAI B detects suspicious activity on PUBLIC such as an unusual amount or unusual mix of activity, then: (a) a new request server is created (or drawn from a pool) for each client, (b) the client is directed to the new request server, (c) the new request server may have new worker servers, or existing worker servers could be utilized, (d) if a suspicious client request server is provided worker servers distinct from any worker servers of all other request servers, all unsuspicious clients are insulated from any suspicious client activity, (e) suspicious clients may be allowed to continue making requests to the insulated MAI, and (f) suspicious client requests to the MAI can be used to gather information about suspicious clients; and (x) the insulated MAI may take actions, such as: (a) pretend to execute suspicious client requests, (b) pretend to give selective errors to suspicious client requests, and/or (c) vary the amount of time to process suspicious client requests.
Some embodiments of the present invention may include one, or more, of the following features, characteristics and/or advantages: (i) willing confederates of suspicious clients can be recognized by watching for activity based on responses given exclusively to the suspicious client, such as: (a) a suspicious client gets a notification that its request server is being serviced, and thus a new request server is being provided, subsequently a willing confederate attempts to use the new request server, (b) a suspicious client is notified that its request to create a new server has been “successful”, subsequently a willing confederate attempts to modify the new server, (c) a suspicious client attempts to power on a server known to it, but receives a notification that the suspicious client is not authorized to power on that server, subsequently a willing confederate attempts to power on that server, (d) a suspicious client makes a very large number of requests which all “succeed,” but each request takes ten times as long as the previous one, after the requests pass a certain threshold in time, a willing confederate dramatically ups the pace of its requests, (e) a suspicious client obtains the authorization key for disk space owned by a particular server, subsequently a willing confederate attempts to use the key that the suspicious client obtained, (f) a suspicious client adds network ports to a server it has created, subsequently a willing confederate attempts to use the new network ports, and/or (g) a suspicious client is notified that new management APIs are available to it, subsequently a willing confederate attempts to use the new APIs; (ii) confederates of suspicious clients may be directed to an insulated MAI and subjected to actions such as: (a) pretend to execute requests, (b) pretend to give selective errors to requests, and/or (c) vary the amount of time to process requests; (iii) an apparent legitimate client may, unwillingly, carry out suspicious activity that is later exploited by a suspicious client or willing confederate, then the legitimate client may, in fact, be an unwilling confederate, such as: (a) a legitimate client (i.e., unwilling confederate) gets a notification that its request server is being serviced, and thus a new request server is being provided, subsequently a suspicious client and/or willing confederate attempts to use the new request server, (b) a legitimate client (i.e., unwilling confederate) is notified that its request to create a new server has been successful, subsequently a suspicious client and/or willing confederate attempts to modify the new server, (c) a legitimate client (i.e., unwilling confederate) obtains the authorization key for disk space owned by a particular server, subsequently a suspicious client and/or willing confederate attempts to use the key that the unwilling confederate obtained, (d) a legitimate client (i.e., unwilling confederate) adds network ports to a server it has created, subsequently a suspicious client and/or willing confederate attempts to use the new network ports, and (e) a legitimate client (i.e., unwilling confederate) is notified that new management APIs are available to it, subsequently a suspicious client and/or willing confederate attempts to use the new APIs; (iv) both willing and unwilling confederates may be useful in determining the identity and/or origin of a suspicious client; and (v) unwilling confederates may be useful in determining information, such as: (a) how the attack spreads, (b) future attack spreading patterns, (c) future speed of attack spread, and (d) programming paradigm of the suspicious client.
Some embodiments of the present invention may include one, or more, of the following features, characteristics and/or advantages: (i) arbitrary data may be “pushed” to suspicious clients to elicit revealing responses; (ii) arbitrary data is simulated, that is, it is false data pushed to suspicious clients of a type and/or form that the suspicious client would expect to receive from a given request (for example, if a suspicious client requests to create a new virtual machine, the system may respond that the virtual machine has been created without actually creating the virtual machine); (iii) suspicious client activity may be sent to an intelligent engine for analysis to determine methods to elicit more information; and (iv) the MAIs client's view of the managed system is encapsulated by the MAI and enables opportunity beyond merely shutting down an attack, such as: (a) identification of attack perpetrators, and/or (b) identification of strategies to establish defense mechanisms to detect, deter, and prevent future attacks.
Some embodiments of the present invention may include one, or more, of the following features, characteristics and/or advantages: (i) attackers may be identified if a client issues too many “malformed” requests over a given timeframe, that client would be considered an attacker; (ii) these criteria could apply to different uses for the servers described, such as: (a) a malformed request to a system management API is one where the data provided in the request is not consistent with a valid system management API call, (b) a malformed credit card request is one that gets the 3 to 4 character “security code” wrong, and (c) a malformed request to an email server may be one that qualifies for the spam folder by the spam definition provided to a mail server; (iii) too many requests over a given timeframe could, for example, be defined as “more than 99 over a 5-minute period”; (iv) attackers may be identified by a sequence of requests that don't make sense, such as: (a) for a system management API this could mean a sequence where a request is made to create a server, followed by a request to query the details of that server before the request to create is completed, (b) for a credit card, this could be the use of the same credit card at two restaurants 100 miles apart within ten seconds, and (c) for email, this could be someone sending the same attachment six times in one minute; (v) an attacker may be identified by high frequency, irregular activity; (vi) for all applications cited previously, this would be more requests from a single client per unit time than is reasonable; (vii) attackers may be identified by policy violations per unit time, such as: (a) for a system management API, a policy violation could be exceeding the client limits for CPU, and/or memory, and/or disk, (b) for a credit card, a policy violation could be exceeding the card's credit limit, and (c) for an email, a policy violation could be sending an attachment that is too large; (viii) an attacker may be identified, and isolated, based on a confidence level dependent response, such as: (a) if a system management API server received 50 malformed requests in five minutes, the recipient system management API server could slow down the server response, or (b) for 100 malformed requests, the recipient system management API server might not execute the function and return fake responses; (ix) an appropriate confidence level depends on the “job” that the MAI is doing; (x) what constitutes suspicious activity for a system management API is different than what constitutes suspicious activity for a credit card or email address; (xi) the confidence level is based on the type of “violation” as well as the application for which that violation is experienced; and (xii) if a legitimate user was improperly identified and treated as an attacker, the means to discover and correct improper identification depend on the violation and the application for which that violation is experienced, such as: (a) for a credit card, this might require a call or message to the credit card company, the action would be to re-enable the card to work, (b) for a system management API, this may require some “out-of-band” communication, and the action may be to execute the requests that were faked or speed up request processing for the client, and (c) for email, this may require some “out-of-band” activity, the action may be analogous to that with a system management API.
Some embodiments of the present invention may include one, or more, of the following features, characteristics and/or advantages: (i) the MAI mechanism to pretend to execute suspicious client request, or pushing arbitrary data, is doing what the servers already do, which is to give responses, while not actually performing any function, but still logging the request (for example, for a system management API, if the request were to be to create a server definition, a response to the request may say the server was created, while not actually updating the virtual configuration); (ii) a mechanism to enable the collection of as much available data as possible which may later be used to reduce or analyze data; (iii) gather as much data as possible over as wide a range of situations as possible about the attacker; and (iv) gathered data may be used with “big data” analytic software that identifies correlations in non-structured data and would have a good chance to discover correlations that a person may not see, or could not see because a human could not process that much data.
Some embodiments of the present invention may include one, or more, of the following features, characteristics and/or advantages: (i) allows continuing access, but surreptitiously isolates the offending client and surreptitiously elicits information from the client, and any confederates, while encouraging suspicious clients to “stay on the line”; (ii) surreptitiously continuing suspicious client access and exploiting that access to defend against the client and any confederates; (iii) monitors clients programmatically; (iv) programmatically and surreptitiously isolate the offending/suspicious clients; (v) programmatically and surreptitiously eliciting information from the client, and any confederates, while encouraging them to “stay on the line”; (vi) programmatically and surreptitiously exploiting suspicious clients to defend against the client and any confederates; (vii) allows all data to be passed; (viii) surreptitiously isolates the suspicious client and surreptitiously elicits information from the client, and any confederates, while encouraging them to “stay on the line”; (ix) does not delete data, data is used to programmatically and surreptitiously exploit the suspicious client to defend against the suspicious client and any confederates; (x) monitors clients at the application request level; (xi) programmatically and surreptitiously isolates the offending client, and programmatically and surreptitiously elicits information from the client, and any confederates, while encouraging them to “stay on the line”; (xii) starts from a higher semantic level and is able to take action at a higher semantic level; (xiii) monitoring, interpretation of communication, and eliciting of information is the core; (xiv) in addition to isolation, elements of embodiments of the present invention build upon isolation; and (xv) a tangible implementation of security issues.
Some embodiments of the present invention may include one, or more, of the following features, characteristics and/or advantages: (i) a configuration file to determine which MAI is responsible for which activities (i.e. determines how the novel techniques are coordinated); (ii) all MAIs communicate with other MAIs via a common communication layer (for example, a shared queue); (iii) communication with clients is handled by request and response servers via a standard communication protocol, such as: (a) TCP/IP, and (b) UDP, etc.; (iv) all requests, at some point, interact with the communication later, thus all requests can be viewed by all MAIs; (v) not all MAIs may be authorized to handle a request; (vi) rerouting a request may include actions, such as: (a) authorizing and/or unauthorizing request and/or response servers to handle particular clients, and (b) authorizing and/or unauthorizing worker servers to handle particular requests; and/or (vii) a MAI configured to determine whether requests and/or clients are suspicious includes the capability to authorize and/or unauthorize request, response and/or worker servers.
Some embodiments of the present invention may implement a method for gathering information about an entity attacking (e.g., attempting to hack into, or gain unauthorized access to) a computing device and/or server which includes some or all of the following steps (not necessarily in the following order): (i) receiving a request from an entity to access and/or utilize a computing device and/or server; (ii) determining that the request exceeds a suspicion threshold; (iii) rerouting the request such that the request is processed (or otherwise handled) with increased isolation (for example, there could be a server that is isolated from actual (i.e., legitimate) client data and/or activity); (iv) subsequent to rerouting the request, gathering information about entity interaction; and (v) recording the gathered information.
Some embodiments of the present invention may implement a method for gathering information about an entity attacking (e.g., attempting to hack into, or gain unauthorized access to) a computing device and/or server which includes some or all of the following steps (not necessarily in the following order): (i) receiving a request from an entity to access and/or utilize a computing device and/or server; (ii) determining that the request exceeds a suspicion threshold; (iii) rerouting the request such that the request is processed (or otherwise handled) with increased isolation (for example, there could be a server that is isolated from actual (i.e., legitimate) client data and/or activity); (iv) subsequent to rerouting the request, gathering information about entity interaction; (v) recording the gathered information; (vi) performing an action; and (vii) monitoring entity interaction.
Some embodiments of the present invention may implement a method for gathering information about an entity attacking (e.g., attempting to hack into, or gain unauthorized access to) a computing device and/or server which includes some or all of the following steps (not necessarily in the following order): (i) receiving a request from an entity to access and/or utilize a computing device and/or server; (ii) determining that the request exceeds a suspicion threshold; (iii) rerouting the request such that the request is processed (or otherwise handled) with increased isolation (for example, there could be a server that is isolated from actual (i.e., legitimate) client data and/or activity); (iv) subsequent to rerouting the request, gathering information about entity interaction; (v) recording the gathered information; (vi) generating a false result to the request and/or subsequent requests; (vii) generating selected errors; (viii) varying time to process the request and/or subsequent requests; and (ix) generating a response to previous reactions (e.g., to observe responses to a particular sequence of actions).
Some embodiments of the present invention may implement a method for gathering information about an entity attacking (e.g., attempting to hack into, or gain unauthorized access to) a computing device and/or server which includes some or all of the following steps (not necessarily in the following order): (i) receiving a request from an entity to access and/or utilize a computing device and/or server; (ii) determining that the request exceeds a suspicion threshold; (iii) rerouting the request such that the request is processed (or otherwise handled) with increased isolation (for example, there could be a server that is isolated from actual (i.e., legitimate) client data and/or activity); (iv) subsequent to rerouting the request, gathering information about entity interaction; (v) recording the gathered information; (vi) a first set of servers configured to receive requests from clients; (vii) a second set of servers configured to process requests; (viii) a third set of servers configured to responds to requests; and (ix) a shared queue configured for internal communication among the first, second, and third set of servers.
An embodiment of a possible hardware and software environment for software and/or methods according to the present invention will now be described in detail with reference to the Figures.
An embodiment of a possible hardware and software environment for software and/or methods according to the present invention will now be described in detail with reference to the Figures.
Present invention: should not be taken as an absolute indication that the subject matter described by the term “present invention” is covered by either the claims as they are filed, or by the claims that may eventually issue after patent prosecution; while the term “present invention” is used to help the reader to get a general feel for which disclosures herein are believed to potentially be new, this understanding, as indicated by use of the term “present invention,” is tentative and provisional and subject to change over the course of patent prosecution as relevant information is developed and as the claims are potentially amended.
Embodiment: see definition of “present invention” above—similar cautions apply to the term “embodiment.”
and/or: inclusive or; for example, A, B “and/or” C means that at least one of A or B or C is true and applicable.
Including/include/includes: unless otherwise explicitly noted, means “including but not necessarily limited to.”
Receive/provide/send/input/output/report: unless otherwise explicitly specified, these words should not be taken to imply: (i) any particular degree of directness with respect to the relationship between their objects and subjects; and/or (ii) absence of intermediate components, actions and/or things interposed between their objects and subjects.
Without substantial human intervention: a process that occurs automatically (often by operation of machine logic, such as software) with little or no human input; some examples that involve “no substantial human intervention” include: (i) computer is performing complex processing and a human switches the computer to an alternative power supply due to an outage of grid power so that processing continues uninterrupted; (ii) computer is about to perform resource intensive processing, and human confirms that the resource-intensive processing should indeed be undertaken (in this case, the process of confirmation, considered in isolation, is with substantial human intervention, but the resource intensive processing does not include any substantial human intervention, notwithstanding the simple yes-no style confirmation required to be made by a human); and (iii) using machine logic, a computer has made a weighty decision (for example, a decision to ground all airplanes in anticipation of bad weather), but, before implementing the weighty decision the computer must obtain simple yes-no style confirmation from a human source.
Automatically: without any human intervention.
Module/Sub-Module: any set of hardware, firmware and/or software that operatively works to do some kind of function, without regard to whether the module is: (i) in a single local proximity; (ii) distributed over a wide area; (iii) in a single proximity within a larger piece of software code; (iv) located within a single piece of software code; (v) located in a single storage device, memory or medium; (vi) mechanically connected; (vii) electrically connected; and/or (viii) connected in data communication.
Computer: any device with significant data processing and/or machine readable instruction reading capabilities including, but not limited to: desktop computers, mainframe computers, laptop computers, field-programmable gate array (FPGA) based devices, smart phones, personal digital assistants (PDAs), body-mounted or inserted computers, embedded device style computers, application-specific integrated circuit (ASIC) based devices.
| Number | Name | Date | Kind |
|---|---|---|---|
| 5987611 | Freund | Nov 1999 | A |
| 6085224 | Wagner | Jul 2000 | A |
| 6141686 | Jackowski | Oct 2000 | A |
| 20020144157 | Zhao | Oct 2002 | A1 |
| 20110185061 | Chen | Jul 2011 | A1 |
| 20140096229 | Burns | Apr 2014 | A1 |
| 20140298469 | Marion | Oct 2014 | A1 |
| 20160119377 | Goldberg | Apr 2016 | A1 |
| 20160323300 | Boss | Nov 2016 | A1 |
| 20170220796 | Cath | Aug 2017 | A1 |
| 20170310705 | Gopalakrishna | Oct 2017 | A1 |
| 20180139179 | Ettema | May 2018 | A1 |
| 20190058733 | Wright | Feb 2019 | A1 |
| 20200336510 | Li | Oct 2020 | A1 |
| Entry |
|---|
| Shay et al., “Beyond Sunglasses and Spray Paint: A Taxonomy of Surveillance Countermeasures”, Technology and Society (ISTAS), 2013 IEEE International Symposium on, IEEE, 2013. |
| Number | Date | Country | |
|---|---|---|---|
| 20210037054 A1 | Feb 2021 | US |
