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.
Claims
exact text as granted — not AI-modifiedWhat is claimed is:
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.Join the waitlist — get patent alerts
Track US2015304343A1 — get alerts on status changes and closely related new filings.
We store only your email — no account needed. See our privacy policy.