Patent Grant
9473481
Traditional techniques for securing applications and/or computing systems from attack by potential security threats are becoming less effective as computing environments change. For example, traditional computing environment perimeters, e.g., firewalls, were placed at choke points within private networks to protect the applications and computing systems within the private network. A traditional computing environment perimeter may have been useful in protecting applications from external potential security threats when the applications were hosted within the private network or intranet. However, because current computing practices include hosting applications in cloud computing environments (e.g., that are external to the private network) for access by computing systems within the private network, the traditional computing environment perimeter of the private network has become a less effective tool for protecting hosted applications. Traditional computing environment perimeters are also less effective at protecting against back door attacks, and encouraged users to enter and leave through network back doors.
What is needed is a method and system for providing a virtual asset perimeter that provides protection through an elastic perimeter and that includes and incorporates trusted or vetted assets.
In accordance with one embodiment, a system and method for providing a virtual perimeter includes maintaining, with a first instance of a virtual perimeter agent, a data structure for identifying the first plurality of assets, according to one embodiment. The first instance of the virtual perimeter agent resides on a first of the first plurality of assets, and the data structure includes identifiers for the first plurality of assets, according to one embodiment. The first plurality of assets include computing systems configured to communicate over one or more networks, and the first plurality of assets is included within the virtual perimeter and a second plurality of assets is excluded from the virtual perimeter, according to one embodiment. The system and method include providing services, from a first of the first plurality of assets, to a second of the first plurality of assets, at least partially based on the identifiers for the first plurality of assets and at least partially based on a first role assigned to the first of the first plurality of assets, according to one embodiment. The first role is enforced on the first of the first plurality of assets by the first instance of the virtual perimeter agent, according to one embodiment. The system and method include admitting one of the second plurality of assets into the virtual perimeter if characteristics of the one of the second plurality of assets satisfy criteria for admission to the virtual perimeter, according to on embodiment. Admitting the one of the second plurality of assets can include installing a second instance of the virtual perimeter agent on the one of the second plurality of assets; adding an identifier of the one of the second plurality of assets to the data structure; and assigning a second role to the one of the second plurality of assets to determine second access privileges of the one of the second plurality of assets within the virtual perimeter, according to one embodiment.
In accordance with one embodiment, a system and method for maintaining a secure virtual perimeter of communicatively coupled assets includes receiving, with a first asset, a request asset for access to the virtual perimeter, from a second asset, according to one embodiment. The first asset is one of a first plurality of assets and the second asset is one of a second plurality of assets, and the first plurality of assets are included in the virtual perimeter and the second plurality of assets are excluded from the virtual perimeter, according to one embodiment. Each of the first plurality of assets and each of the second plurality of assets include one or more of a server, a computing system, a virtual machine, and a mobile device, according to one embodiment. The system and method include transmitting, with the first asset, a request for configuration information of the second asset, from the second asset. The system and method include receiving the configuration information of the second asset from the second asset. The system and method include determining whether the configuration information of the second asset satisfies conditions for admission to the virtual perimeter. The system and method include assigning a role to the second asset if the configuration information of the second asset satisfies the conditions for admission to the virtual perimeter. The system and method include providing virtual perimeter admission information to the second asset to enable the second asset to share services and resources with the first plurality of assets within the virtual perimeter.
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.
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.
The INTRODUCTORY SYSTEM, HARDWARE ARCHITECTURE, and PROCESS sections herein include systems and processes suitable for providing a virtual asset perimeter, according to various embodiments.
Herein, the term “production environment” includes the various components, or assets, used to deploy, implement, access, and use, a given application as that application is intended to be used. In various embodiments, production environments include multiple assets that are combined, communicatively coupled, virtually and/or physically connected, and/or associated with one another, to provide the production environment implementing the application.
As specific illustrative examples, the assets making up a given production environment can include, but are not limited to, one or more computing environments used to implement the application in the production environment such as a data center, a cloud computing environment, a dedicated hosting environment, and/or one or more other computing environments in which one or more assets used by the application in the production environment are implemented; one or more computing systems or computing entities used to implement the application in the production environment; one or more virtual assets used to implement the application in the production environment; one or more supervisory or control systems, such as hypervisors, or other monitoring and management systems, used to monitor and control assets and/or components of the production environment; one or more communications channels for sending and receiving data used to implement the application in the production environment; one or more access control systems for limiting access to various components of the production environment, such as firewalls and gateways; one or more traffic and/or routing systems used to direct, control, and/or buffer, data traffic to components of the production environment, such as routers and switches; one or more communications endpoint proxy systems used to buffer, process, and/or direct data traffic, such as load balancers or buffers; one or more secure communication protocols and/or endpoints used to encrypt/decrypt data, such as Secure Sockets Layer (SSL) protocols, used to implement the application in the production environment; one or more databases used to store data in the production environment; one or more internal or external services used to implement the application in the production environment; one or more backend systems, such as backend servers or other hardware used to process data and implement the application in the production environment; one or more software systems used to implement the application in the production environment; and/or any other assets/components making up an actual production environment in which an application is deployed, implemented, accessed, and run, e.g., operated, as discussed herein, and/or as known in the art at the time of filing, and/or as developed after the time of filing.
As used herein, the terms “computing system”, “computing device”, and “computing entity”, include, but are not limited to, a virtual asset; a server computing system; a workstation; a desktop computing system; a mobile computing system, including, but not limited to, smart phones, portable devices, and/or devices worn or carried by a user; a database system or storage cluster; a switching system; a router; any hardware system; any communications system; any form of proxy system; a gateway system; a firewall system; a load balancing system; or any device, subsystem, or mechanism that includes components that can execute all, or part, of any one of the processes and/or operations as described herein.
In addition, as used herein, the terms computing system and computing entity, can denote, but are not limited to, systems made up of multiple: virtual assets; server computing systems; workstations; desktop computing systems; mobile computing systems; database systems or storage clusters; switching systems; routers; hardware systems; communications systems; proxy systems; gateway systems; firewall systems; load balancing systems; or any devices that can be used to perform the processes and/or operations as described herein.
As used herein, the term “computing environment” includes, but is not limited to, a logical or physical grouping of connected or networked computing systems and/or virtual assets using the same infrastructure and systems such as, but not limited to, hardware systems, software systems, and networking/communications systems. Typically, computing environments are either known environments, e.g., “trusted” environments, or unknown, e.g., “untrusted” environments. Typically, trusted computing environments are those where the assets, infrastructure, communication and networking systems, and security systems associated with the computing systems and/or virtual assets making up the trusted computing environment, are either under the control of, or known to, a party. Examples of trusted computing environments include the assets and components making up data centers associated with, and/or controlled by, an application and/or any computing systems and/or virtual assets, and/or networks of computing systems and/or virtual assets, associated with, known by, and/or controlled by, an application.
In contrast, unknown, or untrusted computing environments are environments and systems where the assets, components, infrastructure, communication and networking systems, and security systems implemented and associated with the computing systems and/or virtual assets making up the untrusted computing environment, are not under the control of, and/or are not known by, a party, and/or are dynamically configured with new elements capable of being added that are unknown to the party. Examples of untrusted computing environments include, but are not limited to, public networks, such as the Internet, various cloud-based computing environments, and various other forms of distributed computing systems.
In various embodiments, each computing environment includes allocated assets and virtual assets associated with, and controlled or used to create, and/or deploy, and/or operate an application.
It is often the case that to create, and/or deploy, and/or operate, application data must be transferred between a first computing environment that is an untrusted computing environment and a trusted computing environment. However, in other situations a party may wish to transfer data between two trusted computing environments, and/or two untrusted computing environments.
In various embodiments, one or more cloud computing environments are used to create, and/or deploy, and/or operate an application that can be any form of cloud computing environment, such as, but not limited to, a public cloud; a private cloud; a virtual private network (VPN); a subnet; a Virtual Private Cloud (VPC); a sub-net or any security/communications grouping; or any other cloud-based infrastructure, sub-structure, or architecture, as discussed herein, and/or as known in the art at the time of filing, and/or as developed after the time of filing.
In many cases, a given application or service may utilize, and interface with, multiple cloud computing environments, such as multiple VPCs, in the course of being created, and/or deployed, and/or operated.
As used herein, the term “virtual asset” includes any virtualized entity or resource, and/or virtualized part of an actual, or “bare metal” entity. In various embodiments, the virtual assets can be, but are not limited to, virtual machines, virtual servers, and instances implemented in a cloud computing environment; databases associated with a cloud computing environment, and/or implemented in a cloud computing environment; services associated with, and/or delivered through, a cloud computing environment; communications systems used with, part of, or provided through, a cloud computing environment; and/or any other virtualized assets and/or sub-systems of “bare metal” physical devices such as mobile devices, remote sensors, laptops, desktops, point-of-sale devices, ATMs, electronic voting machines, etc., located within a data center, within a cloud computing environment, and/or any other physical or logical location, as discussed herein, and/or as known/available in the art at the time of filing, and/or as developed/made available after the time of filing.
In various embodiments, any, or all, of the assets making up a given production environment discussed herein, and/or as known in the art at the time of filing, and/or as developed after the time of filing, can be implemented as virtual assets.
Typically, virtual assets are created, or instantiated, using steps, instructions, processes, code, or “recipes” referred to herein as “virtual asset creation templates.” Typically, virtual assets that have the same, or similar, operational parameters are created using the same or similar “virtual asset creation templates.”
Examples of virtual asset creation templates include, but are not limited to, any tool and/or system for creating and managing a collection of related cloud resources. Illustrative examples of such a virtual asset creation template are any of the cloud formation templates/tools provided by Amazon Web Service (AWS), Rack Space, Joyent, and/or any other of the numerous cloud based infrastructure providers.
Other examples of virtual asset creation templates include, but are not limited to, any configuration management tool associated with, and/or used to create, virtual assets. One specific illustrative example of such a virtual asset creation template is a cookbook or recipe tool such as a Chef Recipe or system or any other fundamental element, or set of elements, used to override the default settings on a node within an infrastructure or architecture.
Other examples of virtual asset creation templates include, but are not limited to, any virtual appliance used to instantiate virtual assets. One specific illustrative example of such a virtual asset creation template is an Amazon Machine Image (AMI), and/or similar functionality provided by Amazon Web Service (AWS), Rack Space, Joyent, and/or any other of the numerous cloud based infrastructure providers.
Other examples of virtual asset creation templates include, but are not limited to, any appliance, or tool, or system, or framework, used to instantiate virtual assets as discussed herein, and/or as known/available in the art at the time of filing, and/or as developed/made available after the time of filing.
Herein virtual assets that have the same, or similar, operational parameters and are created by the same or similar virtual asset creation template are generically referred to as virtual assets of the same “class.” Examples of virtual asset classes include, but are not limited to, virtual machine classes; virtual server classes; virtual database or data store classes; self-monitoring virtual assets including specific types of instances instantiated in a cloud environment; application development process classes; and application classes.
In one embodiment, two or more assets, such as computing systems and/or virtual assets, and/or two or more computing environments, are connected by one or more communications channels including but not limited to, Secure Sockets Layer communications channels and various other secure communications channels, and/or distributed computing system networks, such as, but not limited to: a public cloud; a private cloud; a virtual private network (VPN); a subnet; any general network, communications network, or general network/communications network system; a combination of different network types; a public network; a private network; a satellite network; a cable network; or any other network capable of allowing communication between two or more assets, computing systems, and/or virtual assets, as discussed herein, and/or available or known at the time of filing, and/or as developed after the time of filing.
As used herein, the term “network” includes, but is not limited to, any network or network system such as, but not limited to, a peer-to-peer network, a hybrid peer-to-peer network, a Local Area Network (LAN), a Wide Area Network (WAN), a public network, such as the Internet, a private network, a cellular network, any general network, communications network, or general network/communications network system; a wireless network; a wired network; a wireless and wired combination network; a satellite network; a cable network; any combination of different network types; or any other system capable of allowing communication between two or more assets, virtual assets, and/or computing systems, whether available or known at the time of filing or as later developed.
As used herein, the term “user” includes, but is not limited to, any party, parties, entity, and/or entities using, or otherwise interacting with any of the methods or systems discussed herein. For instance, in various embodiments, a user can be, but is not limited to, a person, a commercial entity, an application, a service, and/or a computing system.
As used herein, the term “tenant” includes, but is not limited to, any user that enters a relationship, agreement, and/or contract, with an asset service provider or other service provider to receive an allocation of one or more assets or asset resources within an asset computing environment. In some embodiments, the terms “tenant” and “tenant computing environment” are interchangeably used even though, in some cases, a tenant represents a party, parties, or entities while the tenant computing environment represents one or more computing resources that are used by or that are at least partially under the control of the tenant.
The production environment 100 utilizes the resources of multiple virtual and/or physical assets to realize a virtual asset perimeter, according to one embodiment. The production environment 100 includes assets 110, communicatively coupled together by a network 120, according to one embodiment. At least some of the assets 110 are operatively coupled and/or organized by a virtual asset perimeter 130, to provide a secure network of shared services and/or resources to the assets 110 that are within the virtual asset perimeter 130, according to one embodiment.
The assets 110 include assets 110A, 110B, 110C, 110D, 110E, 110F, 110G, and 110H, according to one embodiment. The assets 110 can include more or less assets than the eight assets illustrated in the production environment 100, according to various embodiments. In one embodiment, the assets 110 include all assets that are, that can be, and/or that will be communicatively coupled to the Internet. Each of the assets 110 includes physical characteristics 111 (inclusive of physical characteristics 111A-111H), operational characteristics 112 (inclusive of operational characteristics 112A-112H), and metadata 113 (inclusive of metadata 113A-113H), according to one embodiment. The physical characteristics 111 include, but are not limited to, memory capacity, number of processors, speed of processors, peripheral accessories (e.g., keyboard, touch screens, network cards), and platform type (e.g., server, laptop, desktop, mobile device, virtual machine). The operational characteristics 112 include, but are not limited to, available services, software capabilities, communications protocols, security features, access/permissions rights to the asset, directory services, operating systems, and user accounts for accessing the asset or for accessing other assets. The metadata 113 can include one or more of the physical characteristics 111 and/or one or more of the operational characteristics 112, according to one embodiment. Additionally, the metadata 113 includes information associated with identifying the assets 110, for example, device identifiers (“IDs”), media access control (“MAC”) addresses, burned-in addresses (“BIA”), internet protocol (“IP”) addresses, subnet addresses, uniform resource locators (“URLs”), domain names, and other hardware, physical, or network addresses, according to various embodiments.
Each of the assets 110 can have physical characteristics 111 and/or operational characteristics 112 that are different from others of the assets 110, according to one embodiment. For example, the asset 110A may be a server in a data center that hosts security software for identifying and resolving potential security threats within a network. As another example, the asset 110B may be an allocation of hardware, software, and firmware resources, e.g., a virtual asset or virtual machine, for use by a tenant or customer to store information or host one or more services for other users. As yet another example, the asset 110C may be a mobile device such as a smart phone from which a user accesses one or more user accounts to receive services from other assets 110. According to various embodiments, each of the assets 110 is configured as one or more of a server, a gateway, a virtual private cloud, a subnet, a virtual asset, a laptop, a desktop, a mobile device, and other computing environment. According to various embodiments, each of the assets 110 of the production environment 100 can be generically referred to as a “first asset”, a “second asset”, a “third asset”, and so forth.
The assets 110 are communicatively coupled together through the network 120, according to one embodiment. The network 120 can include one or more communication channels 121, 122, 123, 124, 125, 126, 127, and 128 to enable the assets to communicate information to one another, according to one embodiment. The network 120 can include, but is not limited to, a LAN, a PAN, a WAN, an intranet, a virtual private cloud, and the Internet, according to various embodiments.
The virtual asset perimeter 130 includes the assets 110A, 110B, and 110E, and represents a mechanism for determining how to make relationships and for maintaining and/or changing relationships that have been created between the assets 110, according to one embodiment. The virtual asset perimeter 130 includes the ability to evolve by, for example, automatically admitting assets to the virtual asset perimeter 130 and by automatically removing assets from the virtual asset perimeter 130, in accordance with one or more rules or policies. In one embodiment, the admission and expulsion of assets to/from the virtual asset perimeter 130 is performed automatically and is at least partially based on physical characteristics, operational characteristics, metadata, and/or communications associated with a particular asset. The virtual asset perimeter 130 overcomes deficiencies of traditional parameters, e.g., firewalls, by combining security controls together with a construct to create a virtual network.
According to one embodiment, each of the assets 110 that are admitted into the virtual asset perimeter 130 receive a virtual perimeter module 131 (inclusive of virtual perimeter modules 131A, 131B, 131E) and roles 132 (inclusive of roles 132A, 132B, 132E) to define, expand, maintain, and collapse the virtual asset perimeter 130. The virtual perimeter module 131 tracks which of the assets 110 have been admitted to the virtual asset perimeter 130 by maintaining a list or data structure of identifiers, e.g., IP addresses, or the assets 110 that have been admitted to the virtual asset perimeter, in one embodiment. The virtual perimeter module 131 enables the assets 110 to admit additional assets, e.g., trusted assets, to the virtual asset perimeter 130, in one embodiment. The virtual perimeter module 131 provides security to assets 110A, 110B, 110E, by maintaining and enforcing policies for security, communications, and admission to the virtual perimeter 130, in one embodiment. The virtual perimeter module 131 also enables the sharing of services and/or resources between the assets 110, e.g., the assets 110A, 110B, 110E, of the virtual asset perimeter 130, in one embodiment.
The virtual perimeter module 131 is installed in an asset if the asset satisfies one or more predetermined conditions, according to one embodiment. An asset that requests admission to the virtual asset perimeter 130 is an admission requesting asset, and an asset that can grant admission to the virtual perimeter is an admission granting asset, in one embodiment. An admission granting asset can receive a request for admission, along with configuration information or communications history, from an admission requesting asset, and can determine whether the admissions requesting asset is a hacker or is compromised by one or more potential security threats, e.g., viruses. In one embodiment, the predetermined condition includes having a clean bill-of-health. In other words, an admission requesting asset can be required to provide communications traffic history to enable the admission granting asset to search for digital signatures that are associated with potential security threats. The admission granting asset can be configured to determine the geographic origins of the communications traffic history and the predetermined conditions can be based on the geographic origins of the communications traffic. For example, if the communications traffic history includes multiple communications having geographical origins in particular portions of, for example, the Middle-East, central Europe, or South-east Asia, the admissions granting asset can automatically deny the admissions request to the virtual asset perimeter 130, in one embodiment. To provide further security, the policies and rules for admission may be encrypted so that the reasons for the denial are not available for extraction from the admissions granting asset and are not provided to the admissions requesting asset. By keeping at least part of the admissions rules and policies a secret, the virtual perimeter module 131 can prevent or undermine attempts to falsify communications traffic data or history, according to one embodiment. Other predetermined conditions can be based on configurations of the admission requesting asset, such as whether the asset is protected by anti-virus or anti-malware software, whether the asset provides services to geographically suspicious locations, whether the asset employs encrypted communications, whether the asset is already admitted to other virtual asset perimeters, or whether the asset is configured for providing services that are desired by the virtual asset perimeter 130, e.g., computing security services, according to various embodiments.
The roles 132 received by each of the assets 110 that are admitted to the virtual asset perimeter 130 determine the access privileges of the recipient, according to one embodiment. The roles 132 can be assigned for an indefinite duration, e.g., permanent, or the roles 132 can be assigned temporarily, e.g., for 3 months or for the duration of a project. The roles 132 include, but are not limited to, architect, security, developer, operator, user, contributor, content generator, and editor. Each of the roles can include different levels of privileges within the virtual asset perimeter 130. For example, an asset with a security role can be granted access to scan each of the other assets 110 for potential security threats and/or for compliance to the rules or policies of the virtual asset perimeter 130. Because any of the assets 110 can belong to multiple virtual asset perimeters, the roles 132 can include a first set of roles for a first virtual asset perimeter and a second different set of roles for a second different virtual asset perimeter, according to one embodiment. For example, the roles 132A of the asset 110A can be limited to content generator privileges for the virtual asset perimeter 130 and can include security or architect privileges for another virtual asset perimeter to which the asset 110A is admitted. The virtual perimeter module 131 is configured to enable and/or prevent asset operations based at least in part on the roles 132 that have been assigned to the asset. For example, the virtual perimeter module 131 can be configured to enable an asset with architect privileges or security privileges to admit additional assets into the virtual asset perimeter. In one embodiment, roles 132 can be limited to a single role, e.g., content generator, or can include multiple roles, e.g., architect, security, user, and editor.
In one embodiment, the assets 110 of the virtual asset perimeter 130 are organized into a cluster 133. The cluster 133 includes the asset 110A and the asset 110B, in one embodiment. The cluster 133 represents a grouping of the assets 110A and 110B based on function or physical characteristics of the assets 110A and 110B. The assets 110A and 110B can share functional characteristics such as services provided, resources provided, roles, and/or other physical or operational characteristics, according to various embodiments. For example, the assets 110A and 110B can both be servers, mobile devices, security service providers, virtual machines, or the like, according to various embodiments.
In one embodiment, the production environment 100 includes a second virtual asset perimeter 140. The second virtual asset perimeter 140 includes the assets 110E, the asset 110F, and the asset 110G, in one embodiment. The security features, communications protocols, number of assets, and admission standards of the second virtual asset perimeter 140 are different than those of the virtual asset perimeter 130, according to one embodiment. Each of the assets 110 can be incorporated or admitted to one or more virtual asset perimeters, e.g., virtual asset perimeters 130, 140, to selectively share services and/or resources, according to one embodiment.
The communications module 201 enables one asset 110 of the virtual asset perimeter 130 to communicate with another asset 110 of the virtual asset perimeter, according to one embodiment. The communications module 201 can be configured to use one or more standard or proprietary communications techniques to transfer information between the assets 110. The communications module 201 can block traffic or requests from unauthorized assets, e.g., assets 110 that are not within the virtual asset perimeter 130. The communications module 201 is configured to use the perimeter assets database 202 to determine whether an asset 110 has been admitted to the virtual asset perimeter 130, and filters traffic to the asset 110, at least partially based on the contents of the perimeter assets database 202, according to one embodiment.
The perimeter assets database 202 includes characteristics, metadata, and identification for each of the assets 110 that are included in the virtual asset perimeter 130, according to one embodiment. The perimeter assets database 202 can be implemented as a table, a database, or other data structure. The perimeter assets database 202 includes information such as device IDs, IP addresses, MAC addresses, available resources, roles, offered services, and the like for one or more of the assets 110 that are included in the virtual asset perimeter 130, according to one embodiment. The virtual perimeter module 131 updates the perimeter assets database 202 when a new asset, e.g., asset 110H, is added to the virtual perimeter 130, or when an asset is removed from the virtual asset perimeter 130, according to one embodiment.
The services policy 203 includes rules and policies for providing services to the assets 110 that are internal and external to the virtual asset perimeter 130, according one embodiment. For example, if the asset 110B is a virtual asset that hosts a financial services application, the services policy 203 may include rules that permit the asset 110B to provide access to the financial services application to the assets 110 that are identified in the perimeter assets database 202, e.g., the assets 110 that are internal to the virtual asset perimeter 130, according to one embodiment. The services policy 203 may also include rules that prohibit the asset 110B from providing access to its financial services application to one or more of the assets 110 that are not identified in the perimeter assets database 202, e.g., the assets 110 that are external to the virtual asset perimeter 130, according to one embodiment. The services engine 204 executes the services policy 203 to enforce and apply the various rules defined within the services policy 203, according to one embodiment.
The user accounts database 205 includes information about the user accounts associated with the asset 110 onto which the virtual perimeter module 131 is installed, according to one embodiment. For example, the user accounts database 205 can include usernames, passwords, payment information, usage history, encryption algorithms, communication protocols, or similar information for each user account that receives services from, or that otherwise uses the resources of, an asset 110, according to one embodiment. Some of the user accounts may be linked to an asset 110 that uses poor security practices, e.g., unencrypted communications, and is outside of the virtual asset perimeter 130. Others of the user accounts may be linked to an asset 110 that applies stringent security practices. The virtual perimeter module 131 uses the characteristics of the user accounts and/or the characteristics of the service providers of the user accounts to determine a level of trust of each of the accounts. For example, if one account is associated with a social media service that reportedly installs malware on user computing systems, then that particular account will be assigned a low level of trust, according to one embodiment. In some embodiments, the user accounts of the user accounts database 205 are associated with links between an asset 110 and a user computing system. In other embodiments, the user accounts of the user accounts database 205 are associated with links between one asset 110 and another asset 110. In either case, the virtual perimeter module 131 can use the user accounts database 205 to assign levels of trust to user accounts to provide a secure computing environment, e.g., virtual network, for users to receive services with the user accounts. In one embodiment, if the user accounts database 205 includes a relatively low level of trust assigned to a particular user account, the services engine 204 blocks use of the particular user account to maintain the security of the virtual asset perimeter 130.
In one embodiment, the virtual perimeter module 131 optionally includes the admissions policy 206, the expulsion policy 207, and the admissions engine 208 for use by the assets 110 that have the authorization and/or the privileges for admitting/removing other assets to/from the virtual asset perimeter 130, according to one embodiment. In one embodiment, use of the admissions policy 206, the expulsion policy 207, and the admissions engine 208 is authorized based at least partially on the roles 132 associated with the asset 110. For example, the use of the admissions policy 206, the expulsion policy 207, and the admissions engine 208 can be limited to the assets 110 that have architect privileges and security privileges.
The admissions policy 206 includes rules, e.g., admissibility rules, and policies that determine when an asset 110 is admissible to the virtual asset perimeter 130, according to one embodiment. The admissibility rules include, but are not limited to, thresholds or requirements for authentication algorithms, length of encryption keys, life of the asset, memory capacity, processor speeds, operating system versions, user accounts to which the asset provides services, types of services provided, database capacity, communications protocols, communications traffic, and evidence of exposure to potential security threats, according to various embodiments. For example, the admissions policy 206 can include a rule that communications traffic to/from a potential admittee be clean of digital signatures and/or patterns that are associated with known security threats or potential security threats. As another example, the admissions policy 206 can include a rule that the configuration information of the assets indicates that an operating system of the asset is a version that post-dates a particular date or year, e.g., 2010. As another example, the admissions policy 206 can include a rule that a potential admittee employ encrypted communications of at least 256-bit encryption.
According to various other embodiments, the admissions policy 206 includes rules for potential admittees that are at least partially based on the characteristics or configuration information of the asset. For example, if a potential admittee is a smart phone, the admissions policy 206 may employ looser standards than if the potential admittee is a server. The admissions policy 206 includes rules that enable the assets 110 to automatically determine whether or not a potential admittee, e.g., another asset 110, can be admitted to the virtual asset perimeter 130 without compromising the security of the virtual asset perimeter 130, according to one embodiment.
The expulsion policy 207 includes rules and policies that determine when an asset 110 is to be removed or expelled from the virtual asset perimeter 130, according to one embodiment. The expulsion policy 207 includes rules that maintain the security and protection of the assets 110 that are within the virtual asset perimeter 130. The expulsion policy 207 more specifically includes rules that identify assets 110 that have been compromised by potential security threats or that have failed to maintain standards or requirements for admission to the virtual asset perimeter 130, in one embodiment. For example, the expulsion policy 207 can include a rule that an asset 110 be removed from the virtual asset perimeter 130 if a security scan of the asset 110 identifies one or more Trojan programs, viruses, or other malicious software. As another example, the expulsion policy 207 can include a rule that an asset 110 be removed from the virtual asset perimeter 130 if the configuration information of the asset 110 indicates a failure to update the asset 110 to a particular version of an operating system, indicates a failure to install a particular security patch, or indicates a failure to otherwise comply with one or more predetermined security standards or operations. The expulsion policy 207 can also include rules for providing notification to the assets 110 that are going to be expelled from the virtual asset perimeter 130, to provide the assets 110 with an opportunity to remedy any deficiencies, according to one embodiment
The admissions engine 208 executes the admissions policy 206 and the expulsion policy 207 to enforce and apply the various rules defined within the admissions policy 206 and the expulsion policy 207, according to one embodiment. The admissions engine 208 can be configured to install an instance of the virtual perimeter module 131 onto a new admittee to the virtual asset perimeter 130, in one embodiment. The admissions engine 208 can be configured to assign one or more roles 132 to the new admittee, at least partially based on the configuration information of the new admittee. For example, the admissions engine 208 may assign security privileges to a new admittee, e.g., asset 110H, if the asset is associated with a computer security provider and is configured to provide security services to virtual networks. The admissions engine 208 updates the perimeter assets database 202 to reflect the admission of new assets and to reflect the removal of previous assets from the virtual asset perimeter 130, according to one embodiment. The admissions engine 208 transmits updates to instances of the perimeter assets database 202 throughout the virtual asset perimeter 130, so that each of the assets 110 within the virtual asset perimeter 130 has an up-to-date list of the assets 110 that are authorized to share services and resources within the virtual asset perimeter 130, according to one embodiment.
In one embodiment, the virtual perimeter module 131 optionally includes the security threat engine 209 and the security threat database 210 for use by the assets 110 that have the authorization and/or the privileges for performing security operations within the virtual asset perimeter 130, according to one embodiment. In one embodiment, the security threat engine 209 and the security threat database 210 are installed or enabled in the assets 110 that have the roles 132 of architect or security. The security threat engine 209 identifies potential security threats within the virtual asset perimeter 130 based at least partially on the contents of the security threat database 210, according to one embodiment. The security threat engine 209 periodically or pseudo-randomly performs security scans of the assets 110 within the virtual asset perimeter 130, to ensure that potential security threats do not compromise the integrity of the virtual asset perimeter 130, in one embodiment. The security threat engine 209 is configured to update the security threat database 210 based on prior security attacks and/or based on information received from one or more computer security repositories/databases, according to one embodiment. Once the security threat engine 209 identifies a potential security threat within the virtual asset perimeter 130, the security threat engine 209 is configured to transmit a security patch or other remedial code to the affected asset 110, in one embodiment. In another embodiment, once the security threat engine 209 identifies a potential security threat within the virtual asset perimeter 130, the security threat engine 209 is configured to notify the admissions engine 208 of the security breach so that the admissions engine 208 can expel the affected asset 110 from the virtual asset perimeter.
The operation of the virtual perimeter module 131 is described herein in terms of various modules, engines, policies, and databases, in accordance with various embodiments. However, in other embodiments, the functionality of the modules, engines, policies, and databases described herein can be implemented in the virtual perimeter module 131 or into a virtual perimeter agent using other hierarchies, organizational models, and/or techniques.
At block 304, the first asset 301 transmits a request for access to the virtual asset perimeter, according to one embodiment.
At block 306, the second asset 302 receives the request for access to the virtual asset perimeter, according to one embodiment.
At block 308, the second asset 302 transmits a request for configuration information, according to one embodiment. The requested configuration information can include, but not be limited to, communication protocols, physical characteristics, operational characteristics, communication traffic history, or the like.
At block 310, the first asset 301 receives the request for configuration information, according to one embodiment.
At block 312, the first asset 301 retrieves configuration information, according to one embodiment.
At block 314, the first asset 301 transmits the retrieved configuration information to the second asset 302, according to one embodiment.
At block 316 the second asset 302 receives the retrieved configuration information from the first asset 301, according to one embodiment.
At block 318, the second asset 302 determines whether the configuration information satisfies conditions for admission to the virtual asset perimeter, according to one embodiment.
At block 320 the second asset 302 assigns one or more roles to the admission requesting asset, if the configuration information satisfies the conditions, according to one embodiment.
At block 322, the second asset 302 provides virtual asset perimeter information to the admission requesting asset for the assigned one or more roles, according to one embodiment. The virtual asset perimeter information can include a virtual perimeter module to enable the admission requesting asset to interact with one or more other assets that have been admitted to the virtual asset perimeter, according to one embodiment.
At block 324, the first asset 301 receives the virtual asset perimeter information associated with the one or more roles, according to one embodiment.
At block 326, the first asset 301 distributes information, data, or services to the assets within the virtual asset perimeter, in accordance with the assigned one or more roles, according to one embodiment.
At block 404, the first asset 401 periodically monitors communications of assets within the virtual asset perimeter, according to one embodiment.
At block 406 the first asset 401 detects a potential security threat within one of the assets, according to one embodiment.
At block 408 the first asset 401 requests configuration information from the one of the assets in which the potential security threat is detected, according to one embodiment.
At block 410, the second asset 402 receives the request for configuration information, from the first asset 401, according to one embodiment.
At block 412, the second asset 402 retrieves configuration information, according to one embodiment.
At block 414, the second asset 402 transmits the retrieved configuration information, to the first asset 401, according to one embodiment.
At block 416, the first asset 401 determines whether the configuration information satisfies conditions for disassociation from the virtual asset perimeter, according to one embodiment.
At block 418, the first asset 401 notifies the one of the assets of disassociation from the virtual asset perimeter, according to one embodiment.
At block 420, the virtual asset 401 updates records to reflect removal of the one of the assets from the virtual asset perimeter, according to one embodiment. Updating the records can include updating one or more tables, data structures, and/or databases, according to one embodiment.
At block 422, the second asset 402 receives the notification of disassociation from the virtual asset perimeter, according to one embodiment.
At block 502, the process begins.
At block 504, the process maintains, with a first instance of a virtual perimeter agent, a data structure for identifying the first plurality of assets, according to one embodiment. The first instance of the virtual perimeter agent resides on a first of the first plurality of assets, and the data structure includes identifiers for the first plurality of assets, according to one embodiment. The first plurality of assets include computing systems configured to communicate over one or more networks, and the first plurality of assets is included within the virtual perimeter and a second plurality of assets is excluded from the virtual perimeter, according to one embodiment.
At block 506, the process provides services, from a first of the first plurality of assets, to a second of the first plurality of assets, at least partially based on the identifiers for the first plurality of assets and at least partially based on a first role assigned to the first of the first plurality of assets, according to one embodiment. The first role is enforced on the first of the first plurality of assets by the first instance of the virtual perimeter agent, according to one embodiment.
At block 508, the process admits one of the second plurality of assets into the virtual perimeter if characteristics of the one of the second plurality of assets satisfy criteria for admission to the virtual perimeter, according to on embodiment. Admitting the one of the second plurality of assets can include installing a second instance of the virtual perimeter agent on the one of the second plurality of assets; adding an identifier of the one of the second plurality of assets to the data structure; and assigning a second role to the one of the second plurality of assets to determine second access privileges of the one of the second plurality of assets within the virtual perimeter, according to one embodiment.
At block 510, the process ends.
As noted above, the specific illustrative examples discussed above are but illustrative examples of implementations of embodiments of the method or process for providing a virtual asset perimeter. Those of skill in the art will readily recognize that other implementations and embodiments are possible. Therefore the discussion above should not be construed as a limitation on the claims provided below.
In the discussion above, certain aspects of one embodiment include process steps and/or operations and/or instructions described herein for illustrative purposes in a particular order and/or grouping. However, the particular order and/or grouping shown and discussed herein are illustrative only and not limiting. Those of skill in the art will recognize that other orders and/or grouping of the process steps and/or operations and/or instructions are possible and, in some embodiments, one or more of the process steps and/or operations and/or instructions discussed above can be combined and/or deleted. In addition, portions of one or more of the process steps and/or operations and/or instructions can be re-grouped as portions of one or more other of the process steps and/or operations and/or instructions discussed herein. Consequently, the particular order and/or grouping of the process steps and/or operations and/or instructions discussed herein do not limit the scope of the invention as claimed below.
As discussed in more detail above, using the above embodiments, with little or no modification and/or input, there is considerable flexibility, adaptability, and opportunity for customization to meet the specific needs of various parties under numerous circumstances.
In the discussion above, certain aspects of one embodiment include process steps and/or operations and/or instructions described herein for illustrative purposes in a particular order and/or grouping. However, the particular order and/or grouping shown and discussed herein are illustrative only and not limiting. Those of skill in the art will recognize that other orders and/or grouping of the process steps and/or operations and/or instructions are possible and, in some embodiments, one or more of the process steps and/or operations and/or instructions discussed above can be combined and/or deleted. In addition, portions of one or more of the process steps and/or operations and/or instructions can be re-grouped as portions of one or more other of the process steps and/or operations and/or instructions discussed herein. Consequently, the particular order and/or grouping of the process steps and/or operations and/or instructions discussed herein do not limit the scope of the invention as claimed below.
The present invention has been described in particular detail with respect to specific possible embodiments. Those of skill in the art will appreciate that the invention may be practiced in other embodiments. For example, the nomenclature used for components, capitalization of component designations and terms, the attributes, data structures, or any other programming or structural aspect is not significant, mandatory, or limiting, and the mechanisms that implement the invention or its features can have various different names, formats, or protocols. Further, the system or functionality of the invention may be implemented via various combinations of software and hardware, as described, or entirely in hardware elements. Also, particular divisions of functionality between the various components described herein are merely exemplary, and not mandatory or significant. Consequently, functions performed by a single component may, in other embodiments, be performed by multiple components, and functions performed by multiple components may, in other embodiments, be performed by a single component.
Some portions of the above description present the features of the present invention in terms of algorithms and symbolic representations of operations, or algorithm-like representations, of operations on information/data. These algorithmic or algorithm-like descriptions and representations are the means used by those of skill in the art to most effectively and efficiently convey the substance of their work to others of skill in the art. These operations, while described functionally or logically, are understood to be implemented by computer programs or computing systems. Furthermore, it has also proven convenient at times to refer to these arrangements of operations as steps or modules or by functional names, without loss of generality.
Unless specifically stated otherwise, as would be apparent from the above discussion, it is appreciated that throughout the above description, discussions utilizing terms such as, but not limited to, “activating”, “accessing”, “adding”, “aggregating”, “alerting”, “applying”, “analyzing”, “associating”, “calculating”, “capturing”, “categorizing”, “classifying”, “comparing”, “creating”, “defining”, “detecting”, “determining”, “distributing”, “eliminating”, “encrypting”, “extracting”, “filtering”, “forwarding”, “generating”, “identifying”, “implementing”, “informing”, “monitoring”, “obtaining”, “posting”, “processing”, “providing”, “receiving”, “requesting”, “saving”, “sending”, “storing”, “substituting”, “transferring”, “transforming”, “transmitting”, “using”, etc., refer to the action and process of a computing system or similar electronic device that manipulates and operates on data represented as physical (electronic) quantities within the computing system memories, resisters, caches or other information storage, transmission or display devices.
The present invention also relates to an apparatus or system for performing the operations described herein. This apparatus or system may be specifically constructed for the required purposes, or the apparatus or system can comprise a general purpose system selectively activated or configured/reconfigured by a computer program stored on a computer program product as discussed herein that can be accessed by a computing system or other device.
Those of skill in the art will readily recognize that the algorithms and operations presented herein are not inherently related to any particular computing system, computer architecture, computer or industry standard, or any other specific apparatus. Various general purpose systems may also be used with programs in accordance with the teaching herein, or it may prove more convenient/efficient to construct more specialized apparatuses to perform the required operations described herein. The required structure for a variety of these systems will be apparent to those of skill in the art, along with equivalent variations. In addition, the present invention is not described with reference to any particular programming language and it is appreciated that a variety of programming languages may be used to implement the teachings of the present invention as described herein, and any references to a specific language or languages are provided for illustrative purposes only and for enablement of the contemplated best mode of the invention at the time of filing.
The present invention is well suited to a wide variety of computer network systems operating over numerous topologies. Within this field, the configuration and management of large networks comprise storage devices and computers that are communicatively coupled to similar or dissimilar computers and storage devices over a private network, a LAN, a WAN, a private network, or a public network, such as the Internet.
It should also be noted that the language used in the specification has been principally selected for readability, clarity and instructional purposes, and may not have been selected to delineate or circumscribe the inventive subject matter. Accordingly, the disclosure of the present invention is intended to be illustrative, but not limiting, of the scope of the invention, which is set forth in the claims below.
In addition, the operations shown in the 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.
| Number | Name | Date | Kind |
|---|---|---|---|
| 5712641 | Casabona et al. | Jan 1998 | A |
| 5731991 | Kinra et al. | Mar 1998 | A |
| 6085224 | Wagner | Jul 2000 | A |
| 6205552 | Fudge | Mar 2001 | B1 |
| 6343236 | Gibson et al. | Jan 2002 | B1 |
| 6549932 | McNally et al. | Apr 2003 | B1 |
| 6651183 | Gensler et al. | Nov 2003 | B1 |
| 7114183 | Joiner | Sep 2006 | B1 |
| 7296261 | Witchel et al. | Nov 2007 | B2 |
| 7373524 | Motsinger et al. | May 2008 | B2 |
| 7426745 | McCarty | Sep 2008 | B2 |
| 7506371 | Ben-Natan | Mar 2009 | B1 |
| 7552424 | Bischof et al. | Jun 2009 | B1 |
| 7640458 | Rao et al. | Dec 2009 | B2 |
| 7761923 | Khuti et al. | Jul 2010 | B2 |
| 7788235 | Yeo | Aug 2010 | B1 |
| 7792256 | Arledge et al. | Sep 2010 | B1 |
| 7831570 | Sack et al. | Nov 2010 | B2 |
| 7925527 | Flam | Apr 2011 | B1 |
| 7944355 | Kumar et al. | May 2011 | B2 |
| 7996836 | McCorkendale et al. | Aug 2011 | B1 |
| 8001422 | Sun et al. | Aug 2011 | B1 |
| 8095962 | Condon | Jan 2012 | B2 |
| 8171485 | Muller | May 2012 | B2 |
| 8171554 | Elovici et al. | May 2012 | B2 |
| 8181036 | Nachenberg | May 2012 | B1 |
| 8281399 | Chen et al. | Oct 2012 | B1 |
| 8312516 | Malatesta | Nov 2012 | B1 |
| 8438643 | Wiemer et al. | May 2013 | B2 |
| 8510821 | Brandwine et al. | Aug 2013 | B1 |
| 8555388 | Wang et al. | Oct 2013 | B1 |
| 8561126 | Ananthanarayanan et al. | Oct 2013 | B2 |
| 8561127 | Agrawal et al. | Oct 2013 | B1 |
| 8572733 | Rockwood | Oct 2013 | B1 |
| 8615785 | Elrod et al. | Dec 2013 | B2 |
| 8621618 | Ramsey et al. | Dec 2013 | B1 |
| 8683585 | Chen et al. | Mar 2014 | B1 |
| 8688820 | Bhogi et al. | Apr 2014 | B1 |
| 8726383 | Blackwell | May 2014 | B2 |
| 8776050 | Plouffe et al. | Jul 2014 | B2 |
| 8813225 | Fuller et al. | Aug 2014 | B1 |
| 8990935 | Cutts | Mar 2015 | B1 |
| 9047582 | Hutchinson et al. | Jun 2015 | B2 |
| 9049105 | Feinstein et al. | Jun 2015 | B1 |
| 9112841 | Brandwine et al. | Aug 2015 | B1 |
| 9270690 | Kraitsman et al. | Feb 2016 | B2 |
| 20020066034 | Schlossberg et al. | May 2002 | A1 |
| 20020099992 | Distler et al. | Jul 2002 | A1 |
| 20020116404 | Cha et al. | Aug 2002 | A1 |
| 20020138416 | Lovejoy et al. | Sep 2002 | A1 |
| 20020147803 | Dodd et al. | Oct 2002 | A1 |
| 20030046128 | Heinrich | Mar 2003 | A1 |
| 20030051154 | Barton et al. | Mar 2003 | A1 |
| 20030084327 | Lingafelt et al. | May 2003 | A1 |
| 20030088791 | Porras et al. | May 2003 | A1 |
| 20030110392 | Aucsmith et al. | Jun 2003 | A1 |
| 20030188191 | Aaron et al. | Oct 2003 | A1 |
| 20030195959 | Labadie et al. | Oct 2003 | A1 |
| 20030233438 | Hutchinson et al. | Dec 2003 | A1 |
| 20040006704 | Dahlstrom et al. | Jan 2004 | A1 |
| 20040181775 | Anonsen et al. | Sep 2004 | A1 |
| 20040237093 | Sluiman et al. | Nov 2004 | A1 |
| 20040249973 | Alkhatib | Dec 2004 | A1 |
| 20040249974 | Alkhatib | Dec 2004 | A1 |
| 20050018618 | Mualem et al. | Jan 2005 | A1 |
| 20050066309 | Creamer et al. | Mar 2005 | A1 |
| 20050091304 | Trayler | Apr 2005 | A1 |
| 20050114836 | Fu | May 2005 | A1 |
| 20050155013 | Carrigan | Jul 2005 | A1 |
| 20050172162 | Takahashi et al. | Aug 2005 | A1 |
| 20050182969 | Ginter et al. | Aug 2005 | A1 |
| 20050188222 | Motsinger et al. | Aug 2005 | A1 |
| 20050193231 | Scheuren | Sep 2005 | A1 |
| 20050193269 | Haswell et al. | Sep 2005 | A1 |
| 20050204151 | Fang et al. | Sep 2005 | A1 |
| 20050278790 | Birk et al. | Dec 2005 | A1 |
| 20060031407 | Dispensa | Feb 2006 | A1 |
| 20060037077 | Gadde et al. | Feb 2006 | A1 |
| 20060090206 | Ladner et al. | Apr 2006 | A1 |
| 20060101520 | Schumaker et al. | May 2006 | A1 |
| 20060184838 | Singonahalli et al. | Aug 2006 | A1 |
| 20060203739 | Padmanabhan et al. | Sep 2006 | A1 |
| 20060293940 | Tsyganskiy et al. | Dec 2006 | A1 |
| 20070027999 | Allen et al. | Feb 2007 | A1 |
| 20070079168 | Sivakumar et al. | Apr 2007 | A1 |
| 20070094711 | Corley et al. | Apr 2007 | A1 |
| 20070180509 | Swartz et al. | Aug 2007 | A1 |
| 20070185875 | Chang et al. | Aug 2007 | A1 |
| 20070250424 | Kothari | Oct 2007 | A1 |
| 20080016570 | Capalik | Jan 2008 | A1 |
| 20080025288 | Benner et al. | Jan 2008 | A1 |
| 20080044018 | Scrimsher et al. | Feb 2008 | A1 |
| 20080141332 | Treinen | Jun 2008 | A1 |
| 20080148398 | Mezack et al. | Jun 2008 | A1 |
| 20080177691 | Alperovitch et al. | Jul 2008 | A1 |
| 20080262990 | Kapoor et al. | Oct 2008 | A1 |
| 20080263670 | Stavrica | Oct 2008 | A1 |
| 20080295076 | McKain et al. | Nov 2008 | A1 |
| 20090007264 | Chatterjee et al. | Jan 2009 | A1 |
| 20090089682 | Baier et al. | Apr 2009 | A1 |
| 20090106838 | Clark et al. | Apr 2009 | A1 |
| 20090199273 | Yalamanchi | Aug 2009 | A1 |
| 20090228973 | Kumar | Sep 2009 | A1 |
| 20090254970 | Agarwal et al. | Oct 2009 | A1 |
| 20090254990 | McGee | Oct 2009 | A1 |
| 20090288078 | Makonahalli et al. | Nov 2009 | A1 |
| 20090300045 | Chaudhry et al. | Dec 2009 | A1 |
| 20090300423 | Ferris | Dec 2009 | A1 |
| 20090319527 | King et al. | Dec 2009 | A1 |
| 20100020700 | Kailash et al. | Jan 2010 | A1 |
| 20100030544 | Gopalan et al. | Feb 2010 | A1 |
| 20100070964 | Blumfield et al. | Mar 2010 | A1 |
| 20100077203 | Ogawa et al. | Mar 2010 | A1 |
| 20100122317 | Yadav | May 2010 | A1 |
| 20100192220 | Heizmann et al. | Jul 2010 | A1 |
| 20100212010 | Stringer et al. | Aug 2010 | A1 |
| 20100217850 | Ferris | Aug 2010 | A1 |
| 20100251363 | Todorovic | Sep 2010 | A1 |
| 20100257580 | Zhao | Oct 2010 | A1 |
| 20100257599 | Gleichauf | Oct 2010 | A1 |
| 20100269121 | Montesissa et al. | Oct 2010 | A1 |
| 20100306354 | DeHaan et al. | Dec 2010 | A1 |
| 20100318481 | Feynman | Dec 2010 | A1 |
| 20110029957 | Shufer et al. | Feb 2011 | A1 |
| 20110034182 | Issa et al. | Feb 2011 | A1 |
| 20110047621 | Brando et al. | Feb 2011 | A1 |
| 20110055921 | Narayanaswamy et al. | Mar 2011 | A1 |
| 20110101109 | Bona et al. | May 2011 | A1 |
| 20110138382 | Hauser et al. | Jun 2011 | A1 |
| 20110138469 | Ye et al. | Jun 2011 | A1 |
| 20110145657 | Bishop et al. | Jun 2011 | A1 |
| 20110154324 | Pagan et al. | Jun 2011 | A1 |
| 20110208677 | Zhou et al. | Aug 2011 | A1 |
| 20110208797 | Kim | Aug 2011 | A1 |
| 20110238855 | Korsunsky et al. | Sep 2011 | A1 |
| 20120005750 | Satish | Jan 2012 | A1 |
| 20120039336 | Richmond et al. | Feb 2012 | A1 |
| 20120072985 | Davne et al. | Mar 2012 | A1 |
| 20120110672 | Judge et al. | May 2012 | A1 |
| 20120117654 | Yalakanti | May 2012 | A1 |
| 20120137367 | Dupont et al. | May 2012 | A1 |
| 20120151488 | Arcese et al. | Jun 2012 | A1 |
| 20120185390 | Palnitkar et al. | Jul 2012 | A1 |
| 20120185913 | Martinez et al. | Jul 2012 | A1 |
| 20120209947 | Glaser et al. | Aug 2012 | A1 |
| 20120210437 | Karande et al. | Aug 2012 | A1 |
| 20120233668 | Leafe et al. | Sep 2012 | A1 |
| 20120303776 | Ferris | Nov 2012 | A1 |
| 20120304300 | LaBumbard | Nov 2012 | A1 |
| 20120311016 | DeAnna et al. | Dec 2012 | A1 |
| 20120311157 | Erickson et al. | Dec 2012 | A1 |
| 20120311387 | Santhosh et al. | Dec 2012 | A1 |
| 20120324572 | Gordon et al. | Dec 2012 | A1 |
| 20120324576 | Clark et al. | Dec 2012 | A1 |
| 20130019242 | Chen et al. | Jan 2013 | A1 |
| 20130046667 | Hill et al. | Feb 2013 | A1 |
| 20130054792 | Sharaf | Feb 2013 | A1 |
| 20130055398 | Li et al. | Feb 2013 | A1 |
| 20130067067 | Miri et al. | Mar 2013 | A1 |
| 20130091376 | Raspudic et al. | Apr 2013 | A1 |
| 20130097316 | Bender et al. | Apr 2013 | A1 |
| 20130104237 | Riley et al. | Apr 2013 | A1 |
| 20130117809 | McDougal et al. | May 2013 | A1 |
| 20130117852 | Stute | May 2013 | A1 |
| 20130125121 | White | May 2013 | A1 |
| 20130132854 | Raleigh | May 2013 | A1 |
| 20130133072 | Kraitsman et al. | May 2013 | A1 |
| 20130160072 | Reus et al. | Jun 2013 | A1 |
| 20130174259 | Pearcy et al. | Jul 2013 | A1 |
| 20130185795 | Winn et al. | Jul 2013 | A1 |
| 20130227695 | Shankar | Aug 2013 | A1 |
| 20130238786 | Khesin | Sep 2013 | A1 |
| 20130247135 | Kundu et al. | Sep 2013 | A1 |
| 20130276108 | Blackwell | Oct 2013 | A1 |
| 20130276152 | Hirsch et al. | Oct 2013 | A1 |
| 20130291068 | Huang et al. | Oct 2013 | A1 |
| 20130291087 | Kailash et al. | Oct 2013 | A1 |
| 20130305357 | Ayyagari et al. | Nov 2013 | A1 |
| 20130305369 | Karta et al. | Nov 2013 | A1 |
| 20130305371 | Figlin et al. | Nov 2013 | A1 |
| 20130339514 | Crank et al. | Dec 2013 | A1 |
| 20130346596 | Balakrishnan et al. | Dec 2013 | A1 |
| 20130347131 | Mooring et al. | Dec 2013 | A1 |
| 20140013452 | Aissi et al. | Jan 2014 | A1 |
| 20140026122 | Markande et al. | Jan 2014 | A1 |
| 20140026179 | Devarajan et al. | Jan 2014 | A1 |
| 20140068784 | Merkow et al. | Mar 2014 | A1 |
| 20140074799 | Karampuri et al. | Mar 2014 | A1 |
| 20140082621 | Fitzgerald et al. | Mar 2014 | A1 |
| 20140089204 | Spies et al. | Mar 2014 | A1 |
| 20140096134 | Barak et al. | Apr 2014 | A1 |
| 20140165130 | Zaitsev | Jun 2014 | A1 |
| 20140173738 | Condry et al. | Jun 2014 | A1 |
| 20140189680 | Kripalani | Jul 2014 | A1 |
| 20140214460 | Rahnama | Jul 2014 | A1 |
| 20140258446 | Bursell | Sep 2014 | A1 |
| 20140258715 | Rodniansky | Sep 2014 | A1 |
| 20140259169 | Harrison | Sep 2014 | A1 |
| 20140282840 | Guinan | Sep 2014 | A1 |
| 20140289854 | Mahvi | Sep 2014 | A1 |
| 20140317737 | Shin et al. | Oct 2014 | A1 |
| 20140344933 | Huh et al. | Nov 2014 | A1 |
| 20150032587 | Broom et al. | Jan 2015 | A1 |
| 20150033340 | Giokas | Jan 2015 | A1 |
| 20150052108 | Volk et al. | Feb 2015 | A1 |
| 20150052402 | Gurumurthy et al. | Feb 2015 | A1 |
| 20150095691 | Edwards | Apr 2015 | A1 |
| 20150106939 | Lietz et al. | Apr 2015 | A1 |
| 20150128246 | Feghali et al. | May 2015 | A1 |
| 20150128274 | Giokas | May 2015 | A1 |
| 20150150123 | Be'ery | May 2015 | A1 |
| 20150229661 | Balabine et al. | Aug 2015 | A1 |
| 20150371044 | Horne et al. | Dec 2015 | A1 |
| Number | Date | Country |
|---|---|---|
| 2 541 420 | Jan 2013 | EP |
| WO 02091182 | Nov 2002 | WO |
| WO 2012135192 | Oct 2012 | WO |
| WO 2013067404 | May 2013 | WO |
| WO 2015102776 | Jul 2015 | WO |
| Entry |
|---|
| Lietz et al., “Method and System for Dynamic and Comprehensive Vulnerability Management,” U.S. Appl. No. 14/052,971, filed Oct. 14, 2013. |
| Lietz et al., “Method and System for Creating and Dynamically Deploying Resource Specific Discovery Agents for Determining the State of a Cloud Computing Environment,” U.S. Appl. No. 14/079,425, filed on Nov. 13, 2013. |
| Lietz et al., “Method and System for Creating Enriched Log Data,” U.S. Appl. No. 14/139,449, filed Dec. 23, 2013. |
| Cabrera et al., “Method and System for Intrusion and Extrusion Detection,” U.S. Appl. No. 14/143,999, filed Dec. 30, 2013. |
| Cabrera et al., “Method and System for Extrusion and Intrusion Detection in a Cloud Computing Environment Using Network Communications Devices,” U.S. Appl. No. 14/166,116, filed Jan. 28, 2014. |
| Cabrera et al., “Method and System for Extrusion and Intrusion Detection in a Cloud Computing Environment,” U.S. Appl. No. 14/171,388, filed Feb. 3, 2014. |
| Lietz et al., “Method and System for Virtual Asset Assisted Extrusion and Intrusion Detection in a Cloud Computing Environment,” U.S. Appl. No. 14/171,438, filed Feb. 3, 2014. |
| Bishop et al., “Method and System for Testing Cloud Based Applications in a Production Environment Using Fabricated User Data,” U.S. Appl. No. 14/222,279, filed Mar. 21, 2014. |
| Weaver et al., “Method and System for Comparing Different Versions of a Cloud Based Application in a Production Environment Using Segregated Backend Systems,” U.S. Appl. No. 14/231,141, filed Mar. 31, 2014. |
| Brinkley et al., “Method and System for Testing Cloud Based Applications and Services in a Production Environment Using Segregated Backend Systems,” U.S. Appl. No. 14/231,253, filed Mar. 31, 2014. |
| Lietz et al., “Method and System for Providing Security Aware Applications,” U.S. Appl. No. 14/247,131, filed Apr. 7, 2014. |
| Cabrera et al., Method and System for Providing Self-Monitoring, Self-Reporting, and Self-Repairing Virtual Assets in a Cloud Computing Environment, U.S. Appl. No. 14/256,289, filed Apr. 18, 2014. |
| Bishop et al., “Method and System for Ensuring an Application Conforms with Security and Regulatory Controls Prior to Deployment,” U.S. Appl. No. 14/261,621, filed Apr. 25, 2014. |
| Lietz et al., “Method and System for Detecting Irregularities and Vulnerabilities in Dedicated Hosting Environments,” U.S. Appl. No. 14/266,018, filed Apr. 30, 2014. |
| Lietz et al., “Method and System for Providing Reference Architecture Pattern-Based Permissions Management,” U.S. Appl. No. 14/266,107, filed Apr. 30, 2014. |
| Cabrera et al., “Method and Apparatus for Automating the Building of Threat Models for the Public Cloud,” U.S. Appl. No. 14/288,260, filed May 27, 2014. |
| Bonney et al., “Method and System for Implementing Data Security Policies Using Database Classification,” U.S. Appl. No. 14/289,817, filed May 29, 2014. |
| Lietz et al., “Method and System for Secure Delivery of Information to Computing Environments,” U.S. Appl. No. 14/319,286, filed Jun. 30, 2014. |
| Cabrera et al., “Method and System for Efficient Management of Security Threats in a Distributed Computing Environment,” U.S. Appl. No. 14/319,352, filed Jun. 30, 2014. |
| Cabrera et al., “Method and System for Providing Automated Self-Healing Virtual Assets,” U.S. Appl. No. 14/448,326, filed Jul. 31, 2014. |
| Number | Date | Country | |
|---|---|---|---|
| 20160036795 A1 | Feb 2016 | US |
