US20150304343A1 - Method and system for providing self-monitoring, self-reporting, and self-repairing virtual assets in a cloud computing environment - Google Patents

Method and system for providing self-monitoring, self-reporting, and self-repairing virtual assets in a cloud computing environment Download PDF

Info

Publication number
US20150304343A1
US20150304343A1 US14/256,289 US201414256289A US2015304343A1 US 20150304343 A1 US20150304343 A1 US 20150304343A1 US 201414256289 A US201414256289 A US 201414256289A US 2015304343 A1 US2015304343 A1 US 2015304343A1
Authority
US
United States
Prior art keywords
self
reporting
monitoring
virtual asset
virtual
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Abandoned
Application number
US14/256,289
Inventor
Luis Felipe Cabrera
M. Shannon Lietz
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Intuit Inc
Original Assignee
Intuit Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Intuit Inc filed Critical Intuit Inc
Priority to US14/256,289 priority Critical patent/US20150304343A1/en
Assigned to INTUIT INC. reassignment INTUIT INC. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: LIETZ, M. SHANNON, CABRERA, LUIS FELIPE
Publication of US20150304343A1 publication Critical patent/US20150304343A1/en
Application status is Abandoned legal-status Critical

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44Arrangements for executing specific programs
    • G06F9/455Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533Hypervisors; Virtual machine monitors
    • G06F9/45558Hypervisor-specific management and integration aspects
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/50Monitoring users, programs or devices to maintain the integrity of platforms, e.g. of processors, firmware or operating systems
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/50Monitoring users, programs or devices to maintain the integrity of platforms, e.g. of processors, firmware or operating systems
    • G06F21/55Detecting local intrusion or implementing counter-measures
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance or administration or management of packet switching networks
    • H04L41/08Configuration management of network or network elements
    • H04L41/0876Aspects of the degree of configuration automation
    • H04L41/0886Fully automatic configuration
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance or administration or management of packet switching networks
    • H04L41/50Network service management, i.e. ensuring proper service fulfillment according to an agreement or contract between two parties, e.g. between an IT-provider and a customer
    • H04L41/5019Ensuring SLA
    • H04L41/5025Ensuring SLA by proactively reacting to service quality change, e.g. degradation or upgrade, by reconfiguration
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance or administration or management of packet switching networks
    • H04L41/50Network service management, i.e. ensuring proper service fulfillment according to an agreement or contract between two parties, e.g. between an IT-provider and a customer
    • H04L41/5032Generating service level reports
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00Network architectures or network communication protocols for network security
    • H04L63/14Network architectures or network communication protocols for network security for detecting or protecting against malicious traffic
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00Network architectures or network communication protocols for network security
    • H04L63/14Network architectures or network communication protocols for network security for detecting or protecting against malicious traffic
    • H04L63/1408Network architectures or network communication protocols for network security for detecting or protecting against malicious traffic by monitoring network traffic
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00Network architectures or network communication protocols for network security
    • H04L63/14Network architectures or network communication protocols for network security for detecting or protecting against malicious traffic
    • H04L63/1408Network architectures or network communication protocols for network security for detecting or protecting against malicious traffic by monitoring network traffic
    • H04L63/1416Event detection, e.g. attack signature detection
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00Network architectures or network communication protocols for network security
    • H04L63/14Network architectures or network communication protocols for network security for detecting or protecting against malicious traffic
    • H04L63/1408Network architectures or network communication protocols for network security for detecting or protecting against malicious traffic by monitoring network traffic
    • H04L63/1425Traffic logging, e.g. anomaly detection
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00Network architectures or network communication protocols for network security
    • H04L63/14Network architectures or network communication protocols for network security for detecting or protecting against malicious traffic
    • H04L63/1433Vulnerability analysis
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44Arrangements for executing specific programs
    • G06F9/455Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533Hypervisors; Virtual machine monitors
    • G06F9/45558Hypervisor-specific management and integration aspects
    • G06F2009/45591Monitoring or debugging support
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44Arrangements for executing specific programs
    • G06F9/455Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533Hypervisors; Virtual machine monitors
    • G06F9/45558Hypervisor-specific management and integration aspects
    • G06F2009/45595Network integration; Enabling network access in virtual machine instances
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance or administration or management of packet switching networks
    • H04L41/50Network service management, i.e. ensuring proper service fulfillment according to an agreement or contract between two parties, e.g. between an IT-provider and a customer
    • H04L41/508Network service management, i.e. ensuring proper service fulfillment according to an agreement or contract between two parties, e.g. between an IT-provider and a customer based on type of value added network service under agreement
    • H04L41/5096Network service management, i.e. ensuring proper service fulfillment according to an agreement or contract between two parties, e.g. between an IT-provider and a customer based on type of value added network service under agreement wherein the managed service relates to distributed or central networked applications

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 (42)

What 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.
US14/256,289 2014-04-18 2014-04-18 Method and system for providing self-monitoring, self-reporting, and self-repairing virtual assets in a cloud computing environment Abandoned US20150304343A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US14/256,289 US20150304343A1 (en) 2014-04-18 2014-04-18 Method and system for providing self-monitoring, self-reporting, and self-repairing virtual assets in a cloud computing environment

Applications Claiming Priority (9)

Application Number Priority Date Filing Date Title
US14/256,289 US20150304343A1 (en) 2014-04-18 2014-04-18 Method and system for providing self-monitoring, self-reporting, and self-repairing virtual assets in a cloud computing environment
AU2015247499A AU2015247499A1 (en) 2014-04-18 2015-04-17 Method and system for providing self-monitoring, self-reporting, and self-repairing virtual assets in a cloud computing environment
EP15779347.2A EP3132349A4 (en) 2014-04-18 2015-04-17 Method and system for providing self-monitoring, self-reporting, and self-repairing virtual assets in a cloud computing environment
CA2943301A CA2943301A1 (en) 2014-04-18 2015-04-17 Method and system for providing self-monitoring, self-reporting, and self-repairing virtual assets in a cloud computing environment
PCT/US2015/026312 WO2015161162A1 (en) 2014-04-18 2015-04-17 Method and system for providing self-monitoring, self-reporting, and self-repairing virtual assets in a cloud computing environment
US15/356,985 US10055247B2 (en) 2014-04-18 2016-11-21 Method and system for enabling self-monitoring virtual assets to correlate external events with characteristic patterns associated with the virtual assets
US15/581,835 US9923909B2 (en) 2014-02-03 2017-04-28 System and method for providing a self-monitoring, self-reporting, and self-repairing virtual asset configured for extrusion and intrusion detection and threat scoring in a cloud computing environment
US15/903,963 US10360062B2 (en) 2014-02-03 2018-02-23 System and method for providing a self-monitoring, self-reporting, and self-repairing virtual asset configured for extrusion and intrusion detection and threat scoring in a cloud computing environment
US16/054,796 US20180341512A1 (en) 2014-04-18 2018-08-03 Method and system for enabling self-monitoring virtual assets to correlate external events with characteristic patterns associated with the virtual assets

Related Parent Applications (2)

Application Number Title Priority Date Filing Date
US14/448,405 Continuation US9516044B2 (en) 2014-07-31 2014-07-31 Method and system for correlating self-reporting virtual asset data with external events to generate an external event identification database
US15/067,528 Continuation US9686301B2 (en) 2014-02-03 2016-03-11 Method and system for virtual asset assisted extrusion and intrusion detection and threat scoring in a cloud computing environment

Related Child Applications (3)

Application Number Title Priority Date Filing Date
US14/448,405 Continuation US9516044B2 (en) 2014-07-31 2014-07-31 Method and system for correlating self-reporting virtual asset data with external events to generate an external event identification database
US15/356,985 Continuation US10055247B2 (en) 2014-04-18 2016-11-21 Method and system for enabling self-monitoring virtual assets to correlate external events with characteristic patterns associated with the virtual assets
US15/581,835 Continuation US9923909B2 (en) 2014-02-03 2017-04-28 System and method for providing a self-monitoring, self-reporting, and self-repairing virtual asset configured for extrusion and intrusion detection and threat scoring in a cloud computing environment

Publications (1)

Publication Number Publication Date
US20150304343A1 true US20150304343A1 (en) 2015-10-22

Family

ID=54322989

Family Applications (5)

Application Number Title Priority Date Filing Date
US14/256,289 Abandoned US20150304343A1 (en) 2014-04-18 2014-04-18 Method and system for providing self-monitoring, self-reporting, and self-repairing virtual assets in a cloud computing environment
US15/356,985 Active US10055247B2 (en) 2014-04-18 2016-11-21 Method and system for enabling self-monitoring virtual assets to correlate external events with characteristic patterns associated with the virtual assets
US15/581,835 Active US9923909B2 (en) 2014-02-03 2017-04-28 System and method for providing a self-monitoring, self-reporting, and self-repairing virtual asset configured for extrusion and intrusion detection and threat scoring in a cloud computing environment
US15/903,963 Active US10360062B2 (en) 2014-02-03 2018-02-23 System and method for providing a self-monitoring, self-reporting, and self-repairing virtual asset configured for extrusion and intrusion detection and threat scoring in a cloud computing environment
US16/054,796 Pending US20180341512A1 (en) 2014-04-18 2018-08-03 Method and system for enabling self-monitoring virtual assets to correlate external events with characteristic patterns associated with the virtual assets

Family Applications After (4)

Application Number Title Priority Date Filing Date
US15/356,985 Active US10055247B2 (en) 2014-04-18 2016-11-21 Method and system for enabling self-monitoring virtual assets to correlate external events with characteristic patterns associated with the virtual assets
US15/581,835 Active US9923909B2 (en) 2014-02-03 2017-04-28 System and method for providing a self-monitoring, self-reporting, and self-repairing virtual asset configured for extrusion and intrusion detection and threat scoring in a cloud computing environment
US15/903,963 Active US10360062B2 (en) 2014-02-03 2018-02-23 System and method for providing a self-monitoring, self-reporting, and self-repairing virtual asset configured for extrusion and intrusion detection and threat scoring in a cloud computing environment
US16/054,796 Pending US20180341512A1 (en) 2014-04-18 2018-08-03 Method and system for enabling self-monitoring virtual assets to correlate external events with characteristic patterns associated with the virtual assets

Country Status (5)

Country Link
US (5) US20150304343A1 (en)
EP (1) EP3132349A4 (en)
AU (1) AU2015247499A1 (en)
CA (1) CA2943301A1 (en)
WO (1) WO2015161162A1 (en)

Cited By (17)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20150324216A1 (en) * 2014-05-12 2015-11-12 Netapp, Inc. Self-repairing configuration service for virtual machine migration
US20160065690A1 (en) * 2014-08-27 2016-03-03 Kabushiki Kaisha Toshiba System and method for selecting virtual desktop environment
US9459987B2 (en) 2014-03-31 2016-10-04 Intuit Inc. Method and system for comparing different versions of a cloud based application in a production environment using segregated backend systems
US9516064B2 (en) 2013-10-14 2016-12-06 Intuit Inc. Method and system for dynamic and comprehensive vulnerability management
US9596251B2 (en) 2014-04-07 2017-03-14 Intuit Inc. Method and system for providing security aware applications
US9686301B2 (en) 2014-02-03 2017-06-20 Intuit Inc. Method and system for virtual asset assisted extrusion and intrusion detection and threat scoring in a cloud computing environment
US9742794B2 (en) 2014-05-27 2017-08-22 Intuit Inc. Method and apparatus for automating threat model generation and pattern identification
US9888025B2 (en) 2014-02-27 2018-02-06 Intuit Inc. Method and system for providing an efficient asset management and verification service
US9900322B2 (en) 2014-04-30 2018-02-20 Intuit Inc. Method and system for providing permissions management
US9923909B2 (en) 2014-02-03 2018-03-20 Intuit Inc. System and method for providing a self-monitoring, self-reporting, and self-repairing virtual asset configured for extrusion and intrusion detection and threat scoring in a cloud computing environment
US10007714B2 (en) * 2015-03-05 2018-06-26 Microsoft Technology Licensing, Llc Ongoing management for pre-planned handling of digital presence
US10013181B2 (en) 2015-12-07 2018-07-03 International Business Machines Corporation Distributed storage of data in a local storage and a heterogeneous cloud
US10050997B2 (en) 2014-06-30 2018-08-14 Intuit Inc. Method and system for secure delivery of information to computing environments
US10122832B2 (en) * 2015-12-07 2018-11-06 International Business Machines Corporation Communications of usernames and passwords to a plurality of cloud storages via a plurality of communications protocols that change over time
US10171585B2 (en) 2015-12-07 2019-01-01 International Business Machines Corporation Method, system, and computer program product for distributed storage of data in a heterogeneous cloud
US10216531B2 (en) 2014-05-12 2019-02-26 Netapp, Inc. Techniques for virtual machine shifting
US10382528B2 (en) 2015-05-27 2019-08-13 Microsoft Technology Licensing, Llc Disposition actions in digital asset management based on trigger events

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9088541B2 (en) 2013-05-31 2015-07-21 Catbird Networks, Inc. Systems and methods for dynamic network security control and configuration
US10205736B2 (en) * 2017-02-27 2019-02-12 Catbird Networks, Inc. Behavioral baselining of network systems

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20110167494A1 (en) * 2009-12-31 2011-07-07 Bowen Brian M Methods, systems, and media for detecting covert malware
US20130263226A1 (en) * 2012-01-22 2013-10-03 Frank W. Sudia False Banking, Credit Card, and Ecommerce System
US20140096134A1 (en) * 2012-10-02 2014-04-03 Ca, Inc. System and method for enforcement of security controls on virtual machines throughout life cycle state changes
US20140189090A1 (en) * 2009-09-03 2014-07-03 C3Dna, Inc. Apparatus and methods for cognitive containters to optimize managed computations and computing resources

Family Cites Families (420)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5712641A (en) 1996-02-28 1998-01-27 Electro-Radiation Incorporated Interference cancellation system for global positioning satellite receivers
US5731991A (en) 1996-05-03 1998-03-24 Electronic Data Systems Corporation Software product evaluation
US5732218A (en) 1997-01-02 1998-03-24 Lucent Technologies Inc. Management-data-gathering system for gathering on clients and servers data regarding interactions between the servers, the clients, and users of the clients during real use of a network of clients and servers
US6085224A (en) 1997-03-11 2000-07-04 Intracept, Inc. Method and system for responding to hidden data and programs in a datastream
US7403922B1 (en) 1997-07-28 2008-07-22 Cybersource Corporation Method and apparatus for evaluating fraud risk in an electronic commerce transaction
US6202066B1 (en) 1997-11-19 2001-03-13 The United States Of America As Represented By The Secretary Of Commerce Implementation of role/group permission association using object access type
JP3693807B2 (en) 1998-03-17 2005-09-14 富士通株式会社 Client / server system, computer and recording medium
US6549932B1 (en) 1998-06-03 2003-04-15 International Business Machines Corporation System, method and computer program product for discovery in a distributed computing environment
US20120151553A1 (en) 2005-11-16 2012-06-14 Azos Ai, Llc System, method, and apparatus for data cognition incorporating autonomous security protection
US6321338B1 (en) 1998-11-09 2001-11-20 Sri International Network surveillance
US6205552B1 (en) 1998-12-31 2001-03-20 Mci Worldcom, Inc. Method and apparatus for checking security vulnerability of networked devices
US6343236B1 (en) 1999-04-02 2002-01-29 General Electric Company Method and system for analyzing fault log data for diagnostics
US6651183B1 (en) 1999-10-28 2003-11-18 International Business Machines Corporation Technique for referencing failure information representative of multiple related failures in a distributed computing environment
US6748584B1 (en) 1999-12-29 2004-06-08 Veritas Operating Corporation Method for determining the degree to which changed code has been exercised
US6907546B1 (en) 2000-03-27 2005-06-14 Accenture Llp Language-driven interface for an automated testing framework
KR100390853B1 (en) 2000-06-07 2003-07-10 차상균 A Logging Method and System for Highly Parallel Recovery Operation in Main-Memory Transaction Processing Systems
US7925527B1 (en) 2000-08-16 2011-04-12 Sparta Systems, Inc. Process control system utilizing a database system to monitor a project's progress and enforce a workflow of activities within the project
US20110238855A1 (en) 2000-09-25 2011-09-29 Yevgeny Korsunsky Processing data flows with a data flow processor
US8010469B2 (en) 2000-09-25 2011-08-30 Crossbeam Systems, Inc. Systems and methods for processing data flows
US20020066034A1 (en) 2000-10-24 2002-05-30 Schlossberg Barry J. Distributed network security deception system
MXPA03006024A (en) 2001-01-02 2005-02-14 Trusecure Corp Object-oriented method, system and medium for risk management by creating inter-dependency between objects, criteria and metrics.
US6782501B2 (en) 2001-01-23 2004-08-24 Cadence Design Systems, Inc. System for reducing test data volume in the testing of logic products
US6985955B2 (en) 2001-01-29 2006-01-10 International Business Machines Corporation System and method for provisioning resources to users based on roles, organizational information, attributes and third-party information or authorizations
AU2002244083A1 (en) 2001-01-31 2002-08-12 Timothy David Dodd Method and system for calculating risk in association with a security audit of a computer network
US20020103801A1 (en) 2001-01-31 2002-08-01 Lyons Martha L. Centralized clearinghouse for community identity information
WO2002079907A2 (en) 2001-03-29 2002-10-10 Accenture Llp Overall risk in a system
US7228438B2 (en) 2001-04-30 2007-06-05 Matsushita Electric Industrial Co., Ltd. Computer network security system employing portable storage device
WO2002091182A2 (en) 2001-05-08 2002-11-14 Teradyne, Inc. Facilitating comparisons between simulated and actual behavior of electronic devices
US6944775B2 (en) 2001-07-26 2005-09-13 Networks Associates Technology, Inc. Scanner API for executing multiple scanning engines
US20030037263A1 (en) 2001-08-08 2003-02-20 Trivium Systems Inc. Dynamic rules-based secure data access system for business computer platforms
US7093294B2 (en) 2001-10-31 2006-08-15 International Buisiness Machines Corporation System and method for detecting and controlling a drone implanted in a network attached device such as a computer
US7603440B1 (en) 2001-11-09 2009-10-13 Persystent Technology Corporation System and method for management of end user computing devices
US20030110392A1 (en) 2001-12-06 2003-06-12 Aucsmith David W. Detecting intrusions
US7174566B2 (en) 2002-02-01 2007-02-06 Intel Corporation Integrated network intrusion detection
US6715084B2 (en) 2002-03-26 2004-03-30 Bellsouth Intellectual Property Corporation Firewall system and method via feedback from broad-scope monitoring for intrusion detection
US7577722B1 (en) 2002-04-05 2009-08-18 Vmware, Inc. Provisioning of computer systems using virtual machines
WO2003088119A1 (en) 2002-04-08 2003-10-23 Topcoder, Inc. System and method for soliciting proposals for software development services
CA2381737A1 (en) 2002-04-15 2003-10-15 Ibm Canada Limited-Ibm Canada Limitee Framework for managing data that provides correlation information in a distributed computing system
BR0215761A (en) 2002-06-18 2006-11-28 Computer Ass Think Inc methods and systems for managing enterprise resources
US20040006704A1 (en) 2002-07-02 2004-01-08 Dahlstrom Dale A. System and method for determining security vulnerabilities
US7418733B2 (en) 2002-08-26 2008-08-26 International Business Machines Corporation Determining threat level associated with network activity
US7114183B1 (en) 2002-08-28 2006-09-26 Mcafee, Inc. Network adaptive baseline monitoring system and method
US7231664B2 (en) 2002-09-04 2007-06-12 Secure Computing Corporation System and method for transmitting and receiving secure data in a virtual private group
US7055062B2 (en) 2002-10-31 2006-05-30 General Electric Company Method, system and program product for establishing a self-diagnosing and self-repairing automated system
US7047448B2 (en) * 2002-11-21 2006-05-16 Bitfone Corporation Software self-repair toolkit for electronic devices
US8332464B2 (en) 2002-12-13 2012-12-11 Anxebusiness Corp. System and method for remote network access
CN1650274A (en) 2002-12-26 2005-08-03 富士通株式会社 Operation managing method and operation managing server
US7779247B2 (en) 2003-01-09 2010-08-17 Jericho Systems Corporation Method and system for dynamically implementing an enterprise resource policy
US7596625B2 (en) 2003-01-27 2009-09-29 Microsoft Corporation Peer-to-peer grouping interfaces and methods
US7730446B2 (en) 2003-03-12 2010-06-01 Microsoft Corporation Software business process model
CA2424006A1 (en) 2003-03-28 2004-09-28 Ibm Canada Limited - Ibm Canada Limitee A technique to generically manage extensible correlation data
US20040249973A1 (en) 2003-03-31 2004-12-09 Alkhatib Hasan S. Group agent
US20040249974A1 (en) 2003-03-31 2004-12-09 Alkhatib Hasan S. Secure virtual address realm
US7426745B2 (en) 2003-04-24 2008-09-16 International Business Machines Corporation Methods and systems for transparent data encryption and decryption
US7246156B2 (en) 2003-06-09 2007-07-17 Industrial Defender, Inc. Method and computer program product for monitoring an industrial network
US8261037B2 (en) 2003-07-11 2012-09-04 Ca, Inc. Storage self-healing and capacity planning system and method
US7463590B2 (en) 2003-07-25 2008-12-09 Reflex Security, Inc. System and method for threat detection and response
US8776050B2 (en) 2003-08-20 2014-07-08 Oracle International Corporation Distributed virtual machine monitor for managing multiple virtual resources across multiple physical nodes
US7673297B1 (en) 2003-09-03 2010-03-02 The Directv Group, Inc. Automatic software update detection and flexible installer for set-top boxes
US7493387B2 (en) 2003-09-19 2009-02-17 International Business Machines Corporation Validating software in a grid environment using ghost agents
US7509487B2 (en) 2003-09-29 2009-03-24 Gemalto Inc. Secure networking using a resource-constrained device
US7886348B2 (en) 2003-10-03 2011-02-08 Verizon Services Corp. Security management system for monitoring firewall operation
US7552424B1 (en) 2003-10-06 2009-06-23 Sap Ag Apparatus and method for identifying a system under test
US20050091304A1 (en) 2003-10-27 2005-04-28 Advanced Premise Technologies, Llc Telecommunications device and method
US7437764B1 (en) 2003-11-14 2008-10-14 Symantec Corporation Vulnerability assessment of disk images
US20050114836A1 (en) 2003-11-24 2005-05-26 Jennifer Fu Block box testing in multi-tier application environments
US7337427B2 (en) 2004-01-08 2008-02-26 International Business Machines Corporation Self-healing cross development environment
US7506371B1 (en) 2004-01-22 2009-03-17 Guardium, Inc. System and methods for adaptive behavior based access control
US7216255B2 (en) 2004-01-23 2007-05-08 Microsoft Corporation Adaptive recovery from system failure for application instances that govern message transactions
US7716726B2 (en) 2004-02-13 2010-05-11 Microsoft Corporation System and method for protecting a computing device from computer exploits delivered over a networked environment in a secured communication
US7373524B2 (en) 2004-02-24 2008-05-13 Covelight Systems, Inc. Methods, systems and computer program products for monitoring user behavior for a server application
US20050188222A1 (en) 2004-02-24 2005-08-25 Covelight Systems, Inc. Methods, systems and computer program products for monitoring user login activity for a server application
US7761923B2 (en) 2004-03-01 2010-07-20 Invensys Systems, Inc. Process control methods and apparatus for intrusion detection, protection and network hardening
US8051483B2 (en) 2004-03-12 2011-11-01 Fortinet, Inc. Systems and methods for updating content detection devices and systems
US9027135B1 (en) 2004-04-01 2015-05-05 Fireeye, Inc. Prospective client identification using malware attack detection
US8566946B1 (en) * 2006-04-20 2013-10-22 Fireeye, Inc. Malware containment on connection
JP2005309644A (en) 2004-04-20 2005-11-04 Hitachi Ltd Resource control method and its system
US7827294B2 (en) 2004-05-06 2010-11-02 American Express Travel Related Services Company, Inc. System and method for dynamic security provisioning of computing resources
US8266670B1 (en) 2004-05-06 2012-09-11 American Express Travel Related Services Company, Inc. System and method for dynamic security provisioning of data resources
US7559058B2 (en) 2004-05-11 2009-07-07 Microsoft Corporation Efficient patching
US7490268B2 (en) 2004-06-01 2009-02-10 The Trustees Of Columbia University In The City Of New York Methods and systems for repairing applications
US20050278790A1 (en) 2004-06-10 2005-12-15 International Business Machines Corporation System and method for using security levels to simplify security policy management
US8688820B1 (en) 2004-06-28 2014-04-01 Oracle America, Inc. Methods and apparatus for remote management and self management of servers
US20060037077A1 (en) 2004-08-16 2006-02-16 Cisco Technology, Inc. Network intrusion detection system having application inspection and anomaly detection characteristics
US7944355B2 (en) 2004-09-01 2011-05-17 Microsoft Corporation Security techniques in the RFID framework
US8010460B2 (en) 2004-09-02 2011-08-30 Linkedin Corporation Method and system for reputation evaluation of online users in a social networking scheme
US7543740B2 (en) 2004-09-17 2009-06-09 Digital Envoy, Inc. Fraud analyst smart cookie
WO2006039208A2 (en) 2004-09-22 2006-04-13 Cyberdefender Corporation Threat protection network
US20060064740A1 (en) * 2004-09-22 2006-03-23 International Business Machines Corporation Network threat risk assessment tool
WO2006044835A2 (en) 2004-10-15 2006-04-27 Kenai Systems, Inc. Method, system and apparatus for assessing vulnerability in web services
US20060101519A1 (en) 2004-11-05 2006-05-11 Lasswell Kevin W Method to provide customized vulnerability information to a plurality of organizations
US20060101520A1 (en) 2004-11-05 2006-05-11 Schumaker Troy T Method to manage network security over a distributed network
US7716527B2 (en) 2004-11-08 2010-05-11 International Business Machines Corporation Repair system
US9450966B2 (en) 2004-11-29 2016-09-20 Kip Sign P1 Lp Method and apparatus for lifecycle integrity verification of virtual machines
US7409719B2 (en) 2004-12-21 2008-08-05 Microsoft Corporation Computer security management, such as in a virtual machine or hardened operating system
US8561126B2 (en) 2004-12-29 2013-10-15 International Business Machines Corporation Automatic enforcement of obligations according to a data-handling policy
WO2006071985A2 (en) 2004-12-29 2006-07-06 Alert Logic, Inc. Threat scoring system and method for intrusion detection security networks
US7831570B2 (en) 2004-12-30 2010-11-09 Oracle International Corporation Mandatory access control label security
US7793269B2 (en) 2005-02-15 2010-09-07 Ebay Inc. Parallel software testing based on a normalized configuration
US8095962B2 (en) 2005-02-17 2012-01-10 At&T Intellectual Property I, L.P. Method and system of auditing databases for security compliance
US20060203739A1 (en) 2005-03-14 2006-09-14 Microsoft Corporation Profiling wide-area networks using peer cooperation
US7792256B1 (en) * 2005-03-25 2010-09-07 Arledge Charles E System and method for remotely monitoring, controlling, and managing devices at one or more premises
US7574746B2 (en) 2005-03-31 2009-08-11 International Business Machines Corporation Access validation and management of access permissions to referenced shared resources in a networked environment
US20060293940A1 (en) 2005-04-22 2006-12-28 Igor Tsyganskiy Methods and systems for applying intelligent filters and identifying life cycle events for data elements during business application debugging
US9033225B2 (en) 2005-04-26 2015-05-19 Guy Hefetz Method and system for authenticating internet users
US20060248573A1 (en) 2005-04-28 2006-11-02 Content Guard Holdings, Inc. System and method for developing and using trusted policy based on a social model
US20060272018A1 (en) 2005-05-27 2006-11-30 Mci, Inc. Method and apparatus for detecting denial of service attacks
US7487433B2 (en) 2005-06-10 2009-02-03 Microsoft Corporation Exception handling in content based routing solutions
US8474049B2 (en) 2005-06-28 2013-06-25 Panasonic Corporation Verification method, information processing device, recording medium, verification system, certification program, and verification program
US20070006304A1 (en) 2005-06-30 2007-01-04 Microsoft Corporation Optimizing malware recovery
US8572733B1 (en) 2005-07-06 2013-10-29 Raytheon Company System and method for active data collection in a network security system
US20070027999A1 (en) 2005-07-29 2007-02-01 Allen James P Method for coordinated error tracking and reporting in distributed storage systems
WO2007021836A2 (en) 2005-08-15 2007-02-22 Toutvirtual Inc. Virtual systems management
US8438643B2 (en) 2005-09-22 2013-05-07 Alcatel Lucent Information system service-level security risk analysis
WO2007038517A1 (en) 2005-09-26 2007-04-05 Wiresoft, Inc. Methods, software and apparatus for detecting and neutralizing viruses from computer systems and networks
US7627893B2 (en) 2005-10-20 2009-12-01 International Business Machines Corporation Method and system for dynamic adjustment of computer security based on network activity of users
US20070101400A1 (en) 2005-10-31 2007-05-03 Overcow Corporation Method of providing secure access to computer resources
US20070180509A1 (en) 2005-12-07 2007-08-02 Swartz Alon R Practical platform for high risk applications
US7934229B1 (en) 2005-12-29 2011-04-26 Symantec Corporation Generating options for repairing a computer infected with malicious software
US20070157311A1 (en) 2005-12-29 2007-07-05 Microsoft Corporation Security modeling and the application life cycle
US8255996B2 (en) 2005-12-30 2012-08-28 Extreme Networks, Inc. Network threat detection and mitigation
US20070169204A1 (en) 2006-01-17 2007-07-19 International Business Machines Corporation System and method for dynamic security access
US20070185875A1 (en) 2006-02-09 2007-08-09 International Business Machines Corporation Extensible role based authorization for manageable resources
US7712137B2 (en) 2006-02-27 2010-05-04 Microsoft Corporation Configuring and organizing server security information
US8561127B1 (en) 2006-03-01 2013-10-15 Adobe Systems Incorporated Classification of security sensitive information and application of customizable security policies
US8117104B2 (en) 2006-04-20 2012-02-14 Agiliance, Inc. Virtual asset groups in a compliance management system
CA2547047A1 (en) 2006-05-15 2007-11-15 Embotics Corporation Management of virtual machines using mobile autonomic elements
US20140373144A9 (en) 2006-05-22 2014-12-18 Alen Capalik System and method for analyzing unauthorized intrusion into a computer network
US8312516B1 (en) 2006-06-20 2012-11-13 Workday, Inc. Security permissions with dynamic definition
US20080005223A1 (en) 2006-06-28 2008-01-03 Microsoft Corporation Reputation data for entities and data processing
US8615440B2 (en) 2006-07-12 2013-12-24 Ebay Inc. Self correcting online reputation
US20100077203A1 (en) 2006-07-13 2010-03-25 Keiko Ogawa Relay device
US8194638B2 (en) 2006-07-27 2012-06-05 International Business Machines Corporation Dual network types solution for computer interconnects
US20080044018A1 (en) 2006-07-31 2008-02-21 Scrimsher John P Method and system to detect and prevent computer network intrusion
US8595817B2 (en) 2006-08-01 2013-11-26 Cisco Technology, Inc. Dynamic authenticated perimeter defense
US8789187B1 (en) 2006-09-28 2014-07-22 Whitehat Security, Inc. Pattern tracking and capturing human insight in a web application security scanner
US7788235B1 (en) 2006-09-29 2010-08-31 Symantec Corporation Extrusion detection using taint analysis
US8161475B2 (en) 2006-09-29 2012-04-17 Microsoft Corporation Automatic load and balancing for virtual machines to meet resource requirements
US8181036B1 (en) 2006-09-29 2012-05-15 Symantec Corporation Extrusion detection of obfuscated content
US8612971B1 (en) 2006-10-17 2013-12-17 Manageiq, Inc. Automatic optimization for virtual systems
US20080148398A1 (en) 2006-10-31 2008-06-19 Derek John Mezack System and Method for Definition and Automated Analysis of Computer Security Threat Models
US8191149B2 (en) * 2006-11-13 2012-05-29 Electronics And Telecommunications Research Institute System and method for predicting cyber threat
US8056115B2 (en) 2006-12-11 2011-11-08 International Business Machines Corporation System, method and program product for identifying network-attack profiles and blocking network intrusions
US7996836B1 (en) 2006-12-29 2011-08-09 Symantec Corporation Using a hypervisor to provide computer security
US8108855B2 (en) 2007-01-02 2012-01-31 International Business Machines Corporation Method and apparatus for deploying a set of virtual software resource templates to a set of nodes
US8958562B2 (en) 2007-01-16 2015-02-17 Voltage Security, Inc. Format-preserving cryptographic systems
US7949716B2 (en) 2007-01-24 2011-05-24 Mcafee, Inc. Correlation and analysis of entity attributes
US8176178B2 (en) 2007-01-29 2012-05-08 Threatmetrix Pty Ltd Method for tracking machines on a network using multivariable fingerprinting of passively available information
US7788540B2 (en) 2007-01-31 2010-08-31 Microsoft Corporation Tracking down elusive intermittent failures
WO2008111428A1 (en) 2007-03-14 2008-09-18 Nec Corporation Operation management device, operation management method, and operation management program
US8171485B2 (en) 2007-03-26 2012-05-01 Credit Suisse Securities (Europe) Limited Method and system for managing virtual and real machines
US20080295076A1 (en) 2007-05-23 2008-11-27 Microsoft Corporation Graphical user interface testing
US20080307525A1 (en) 2007-06-05 2008-12-11 Computer Associates Think, Inc. System and method for evaluating security events in the context of an organizational structure
US8661534B2 (en) 2007-06-26 2014-02-25 Microsoft Corporation Security system with compliance checking and remediation
US20090007100A1 (en) 2007-06-28 2009-01-01 Microsoft Corporation Suspending a Running Operating System to Enable Security Scanning
US20090030756A1 (en) 2007-07-27 2009-01-29 Bank Of America Corporation Managing Risk Associated with Various Transactions
WO2009032053A2 (en) 2007-08-14 2009-03-12 Id Rank Security, Inc. High performance, high bandwidth network operating system
US8099787B2 (en) 2007-08-15 2012-01-17 Bank Of America Corporation Knowledge-based and collaborative system for security assessment of web applications
US20100042734A1 (en) 2007-08-31 2010-02-18 Atli Olafsson Proxy server access restriction apparatus, systems, and methods
KR100925176B1 (en) 2007-09-21 2009-11-05 한국전자통신연구원 Apparatus and method for visualizing network state by using geographic information
US8091065B2 (en) 2007-09-25 2012-01-03 Microsoft Corporation Threat analysis and modeling during a software development lifecycle of a software application
US20090089682A1 (en) 2007-09-27 2009-04-02 Rockwell Automation Technologies, Inc. Collaborative environment for sharing visualizations of industrial automation data
US8040883B2 (en) 2007-10-19 2011-10-18 Wayport, Inc. Probe insertion for one or more network address translated addresses
US8286243B2 (en) 2007-10-23 2012-10-09 International Business Machines Corporation Blocking intrusion attacks at an offending host
US8032939B2 (en) 2007-11-06 2011-10-04 Airtight Networks, Inc. Method and system for providing wireless vulnerability management for local area computer networks
US7991726B2 (en) 2007-11-30 2011-08-02 Bank Of America Corporation Intrusion detection system alerts mechanism
US8132231B2 (en) 2007-12-06 2012-03-06 International Business Machines Corporation Managing user access entitlements to information technology resources
EP2235883A4 (en) 2007-12-18 2014-10-01 Seth Cirker Threat based adaptable network and physical security system
US8412931B2 (en) 2007-12-27 2013-04-02 Apple Inc. Techniques for credential strength analysis via failed intruder access attempts
US8838540B2 (en) 2008-01-03 2014-09-16 Groundspeak, Inc. System and method for providing recognized offline modification of a virtual asset
US7925923B1 (en) 2008-01-31 2011-04-12 Hewlett-Packard Development Company, L.P. Migrating a virtual machine in response to failure of an instruction to execute
US8566909B2 (en) 2008-02-01 2013-10-22 Oracle International Corporation Row-level security with expression data type
US8171554B2 (en) 2008-02-04 2012-05-01 Yuval Elovici System that provides early detection, alert, and response to electronic threats
US20090228973A1 (en) 2008-03-06 2009-09-10 Chendil Kumar Techniques for automatic discovery and update of client environmental information in a virtual private network (vpn)
US20090228294A1 (en) 2008-03-10 2009-09-10 Assertid Inc. Method and system for on-line identification assertion
US7908658B1 (en) 2008-03-17 2011-03-15 Trend Micro Incorporated System using IM screener in a client computer to monitor bad reputation web sites in outgoing messages to prevent propagation of IM attacks
US20090254970A1 (en) 2008-04-04 2009-10-08 Avaya Inc. Multi-tier security event correlation and mitigation
US8443440B2 (en) 2008-04-05 2013-05-14 Trend Micro Incorporated System and method for intelligent coordination of host and guest intrusion prevention in virtualized environment
US9063808B2 (en) 2008-05-15 2015-06-23 International Business Machines Corporation Deploying a package for a software application
US8266284B2 (en) 2008-05-16 2012-09-11 Microsoft Corporation System from reputation shaping a peer-to-peer network
US8935692B2 (en) 2008-05-22 2015-01-13 Red Hat, Inc. Self-management of virtual machines in cloud-based networks
US20090300423A1 (en) 2008-05-28 2009-12-03 James Michael Ferris Systems and methods for software test management in cloud-based network
US7899849B2 (en) 2008-05-28 2011-03-01 Zscaler, Inc. Distributed security provisioning
US8341625B2 (en) 2008-05-29 2012-12-25 Red Hat, Inc. Systems and methods for identification and management of cloud-based virtual machines
US8359632B2 (en) 2008-05-30 2013-01-22 Microsoft Corporation Centralized account reputation
US8122503B2 (en) 2008-05-31 2012-02-21 Hewlett-Packard Development Company, L.P. Methods and systems for managing a potential security threat to a network
US9557889B2 (en) 2009-01-28 2017-01-31 Headwater Partners I Llc Service plan design, user interfaces, application programming interfaces, and device management
US9652788B2 (en) 2008-06-18 2017-05-16 Oracle International Corporation Method and apparatus for logging privilege use in a distributed computing environment
US9069599B2 (en) 2008-06-19 2015-06-30 Servicemesh, Inc. System and method for a cloud computing abstraction layer with security zone facilities
US8527631B1 (en) 2008-06-26 2013-09-03 Trend Micro, Inc. Web site reputation service using proxy auto-configuration
US8595282B2 (en) * 2008-06-30 2013-11-26 Symantec Corporation Simplified communication of a reputation score for an entity
US8001422B1 (en) 2008-06-30 2011-08-16 Amazon Technologies, Inc. Shadow testing services
US8224755B2 (en) 2008-07-07 2012-07-17 International Business Machines Corporation Socially derived, graduated access control in collaboration environments
US7894350B2 (en) 2008-07-24 2011-02-22 Zscaler, Inc. Global network monitoring
US9065800B2 (en) 2011-03-18 2015-06-23 Zscaler, Inc. Dynamic user identification and policy enforcement in cloud-based secure web gateways
US8472328B2 (en) 2008-07-31 2013-06-25 Riverbed Technology, Inc. Impact scoring and reducing false positives
CN101374051A (en) 2008-08-22 2009-02-25 中国航天科工集团第二研究院七○六所 Method for evaluating information system risk base on multi-element fusion
US8930275B2 (en) 2008-09-08 2015-01-06 Robin Heizmann Apparatuses, methods and systems for providing a virtual development and deployment environment including real and synthetic data
US20100076987A1 (en) 2008-09-10 2010-03-25 Benjamin Schreiner Trust Profile Aggregation from Various Trust Record Sources
US8321516B2 (en) 2008-09-30 2012-11-27 Aol Inc. Systems and methods for creating and updating reputation records
US8117106B2 (en) 2008-10-30 2012-02-14 Telesign Corporation Reputation scoring and reporting system
EP2469476A3 (en) 2008-10-31 2014-08-20 Accenture Global Services Limited System for controlling user access to a service
US8392496B2 (en) 2008-12-19 2013-03-05 Watchguard Technologies, Inc. Cluster architecture for network security processing
US10115153B2 (en) 2008-12-31 2018-10-30 Fair Isaac Corporation Detection of compromise of merchants, ATMS, and networks
US20100175108A1 (en) 2009-01-02 2010-07-08 Andre Protas Method and system for securing virtual machines by restricting access in connection with a vulnerability audit
US20100199351A1 (en) 2009-01-02 2010-08-05 Andre Protas Method and system for securing virtual machines by restricting access in connection with a vulnerability audit
US20100212010A1 (en) 2009-02-18 2010-08-19 Stringer John D Systems and methods that detect sensitive data leakages from applications
US8977750B2 (en) 2009-02-24 2015-03-10 Red Hat, Inc. Extending security platforms to cloud-based networks
US8387045B2 (en) 2009-03-12 2013-02-26 International Business Machines Corporation Cloning image creation using virtual machine environment
US9177145B2 (en) * 2009-03-24 2015-11-03 Sophos Limited Modified file tracking on virtual machines
US8381289B1 (en) 2009-03-31 2013-02-19 Symantec Corporation Communication-based host reputation system
US8195980B2 (en) * 2009-03-31 2012-06-05 Oracle America, Inc. Virtual machine snapshotting and damage containment
CN101854340B (en) 2009-04-03 2015-04-01 瞻博网络公司 Behavior based communication analysis carried out based on access control information
EP2241977B1 (en) 2009-04-17 2015-05-27 Accenture Global Services Limited Exchangeable application components
US20100287530A1 (en) 2009-05-05 2010-11-11 Borland Software Corporation Requirements definition using interactive prototyping
US9471920B2 (en) 2009-05-15 2016-10-18 Idm Global, Inc. Transaction assessment and/or authentication
US9477671B2 (en) 2009-05-27 2016-10-25 Oracle International Corporation System and method for implementing effective date constraints in a role hierarchy
US9104407B2 (en) 2009-05-28 2015-08-11 Red Hat, Inc. Flexible cloud management with power management support
US8281307B2 (en) 2009-06-01 2012-10-02 International Business Machines Corporation Virtual solution composition and deployment system and method
CA2764390C (en) 2009-06-10 2019-02-26 Ab Initio Technology Llc Generating test data
US9569240B2 (en) 2009-07-21 2017-02-14 Adobe Systems Incorporated Method and system to provision and manage a computing application hosted by a virtual instance of a machine
US8549476B2 (en) 2009-07-30 2013-10-01 Hewlett-Packard Development Company, L.P. Comparison of result of program operation to result of an operation of a different version of the program
US8566932B1 (en) 2009-07-31 2013-10-22 Symantec Corporation Enforcing good network hygiene using reputation-based automatic remediation
US20110034182A1 (en) 2009-08-05 2011-02-10 Oto Technologies, Llc Geographic messaging using location-identified access points
US9081958B2 (en) * 2009-08-13 2015-07-14 Symantec Corporation Using confidence about user intent in a reputation system
US8443448B2 (en) 2009-08-20 2013-05-14 Federal Reserve Bank Of New York System and method for detection of non-compliant software installation
US8789173B2 (en) 2009-09-03 2014-07-22 Juniper Networks, Inc. Protecting against distributed network flood attacks
KR101012872B1 (en) 2009-09-16 2011-02-08 주식회사 팬택 Security apparatus and method for open platform
US8880682B2 (en) 2009-10-06 2014-11-04 Emc Corporation Integrated forensics platform for analyzing IT resources consumed to derive operational and architectural recommendations
US8413894B2 (en) 2009-11-05 2013-04-09 X-Card Holdings, Llc Card with illuminated codes for use in secure transactions
US8429716B2 (en) 2009-11-05 2013-04-23 Novell, Inc. System and method for transparent access and management of user accessible cloud assets
US20120137367A1 (en) 2009-11-06 2012-05-31 Cataphora, Inc. Continuous anomaly detection based on behavior modeling and heterogeneous information analysis
US20110138469A1 (en) 2009-12-03 2011-06-09 Recursion Software, Inc. System and method for resolving vulnerabilities in a computer network
US20110138382A1 (en) 2009-12-03 2011-06-09 Recursion Software, Inc. System and method for loading resources into a virtual machine
US8578375B2 (en) 2009-12-23 2013-11-05 International Business Machines Corporation Virtual machine administration for data center resource managers
US8424091B1 (en) 2010-01-12 2013-04-16 Trend Micro Incorporated Automatic local detection of computer security threats
US8516576B2 (en) * 2010-01-13 2013-08-20 Microsoft Corporation Network intrusion detection with distributed correlation
AU2011209673B2 (en) 2010-01-26 2015-11-19 Emc Corporation System and method for network security including detection of man-in-the-browser attacks
US8819826B2 (en) 2010-01-27 2014-08-26 Mcafee, Inc. Method and system for detection of malware that connect to network destinations through cloud scanning and web reputation
US8874914B2 (en) 2010-02-05 2014-10-28 Accenture Global Services Limited Secure and automated credential information transfer mechanism
US20110202551A1 (en) 2010-02-16 2011-08-18 Lifeworx, Inc. Apparatuses, Methods And Systems For Assurance Of Reputation
US20110208797A1 (en) 2010-02-22 2011-08-25 Full Armor Corporation Geolocation-Based Management of Virtual Applications
US8325727B2 (en) 2010-04-08 2012-12-04 Calix, Inc. Inline packet replication in network devices
US9300688B2 (en) 2010-04-18 2016-03-29 Ca, Inc. Protected application stack and method and system of utilizing
US8621638B2 (en) 2010-05-14 2013-12-31 Mcafee, Inc. Systems and methods for classification of messaging entities
US8574085B1 (en) 2010-05-14 2013-11-05 David Alexander Jackson Artificial cave obstacle course with electronic sensing
US20110296519A1 (en) 2010-05-14 2011-12-01 Mcafee, Inc. Reputation based connection control
US20120174219A1 (en) 2010-05-14 2012-07-05 Mcafee, Inc. Identifying mobile device reputations
US8910278B2 (en) 2010-05-18 2014-12-09 Cloudnexa Managing services in a cloud computing environment
US8639923B2 (en) 2010-05-28 2014-01-28 Dell Products, Lp System and method for component authentication of a secure client hosted virtualization in an information handling system
US8909928B2 (en) 2010-06-02 2014-12-09 Vmware, Inc. Securing customer virtual machines in a multi-tenant cloud
US8510821B1 (en) 2010-06-29 2013-08-13 Amazon Technologies, Inc. Tiered network flow analysis
US8533831B2 (en) 2010-07-02 2013-09-10 Symantec Corporation Systems and methods for alternating malware classifiers in an attempt to frustrate brute-force malware testing
CA2746587C (en) 2010-07-16 2016-10-25 Research In Motion Limited System and method for performing access control
US9270690B2 (en) 2010-07-21 2016-02-23 Seculert Ltd. Network protection system and method
US8607353B2 (en) 2010-07-29 2013-12-10 Accenture Global Services Gmbh System and method for performing threat assessments using situational awareness
WO2012023657A1 (en) 2010-08-16 2012-02-23 주식회사 이세정보 Network-based harmful-program detection method using a virtual machine, and a system comprising the same
US8327373B2 (en) 2010-08-24 2012-12-04 Novell, Inc. System and method for structuring self-provisioning workloads deployed in virtualized data centers
US8474018B2 (en) 2010-09-03 2013-06-25 Ebay Inc. Role-based attribute based access control (RABAC)
US9112841B1 (en) 2010-09-17 2015-08-18 Amazon Technologies, Inc. Appliance backnets in dedicated resource environment
US8954544B2 (en) 2010-09-30 2015-02-10 Axcient, Inc. Cloud-based virtual machines and offices
US8800029B2 (en) 2010-10-04 2014-08-05 International Business Machines Corporation Gathering, storing and using reputation information
US9215244B2 (en) 2010-11-18 2015-12-15 The Boeing Company Context aware network security monitoring for threat detection
US20120144489A1 (en) 2010-12-07 2012-06-07 Microsoft Corporation Antimalware Protection of Virtual Machines
US20120151488A1 (en) 2010-12-10 2012-06-14 International Business Machines Corporation Measuring Transaction Performance Across Application Asynchronous Flows
CA2821095C (en) 2010-12-14 2018-10-02 Early Warning Services, Llc System and method for detecting fraudulent account access and transfers
US8990950B2 (en) 2010-12-27 2015-03-24 International Business Machines Corporation Enabling granular discretionary access control for data stored in a cloud computing environment
US8918785B1 (en) 2010-12-29 2014-12-23 Amazon Technologies, Inc. Managing virtual machine network through security assessment
US8621618B1 (en) 2011-02-07 2013-12-31 Dell Products, Lp System and method for assessing whether a communication contains an attack
US8683585B1 (en) 2011-02-10 2014-03-25 Symantec Corporation Using file reputations to identify malicious file sources in real time
EP2487860B1 (en) 2011-02-10 2013-09-25 Telefónica, S.A. Method and system for improving security threats detection in communication networks
US8726383B2 (en) 2011-02-14 2014-05-13 Ca, Inc. Flow data for security intrusion detection
US8914892B2 (en) 2011-02-14 2014-12-16 International Business Machines Corporation Method and system to enhance accuracy of a data leak prevention (DLP) system
US8903943B2 (en) 2011-02-15 2014-12-02 Salesforce.Com, Inc. Integrating cloud applications and remote jobs
US9141410B2 (en) 2011-03-08 2015-09-22 Rackspace Us, Inc. Pluggable allocation in a cloud computing system
US9239930B2 (en) 2011-03-16 2016-01-19 Successfactors, Inc. System and method for assigning permissions to access data and perform actions in a computer system
WO2012135192A2 (en) 2011-03-28 2012-10-04 Mcafee, Inc. System and method for virtual machine monitor based anti-malware security
US8799997B2 (en) 2011-04-18 2014-08-05 Bank Of America Corporation Secure network cloud architecture
GB2512685B (en) 2011-04-27 2018-11-14 Seven Networks Llc Detection and filtering of malware based on traffic observations made in a distributed mobile traffic management system
US8789192B2 (en) 2011-05-23 2014-07-22 Lockheed Martin Corporation Enterprise vulnerability management
US8555388B1 (en) 2011-05-24 2013-10-08 Palo Alto Networks, Inc. Heuristic botnet detection
US9052939B2 (en) 2011-05-27 2015-06-09 Red Hat, Inc. Data compliance management associated with cloud migration events
US20120311016A1 (en) 2011-06-02 2012-12-06 Recursion Software, Inc. System and method for providing self-healing capabilites in a distributed knowlegde network/intelligent sensor network
US20120311157A1 (en) 2011-06-03 2012-12-06 Erickson Philip J Integrated information technology service management for cloud resources
US8762113B2 (en) 2011-06-03 2014-06-24 Sony Computer Entertainment America Llc Method and apparatus for load testing online server systems
US8955133B2 (en) * 2011-06-09 2015-02-10 Microsoft Corporation Applying antimalware logic without revealing the antimalware logic to adversaries
US20120324572A1 (en) 2011-06-16 2012-12-20 Telefonaktiebolaget L M Ericsson (Publ) Systems and methods that perform application request throttling in a distributed computing environment
US20120324446A1 (en) 2011-06-17 2012-12-20 Microsoft Corporation Virtual machine image composition and signing
US20130007772A1 (en) 2011-06-28 2013-01-03 Unisys Corporation Method and system for automated system migration
TWI476586B (en) 2011-07-13 2015-03-11 Inst Information Industry Cloud-based test system, method and computer readable storage medium storing thereof
US20130019314A1 (en) 2011-07-14 2013-01-17 International Business Machines Corporation Interactive virtual patching using a web application server firewall
US8869036B1 (en) 2011-07-20 2014-10-21 Google Inc. System for troubleshooting site configuration based on real-time analytics data
US10356106B2 (en) 2011-07-26 2019-07-16 Palo Alto Networks (Israel Analytics) Ltd. Detecting anomaly action within a computer network
US8417609B2 (en) 2011-08-19 2013-04-09 Bank Of America Corporation Methods and systems for modeling deposits' data
US20130054792A1 (en) 2011-08-25 2013-02-28 Salesforce.Com, Inc. Cloud-based performance testing of functionality of an application prior to completion of development
US8819832B2 (en) 2011-08-26 2014-08-26 Rapid7, Llc Systems and methods for performing vulnerability scans on virtual machines
US20130055246A1 (en) 2011-08-26 2013-02-28 Rapid7, LLC. Systems and methods for identifying virtual machines in a network
US9275230B2 (en) 2011-08-30 2016-03-01 Hewlett-Packard Development Company, L.P. Communication with a virtual trusted runtime BIOS
US8806005B2 (en) 2011-09-12 2014-08-12 Microsoft Corporation Cross-machine event log correlation
US20130074181A1 (en) * 2011-09-19 2013-03-21 Cisco Technology, Inc. Auto Migration of Services Within a Virtual Data Center
US9811667B2 (en) 2011-09-21 2017-11-07 Mcafee, Inc. System and method for grouping computer vulnerabilities
US9294489B2 (en) 2011-09-26 2016-03-22 Intellectual Discovery Co., Ltd. Method and apparatus for detecting an intrusion on a cloud computing service
US9215153B2 (en) 2011-10-04 2015-12-15 International Business Machines Corporation Providing status information for virtual resource computing environment
US20130091376A1 (en) * 2011-10-05 2013-04-11 International Business Machines Corporation Self-repairing database system
WO2013055807A1 (en) 2011-10-10 2013-04-18 Global Dataguard, Inc Detecting emergent behavior in communications networks
US8850512B2 (en) 2011-10-13 2014-09-30 Mcafee, Inc. Security assessment of virtual machine environments
US9161226B2 (en) 2011-10-17 2015-10-13 Blackberry Limited Associating services to perimeters
US9058486B2 (en) 2011-10-18 2015-06-16 Mcafee, Inc. User behavioral risk assessment
GB2509872A (en) 2011-11-03 2014-07-16 Raytheon Co Intrusion prevention system (IPS) mode for a malware detection system
US8924723B2 (en) 2011-11-04 2014-12-30 International Business Machines Corporation Managing security for computer services
US9843488B2 (en) 2011-11-07 2017-12-12 Netflow Logic Corporation Method and system for confident anomaly detection in computer network traffic
CN103917983B (en) 2011-11-10 2016-11-16 英特尔公司 Means for protecting the electronic device in the virtual boundary, the system and method
US9311160B2 (en) 2011-11-10 2016-04-12 Verizon Patent And Licensing Inc. Elastic cloud networking
US20130124644A1 (en) 2011-11-11 2013-05-16 Mcafee, Inc. Reputation services for a social media identity
US9519472B2 (en) 2011-11-23 2016-12-13 Red Hat, Inc. Automation of virtual machine installation by splitting an installation into a minimal installation and customization
US8813172B2 (en) 2011-12-16 2014-08-19 Microsoft Corporation Protection of data in a mixed use device
US8973147B2 (en) 2011-12-29 2015-03-03 Mcafee, Inc. Geo-mapping system security events
US20130185795A1 (en) 2012-01-12 2013-07-18 Arxceo Corporation Methods and systems for providing network protection by progressive degradation of service
US20130212130A1 (en) 2012-02-15 2013-08-15 Flybits, Inc. Zone Oriented Applications, Systems and Methods
AU2013200916B2 (en) 2012-02-20 2014-09-11 Kl Data Security Pty Ltd Cryptographic Method and System
US9443086B2 (en) 2012-02-23 2016-09-13 Infosys Limited Systems and methods for fixing application vulnerabilities through a correlated remediation approach
US9054917B2 (en) 2012-03-08 2015-06-09 Empire Technology Development Llc Secure migration of virtual machines
US8793766B2 (en) 2012-03-13 2014-07-29 International Business Machines Corporation Method and apparatus for security-aware elasticity of application and services
US8281399B1 (en) 2012-03-28 2012-10-02 Symantec Corporation Systems and methods for using property tables to perform non-iterative malware scans
US9319286B2 (en) 2012-03-30 2016-04-19 Cognizant Business Services Limited Apparatus and methods for managing applications in multi-cloud environments
CN104246808A (en) 2012-03-30 2014-12-24 英特尔公司 Client security scoring
EP2836979A4 (en) 2012-04-06 2018-08-08 Live Nation Entertainment Inc. Methods and systems of inhibiting automated scripts from accessing a ticket site
US8931043B2 (en) 2012-04-10 2015-01-06 Mcafee Inc. System and method for determining and using local reputations of users and hosts to protect information in a network environment
US8789181B2 (en) 2012-04-11 2014-07-22 Ca, Inc. Flow data for security data loss prevention
US8856885B2 (en) 2012-04-30 2014-10-07 Citrix Systems, Inc. Managing cloud zones
US8955091B2 (en) 2012-04-30 2015-02-10 Zscaler, Inc. Systems and methods for integrating cloud services with information management systems
US9385918B2 (en) 2012-04-30 2016-07-05 Cisco Technology, Inc. System and method for secure provisioning of virtualized images in a network environment
EP2663053A3 (en) 2012-05-09 2014-01-01 Computer Security Products, Inc. Methods and apparatus for creating and implementing security policies for resources on a network
US9378255B2 (en) 2012-05-11 2016-06-28 Sap Se Cloud logistics
US9049105B1 (en) 2012-05-11 2015-06-02 Amazon Technologies, Inc. Systems and methods for tracking and managing event records associated with network incidents
US9503463B2 (en) 2012-05-14 2016-11-22 Zimperium, Inc. Detection of threats to networks, based on geographic location
US8959623B2 (en) 2012-05-25 2015-02-17 Ca, Inc. Protecting virtual machine console from misuse, hijacking or eavesdropping in cloud environments
US9043903B2 (en) 2012-06-08 2015-05-26 Crowdstrike, Inc. Kernel-level security agent
US9003023B2 (en) 2012-06-13 2015-04-07 Zscaler, Inc. Systems and methods for interactive analytics of internet traffic
US8813225B1 (en) 2012-06-15 2014-08-19 Amazon Technologies, Inc. Provider-arbitrated mandatory access control policies in cloud computing environments
US8891392B2 (en) 2012-06-21 2014-11-18 Breakingpoint Systems, Inc. Dynamic latency analysis system
US10237290B2 (en) 2012-06-26 2019-03-19 Aeris Communications, Inc. Methodology for intelligent pattern detection and anomaly detection in machine to machine communication network
WO2014004747A2 (en) 2012-06-26 2014-01-03 Lynuxworks, Inc. Systems and methods involving features of hardware virtualization such as separation kernel hypervisors, hypervisors, hypervisor guest context, hypervisor context, rootkit detection/prevention, and/or other features
WO2014008403A1 (en) 2012-07-03 2014-01-09 Visa International Service Association Data protection hub
US9047410B2 (en) 2012-07-18 2015-06-02 Infosys Limited Cloud-based application testing
US8966573B2 (en) 2012-07-20 2015-02-24 Ca, Inc. Self-generation of virtual machine security clusters
US20140040299A1 (en) 2012-08-03 2014-02-06 Cisco Technology, Inc. Automated Method of Detecting Pattern Matches between Converged Infrastructure Models and an Operating Converged Infrastructure
US8756698B2 (en) 2012-08-10 2014-06-17 Nopsec Inc. Method and system for managing computer system vulnerabilities
US8656482B1 (en) 2012-08-20 2014-02-18 Bitdefender IPR Management Ltd. Secure communication using a trusted virtual machine
US9258321B2 (en) 2012-08-23 2016-02-09 Raytheon Foreground Security, Inc. Automated internet threat detection and mitigation system and associated methods
US9317508B2 (en) 2012-09-07 2016-04-19 Red Hat, Inc. Pro-active self-healing in a distributed file system
US20140074560A1 (en) 2012-09-10 2014-03-13 Oracle International Corporation Advanced skill match and reputation management for workforces
US9015795B2 (en) 2012-09-10 2015-04-21 Oracle International Corporation Reputation-based auditing of enterprise application authorization models
US8844045B2 (en) 2012-09-14 2014-09-23 Mastercard International Incorporated Methods and systems for evaluating software for known vulnerabilities
EP2575043B1 (en) 2012-10-15 2014-10-15 Kyriba Method to secure an application executable in a distant server accessible via a public computer network, and improved virtual server.
US8990935B1 (en) 2012-10-17 2015-03-24 Google Inc. Activity signatures and activity replay detection
US9571507B2 (en) 2012-10-21 2017-02-14 Mcafee, Inc. Providing a virtual security appliance architecture to a virtual cloud infrastructure
US20140137257A1 (en) * 2012-11-12 2014-05-15 Board Of Regents, The University Of Texas System System, Method and Apparatus for Assessing a Risk of One or More Assets Within an Operational Technology Infrastructure
US8925076B2 (en) 2012-12-11 2014-12-30 Kaspersky Lab Zao Application-specific re-adjustment of computer security settings
US9323935B2 (en) 2012-12-18 2016-04-26 Mcafee, Inc. User device security profile
US9519801B2 (en) 2012-12-19 2016-12-13 Salesforce.Com, Inc. Systems, methods, and apparatuses for implementing data masking via compression dictionaries
US9021452B2 (en) 2012-12-27 2015-04-28 Commvault Systems, Inc. Automatic identification of storage requirements, such as for use in selling data storage management solutions
US9137263B2 (en) 2013-01-04 2015-09-15 International Business Machines Corporation Generating role-based access control policies based on discovered risk-averse roles
US9130920B2 (en) 2013-01-07 2015-09-08 Zettaset, Inc. Monitoring of authorization-exceeding activity in distributed networks
US9729505B2 (en) 2013-01-31 2017-08-08 Entit Software Llc Security threat analysis
EP2951753A4 (en) 2013-01-31 2016-09-21 Hewlett Packard Entpr Dev Lp Targeted security alerts
US9081957B2 (en) 2013-02-07 2015-07-14 Ryatheon BBN Technologies Corp Dynamic operational watermarking for software and hardware assurance
US9251115B2 (en) 2013-03-07 2016-02-02 Citrix Systems, Inc. Dynamic configuration in cloud computing environments
US20140259169A1 (en) 2013-03-11 2014-09-11 Hewlett-Packard Development Company, L.P. Virtual machines
US9043593B2 (en) 2013-03-11 2015-05-26 International Business Machines Corporation Session attribute propagation through secure database server tiers
US9027087B2 (en) 2013-03-14 2015-05-05 Rackspace Us, Inc. Method and system for identity-based authentication of virtual machines
US8959633B1 (en) * 2013-03-14 2015-02-17 Amazon Technologies, Inc. Detecting anomalous behavior patterns in an electronic environment
US9043912B2 (en) 2013-03-15 2015-05-26 Mehdi Mahvi Method for thwarting application layer hypertext transport protocol flood attacks focused on consecutively similar application-specific data packets
US20140282840A1 (en) 2013-03-15 2014-09-18 True Ultimate Standards Everywhere, Inc. Managing data handling policies
KR101394424B1 (en) 2013-04-22 2014-05-13 한국인터넷진흥원 Hypervisor-based intrusion prevention platform and virtual network intrusion prevention system
US9319425B2 (en) 2013-07-23 2016-04-19 Crypteia Networks S.A. Systems and methods for self-tuning network intrusion detection and prevention
US20150032587A1 (en) 2013-07-29 2015-01-29 Direct Capital Corporation Automated Financing Workflow
US9201738B2 (en) 2013-08-14 2015-12-01 Globalfoundries Inc. Method, computer readable storage medium and computer system for obtaining snapshots of data
US9471474B2 (en) 2013-08-19 2016-10-18 Microsoft Technology Licensing, Llc Cloud deployment infrastructure validation engine
US20150052614A1 (en) 2013-08-19 2015-02-19 International Business Machines Corporation Virtual machine trust isolation in a cloud environment
US9104865B2 (en) 2013-08-29 2015-08-11 International Business Machines Corporation Threat condition management
US9811435B2 (en) 2013-09-03 2017-11-07 Cisco Technology, Inc. System for virtual machine risk monitoring
US9110699B2 (en) 2013-09-19 2015-08-18 International Business Machines Corporation Determining optimal methods for creating virtual machines
US8863284B1 (en) 2013-10-10 2014-10-14 Kaspersky Lab Zao System and method for determining a security status of potentially malicious files
US9246935B2 (en) 2013-10-14 2016-01-26 Intuit Inc. Method and system for dynamic and comprehensive vulnerability management
US10193963B2 (en) 2013-10-24 2019-01-29 Vmware, Inc. Container virtual machines for hadoop
US20150128130A1 (en) 2013-11-01 2015-05-07 Intuit Inc. Method and system for providing and dynamically deploying hardened task specific virtual hosts
US9390288B2 (en) 2013-11-01 2016-07-12 Intuit Inc. Method and system for validating a virtual asset
WO2015066604A1 (en) 2013-11-04 2015-05-07 Crypteia Networks S.A. Systems and methods for identifying infected network infrastructure
US9407602B2 (en) 2013-11-07 2016-08-02 Attivo Networks, Inc. Methods and apparatus for redirecting attacks on a network
US9313281B1 (en) 2013-11-13 2016-04-12 Intuit Inc. Method and system for creating and dynamically deploying resource specific discovery agents for determining the state of a cloud computing environment
US9418236B2 (en) 2013-11-13 2016-08-16 Intuit Inc. Method and system for dynamically and automatically managing resource access permissions
US9148440B2 (en) 2013-11-25 2015-09-29 Imperva, Inc. Coordinated detection and differentiation of denial of service attacks
US9501345B1 (en) 2013-12-23 2016-11-22 Intuit Inc. Method and system for creating enriched log data
US9323926B2 (en) 2013-12-30 2016-04-26 Intuit Inc. Method and system for intrusion and extrusion detection
US20150215327A1 (en) 2014-01-28 2015-07-30 Intuit Inc. Method and system for extrusion and intrusion detection in a cloud computing environment using network communications devices
US20150222653A1 (en) 2014-02-03 2015-08-06 Intuit Inc. Method and system for extrusion and intrusion detection in a cloud computing environment
US9325726B2 (en) 2014-02-03 2016-04-26 Intuit Inc. Method and system for virtual asset assisted extrusion and intrusion detection in a cloud computing environment
US20180152473A1 (en) 2014-02-21 2018-05-31 Intuit Inc. Method and system for creating and deploying virtual assets
US10121007B2 (en) 2014-02-21 2018-11-06 Intuit Inc. Method and system for providing a robust and efficient virtual asset vulnerability management and verification service
US9298927B2 (en) 2014-02-27 2016-03-29 Intuit Inc. Method and system for providing an efficient vulnerability management and verification service
US20150271195A1 (en) 2014-03-18 2015-09-24 Intuit Inc. Method and system for providing temporary secure access enabled virtual assets
US20150269064A1 (en) 2014-03-21 2015-09-24 Intuit Inc. Method and system for testing cloud based applications in a production environment using fabricated user data
US20150278523A1 (en) 2014-03-31 2015-10-01 Intuit Inc. Method and system for testing cloud based applications and services in a production environment using segregated backend systems
US9245117B2 (en) 2014-03-31 2016-01-26 Intuit Inc. Method and system for comparing different versions of a cloud based application in a production environment using segregated backend systems
US9276945B2 (en) 2014-04-07 2016-03-01 Intuit Inc. Method and system for providing security aware applications
US20150304343A1 (en) 2014-04-18 2015-10-22 Intuit Inc. Method and system for providing self-monitoring, self-reporting, and self-repairing virtual assets in a cloud computing environment
US9374389B2 (en) 2014-04-25 2016-06-21 Intuit Inc. Method and system for ensuring an application conforms with security and regulatory controls prior to deployment
US9319415B2 (en) 2014-04-30 2016-04-19 Intuit Inc. Method and system for providing reference architecture pattern-based permissions management
US20150319186A1 (en) 2014-04-30 2015-11-05 Intuit Inc. Method and system for detecting irregularities and vulnerabilities in dedicated hosting environments
US20150341357A1 (en) 2014-05-23 2015-11-26 Intuit Inc. Method and system for access control management using reputation scores
US9330263B2 (en) 2014-05-27 2016-05-03 Intuit Inc. Method and apparatus for automating the building of threat models for the public cloud
US20150347773A1 (en) 2014-05-29 2015-12-03 Intuit Inc. Method and system for implementing data security policies using database classification
US9342690B2 (en) 2014-05-30 2016-05-17 Intuit Inc. Method and apparatus for a scoring service for security threat management
US9866581B2 (en) 2014-06-30 2018-01-09 Intuit Inc. Method and system for secure delivery of information to computing environments
US20150381641A1 (en) 2014-06-30 2015-12-31 Intuit Inc. Method and system for efficient management of security threats in a distributed computing environment
US9473481B2 (en) 2014-07-31 2016-10-18 Intuit Inc. Method and system for providing a virtual asset perimeter
US10102082B2 (en) 2014-07-31 2018-10-16 Intuit Inc. Method and system for providing automated self-healing virtual assets
US9516044B2 (en) 2014-07-31 2016-12-06 Intuit Inc. Method and system for correlating self-reporting virtual asset data with external events to generate an external event identification database
US10042908B2 (en) 2014-09-26 2018-08-07 Oracle International Corporation Method and system for implementing a unified DB clone system

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140189090A1 (en) * 2009-09-03 2014-07-03 C3Dna, Inc. Apparatus and methods for cognitive containters to optimize managed computations and computing resources
US20110167494A1 (en) * 2009-12-31 2011-07-07 Bowen Brian M Methods, systems, and media for detecting covert malware
US20130263226A1 (en) * 2012-01-22 2013-10-03 Frank W. Sudia False Banking, Credit Card, and Ecommerce System
US20140096134A1 (en) * 2012-10-02 2014-04-03 Ca, Inc. System and method for enforcement of security controls on virtual machines throughout life cycle state changes

Cited By (19)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9516064B2 (en) 2013-10-14 2016-12-06 Intuit Inc. Method and system for dynamic and comprehensive vulnerability management
US10360062B2 (en) 2014-02-03 2019-07-23 Intuit Inc. System and method for providing a self-monitoring, self-reporting, and self-repairing virtual asset configured for extrusion and intrusion detection and threat scoring in a cloud computing environment
US9686301B2 (en) 2014-02-03 2017-06-20 Intuit Inc. Method and system for virtual asset assisted extrusion and intrusion detection and threat scoring in a cloud computing environment
US9923909B2 (en) 2014-02-03 2018-03-20 Intuit Inc. System and method for providing a self-monitoring, self-reporting, and self-repairing virtual asset configured for extrusion and intrusion detection and threat scoring in a cloud computing environment
US9888025B2 (en) 2014-02-27 2018-02-06 Intuit Inc. Method and system for providing an efficient asset management and verification service
US9459987B2 (en) 2014-03-31 2016-10-04 Intuit Inc. Method and system for comparing different versions of a cloud based application in a production environment using segregated backend systems
US9596251B2 (en) 2014-04-07 2017-03-14 Intuit Inc. Method and system for providing security aware applications
US10055247B2 (en) 2014-04-18 2018-08-21 Intuit Inc. Method and system for enabling self-monitoring virtual assets to correlate external events with characteristic patterns associated with the virtual assets
US9900322B2 (en) 2014-04-30 2018-02-20 Intuit Inc. Method and system for providing permissions management
US10216531B2 (en) 2014-05-12 2019-02-26 Netapp, Inc. Techniques for virtual machine shifting
US20150324216A1 (en) * 2014-05-12 2015-11-12 Netapp, Inc. Self-repairing configuration service for virtual machine migration
US9742794B2 (en) 2014-05-27 2017-08-22 Intuit Inc. Method and apparatus for automating threat model generation and pattern identification
US10050997B2 (en) 2014-06-30 2018-08-14 Intuit Inc. Method and system for secure delivery of information to computing environments
US20160065690A1 (en) * 2014-08-27 2016-03-03 Kabushiki Kaisha Toshiba System and method for selecting virtual desktop environment
US10007714B2 (en) * 2015-03-05 2018-06-26 Microsoft Technology Licensing, Llc Ongoing management for pre-planned handling of digital presence
US10382528B2 (en) 2015-05-27 2019-08-13 Microsoft Technology Licensing, Llc Disposition actions in digital asset management based on trigger events
US10122832B2 (en) * 2015-12-07 2018-11-06 International Business Machines Corporation Communications of usernames and passwords to a plurality of cloud storages via a plurality of communications protocols that change over time
US10171585B2 (en) 2015-12-07 2019-01-01 International Business Machines Corporation Method, system, and computer program product for distributed storage of data in a heterogeneous cloud
US10013181B2 (en) 2015-12-07 2018-07-03 International Business Machines Corporation Distributed storage of data in a local storage and a heterogeneous cloud

Also Published As

Publication number Publication date
WO2015161162A1 (en) 2015-10-22
US10360062B2 (en) 2019-07-23
EP3132349A4 (en) 2018-02-28
US20170068563A1 (en) 2017-03-09
US20180191753A1 (en) 2018-07-05
US20180341512A1 (en) 2018-11-29
EP3132349A1 (en) 2017-02-22
US20170237756A1 (en) 2017-08-17
US9923909B2 (en) 2018-03-20
AU2015247499A1 (en) 2016-10-06
CA2943301A1 (en) 2015-10-22
US10055247B2 (en) 2018-08-21

Similar Documents

Publication Publication Date Title
US9594881B2 (en) System and method for passive threat detection using virtual memory inspection
US8595822B2 (en) System and method for cloud based scanning for computer vulnerabilities in a network environment
US9128941B2 (en) On-demand content classification using an out-of-band communications channel for facilitating file activity monitoring and control
US20160359872A1 (en) System for monitoring and managing datacenters
US20160212012A1 (en) System and method of network functions virtualization of network services within and across clouds
US20160359877A1 (en) Intra-datacenter attack detection
US20120030731A1 (en) System and Method for Local Protection Against Malicious Software
US20070192867A1 (en) Security appliances
US20160057166A1 (en) Cyber-security system and methods thereof for detecting and mitigating advanced persistent threats
Shin et al. Fresco: Modular composable security services for software-defined networks
US10063587B2 (en) Management of security actions based on computing asset classification
US9495188B1 (en) Synchronizing a honey network configuration to reflect a target network environment
JP2016537695A (en) Optimized resource allocation to virtual machines in the malware content detection system
WO2004023714A2 (en) Computer network security system utilizing dynamic mobile sensor agents
US20070266433A1 (en) System and Method for Securing Information in a Virtual Computing Environment
JP6196397B2 (en) Cyber ​​security system
CN104246785A (en) System and method for crowdsourcing of mobile application reputations
US7703138B2 (en) Use of application signature to identify trusted traffic
KR20150006042A (en) Systems and methods for providing mobile security based on dynamic attestation
US9294442B1 (en) System and method for threat-driven security policy controls
US8973088B1 (en) Policy enforcement using host information profile
US20150106939A1 (en) Method and system for dynamic and comprehensive vulnerability management
US20160261631A1 (en) Emulating shellcode attacks
US9609019B2 (en) System and method for directing malicous activity to a monitoring system
GB2503540A (en) Applying policy wrappers to computer applications for secure communication

Legal Events

Date Code Title Description
AS Assignment

Owner name: INTUIT INC., CALIFORNIA

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:CABRERA, LUIS FELIPE;LIETZ, M. SHANNON;SIGNING DATES FROM 20140411 TO 20140416;REEL/FRAME:032708/0252

STCB Information on status: application discontinuation

Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION