METHOD AND SYSTEM FOR PROVIDING SELF-MONITORING, SELF-REPORTING, AND SELF-REPAIRING VIRTUAL ASSETS IN A CLOUD COMPUTING ENVIRONMENT

Abstract

Self-monitoring, self-reporting, and self-repairing virtual assets are provided that include virtual asset self-monitoring logic for detecting one or more trigger events within the self-monitoring, self-reporting, and self-repairing virtual assets, virtual asset self-reporting logic representing instructions for generating trigger event reporting data from the self-monitoring, self-reporting, and self-repairing virtual assets, and virtual asset self-reporting communications channel creation logic for opening a self-reporting communications channel between the self-monitoring, self-reporting, and self-repairing virtual assets and a virtual asset monitoring system.

Description

BACKGROUND

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 and systems associated with sensitive data, such as financial data, to cloud-based infrastructures, and/or other distributive computing models. This is because many owners and operators of data centers that provide access to data and other resources are extremely hesitant to allow their data and resources to be accessed, processed, and/or otherwise used, by virtual assets in the cloud.

In a cloud computing environment, various virtual assets, such as, but not limited to, virtual machine instances, data stores, and services, are created, launched, or instantiated, in the cloud for use by an “owner” of the virtual asset, herein also referred to as a user of the virtual asset.

Herein the terms “owner” and “user” of a virtual asset include, but are not limited to, applications, systems, and sub-systems of software and/or hardware, as well as persons or entities associated with an account number, or other identity, through which the virtual asset is purchased, approved managed, used, and/or created.

One 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, a malicious entity is able to 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.

The situation described above represents a significant issue that must be resolved before highly sensitive data, such as financial data, can be safely processed in a cloud computing environment.

What is needed is a method and system for providing a virtual asset that can independently and automatically detect one or more trigger events within the virtual asset, generate suspicious event reporting data from the virtual asset, and provide the reporting data to a monitoring system external to the virtual asset, all without relying on detection of the suspicious event by entities outside the virtual asset itself or the use of normal communications channels.

SUMMARY

In accordance with one embodiment, a method and system for providing self-monitoring and self-reporting virtual assets includes providing a virtual asset monitoring system. In one embodiment, one or more trigger events to be reported when detected in a virtual asset are defined and virtual asset self-monitoring logic representing instructions for detecting the one or more trigger events within a virtual asset is generated.

In one embodiment, virtual asset self-reporting logic for generating trigger event reporting data indicating a detected trigger event in a virtual asset is generated. In one embodiment, virtual asset self-reporting communications channel creation logic for opening a self-reporting communications channel between a virtual asset and the virtual asset monitoring system is generated.

In one embodiment, a self-monitoring and self-reporting virtual asset is instantiated including the virtual asset self-monitoring logic, the virtual asset self-reporting logic, and the virtual asset self-reporting communications channel creation logic. In one embodiment, when the self-monitoring and self-reporting virtual asset detects a trigger event in the self-monitoring and self-reporting virtual asset using the virtual asset self-monitoring logic, the self-monitoring and self-reporting virtual asset uses the virtual asset self-reporting logic to generate trigger event reporting data indicating the detected trigger event. The self-monitoring and self-reporting virtual asset then uses the virtual asset self-reporting communications channel creation logic to open a self-reporting communications channel between the self-monitoring and self-reporting virtual asset and the virtual asset monitoring system.

In one embodiment, the self-monitoring and self-reporting virtual asset then uses the self-reporting communications channel to transfer the trigger event reporting data from the self-monitoring and self-reporting virtual asset to the virtual asset monitoring system.

In accordance with one embodiment, a method and system for providing self-monitoring, self-reporting, and self-repairing virtual assets includes providing a virtual asset monitoring system.

In one embodiment, one or more trigger events to be reported when detected in a virtual asset are defined and virtual asset self-monitoring logic for detecting the one or more trigger events within a virtual asset is generated.

In one embodiment, virtual asset self-reporting logic for generating trigger event reporting data indicating a detected trigger event in a virtual asset and virtual asset self-reporting communications channel creation logic for opening a self-reporting communications channel between a virtual asset and the virtual asset monitoring system is generated.

In one embodiment, a self-monitoring, self-reporting, and self-repairing virtual asset is instantiated including the virtual asset self-monitoring logic, the virtual asset self-reporting logic, and the virtual asset self-reporting communications channel creation logic. In one embodiment, when a trigger event is detected in the self-monitoring, self-reporting, and self-repairing virtual asset using the virtual asset self-monitoring logic, the self-monitoring, self-reporting, and self-repairing virtual asset uses the virtual asset self-reporting logic to generate trigger event reporting data indicating the detected trigger event.

In one embodiment, the self-monitoring, self-reporting, and self-repairing virtual asset then uses the virtual asset self-reporting communications channel creation logic to open a self-reporting communications channel between the self-monitoring, self-reporting, and self-repairing virtual asset and the virtual asset monitoring system. In one embodiment, the self-monitoring, self-reporting, and self-repairing virtual asset then uses the self-reporting communications channel to transfer the trigger event reporting data from the self-monitoring, self-reporting, and self-repairing virtual asset to the virtual asset monitoring system.

In one embodiment, the trigger event reporting data is analyzed and responsive action implementation data representing instructions for implementing one or more responsive actions to the trigger event is generated and/or selected. In one embodiment, the responsive action implementation data is transferred from the virtual asset monitoring system to the self-monitoring, self-reporting, and self-repairing virtual asset where the self-monitoring, self-reporting, and self-repairing virtual asset uses the responsive action implementation data to implement the one or more responsive actions to the trigger event indicated in the trigger event reporting data.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a functional block diagram showing the interaction of various components of a production environment for implementing one embodiment;

FIG. 2 is a more detailed functional block diagram showing the interaction of various components for implementing one embodiment;

FIG. 3 is a functional diagram of a self-monitoring, self-reporting, and self-repairing virtual asset creation template in accordance with one embodiment;

FIG. 4 is a flow chart depicting a process for providing self-monitoring and self-reporting virtual assets in accordance with one embodiment; and

FIG. 5 is a flow chart depicting a process for providing self-monitoring, self-reporting, and self-repairing virtual assets in accordance with 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 FIGS. 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.

DETAILED DESCRIPTION

Embodiments will now be discussed with reference to the accompanying FIGS., 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 FIGS., 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.

In accordance with one embodiment, a method and system for providing self-monitoring, self-reporting, and self-repairing virtual assets includes a process for providing self-monitoring, self-reporting, and self-repairing virtual assets implemented, at least in part, in a production environment.

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, 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, used to implement the application in the production environment; one or more communications channels used to implement the application in the production environment; one or more access control systems, such as firewalls and gateways, used to implement the application in the production environment; one or more routing systems, such as routers and switches, used to implement the application in the production environment; one or more communications endpoint proxy systems, such as load balancers or buffers, used to implement the application in the production environment; one or more traffic or access control systems used to implement the application in the production environment; one or more secure communication protocols and/or endpoints, such as Secure Sockets Layer (SSL) protocols, used to implement the application in the production environment; one or more databases used to implement the application 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 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, 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” and “computing entity”, include, but are not limited to, a virtual asset; a server computing system; a workstation; a desktop computing system; 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; 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.

In accordance with one embodiment, a method and system for providing self-monitoring, self-reporting, and self-repairing virtual assets includes a process for providing self-monitoring, self-reporting, and self-repairing virtual assets implemented, at least in part, by one or more virtual assets in a cloud computing environment. In one embodiment, the cloud computing environment is part of, or is, the production environment of the application.

In one embodiment, the production environment includes one or more cloud computing environments. In various embodiments, the cloud computing environments 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 provided through the production environment may utilize, and interface with, multiple cloud computing environments, such as multiple VPCs, in the course of providing the associated service. In various embodiments, each cloud computing environment includes allocated assets and virtual assets associated with, and controlled or used by, the party utilizing the cloud computing environment.

As used herein, the term “virtual asset” includes any virtualized entity or resource, and/or 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, the computing systems, and/or computing entities 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.

Some virtual assets are substantially similar to, or identical to, other virtual assets in that the virtual assets have the same, or similar, operational parameters such as, but not limited to, the self-monitoring logic and capabilities as described herein; the self-reporting logic and capabilities as described herein; the self-repairing logic and capabilities as described herein; the same, or similar, function; the same, or similar, connectivity and communication features; the same, or similar, storage capability allocated to the virtual assets; the same, or similar, processing capability allocated to the virtual assets; the same, or similar, hardware, allocated to the virtual assets; the same, or similar, software allocated to virtual assets; and/or any combination of similar, or identical, operational parameters 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.

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. One specific illustrative example of such a virtual asset creation template is a cloud formation template such as any of the Amazon Web Service (AWS) cloud formation tools/templates.

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.

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).

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 self-monitoring logic and capabilities as described herein; self-reporting virtual assets including self-reporting logic and capabilities as described herein; self-repairing virtual assets including self-repairing logic and capabilities as described herein; specific types of instances instantiated in a cloud environment; application development process classes; and application classes.

In various embodiments, the one or more assets included in the production environment and/or implementing the processes for providing self-monitoring, self-reporting, and self-repairing virtual assets are logically or physically located, and/or associated with, two or more computing environments. 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. 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 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. 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.

It is often the case that an application needs to transfer data to, and/or from, a first computing environment that is an untrusted computing environment, such as, but not limited to, a public cloud, a virtual private cloud, and a trusted computing environment, such as, but not limited to, networks of computing systems in a data center controlled by, and/or associated with, the application. However, in other situations a party may wish to transfer data between two trusted computing environments, and/or two untrusted computing environments.

In one embodiment, two or more assets, such as computing systems and/or virtual assets, and/or two or more computing environments, in the production environment 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.

FIG. 1 is a functional diagram of the interaction of various elements associated with exemplary embodiments of the methods and systems for providing self-monitoring, self-reporting, and self-repairing virtual assets discussed herein. Of particular note, the various elements/assets in FIG. 1 are shown for illustrative purposes as being associated with production environment 1 and specific computing environments within production environment 1, such as computing environments 10, 12, 13, 14, and 15. However, the exemplary placement of the various elements/assets within these environments and systems in FIG. 1 is made for illustrative purposes only and, in various embodiments, any individual element/asset shown in FIG. 1, or combination of elements/assets shown in FIG. 1, can be implemented and/or deployed on any of one or more various computing environments or systems, and/or architectural or infrastructure components, such as one or more hardware systems, one or more software systems, one or more data centers, more or more clouds or cloud types, one or more third party service capabilities, or any other computing environments, architectural, and/or infrastructure components, as discussed herein, and/or as known in the art at the time of filing, and/or as developed/made available after the time of filing.

In addition, the elements shown in FIG. 1, and/or the computing environments, systems and architectural and/or infrastructure components, deploying the elements shown in FIG. 1, can be under the control of, or otherwise associated with, various parties or entities, or multiple parties or entities, such as, but not limited to, the owner of a data center, a party and/or entity providing all or a portion of a cloud-based computing environment, the owner or a provider of an application or service, the owner or provider of one or more resources, and/or any other party and/or entity providing one or more functions, and/or any other party and/or entity as discussed herein, and/or as known in the art at the time of filing, and/or as made known after the time of filing.

FIG. 2 is a more detailed functional diagram of the interaction of various elements associated with one embodiment of the methods and systems for providing self-monitoring, self-reporting, and self-repairing virtual assets discussed herein. Of particular note, the various elements in FIG. 2 are shown for illustrative purposes as being associated with specific computing environments, such as computing environment 15 and computing environment 13. However, the exemplary placement of the various elements within these environments and systems in FIG. 2 is made for illustrative purposes only and, in various embodiments, any individual element shown in FIG. 2, or combination of elements shown in FIG. 2, can be implemented and/or deployed on any of one or more various computing environments or systems, and/or architectural or infrastructure components, such as one or more hardware systems, one or more software systems, one or more data centers, more or more clouds or cloud types, one or more third party service capabilities, or any other computing environments, architectural, and/or infrastructure components as discussed herein, and/or as known in the art at the time of filing, and/or as developed/made available after the time of filing.

In addition, the elements shown in FIG. 2, and/or the computing environments, systems and architectural and/or infrastructure components, deploying the elements shown in FIG. 2, can be under the control of, or otherwise associated with, various parties or entities, or multiple parties or entities, such as, but not limited to, the owner of a data center, a party and/or entity providing all or a portion of a cloud-based computing environment, the owner or a provider of a service, the owner or provider of one or more resources, and/or any other party and/or entity providing one or more functions, and/or any other party and/or entity as discussed herein, and/or as known in the art at the time of filing, and/or as made known after the time of filing.

In one embodiment, a production environment is provided for implementing an application. As noted above, FIG. 1 is a functional diagram of the interaction of various elements associated with one embodiment of a method and system for providing self-monitoring, self-reporting, and self-repairing virtual assets discussed herein. In particular, FIG. 1 shows a given application, e.g., application 100 implemented in production environment 1 on server 153 and using various assets.

As seen in FIG. 1, in this specific illustrative example, application 100 is to be implemented using, and including, assets such as, but not limited to, computing environments 10, 12, 13, 14, and 15, used to implement application 100 in production environment 1, such as a data center, a cloud computing environment, and/or one or more other computing environments in which one or more assets and/or services used to implement application 100 in production environment 1 are deployed.

As seen in FIG. 1, production environment 1 includes computing environment 10, for instance a local area network, or the Internet, that includes users 106 and 108 generating user data traffic 107 and 109, respectively, using one or more computing systems (not shown). As seen in FIG. 1, user data traffic 107 and 109 is provided to computing environment 12, such as an access layer or Internet Service Provider (ISP) service used to access application 100, via communications channel 121.

As seen in FIG. 1, production environment 1 includes computing environment 12 which, in turn, includes, as illustrative examples, one or more assets such as router 125, gateway 126, access control 127, and firewall 128. As seen in FIG. 1, in this specific illustrative example, computing environment 12 is commutatively coupled to computing environment 13 of production environment 1 by communications channel 130.

In the specific illustrative example of FIG. 1, computing environment 13 of production environment 1 is a cloud computing environment and includes representative self-monitoring, self-reporting, and self-repairing virtual assets 131 and 135 used to implement application 100. Self-monitoring, self-reporting, and self-repairing virtual assets 131 and 135 are discussed in more detail below.

In the specific illustrative example of FIG. 1, production environment 1 includes computing environment 14, such as an access control layer, commutatively coupled to computing environment 13 by communications channel 141. In this specific illustrative example, computing environment 14 includes assets such as exemplary access control systems, e.g., one or more of access control 143, endpoint proxy 144, load balancer 145, and protocol endpoint 146.

As seen in the specific illustrative example of FIG. 1, production environment 1 includes computing environment 15, such as a data center or infrastructure provider environment, commutatively coupled to computing environment 14 by communications channel 150. In this specific illustrative example, computing environment 15 includes assets such server 153 associated with application 100 and virtual asset monitoring system 114. Virtual asset monitoring system 114 is discussed in more detail below.

In one embodiment, a cloud computing environment is provided. In various embodiments, the provided cloud computing environment 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 one embodiment, one more self-monitoring and self-reporting virtual assets, and/or and self-monitoring, self-reporting, and self-repairing virtual assets are provided in a production environment.

As noted above, as used herein, the term “virtual asset”, such as is used in the terms “self-monitoring and self-reporting virtual asset” and “self-monitoring, self-reporting, and self-repairing virtual asset” includes any virtualized entity or resource, and/or part of an actual, or “bare metal” entity.

As also noted above, in the specific illustrative example of FIG. 1, computing environment 13 is a cloud computing environment that is part of production environment 1 and includes representative self-monitoring, self-reporting, and self-repairing virtual assets 131 and 135.

As discussed in more detail below, in one embodiment, self-monitoring, self-reporting, and self-repairing virtual assets 131 and 135 include virtual asset self-monitoring logic 132 and 136, respectively. In one embodiment, virtual asset self-monitoring logic 132 and 136 include data and instructions for detecting one or more trigger events within self-monitoring, self-reporting, and self-repairing virtual assets 131 and 135, respectively.

As discussed in more detail below, in one embodiment, self-monitoring, self-reporting, and self-repairing virtual assets 131 and 135 include virtual asset self-reporting logic 133 and 137, respectively. In one embodiment, virtual asset self-reporting logic 133 and 137 includes data and instructions for generating trigger event reporting data if one of the one or more trigger events is detected in self-monitoring, self-reporting, and self-repairing virtual assets 131 and 135 by virtual asset self-monitoring logic 132 and 136, respectively.

As discussed in more detail below, in one embodiment, self-monitoring, self-reporting, and self-repairing virtual assets 131 and 135 include virtual asset self-reporting communications channel creation logic 134 and 138, respectively. In one embodiment, virtual asset self-reporting communications channel creation logic 134 and 138 includes data and instructions for opening a virtual asset self-reporting communications channel, such as virtual asset self-reporting communications channels 152 and 151, respectively, between self-monitoring, self-reporting, and self-repairing virtual assets 131 and 135, respectively, and virtual asset monitoring system 114, if one of the one or more trigger events is detected in self-monitoring, self-reporting, and self-repairing virtual assets 131 and 135 by the virtual asset self-monitoring logic 132 and 136, respectively.

As seen in FIG. 1 and as discussed in more detail below, virtual asset monitoring system 114 includes trigger event reporting data receipt module 115 for receiving trigger event reporting data from self-monitoring, self-reporting, and self-repairing virtual assets 131 and 135 if one of the one or more trigger events is detected in self-monitoring, self-reporting, and self-repairing virtual assets 131 and 135 by the virtual asset self-monitoring logic 132 and 136, respectively.

As also seen in FIG. 1, and as discussed in more detail below, virtual asset monitoring system 114 includes responsive action implementation data 117, which, in one embodiment, is provided to self-monitoring, self-reporting, and self-repairing virtual assets 131 and 135 in response to the receipt of trigger event data from self-monitoring, self-reporting, and self-repairing virtual assets 131 and 135.

In one embodiment, the virtual asset monitoring system is implemented in a first computing environment that is distinct from the computing environment in which the self-monitoring, self-reporting, and self-repairing virtual assets are implemented, operated, and/or instantiated.

In one embodiment, the virtual asset monitoring system is implemented, at least in part, in a data center associated with the application being implemented and/or an owner of the self-monitoring, self-reporting, and self-repairing virtual assets. In various embodiments, the virtual asset monitoring system is implemented in software, hardware, and/or a combination of software and hardware.

In one embodiment, the virtual asset monitoring system includes a virtual asset monitoring module and a response action implementation module. In one embodiment, the virtual asset monitoring module of the virtual asset monitoring system includes a trigger event reporting data receipt module which, as discussed below, is used to receive detected trigger event data from the self-monitoring, self-reporting, and self-repairing virtual assets. In one embodiment, the responsive action implementation module of the virtual asset monitoring system includes the capability to analyze the detected trigger event data received from the self-monitoring, self-reporting, and self-repairing virtual assets. In one embodiment, the analysis capability of the responsive action implementation module takes the form of a mapping module used to map specific detected trigger event data to specific responsive action data.

In a specific illustrative example, the responsive action implementation module receives the detected trigger event data from the trigger event reporting data receipt module and a mapping module is used to analyze the detected trigger event data and identify the detected trigger event. In this specific illustrative example, the mapping module then maps the detected trigger event to a specific responsive action represented and implemented by associated responsive action data.

As discussed in more detail below, in various embodiments, depending on the detected trigger event, the responsive actions represented by the responsive action data can include, but are not limited to, any one or more of, ignoring the detected trigger data; requesting the detected trigger data no longer be sent; performing a scan of selected data within the self-monitoring, self-reporting, and self-repairing virtual asset; obtaining data from the self-monitoring, self-reporting, and self-repairing virtual asset; directing a transfer of data from within the self-monitoring, self-reporting, and self-repairing virtual asset to a location outside the self-monitoring, self-reporting, and self-repairing virtual asset; closing down one or more communications channels used by the self-monitoring, self-reporting, and self-repairing virtual asset; shutting down one or more capabilities of the self-monitoring, self-reporting, and self-repairing virtual asset; aborting one or more operations performed by the self-monitoring, self-reporting, and self-repairing virtual asset; destroying the self-monitoring, self-reporting, and self-repairing virtual asset; generating and/or transferring incorrect and/or deceptive data from the self-monitoring, self-reporting, and self-repairing virtual asset to a location outside the self-monitoring, self-reporting, and self-repairing virtual asset associated with a malicious entity; and/or any other desired responsive actions, or combination of responsive actions, as discussed herein, and/or as known in the art at the time of filing, and/or as developed/become available after the time of filing.

As noted above, FIG. 2 is a more detailed functional diagram of the interaction of various elements associated with one embodiment of the methods and systems for providing self-monitoring, self-reporting, and self-repairing virtual assets discussed herein. Referring to FIG. 2, virtual asset monitoring system 114 is shown in this specific illustrative example as being implemented in computing environment 15.

As seen in FIG. 2, virtual asset monitoring system 114 includes virtual asset monitoring module 211 and responsive action implementation module 215. As also seen in FIG. 2, in this specific illustrative example, virtual asset monitoring module 211 includes trigger event reporting data receipt module 115; shown in this illustrative example as having received detected trigger event data 203 from self-monitoring, self-reporting, and self-repairing virtual asset 135 via virtual asset self-reporting communication channel 151.

As also seen in FIG. 2, virtual asset monitoring system 114 includes responsive action implementation module 215 which includes mapping module 214 that maps received detected trigger event data 203 to one or more of responsive action A data 215, responsive action B data 216, and/or responsive action C data 217. As those of skill in the art will readily recognize, responsive action A data 215, responsive action B data 216, and responsive action C data 217 are representative of any number of responsive action data desired including fewer or more responsive action data.

In one embodiment, one or more trigger events are defined. In various embodiments, the one or more trigger events defined are events, states, or occurrences, that when detected in a virtual asset represent a potential security vulnerability, and/or a deviation from normal virtual asset operation.

In various embodiments, the one or more trigger events defined can include, but are not limited to, one or more of: a network message from a virtual asset directed to a location known to be associated with malicious entities, i.e., a black-listed destination; the frequency of outgoing network messages changing to a level above a defined threshold level, i.e., the frequency of outgoing network messages changing to a level deemed “not normal”; a response to a customer request being directed to a destination that is not the customer location of record; a virtual asset receiving a high-frequency of login attempts that fail; a size of the parameters sent into a virtual asset being outside a defined “normal” range of sizes for parameters; a size of outgoing network messages being outside a defined “normal” range of sizes of outgoing messages; a total amount of data in any one communication connection of a virtual asset exceeding a defined maximum normal size of a communication to a customer; a request to a virtual asset coming in from a location known to be associated with malicious entities, i.e., a black-listed origin location; an internal elapsed time of defined critical operations changing to a time outside a defined range of “normal” values; and/or any other trigger event, or combination of trigger events, as discussed herein, and/or as known in the art at the time of filing, and/or as developed/made available after the time of filing.

In one embodiment, once the trigger events are defined, virtual asset self-monitoring logic is generated for monitoring the primary operational logic and data of a virtual asset and detecting the one or more defined trigger events. In one embodiment, the virtual asset self-monitoring logic includes machine-readable code and instructions for monitoring the operational logic of the virtual asset and detecting the one or more defined trigger events within the virtual asset.

In one embodiment, virtual asset self-reporting logic is generated for generating trigger event reporting data indicating a detected trigger event if one of the one or more trigger events is detected in a virtual asset by the virtual asset self-monitoring logic. In one embodiment, the virtual asset self-reporting logic includes machine-readable code and instructions for creating detected trigger event data indicating a detected trigger event, and/or describing the detected trigger event, and/or generating log data representing the detected trigger event.

In one embodiment, virtual asset self-reporting communications channel creation logic is generated for opening a self-reporting communications channel between a virtual asset and the virtual asset monitoring system if one of the one or more trigger events is detected in a virtual asset by the virtual asset self-monitoring logic. In one embodiment, the virtual asset self-reporting communication channel creation logic includes machine-readable code and instructions for activating a self-reporting communications door, or port, pre-deployed, or implemented by, the virtual asset self-reporting communications channel creation logic in the virtual asset and thereby opening a self-reporting communications channel between the virtual asset and the virtual asset monitoring system.

In one embodiment, one or more self-monitoring and self-reporting virtual assets, and/or self-monitoring, self-reporting, and self-repairing virtual assets, are instantiated in a computing environment. In one embodiment, the one or more self-monitoring and self-reporting virtual assets, and/or self-monitoring, self-reporting, and self-repairing virtual assets, are instantiated in a second computing environment that is distinct from the first computing environment in which the virtual asset monitoring system is implemented. In one embodiment, the one or more self-monitoring and self-reporting virtual assets, and/or self-monitoring, self-reporting, and self-repairing virtual assets, are instantiated in a cloud computing environment that is distinct from a data center in which the virtual asset monitoring system is implemented.

As noted above, as used herein, the term “virtual asset”, such as used in the terms “self-monitoring and self-reporting virtual asset” and “self-monitoring, self-reporting, and self-repairing virtual asset” includes any virtualized entity or resource, and/or 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, the computing systems, and/or computing entities 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, and more particularly as, self-monitoring and self-reporting virtual assets, and/or self-monitoring, self-reporting, and self-repairing virtual assets.

As also noted above, some virtual assets are substantially similar to, or identical to, other virtual assets in that the virtual assets have the same, or similar, operational parameters such as, but not limited to, the self-monitoring logic and capabilities as described herein; the self-reporting logic and capabilities as described herein; the self-repairing logic and capabilities as described herein; the same, or similar, function; the same, or similar, connectivity and communication features; the same, or similar, storage capability allocated to the virtual assets; the same, or similar, processing capability allocated to the virtual assets; the same, or similar, hardware, allocated to the virtual assets; the same, or similar, software allocated to virtual assets; and/or any combination of similar, or identical, operational parameters 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.

Typically, virtual assets, including self-monitoring and self-reporting virtual assets, and/or self-monitoring, self-reporting, and self-repairing 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. One specific illustrative example of such a virtual asset creation template is a cloud formation template such as any of the Amazon Web Service (AWS) cloud formation tools/templates.

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.

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).

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 self-monitoring logic and capabilities as described herein; self-reporting virtual assets including self-reporting logic and capabilities as described herein; self-repairing virtual assets including self-repairing logic and capabilities as described herein; specific types of instances instantiated in a cloud environment; application development process classes; and application classes.

In one embodiment, the virtual asset self-monitoring logic, the virtual asset self-reporting logic, and the virtual asset self-reporting communications channel creation logic, are provided to each of the one or more self-monitoring and self-reporting virtual assets, and/or self-monitoring, self-reporting, and self-repairing virtual assets, instantiated in the computing environment.

In one embodiment, the virtual asset self-monitoring logic, the virtual asset self-reporting logic, and the virtual asset self-reporting communications channel creation logic, are provided to each of the one or more self-monitoring and self-reporting virtual assets, and/or self-monitoring, self-reporting, and self-repairing virtual assets, instantiated in the computing environment using one or more self-monitoring, self-reporting, and self-repairing virtual asset creation templates.

Returning to FIG. 2, self-monitoring, self-reporting, and self-repairing virtual asset 135 is shown as implemented, in this specific illustrative example, in computing environment 13 and includes virtual asset self-monitoring logic 136, virtual asset self-reporting logic 137, and virtual asset self-reporting communications channel creation logic 138. In this specific illustrative example, virtual asset self-monitoring logic 136, virtual asset self-reporting logic 137, and virtual asset self-reporting communications channel creation logic 138 are provided to self-monitoring, self-reporting, and self-repairing virtual asset 135 using a self-monitoring, self-reporting, and self-repairing virtual asset creation template such as self-monitoring, self-reporting, and self-repairing virtual asset creation template 300 of FIG. 3 discussed below.

In one embodiment, once one or more self-monitoring and self-reporting virtual assets, and/or self-monitoring, self-reporting, and self-repairing virtual assets are instantiated and include the virtual asset self-monitoring logic, the virtual asset self-reporting logic, and the virtual asset self-reporting communications channel creation logic, the virtual asset self-monitoring logic is used to monitor and detect any of the defined trigger events within the self-monitoring and self-reporting virtual assets, and/or self-monitoring, self-reporting, and self-repairing virtual assets.

In one embodiment, the virtual asset self-monitoring logic is used to monitor and detect any of the defined trigger events within the self-monitoring and self-reporting virtual assets, and/or self-monitoring, self-reporting, and self-repairing virtual assets by monitoring primary virtual asset logic and data used by the self-monitoring and self-reporting virtual assets, and/or self-monitoring, self-reporting, and self-repairing virtual assets, in the course of their normal operations and the performance of their assigned functions.

In one embodiment, if one of the defined trigger events is detected within an affected one of the self-monitoring and self-reporting virtual assets, and/or self-monitoring, self-reporting, and self-repairing virtual assets, by the virtual asset self-monitoring logic, detected trigger event data associated with, describing, or representing log data associated with, the detected trigger event is generated by the virtual asset self-reporting logic provided to the affected self-monitoring and self-reporting, and/or self-monitoring, self-reporting, and self-repairing virtual asset.

In one embodiment, once a defined trigger event is detected within the self-monitoring and self-reporting, and/or self-monitoring, self-reporting, and self-repairing virtual asset, by the virtual asset self-monitoring logic, the virtual asset self-reporting communications channel creation logic provided to the self-monitoring and self-reporting virtual asset, and/or self-monitoring, self-reporting, and self-repairing virtual asset, is used to generate a self-reporting communications channel between the self-monitoring and self-reporting virtual asset, and/or self-monitoring, self-reporting, and self-repairing virtual asset, and the virtual asset monitoring system.

As noted above, in one embodiment, the virtual asset self-reporting communications channel creation logic generates a self-reporting communications channel by activating a self-reporting virtual asset self-reporting communications port pre-deployed, and/or implemented by, the virtual asset self-reporting communications channel creation logic. In one embodiment, the self-reporting communications channel generated by the virtual asset self-reporting communications channel creation logic is a communications channel distinct, and separate from, the various other “normal” communications channels utilized by the self-monitoring and self-reporting virtual assets, and/or self-monitoring, self-reporting, and self-repairing virtual assets, and/or other assets within the computing environment, and/or production environment, associated with the self-monitoring and self-reporting virtual assets, and/or self-monitoring, self-reporting, and self-repairing virtual assets.

Consequently, in one embodiment, the self-reporting communications channel generated by the virtual asset self-reporting communications channel creation logic is not subject to manipulation, and/or termination, by a malicious party that may have taken control of the self-monitoring and self-reporting virtual asset, and/or self-monitoring, self-reporting, and self-repairing virtual asset. In addition, the self-reporting communications channel generated by the virtual asset self-reporting communications channel creation logic is not dependent on security policy implementation systems or other entities outside of the self-monitoring and self-reporting virtual asset, and/or self-monitoring, self-reporting, and self-repairing virtual asset, other than the virtual asset monitoring system.

In one embodiment, once the self-reporting communications channel is generated by the virtual asset self-reporting communications channel creation logic, the detected trigger event data generated by the virtual asset self-reporting logic is transferred to trigger event data transfer logic which, in turn, facilitates the transfer of the detected trigger event data to the virtual asset self-reporting communications port generated by the virtual asset self-reporting communications channel creation logic.

In one embodiment, the detected trigger event data is then transferred from the self-monitoring and self-reporting virtual asset, and/or self-monitoring, self-reporting, and self-repairing virtual asset, to the virtual asset monitoring system using the virtual asset self-reporting communications channel generated by the virtual asset self-reporting communications channel creation logic.

In a specific illustrative example where the detected trigger event is detected in a self-monitoring and self-reporting virtual asset, once the detected trigger event data is transferred from the self-monitoring and self-reporting virtual asset to the virtual asset monitoring system, analysis is performed at the virtual asset monitoring system and appropriate investigative and/or protective action is taken in response to the detected trigger event.

However, in a specific illustrative example where the detected trigger event is detected in a self-monitoring, self-reporting, and self-repairing virtual asset, once the detected trigger event data is transferred from the self-monitoring, self-reporting, and self-repairing virtual asset to the virtual asset monitoring system, analysis is performed at the virtual asset monitoring system.

In one embodiment, the analysis performed at the virtual asset monitoring system includes mapping the detected trigger event data received to associated responsive action implementation data representing instructions for implementing one or more responsive actions to the trigger event indicated in the trigger event reporting data.

In one embodiment, once the detected trigger event data received is mapped to associated responsive action implementation data representing instructions for implementing one or more responsive actions to the trigger event indicated in the trigger event reporting data, the appropriate, or mapped, responsive action implementation data associated with the received trigger event data is provided to the self-monitoring, self-reporting, and self-repairing virtual asset.

In one embodiment, the appropriate, or mapped, responsive action implementation data associated with the received trigger event data is provided to the self-monitoring, self-reporting, and self-repairing virtual asset using the virtual asset self-reporting communication channel, and the virtual asset self-reporting communications port, generated by the virtual asset self-reporting communications channel creation logic provided to the self-monitoring, self-reporting, and self-repairing virtual asset.

In one embodiment, once the appropriate, or mapped, responsive action implementation data associated with the received trigger event data is provided to the self-monitoring, self-reporting, and self-repairing virtual asset, the appropriate, or mapped, responsive action implementation data is used by the self-monitoring, self-reporting, and self-repairing virtual asset to implement the responsive action associated with the responsive action implementation data.

As noted above, in various embodiments, the responsive actions associated with the responsive action implementation data can include, but are not limited to, any one or more of, requesting the detected trigger data no longer be sent; performing a scan of selected data within the self-monitoring, self-reporting, and self-repairing virtual asset; obtaining data from the self-monitoring, self-reporting, and self-repairing virtual asset; directing a transfer of data from within the self-monitoring, self-reporting, and self-repairing virtual asset to a location outside the self-monitoring, self-reporting, and self-repairing virtual asset; closing down one or more communications channels used by the self-monitoring, self-reporting, and self-repairing virtual asset; shutting down one or more capabilities of the self-monitoring, self-reporting, and self-repairing virtual asset; aborting one or more operations performed by the self-monitoring, self-reporting, and self-repairing virtual asset; destroying the self-monitoring, self-reporting, and self-repairing virtual asset; generating and/or transferring incorrect and/or deceptive data from the self-monitoring, self-reporting, and self-repairing virtual asset to a location outside the self-monitoring, self-reporting, and self-repairing virtual asset associated with a malicious entity; and/or any other desired responsive actions, or combination of responsive actions, as discussed herein, and/or as known in the art at the time of filing, and/or as developed/become available after the time of filing.

Returning to FIG. 2, as noted above, self-reporting, and self-repairing virtual asset 135 includes virtual asset self-monitoring logic 136 that is used by self-monitoring, self-reporting, and self-repairing virtual asset 135 to monitor primary virtual asset logic and data 201 associated with the normal operations and functions of self-monitoring, self-reporting, and self-repairing virtual asset 135 to detect a defined trigger event, such as detected trigger event 202.

In one embodiment, once detected trigger event 202 is detected by virtual asset self-monitoring logic 136, notice of detected trigger event 202 is provided to virtual asset self-reporting logic 137 and virtual asset self-reporting communications channel creation logic 138.

In one embodiment, once virtual asset self-reporting logic 137 receives notice of detected trigger event 202, virtual asset self-reporting logic 137 is used to generate detected trigger event data 203 representing a description, log data, or other data indicating detected trigger event 202.

In one embodiment, once virtual asset self-reporting communications channel creation logic 138 receives notice of detected trigger event 202, virtual asset self-reporting communications channel creation logic 138 activates virtual asset self-reporting communications port 205 and thereby creates virtual asset self-reporting communications channel 151.

In one embodiment, detected trigger event data 203 is provided to trigger event data transfer logic 204 which, in turn, facilitates the transfer of detected trigger event data 203 to virtual asset monitoring system 114 via virtual asset self-reporting communications port 205 and virtual asset self-reporting communications channel 151.

In one embodiment, detected trigger event data 203 is received at trigger event reporting data receipt module 115 of virtual asset monitoring module 211 of virtual asset monitoring system 114.

As noted above, in one embodiment, where self-monitoring, self-reporting, and self-repairing virtual asset 135 is used as a self-monitoring and self-reporting virtual asset only, once detected trigger event data 203 is provided to virtual asset monitoring system 114, further investigative and protective action is taken, as needed.

However, as also noted above, in one embodiment, once detected trigger event data 203 is transferred from self-monitoring, self-reporting, and self-repairing virtual asset 135 to trigger event reporting data receipt module 115 of virtual asset monitoring module 211 of virtual asset monitoring system 114, trigger event data 203 is analyzed. In one embodiment, the analysis of trigger event data 203 is performed using mapping module 214.

In one embodiment, mapping module 214 is used to map the detected trigger event indicated in detected trigger event data 203 to one or more of, responsive action A data 215, responsive action B data 216, and/or responsive action C data 217. In the specific illustrative example shown in FIG. 2, detected trigger event data 203 is mapped to responsive action A data 215 by mapping module 214.

In one embodiment, responsive action A data 215 is then provided to responsive action implementation data receipt logic 206 of self-monitoring, self-reporting, and self-repairing virtual asset 135 using either virtual asset self-reporting communication channel 151, or another communications channel, such as communications channel 159.

In one embodiment, once responsive action A data 215 is provided to responsive action implementation data receipt logic 206 of self-monitoring, self-reporting, and self-repairing virtual asset 135, responsive action A data 215 is used by responsive action implementation logic 207 of self-monitoring, self-reporting, and self-repairing virtual asset 135 to implement the specific responsive action associated with responsive action A data 215 within self-monitoring, self-reporting, and self-repairing virtual asset 135.

As noted above, in one embodiment the self-monitoring and self-reporting virtual assets, and/or self-monitoring, self-reporting, and self-repairing virtual assets, are instantiated to include at least the virtual asset self-monitoring logic, the virtual asset self-reporting logic, and the virtual asset self-reporting communications logic, using a self-monitoring, self-reporting, and self-repairing virtual asset creation template.

FIG. 3 shows a simplified block diagram of a self-monitoring, self-reporting, and self-repairing virtual asset creation template 300. As seen in FIG. 3, in one embodiment, self-monitoring, self-reporting, and self-repairing virtual asset creation template 300 includes primary virtual asset logic and data 201.

In one embodiment, primary virtual asset logic and data 201 includes primary virtual asset logic and data, and instructions associated with the self-monitoring, self-reporting, and self-repairing virtual asset itself, and/or the normal functions and operations of the self-monitoring, self-reporting, and self-repairing virtual asset, and/or the operating environment of the self-monitoring, self-reporting, and self-repairing virtual asset, such as a cloud computing environment and/or one or more management systems for the cloud computing environment.

As specific illustrative examples, in various embodiments, primary virtual asset logic and data 201 includes, but is not limited to, one or more of, data indicating the self-monitoring, self-reporting, and self-repairing virtual asset's identification; data indicating the region associated with the self-monitoring, self-reporting, and self-repairing virtual asset; data indicating the availability zone associated with the self-monitoring, self-reporting, and self-repairing virtual asset; data representing and/or indicating software modules and code residing within, or assigned to, the self-monitoring, self-reporting, and self-repairing virtual asset; data indicating a number of software modules residing within, or associated with, the self-monitoring, self-reporting, and self-repairing virtual asset; data representing or indicating files and/or file names residing within, or assigned to, the self-monitoring, self-reporting, and self-repairing virtual asset; data representing and/or indicating the exact configuration of the self-monitoring, self-reporting, and self-repairing virtual asset; data indicating a boot sequence for the self-monitoring, self-reporting, and self-repairing virtual asset; any data provided by a hypervisor or virtualization layer associated with the self-monitoring, self-reporting, and self-repairing virtual asset; any data provided from a cloud control plane associated with the self-monitoring, self-reporting, and self-repairing virtual asset; any data provided by any management system associated with the computing environment of the self-monitoring, self-reporting, and self-repairing virtual asset; communications and data transfer logic associated with the self-monitoring, self-reporting, and self-repairing virtual asset, such as logic and instructions for providing “normal” communications channels and data transfer mechanisms to be used by self-monitoring, self-reporting, and self-repairing virtual asset once the self-monitoring, self-reporting, and self-repairing virtual asset is instantiated, and/or deployed; and/or any combination of “inside” or “normal” operational virtual asset logic and data 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 one embodiment, using at least part of primary virtual asset logic and data 201, a self-monitoring, self-reporting, and self-repairing virtual asset can be instantiated, or launched, in a computing environment. In one embodiment, as a specific illustrative example, self-monitoring, self-reporting, and self-repairing virtual asset is a self-monitoring, self-reporting, and self-repairing virtual machine, or self-monitoring, self-reporting, and self-repairing virtual server instance, to be launched in a cloud computing environment.

In one embodiment, self-monitoring, self-reporting, and self-repairing virtual asset creation template 300 includes virtual asset self-monitoring logic 136, as discussed above.

In one embodiment, self-monitoring, self-reporting, and self-repairing virtual asset creation template 300 includes virtual asset self-reporting logic 137, as discussed above.

In one embodiment, self-monitoring, self-reporting, and self-repairing virtual asset creation template 300 includes virtual asset self-reporting communication channel creation logic 138, as discussed above.

In one embodiment, self-monitoring, self-reporting, and self-repairing virtual asset creation template 300 includes virtual asset self-reporting communication port activation logic 303. In one embodiment, virtual asset self-reporting communication port activation logic 303 includes instructions and data for generating and activating a self-reporting communications door in response to detection of a trigger event by virtual asset self-monitoring logic 136 and instructions from virtual asset self-reporting communications channel creation logic 138.

In one embodiment, self-monitoring, self-reporting, and self-repairing virtual asset creation template 300 includes trigger event reporting data transfer logic 204, as discussed above.

In one embodiment, self-monitoring, self-reporting, and self-repairing virtual asset creation template 300 includes responsive action implementation data receipt logic 206, as discussed above.

In one embodiment, self-monitoring, self-reporting, and self-repairing virtual asset creation template 300 includes responsive action implementation logic 207, as discussed above.

In one embodiment, self-monitoring, self-reporting, and self-repairing virtual asset creation template 300 includes virtual asset self-reporting communication port deactivation logic 305. In one embodiment, virtual asset self-reporting communication port deactivation logic 305 includes instructions and data for deactivating the self-reporting communications door in response instructions from virtual asset self-reporting communications channel creation logic 138.

Using the methods and systems for providing self-monitoring and self-reporting, and/or self-monitoring, self-reporting, and self-repairing virtual assets, discussed herein, self-monitoring and self-reporting, and/or self-monitoring, self-reporting, and self-repairing virtual assets are provided that can independently and automatically detect one or more trigger events within the self-monitoring and self-reporting, and/or self-monitoring, self-reporting, and self-repairing virtual assets, generate suspicious event reporting data from the self-monitoring and self-reporting, and/or self-monitoring, self-reporting, and self-repairing virtual assets, and provide the reporting data to a monitoring system external to the self-monitoring and self-reporting, and/or self-monitoring, self-reporting, and self-repairing virtual assets, all without relying detection of the suspicious event by entities outside the self-monitoring and self-reporting virtual assets, and/or self-monitoring, self-reporting, and self-repairing virtual assets, and/or normal communications channels.

Therefore, using the self-monitoring and self-reporting, and/or self-monitoring, self-reporting, and self-repairing virtual assets, and the methods and systems for providing self-monitoring and self-reporting, and/or self-monitoring, self-reporting, and self-repairing virtual assets discussed herein, virtual assets, and the data processed and stored by virtual assets, are made more secure.

Process

In one embodiment, a self-monitoring and self-reporting virtual asset is instantiated including virtual asset self-monitoring logic, virtual asset self-reporting logic, and virtual asset self-reporting communications channel creation logic.

In one embodiment, when a trigger event is detected in the self-monitoring and self-reporting virtual asset using the virtual asset self-monitoring logic, the self-monitoring and self-reporting virtual asset uses the virtual asset self-reporting logic to generate trigger event reporting data indicating the detected trigger event.

In one embodiment, the self-monitoring and self-reporting virtual asset then uses the virtual asset self-reporting communications channel creation logic to open a self-reporting communications channel between the self-monitoring and self-reporting virtual asset and a virtual asset monitoring system. In one embodiment, the self-monitoring and self-reporting virtual asset then uses the self-reporting communications channel to report the trigger event to the virtual asset monitoring system.

FIG. 4 is a flow chart of a process 400 for providing self-monitoring and self-reporting virtual assets in accordance with one embodiment. In one embodiment, process 400 for providing self-monitoring and self-reporting virtual assets begins at ENTER OPERATION 401 of FIG. 4 and process flow proceeds to PROVIDE A VIRTUAL ASSET MONITORING SYSTEM OPERATION 403.

In one embodiment, at PROVIDE A VIRTUAL ASSET MONITORING SYSTEM OPERATION 403, a virtual asset monitoring system is provided.

In one embodiment, at PROVIDE A VIRTUAL ASSET MONITORING SYSTEM OPERATION 403 the virtual asset monitoring system is implemented in a first computing environment that is distinct from the computing environment in which the self-monitoring and self-reporting virtual assets are implemented, operated, and/or instantiated.

In one embodiment, at PROVIDE A VIRTUAL ASSET MONITORING SYSTEM OPERATION 403 the virtual asset monitoring system is implemented, at least in part, in a data center associated with an application being implemented and/or an owner of the self-monitoring and self-reporting virtual assets.

In various embodiments, at PROVIDE A VIRTUAL ASSET MONITORING SYSTEM OPERATION 403 the virtual asset monitoring system is implemented in software, hardware, and/or a combination of software and hardware. In one embodiment, at PROVIDE A VIRTUAL ASSET MONITORING SYSTEM OPERATION 403 the virtual asset monitoring system includes a virtual asset monitoring module. In one embodiment, at PROVIDE A VIRTUAL ASSET MONITORING SYSTEM OPERATION 403 the virtual asset monitoring module of the virtual asset monitoring system includes a trigger event reporting data receipt module which is used to receive detected trigger event data from the self-monitoring and self-reporting virtual assets.

In one embodiment, once a virtual asset monitoring system is provided at PROVIDE A VIRTUAL ASSET MONITORING SYSTEM OPERATION 403, process flow proceeds to DEFINE ONE OR MORE TRIGGER EVENTS TO BE REPORTED WHEN DETECTED IN A VIRTUAL ASSET OPERATION 405.

In one embodiment, at DEFINE ONE OR MORE TRIGGER EVENTS TO BE REPORTED WHEN DETECTED IN A VIRTUAL ASSET OPERATION 405, one or more trigger events are defined.

In various embodiments, the one or more trigger events defined at DEFINE ONE OR MORE TRIGGER EVENTS TO BE REPORTED WHEN DETECTED IN A VIRTUAL ASSET OPERATION 405 are events, states, or occurrences, that when detected in a virtual asset represent a potential security vulnerability, and/or a deviation from normal virtual asset operation.

In various embodiments, the one or more trigger events defined at DEFINE ONE OR MORE TRIGGER EVENTS TO BE REPORTED WHEN DETECTED IN A VIRTUAL ASSET OPERATION 405 can include, but are not limited to, one or more of, a network message from a virtual asset directed to a location known to be associated with malicious entities, i.e., a black-listed destination; the frequency of outgoing network messages changing to a level above a defined threshold level, i.e., the frequency of outgoing network messages changing to a level deemed “not normal”; a response to a customer request being directed to a destination that is not the customer location of record; a virtual asset receiving a high-frequency of login attempts that fail; a size of the parameters sent into a virtual asset being outside a defined “normal” range of sizes for parameters; a size of outgoing network messages being outside a defined “normal” range of sizes of outgoing messages; a total amount of data in any one communication connection of a virtual asset exceeding a defined maximum normal size of a communication to a customer; a request to a virtual asset coming in from a location known to be associated with malicious entities, i.e., a black-listed origin location; an internal elapsed time of defined critical operations changing to a time outside a defined range of “normal” values; and/or any other trigger event, or combination of trigger events, as discussed herein, and/or as known in the art at the time of filing, and/or as developed/made available after the time of filing.

In one embodiment, once one or more trigger events are defined at DEFINE ONE OR MORE TRIGGER EVENTS TO BE REPORTED WHEN DETECTED IN A VIRTUAL ASSET OPERATION 405, process flow proceeds to GENERATE VIRTUAL ASSET SELF-MONITORING LOGIC REPRESENTING INSTRUCTIONS FOR DETECTING THE ONE OR MORE TRIGGER EVENTS WITHIN A VIRTUAL ASSET OPERATION 407.

In one embodiment, at GENERATE VIRTUAL ASSET SELF-MONITORING LOGIC REPRESENTING INSTRUCTIONS FOR DETECTING THE ONE OR MORE TRIGGER EVENTS WITHIN A VIRTUAL ASSET OPERATION 407 virtual asset self-monitoring logic is generated for monitoring the operational logic of a virtual asset and detecting the one or more defined trigger events of DEFINE ONE OR MORE TRIGGER EVENTS TO BE REPORTED WHEN DETECTED IN A VIRTUAL ASSET OPERATION 405.

In one embodiment, the virtual asset self-monitoring logic of GENERATE VIRTUAL ASSET SELF-MONITORING LOGIC REPRESENTING INSTRUCTIONS FOR DETECTING THE ONE OR MORE TRIGGER EVENTS WITHIN A VIRTUAL ASSET OPERATION 407 includes machine-readable code and instructions for monitoring the primary operational logic and data of the virtual asset and detecting the one or more defined trigger events within the virtual asset.

In one embodiment, once virtual asset self-monitoring logic is generated for monitoring the operational logic of a virtual asset and detecting the one or more defined trigger events of DEFINE ONE OR MORE TRIGGER EVENTS TO BE REPORTED WHEN DETECTED IN A VIRTUAL ASSET OPERATION 405 at GENERATE VIRTUAL ASSET SELF-MONITORING LOGIC REPRESENTING INSTRUCTIONS FOR DETECTING THE ONE OR MORE TRIGGER EVENTS WITHIN A VIRTUAL ASSET OPERATION 407, process flow proceeds to GENERATE VIRTUAL ASSET SELF-REPORTING LOGIC REPRESENTING INSTRUCTIONS FOR GENERATING TRIGGER EVENT REPORTING DATA INDICATING A DETECTED TRIGGER EVENT OPERATION 409.

In one embodiment, at GENERATE VIRTUAL ASSET SELF-REPORTING LOGIC REPRESENTING INSTRUCTIONS FOR GENERATING TRIGGER EVENT REPORTING DATA INDICATING A DETECTED TRIGGER EVENT OPERATION 409, virtual asset self-reporting logic is generated for generating trigger event reporting data indicating a detected trigger event of DEFINE ONE OR MORE TRIGGER EVENTS TO BE REPORTED WHEN DETECTED IN A VIRTUAL ASSET OPERATION 405 if one of the one or more trigger events is detected in a virtual asset by the virtual asset self-monitoring logic of GENERATE VIRTUAL ASSET SELF-MONITORING LOGIC REPRESENTING INSTRUCTIONS FOR DETECTING THE ONE OR MORE TRIGGER EVENTS WITHIN A VIRTUAL ASSET OPERATION 407.

In one embodiment, the virtual asset self-reporting logic of GENERATE VIRTUAL ASSET SELF-REPORTING LOGIC REPRESENTING INSTRUCTIONS FOR GENERATING TRIGGER EVENT REPORTING DATA INDICATING A DETECTED TRIGGER EVENT OPERATION 409 includes machine-readable code and instructions for creating detected trigger event data indicating a detected trigger event, and/or describing the detected trigger event, and/or generating log data representing the detected trigger event.

In one embodiment, once virtual asset self-reporting logic is generated for generating trigger event reporting data indicating a detected trigger event of DEFINE ONE OR MORE TRIGGER EVENTS TO BE REPORTED WHEN DETECTED IN A VIRTUAL ASSET OPERATION 405 if one of the one or more trigger events is detected in a virtual asset by the virtual asset self-monitoring logic of GENERATE VIRTUAL ASSET SELF-MONITORING LOGIC REPRESENTING INSTRUCTIONS FOR DETECTING THE ONE OR MORE TRIGGER EVENTS WITHIN A VIRTUAL ASSET OPERATION 407 at GENERATE VIRTUAL ASSET SELF-REPORTING LOGIC REPRESENTING INSTRUCTIONS FOR GENERATING TRIGGER EVENT REPORTING DATA INDICATING A DETECTED TRIGGER EVENT OPERATION 409, process flow proceeds to GENERATE SELF-REPORTING COMMUNICATIONS CHANNEL CREATION LOGIC REPRESENTING INSTRUCTIONS FOR OPENING A SELF-REPORTING COMMUNICATIONS CHANNEL BETWEEN A VIRTUAL ASSET AND THE VIRTUAL ASSET MONITORING SYSTEM OPERATION 411.

In one embodiment, at GENERATE SELF-REPORTING COMMUNICATIONS CHANNEL CREATION LOGIC REPRESENTING INSTRUCTIONS FOR OPENING A SELF-REPORTING COMMUNICATIONS CHANNEL BETWEEN A VIRTUAL ASSET AND THE VIRTUAL ASSET MONITORING SYSTEM OPERATION 411, virtual asset self-reporting communications channel creation logic is generated for opening a self-reporting communications channel between a virtual asset and the virtual asset monitoring system of PROVIDE A VIRTUAL ASSET MONITORING SYSTEM OPERATION 403 if one of the one or more trigger events of DEFINE ONE OR MORE TRIGGER EVENTS TO BE REPORTED WHEN DETECTED IN A VIRTUAL ASSET OPERATION 405 is detected in a virtual asset by the virtual asset self-monitoring logic of GENERATE VIRTUAL ASSET SELF-MONITORING LOGIC REPRESENTING INSTRUCTIONS FOR DETECTING THE ONE OR MORE TRIGGER EVENTS WITHIN A VIRTUAL ASSET OPERATION 407.

In one embodiment, the virtual asset self-reporting communication channel creation logic of GENERATE SELF-REPORTING COMMUNICATIONS CHANNEL CREATION LOGIC REPRESENTING INSTRUCTIONS FOR OPENING A SELF-REPORTING COMMUNICATIONS CHANNEL BETWEEN A VIRTUAL ASSET AND THE VIRTUAL ASSET MONITORING SYSTEM OPERATION 411 includes machine-readable code and instructions for activating a virtual asset self-reporting communications port, or door, pre-deployed, and/or implemented by, the virtual asset self-reporting communications channel creation logic in the virtual asset and thereby opening a self-reporting communications channel between a virtual asset and the virtual asset monitoring system.

In one embodiment, once virtual asset self-reporting communications channel creation logic is generated for opening a self-reporting communications channel between a virtual asset and the virtual asset monitoring system of PROVIDE A VIRTUAL ASSET MONITORING SYSTEM OPERATION 403 when one of the one or more trigger events of DEFINE ONE OR MORE TRIGGER EVENTS TO BE REPORTED WHEN DETECTED IN A VIRTUAL ASSET OPERATION 405 is detected in a virtual asset by the virtual asset self-monitoring logic of GENERATE VIRTUAL ASSET SELF-MONITORING LOGIC REPRESENTING INSTRUCTIONS FOR DETECTING THE ONE OR MORE TRIGGER EVENTS WITHIN A VIRTUAL ASSET OPERATION 407 at GENERATE SELF-REPORTING COMMUNICATIONS CHANNEL CREATION LOGIC REPRESENTING INSTRUCTIONS FOR OPENING A SELF-REPORTING COMMUNICATIONS CHANNEL BETWEEN A VIRTUAL ASSET AND THE VIRTUAL ASSET MONITORING SYSTEM OPERATION 411, process flow proceeds to INSTANTIATE A SELF-MONITORING AND SELF-REPORTING VIRTUAL ASSET INCLUDING THE VIRTUAL ASSET SELF-MONITORING LOGIC, THE VIRTUAL ASSET SELF-REPORTING LOGIC, AND THE SELF-REPORTING COMMUNICATIONS CHANNEL CREATION LOGIC OPERATION 413.

In one embodiment, at INSTANTIATE A SELF-MONITORING AND SELF-REPORTING VIRTUAL ASSET INCLUDING THE VIRTUAL ASSET SELF-MONITORING LOGIC, THE VIRTUAL ASSET SELF-REPORTING LOGIC, AND THE SELF-REPORTING COMMUNICATIONS CHANNEL CREATION LOGIC OPERATION 413, one or more self-monitoring and self-reporting virtual assets are instantiated in a computing environment.

In one embodiment, at INSTANTIATE A SELF-MONITORING AND SELF-REPORTING VIRTUAL ASSET INCLUDING THE VIRTUAL ASSET SELF-MONITORING LOGIC, THE VIRTUAL ASSET SELF-REPORTING LOGIC, AND THE SELF-REPORTING COMMUNICATIONS CHANNEL CREATION LOGIC OPERATION 413 the one or more self-monitoring and self-reporting virtual assets are instantiated in a second computing environment that is distinct from the first computing environment in which the virtual asset monitoring system of PROVIDE A VIRTUAL ASSET MONITORING SYSTEM OPERATION 403 is implemented.

In one embodiment, at INSTANTIATE A SELF-MONITORING AND SELF-REPORTING VIRTUAL ASSET INCLUDING THE VIRTUAL ASSET SELF-MONITORING LOGIC, THE VIRTUAL ASSET SELF-REPORTING LOGIC, AND THE SELF-REPORTING COMMUNICATIONS CHANNEL CREATION LOGIC OPERATION 413 the one or more self-monitoring and self-reporting virtual assets are instantiated in a cloud computing environment that is distinct from a data center in which the virtual asset monitoring system of PROVIDE A VIRTUAL ASSET MONITORING SYSTEM OPERATION 403 is implemented.

As noted above, as used herein, the term “virtual asset”, such as used in the term “self-monitoring and self-reporting virtual asset” includes any virtualized entity or resource, and/or part of an actual, or “bare metal” entity.

In various embodiments, any, or all, of the assets making up a given production environment, the computing systems, and/or computing entities 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, and more particularly as, self-monitoring and self-reporting virtual assets.

As also noted above, virtual assets, including self-monitoring and self-reporting 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. One specific illustrative example of such a virtual asset creation template is a cloud formation template such as any of the Amazon Web Service (AWS) cloud formation tools/templates.

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.

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).

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.

In one embodiment, the virtual asset self-monitoring logic of GENERATE VIRTUAL ASSET SELF-MONITORING LOGIC REPRESENTING INSTRUCTIONS FOR DETECTING THE ONE OR MORE TRIGGER EVENTS WITHIN A VIRTUAL ASSET OPERATION 407, the virtual asset self-reporting logic of GENERATE VIRTUAL ASSET SELF-REPORTING LOGIC REPRESENTING INSTRUCTIONS FOR GENERATING TRIGGER EVENT REPORTING DATA INDICATING A DETECTED TRIGGER EVENT OPERATION 409, and the virtual asset self-reporting communications channel creation logic of GENERATE SELF-REPORTING COMMUNICATIONS CHANNEL CREATION LOGIC REPRESENTING INSTRUCTIONS FOR OPENING A SELF-REPORTING COMMUNICATIONS CHANNEL BETWEEN A VIRTUAL ASSET AND THE VIRTUAL ASSET MONITORING SYSTEM OPERATION 411, are provided to each of the one or more self-monitoring and self-reporting virtual assets instantiated at INSTANTIATE A SELF-MONITORING AND SELF-REPORTING VIRTUAL ASSET INCLUDING THE VIRTUAL ASSET SELF-MONITORING LOGIC, THE VIRTUAL ASSET SELF-REPORTING LOGIC, AND THE SELF-REPORTING COMMUNICATIONS CHANNEL CREATION LOGIC OPERATION 413.

In one embodiment, the virtual asset self-monitoring logic, the virtual asset self-reporting logic, and the virtual asset self-reporting communications channel creation logic, are provided to each of the one or more self-monitoring and self-reporting virtual assets instantiated in the computing environment at INSTANTIATE A SELF-MONITORING AND SELF-REPORTING VIRTUAL ASSET INCLUDING THE VIRTUAL ASSET SELF-MONITORING LOGIC, THE VIRTUAL ASSET SELF-REPORTING LOGIC, AND THE SELF-REPORTING COMMUNICATIONS CHANNEL CREATION LOGIC OPERATION 413 using one or more self-monitoring, self-reporting, and self-repairing virtual asset creation templates.

In one embodiment, once one or more self-monitoring and self-reporting virtual assets are instantiated in a computing environment at INSTANTIATE A SELF-MONITORING AND SELF-REPORTING VIRTUAL ASSET INCLUDING THE VIRTUAL ASSET SELF-MONITORING LOGIC, THE VIRTUAL ASSET SELF-REPORTING LOGIC, AND THE SELF-REPORTING COMMUNICATIONS CHANNEL CREATION LOGIC OPERATION 413, process flow proceeds to USE THE VIRTUAL ASSET SELF-MONITORING LOGIC IN THE SELF-MONITORING AND SELF-REPORTING VIRTUAL ASSET TO DETECT A TRIGGER EVENT IN THE SELF-MONITORING AND SELF-REPORTING VIRTUAL ASSET OPERATION 415.

In one embodiment, at USE THE VIRTUAL ASSET SELF-MONITORING LOGIC IN THE SELF-MONITORING AND SELF-REPORTING VIRTUAL ASSET TO DETECT A TRIGGER EVENT IN THE SELF-MONITORING AND SELF-REPORTING VIRTUAL ASSET OPERATION 415, the virtual asset self-monitoring logic of GENERATE VIRTUAL ASSET SELF-MONITORING LOGIC REPRESENTING INSTRUCTIONS FOR DETECTING THE ONE OR MORE TRIGGER EVENTS WITHIN A VIRTUAL ASSET OPERATION 407 provided to the one or more self-monitoring and self-reporting virtual assets at INSTANTIATE A SELF-MONITORING AND SELF-REPORTING VIRTUAL ASSET INCLUDING THE VIRTUAL ASSET SELF-MONITORING LOGIC, THE VIRTUAL ASSET SELF-REPORTING LOGIC, AND THE SELF-REPORTING COMMUNICATIONS CHANNEL CREATION LOGIC OPERATION 413 is used to monitor and detect any of the defined trigger events of DEFINE ONE OR MORE TRIGGER EVENTS TO BE REPORTED WHEN DETECTED IN A VIRTUAL ASSET OPERATION 405 within the self-monitoring and self-reporting virtual assets.

In one embodiment, at USE THE VIRTUAL ASSET SELF-MONITORING LOGIC IN THE SELF-MONITORING AND SELF-REPORTING VIRTUAL ASSET TO DETECT A TRIGGER EVENT IN THE SELF-MONITORING AND SELF-REPORTING VIRTUAL ASSET OPERATION 415 the virtual asset self-monitoring logic is used to monitor and detect any of the defined trigger events within the self-monitoring and self-reporting virtual assets by monitoring primary virtual asset logic and data used by the self-monitoring and self-reporting virtual assets in the course of their normal operations and the performance of their assigned functions.

In one embodiment, once the virtual asset self-monitoring logic of GENERATE VIRTUAL ASSET SELF-MONITORING LOGIC REPRESENTING INSTRUCTIONS FOR DETECTING THE ONE OR MORE TRIGGER EVENTS WITHIN A VIRTUAL ASSET OPERATION 407 provided to the one or more self-monitoring and self-reporting virtual assets at INSTANTIATE A SELF-MONITORING AND SELF-REPORTING VIRTUAL ASSET INCLUDING THE VIRTUAL ASSET SELF-MONITORING LOGIC, THE VIRTUAL ASSET SELF-REPORTING LOGIC, AND THE SELF-REPORTING COMMUNICATIONS CHANNEL CREATION LOGIC OPERATION 413 is used to monitor and detect any of the defined trigger events of DEFINE ONE OR MORE TRIGGER EVENTS TO BE REPORTED WHEN DETECTED IN A VIRTUAL ASSET OPERATION 405 within the self-monitoring and self-reporting virtual assets at USE THE VIRTUAL ASSET SELF-MONITORING LOGIC IN THE SELF-MONITORING AND SELF-REPORTING VIRTUAL ASSET TO DETECT A TRIGGER EVENT IN THE SELF-MONITORING AND SELF-REPORTING VIRTUAL ASSET OPERATION 415, process flow proceeds to USE THE VIRTUAL ASSET SELF-REPORTING LOGIC IN THE SELF-MONITORING AND SELF-REPORTING VIRTUAL ASSET TO GENERATE TRIGGER EVENT REPORTING DATA OPERATION 417.

In one embodiment, if one of the defined trigger events is detected within one of the self-monitoring and self-reporting virtual assets by the virtual asset self-monitoring logic at USE THE VIRTUAL ASSET SELF-MONITORING LOGIC IN THE SELF-MONITORING AND SELF-REPORTING VIRTUAL ASSET TO DETECT A TRIGGER EVENT IN THE SELF-MONITORING AND SELF-REPORTING VIRTUAL ASSET OPERATION 415, then at USE THE VIRTUAL ASSET SELF-REPORTING LOGIC IN THE SELF-MONITORING AND SELF-REPORTING VIRTUAL ASSET TO GENERATE TRIGGER EVENT REPORTING DATA OPERATION 417 detected trigger event data associated with, describing, or representing log data associated with, the detected trigger event is generated by the virtual asset self-reporting logic of GENERATE VIRTUAL ASSET SELF-REPORTING LOGIC REPRESENTING INSTRUCTIONS FOR GENERATING TRIGGER EVENT REPORTING DATA INDICATING A DETECTED TRIGGER EVENT OPERATION 409 provided to the affected self-monitoring and self-reporting virtual asset at INSTANTIATE A SELF-MONITORING AND SELF-REPORTING VIRTUAL ASSET INCLUDING THE VIRTUAL ASSET SELF-MONITORING LOGIC, THE VIRTUAL ASSET SELF-REPORTING LOGIC, AND THE SELF-REPORTING COMMUNICATIONS CHANNEL CREATION LOGIC OPERATION 413.

In one embodiment, once detected trigger event data associated with, describing, or representing log data associated with, the detected trigger event is generated by the virtual asset self-reporting logic provided to the affected self-monitoring and self-reporting at USE THE VIRTUAL ASSET SELF-REPORTING LOGIC IN THE SELF-MONITORING AND SELF-REPORTING VIRTUAL ASSET TO GENERATE TRIGGER EVENT REPORTING DATA OPERATION 417, process flow proceeds to USE THE SELF-REPORTING COMMUNICATIONS CHANNEL CREATION LOGIC IN THE SELF-MONITORING AND SELF-REPORTING VIRTUAL ASSET TO GENERATE A SELF-REPORTING COMMUNICATIONS CHANNEL BETWEEN THE SELF-MONITORING AND SELF-REPORTING VIRTUAL ASSET AND THE VIRTUAL ASSET MONITORING SYSTEM OPERATION 419.

In one embodiment, once a defined trigger event is detected within the self-monitoring and self-reporting virtual asset by the virtual asset self-monitoring logic at USE THE VIRTUAL ASSET SELF-MONITORING LOGIC IN THE SELF-MONITORING AND SELF-REPORTING VIRTUAL ASSET TO DETECT A TRIGGER EVENT IN THE SELF-MONITORING AND SELF-REPORTING VIRTUAL ASSET OPERATION 415, at USE THE SELF-REPORTING COMMUNICATIONS CHANNEL CREATION LOGIC IN THE SELF-MONITORING AND SELF-REPORTING VIRTUAL ASSET TO GENERATE A SELF-REPORTING COMMUNICATIONS CHANNEL BETWEEN THE SELF-MONITORING AND SELF-REPORTING VIRTUAL ASSET AND THE VIRTUAL ASSET MONITORING SYSTEM OPERATION 419 the virtual asset self-reporting communications channel creation logic of GENERATE SELF-REPORTING COMMUNICATIONS CHANNEL CREATION LOGIC REPRESENTING INSTRUCTIONS FOR OPENING A SELF-REPORTING COMMUNICATIONS CHANNEL BETWEEN A VIRTUAL ASSET AND THE VIRTUAL ASSET MONITORING SYSTEM OPERATION 411 provided to the self-monitoring and self-reporting virtual asset at INSTANTIATE A SELF-MONITORING AND SELF-REPORTING VIRTUAL ASSET INCLUDING THE VIRTUAL ASSET SELF-MONITORING LOGIC, THE VIRTUAL ASSET SELF-REPORTING LOGIC, AND THE SELF-REPORTING COMMUNICATIONS CHANNEL CREATION LOGIC OPERATION 413, is used to generate a self-reporting communications channel between the self-monitoring and self-reporting virtual asset and the virtual asset monitoring system of PROVIDE A VIRTUAL ASSET MONITORING SYSTEM OPERATION 403.

As noted above, in one embodiment, the virtual asset self-reporting communications channel creation logic of GENERATE SELF-REPORTING COMMUNICATIONS CHANNEL CREATION LOGIC REPRESENTING INSTRUCTIONS FOR OPENING A SELF-REPORTING COMMUNICATIONS CHANNEL BETWEEN A VIRTUAL ASSET AND THE VIRTUAL ASSET MONITORING SYSTEM OPERATION 411 generates a self-reporting communications channel at USE THE SELF-REPORTING COMMUNICATIONS CHANNEL CREATION LOGIC IN THE SELF-MONITORING AND SELF-REPORTING VIRTUAL ASSET TO GENERATE A SELF-REPORTING COMMUNICATIONS CHANNEL BETWEEN THE SELF-MONITORING AND SELF-REPORTING VIRTUAL ASSET AND THE VIRTUAL ASSET MONITORING SYSTEM OPERATION 419 by activating a self-reporting virtual asset self-reporting communications port pre-deployed, and/or implemented by, the virtual asset self-reporting communications channel creation logic.

In one embodiment, the self-reporting communications channel generated by the virtual asset self-reporting communications channel creation logic at USE THE SELF-REPORTING COMMUNICATIONS CHANNEL CREATION LOGIC IN THE SELF-MONITORING AND SELF-REPORTING VIRTUAL ASSET TO GENERATE A SELF-REPORTING COMMUNICATIONS CHANNEL BETWEEN THE SELF-MONITORING AND SELF-REPORTING VIRTUAL ASSET AND THE VIRTUAL ASSET MONITORING SYSTEM OPERATION 419 is a communications channel distinct, and separate from, the various other “normal” communications channels utilized by the self-monitoring and self-reporting virtual assets and/or other assets within the computing environment, and/or production environment, associated with the self-monitoring and self-reporting virtual assets.

Consequently, in one embodiment, the self-reporting communications channel generated by the virtual asset self-reporting communications channel creation logic at USE THE SELF-REPORTING COMMUNICATIONS CHANNEL CREATION LOGIC IN THE SELF-MONITORING AND SELF-REPORTING VIRTUAL ASSET TO GENERATE A SELF-REPORTING COMMUNICATIONS CHANNEL BETWEEN THE SELF-MONITORING AND SELF-REPORTING VIRTUAL ASSET AND THE VIRTUAL ASSET MONITORING SYSTEM OPERATION 419 is not subject to manipulation, and/or termination, by a malicious party that may have taken control of the self-monitoring and self-reporting virtual asset. In addition, the self-reporting communications channel generated by the virtual asset self-reporting communications channel creation logic is not dependent on security policy implementation systems and entities outside of the self-monitoring and self-reporting virtual asset, other than the virtual asset monitoring system.

In one embodiment, once the virtual asset self-reporting communications channel creation logic of GENERATE SELF-REPORTING COMMUNICATIONS CHANNEL CREATION LOGIC REPRESENTING INSTRUCTIONS FOR OPENING A SELF-REPORTING COMMUNICATIONS CHANNEL BETWEEN A VIRTUAL ASSET AND THE VIRTUAL ASSET MONITORING SYSTEM OPERATION 411 provided to the self-monitoring and self-reporting virtual asset at INSTANTIATE A SELF-MONITORING AND SELF-REPORTING VIRTUAL ASSET INCLUDING THE VIRTUAL ASSET SELF-MONITORING LOGIC, THE VIRTUAL ASSET SELF-REPORTING LOGIC, AND THE SELF-REPORTING COMMUNICATIONS CHANNEL CREATION LOGIC OPERATION 413, is used to generate a self-reporting communications channel between the self-monitoring and self-reporting virtual asset and the virtual asset monitoring system of PROVIDE A VIRTUAL ASSET MONITORING SYSTEM OPERATION 403 at USE THE SELF-REPORTING COMMUNICATIONS CHANNEL CREATION LOGIC IN THE SELF-MONITORING AND SELF-REPORTING VIRTUAL ASSET TO GENERATE A SELF-REPORTING COMMUNICATIONS CHANNEL BETWEEN THE SELF-MONITORING AND SELF-REPORTING VIRTUAL ASSET AND THE VIRTUAL ASSET MONITORING SYSTEM OPERATION 419, process flow proceeds to USE THE SELF-REPORTING COMMUNICATIONS CHANNEL TO TRANSFER THE TRIGGER EVENT REPORTING DATA FROM THE SELF-MONITORING AND SELF-REPORTING VIRTUAL ASSET TO THE VIRTUAL ASSET MONITORING SYSTEM OPERATION 421.

In one embodiment, at USE THE SELF-REPORTING COMMUNICATIONS CHANNEL TO TRANSFER THE TRIGGER EVENT REPORTING DATA FROM THE SELF-MONITORING AND SELF-REPORTING VIRTUAL ASSET TO THE VIRTUAL ASSET MONITORING SYSTEM OPERATION 421 the detected trigger event data of USE THE VIRTUAL ASSET SELF-REPORTING LOGIC IN THE SELF-MONITORING AND SELF-REPORTING VIRTUAL ASSET TO GENERATE TRIGGER EVENT REPORTING DATA OPERATION 417 is transferred from the self-monitoring and self-reporting virtual asset to the virtual asset monitoring system of PROVIDE A VIRTUAL ASSET MONITORING SYSTEM OPERATION 403 using the virtual asset self-reporting communications channel generated by the virtual asset self-reporting communications channel creation logic at USE THE SELF-REPORTING COMMUNICATIONS CHANNEL CREATION LOGIC IN THE SELF-MONITORING AND SELF-REPORTING VIRTUAL ASSET TO GENERATE A SELF-REPORTING COMMUNICATIONS CHANNEL BETWEEN THE SELF-MONITORING AND SELF-REPORTING VIRTUAL ASSET AND THE VIRTUAL ASSET MONITORING SYSTEM OPERATION 419.

In one embodiment, once the detected trigger event data of USE THE VIRTUAL ASSET SELF-REPORTING LOGIC IN THE SELF-MONITORING AND SELF-REPORTING VIRTUAL ASSET TO GENERATE TRIGGER EVENT REPORTING DATA OPERATION 417 is transferred from the self-monitoring and self-reporting virtual asset to the virtual asset monitoring system of PROVIDE A VIRTUAL ASSET MONITORING SYSTEM OPERATION 403 using the virtual asset self-reporting communications channel generated by the virtual asset self-reporting communications channel creation logic at USE THE SELF-REPORTING COMMUNICATIONS CHANNEL TO TRANSFER THE TRIGGER EVENT REPORTING DATA FROM THE SELF-MONITORING AND SELF-REPORTING VIRTUAL ASSET TO THE VIRTUAL ASSET MONITORING SYSTEM OPERATION 421, process flow proceeds to EXIT OPERATION 430.

In one embodiment, at EXIT OPERATION 430 process 400 for providing self-monitoring and self-reporting virtual assets is exited to await new data.

Using the self-monitoring and self-reporting virtual assets of process 400 for providing self-monitoring and self-reporting virtual assets, self-monitoring and self-reporting virtual assets are provided that can independently and automatically detect one or more trigger events within the self-monitoring and self-reporting virtual assets, generate suspicious event reporting data from the self-monitoring and self-reporting virtual assets, and provide the reporting data to a monitoring system external to self-monitoring and self-reporting virtual assets, all without relying detection of the suspicious event by entities outside the self-monitoring and self-reporting virtual assets themselves, and/or normal communications channels.

Therefore, using the self-monitoring and self-reporting virtual assets, and the methods and systems for providing self-monitoring and self-reporting virtual assets discussed herein, virtual assets, and the data processed and stored by virtual assets, are made more secure.

In the specific illustrative embodiments discussed above where the detected trigger event is detected in a self-monitoring and self-reporting virtual asset, once the detected trigger event data is transferred from the self-monitoring and self-reporting virtual asset to the virtual asset monitoring system, analysis is performed at the virtual asset monitoring system and appropriate investigative and/or protective action is taken in response to the detected trigger event.

However, where the detected trigger event is detected in a self-monitoring, self-reporting, and self-repairing virtual asset, once the detected trigger event data is transferred from the self-monitoring and self-reporting virtual asset to the virtual asset monitoring system, further analysis and actions are taken automatically.

In one embodiment, a self-monitoring, self-reporting, and self-repairing virtual asset is instantiated including virtual asset self-monitoring logic, virtual asset self-reporting logic, and virtual asset self-reporting communications channel creation logic.

In one embodiment, when a trigger event is detected in the self-monitoring, self-reporting, and self-repairing virtual asset using the virtual asset self-monitoring logic, the self-monitoring, self-reporting, and self-repairing virtual asset uses the virtual asset self-reporting logic to generate trigger event reporting data indicating the detected trigger event.

In one embodiment, the self-monitoring, self-reporting, and self-repairing virtual asset then uses the virtual asset self-reporting communications channel creation logic to open a self-reporting communications channel between the self-monitoring, self-reporting, and self-repairing virtual asset and a virtual asset monitoring system. In one embodiment, the self-monitoring, self-reporting, and self-repairing virtual asset then uses the self-reporting communications channel to report the trigger event to the virtual asset monitoring system.

In one embodiment, responsive action implementation data representing instructions for implementing one or more responsive actions to the trigger event is then generated and sent to the self-monitoring, self-reporting, and self-repairing virtual asset where the self-monitoring, self-reporting, and self-repairing virtual asset uses the responsive action implementation data to respond to the trigger event.

FIG. 5 is a flow chart of a process 500 for providing self-monitoring, self-reporting, and self-repairing virtual assets in accordance with one embodiment. In one embodiment, process 500 for providing self-monitoring, self-reporting, and self-repairing virtual assets begins at ENTER OPERATION 501 of FIG. 5 and process flow proceeds to PROVIDE A VIRTUAL ASSET MONITORING SYSTEM OPERATION 503.

In one embodiment, at PROVIDE A VIRTUAL ASSET MONITORING SYSTEM OPERATION 503, a virtual asset monitoring system is provided.

In one embodiment, the virtual asset monitoring system of PROVIDE A VIRTUAL ASSET MONITORING SYSTEM OPERATION 503 is implemented in a first computing environment that is distinct from the computing environment in which the self-monitoring, self-reporting, and self-repairing virtual assets are implemented, operated, and/or instantiated.

In one embodiment, the virtual asset monitoring system of PROVIDE A VIRTUAL ASSET MONITORING SYSTEM OPERATION 503 is implemented, at least in part, in a data center associated with the application being implemented, and/or an owner of the self-monitoring, self-reporting, and self-repairing virtual assets. In various embodiments, the virtual asset monitoring system is implemented in software, hardware, and/or a combination of software and hardware.

In one embodiment, the virtual asset monitoring system of PROVIDE A VIRTUAL ASSET MONITORING SYSTEM OPERATION 503 includes a virtual asset monitoring module and a response action implementation module.

In one embodiment, the virtual asset monitoring module of the virtual asset monitoring system of PROVIDE A VIRTUAL ASSET MONITORING SYSTEM OPERATION 503 includes a trigger event reporting data receipt module which, as discussed below, is used to receive detected trigger event data from the self-monitoring, self-reporting, and self-repairing virtual assets.

In one embodiment, the responsive action implementation module of the virtual asset monitoring system of PROVIDE A VIRTUAL ASSET MONITORING SYSTEM OPERATION 503 includes the capability to analyze the detected trigger event data received from the self-monitoring, self-reporting, and self-repairing virtual assets. In one embodiment, the analysis capability of the responsive action implementation module takes the form of a mapping module used to map specific detected trigger event data to specific responsive action data.

In a specific illustrative example, in one embodiment, the responsive action implementation module receives the detected trigger event data from the trigger event reporting data receipt module and a mapping module is used to analyze the detected trigger event data and identify the detected trigger event. In this specific illustrative example, the mapping module then maps the detected trigger event to a specific responsive action represented and implemented by associated responsive action data.

In one embodiment, once a virtual asset monitoring system is provided at PROVIDE A VIRTUAL ASSET MONITORING SYSTEM OPERATION 503, process flow proceeds to GENERATE VIRTUAL ASSET SELF-MONITORING LOGIC REPRESENTING INSTRUCTIONS FOR DETECTING THE ONE OR MORE TRIGGER EVENTS WITHIN A VIRTUAL ASSET OPERATION 505.

In one embodiment, at GENERATE VIRTUAL ASSET SELF-MONITORING LOGIC REPRESENTING INSTRUCTIONS FOR DETECTING THE ONE OR MORE TRIGGER EVENTS WITHIN A VIRTUAL ASSET OPERATION 505, one or more trigger events are defined and virtual asset self-monitoring logic is generated for monitoring the operational logic of a virtual asset and detecting the one or more defined trigger events.

In various embodiments, the one or more trigger events defined at GENERATE VIRTUAL ASSET SELF-MONITORING LOGIC REPRESENTING INSTRUCTIONS FOR DETECTING THE ONE OR MORE TRIGGER EVENTS WITHIN A VIRTUAL ASSET OPERATION 505 are events, states, or occurrences, that when detected in a virtual asset represent a potential security vulnerability, and/or a deviation from normal virtual asset operation.

In various embodiments, the one or more trigger events defined at GENERATE VIRTUAL ASSET SELF-MONITORING LOGIC REPRESENTING INSTRUCTIONS FOR DETECTING THE ONE OR MORE TRIGGER EVENTS WITHIN A VIRTUAL ASSET OPERATION 505 can include, but are not limited to, one or more of, a network message from a virtual asset directed to a location known to be associated with malicious entities, i.e., a black-listed destination; the frequency of outgoing network messages changing to a level above a defined threshold level, i.e., the frequency of outgoing network messages changing to a level deemed “not normal”; a response to a customer request being directed to a destination that is not the customer location of record; a virtual asset receiving a high-frequency of login attempts that fail; a size of the parameters sent into a virtual asset being outside a defined “normal” range of sizes for parameters; a size of outgoing network messages being outside a defined “normal” range of sizes of outgoing messages; a total amount of data in any one communication connection of a virtual asset exceeding a defined maximum normal size of a communication to a customer; a request to a virtual asset coming in from a location known to be associated with malicious entities, i.e., a black-listed origin location; an internal elapsed time of defined critical operations changing to a time outside a defined range of “normal” values; and/or any other trigger event, or combination of trigger events, as discussed herein, and/or as known in the art at the time of filing, and/or as developed/made available after the time of filing.

In one embodiment, once one or more trigger events are defined at GENERATE VIRTUAL ASSET SELF-MONITORING LOGIC REPRESENTING INSTRUCTIONS FOR DETECTING THE ONE OR MORE TRIGGER EVENTS WITHIN A VIRTUAL ASSET OPERATION 505, virtual asset self-monitoring logic is generated for monitoring the operational logic of a virtual asset and detecting the one or more defined trigger events.

In one embodiment, the virtual asset self-monitoring logic of GENERATE VIRTUAL ASSET SELF-MONITORING LOGIC REPRESENTING INSTRUCTIONS FOR DETECTING THE ONE OR MORE TRIGGER EVENTS WITHIN A VIRTUAL ASSET OPERATION 505 includes machine-readable code and instructions for monitoring the operational logic of the virtual asset and detecting the one or more defined trigger events within the virtual asset

In one embodiment, once one or more trigger events are defined and virtual asset self-monitoring logic is generated for monitoring the operational logic of a virtual asset and detecting the one or more defined trigger events at GENERATE VIRTUAL ASSET SELF-MONITORING LOGIC REPRESENTING INSTRUCTIONS FOR DETECTING THE ONE OR MORE TRIGGER EVENTS WITHIN A VIRTUAL ASSET OPERATION 505, process flow proceeds to GENERATE VIRTUAL ASSET SELF-REPORTING LOGIC REPRESENTING INSTRUCTIONS FOR GENERATING TRIGGER EVENT REPORTING DATA INDICATING A DETECTED TRIGGER EVENT OPERATION 507.

In one embodiment, at GENERATE VIRTUAL ASSET SELF-REPORTING LOGIC REPRESENTING INSTRUCTIONS FOR GENERATING TRIGGER EVENT REPORTING DATA INDICATING A DETECTED TRIGGER EVENT OPERATION 507, virtual asset self-reporting logic is generated for generating trigger event reporting data indicating a detected trigger event if one of the one or more trigger events is detected in a virtual asset by the virtual asset self-monitoring logic of GENERATE VIRTUAL ASSET SELF-MONITORING LOGIC REPRESENTING INSTRUCTIONS FOR DETECTING THE ONE OR MORE TRIGGER EVENTS WITHIN A VIRTUAL ASSET OPERATION 505.

In one embodiment, the virtual asset self-reporting logic of GENERATE VIRTUAL ASSET SELF-REPORTING LOGIC REPRESENTING INSTRUCTIONS FOR GENERATING TRIGGER EVENT REPORTING DATA INDICATING A DETECTED TRIGGER EVENT OPERATION 507 includes machine-readable code and instructions for creating detected trigger event data indicating a detected trigger event, and/or describing the detected trigger event, and/or generating log data representing the detected trigger event.

In one embodiment, once virtual asset self-reporting logic is generated for generating trigger event reporting data indicating a detected trigger event if one of the one or more trigger events is detected in a virtual asset by the virtual asset self-monitoring logic of GENERATE VIRTUAL ASSET SELF-MONITORING LOGIC REPRESENTING INSTRUCTIONS FOR DETECTING THE ONE OR MORE TRIGGER EVENTS WITHIN A VIRTUAL ASSET OPERATION 505 at GENERATE VIRTUAL ASSET SELF-REPORTING LOGIC REPRESENTING INSTRUCTIONS FOR GENERATING TRIGGER EVENT REPORTING DATA INDICATING A DETECTED TRIGGER EVENT OPERATION 507, process flow proceeds to GENERATE SELF-REPORTING COMMUNICATIONS CHANNEL CREATION LOGIC REPRESENTING INSTRUCTIONS FOR OPENING A SELF-REPORTING COMMUNICATIONS CHANNEL BETWEEN A VIRTUAL ASSET AND THE VIRTUAL ASSET MONITORING SYSTEM OPERATION 509.

In one embodiment, at GENERATE SELF-REPORTING COMMUNICATIONS CHANNEL CREATION LOGIC REPRESENTING INSTRUCTIONS FOR OPENING A SELF-REPORTING COMMUNICATIONS CHANNEL BETWEEN A VIRTUAL ASSET AND THE VIRTUAL ASSET MONITORING SYSTEM OPERATION 509, virtual asset self-reporting communications channel creation logic is generated for opening a self-reporting communications channel between a virtual asset and the virtual asset monitoring system of PROVIDE A VIRTUAL ASSET MONITORING SYSTEM OPERATION 503 if one of the one or more trigger events is detected in a virtual asset by the virtual asset self-monitoring logic of GENERATE VIRTUAL ASSET SELF-MONITORING LOGIC REPRESENTING INSTRUCTIONS FOR DETECTING THE ONE OR MORE TRIGGER EVENTS WITHIN A VIRTUAL ASSET OPERATION 505.

In one embodiment, the virtual asset self-reporting communication channel creation logic of GENERATE SELF-REPORTING COMMUNICATIONS CHANNEL CREATION LOGIC REPRESENTING INSTRUCTIONS FOR OPENING A SELF-REPORTING COMMUNICATIONS CHANNEL BETWEEN A VIRTUAL ASSET AND THE VIRTUAL ASSET MONITORING SYSTEM OPERATION 509 includes machine-readable code and instructions for activating a self-reporting communications port, or door, implemented by the virtual asset self-reporting communications channel creation logic in the virtual and thereby opening a self-reporting communications channel between a virtual asset and the virtual asset monitoring system.

In one embodiment, once virtual asset self-reporting communications channel creation logic is generated for opening a self-reporting communications channel between a virtual asset and the virtual asset monitoring system if one of the one or more trigger events is detected in a virtual asset by the virtual asset self-monitoring logic at GENERATE SELF-REPORTING COMMUNICATIONS CHANNEL CREATION LOGIC REPRESENTING INSTRUCTIONS FOR OPENING A SELF-REPORTING COMMUNICATIONS CHANNEL BETWEEN A VIRTUAL ASSET AND THE VIRTUAL ASSET MONITORING SYSTEM OPERATION 509, process flow proceeds to INSTANTIATE A SELF-MONITORING, SELF-REPORTING, AND SELF-REPAIRING VIRTUAL ASSET, INCLUDING THE VIRTUAL ASSET SELF-MONITORING LOGIC, THE VIRTUAL ASSET SELF-REPORTING LOGIC AND THE SELF-REPORTING COMMUNICATIONS CHANNEL CREATION LOGIC OPERATION 511.

In one embodiment, at INSTANTIATE A SELF-MONITORING, SELF-REPORTING, AND SELF-REPAIRING VIRTUAL ASSET, INCLUDING THE VIRTUAL ASSET SELF-MONITORING LOGIC, THE VIRTUAL ASSET SELF-REPORTING LOGIC AND THE SELF-REPORTING COMMUNICATIONS CHANNEL CREATION LOGIC OPERATION 511, one or more self-monitoring, self-reporting, and self-repairing virtual assets, are instantiated in a computing environment.

In one embodiment, the one or more self-monitoring, self-reporting, and self-repairing virtual assets, are instantiated at INSTANTIATE A SELF-MONITORING, SELF-REPORTING, AND SELF-REPAIRING VIRTUAL ASSET, INCLUDING THE VIRTUAL ASSET SELF-MONITORING LOGIC, THE VIRTUAL ASSET SELF-REPORTING LOGIC AND THE SELF-REPORTING COMMUNICATIONS CHANNEL CREATION LOGIC OPERATION 511 in a second computing environment that is distinct from the first computing environment in which the virtual asset monitoring system is implemented.

In one embodiment, the one or more self-monitoring, self-reporting, and self-repairing virtual assets, are instantiated at INSTANTIATE A SELF-MONITORING, SELF-REPORTING, AND SELF-REPAIRING VIRTUAL ASSET, INCLUDING THE VIRTUAL ASSET SELF-MONITORING LOGIC, THE VIRTUAL ASSET SELF-REPORTING LOGIC AND THE SELF-REPORTING COMMUNICATIONS CHANNEL CREATION LOGIC OPERATION 511 in a cloud computing environment that is distinct from a data center in which the virtual asset monitoring system is implemented.

As noted above, as used herein, the term “virtual asset”, such as used in the term “self-monitoring, self-reporting, and self-repairing virtual asset” includes any virtualized entity or resource, and/or part of an actual, or “bare metal” entity.

In various embodiments, any, or all, of the assets making up a given production environment, the computing systems, and/or computing entities 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, and more particularly as self-monitoring, self-reporting, and self-repairing virtual assets.

In one embodiment, the virtual asset self-monitoring logic of GENERATE VIRTUAL ASSET SELF-MONITORING LOGIC REPRESENTING INSTRUCTIONS FOR DETECTING THE ONE OR MORE TRIGGER EVENTS WITHIN A VIRTUAL ASSET OPERATION 505, the virtual asset self-reporting logic of GENERATE VIRTUAL ASSET SELF-REPORTING LOGIC REPRESENTING INSTRUCTIONS FOR GENERATING TRIGGER EVENT REPORTING DATA INDICATING A DETECTED TRIGGER EVENT OPERATION 507, and the virtual asset self-reporting communications channel creation logic of GENERATE SELF-REPORTING COMMUNICATIONS CHANNEL CREATION LOGIC REPRESENTING INSTRUCTIONS FOR OPENING A SELF-REPORTING COMMUNICATIONS CHANNEL BETWEEN A VIRTUAL ASSET AND THE VIRTUAL ASSET MONITORING SYSTEM OPERATION 509, are provided to each of the one or more self-monitoring, self-reporting, and self-repairing virtual assets of INSTANTIATE A SELF-MONITORING, SELF-REPORTING, AND SELF-REPAIRING VIRTUAL ASSET, INCLUDING THE VIRTUAL ASSET SELF-MONITORING LOGIC, THE VIRTUAL ASSET SELF-REPORTING LOGIC AND THE SELF-REPORTING COMMUNICATIONS CHANNEL CREATION LOGIC OPERATION 511.

In one embodiment, at INSTANTIATE A SELF-MONITORING, SELF-REPORTING, AND SELF-REPAIRING VIRTUAL ASSET, INCLUDING THE VIRTUAL ASSET SELF-MONITORING LOGIC, THE VIRTUAL ASSET SELF-REPORTING LOGIC AND THE SELF-REPORTING COMMUNICATIONS CHANNEL CREATION LOGIC OPERATION 511 the virtual asset self-monitoring logic, the virtual asset self-reporting logic, and the virtual asset self-reporting communications channel creation logic, are provided to each of the one or more self-monitoring, self-reporting, and self-repairing virtual assets, using one or more self-monitoring, self-reporting, and self-repairing virtual asset creation templates.

In one embodiment, once one or more self-monitoring, self-reporting, and self-repairing virtual assets, are instantiated in a computing environment at INSTANTIATE A SELF-MONITORING, SELF-REPORTING, AND SELF-REPAIRING VIRTUAL ASSET, INCLUDING THE VIRTUAL ASSET SELF-MONITORING LOGIC, THE VIRTUAL ASSET SELF-REPORTING LOGIC AND THE SELF-REPORTING COMMUNICATIONS CHANNEL CREATION LOGIC OPERATION 511, process flow proceeds to USE THE VIRTUAL ASSET SELF-MONITORING LOGIC TO DETECT A TRIGGER EVENT IN THE SELF-MONITORING, SELF-REPORTING, AND SELF-REPAIRING VIRTUAL ASSET OPERATION 513.

In one embodiment, at USE THE VIRTUAL ASSET SELF-MONITORING LOGIC TO DETECT A TRIGGER EVENT IN THE SELF-MONITORING, SELF-REPORTING, AND SELF-REPAIRING VIRTUAL ASSET OPERATION 513, the virtual asset self-monitoring logic provided to the self-monitoring, self-reporting, and self-repairing virtual assets is used to monitor and detect any of the defined trigger events within the self-monitoring, self-reporting, and self-repairing virtual assets.

In one embodiment, at USE THE VIRTUAL ASSET SELF-MONITORING LOGIC TO DETECT A TRIGGER EVENT IN THE SELF-MONITORING, SELF-REPORTING, AND SELF-REPAIRING VIRTUAL ASSET OPERATION 513 the virtual asset self-monitoring logic is used to monitor and detect any of the defined trigger events within the self-monitoring, self-reporting, and self-repairing virtual assets by monitoring primary virtual asset logic and data used by the self-monitoring, self-reporting, and self-repairing virtual assets in the course of their normal operations and the performance of their assigned functions.

In one embodiment, once the virtual asset self-monitoring logic provided to the self-monitoring, self-reporting, and self-repairing virtual assets is used to monitor and detect any of the defined trigger events within the self-monitoring, self-reporting, and self-repairing virtual assets at USE THE VIRTUAL ASSET SELF-MONITORING LOGIC TO DETECT A TRIGGER EVENT IN THE SELF-MONITORING, SELF-REPORTING, AND SELF-REPAIRING VIRTUAL ASSET OPERATION 513, process flow proceeds to USE THE VIRTUAL ASSET SELF-REPORTING LOGIC TO GENERATE TRIGGER EVENT REPORTING DATA INDICATING THE DETECTED TRIGGER EVENT HAS BEEN DETECTED OPERATION 515.

In one embodiment, if one of the defined trigger events is detected within an affected one of the self-monitoring, self-reporting, and self-repairing virtual assets by the virtual asset self-monitoring logic at USE THE VIRTUAL ASSET SELF-MONITORING LOGIC TO DETECT A TRIGGER EVENT IN THE SELF-MONITORING, SELF-REPORTING, AND SELF-REPAIRING VIRTUAL ASSET OPERATION 513, then, at USE THE VIRTUAL ASSET SELF-REPORTING LOGIC TO GENERATE TRIGGER EVENT REPORTING DATA INDICATING THE DETECTED TRIGGER EVENT HAS BEEN DETECTED OPERATION 515, detected trigger event data associated with, describing, or representing log data associated with, the detected trigger event is generated by the virtual asset self-reporting logic provided to the affected self-monitoring, self-reporting, and self-repairing virtual asset.

In one embodiment, once detected trigger event data associated with, describing, or representing log data associated with, the detected trigger event is generated by the virtual asset self-reporting logic provided to the affected self-monitoring, self-reporting, and self-repairing virtual asset at USE THE VIRTUAL ASSET SELF-REPORTING LOGIC TO GENERATE TRIGGER EVENT REPORTING DATA INDICATING THE DETECTED TRIGGER EVENT HAS BEEN DETECTED OPERATION 515, process flow proceeds to USE THE SELF-REPORTING COMMUNICATIONS CHANNEL CREATION LOGIC TO GENERATE A SELF-REPORTING COMMUNICATIONS CHANNEL BETWEEN THE SELF-MONITORING, SELF-REPORTING, AND SELF-REPAIRING VIRTUAL ASSET AND THE VIRTUAL ASSET MONITORING SYSTEM OPERATION 517.

In one embodiment, once a defined trigger event is detected within the self-monitoring, self-reporting, and self-repairing virtual asset by the virtual asset self-monitoring logic at USE THE SELF-REPORTING COMMUNICATIONS CHANNEL CREATION LOGIC TO GENERATE A SELF-REPORTING COMMUNICATIONS CHANNEL BETWEEN THE SELF-MONITORING, SELF-REPORTING, AND SELF-REPAIRING VIRTUAL ASSET AND THE VIRTUAL ASSET MONITORING SYSTEM OPERATION 517, the virtual asset self-reporting communications channel creation logic provided to the self-monitoring, self-reporting, and self-repairing virtual asset, is used to generate a self-reporting communications channel between the self-monitoring, self-reporting, and self-repairing virtual asset and the virtual asset monitoring system.

As noted above, in one embodiment, at USE THE SELF-REPORTING COMMUNICATIONS CHANNEL CREATION LOGIC TO GENERATE A SELF-REPORTING COMMUNICATIONS CHANNEL BETWEEN THE SELF-MONITORING, SELF-REPORTING, AND SELF-REPAIRING VIRTUAL ASSET AND THE VIRTUAL ASSET MONITORING SYSTEM OPERATION 517, the virtual asset self-reporting communications channel creation logic generates a self-reporting communications channel by activating a self-reporting virtual asset self-reporting communications port pre-deployed, and/or implemented by, the virtual asset self-reporting communications channel creation logic.

In one embodiment, the self-reporting communications channel generated by the virtual asset self-reporting communications channel creation logic at USE THE SELF-REPORTING COMMUNICATIONS CHANNEL CREATION LOGIC TO GENERATE A SELF-REPORTING COMMUNICATIONS CHANNEL BETWEEN THE SELF-MONITORING, SELF-REPORTING, AND SELF-REPAIRING VIRTUAL ASSET AND THE VIRTUAL ASSET MONITORING SYSTEM OPERATION 517 is a communications channel distinct, and separate from, the various other “normal” communications channels utilized by the self-monitoring, self-reporting, and self-repairing virtual assets, and/or other assets within the computing environment, and/or production environment, associated with the self-monitoring, self-reporting, and self-repairing virtual assets.

Consequently, in one embodiment, the self-reporting communications channel generated by the virtual asset self-reporting communications channel creation logic at USE THE SELF-REPORTING COMMUNICATIONS CHANNEL CREATION LOGIC TO GENERATE A SELF-REPORTING COMMUNICATIONS CHANNEL BETWEEN THE SELF-MONITORING, SELF-REPORTING, AND SELF-REPAIRING VIRTUAL ASSET AND THE VIRTUAL ASSET MONITORING SYSTEM OPERATION 517 is not subject to manipulation, and/or termination, by a malicious party that may have taken control of the self-monitoring, self-reporting, and self-repairing virtual asset.

In addition, the self-reporting communications channel generated by the virtual asset self-reporting communications channel creation logic at USE THE SELF-REPORTING COMMUNICATIONS CHANNEL CREATION LOGIC TO GENERATE A SELF-REPORTING COMMUNICATIONS CHANNEL BETWEEN THE SELF-MONITORING, SELF-REPORTING, AND SELF-REPAIRING VIRTUAL ASSET AND THE VIRTUAL ASSET MONITORING SYSTEM OPERATION 517 is not dependent on security policy implementation systems and entities outside of the self-monitoring, self-reporting, and self-repairing virtual asset, other than the virtual asset monitoring system.

In one embodiment, once the virtual asset self-reporting communications channel creation logic provided to the self-monitoring, self-reporting, and self-repairing virtual asset, is used to generate a self-reporting communications channel between the self-monitoring, self-reporting, and self-repairing virtual asset and the virtual asset monitoring system at USE THE SELF-REPORTING COMMUNICATIONS CHANNEL CREATION LOGIC TO GENERATE A SELF-REPORTING COMMUNICATIONS CHANNEL BETWEEN THE SELF-MONITORING, SELF-REPORTING, AND SELF-REPAIRING VIRTUAL ASSET AND THE VIRTUAL ASSET MONITORING SYSTEM OPERATION 517, process flow proceeds to USE THE SELF-REPORTING COMMUNICATIONS CHANNEL TO TRANSFER THE TRIGGER EVENT REPORTING DATA FROM THE SELF-MONITORING, SELF-REPORTING, AND SELF-REPAIRING VIRTUAL ASSET TO THE VIRTUAL ASSET MONITORING SYSTEM OPERATION 519.

In one embodiment, at USE THE SELF-REPORTING COMMUNICATIONS CHANNEL TO TRANSFER THE TRIGGER EVENT REPORTING DATA FROM THE SELF-MONITORING, SELF-REPORTING, AND SELF-REPAIRING VIRTUAL ASSET TO THE VIRTUAL ASSET MONITORING SYSTEM OPERATION 519, the detected trigger event data generated by the virtual asset self-reporting logic at USE THE VIRTUAL ASSET SELF-REPORTING LOGIC TO GENERATE TRIGGER EVENT REPORTING DATA INDICATING THE DETECTED TRIGGER EVENT HAS BEEN DETECTED OPERATION 515 is transferred from the self-monitoring, self-reporting, and self-repairing virtual asset to the virtual asset monitoring system of PROVIDE A VIRTUAL ASSET MONITORING SYSTEM OPERATION 503 using the virtual asset self-reporting communications channel generated by the virtual asset self-reporting communications channel creation logic at USE THE SELF-REPORTING COMMUNICATIONS CHANNEL CREATION LOGIC TO GENERATE A SELF-REPORTING COMMUNICATIONS CHANNEL BETWEEN THE SELF-MONITORING, SELF-REPORTING, AND SELF-REPAIRING VIRTUAL ASSET AND THE VIRTUAL ASSET MONITORING SYSTEM OPERATION 517.

In one embodiment, once the detected trigger event data generated by the virtual asset self-reporting logic at USE THE VIRTUAL ASSET SELF-REPORTING LOGIC TO GENERATE TRIGGER EVENT REPORTING DATA INDICATING THE DETECTED TRIGGER EVENT HAS BEEN DETECTED OPERATION 515 is transferred from the self-monitoring, self-reporting, and self-repairing virtual asset to the virtual asset monitoring system of PROVIDE A VIRTUAL ASSET MONITORING SYSTEM OPERATION 503 using the virtual asset self-reporting communications channel generated by the virtual asset self-reporting communications channel creation logic at USE THE SELF-REPORTING COMMUNICATIONS CHANNEL TO TRANSFER THE TRIGGER EVENT REPORTING DATA FROM THE SELF-MONITORING, SELF-REPORTING, AND SELF-REPAIRING VIRTUAL ASSET TO THE VIRTUAL ASSET MONITORING SYSTEM OPERATION 519, process flow proceeds to GENERATE RESPONSIVE ACTION IMPLEMENTATION DATA IMPLEMENTING ONE OR MORE RESPONSIVE ACTIONS TO THE DETECTED TRIGGER EVENT OPERATION 521.

In one embodiment, at GENERATE RESPONSIVE ACTION IMPLEMENTATION DATA IMPLEMENTING ONE OR MORE RESPONSIVE ACTIONS TO THE DETECTED TRIGGER EVENT OPERATION 521, analysis is performed at the virtual asset monitoring system and the appropriate, or mapped, responsive action implementation data associated with the received trigger event data is identified.

In one embodiment, the analysis performed at GENERATE RESPONSIVE ACTION IMPLEMENTATION DATA IMPLEMENTING ONE OR MORE RESPONSIVE ACTIONS TO THE DETECTED TRIGGER EVENT OPERATION 521 includes mapping the detected trigger event data received to associated responsive action implementation data representing instructions for implementing one or more responsive actions to the trigger event indicated in the trigger event reporting data.

In various embodiments, the one or more responsive actions to the trigger event indicated in the trigger event reporting data represented in the associated responsive action implementation data includes data and instructions for, but not limited to, any of the following operations: ignoring the detected trigger event; requesting that the detected trigger event data no longer be reported; performing one or more scans on all, or part, of the logic and data contained and/or processed by the self-monitoring, self-reporting, and self-repairing virtual assets, in one embodiment to attempt to identify malicious code or activity; obtaining data from the self-monitoring, self-reporting, and self-repairing virtual assets; destroying data within the self-monitoring, self-reporting, and self-repairing virtual assets; directing a transfer of data from within the self-monitoring, self-reporting, and self-repairing virtual assets to a location outside the self-monitoring, self-reporting, and self-repairing virtual assets, e.g., pulling data from the self-monitoring, self-reporting, and self-repairing virtual assets prior to destroying the self-monitoring, self-reporting, and self-repairing virtual assets; closing down one or more communications channels used by the self-monitoring, self-reporting, and self-repairing virtual assets; shutting down, or off, one or more capabilities of the self-monitoring, self-reporting, and self-repairing virtual assets; aborting one or more operations being performed by the self-monitoring, self-reporting, and self-repairing virtual assets; destroying the self-monitoring, self-reporting, and self-repairing virtual assets; and/or generating and/or transferring incorrect and/or deceptive data from the self-monitoring, self-reporting, and self-repairing virtual assets to a location outside the self-monitoring, self-reporting, and self-repairing virtual asset, such as a location or source associated with a malicious party; and/or any other desired responsive actions, or combination of responsive actions, as discussed herein, and/or as known in the art at the time of filing, and/or as developed/become available after the time of filing.

In one embodiment, once analysis is performed at the virtual asset monitoring system and the appropriate, or mapped, responsive action implementation data associated with the received trigger event data is identified at GENERATE RESPONSIVE ACTION IMPLEMENTATION DATA IMPLEMENTING ONE OR MORE RESPONSIVE ACTIONS TO THE DETECTED TRIGGER EVENT OPERATION 521, process flow proceeds to TRANSFER THE RESPONSIVE ACTION IMPLEMENTATION DATA FROM THE VIRTUAL ASSET MONITORING SYSTEM TO THE SELF-MONITORING, SELF-REPORTING, AND SELF-REPAIRING VIRTUAL ASSET OPERATION 523.

In one embodiment, at TRANSFER THE RESPONSIVE ACTION IMPLEMENTATION DATA FROM THE VIRTUAL ASSET MONITORING SYSTEM TO THE SELF-MONITORING, SELF-REPORTING, AND SELF-REPAIRING VIRTUAL ASSET OPERATION 523, the appropriate, or mapped, responsive action implementation data associated with the received trigger event data of GENERATE RESPONSIVE ACTION IMPLEMENTATION DATA IMPLEMENTING ONE OR MORE RESPONSIVE ACTIONS TO THE DETECTED TRIGGER EVENT OPERATION 521 is provided to the self-monitoring, self-reporting, and self-repairing virtual asset.

In one embodiment, at TRANSFER THE RESPONSIVE ACTION IMPLEMENTATION DATA FROM THE VIRTUAL ASSET MONITORING SYSTEM TO THE SELF-MONITORING, SELF-REPORTING, AND SELF-REPAIRING VIRTUAL ASSET OPERATION 523, the appropriate, or mapped, responsive action implementation data associated with the received trigger event data of GENERATE RESPONSIVE ACTION IMPLEMENTATION DATA IMPLEMENTING ONE OR MORE RESPONSIVE ACTIONS TO THE DETECTED TRIGGER EVENT OPERATION 521 is provided to the self-monitoring, self-reporting, and self-repairing virtual asset using the virtual asset self-reporting communication channel, and the virtual asset self-reporting communications port, generated by the virtual asset self-reporting communications channel creation logic provided to the self-monitoring, self-reporting, and self-repairing virtual asset.

In one embodiment, once the appropriate, or mapped, responsive action implementation data associated with the received trigger event data of GENERATE RESPONSIVE ACTION IMPLEMENTATION DATA IMPLEMENTING ONE OR MORE RESPONSIVE ACTIONS TO THE DETECTED TRIGGER EVENT OPERATION 521 is provided to the self-monitoring, self-reporting, and self-repairing virtual asset at TRANSFER THE RESPONSIVE ACTION IMPLEMENTATION DATA FROM THE VIRTUAL ASSET MONITORING SYSTEM TO THE SELF-MONITORING, SELF-REPORTING, AND SELF-REPAIRING VIRTUAL ASSET OPERATION 523, process flow proceeds to USE THE RESPONSIVE ACTION IMPLEMENTATION DATA TO IMPLEMENT THE ONE OR MORE RESPONSIVE ACTIONS TO THE TRIGGER EVENT INDICATED IN THE TRIGGER EVENT REPORTING DATA OPERATION 525.

In one embodiment, at USE THE RESPONSIVE ACTION IMPLEMENTATION DATA TO IMPLEMENT THE ONE OR MORE RESPONSIVE ACTIONS TO THE TRIGGER EVENT INDICATED IN THE TRIGGER EVENT REPORTING DATA OPERATION 525, the appropriate, or mapped, responsive action implementation data is used by the self-monitoring, self-reporting, and self-repairing virtual asset to implement the responsive action associated with the responsive action implementation data.

As noted above, in various embodiments the responsive actions associated with the responsive action implementation data implemented at USE THE RESPONSIVE ACTION IMPLEMENTATION DATA TO IMPLEMENT THE ONE OR MORE RESPONSIVE ACTIONS TO THE TRIGGER EVENT INDICATED IN THE TRIGGER EVENT REPORTING DATA OPERATION 525 can include, but are not limited to, any one or more of, ignoring the detected trigger data; requesting the detected trigger data no longer be sent; performing a scan of selected data within the self-monitoring, self-reporting, and self-repairing virtual asset; obtaining data from the self-monitoring, self-reporting, and self-repairing virtual asset; directing a transfer of data from within the self-monitoring, self-reporting, and self-repairing virtual asset to a location outside the self-monitoring, self-reporting, and self-repairing virtual asset; closing down one or more communications channels used by the self-monitoring, self-reporting, and self-repairing virtual asset; shutting down one or more capabilities of the self-monitoring, self-reporting, and self-repairing virtual asset; aborting one or more operations performed by the self-monitoring, self-reporting, and self-repairing virtual asset; destroying the self-monitoring, self-reporting, and self-repairing virtual asset; generating and/or transferring incorrect and/or deceptive data from the self-monitoring, self-reporting, and self-repairing virtual asset to a location outside the self-monitoring, self-reporting, and self-repairing virtual asset associated with a malicious entity; and/or any other desired responsive actions, or combination of responsive actions, as discussed herein, and/or as known in the art at the time of filing, and/or as developed/become available after the time of filing.

In one embodiment, once the appropriate, or mapped, responsive action implementation data is used by the self-monitoring, self-reporting, and self-repairing virtual asset to implement the responsive action associated with the responsive action implementation data at USE THE RESPONSIVE ACTION IMPLEMENTATION DATA TO IMPLEMENT THE ONE OR MORE RESPONSIVE ACTIONS TO THE TRIGGER EVENT INDICATED IN THE TRIGGER EVENT REPORTING DATA OPERATION 525, process flow proceeds to EXIT OPERATION 530.

In one embodiment, at EXIT OPERATION 530 process 500 for providing self-monitoring, self-reporting, and self-repairing virtual assets is exited to await new data.

Using process 500 for providing self-monitoring, self-reporting, and self-repairing virtual assets, self-monitoring, self-reporting, and self-repairing virtual assets are provided that can independently and automatically detect one or more trigger events within the self-monitoring, self-reporting, and self-repairing virtual asset, generate suspicious event reporting data from the self-monitoring, self-reporting, and self-repairing virtual asset, provide the reporting data to a monitoring system external to the self-monitoring, self-reporting, and self-repairing virtual asset, and automatically implement responsive actions and repairs to the self-monitoring, self-reporting, and self-repairing virtual asset, all without relying detection of the suspicious event by entities outside the self-monitoring, self-reporting, and self-repairing virtual asset itself, and/or any normal communications channels.

Therefore, using the self-monitoring, self-reporting, and self-repairing virtual assets, and the methods and systems for providing self-monitoring, self-reporting, and self-repairing virtual assets discussed herein, virtual assets, and the data processed and stored by virtual assets, are made more secure.

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.

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”, “aggregating”, “alerting”, “applying”, “analyzing”, “associating”, “calculating”, “capturing”, “categorizing”, “classifying”, “comparing”, “creating”, “defining”, “detecting”, “determining”, “distributing”, “encrypting”, “extracting”, “filtering”, “forwarding”, “generating”, “identifying”, “implementing”, “informing”, “monitoring”, “obtaining”, “posting”, “processing”, “providing”, “receiving”, “requesting”, “saving”, “sending”, “storing”, “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.

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 FIGS., 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.

Claims

1. A self-monitoring and self-reporting virtual asset comprising:

virtual asset self-monitoring logic, the virtual asset self-monitoring logic including data and instructions for detecting one or more trigger events within the self-monitoring and self-reporting virtual asset;

virtual asset self-reporting logic, the virtual asset self-reporting logic including data and instructions for generating trigger event reporting data if one of the one or more trigger events is detected in the self-monitoring and self-reporting virtual asset by the virtual asset self-monitoring logic;

self-reporting communications channel creation logic, the self-reporting communications channel creation logic including data and instructions for opening a self-reporting communications channel between the self-monitoring and self-reporting virtual asset and a virtual asset monitoring system if one of the one or more trigger events is detected in the self-monitoring and self-reporting virtual asset by the virtual asset self-monitoring logic; and

trigger event reporting data transfer logic, the trigger event reporting data transfer logic including data and instructions for transferring the trigger event reporting data from the self-monitoring and self-reporting virtual asset to the virtual asset monitoring system if one of the one or more trigger events is detected in the self-monitoring and self-reporting virtual asset by the virtual asset self-monitoring logic.

2. The self-monitoring and self-reporting virtual asset of claim 1 wherein at least one of the one or more trigger events is selected from the group of trigger events consisting of:

a network message from a virtual asset directed to a location known to be associated with malicious entities;

a frequency of outgoing network messages changing level above a defined threshold level;

a response to a customer request being directed to a destination that is not the customer location of record;

a virtual asset receiving a high-frequency of login attempts that fail;

a size of the parameters sent into a virtual asset being outside a defined range;

a size of outgoing network messages being outside a defined range;

a total amount of data in any one communication connection of a virtual asset exceeding a defined maximum;

a request to a virtual asset coming in from a location known to be associated with malicious entities; and

an internal elapsed time of defined critical operations changing to a time outside a defined range.

3. The self-monitoring and self-reporting virtual asset of claim 1 wherein the virtual asset monitoring system is implemented, at least in part, in a first computing environment and the self-monitoring and self-reporting virtual asset is implemented, at least in part, in a second computing environment, the second computing environment being distinct from the first computing environment.

4. The self-monitoring and self-reporting virtual asset of claim 3 wherein the first computing environment is a data center associated with an owner of the self-monitoring and self-reporting virtual asset.

5. The self-monitoring and self-reporting virtual asset of claim 4 wherein the second computing environment is a cloud computing environment in which the self-monitoring and self-reporting virtual asset is instantiated.

6. The self-monitoring and self-reporting virtual asset of claim 1 wherein the self-monitoring and self-reporting virtual asset is a virtual asset selected from the group of the virtual assets consisting of:

a virtual machine;

a virtual server;

a database or data store;

an instance in a cloud environment;

a cloud environment access system;

part of a mobile device;

part of a remote sensor;

part of a server computing system; and

part of a desktop computing system.

7. A self-monitoring, self-reporting, and self-repairing virtual asset comprising:

virtual asset self-monitoring logic, the virtual asset self-monitoring logic including data and instructions for detecting one or more trigger events within the self-monitoring, self-reporting, and self-repairing virtual asset;

virtual asset self-reporting logic, the virtual asset self-reporting logic including data and instructions for generating trigger event reporting data if one of the one or more trigger events is detected in the self-monitoring, self-reporting, and self-repairing virtual asset by the virtual asset self-monitoring logic;

self-reporting communications channel creation logic, the self-reporting communications channel creation logic including data and instructions for opening a self-reporting communications channel between the self-monitoring, self-reporting, and self-repairing virtual asset and a virtual asset monitoring system if one of the one or more trigger events is detected in the self-monitoring, self-reporting, and self-repairing virtual asset by the virtual asset self-monitoring logic;

trigger event reporting data transfer logic, the trigger event reporting data transfer logic including data and instructions for transferring the trigger event reporting data from the self-monitoring, self-reporting, and self-repairing virtual asset to the virtual asset monitoring system if one of the one or more trigger events is detected in the self-monitoring, self-reporting, and self-repairing virtual asset by the virtual asset self-monitoring logic;

responsive action implementation data receipt logic, the responsive action implementation data receipt logic including data and instructions for receiving responsive action implementation data from the virtual asset monitoring system; and

responsive action implementation logic, the responsive action implementation logic including data and instructions for implementing the one or more responsive actions indicated in the responsive action implementation data received by the responsive action implementation data receipt logic.

8. The self-monitoring, self-reporting, and self-repairing virtual asset of claim 7 wherein at least one of the one or more trigger events is selected from the group of trigger events consisting of:

a network message from a virtual asset directed to a location known to be associated with malicious entities;

a network message from a virtual asset directed to a location known to be associated with malicious entities;

a frequency of outgoing network messages changing level above a defined threshold level;

a response to a customer request being directed to a destination that is not the customer location of record;

a virtual asset receiving a high-frequency of login attempts that fail;

a size of the parameters sent into a virtual asset being outside a defined range;

a size of outgoing network messages being outside a defined range;

a total amount of data in any one communication connection of a virtual asset exceeding a defined maximum;

a request to a virtual asset coming in from a location known to be associated with malicious entities; and

an internal elapsed time of defined critical operations changing to a time outside a defined range.

9. The self-monitoring, self-reporting, and self-repairing virtual asset of claim 7 wherein the virtual asset monitoring system is implemented, at least in part, in a first computing environment and the self-monitoring, self-reporting, and self-repairing virtual asset is implemented, at least in part, in a second computing environment, the second computing environment being distinct from the first computing environment.

10. The self-monitoring, self-reporting, and self-repairing virtual asset of claim 9 wherein the first computing environment is a data center associated with an owner of the self-monitoring, self-reporting, and self-repairing virtual asset.

11. The self-monitoring, self-reporting, and self-repairing virtual asset of claim 10 wherein the second computing environment is a cloud computing environment in which the self-monitoring, self-reporting, and self-repairing virtual asset is instantiated.

12. The self-monitoring, self-reporting, and self-repairing virtual asset of claim 7 wherein the self-monitoring, self-reporting, and self-repairing virtual asset is a virtual asset selected from the group of the virtual assets consisting of:

a virtual machine;

a virtual server;

a database or data store;

an instance in a cloud environment;

a cloud environment access system;

part of a mobile device;

part of a remote sensor;

part of a server computing system; and

part of a desktop computing system.

13. The self-monitoring, self-reporting, and self-repairing virtual asset of claim 7 wherein the responsive action implementation data receipt logic receives the responsive action implementation data from the virtual asset monitoring system using the self-reporting communications channel.

14. The self-monitoring, self-reporting, and self-repairing virtual asset of claim 7 wherein at least one of the one or more responsive actions indicated in the responsive action implementation data received by the responsive action implementation data receipt logic of the self-monitoring, self-reporting, and self-repairing virtual asset includes a responsive action selected from the group of responsive actions consisting of:

performing a scan of selected data within the self-monitoring, self-reporting, and self-repairing virtual asset;

obtaining data from the self-monitoring, self-reporting, and self-repairing virtual asset;

directing a transfer of data from within the self-monitoring, self-reporting, and self-repairing virtual asset to a location outside the self-monitoring, self-reporting, and self-repairing virtual asset;

closing down one or more communications channels used by the self-monitoring, self-reporting, and self-repairing virtual asset;

shutting down one or more capabilities of the self-monitoring, self-reporting, and self-repairing virtual asset;

aborting one or more operations performed by the self-monitoring, self-reporting, and self-repairing virtual asset;

destroying the self-monitoring, self-reporting, and self-repairing virtual asset; and

generating and/or transferring incorrect and/or deceptive data from the self-monitoring, self-reporting, and self-repairing virtual asset to a location outside the self-monitoring, self-reporting, and self-repairing virtual asset.

15. A system for providing self-monitoring and self-reporting virtual assets comprising:

at least one processor; and

at least one memory coupled to the at least one processor, the at least one memory having stored therein instructions which when executed by any set of the one or more processors, perform a process for providing self-monitoring and self-reporting virtual assets, the process for providing self-monitoring and self-reporting virtual assets including:

providing a virtual asset monitoring system;

defining one or more trigger events to be reported when detected in a virtual asset;

generating virtual asset self-monitoring logic representing instructions for detecting the one or more trigger events within a virtual asset;

generating virtual asset self-reporting logic representing instructions for generating trigger event reporting data indicating a detected trigger event if one of the one or more trigger events is detected in a virtual asset;

generating virtual asset self-reporting communications channel creation logic representing instructions for opening a self-reporting communications channel between a virtual asset and the virtual asset monitoring system if one of the one or more trigger events is detected a virtual asset;

instantiating a self-monitoring and self-reporting virtual asset, the self-monitoring and self-reporting virtual asset including the virtual asset self-monitoring logic, the virtual asset self-reporting logic, and the virtual asset self-reporting communications channel creation logic;

the self-monitoring and self-reporting virtual asset using the virtual asset self-monitoring logic to detect a trigger event of the one or more trigger events in the self-monitoring and self-reporting virtual asset;

the self-monitoring and self-reporting virtual asset using the virtual asset self-reporting logic to generate trigger event reporting data indicating the detected trigger event has been detected;

the self-monitoring and self-reporting virtual asset using the virtual asset self-reporting communications channel creation logic to generate a self-reporting communications channel between the self-monitoring and self-reporting virtual asset and the virtual asset monitoring system; and

the self-monitoring and self-reporting virtual asset using the self-reporting communications channel to transfer the trigger event reporting data from the self-monitoring and self-reporting virtual asset to the virtual asset monitoring system.

16. The system for providing self-monitoring and self-reporting virtual assets of claim 15 wherein at least one of the one or more trigger events is selected from the group of trigger events consisting of:

a network message from a virtual asset directed to a location known to be associated with malicious entities;

a frequency of outgoing network messages changing level above a defined threshold level;

a response to a customer request being directed to a destination that is not the customer location of record;

a virtual asset receiving a high-frequency of login attempts that fail;

a size of the parameters sent into a virtual asset being outside a defined range;

a size of outgoing network messages being outside a defined range;

a total amount of data in any one communication connection of a virtual asset exceeding a defined maximum;

a request to a virtual asset coming in from a location known to be associated with malicious entities; and

an internal elapsed time of defined critical operations changing to a time outside a defined range.

17. The system for providing self-monitoring and self-reporting virtual assets of claim 15 wherein the virtual asset monitoring system is implemented, at least in part, in a first computing environment and the self-monitoring and self-reporting virtual asset is implemented, at least in part, in a second computing environment, the second computing environment being distinct from the first computing environment.

18. The system for providing self-monitoring and self-reporting virtual assets of claim 17 wherein the first computing environment is a data center associated with an owner of the self-monitoring and self-reporting virtual asset.

19. The system for providing self-monitoring and self-reporting virtual assets of claim 18 wherein the second computing environment is a cloud computing environment in which the self-monitoring and self-reporting virtual is instantiated.

20. The system for providing self-monitoring and self-reporting virtual assets of claim 15 wherein the self-monitoring and self-reporting virtual asset is a virtual asset selected from the group of the virtual assets consisting of:

a virtual machine;

a virtual server;

a database or data store;

an instance in a cloud environment;

a cloud environment access system;

part of a mobile device;

part of a remote sensor;

part of a server computing system; and

part of a desktop computing system.

21. A system for providing self-monitoring, self-reporting, and self-repairing virtual assets comprising:

at least one processor; and

at least one memory coupled to the at least one processor, the at least one memory having stored therein instructions which when executed by any set of the one or more processors, perform a process for providing self-monitoring, self-reporting, and self-repairing virtual assets, the process for providing self-monitoring, self-reporting, and self-repairing virtual assets including:

providing a virtual asset monitoring system;

defining one or more trigger events to be reported when detected in a virtual asset;

generating virtual asset self-monitoring logic representing instructions for detecting the one or more trigger events within a virtual asset;

generating virtual asset self-reporting logic representing instructions for generating trigger event reporting data indicating a detected trigger event if one of the one or more trigger events is detected in a virtual asset;

generating virtual asset self-reporting communications channel creation logic representing instructions for opening a self-reporting communications channel between a virtual asset and the virtual asset monitoring system if one of the one or more trigger events is detected in a virtual asset;

instantiating a self-monitoring, self-reporting, and self-repairing virtual asset, the self-monitoring, self-reporting, and self-repairing virtual asset including the virtual asset self-monitoring logic, the virtual asset self-reporting logic, and the virtual asset self-reporting communications channel creation logic;

the self-monitoring, self-reporting, and self-repairing virtual asset using the virtual asset self-monitoring logic to detect a trigger event of the one or more trigger events in the self-monitoring, self-reporting, and self-repairing virtual asset;

the self-monitoring, self-reporting, and self-repairing virtual asset using the virtual asset self-reporting logic to generate trigger event reporting data indicating the detected trigger event has been detected;

the self-monitoring, self-reporting, and self-repairing virtual asset using the virtual asset self-reporting communications channel creation logic to generate a self-reporting communications channel between the self-monitoring, self-reporting, and self-repairing virtual asset and the virtual asset monitoring system;

the self-monitoring, self-reporting, and self-repairing virtual asset using the self-reporting communications channel to transfer the trigger event reporting data from the self-monitoring, self-reporting, and self-repairing virtual asset to the virtual asset monitoring system;

analyzing the trigger event reporting data;

generating responsive action implementation data representing instructions for implementing one or more responsive actions to the trigger event indicated in the trigger event reporting data;

transferring the responsive action implementation data from the virtual asset monitoring system to the self-monitoring, self-reporting, and self-repairing virtual asset; and

the self-monitoring, self-reporting, and self-repairing virtual asset using the responsive action implementation data to implement the one or more responsive actions to the trigger event indicated in the trigger event reporting data.

22. The system for providing self-monitoring, self-reporting, and self-repairing virtual assets of claim 21 wherein at least one of the one or more trigger events is selected from the group of trigger events consisting of:

a network message from a virtual asset directed to a location known to be associated with malicious entities;

a frequency of outgoing network messages changing level above a defined threshold level;

a response to a customer request being directed to a destination that is not the customer location of record;

a virtual asset receiving a high-frequency of login attempts that fail;

a size of the parameters sent into a virtual asset being outside a defined range;

a size of outgoing network messages being outside a defined range;

a total amount of data in any one communication connection of a virtual asset exceeding a defined maximum;

a request to a virtual asset coming in from a location known to be associated with malicious entities; and

an internal elapsed time of defined critical operations changing to a time outside a defined range.

23. The system for providing self-monitoring, self-reporting, and self-repairing virtual assets of claim 21 wherein the virtual asset monitoring system is implemented, at least in part, in a first computing environment and the self-monitoring, self-reporting, and self-repairing virtual asset is implemented, at least in part, in a second computing environment, the second computing environment being distinct from the first computing environment.

24. The system for providing self-monitoring, self-reporting, and self-repairing virtual assets of claim 23 wherein the first computing environment is a data center associated with an owner of the self-monitoring, self-reporting, and self-repairing virtual asset.

25. The system for providing self-monitoring, self-reporting, and self-repairing virtual assets of claim 24 wherein the second computing environment is a cloud computing environment in which the self-monitoring, self-reporting, and self-repairing virtual asset is instantiated.

26. The system for providing self-monitoring, self-reporting, and self-repairing virtual assets of claim 21 wherein the self-monitoring, self-reporting, and self-repairing virtual asset is a virtual asset selected from the group of virtual assets consisting of:

a virtual machine;

a virtual server;

a database or data store;

an instance in a cloud environment;

a cloud environment access system;

part of a mobile device;

part of a remote sensor;

part of a server computing system; and

part of a desktop computing system.

27. The system for providing self-monitoring, self-reporting, and self-repairing virtual assets of claim 21 wherein the responsive action implementation data is received from the virtual asset monitoring system using the self-reporting communications channel.

28. The system for providing self-monitoring, self-reporting, and self-repairing virtual assets of claim 21 wherein at least one of the one or more responsive actions indicated in the responsive action implementation data received by the responsive action implementation data receipt logic of the self-monitoring, self-reporting, and self-repairing virtual asset includes a responsive action selected from the group of responsive actions consisting of:

performing a scan of selected data within the self-monitoring, self-reporting, and self-repairing virtual asset;

obtaining data from the self-monitoring, self-reporting, and self-repairing virtual asset;

directing a transfer of data from within the self-monitoring, self-reporting, and self-repairing virtual asset to a location outside the self-monitoring, self-reporting, and self-repairing virtual asset;

closing down one or more communications channels used by the self-monitoring, self-reporting, and self-repairing virtual asset;

shutting down one or more capabilities of the self-monitoring, self-reporting, and self-repairing virtual asset;

aborting one or more operations performed by the self-monitoring, self-reporting, and self-repairing virtual asset;

destroying the self-monitoring, self-reporting, and self-repairing virtual asset; and

generating and/or transferring incorrect and/or deceptive data from the self-monitoring, self-reporting, and self-repairing virtual asset to a location outside the self-monitoring, self-reporting, and self-repairing virtual asset.

29. A system for providing self-monitoring and self-reporting virtual assets comprising:

a virtual asset monitoring system; and

one or more self-monitoring and self-reporting virtual assets, each of the one or more self-monitoring and self-reporting virtual assets including:

virtual asset self-monitoring logic, the virtual asset self-monitoring logic including data and instructions for detecting one or more trigger events within the self-monitoring and self-reporting virtual assets;

virtual asset self-reporting logic, the virtual asset self-reporting logic including data and instructions for generating trigger event reporting data if one of the one or more trigger events is detected in the self-monitoring and self-reporting virtual assets by the virtual asset self-monitoring logic;

self-reporting communications channel creation logic, the self-reporting communications channel creation logic including data and instructions for opening a self-reporting communications channel between the self-monitoring and self-reporting virtual assets and the virtual asset monitoring system if one of the one or more trigger events is detected in the self-monitoring and self-reporting virtual assets by the virtual asset self-monitoring logic; and

trigger event reporting data transfer logic, the trigger event reporting data transfer logic including data and instructions for transferring the trigger event reporting data from the self-monitoring and self-reporting virtual assets to the virtual asset monitoring system if one of the one or more trigger events is detected in the self-monitoring and self-reporting virtual assets by the virtual asset self-monitoring logic.

30. The system for providing self-monitoring and self-reporting virtual assets of claim 29 wherein at least one of the one or more trigger events is selected from the group of trigger events consisting of:

a network message from a virtual asset directed to a location known to be associated with malicious entities;

a frequency of outgoing network messages changing level above a defined threshold level;

a response to a customer request being directed to a destination that is not the customer location of record;

a virtual asset receiving a high-frequency of login attempts that fail;

a size of the parameters sent into a virtual asset being outside a defined range;

a size of outgoing network messages being outside a defined range;

a total amount of data in any one communication connection of a virtual asset exceeding a defined maximum;

a request to a virtual asset coming in from a location known to be associated with malicious entities; and

an internal elapsed time of defined critical operations changing to a time outside a defined range.

31. The system for providing self-monitoring and self-reporting virtual assets of claim 29 wherein the virtual asset monitoring system is implemented, at least in part, in a first computing environment and the self-monitoring and self-reporting virtual assets are implemented, at least in part, in a second computing environment, the second computing environment being distinct from the first computing environment.

32. The system for providing self-monitoring and self-reporting virtual assets of claim 31 wherein the first computing environment is a data center associated with an owner of the self-monitoring and self-reporting virtual assets.

33. The system for providing self-monitoring and self-reporting virtual assets of claim 32 wherein the second computing environment is a cloud computing environment in which the self-monitoring and self-reporting virtual assets are instantiated.

34. The system for providing self-monitoring and self-reporting virtual assets of claim 29 wherein at least one of the self-monitoring and self-reporting virtual asset is a virtual asset selected from the group of the virtual assets consisting of:

a virtual machine;

a virtual server;

a database or data store;

an instance in a cloud environment;

a cloud environment access system;

part of a mobile device;

part of a remote sensor;

part of a server computing system; and

part of a desktop computing system.

35. A system for providing self-monitoring, self-reporting, and self-repairing virtual assets comprising:

a virtual asset monitoring system; and

one or more self-monitoring, self-reporting, and self-repairing assets, each of the one or more self-monitoring, self-reporting, and self-repairing virtual assets including:

virtual asset self-monitoring logic, the virtual asset self-monitoring logic including data and instructions for detecting one or more trigger events within the self-monitoring, self-reporting, and self-repairing virtual assets;

virtual asset self-reporting logic, the virtual asset self-reporting logic including data and instructions for generating trigger event reporting data if one of the one or more trigger events is detected in the self-monitoring, self-reporting, and self-repairing virtual assets by the virtual asset self-monitoring logic;

self-reporting communications channel creation logic, the self-reporting communications channel creation logic including data and instructions for opening a self-reporting communications channel between the self-monitoring, self-reporting, and self-repairing virtual assets and the virtual asset monitoring system if one of the one or more trigger events is detected in the self-monitoring, self-reporting, and self-repairing virtual assets by the virtual asset self-monitoring logic;

trigger event reporting data transfer logic, the trigger event reporting data transfer logic including data and instructions for transferring the trigger event reporting data from the self-monitoring, self-reporting, and self-repairing virtual assets to the virtual asset monitoring system if one of the one or more trigger events is detected in the self-monitoring, self-reporting, and self-repairing virtual assets by the virtual asset self-monitoring logic;

responsive action implementation data receipt logic, the responsive action implementation data receipt logic including data and instructions for receiving responsive action implementation data from the virtual asset monitoring system; and

responsive action implementation logic, the responsive action implementation logic including data and instructions for implementing the one or more responsive actions indicated in the responsive action implementation data received by the responsive action implementation data receipt logic.

36. The system for providing self-monitoring, self-reporting, and self-repairing virtual assets of claim 35 wherein at least one of the one or more trigger events is selected from the group of trigger events consisting of:

a network message from a virtual asset directed to a location known to be associated with malicious entities;

a frequency of outgoing network messages changing level above a defined threshold level;

a response to a customer request being directed to a destination that is not the customer location of record;

a virtual asset receiving a high-frequency of login attempts that fail;

a size of the parameters sent into a virtual asset being outside a defined range;

a size of outgoing network messages being outside a defined range;

a total amount of data in any one communication connection of a virtual asset exceeding a defined maximum;

a request to a virtual asset coming in from a location known to be associated with malicious entities; and

an internal elapsed time of defined critical operations changing to a time outside a defined range.

37. The system for providing self-monitoring, self-reporting, and self-repairing virtual assets of claim 35 wherein the virtual asset monitoring system is implemented, at least in part, in a first computing environment and the self-monitoring, self-reporting, and self-repairing virtual assets are implemented, at least in part, in a second computing environment, the second computing environment being distinct from the first computing environment.

38. The system for providing self-monitoring, self-reporting, and self-repairing virtual assets of claim 37 wherein the first computing environment is a data center associated with an owner of the self-monitoring, self-reporting, and self-repairing virtual assets.

39. The system for providing self-monitoring, self-reporting, and self-repairing virtual assets of claim 38 wherein the second computing environment is a cloud computing environment in which the self-monitoring, self-reporting, and self-repairing virtual assets are instantiated.

40. The system for providing self-monitoring, self-reporting, and self-repairing virtual assets of claim 35 wherein at least one of the self-monitoring, self-reporting, and self-repairing virtual assets is a virtual asset selected from the group of the virtual assets consisting of:

a virtual machine;

a virtual server;

a database or data store;

an instance in a cloud environment;

a cloud environment access system;

part of a mobile device;

part of a remote sensor;

part of a server computing system; and

part of a desktop computing system.

41. The system for providing self-monitoring, self-reporting, and self-repairing virtual assets of claim 35 wherein the responsive action implementation data receipt logic receives the responsive action implementation data from the virtual asset monitoring system using the self-reporting communications channel.

42. The system for providing self-monitoring, self-reporting, and self-repairing virtual assets of claim 35 wherein at least one of the one or more responsive actions indicated in the responsive action implementation data received by the responsive action implementation data receipt logic of the self-monitoring, self-reporting, and self-repairing virtual asset includes a responsive action selected from the group of responsive actions consisting of:

performing a scan of selected data within the self-monitoring, self-reporting, and self-repairing virtual asset;

obtaining data from the self-monitoring, self-reporting, and self-repairing virtual asset;

directing a transfer of data from within the self-monitoring, self-reporting, and self-repairing virtual asset to a location outside the self-monitoring, self-reporting, and self-repairing virtual asset;

closing down one or more communications channels used by the self-monitoring, self-reporting, and self-repairing virtual asset;

shutting down one or more capabilities of the self-monitoring, self-reporting, and self-repairing virtual asset;

aborting one or more operations performed by the self-monitoring, self-reporting, and self-repairing virtual asset;

destroying the self-monitoring, self-reporting, and self-repairing virtual asset; and

generating and/or transferring incorrect and/or deceptive data from the self-monitoring, self-reporting, and self-repairing virtual asset to a location outside the self-monitoring, self-reporting, and self-repairing virtual asset.