Patent Grant
10050997
As various forms of distributed computing, such as cloud computing, have come to dominate the computing landscape, security has become a bottleneck issue that currently prevents the complete migration of various capabilities associated with sensitive data into cloud-based infrastructures, and/or other distributive computing models. This is at least partially because many owners and operators of data centers that provide access to data and other resources are hesitant to allow their data and resources to be accessed, processed, and/or otherwise used, by virtual assets in the cloud.
A major security issue in a cloud computing environment is that vulnerabilities associated with virtual assets are not always known or understood at the time the virtual assets are created and deployed, e.g., instantiated, in a given computing environment and, once deployed, detecting and/or responding to newly identified vulnerabilities through “normal” communications channels associated with the virtual assets can be challenging, if not impossible.
In addition, in some cases, malicious entities can take control of a virtual asset. In these cases, the malicious entity often takes over, or closes down, normal communications channels associated with the virtual asset. Consequently, in some cases, the malicious entity can mask the fact they have taken control of the virtual asset from other entities outside the virtual asset, such as entities deployed by the owner to monitor and enforce security policies. This leaves the malicious entity relatively free to manipulate the virtual asset under its control and access any data used by the virtual asset, with little concern of detection by the legitimate owner of the virtual asset. Even in cases where the legitimate owner of the virtual asset does become aware that the virtual asset has been compromised, if the malicious entity has shut down, or taken control of, the normal communications channels associated with the virtual asset, the malicious entity can thwart any traditional efforts by the legitimate owner to communicate with the virtual asset and/or repair the virtual asset.
What is needed is a method and system for protecting and repairing a virtual asset from damage by potential security threats.
In accordance with one embodiment, a method and system protecting and repairing a virtual asset from damage by potential security threats includes monitoring a current virtual asset for potential security threats with a virtual asset agent running within the current virtual asset. The virtual asset agent runs, in one embodiment, within the current virtual asset and identifies potential security threats that risk compromising virtual asset data to unauthorized computing systems. The method and system determine a severity of the potential security threats that are identified for having gained access into the current virtual asset, according to one embodiment. According to one embodiment, the severity of the potential security threats is related to a content of the virtual asset data. If the severity is greater than a predetermined threshold, the method and system create a new virtual asset with the virtual asset agent and decommissions the current virtual asset, according to one embodiment. In one embodiment, creating the new virtual asset includes one or more of copying the virtual asset data to the new virtual asset, copying one or more application programs hosted by the current virtual asset to the new virtual asset, and copying the virtual asset agent to the new virtual asset to enable the new virtual asset to protect and repair the new virtual asset from damage by potential security threats. The method and system receive, with the new virtual asset, secrets that are associated with the current virtual asset to enable the new virtual asset to continue operations of the current virtual asset, according to one embodiment. For example, upon receiving the secrets of the current virtual asset, the new virtual asset are able to decrypt and encrypt one or more databases and can further establish communications channels previously used by the current virtual asset, according to one embodiment. The secrets received from an asset management computing system and include one or more passwords, passcodes, encryption keys, and any other secrets now known or later developed.
In accordance with one embodiment, a method and system protecting and repairing a first asset from damage by potential security threats includes monitoring the first virtual asset, with an asset management computing system, and determining whether the first virtual asset includes security updates for the potential security threats, according to one embodiment. The first virtual asset includes a virtual asset agent configured to monitor the first virtual asset for the potential security threats and repair the first virtual asset from the damage caused by the potential security threats. If the first virtual asset does not include one or more of the security updates for the potential security threats, the method and system updates the first virtual asset by transmitting the one or more of the security updates to the first virtual asset over a first communication channel from the asset management computing system, according to one embodiment. In various embodiments, the first communication channel is a trusted or secure communication channel. The first communication channel is different, in one embodiment, than a second communication channel that is used by the asset management computing system to transmit and receive information over the Internet, according to one embodiment. The method and system receive notification from the virtual asset agent that the virtual asset agent created a second virtual asset in response to the virtual asset agent detecting intrusion by the potential security threats into the first virtual asset, according to one embodiment. The method and system transmit secrets associated with the first virtual asset to the second virtual asset using the first communication channel thereby enabling the second virtual asset to continue operations of the first virtual asset, according to one embodiment.
Common reference numerals are used throughout the FIGS. and the detailed description to indicate like elements. One skilled in the art will readily recognize that the above figures are examples and that other architectures, modes of operation, orders of operation, and elements/functions can be provided and implemented without departing from the characteristics and features of the invention, as set forth in the claims.
Embodiments will now be discussed with reference to the accompanying figures, which depict one or more exemplary embodiments. Embodiments may be implemented in many different forms and should not be construed as limited to the embodiments set forth herein, shown in the figures, and/or described below. Rather, these exemplary embodiments are provided to allow a complete disclosure that conveys the principles of the invention, as set forth in the claims, to those of skill in the art.
The INTRODUCTORY SYSTEM, HARDWARE ARCHITECTURE, and PROCESS sections herein include systems and processes suitable for protecting and repairing a virtual asset from damage by potential security threats, according to various embodiments.
Introductory System
Herein, the term “production environment” includes the various components, or assets, used to deploy, implement, access, and use, a given application as that application is intended to be used. In various embodiments, production environments include multiple assets that are combined, communicatively coupled, virtually and/or physically connected, and/or associated with one another, to provide the production environment implementing the application.
As specific illustrative examples, the assets making up a given production environment can include, but are not limited to, one or more computing environments used to implement the application in the production environment such as a data center, a cloud computing environment, a dedicated hosting environment, and/or one or more other computing environments in which one or more assets used by the application in the production environment are implemented; one or more computing systems or computing entities used to implement the application in the production environment; one or more virtual assets used to implement the application in the production environment; one or more supervisory or control systems, such as hypervisors, or other monitoring and management systems, used to monitor and control assets and/or components of the production environment; one or more communications channels for sending and receiving data used to implement the application in the production environment; one or more access control systems for limiting access to various components of the production environment, such as firewalls and gateways; one or more traffic and/or routing systems used to direct, control, and/or buffer, data traffic to components of the production environment, such as routers and switches; one or more communications endpoint proxy systems used to buffer, process, and/or direct data traffic, such as load balancers or buffers; one or more secure communication protocols and/or endpoints used to encrypt/decrypt data, such as Secure Sockets Layer (SSL) protocols, used to implement the application in the production environment; one or more databases used to store data in the production environment; one or more internal or external services used to implement the application in the production environment; one or more backend systems, such as backend servers or other hardware used to process data and implement the application in the production environment; one or more software systems used to implement the application in the production environment; and/or any other assets/components making up an actual production environment in which an application is deployed, implemented, accessed, and run, e.g., operated, as discussed herein, and/or as known in the art at the time of filing, and/or as developed after the time of filing.
As used herein, the terms “computing system”, “computing device”, and “computing entity”, include, but are not limited to, a virtual asset; a server computing system; a workstation; a desktop computing system; a mobile computing system, including, but not limited to, smart phones, portable devices, and/or devices worn or carried by a user; a database system or storage cluster; a switching system; a router; any hardware system; any communications system; any form of proxy system; a gateway system; a firewall system; a load balancing system; or any device, subsystem, or mechanism that includes components that can execute all, or part, of any one of the processes and/or operations as described herein.
In addition, as used herein, the terms computing system and computing entity, can denote, but are not limited to, systems made up of multiple: virtual assets; server computing systems; workstations; desktop computing systems; mobile computing systems; database systems or storage clusters; switching systems; routers; hardware systems; communications systems; proxy systems; gateway systems; firewall systems; load balancing systems; or any devices that can be used to perform the processes and/or operations as described herein.
As used herein, the term “computing environment” includes, but is not limited to, a logical or physical grouping of connected or networked computing systems and/or virtual assets using the same infrastructure and systems such as, but not limited to, hardware systems, software systems, and networking/communications systems. Typically, computing environments are either known environments, e.g., “trusted” environments, or unknown, e.g., “untrusted” environments. Typically, trusted computing environments are those where the assets, infrastructure, communication and networking systems, and security systems associated with the computing systems and/or virtual assets making up the trusted computing environment, are either under the control of, or known to, a party. Examples of trusted computing environments include the assets and components making up data centers associated with, and/or controlled by, an application and/or any computing systems and/or virtual assets, and/or networks of computing systems and/or virtual assets, associated with, known by, and/or controlled by, an application.
In contrast, unknown, or untrusted computing environments are environments and systems where the assets, components, infrastructure, communication and networking systems, and security systems implemented and associated with the computing systems and/or virtual assets making up the untrusted computing environment, are not under the control of, and/or are not known by, a party, and/or are dynamically configured with new elements capable of being added that are unknown to the party. Examples of untrusted computing environments include, but are not limited to, public networks, such as the Internet, various cloud-based computing environments, and various other forms of distributed computing systems.
In various embodiments, each computing environment includes allocated assets and virtual assets associated with, and controlled or used to create, and/or deploy, and/or operate an application.
It is often the case that to create, and/or deploy, and/or operate, application data must be transferred between a first computing environment that is an untrusted computing environment and a trusted computing environment. However, in other situations a party may wish to transfer data between two trusted computing environments, and/or two untrusted computing environments.
In various embodiments, one or more cloud computing environments are used to create, and/or deploy, and/or operate an application that can be any form of cloud computing environment, such as, but not limited to, a public cloud; a private cloud; a virtual private network (VPN); a subnet; a Virtual Private Cloud (VPC); a sub-net or any security/communications grouping; or any other cloud-based infrastructure, sub-structure, or architecture, as discussed herein, and/or as known in the art at the time of filing, and/or as developed after the time of filing.
In many cases, a given application or service may utilize, and interface with, multiple cloud computing environments, such as multiple VPCs, in the course of being created, and/or deployed, and/or operated.
As used herein, the term “virtual asset” includes any virtualized entity or resource, and/or virtualized part of an actual, or “bare metal” entity. In various embodiments, the virtual assets can be, but are not limited to, virtual machines, virtual servers, and instances implemented in a cloud computing environment; databases associated with a cloud computing environment, and/or implemented in a cloud computing environment; services associated with, and/or delivered through, a cloud computing environment; communications systems used with, part of, or provided through, a cloud computing environment; and/or any other virtualized assets and/or sub-systems of “bare metal” physical devices such as mobile devices, remote sensors, laptops, desktops, point-of-sale devices, ATMs, electronic voting machines, etc., located within a data center, within a cloud computing environment, and/or any other physical or logical location, as discussed herein, and/or as known/available in the art at the time of filing, and/or as developed/made available after the time of filing.
In various embodiments, any, or all, of the assets making up a given production environment discussed herein, and/or as known in the art at the time of filing, and/or as developed after the time of filing, can be implemented as virtual assets.
Typically, virtual assets are created, or instantiated, using steps, instructions, processes, code, or “recipes” referred to herein as “virtual asset creation templates.” Typically, virtual assets that have the same, or similar, operational parameters are created using the same or similar “virtual asset creation templates.”
Examples of virtual asset creation templates include, but are not limited to, any tool and/or system for creating and managing a collection of related cloud resources. Illustrative examples of such a virtual asset creation template are any of the cloud formation templates/tools provided by Amazon Web Service (AWS), Rack Space, Joyent, and/or any other of the numerous cloud based infrastructure providers.
Other examples of virtual asset creation templates include, but are not limited to, any configuration management tool associated with, and/or used to create, virtual assets. One specific illustrative example of such a virtual asset creation template is a cookbook or recipe tool such as a Chef Recipe or system or any other fundamental element, or set of elements, used to override the default settings on a node within an infrastructure or architecture.
Other examples of virtual asset creation templates include, but are not limited to, any virtual appliance used to instantiate virtual assets. One specific illustrative example of such a virtual asset creation template is an Amazon Machine Image (AMI), and/or similar functionality provided by Amazon Web Service (AWS), Rack Space, Joyent, and/or any other of the numerous cloud based infrastructure providers.
Other examples of virtual asset creation templates include, but are not limited to, any appliance, or tool, or system, or framework, used to instantiate virtual assets as discussed herein, and/or as known/available in the art at the time of filing, and/or as developed/made available after the time of filing.
Herein virtual assets that have the same, or similar, operational parameters and are created by the same or similar virtual asset creation template are generically referred to as virtual assets of the same “class.” Examples of virtual asset classes include, but are not limited to, virtual machine classes; virtual server classes; virtual database or data store classes; self-monitoring virtual assets including specific types of instances instantiated in a cloud environment; application development process classes; and application classes.
In one embodiment, two or more assets, such as computing systems and/or virtual assets, and/or two or more computing environments, are connected by one or more communications channels including but not limited to, Secure Sockets Layer communications channels and various other secure communications channels, and/or distributed computing system networks, such as, but not limited to: a public cloud; a private cloud; a virtual private network (VPN); a subnet; any general network, communications network, or general network/communications network system; a combination of different network types; a public network; a private network; a satellite network; a cable network; or any other network capable of allowing communication between two or more assets, computing systems, and/or virtual assets, as discussed herein, and/or available or known at the time of filing, and/or as developed after the time of filing.
As used herein, the term “network” includes, but is not limited to, any network or network system such as, but not limited to, a peer-to-peer network, a hybrid peer-to-peer network, a Local Area Network (LAN), a Wide Area Network (WAN), a public network, such as the Internet, a private network, a cellular network, any general network, communications network, or general network/communications network system; a wireless network; a wired network; a wireless and wired combination network; a satellite network; a cable network; any combination of different network types; or any other system capable of allowing communication between two or more assets, virtual assets, and/or computing systems, whether available or known at the time of filing or as later developed.
As used herein, the term “user” includes, but is not limited to, any party, parties, entity, and/or entities using, or otherwise interacting with any of the methods or systems discussed herein. For instance, in various embodiments, a user can be, but is not limited to, a person, a commercial entity, an application, a service, and/or a computing system.
As used herein, the term “tenant” includes, but is not limited to, any user that enters a relationship, agreement, and/or contract, with an asset service provider or other service provider to receive an allocation of one or more assets or asset resources within an asset computing environment. In some embodiments, the terms “tenant” and “tenant computing environment” are interchangeably used even though, in some cases, a tenant represents a party, parties, or entities while the tenant computing environment represents one or more computing resources that are used by or that are at least partially under the control of the tenant.
Hardware Architecture
According to one embodiment, an agent is installed on a virtual asset to monitor the asset for security threats or breaches and to prepare the asset for if/when potential security threats or breaches are detected. According to one embodiment, monitoring for potential security threats or breaches includes comparing a number of authorized open communication ports to a number of communication ports that are actually open in a virtual asset. In another embodiment, the agent is configured to monitor one or more logs, monitor memory, monitor network protocols, and/or monitor other features or characteristics of the virtual asset and compare the operations of the virtual asset to one or more predetermined nominal or expected values. According to various embodiments, self-repairing the virtual asset includes copying or backing up data, instantiating a new asset, providing the new asset with the backed up copies of data, and terminating or decommissioning the virtual asset that has been identified as being compromised. In other embodiments, self-repairing includes waiting for user traffic to subside or decrease, prior to failing the compromised asset over to the new or replacement virtual asset, according to one embodiment. The agent and/or an asset management computing system/environment is configured to establish secure communications channels to transfer secrets, e.g., passwords, passcodes, encryption keys, or the like, and/or security updates. As discussed above, if a security update is transmitted to a compromised virtual asset, an existing security threat or malicious code that has gained access into the virtual asset can undermine the efficacy of the security update by detecting, subverting, and/or monitoring the functionality of the security update. Thus, an advantage of the present disclosure is that the agent is configured to establish a trusted communication channel to receive security updates and/or to create or instantiate a new or uncompromised virtual asset to replace the compromised virtual asset, according to one embodiment.
Production environment 100 includes various computing environments for protecting and repairing a virtual asset from damage by potential security threats, according to one embodiment. Production environment 100 includes a computing environment 110 communicatively coupled to an asset computing environment 120, according to one embodiment. Production environment 100 also includes an asset management computing environment 140 communicatively coupled to asset computing environment 120 and configured to manage one or more virtual assets hosted by or existing within asset computing environment 120, according to one embodiment.
Computing environment 110 includes a user 111 that transmits and receives user data traffic 112 via communications channel 113, according to one embodiment. User 111 can represent one or more computing systems configured to transmit, receive, store, update, manage, and/or otherwise manipulate information or applications hosted by virtual assets within asset computing environment 120, according to various embodiments. For example, user 111 can represent a subscriber to one or more services hosted by a virtual asset, such as Web services, database services, financial services, educational services, video services, social networking services, computing services, and/or the like, according to various embodiments.
Communication channel 113 can include one or more public or private networks or communications channels for communicating between the computing environment 110 and the asset computing environment 120. According to one embodiment, communication channel 113 includes one or more networks, such as a LAN, WAN, PAN, intranet, and/or the Internet.
Asset computing environment 120 is configured to host one or more virtual assets 121 that are enabled for self-monitoring, self-repairing, and establishing trusted communications channels with one or more other computing environments, according to one embodiment. Virtual asset 121 is an allocation of one or more hardware, software, and/or firmware resources to one or more customers or tenants. The tenant may purchase, rent, lease, borrow, or otherwise receive authorization to install, operate, transfer, and/or host applications and/or data with virtual asset 121, according to one embodiment. Virtual asset 121 includes application 122 and virtual asset agent 123, according to one embodiment. Application 122 provides an interface to user 111 and can provide one or more databases, computing, or other services to user 111.
Virtual asset agent 123 monitors and repairs virtual asset 121, in addition to establishing trusted communications channels with other computing environments to initialize and/or update virtual asset 121, according to one embodiment. In one embodiment, virtual asset agent 123 is always running, for example, as a background program, e.g., a daemon, for virtual asset 121. In another embodiment, virtual asset agent 123 is selectively and/or periodically executed in response to one or more triggers such as a timer, instantiation of virtual asset 121, user traffic, erroneous operation, or the like. Virtual asset agent 123 includes self-monitoring module 124, self-repairing module 125, and trusted channel communications module 126, according to one embodiment.
Self-monitoring module 124 includes various modules and engines to monitor the security status and/or health of virtual asset 121, according to one embodiment. Self-monitoring module 124 includes, but is not limited to, port monitor 127, log monitor 128, memory monitor 129, protocol monitor 130, analysis module 131, and reporting engine 132, according to one embodiment.
Port monitor 127 is configured to monitor each of the communication ports of virtual asset 121 for suspicious activity and/or characteristics. For example, if virtual asset 121 has opened/configured 13 different communication ports for use and port monitor 127 detects 14 open communication ports, then self-monitoring module 124 notes the discrepancy and notifies one or more administrators of the discrepancy.
Log monitor 128 is configured to read log files generated by virtual asset agent 123 or generated by virtual asset 121. For example, in one embodiment, virtual asset agent 123 or virtual asset 121 creates log files which record messages sent from the virtual asset 121. Log monitor 128 checks each of the Internet protocol (“IP”) addresses of messages sent/transmitted by virtual asset 121. For example, log monitor 128 is configured, in one embodiment, to periodically, e.g., every half-hour or every 12 hours, check all IP addresses of messages sent within the last predetermined period of time. Log monitor 128 applies, in one embodiment, geographical location (“geolocation”) detection utilities to each of the IP addresses to determine the approximate destination of the transmitted message. If, for example, a message has been transmitted to a prohibited or suspicious city, state, country, or region, e.g., rural Afghanistan, log monitor 128 is, in one embodiment, configured to alert an administrator, or otherwise flag the activity for self-monitoring module 124.
Memory monitor 129 is configured to monitor one or more memory locations allocated to virtual asset 121 for potential security breaches and/or security threats, according to one embodiment. Memory monitor 129 checks memory blocks or locations for particular good or bad patterns or signatures. The good patterns or signatures, e.g., a checksum, indicate that particular programs or memory locations have not been changed or maliciously manipulated. Bad/malicious patterns or signatures, e.g., a virus signature, indicate that particular programs or memory locations have been infected by malicious software or code. Upon detecting one or more malicious patterns or signatures, memory monitor 129 flags the signatures or patterns for further review or action by self-monitoring module 124 or for an administrator, according to one embodiment.
Protocol monitor 130 is configured check the various network protocols to determine whether or not use of the network protocols is appropriate and/or expected, according to one embodiment. For example, protocol monitor 130 checks the number of network protocols used to determine whether or not too many protocols have been used. Protocol monitor 130 also checks, in one embodiment, the types of protocols used to determine the appropriateness of the types of protocols used. For example, if virtual asset 121 is configured to provide non-database services, but network protocols related to database services are being employed, protocol monitor 130 can flag the database-related protocol as potentially inappropriate so that the use of the protocol can be further evaluated. Protocol monitor 130 is configured to also analyze characteristics of the protocols. For example, protocol monitor 130 is configured compare the elements, commands, and/or sizes of protocol payloads to historic and/or expected and/or typical characteristics and can flag any anomalies or aberrations as suspicious or potentially inappropriate, according to one embodiment.
Analysis module 131 is configured, in one embodiment, to receive one or more flags from the monitors within self-monitoring module 124 and is also configured to compare and/or analyze the content of the flags or notifications received. For example, analysis module 131 can maintain one or more tables or other data structures that identify which flagged behaviors have already been reviewed and/or dismissed by one or more analysts or administrators. Analysis module 131 is also configured, in one embodiment, to forward potentially valid security threats or security breaches to reporting engine 132.
Reporting engine 132 transmits one or more reports to self-repairing module 125, to asset management computing environment 140, to one or more system administrators, and/or to the tenant to which virtual asset 121 is allocated, according to one embodiment. According to one embodiment, reporting engine 132 uses trusted channel communications module 126 to establish a trusted communication channel with asset management computing environment 140 to report suspicious and/or inappropriate operations, behaviors, characteristics, or other information determined by self-monitoring module 124, according to one embodiment.
Self-repairing module 125 receives one or more flags, alerts, warnings, and/or reports from self-monitoring module 124, e.g., reporting engine 132, and performs self-repair operations in accordance with the weight or seriousness of the received flags, alerts, warnings, and/or reports, according to one embodiment. Self-repairing module 125 includes repair policy 133, data manager 134, and asset manager 135. Self-repairing module 125 uses repair policy 133, data manager 134, and asset manager 135 to determine the weight or severity of potential security breaches/threats and to create new or clean instances of virtual asset 121 if the security breach/threat is determined to be too severe to repair, according to one embodiment.
Self-repairing module 125 uses repair policy 133 to determine if virtual asset agent 123 should create a new instance of virtual asset 121, according to one embodiment. Repair policy 133 receives notification of the various flags, alerts, warnings, and/or reports from reporting engine 132. Repair policy 133 then compares the content of the received reports to one or more tables, databases, or other data structures to determine if the security of virtual asset 121 can withstand the risks associated with the generated flags, alerts, and/or warnings, according to one embodiment. For example, repair policy 133 includes a predetermined numerical threshold which, if exceeded, self-repairing module 125 is configured to create a new instance of the virtual asset 121. For example, repair policy 133 has a predetermined value of 60 points. Repair policy 133 assigns each type of identified security threat or identified potential security threat a point value based on its potential effect or severity on virtual asset 121. If the sum of the points of the identified security threats exceeds the predetermined value of the repair policy, then self-repairing module 125 or repair policy 133 determines that a new instance of virtual asset 121 is to be created, according to one embodiment. In one embodiment, security threats or risks that can control communications to and from a virtual asset are given a higher weight of seriousness than security threats that simply slow down or interrupt the service provided by virtual asset 121. Similarly, identified security threats or breaches that compromise sensitive information, such as credit card information, personal user information, or other user financial information, are assigned a higher weight, seriousness, or priority than other identified security threats or breaches, according to one embodiment.
Self-repairing module 125 attempts to repair an identified security threat or breach if repair policy 133 determines that the security threat or breach is relatively minor, according to one embodiment. In one embodiment, a security threat or breach is relatively minor if the severity of the security threat or breach is below a predetermined threshold. For example, self-repairing module 125 is configured, in one embodiment, to interface with one or more anti-virus or anti-malware software programs and is also configured to automatically execute one or more anti-virus or anti-malware software programs in response to identifying one or more security threats or breaches in virtual asset 121. In another embodiment, repair policy 133 can be configured to establish a trusted communication channel using trusted channel communications module 126 to notify asset management computing environment 140 of the security threat or breach. Repair policy 133 then uses trusted channel communications module 126 to receive one or more security updates or security patches for execution on virtual asset 121 to repair the one or more security threats or breaches, according to one embodiment. In one embodiment, trusted channel communications module 126 and/or other parts of virtual asset agent 123 perform validation of the authenticity of software, data, or other information received over the trusted communication channel established by trusted channel communications module 126. In some embodiments, asset management computing environment 140 requests and retrieves the security update or security patch from a third party, e.g., a software security vendor, and transmits the security update or security patch to the virtual asset agent upon verification of the validity or authenticity of the security update or security patch.
Self-repairing module 125 creates a new instance of virtual asset 121 if the repair policy 133 determines that one or more security threats or breaches are relatively major and/or are difficult to remove/repair. Self-repairing module 125 uses data manager 134 to backup the data associated with virtual asset 121. In the case that virtual asset 121 is configured to provide database services, data manager 134 creates a copy of one or more databases and stores the copies in a location that is external to virtual asset 121, e.g., in another memory store within asset computing environment 120, according to one embodiment. Once the new instance is in place, self-repairing module 125 can cause the database to fail over to the new instance of the database in the new instance of the virtual asset. In other embodiments, data manager 134 transmits backup copies of the data to one or more cloud storage vendors for temporary storage, according to one embodiment.
Self-repairing module 125 uses asset manager 135 to re-instantiate virtual asset 121, according to one embodiment. Asset manager 135 is configured, in one embodiment, to communicate with asset management computing environment 140 and initialize or create another or new virtual asset 136 within asset computing environment 120. Asset manager 135 can initialize new virtual asset 136 to reflect the content and operations of virtual asset 121. Asset manager 135 initializes new virtual asset 136 with a copy of virtual asset agent 123 and with a copy of the data that was backed up with data manager 134, according to one embodiment. Asset manager 135 is also configured to initialize new virtual asset 136 with a copy of application 122, according to one embodiment. In one embodiment, asset manager 135 retains a copy of application 122 as it was initially injected into virtual asset 121, and injects the retained copy into new virtual asset 136 during initialization of new virtual asset 136. During initialization of new virtual asset 136, asset manager 135 requests clean or updated copies of the secrets used during the operations of virtual asset 121. Trusted channel communications module 126 is operable to provide a trusted communication channel between virtual asset 121 and asset management computing environment 140 or between new virtual asset 136 and asset management computing environment 140. The delivery of the clean or updated version of the secrets of virtual asset 121 to new virtual asset 136 enables new virtual asset 136 to establish secure communications, decode and/or encrypt databases, transmit information through one or more gateways, and the like. In one embodiment, asset manager 135 requests an updated version of the secrets for virtual asset 121 through trusted channel communications module 126 to prevent or reduce the risk of interception of the secrets by one or more security threats or otherwise malicious programs, according to one embodiment.
After asset manager 135 receives verification that new virtual asset 136 is properly operating, from asset management computing environment 140 or from new virtual asset 136, asset manager 135 initiates a self-destruct or decommissioning operation to remove virtual asset 121 from asset computing environment 120, or to render virtual asset 121 inoperable, according to one embodiment. For example, according to one embodiment, asset manager 135 communicates with asset computing environment 120 or with asset management computing environment 140 to disassociate, erase, or otherwise forfeit the memory locations, memory blocks, or memory resources that were previously allocated for use by virtual asset 121.
Asset management computing environment 140 is communicatively coupled to asset computing environment 120 through a communication channel 141 and a trusted communication channel 142 to manage one or more virtual assets in asset computing environment 120, according to one embodiment. Asset management computing environment 140 includes virtual asset manager 143 that is configured to provide security updates and provide copies of secrets to the virtual assets of asset computing environment 120, according to one embodiment. In other embodiments, virtual asset manager 143 is also configured to instantiate virtual assets within asset computing environment 120.
Virtual asset manager 143 includes one or more of security manager 144, asset instantiation module 145, and agent manager 146, secrets policy 147, and trusted channel communications module 148, according to one embodiment. Security manager 144 receives flags, alerts, warnings, and/or reports of security threats/breaches or other suspicious activities or communications associated with the virtual asset 121. Security manager 144 is configured to facilitate repair policy 133 in determining whether self-repairing module 125 will create a new instance of the virtual asset 121 or repair the current security threats, according to one embodiment. Security manager 144 is configured, in one embodiment, to provide repair policy 133 with lists, names, and or characteristics of new security threats as they emerge and are identified. Security manager 144 is also configured to manage one or more lists, tables, or other data structures relating to operations or characteristics that self-monitoring module 124 should search for while monitoring virtual asset 121, according to one embodiment.
Asset instantiation module 145 communicates with self-repairing module 125 to support the creation of one or more new instances of virtual asset 121, e.g., new virtual asset 136, according to one embodiment. As described above, self-repairing module 125 is configured to instantiate new versions or instances of virtual asset 121 without the support of asset management computing environment 140. In other embodiments, when self-repairing module 125 determines that a new instance of virtual asset 121 should be created, self-repairing module 125 requests that virtual asset manager 143 create a new instance of virtual asset 121, and asset instantiation module 145 creates the new instance of virtual asset 121 in asset computing environment 120, according to one embodiment. Asset instantiation module 145 communicates with secrets policy 147 and with agent manager 146 to instantiate or initialize new virtual asset 136 with a copy of virtual asset agent 123 and with clean and/or updated copies of any secrets associated with virtual asset 121. By providing the secrets associated with virtual asset 121, new virtual asset 136 is enabled to perform, take over, and/or continue any operations that were previously executed or performed by virtual asset 121, according to one embodiment.
Virtual asset manager 143 uses trusted channel communications module 148 to communicate with virtual asset agent 123 by trusted communication channel 142, in one embodiment. The ability for virtual asset manager 143 to communicate with the virtual asset 121 via the communication channel 141 and via the trusted communication channel 142 reduces the risk that a security threat, e.g., the malicious software program, will intercept, detect, and/or undermine the efficacy of any security updates provided by virtual asset manager 143 to virtual asset agent 123, according to one embodiment. For example, virtual asset manager 143, e.g., security manager 144, is configured to use trusted channel communications module 148 to transmit updates to virtual asset agent 123 via trusted communication channel 142 to enable virtual asset agent 123 to operate with up-to-date anti-virus, anti-malware, or other security features, according to one embodiment. In another embodiment, virtual asset manager 143 is configured to periodically transmit updated copies of secrets to virtual asset 121 in accordance with secrets policy 147. For example, secrets policy 137 may determine that secrets for virtual asset 121 are updated/refreshed on a quarterly, semiannual, annual, biannual, etc., basis. Accordingly, the asset management computing environment 140 communicates with virtual asset 121 with trusted communication channel 142: to update secrets for virtual asset 121; to update virtual asset agent 123; to selectively create new instances of virtual asset 121; and/or to support the ability of virtual asset 121 and virtual asset agent 123 in monitoring and repairing potential and actual security threats or breaches that may compromise the contents and/or operations of virtual asset 121, according to various embodiments.
At 203, asset computing environment 120 monitors the health of the virtual asset, e.g., virtual asset 121, according to one embodiment. As described above, self-monitoring module 124 is configured to monitor various aspects of virtual asset 121, such as, communication ports, logs, memory, and network protocols, according to one embodiment.
At 204, asset computing environment 120 determines whether a security breach has been detected, according to one embodiment. More specifically, analysis module 131 of self-monitoring module 124, or repair policy 133 of self-repairing module 125, determines whether a security breach has been detected and may determine whether the severity of the security breach warrants further action. If virtual asset agent 123 determines that no further action should be taken, the process follows path 205 and asset computing environment 120 continues to monitor health of the virtual asset, e.g., virtual asset 121.
At 206, asset computing environment 120, or virtual asset agent 123, determines that a major or severe security breach has been detected, asset computing environment 120 instantiates a new virtual asset, e.g., new virtual asset 136, and decommissions the current virtual asset, e.g., virtual asset 121, according to one embodiment. Instantiation of new virtual asset 136 can include copying data of virtual asset 121, creating new virtual asset 136, transferring the copy of the data to new virtual asset 136, installing an instance of virtual asset agent 123 onto new virtual asset 136, and/or installing an instance of application 122 onto new virtual asset 136, according to one embodiment. Decommissioning virtual asset 121 includes, in one embodiment, erasing or reallocating memory that was allocated to virtual asset 121. According to one embodiment, the current virtual asset is a first virtual asset and the new virtual asset is a second virtual asset.
At 207, asset computing environment 120 provides notification of instantiation of the new virtual asset, e.g., new virtual asset 136, to asset management computing environment 140, according to one embodiment. Asset computing environment 120 may establish a trusted or secure communication channel with asset management computing environment 140 prior to providing notification of the instantiation of new virtual asset 136, according to one embodiment.
At 208, asset management computing environment 140 establishes a trusted communication channel with the new virtual asset, e.g., new virtual asset 136, and at 209, asset management computing environment 140 transmits secrets to new virtual asset, e.g., new virtual asset 136, according to one embodiment. The secrets transmitted to new virtual asset 136 is, in one embodiment, a copy of the secrets of virtual asset 121. The copy of the secrets enable new virtual asset 136 to continue the operations of virtual asset 121, according to one embodiment.
At 210, asset computing environment 120, e.g., new virtual asset 136, incorporates the received secrets into the new virtual asset, e.g., the new virtual asset 136, according to one embodiment. Incorporation of the secrets enable new virtual asset 136 to established communications, to decode or encrypt databases, and to transmit messages through various gateways and communication paths, according to one embodiment.
Process 201 and process 202 are executed sequentially, in either order, or can be executed concurrently, according to one embodiment. At 211, asset management computing environment 140 monitors for security updates, according to one embodiment. Asset management computing environment 140 is configured to monitor various computer security vendors' websites or databases for security updates or other information related to new security threats. At 212, asset management computing environment 140 determines if a security update has been detected. If asset management computing environment 140 determines that a security update has not been detected, at 213, process 202 returns to monitoring for security updates. If asset management computing environment 140 determines that a security update has been detected, at 214, asset management computing environment 140 establishes a trusted communication channel with the virtual asset, e.g., virtual asset 121 or new virtual asset 136, according to one embodiment. At 215, using the established trusted communication channel, asset management computing environment 140 transmits the security update to the virtual asset, e.g., virtual asset 121 or new virtual asset 136, according to one embodiment. The security update includes any one of a number of security updates, such as security patches, software updates, or the like.
At 216, asset computing environment 120, e.g., virtual asset agent 123 or new virtual asset 136, incorporates the security update into the virtual asset, e.g., virtual asset 121 or new virtual asset 136, according to one embodiment.
Process
At block 302, the process begins.
At block 304, the process monitors a current virtual asset for potential security threats with a virtual asset agent running within the current virtual asset, according to one embodiment. The virtual asset agent runs within the current virtual asset to identify the potential security threats that risk compromising virtual asset data to unauthorized computing systems.
At block 306, the process determines a severity of the potential security threats that are identified by the virtual asset agent for having gained access into the current virtual asset, according to one embodiment. The severity of the potential security threats is related to a content of the virtual asset data. For example, if the content of the virtual asset data is financial information or security information such as passwords, passcodes, or credit card information, the severity of the potential security threats will be greater than if the content includes information that is hosted on a public website or webpage.
At block 308, if the severity is greater than a predetermined threshold, the process creates a new virtual asset with the virtual asset agent and decommissions the current virtual asset, according to one embodiment. In one embodiment, creating the new virtual asset includes copying the virtual asset data to the new virtual asset, copying one or more applications hosted by the current virtual asset to the new virtual asset, and copying the virtual asset agent to the new virtual asset to enable the new virtual asset to protect and repair the new virtual asset from the damage by the potential security threats.
At block 310, the process receives, with the new virtual asset, secrets that are associated with the current virtual asset to enable the new virtual asset to continue operations of the current virtual asset, according to one embodiment. For example, upon receiving the secrets of the current virtual asset, the new virtual asset is enabled to decrypt and encrypt one or more databases and establish communications channels previously used by the current virtual asset, according to one embodiment. The secrets are received from an asset management computing system and include passwords, passcodes, encryption keys, and other secrets known to those of ordinary skill and/or later developed.
At block 312, the process ends.
At block 402, the process begins.
At block 404, the process monitors the first virtual asset, with an asset management computing system, to determine whether the first virtual asset includes security updates for the potential security threats, according to one embodiment. The first virtual asset includes a virtual asset agent configured to monitor the first virtual asset for the potential security threats and repair the first virtual asset from the damage by the potential security threats.
At block 406, if the first virtual asset does not include one or more of the security updates for the potential security threats, the process updates the first virtual asset by transmitting the one or more of the security updates to the first virtual asset over a first communication channel from the asset management computing system, according to one embodiment. The first communication channel is a trusted or secure communication channel. The first communication channel is different than a second communication channel that is used by the asset management computing system to transmit and receive information over the Internet, according to one embodiment.
At block 408, the process receives notification from the virtual asset agent that the virtual asset agent created a second virtual asset in response to the virtual asset agent detecting intrusion by the potential security threats into the first virtual asset, according to one embodiment.
At block 410, the process transmits secrets associated with the first virtual asset to the second virtual asset using the first communication channel to enable the second virtual asset to continue operations of the first virtual asset, according to one embodiment. Operations of the first asset include, but are not limited to, providing database services, computing services, financial services or other cloud-based or network-based services.
At block 412, the process ends.
As noted above, the specific illustrative examples discussed above are but illustrative examples of implementations of embodiments of the method or process for protecting and repairing a virtual asset. Those of skill in the art will readily recognize that other implementations and embodiments are possible. Therefore the discussion above should not be construed as a limitation on the claims provided below.
In the discussion above, certain aspects of one embodiment include process steps and/or operations and/or instructions described herein for illustrative purposes in a particular order and/or grouping. However, the particular order and/or grouping shown and discussed herein are illustrative only and not limiting. Those of skill in the art will recognize that other orders and/or grouping of the process steps and/or operations and/or instructions are possible and, in some embodiments, one or more of the process steps and/or operations and/or instructions discussed above can be combined and/or deleted. In addition, portions of one or more of the process steps and/or operations and/or instructions can be re-grouped as portions of one or more other of the process steps and/or operations and/or instructions discussed herein. Consequently, the particular order and/or grouping of the process steps and/or operations and/or instructions discussed herein do not limit the scope of the invention as claimed below.
As discussed in more detail above, using the above embodiments, with little or no modification and/or input, there is considerable flexibility, adaptability, and opportunity for customization to meet the specific needs of various parties under numerous circumstances.
In the discussion above, certain aspects of one embodiment include process steps and/or operations and/or instructions described herein for illustrative purposes in a particular order and/or grouping. However, the particular order and/or grouping shown and discussed herein are illustrative only and not limiting. Those of skill in the art will recognize that other orders and/or grouping of the process steps and/or operations and/or instructions are possible and, in some embodiments, one or more of the process steps and/or operations and/or instructions discussed above can be combined and/or deleted. In addition, portions of one or more of the process steps and/or operations and/or instructions can be re-grouped as portions of one or more other of the process steps and/or operations and/or instructions discussed herein. Consequently, the particular order and/or grouping of the process steps and/or operations and/or instructions discussed herein do not limit the scope of the invention as claimed below.
The present invention has been described in particular detail with respect to specific possible embodiments. Those of skill in the art will appreciate that the invention may be practiced in other embodiments. For example, the nomenclature used for components, capitalization of component designations and terms, the attributes, data structures, or any other programming or structural aspect is not significant, mandatory, or limiting, and the mechanisms that implement the invention or its features can have various different names, formats, or protocols. Further, the system or functionality of the invention may be implemented via various combinations of software and hardware, as described, or entirely in hardware elements. Also, particular divisions of functionality between the various components described herein are merely exemplary, and not mandatory or significant. Consequently, functions performed by a single component may, in other embodiments, be performed by multiple components, and functions performed by multiple components may, in other embodiments, be performed by a single component.
Some portions of the above description present the features of the present invention in terms of algorithms and symbolic representations of operations, or algorithm-like representations, of operations on information/data. These algorithmic or algorithm-like descriptions and representations are the means used by those of skill in the art to most effectively and efficiently convey the substance of their work to others of skill in the art. These operations, while described functionally or logically, are understood to be implemented by computer programs or computing systems. Furthermore, it has also proven convenient at times to refer to these arrangements of operations as steps or modules or by functional names, without loss of generality.
Unless specifically stated otherwise, as would be apparent from the above discussion, it is appreciated that throughout the above description, discussions utilizing terms such as, but not limited to, “activating”, “accessing”, “adding”, “aggregating”, “alerting”, “applying”, “analyzing”, “associating”, “calculating”, “capturing”, “categorizing”, “classifying”, “comparing”, “creating”, “defining”, “detecting”, “determining”, “distributing”, “eliminating”, “encrypting”, “extracting”, “filtering”, “forwarding”, “generating”, “identifying”, “implementing”, “informing”, “monitoring”, “obtaining”, “posting”, “processing”, “providing”, “receiving”, “requesting”, “saving”, “sending”, “storing”, “substituting”, “transferring”, “transforming”, “transmitting”, “using”, etc., refer to the action and process of a computing system or similar electronic device that manipulates and operates on data represented as physical (electronic) quantities within the computing system memories, resisters, caches or other information storage, transmission or display devices.
The present invention also relates to an apparatus or system for performing the operations described herein. This apparatus or system may be specifically constructed for the required purposes, or the apparatus or system can comprise a general purpose system selectively activated or configured/reconfigured by a computer program stored on a computer program product as discussed herein that can be accessed by a computing system or other device.
Those of skill in the art will readily recognize that the algorithms and operations presented herein are not inherently related to any particular computing system, computer architecture, computer or industry standard, or any other specific apparatus. Various general purpose systems may also be used with programs in accordance with the teaching herein, or it may prove more convenient/efficient to construct more specialized apparatuses to perform the required operations described herein. The required structure for a variety of these systems will be apparent to those of skill in the art, along with equivalent variations. In addition, the present invention is not described with reference to any particular programming language and it is appreciated that a variety of programming languages may be used to implement the teachings of the present invention as described herein, and any references to a specific language or languages are provided for illustrative purposes only and for enablement of the contemplated best mode of the invention at the time of filing.
The present invention is well suited to a wide variety of computer network systems operating over numerous topologies. Within this field, the configuration and management of large networks comprise storage devices and computers that are communicatively coupled to similar or dissimilar computers and storage devices over a private network, a LAN, a WAN, a private network, or a public network, such as the Internet.
It should also be noted that the language used in the specification has been principally selected for readability, clarity and instructional purposes, and may not have been selected to delineate or circumscribe the inventive subject matter. Accordingly, the disclosure of the present invention is intended to be illustrative, but not limiting, of the scope of the invention, which is set forth in the claims below.
In addition, the operations shown in the FIG.s, or as discussed herein, are identified using a particular nomenclature for ease of description and understanding, but other nomenclature is often used in the art to identify equivalent operations.
Therefore, numerous variations, whether explicitly provided for by the specification or implied by the specification or not, may be implemented by one of skill in the art in view of this disclosure.
This application is a continuation of Lietz, et al., U.S. patent application Ser. No. 14/319,286, filed on Jun. 30, 2014, entitled “METHOD AND SYSTEM FOR SECURE DELIVERY OF INFORMATION TO COMPUTING ENVIRONMENTS,” which is herein incorporated by reference in its entirety as if it were fully set forth herein.
| Number | Name | Date | Kind |
|---|---|---|---|
| 5712641 | Casabona et al. | Jan 1998 | A |
| 5731991 | Kinra et al. | Mar 1998 | A |
| 6085224 | Wagner | Jul 2000 | A |
| 6178452 | Miyamoto | Jan 2001 | B1 |
| 6205552 | Fudge | Mar 2001 | B1 |
| 6321338 | Porras et al. | Nov 2001 | B1 |
| 6343236 | Gibson et al. | Jan 2002 | B1 |
| 6549932 | McNally et al. | Apr 2003 | B1 |
| 6651183 | Gensler et al. | Nov 2003 | B1 |
| 7055062 | Shah et al. | May 2006 | B2 |
| 7114183 | Joiner | Sep 2006 | B1 |
| 7296261 | Witchel et al. | Nov 2007 | B2 |
| 7373524 | Motsinger et al. | May 2008 | B2 |
| 7426745 | McCarty | Sep 2008 | B2 |
| 7506371 | Ben-Natan | Mar 2009 | B1 |
| 7552424 | Bischof et al. | Jun 2009 | B1 |
| 7596625 | Manion et al. | Sep 2009 | B2 |
| 7600153 | Cabrera et al. | Oct 2009 | B2 |
| 7640458 | Rao et al. | Dec 2009 | B2 |
| 7761923 | Khuti et al. | Jul 2010 | B2 |
| 7788235 | Yeo | Aug 2010 | B1 |
| 7792256 | Arledge et al. | Sep 2010 | B1 |
| 7831570 | Sack et al. | Nov 2010 | B2 |
| 7925527 | Flam | Apr 2011 | B1 |
| 7934229 | Vogel | Apr 2011 | B1 |
| 7944355 | Kumar et al. | May 2011 | B2 |
| 7996836 | McCorkendale et al. | Aug 2011 | B1 |
| 8001422 | Sun et al. | Aug 2011 | B1 |
| 8095962 | Condon | Jan 2012 | B2 |
| 8108855 | Dias et al. | Jan 2012 | B2 |
| 8161475 | Araujo et al. | Apr 2012 | B2 |
| 8171485 | Muller | May 2012 | B2 |
| 8171554 | Elovici et al. | May 2012 | B2 |
| 8181036 | Nachenberg | May 2012 | B1 |
| 8266670 | Merkow et al. | Sep 2012 | B1 |
| 8281399 | Chen et al. | Oct 2012 | B1 |
| 8312516 | Malatesta | Nov 2012 | B1 |
| 8327373 | Srinivasan | Dec 2012 | B2 |
| 8392496 | Linden et al. | Mar 2013 | B2 |
| 8438643 | Wiemer et al. | May 2013 | B2 |
| 8510821 | Brandwine et al. | Aug 2013 | B1 |
| 8555388 | Wang et al. | Oct 2013 | B1 |
| 8561126 | Ananthanarayanan et al. | Oct 2013 | B2 |
| 8561127 | Agrawal et al. | Oct 2013 | B1 |
| 8572733 | Rockwood | Oct 2013 | B1 |
| 8615785 | Elrod et al. | Dec 2013 | B2 |
| 8621618 | Ramsey et al. | Dec 2013 | B1 |
| 8683585 | Chen et al. | Mar 2014 | B1 |
| 8688820 | Bhogi et al. | Apr 2014 | B1 |
| 8726383 | Blackwell | May 2014 | B2 |
| 8776050 | Plouffe et al. | Jul 2014 | B2 |
| 8813225 | Fuller et al. | Aug 2014 | B1 |
| 8863284 | Polyakov et al. | Oct 2014 | B1 |
| 8959633 | Dokey et al. | Feb 2015 | B1 |
| 8990935 | Cutts | Mar 2015 | B1 |
| 9047582 | Hutchinson et al. | Jun 2015 | B2 |
| 9049105 | Feinstein et al. | Jun 2015 | B1 |
| 9112841 | Brandwine et al. | Aug 2015 | B1 |
| 9215153 | DeLuca et al. | Dec 2015 | B2 |
| 9245117 | Weaver et al. | Jan 2016 | B2 |
| 9246935 | Lietz et al. | Jan 2016 | B2 |
| 9270690 | Kraitsman et al. | Feb 2016 | B2 |
| 9276945 | Lietz et al. | Mar 2016 | B2 |
| 9313281 | Lietz et al. | Apr 2016 | B1 |
| 9319415 | Lietz et al. | Apr 2016 | B2 |
| 9323926 | Cabrera et al. | Apr 2016 | B2 |
| 9325726 | Lietz et al. | Apr 2016 | B2 |
| 9330263 | Cabrera et al. | May 2016 | B2 |
| 9374389 | Bishop et al. | Jun 2016 | B2 |
| 9459987 | Weaver et al. | Oct 2016 | B2 |
| 9473481 | Lietz et al. | Oct 2016 | B2 |
| 9501345 | Lietz et al. | Nov 2016 | B1 |
| 9811435 | Babakhan | Nov 2017 | B2 |
| 20020066034 | Schlossberg et al. | May 2002 | A1 |
| 20020099992 | Distler et al. | Jul 2002 | A1 |
| 20020116404 | Cha et al. | Aug 2002 | A1 |
| 20020138416 | Lovejoy et al. | Sep 2002 | A1 |
| 20020147803 | Dodd et al. | Oct 2002 | A1 |
| 20020156904 | Gullotta et al. | Oct 2002 | A1 |
| 20030037263 | Kamat et al. | Feb 2003 | A1 |
| 20030046128 | Heinrich | Mar 2003 | A1 |
| 20030051154 | Barton et al. | Mar 2003 | A1 |
| 20030084327 | Lingafelt et al. | May 2003 | A1 |
| 20030088791 | Porras et al. | May 2003 | A1 |
| 20030110392 | Aucsmith et al. | Jun 2003 | A1 |
| 20030188191 | Aaron et al. | Oct 2003 | A1 |
| 20030195959 | Labadie et al. | Oct 2003 | A1 |
| 20030233438 | Hutchinson et al. | Dec 2003 | A1 |
| 20040006704 | Dahlstrom et al. | Jan 2004 | A1 |
| 20040044891 | Hanzlik et al. | Mar 2004 | A1 |
| 20040181775 | Anonsen et al. | Sep 2004 | A1 |
| 20040237093 | Sluiman et al. | Nov 2004 | A1 |
| 20040249973 | Alkhatib et al. | Dec 2004 | A1 |
| 20040249974 | Alkhatib et al. | Dec 2004 | A1 |
| 20050018618 | Mualem et al. | Jan 2005 | A1 |
| 20050066309 | Creamer et al. | Mar 2005 | A1 |
| 20050091304 | Trayler | Apr 2005 | A1 |
| 20050114836 | Fu | May 2005 | A1 |
| 20050155013 | Carrigan | Jul 2005 | A1 |
| 20050172162 | Takahashi et al. | Aug 2005 | A1 |
| 20050182969 | Ginter et al. | Aug 2005 | A1 |
| 20050188222 | Motsinger et al. | Aug 2005 | A1 |
| 20050193231 | Scheuren | Sep 2005 | A1 |
| 20050193269 | Haswell et al. | Sep 2005 | A1 |
| 20050204151 | Fang et al. | Sep 2005 | A1 |
| 20050278790 | Birk et al. | Dec 2005 | A1 |
| 20060031407 | Dispensa et al. | Feb 2006 | A1 |
| 20060037077 | Gadde et al. | Feb 2006 | A1 |
| 20060064740 | Kelley et al. | Mar 2006 | A1 |
| 20060090206 | Ladner et al. | Apr 2006 | A1 |
| 20060101520 | Schumaker et al. | May 2006 | A1 |
| 20060117209 | Drouet et al. | Jun 2006 | A1 |
| 20060136720 | Armstrong et al. | Jun 2006 | A1 |
| 20060184838 | Singonahalli et al. | Aug 2006 | A1 |
| 20060195745 | Keromytis et al. | Aug 2006 | A1 |
| 20060203739 | Padmanabhan et al. | Sep 2006 | A1 |
| 20060272018 | Fouant | Nov 2006 | A1 |
| 20060293940 | Tsyganskiy et al. | Dec 2006 | A1 |
| 20070006304 | Kramer et al. | Jan 2007 | A1 |
| 20070027999 | Allen et al. | Feb 2007 | A1 |
| 20070079168 | Sivakumar et al. | Apr 2007 | A1 |
| 20070094711 | Corley et al. | Apr 2007 | A1 |
| 20070157311 | Meier et al. | Jul 2007 | A1 |
| 20070180509 | Swartz et al. | Aug 2007 | A1 |
| 20070185875 | Chang et al. | Aug 2007 | A1 |
| 20070250424 | Kothari | Oct 2007 | A1 |
| 20080016570 | Capalik | Jan 2008 | A1 |
| 20080025288 | Benner et al. | Jan 2008 | A1 |
| 20080044018 | Scrimsher et al. | Feb 2008 | A1 |
| 20080141332 | Treinen | Jun 2008 | A1 |
| 20080148398 | Mezack et al. | Jun 2008 | A1 |
| 20080177691 | Alperovitch et al. | Jul 2008 | A1 |
| 20080184079 | Merriman et al. | Jul 2008 | A1 |
| 20080244744 | Thomas et al. | Oct 2008 | A1 |
| 20080262990 | Kapoor et al. | Oct 2008 | A1 |
| 20080263670 | Stavrica | Oct 2008 | A1 |
| 20080295076 | McKain et al. | Nov 2008 | A1 |
| 20080307525 | Nickle | Dec 2008 | A1 |
| 20090007100 | Field et al. | Jan 2009 | A1 |
| 20090007264 | Chatterjee et al. | Jan 2009 | A1 |
| 20090049553 | Vasudeva | Feb 2009 | A1 |
| 20090083695 | Mir et al. | Mar 2009 | A1 |
| 20090089682 | Baier et al. | Apr 2009 | A1 |
| 20090106838 | Clark et al. | Apr 2009 | A1 |
| 20090177717 | Meehan et al. | Jul 2009 | A1 |
| 20090199273 | Yalamanchi | Aug 2009 | A1 |
| 20090205039 | Ormazabal et al. | Aug 2009 | A1 |
| 20090228973 | Kumar et al. | Sep 2009 | A1 |
| 20090254970 | Agarwal et al. | Oct 2009 | A1 |
| 20090254990 | McGee | Oct 2009 | A1 |
| 20090288078 | Makonahalli et al. | Nov 2009 | A1 |
| 20090293056 | Ferris et al. | Nov 2009 | A1 |
| 20090300045 | Chaudhry et al. | Dec 2009 | A1 |
| 20090300423 | Ferris | Dec 2009 | A1 |
| 20090319527 | King et al. | Dec 2009 | A1 |
| 20100020700 | Kailash et al. | Jan 2010 | A1 |
| 20100030544 | Gopalan et al. | Feb 2010 | A1 |
| 20100042734 | Olafsson et al. | Feb 2010 | A1 |
| 20100070964 | Blumfield et al. | Mar 2010 | A1 |
| 20100077203 | Ogawa et al. | Mar 2010 | A1 |
| 20100122317 | Yadav | May 2010 | A1 |
| 20100175108 | Protas | Jul 2010 | A1 |
| 20100192220 | Heizmann et al. | Jul 2010 | A1 |
| 20100199351 | Protas | Aug 2010 | A1 |
| 20100212010 | Stringer et al. | Aug 2010 | A1 |
| 20100217850 | Ferris | Aug 2010 | A1 |
| 20100251363 | Todorovic | Sep 2010 | A1 |
| 20100257267 | Sohn et al. | Oct 2010 | A1 |
| 20100257580 | Zhao | Oct 2010 | A1 |
| 20100257599 | Gleichauf | Oct 2010 | A1 |
| 20100269121 | Montesissa et al. | Oct 2010 | A1 |
| 20100287530 | MacLean et al. | Nov 2010 | A1 |
| 20100306268 | Bhatti et al. | Dec 2010 | A1 |
| 20100306354 | Dehaan et al. | Dec 2010 | A1 |
| 20100318481 | Feynman | Dec 2010 | A1 |
| 20110029957 | Shufer et al. | Feb 2011 | A1 |
| 20110034182 | Issa et al. | Feb 2011 | A1 |
| 20110040825 | Ramzan et al. | Feb 2011 | A1 |
| 20110047621 | Brando et al. | Feb 2011 | A1 |
| 20110055921 | Narayanaswamy et al. | Mar 2011 | A1 |
| 20110101109 | Bona et al. | May 2011 | A1 |
| 20110138382 | Hauser et al. | Jun 2011 | A1 |
| 20110138469 | Ye et al. | Jun 2011 | A1 |
| 20110145657 | Bishop et al. | Jun 2011 | A1 |
| 20110154324 | Pagan et al. | Jun 2011 | A1 |
| 20110167494 | Bowen et al. | Jul 2011 | A1 |
| 20110208677 | Zhou et al. | Aug 2011 | A1 |
| 20110208797 | Kim | Aug 2011 | A1 |
| 20110238855 | Korsunsky et al. | Sep 2011 | A1 |
| 20120005750 | Satish | Jan 2012 | A1 |
| 20120011510 | Yamakabe et al. | Jan 2012 | A1 |
| 20120039336 | Richmond et al. | Feb 2012 | A1 |
| 20120042362 | Vlasov et al. | Feb 2012 | A1 |
| 20120072985 | Davne et al. | Mar 2012 | A1 |
| 20120110672 | Judge et al. | May 2012 | A1 |
| 20120117654 | Yalakanti | May 2012 | A1 |
| 20120137367 | Dupont et al. | May 2012 | A1 |
| 20120144489 | Jarrett et al. | Jun 2012 | A1 |
| 20120151488 | Arcese et al. | Jun 2012 | A1 |
| 20120185390 | Palnitkar et al. | Jul 2012 | A1 |
| 20120185913 | Martinez et al. | Jul 2012 | A1 |
| 20120209947 | Glaser et al. | Aug 2012 | A1 |
| 20120210437 | Karande et al. | Aug 2012 | A1 |
| 20120233668 | Leafe et al. | Sep 2012 | A1 |
| 20120303776 | Ferris | Nov 2012 | A1 |
| 20120304300 | LaBumbard | Nov 2012 | A1 |
| 20120311016 | DeAnna et al. | Dec 2012 | A1 |
| 20120311157 | Erickson et al. | Dec 2012 | A1 |
| 20120311387 | Santhosh et al. | Dec 2012 | A1 |
| 20120324572 | Gordon et al. | Dec 2012 | A1 |
| 20120324576 | Clark et al. | Dec 2012 | A1 |
| 20130019242 | Chen et al. | Jan 2013 | A1 |
| 20130019314 | Ji et al. | Jan 2013 | A1 |
| 20130046667 | Hill et al. | Feb 2013 | A1 |
| 20130054792 | Sharaf | Feb 2013 | A1 |
| 20130055246 | Li et al. | Feb 2013 | A1 |
| 20130055398 | Li et al. | Feb 2013 | A1 |
| 20130067067 | Miri et al. | Mar 2013 | A1 |
| 20130091376 | Raspudic et al. | Apr 2013 | A1 |
| 20130097316 | Bender et al. | Apr 2013 | A1 |
| 20130104237 | Riley et al. | Apr 2013 | A1 |
| 20130117809 | McDougal et al. | May 2013 | A1 |
| 20130117852 | Stute | May 2013 | A1 |
| 20130125121 | White | May 2013 | A1 |
| 20130132854 | Raleigh et al. | May 2013 | A1 |
| 20130132950 | McLeod et al. | May 2013 | A1 |
| 20130133072 | Kraitsman et al. | May 2013 | A1 |
| 20130160072 | Reus et al. | Jun 2013 | A1 |
| 20130174259 | Pearcy et al. | Jul 2013 | A1 |
| 20130185795 | Winn et al. | Jul 2013 | A1 |
| 20130227695 | Shankar | Aug 2013 | A1 |
| 20130238786 | Khesin | Sep 2013 | A1 |
| 20130247135 | Kundu et al. | Sep 2013 | A1 |
| 20130247206 | Hugard et al. | Sep 2013 | A1 |
| 20130263209 | Panuganty | Oct 2013 | A1 |
| 20130263226 | Sudia | Oct 2013 | A1 |
| 20130276108 | Blackwell | Oct 2013 | A1 |
| 20130276152 | Hirsch et al. | Oct 2013 | A1 |
| 20130291068 | Huang | Oct 2013 | A1 |
| 20130291087 | Kailash et al. | Oct 2013 | A1 |
| 20130305357 | Ayyagari et al. | Nov 2013 | A1 |
| 20130305369 | Karta et al. | Nov 2013 | A1 |
| 20130305371 | Figlin et al. | Nov 2013 | A1 |
| 20130333040 | Diehl et al. | Dec 2013 | A1 |
| 20130339514 | Crank et al. | Dec 2013 | A1 |
| 20130343207 | Cook et al. | Dec 2013 | A1 |
| 20130346596 | Balakrishnan et al. | Dec 2013 | A1 |
| 20130347131 | Mooring et al. | Dec 2013 | A1 |
| 20140013452 | Aissi et al. | Jan 2014 | A1 |
| 20140026122 | Markande et al. | Jan 2014 | A1 |
| 20140026179 | Devarajan et al. | Jan 2014 | A1 |
| 20140026231 | Barak et al. | Jan 2014 | A1 |
| 20140068784 | Merkow et al. | Mar 2014 | A1 |
| 20140074799 | Karampuri et al. | Mar 2014 | A1 |
| 20140082621 | Fitzgerald et al. | Mar 2014 | A1 |
| 20140089204 | Spies et al. | Mar 2014 | A1 |
| 20140096134 | Barak et al. | Apr 2014 | A1 |
| 20140115578 | Cooper et al. | Apr 2014 | A1 |
| 20140165130 | Zaitsev | Jun 2014 | A1 |
| 20140172806 | Wilding | Jun 2014 | A1 |
| 20140173738 | Condry et al. | Jun 2014 | A1 |
| 20140189090 | Mikkilineni | Jul 2014 | A1 |
| 20140189680 | Kripalani | Jul 2014 | A1 |
| 20140196115 | Pelykh | Jul 2014 | A1 |
| 20140201836 | Amsler | Jul 2014 | A1 |
| 20140214460 | Rahnama | Jul 2014 | A1 |
| 20140258446 | Bursell | Sep 2014 | A1 |
| 20140258715 | Rodniansky | Sep 2014 | A1 |
| 20140259169 | Harrison | Sep 2014 | A1 |
| 20140282840 | Guinan | Sep 2014 | A1 |
| 20140289854 | Mahvi | Sep 2014 | A1 |
| 20140317737 | Shin et al. | Oct 2014 | A1 |
| 20140344933 | Huh et al. | Nov 2014 | A1 |
| 20150032587 | Broom et al. | Jan 2015 | A1 |
| 20150033340 | Giokas | Jan 2015 | A1 |
| 20150052108 | Volk et al. | Feb 2015 | A1 |
| 20150052402 | Gurumurthy et al. | Feb 2015 | A1 |
| 20150052520 | Crowell et al. | Feb 2015 | A1 |
| 20150067865 | Seacat Deluca et al. | Mar 2015 | A1 |
| 20150082307 | Bell et al. | Mar 2015 | A1 |
| 20150095691 | Edwards | Apr 2015 | A1 |
| 20150106939 | Lietz et al. | Apr 2015 | A1 |
| 20150128246 | Feghali et al. | May 2015 | A1 |
| 20150128274 | Giokas | May 2015 | A1 |
| 20150150123 | Be'ery | May 2015 | A1 |
| 20150215327 | Cabrera et al. | Jul 2015 | A1 |
| 20150222653 | Cabrera et al. | Aug 2015 | A1 |
| 20150229661 | Balabine et al. | Aug 2015 | A1 |
| 20150269064 | Bishop et al. | Sep 2015 | A1 |
| 20150278523 | Brinkley et al. | Oct 2015 | A1 |
| 20150304343 | Cabrera et al. | Oct 2015 | A1 |
| 20150319186 | Lietz et al. | Nov 2015 | A1 |
| 20150347773 | Bonney et al. | Dec 2015 | A1 |
| 20150371044 | Horne et al. | Dec 2015 | A1 |
| 20150381641 | Cabrera et al. | Dec 2015 | A1 |
| 20150381651 | Lietz et al. | Dec 2015 | A1 |
| 20160034359 | Cabrera et al. | Feb 2016 | A1 |
| 20160092535 | Kuchibhotla et al. | Mar 2016 | A1 |
| 20160098340 | Weaver et al. | Apr 2016 | A1 |
| 20160234167 | Engel et al. | Aug 2016 | A1 |
| 20160371178 | Bishop et al. | Dec 2016 | A1 |
| Number | Date | Country |
|---|---|---|
| 2 541 420 | Jan 2013 | EP |
| WO 2002091182 | Nov 2002 | WO |
| WO 2012135192 | Oct 2012 | WO |
| WO 2013067404 | May 2013 | WO |
| WO 2015102776 | Jul 2015 | WO |
| Entry |
|---|
| Tupakula, et al.; “Security Techniques for Zero Day Attacks;” Proceedings of the 7th International Wireless Communications and Mobile Computing Conference; Jul. 4-8, 2011; IEEE. |
| Tupakula, et al.; “Intrusion Detection Techniques for Infrastructure as a Service Cloud;” 2011 IEEE Ninth International Conference on Dependable, Autonomic and Secure Computing; Dec. 12-14, 2011; IEEE. |
| Number | Date | Country | |
|---|---|---|---|
| 20180124102 A1 | May 2018 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 14319286 | Jun 2014 | US |
| Child | 15854571 | US |
