Patent Grant
12277216
The present disclosure relates generally to detection of vulnerabilities and exposures in cloud computing environments, and specifically to reducing resources required for detecting cybersecurity threats to a cloud computing environment.
Cloud computing infrastructure providers, such as Amazon® Web Services (AWS), Google® Cloud Platform (GCP), Microsoft® Azure, and Oracle® Cloud Infrastructure (OCI), are able to provision hardware resources to multiple tenants (i.e., users and groups of users) by creating an abstraction layer and provisioning the resources as requested.
Tenants in a cloud computing infrastructure may have their own cloud computing environments deployed on top of the infrastructure, with resources provisioned thereto. While the advantages of such cloud computing environments, such as the ability to scale up or down, are well documented, they also carry security risks. Inherently, these cloud computing environments need to be accessed from networks outside of the cloud computing environment in order for example to provide services. This allows not only authorized users to enter the cloud computing environment, but also provides an opportunity for malicious attackers to attempt entry into the cloud computing environment.
Accessing a cloud computing environment allows an attacker to potentially access sensitive data, or utilize the resources of the cloud computing environment for other purposes, such as mining cryptocurrency. It is therefore of primary importance to detect vulnerabilities and exposures in the cloud computing environment, and in workloads such as virtual machines, containers, and serverless functions, deployed therein.
Various solutions exist for scanning workloads deployed in cloud computing environments. Agent-based solutions require an agent to be installed on a workload. This is an additional computational burden, since an agent is an application which requires memory, processing power, etc., to run. Agentless-based solutions, for example, may require generating a snapshot of a disk of a virtual instance (e.g., a virtual machine). When a snapshot is generated, a disk is accessed, a snapshot file is generated, and a second disk is mounted based on the generated snapshot, requiring the intermediate step of generating a snapshot file.
Further, snapshots are generated only of a single disk, which in some instances may be a problem. For example, Microsoft® Azure virtual machines may be deployed using three disk types: an operating system (OS) disk, a temporary disk, and a data disk. Additionally, generating snapshots requires a garbage collection mechanism, as snapshot generation may be interrupted, resulting in garbage data which needs to be purged, and then generating another snapshot until the process is successful.
The plurality of disks are allocated to the VM 512 by a disk level provisioning 505. In an embodiment, the disk level provisioning 505 is an application deployed in a cloud computing infrastructure. The disk level provisioning 505 provisions hardware resource to the VM 512 which results in allocation of a disk. The hardware resources are provisioned from cloud storage pages 510 of the cloud computing infrastructure. The hardware resources may be solid state device (SSD) storage, hard disk drive (HDD) storage, optical storage, other magnetic storage, and the like. In an example embodiment, the cloud storage pages 510 are Azure page blobs. A page blob is a collection of a pages, each page having a predetermined size. For example, the predetermined size may be 512-bytes per page.
When a snapshot is created of the VM 512, a disk needs to be selected, as a snapshot is a copy of a disk at a point in time. As a snapshot is based on a single disk, inspection may become complicated when multiple disks are used in coordination. For example, when disk striping is performed between a plurality of disks, coordination needs to be performed between the snapshots. Furthermore, when a disk snapshot 508 is generated, for example, based on the data disk 506, the snapshot process may be interrupted, resulting in pages which need to be deleted by a garbage collection mechanism. Furthermore, the disk snapshot 508 needs to be assigned a permission to an inspector workload, as well as access to an encryption key if the disk from which the snapshot is generated is an encrypted disk.
It would therefore be advantageous to provide a solution that would overcome the challenges noted above.
A summary of several example embodiments of the disclosure follows. This summary is provided for the convenience of the reader to provide a basic understanding of such embodiments and does not wholly define the breadth of the disclosure. This summary is not an extensive overview of all contemplated embodiments, and is intended to neither identify key or critical elements of all embodiments nor to delineate the scope of any or all aspects. Its sole purpose is to present some concepts of one or more embodiments in a simplified form as a prelude to the more detailed description that is presented later. For convenience, the term “some embodiments” or “certain embodiments” may be used herein to refer to a single embodiment or multiple embodiments of the disclosure.
A system of one or more computers can be configured to perform particular operations or actions by virtue of having software, firmware, hardware, or a combination of them installed on the system that in operation causes or cause the system to perform the actions. One or more computer programs can be configured to perform particular operations or actions by virtue of including instructions that, when executed by data processing apparatus, cause the apparatus to perform the actions.
In one general aspect, method may include selecting a virtual instance in a cloud computing environment, where the virtual instance includes a disk having a disk descriptor with an address in a cloud storage system. Method may also include generating an instruction to clone the disk of the virtual instance, the instruction when executed causes generation of a cloned disk descriptor, the cloned disk descriptor having a data field including the address of the disk of the virtual instance. Method may furthermore include inspecting the cloned disk for a cybersecurity threat. Method may in addition include releasing the cloned disk in response to completing the inspection of the cloned disk. Other embodiments of this aspect include corresponding computer systems, apparatus, and computer programs recorded on one or more computer storage devices, each configured to perform the actions of the methods.
Implementations may include one or more of the following features. Method may include: releasing the cloned disk prior to the cloud computing environment copying a content of the disk of the virtual instance into the cloned disk. Method may include: generating a pointer for the cloned disk descriptor to an encryption key, the encryption key used for encrypting the disk. Method where the cloned disk descriptor includes a pointer to an address of a storage block in a managed storage of the cloud computing environment. Method may include: dereferencing a pointer of the disk of the live virtual instance; and generating a pointer for the cloned disk descriptor based on the dereferenced pointer of the disk of the live virtual instance. Method where inspecting the cloned disk for the cybersecurity threat further may include: inspecting the cloned disk for any one of: an exposure, a vulnerability, a malware, a ransomware, a spyware, a bot, a weak password, an exposed password, an exposed certificate, a misconfiguration, a suspicious event, and any combination thereof. Method may include: deprovisioning the cloned disk descriptor, in response to completing inspecting the at least a disk. Method where the virtual instance remains live during the inspection. Method where the live virtual instance is detected in the cloud computing environment. Method may include: querying a security graph to detect a disk node representing a disk, the disk node connected to a virtual instance node representing the live virtual instance, where the security graph represents the cloud computing environment. Implementations of the described techniques may include hardware, a method or process, or a computer tangible medium.
In one general aspect, non-transitory computer-readable medium may include one or more instructions that, when executed by one or more processors of a device, cause the device to: select a virtual instance in a cloud computing environment, where the virtual instance includes a disk having a disk descriptor with an address in a cloud storage system. Medium may furthermore generate an instruction to clone the disk of the virtual instance, the instruction when executed causes generation of a cloned disk descriptor, the cloned disk descriptor having a data field including the address of the disk of the virtual instance. Medium may in addition inspect the cloned disk for a cybersecurity threat. Medium may moreover release the cloned disk in response to completing the inspection of the cloned disk. Other embodiments of this aspect include corresponding computer systems, apparatus, and computer programs recorded on one or more computer storage devices, each configured to perform the actions of the methods.
In one general aspect, system may include a processing circuitry. System may also include a memory, the memory containing instructions that, when executed by the processing circuitry, configure the system to: select a virtual instance in a cloud computing environment, where the virtual instance includes a disk having a disk descriptor with an address in a cloud storage system. System may in addition generate an instruction to clone the disk of the virtual instance, the instruction when executed causes generation of a cloned disk descriptor, the cloned disk descriptor having a data field including the address of the disk of the virtual instance. System may moreover include inspect the cloned disk for a cybersecurity threat. System may also release the cloned disk in response to completing the inspection of the cloned disk. Other embodiments of this aspect include corresponding computer systems, apparatus, and computer programs recorded on one or more computer storage devices, each configured to perform the actions of the methods.
Implementations may include one or more of the following features. System where the memory contains further instructions which when executed by the processing circuitry further configure the system to: release the cloned disk prior to the cloud computing environment copying a content of the disk of the virtual instance into the cloned disk. System where the memory contains further instructions which when executed by the processing circuitry further configure the system to: generate a pointer for the cloned disk descriptor to an encryption key, the encryption key used for encrypting the disk. System where the cloned disk descriptor includes a pointer to an address of a storage block in a managed storage of the cloud computing environment. System where the memory contains further instructions which when executed by the processing circuitry further configure the system to: dereference a pointer of the disk of the live virtual instance; and generate a pointer for the cloned disk descriptor based on the dereferenced pointer of the disk of the live virtual instance. System where the one or more processors, when inspecting the cloned disk for the cybersecurity threat, are configured to: inspect the cloned disk for any one of: an exposure, a vulnerability, a malware, a ransomware, a spyware, a bot, a weak password, an exposed password, an exposed certificate, a misconfiguration, a suspicious event, and any combination thereof. System where the memory contains further instructions which when executed by the processing circuitry further configure the system to: deprovision the cloned disk descriptor, in response to completing inspecting the at least a disk. System where the virtual instance remains live during the inspection. System where the live virtual instance is detected in the cloud computing environment. System where the memory contains further instructions which when executed by the processing circuitry further configure the system to: query a security graph to detect a disk node representing a disk, the disk node connected to a virtual instance node representing the live virtual instance, where the security graph represents the cloud computing environment. Implementations of the described techniques may include hardware, a method or process, or a computer tangible medium.
The subject matter disclosed herein is particularly pointed out and distinctly claimed in the claims at the conclusion of the specification. The foregoing and other objects, features, and advantages of the disclosed embodiments will be apparent from the following detailed description taken in conjunction with the accompanying drawings.
It is important to note that the embodiments disclosed herein are only examples of the many advantageous uses of the innovative teachings herein. In general, statements made in the specification of the present application do not necessarily limit any of the various claimed embodiments. Moreover, some statements may apply to some inventive features but not to others. In general, unless otherwise indicated, singular elements may be in plural and vice versa with no loss of generality. In the drawings, like numerals refer to like parts through several views.
The various disclosed embodiments include a method and system for inspecting a disk (original disk) of a live virtual instance deployed in a production environment of a cloud computing environment. The production environment is a cloud computing environment which provides services, resources, and the like, to users of the production environment. The original disk is cloned into a cloned disk, which includes generating a cloned disk descriptor. The original disk is a virtual disk, which is assigned physical storage by using a disk descriptor. The disk descriptor is a data structure which includes a reference, such as a pointer, to an address of a physical storage of a shared storage scheme in the cloud computing environment. When generated, the cloned disk descriptor contains a pointer which points to the address of the physical storage of the original disk. The cloned disk may then be inspected, while the live virtual instance remains unperturbed. Cloud computing resource usage is reduced, due at least to not having to generate a snapshot of the disk, which would then be mounted and inspected. Further, no copy is generated and therefore data is not physically duplicated, which would require additional storage resources if performed.
The cloud computing environment 110 includes cloud entities, such as resources and principals. A resource is a cloud entity which supplies functionality, such as processing power, memory, storage, communication, and the like. A resource may supply more than one functionality. Resources may include, for example, virtual machines (VMs), such as VM 112, container engines such as container engines 114, serverless functions such as serverless functions 116, and the like. As used herein, unless otherwise noted, the terms ‘resource’, ‘virtual instance’ and ‘workload’ are used interchangeably. The cloud computing environment 110 may further include an application programming interface (API), through which actions in the cloud environment may be triggered. A container engine may be implemented using Kubernetes® or Docker®. A serverless function may implemented using Lambda®. A VM may be implemented using Oracle® VirtualBox, Azure Virtual Machines, and the like.
In an embodiment, an Azure VM is deployed with an operating system (OS) disk, a temporary disk, and at least one data disk. It should be noted a VM may be deployed with only an OS disk, in some embodiments. The at least one data disk is a managed disk which is attached to the VM and used to store, for example, application data, generated content, and the like. The OS disk includes a preinstalled OS and contains a boot volume. The temporary disk is an optional disk which is not managed, and is used for short-term storage, e.g., for storing a page file, a swap file, and the like. An example of a VM 112 is discussed in more detail in
A principal is a cloud entity which acts on a resource, meaning it can request, or otherwise initiate, actions or operations in the cloud environment which cause a resource to perform a function. A principal may be, for example, a user account, a service account, a role, and the like. In an embodiment a principal is implemented as a data structure which includes information about an entity, such as username, a password hash, an associated role, and the like.
The cloud computing environment 110 is connected with an inspection environment 120. The inspection environment 120 is a cloud computing environment. In an embodiment, the inspection environment 120 is deployed on the cloud computing infrastructure 100, in another cloud computing infrastructure, or a combination thereof. In certain embodiments a portion of the inspection environment 120 is deployed in the cloud computing environment 110. In some embodiments, certain instances deployed in the inspection environment 120 may be deployed in the cloud computing environment 110.
The inspection environment 120 includes a plurality of inspector workloads, such as inspector 124. The inspector 124 is configured to inspect workloads (i.e., virtual instances) of the cloud computing environment 110. In certain embodiments, an inspector, such as inspector 124, may be configured to inspect other cloud entities, such as user accounts, and the like. In an embodiment, a storage, such as a disk of a virtual machine, may be cloned. As will be discussed below, the cloned disk may be accessed by the inspector 124. The inspector 124 may inspect the cloned disk of the workload for security objects, such as secrets, keys, user account information, and the like. In some embodiments, the inspector 124 inspects the cloned workload for applications, operating systems, binaries, libraries, and the like.
In an embodiment, a cloned disk, which may be a clone of, for example, a data disk, an OS disk, and so on, is generated by generating an instruction, which when executed by the cloud computing environment (e.g., by an orchestrator 111 of the cloud computing environment) generates a disk descriptor, based on a virtual instance descriptor (e.g., a VM descriptor). In a cloud computing environment, an orchestrator 111 is an application which configures, coordinates, and manages applications, deployments, and the like. The virtual instance descriptor includes an address where content of the disk is stored. The address may be, for example, an address of a page in a shared storage scheme. The disk descriptor is a data structure which includes therein a data field which includes the original address from the virtual instance descriptor.
A cloned disk is instantly available for inspection, as generating the disk descriptor is an instant operation. In contrast, generating a snapshot requires copying of data, which is only available for inspection once the snapshot generation is complete. Therefore, disk cloning provides faster access to a disk for inspection, and additionally requires less computing resources for such inspection. This is advantageous as the cloning does not disturb a live virtual instance (i.e., a virtual instance deployed in a production environment) while allowing access to a data disk thereof, without requiring cloud resources other than a generation of a cloned disk descriptor. The inspection of a cloned disk is discussed in further detail below.
The inspection environment 120 further includes a security database 122, which is a graph database. A security graph may be stored on the security database 122. The security graph includes a representation of the cloud computing environment 110. For example, cloud entities of the cloud computing environment 110 may be represented each as nodes in the security graph. In an embodiment the security graph is generated based on objects detected by an inspector, such as inspector 124. In an embodiment, a virtual instance (e.g., a virtual machine) is represented by a node stored in the security graph. A disk, such as OS disk, data disk, and the like, are also represented each by a node, which is connected to the node representing the virtual instance. In certain embodiments, generating an instruction to inspect a virtual instance further includes querying a security graph to determine an identifier of a disk which is connected to the virtual instance, by generating a query to detect a node representing a disk which is connected to another node representing the virtual instance.
A controller 126 is further included in the inspection environment 120. In an embodiment the controller 126 is a workload deployed in the inspection environment 120 which is configured to initiate inspection of the cloud computing environment 110. For example, initiating inspection may include determining what cloud entities to inspect, when to inspect them, and the like.
In this example embodiment the plurality of disks includes an operating system (OS) disk 202, an optional temporary disk 204, and at least a data disk 206. The OS disk 202 includes a preinstalled OS, such as Microsoft® Windows, or Linux®. The preinstalled OS is in a boot volume of the OS disk 202. The optional temporary disk 204 may be used for storing temporary data, such as page files, swap files, and the like. The data disk 206 may be used for storing an application, application code, libraries, binaries, application data, and the like. In an embodiment, a plurality of data disks 206 may be allocated to the VM 112. In some configurations, a disk of the plurality of disks may be encrypted. For example, the OS disk 202, and the data disk 206 may be encrypted disks. In certain embodiments an encrypted disk is associated with an encryption key which can be used to decrypt the disk. For example, a VM having a Windows® allocated disk may be configured to encrypt a data disk allocated to the VM using BitLocker. A VM having a Linux® allocated disk may be configured to encrypt a data disk allocated to the VM using DM-Crypt®.
The plurality of disks are allocated to the VM 112 by a disk level provisioning 205. In an embodiment, the disk level provisioning 205 is an application deployed in a cloud computing infrastructure. The disk level provisioning 205 provisions hardware resource to the VM 112 which results in allocation of a disk. The hardware resources are provisioned from cloud storage pages 210 of the cloud computing infrastructure. The hardware resources may be solid state device (SSD) storage, hard disk drive (HDD) storage, optical storage, other magnetic storage, and the like. In an example embodiment, the cloud storage pages 210 are Azure page blobs. A page blob is a collection of a pages, each page having a predetermined size. For example, the predetermined size may be 512-bytes per page.
A disk clone 212 (also referred to as cloned disk 212) includes a disk descriptor which includes a reference to an address of a disk of the VM 112. In certain cloud computing infrastructures, when a disk is cloned, a pointer, such as pointer 216 is used to point to an original disk, in this example the data disk 206. In an embodiment, this may be achieved by dereferencing a pointer of the VM 112 which points to the data disk 206, and generating the pointer 216 for the cloned VM 212 to point to the data disk 206. In certain embodiments where a disk is encrypted, a pointer may be generated for the cloned VM 212 to the encryption key.
In an embodiment, the cloning process generates the disk clone 212 as a background process. This is possible due to utilizing diffs. A diff is an additional content that includes the difference between a content at one point in time (e.g., when the original disk was cloned) and a second, later, point in time. Thus, the VM 112 may access the data disk 206 and any diffs generated, or committed, after the disk clone 212 is generated, whereas the disk clone 212 may access only the content of the original data disk 206, and cannot access any diffs generated since.
The cloned disk 212 may then be inspected by an inspector, such as the inspector 124 of the inspection environment 120 of
By inspecting a cloned disk 212 there is no need to generate a snapshot, which prevents at least some of the deficiencies noted above. Furthermore, cloning is performed on a live virtual instance, which remains live during inspection, as the cloning does not interfere with the virtual instance's operation. Once inspection of the cloned disk 212 is complete, the cloned disk 212 may be spun down, releasing any resources allocated to it, and removing the pointers pointing to the disks of the virtual machine. In an embodiment, the cloned disk 212 may be deleted to accomplish spinning down.
At S310, a live virtual instance is detected in a cloud computing environment. A live virtual instance is a virtual instance which, at the time of detection, is deployed in a production environment. A production environment is a cloud computing environment which provides services and resources, for example, to users of the cloud computing environment. This is an environment which is distinct, for example, from a test environment in which applications, appliances, code, and the like, are tested, before being deployed in a production environment for general use.
In an embodiment, an application programming interface (API) of a cloud computing environment may be queried to detect virtual instances deployed therein. In other embodiments, a security graph may be queried to detect virtual instances deployed in the cloud computing environments. The security graph, which includes a representation of the cloud computing environment, may be queried to detect virtual instances based on at least an attribute. The at least an attribute may be, for example, a type of virtual instance (e.g., virtual machine, container, etc.), a region in which the virtual instance is deployed, a tag indicating that the virtual instance should be inspected, and the like.
In an embodiment, detecting a virtual instance further includes determining an identifier of the virtual instance, such as a name, network address, and the like. The identifier may be used to access the virtual instance. The virtual instance includes a disk (also referred to as original disk). In some embodiments, the disk is represented as a node in the security graph, the node connected to another node, the another node representing the virtual instance.
In certain embodiments, detecting a live virtual instance includes receiving an identifier of the live virtual instance, and an instruction to inspect the live virtual instance.
At S320, an instruction is generated which, when executed, configures the cloud computing environment to clone the disk of the virtual instance. In an embodiment, the instruction is generated for execution by an orchestrator of the cloud computing environment in which the virtual instance, also called a parent virtual instance, is deployed. When executed, the instruction configures, for example, the cloud computing environment, to allocate resources to a cloned disk. The cloned disk is an independent copy of the original disk of the parent virtual instance. An independent copy of a disk is a copy which can be deployed and accessed independently of the original disk. This is as opposed to a copy of a virtual instance, such as a snapshot, which requires additional resources allocated in order to deploy.
For example, a snapshot may be generated based off of a single disk of a virtual instance. A new disk (e.g., persistent volume) may be generated based off of the snapshot, and a claim (e.g., persistent volume claim) generated to another virtual instance in order to access data stored on the new disk. Furthermore, a snapshot is only available once the disk is completely copied. In contrast, a clone is available immediately as the operation of generating a disk descriptor is faster than an operation of generating a snapshot. For at least this reason inspection is completed faster.
In certain embodiments, the instruction, when executed, configures the cloud computing environment to generate a cloned disk having a reference, such as a pointer, to the original disk of the parent virtual instance. In some embodiments, the disk is encrypted with an encryption key. The encryption key, as well as the disk, may be dereferenced. Dereferencing an encryption key (or a disk) may include determining where a pointer of the parent virtual instance is pointing to, e.g., the pointer points to a block address of a managed block storage. A new pointer may be stored for the cloned disk which points to the same block address, encryption key, etc. as the dereferenced pointer.
In some embodiments, an optional check is performed to determine if the cloned disk is configured to be deployed in a same region as the parent virtual instance. A cloud computing infrastructure may limit the ability to clone a disk outside of a region. For example, if an inspection environment is not in the same region as the cloud computing environment in which the virtual instance is inspected, it may not be possible (i.e., not permissible) to generate a disk clone in the region where the inspection environment is.
In other embodiments, an optional check may be performed to determine the number of disks associated with a virtual instance. For example, if the number of disks equals or exceeds a predetermined threshold the cloning process may be initiated, otherwise a snapshot is generated, and inspection is performed on the generated snapshot.
At S330, the cloned disk is inspected for cybersecurity threats. In an embodiment, cybersecurity threats include, but are not limited to, exposures, vulnerabilities, malware, ransomware, spyware, bots, weak passwords, exposed passwords, exposed certificates, outdated certificates, misconfigurations, suspicious events, and the like.
Inspecting a cloned disk includes, in an embodiment, assigning an inspector to the cloned disk. In some embodiments, an inspector, such as inspector 124 of
For example, in an embodiment, a signature for a file, folder, and the like is generated during an inspection. Such a signature is matched to another known signature. The known signature indicates a vulnerability. A signature may be generated, for example, using a checksum.
At S340, the cloned disk is released. In an embodiment, an instruction may be generated which, when executed, configures the cloud computing environment to release the cloned disk. Releasing a cloned disk may include, for example, deprovisioning resources allocated to the cloned disk. For example, a cloned disk may be deleted. Releasing the cloned disk is performed in response to completing the inspection.
While virtual machines are discussed throughout this disclosure, it should be understood that the teachings herein apply equally to other virtual instances with respect to cloning and snapshot generation.
The processing circuitry 410 may be realized as one or more hardware logic components and circuits. For example, and without limitation, illustrative types of hardware logic components that can be used include field programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), Application-specific standard products (ASSPs), system-on-a-chip systems (SOCs), graphics processing units (GPUs), tensor processing units (TPUs), general-purpose microprocessors, microcontrollers, digital signal processors (DSPs), and the like, or any other hardware logic components that can perform calculations or other manipulations of information.
The memory 420 may be volatile (e.g., random access memory, etc.), non-volatile (e.g., read only memory, flash memory, etc.), or a combination thereof.
In one configuration, software for implementing one or more embodiments disclosed herein may be stored in the storage 430. In another configuration, the memory 420 is configured to store such software. Software shall be construed broadly to mean any type of instructions, whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise. Instructions may include code (e.g., in source code format, binary code format, executable code format, or any other suitable format of code). The instructions, when executed by the processing circuitry 410, cause the processing circuitry 410 to perform the various processes described herein.
The storage 430 may be magnetic storage, optical storage, and the like, and may be realized, for example, as flash memory or other memory technology, compact disk-read only memory (CD-ROM), Digital Versatile Disks (DVDs), or any other medium which can be used to store the desired information.
The network interface 440 allows the controller 126 to communicate with, for example, an inspector 124, a security database 122, and the like.
It should be understood that the embodiments described herein are not limited to the specific architecture illustrated in
The various embodiments disclosed herein can be implemented as hardware, firmware, software, or any combination thereof. Moreover, the software is preferably implemented as an application program tangibly embodied on a program storage unit or computer readable medium consisting of parts, or of certain devices and/or a combination of devices. The application program may be uploaded to, and executed by, a machine comprising any suitable architecture. Preferably, the machine is implemented on a computer platform having hardware such as one or more central processing units (“CPUs”), a memory, and input/output interfaces. The computer platform may also include an operating system and microinstruction code. The various processes and functions described herein may be either part of the microinstruction code or part of the application program, or any combination thereof, which may be executed by a CPU, whether or not such a computer or processor is explicitly shown. In addition, various other peripheral units may be connected to the computer platform such as an additional data storage unit and a printing unit. Furthermore, a non-transitory computer readable medium is any computer readable medium except for a transitory propagating signal.
All examples and conditional language recited herein are intended for pedagogical purposes to aid the reader in understanding the principles of the disclosed embodiment and the concepts contributed by the inventor to furthering the art, and are to be construed as being without limitation to such specifically recited examples and conditions. Moreover, all statements herein reciting principles, aspects, and embodiments of the disclosed embodiments, as well as specific examples thereof, are intended to encompass both structural and functional equivalents thereof. Additionally, it is intended that such equivalents include both currently known equivalents as well as equivalents developed in the future, i.e., any elements developed that perform the same function, regardless of structure.
It should be understood that any reference to an element herein using a designation such as “first,” “second,” and so forth does not generally limit the quantity or order of those elements. Rather, these designations are generally used herein as a convenient method of distinguishing between two or more elements or instances of an element. Thus, a reference to first and second elements does not mean that only two elements may be employed there or that the first element must precede the second element in some manner. Also, unless stated otherwise, a set of elements comprises one or more elements.
As used herein, the phrase “at least one of” followed by a listing of items means that any of the listed items can be utilized individually, or any combination of two or more of the listed items can be utilized. For example, if a system is described as including “at least one of A, B, and C,” the system can include A alone; B alone; C alone; 2A; 2B; 2C; 3A; A and B in combination; B and C in combination; A and C in combination; A, B, and C in combination; 2A and C in combination; A, 3B, and 2C in combination; and the like.
This application is a continuation of U.S. patent application Ser. No. 17/664,508 filed on May 23, 2022, now pending. The contents of the above-referenced application are hereby incorporated by reference.
| Number | Name | Date | Kind |
|---|---|---|---|
| 6910132 | Bhattacharya | Jun 2005 | B1 |
| 7627652 | Commons et al. | Dec 2009 | B1 |
| 7784101 | Verbowski et al. | Aug 2010 | B2 |
| 8200965 | Fujibayashi et al. | Jun 2012 | B2 |
| 8352431 | Protopopov et al. | Jan 2013 | B1 |
| 8412688 | Armangau et al. | Apr 2013 | B1 |
| 8413239 | Sutton | Apr 2013 | B2 |
| 8417967 | Foster et al. | Apr 2013 | B2 |
| 8499354 | Satish et al. | Jul 2013 | B1 |
| 8595822 | Schrecker et al. | Nov 2013 | B2 |
| 8701200 | Naldurg et al. | Apr 2014 | B2 |
| 8789049 | Hutchins et al. | Jul 2014 | B2 |
| 8813234 | Bowers et al. | Aug 2014 | B1 |
| 8898481 | Osburn, III et al. | Nov 2014 | B1 |
| 8904525 | Hodgman et al. | Dec 2014 | B1 |
| 8914406 | Haugsnes | Dec 2014 | B1 |
| 9009836 | Yarykin et al. | Apr 2015 | B1 |
| 9094379 | Miller | Jul 2015 | B1 |
| 9119017 | Sinha | Aug 2015 | B2 |
| 9165142 | Sanders et al. | Oct 2015 | B1 |
| 9172621 | Dippenaar | Oct 2015 | B1 |
| 9185136 | Dulkin et al. | Nov 2015 | B2 |
| 9330273 | Khetawat et al. | May 2016 | B2 |
| 9369433 | Paul | Jun 2016 | B1 |
| 9419996 | Porat | Aug 2016 | B2 |
| 9438634 | Ross et al. | Sep 2016 | B1 |
| 9467473 | Jayaraman | Oct 2016 | B2 |
| 9544327 | Sharma et al. | Jan 2017 | B1 |
| 9563385 | Kowalski et al. | Feb 2017 | B1 |
| 9569328 | Pavlov et al. | Feb 2017 | B2 |
| 9582662 | Messick et al. | Feb 2017 | B1 |
| 9596235 | Badam et al. | Mar 2017 | B2 |
| 9607104 | Turner et al. | Mar 2017 | B1 |
| 9646172 | Hahn | May 2017 | B1 |
| 9661009 | Karandikar et al. | May 2017 | B1 |
| 9672355 | Titonis et al. | Jun 2017 | B2 |
| 9712503 | Ahmed | Jul 2017 | B1 |
| 9892261 | Joram et al. | Feb 2018 | B2 |
| 10002247 | Suarez et al. | Jun 2018 | B2 |
| 10032032 | Suarez et al. | Jul 2018 | B2 |
| 10063445 | Preece | Aug 2018 | B1 |
| 10135826 | Reddy | Nov 2018 | B2 |
| 10229125 | Goodman et al. | Mar 2019 | B2 |
| 10255370 | Carpenter et al. | Apr 2019 | B2 |
| 10360025 | Foskett et al. | Jul 2019 | B2 |
| 10412103 | Haugsnes | Sep 2019 | B2 |
| 10412109 | Loureiro et al. | Sep 2019 | B2 |
| 10459664 | Dreier et al. | Oct 2019 | B1 |
| 10503904 | Singh et al. | Dec 2019 | B1 |
| 10536471 | Derbeko et al. | Jan 2020 | B1 |
| 10540499 | Wailly et al. | Jan 2020 | B2 |
| 10552610 | Vashisht et al. | Feb 2020 | B1 |
| 10554507 | Siddiqui et al. | Feb 2020 | B1 |
| 10567468 | Perlmutter | Feb 2020 | B2 |
| 10572226 | Biskup et al. | Feb 2020 | B2 |
| 10574675 | Peppe et al. | Feb 2020 | B2 |
| 10623386 | Bernat et al. | Apr 2020 | B1 |
| 10630642 | Clark et al. | Apr 2020 | B2 |
| 10664619 | Marelas | May 2020 | B1 |
| 10691636 | Tabaaloute et al. | Jun 2020 | B2 |
| 10721260 | Schlarp et al. | Jul 2020 | B1 |
| 10725775 | Suarez et al. | Jul 2020 | B2 |
| 10735430 | Stoler | Aug 2020 | B1 |
| 10735442 | Swackhamer | Aug 2020 | B1 |
| 10791138 | Siddiqui et al. | Sep 2020 | B1 |
| 10803188 | Rajput et al. | Oct 2020 | B1 |
| 10831898 | Wagner | Nov 2020 | B1 |
| 10915626 | Tang | Feb 2021 | B2 |
| 10924503 | Pereira et al. | Feb 2021 | B1 |
| 10972484 | Swackhamer | Apr 2021 | B1 |
| 10997293 | Wiest et al. | May 2021 | B2 |
| 11005860 | Glyer et al. | May 2021 | B1 |
| 11016954 | Babocichin et al. | May 2021 | B1 |
| 11044118 | Reed et al. | Jun 2021 | B1 |
| 11055414 | Claes | Jul 2021 | B2 |
| 11064032 | Yang et al. | Jul 2021 | B1 |
| 11099976 | Khakare et al. | Aug 2021 | B2 |
| 11102231 | Kraning et al. | Aug 2021 | B2 |
| 11165652 | Byrne | Nov 2021 | B1 |
| 11216563 | Veselov | Jan 2022 | B1 |
| 11245730 | Bailey | Feb 2022 | B2 |
| 11271961 | Berger | Mar 2022 | B1 |
| 11334670 | Franco et al. | May 2022 | B2 |
| 11366897 | Ramanathan et al. | Jun 2022 | B1 |
| 11388183 | Hoopes et al. | Jul 2022 | B2 |
| 11397808 | Prabhu et al. | Jul 2022 | B1 |
| 11405426 | Nguyen | Aug 2022 | B2 |
| 11444974 | Shakhzadyan | Sep 2022 | B1 |
| 11483317 | Bolignano et al. | Oct 2022 | B1 |
| 11496498 | Wright et al. | Nov 2022 | B2 |
| 11496519 | Gupta et al. | Nov 2022 | B1 |
| 11503063 | Rao | Nov 2022 | B2 |
| 11507672 | Pagnozzi et al. | Nov 2022 | B1 |
| 11516222 | Srinivasan et al. | Nov 2022 | B1 |
| 11520907 | Borowiec et al. | Dec 2022 | B1 |
| 11546360 | Woodford et al. | Jan 2023 | B2 |
| 11556659 | Kumar et al. | Jan 2023 | B1 |
| 11558401 | Vashisht et al. | Jan 2023 | B1 |
| 11558423 | Gordon et al. | Jan 2023 | B2 |
| 11567751 | Cosentino et al. | Jan 2023 | B2 |
| 11570090 | Shen et al. | Jan 2023 | B2 |
| 11575696 | Ithal et al. | Feb 2023 | B1 |
| 11606378 | Delpont et al. | Mar 2023 | B1 |
| 11614956 | Tsirkin et al. | Mar 2023 | B2 |
| 11645390 | Vijayvargiya et al. | May 2023 | B2 |
| 11662928 | Kumar et al. | May 2023 | B1 |
| 11663340 | Wu et al. | May 2023 | B2 |
| 11669386 | Abrol | Jun 2023 | B1 |
| 11700233 | St. Pierre | Jul 2023 | B2 |
| 11750566 | Montilla Lugo | Sep 2023 | B1 |
| 11757844 | Xiao | Sep 2023 | B2 |
| 11770398 | Erlingsson | Sep 2023 | B1 |
| 11792284 | Nanduri | Oct 2023 | B1 |
| 11799874 | Lichtenstein et al. | Oct 2023 | B1 |
| 11803766 | Srinivasan | Oct 2023 | B1 |
| 11831670 | Molls et al. | Nov 2023 | B1 |
| 11841945 | Fogel et al. | Dec 2023 | B1 |
| 11914707 | Ramanathan et al. | Feb 2024 | B1 |
| 11922220 | Haghighat et al. | Mar 2024 | B2 |
| 11936785 | Shemesh et al. | Mar 2024 | B1 |
| 12019770 | Nilsson et al. | Jun 2024 | B2 |
| 12050696 | Pieno et al. | Jul 2024 | B2 |
| 12058177 | Crabtree et al. | Aug 2024 | B2 |
| 20030188194 | Currie et al. | Oct 2003 | A1 |
| 20030217039 | Kurtz et al. | Nov 2003 | A1 |
| 20050050365 | Seki et al. | Mar 2005 | A1 |
| 20050251863 | Sima | Nov 2005 | A1 |
| 20050283645 | Turner et al. | Dec 2005 | A1 |
| 20070174915 | Gribble et al. | Jul 2007 | A1 |
| 20070271360 | Sahita et al. | Nov 2007 | A1 |
| 20080075283 | Takahashi | Mar 2008 | A1 |
| 20080221833 | Brown et al. | Sep 2008 | A1 |
| 20080307020 | Ko et al. | Dec 2008 | A1 |
| 20080320594 | Jiang | Dec 2008 | A1 |
| 20090106256 | Safari et al. | Apr 2009 | A1 |
| 20090271863 | Govindavajhala et al. | Oct 2009 | A1 |
| 20100242082 | Keene et al. | Sep 2010 | A1 |
| 20100281275 | Lee et al. | Nov 2010 | A1 |
| 20110055361 | Dehaan | Mar 2011 | A1 |
| 20110276806 | Casper et al. | Nov 2011 | A1 |
| 20120110651 | Van Biljon et al. | May 2012 | A1 |
| 20120297206 | Nord et al. | Nov 2012 | A1 |
| 20130024940 | Hutchins et al. | Jan 2013 | A1 |
| 20130054890 | Desai et al. | Feb 2013 | A1 |
| 20130124669 | Anderson et al. | May 2013 | A1 |
| 20130160119 | Sartin | Jun 2013 | A1 |
| 20130160129 | Sartin | Jun 2013 | A1 |
| 20130290708 | Diaz et al. | Oct 2013 | A1 |
| 20140096134 | Barak | Apr 2014 | A1 |
| 20140115578 | Cooper et al. | Apr 2014 | A1 |
| 20140237537 | Manmohan | Aug 2014 | A1 |
| 20140317677 | Vaidya | Oct 2014 | A1 |
| 20140337613 | Martini | Nov 2014 | A1 |
| 20150033305 | Shear | Jan 2015 | A1 |
| 20150055647 | Roberts | Feb 2015 | A1 |
| 20150095995 | Bhalerao | Apr 2015 | A1 |
| 20150163192 | Jain | Jun 2015 | A1 |
| 20150172321 | Kirti et al. | Jun 2015 | A1 |
| 20150254364 | Piduri et al. | Sep 2015 | A1 |
| 20150304302 | Zhang et al. | Oct 2015 | A1 |
| 20150310215 | McBride et al. | Oct 2015 | A1 |
| 20150319160 | Ferguson et al. | Nov 2015 | A1 |
| 20160063466 | Sheridan et al. | Mar 2016 | A1 |
| 20160078231 | Bach et al. | Mar 2016 | A1 |
| 20160103669 | Gamage et al. | Apr 2016 | A1 |
| 20160105454 | Li | Apr 2016 | A1 |
| 20160140352 | Nickolov | May 2016 | A1 |
| 20160156664 | Nagaratnam | Jun 2016 | A1 |
| 20160224600 | Munk | Aug 2016 | A1 |
| 20160299708 | Yang et al. | Oct 2016 | A1 |
| 20160366185 | Lee et al. | Dec 2016 | A1 |
| 20170026416 | Carpenter et al. | Jan 2017 | A1 |
| 20170070506 | Reddy | Mar 2017 | A1 |
| 20170104755 | Arregoces | Apr 2017 | A1 |
| 20170111384 | Loureiro et al. | Apr 2017 | A1 |
| 20170180421 | Shieh et al. | Jun 2017 | A1 |
| 20170185784 | Madou | Jun 2017 | A1 |
| 20170187743 | Madou | Jun 2017 | A1 |
| 20170223024 | Desai | Aug 2017 | A1 |
| 20170230179 | Mannan et al. | Aug 2017 | A1 |
| 20170237560 | Mueller et al. | Aug 2017 | A1 |
| 20170257347 | Yan | Sep 2017 | A1 |
| 20170285978 | Manasse | Oct 2017 | A1 |
| 20170300690 | Ladnai et al. | Oct 2017 | A1 |
| 20170034198 | Powers et al. | Dec 2017 | A1 |
| 20170374136 | Ringdahl | Dec 2017 | A1 |
| 20180004950 | Gupta et al. | Jan 2018 | A1 |
| 20180007087 | Grady et al. | Jan 2018 | A1 |
| 20180026995 | Dufour et al. | Jan 2018 | A1 |
| 20180027009 | Santos | Jan 2018 | A1 |
| 20180063290 | Yang et al. | Mar 2018 | A1 |
| 20180081640 | Collins | Mar 2018 | A1 |
| 20180150412 | Manasse | May 2018 | A1 |
| 20180159882 | Brill | Jun 2018 | A1 |
| 20180181310 | Feinberg | Jun 2018 | A1 |
| 20180191726 | Luukkala | Jul 2018 | A1 |
| 20180219888 | Apostolopoulos | Aug 2018 | A1 |
| 20180234459 | Kung | Aug 2018 | A1 |
| 20180239902 | Godard | Aug 2018 | A1 |
| 20180260566 | Chaganti et al. | Sep 2018 | A1 |
| 20180270268 | Gorodissky et al. | Sep 2018 | A1 |
| 20180276084 | Mitkar | Sep 2018 | A1 |
| 20180278639 | Bernstein et al. | Sep 2018 | A1 |
| 20180288129 | Joshi et al. | Oct 2018 | A1 |
| 20180309747 | Sweet et al. | Oct 2018 | A1 |
| 20180321993 | McClory et al. | Nov 2018 | A1 |
| 20180341768 | Marshall et al. | Nov 2018 | A1 |
| 20180359058 | Kurian | Dec 2018 | A1 |
| 20180359059 | Kurian | Dec 2018 | A1 |
| 20180367548 | Stokes, III et al. | Dec 2018 | A1 |
| 20190007271 | Rickards et al. | Jan 2019 | A1 |
| 20190018961 | Kostyushko et al. | Jan 2019 | A1 |
| 20190043201 | Strong et al. | Feb 2019 | A1 |
| 20190058722 | Levin et al. | Feb 2019 | A1 |
| 20190068617 | Coleman | Feb 2019 | A1 |
| 20190068627 | Thampy | Feb 2019 | A1 |
| 20190081963 | Waghorn | Mar 2019 | A1 |
| 20190104140 | Gordeychik et al. | Apr 2019 | A1 |
| 20190116111 | Izard et al. | Apr 2019 | A1 |
| 20190121986 | Stopel et al. | Apr 2019 | A1 |
| 20190132350 | Smith et al. | May 2019 | A1 |
| 20190149604 | Jahr | May 2019 | A1 |
| 20190166129 | Gaetjen et al. | May 2019 | A1 |
| 20190171811 | Daniel et al. | Jun 2019 | A1 |
| 20190191417 | Baldemair et al. | Jun 2019 | A1 |
| 20190205267 | Richey et al. | Jul 2019 | A1 |
| 20190207966 | Vashisht et al. | Jul 2019 | A1 |
| 20190220575 | Boudreau et al. | Jul 2019 | A1 |
| 20190245883 | Gorodissky et al. | Aug 2019 | A1 |
| 20190260764 | Humphrey et al. | Aug 2019 | A1 |
| 20190278928 | Rungta et al. | Sep 2019 | A1 |
| 20190354675 | Gan et al. | Nov 2019 | A1 |
| 20190377988 | Qi et al. | Dec 2019 | A1 |
| 20200007314 | Vouk et al. | Jan 2020 | A1 |
| 20200007569 | Dodge et al. | Jan 2020 | A1 |
| 20200012659 | Dageville et al. | Jan 2020 | A1 |
| 20200012818 | Levin et al. | Jan 2020 | A1 |
| 20200028862 | Lin | Jan 2020 | A1 |
| 20200044916 | Kaufman et al. | Feb 2020 | A1 |
| 20200050440 | Chuppala et al. | Feb 2020 | A1 |
| 20200082094 | McAllister et al. | Mar 2020 | A1 |
| 20200106782 | Sion | Apr 2020 | A1 |
| 20200125352 | Kannan | Apr 2020 | A1 |
| 20200145405 | Bosch et al. | May 2020 | A1 |
| 20200244678 | Shua | Jul 2020 | A1 |
| 20200244692 | Shua | Jul 2020 | A1 |
| 20200259852 | Wolff et al. | Aug 2020 | A1 |
| 20200287927 | Zadeh et al. | Sep 2020 | A1 |
| 20200320845 | Livny et al. | Oct 2020 | A1 |
| 20200336489 | Wuest et al. | Oct 2020 | A1 |
| 20200382556 | Woolward et al. | Dec 2020 | A1 |
| 20200387357 | Mathon et al. | Dec 2020 | A1 |
| 20200389431 | St. Pierre | Dec 2020 | A1 |
| 20200389469 | Litichever et al. | Dec 2020 | A1 |
| 20200409741 | Dornemann et al. | Dec 2020 | A1 |
| 20210014265 | Hadar et al. | Jan 2021 | A1 |
| 20210026932 | Boudreau et al. | Jan 2021 | A1 |
| 20210042263 | Zdornov et al. | Feb 2021 | A1 |
| 20210089662 | Muniswamy-Reddy et al. | Mar 2021 | A1 |
| 20210105304 | Kraning et al. | Apr 2021 | A1 |
| 20210144517 | Guim Bernat et al. | May 2021 | A1 |
| 20210149788 | Downie | May 2021 | A1 |
| 20210158835 | Hill et al. | May 2021 | A1 |
| 20210168150 | Ross et al. | Jun 2021 | A1 |
| 20210176123 | Plamondon | Jun 2021 | A1 |
| 20210176164 | Kung et al. | Jun 2021 | A1 |
| 20210185073 | Ewaida et al. | Jun 2021 | A1 |
| 20210200881 | Joshi et al. | Jul 2021 | A1 |
| 20210203684 | Maor et al. | Jul 2021 | A1 |
| 20210211453 | Cooney | Jul 2021 | A1 |
| 20210216630 | Karr | Jul 2021 | A1 |
| 20210218567 | Richards et al. | Jul 2021 | A1 |
| 20210226812 | Park | Jul 2021 | A1 |
| 20210226928 | Crabtree et al. | Jul 2021 | A1 |
| 20210234889 | Burle et al. | Jul 2021 | A1 |
| 20210263802 | Gottemukkula et al. | Aug 2021 | A1 |
| 20210297447 | Crabtree et al. | Sep 2021 | A1 |
| 20210306416 | Mukhopadhyay et al. | Sep 2021 | A1 |
| 20210314342 | Oberg | Oct 2021 | A1 |
| 20210320794 | Auh et al. | Oct 2021 | A1 |
| 20210329019 | Shua | Oct 2021 | A1 |
| 20210334386 | AlGhamdi et al. | Oct 2021 | A1 |
| 20210357246 | Kumar et al. | Nov 2021 | A1 |
| 20210360032 | Crabtree et al. | Nov 2021 | A1 |
| 20210368045 | Verma | Nov 2021 | A1 |
| 20210382995 | Massiglia et al. | Dec 2021 | A1 |
| 20210382997 | Yi et al. | Dec 2021 | A1 |
| 20210406365 | Neil et al. | Dec 2021 | A1 |
| 20210409486 | Martinez | Dec 2021 | A1 |
| 20220012771 | Gustafson | Jan 2022 | A1 |
| 20220030020 | Huffman | Jan 2022 | A1 |
| 20220053011 | Rao et al. | Feb 2022 | A1 |
| 20220060497 | Crabtree et al. | Feb 2022 | A1 |
| 20220086173 | Yavo et al. | Mar 2022 | A1 |
| 20220131888 | Kanso | Apr 2022 | A1 |
| 20220156396 | Bednash et al. | May 2022 | A1 |
| 20220179964 | Qiao et al. | Jun 2022 | A1 |
| 20220182403 | Mistry | Jun 2022 | A1 |
| 20220188273 | Koorapati et al. | Jun 2022 | A1 |
| 20220197926 | Passey et al. | Jun 2022 | A1 |
| 20220210053 | Du | Jun 2022 | A1 |
| 20220215101 | Rioux et al. | Jul 2022 | A1 |
| 20220232024 | Kapoor | Jul 2022 | A1 |
| 20220232042 | Crabtree et al. | Jul 2022 | A1 |
| 20220247791 | Duminuco et al. | Aug 2022 | A1 |
| 20220263656 | Moore | Aug 2022 | A1 |
| 20220284362 | Bellinger et al. | Sep 2022 | A1 |
| 20220309166 | Shenoy et al. | Sep 2022 | A1 |
| 20220326861 | Shachar et al. | Oct 2022 | A1 |
| 20220327119 | Gasper et al. | Oct 2022 | A1 |
| 20220342690 | Shua | Oct 2022 | A1 |
| 20220342997 | Watanabe et al. | Oct 2022 | A1 |
| 20220345481 | Shua | Oct 2022 | A1 |
| 20220350931 | Shua | Nov 2022 | A1 |
| 20220357992 | Karpovsky | Nov 2022 | A1 |
| 20220374519 | Botelho et al. | Nov 2022 | A1 |
| 20220400128 | Kfir et al. | Dec 2022 | A1 |
| 20220407841 | Karpowicz | Dec 2022 | A1 |
| 20220407889 | Narigapalli et al. | Dec 2022 | A1 |
| 20220413879 | Passey et al. | Dec 2022 | A1 |
| 20220414103 | Upadhyay et al. | Dec 2022 | A1 |
| 20220417011 | Shua | Dec 2022 | A1 |
| 20220417219 | Sheriff | Dec 2022 | A1 |
| 20230007014 | Narayan | Jan 2023 | A1 |
| 20230011957 | Panse et al. | Jan 2023 | A1 |
| 20230040635 | Narayan | Feb 2023 | A1 |
| 20230075355 | Twigg | Mar 2023 | A1 |
| 20230087093 | Ithal et al. | Mar 2023 | A1 |
| 20230093527 | Shua | Mar 2023 | A1 |
| 20230095756 | Wilkinson et al. | Mar 2023 | A1 |
| 20230110080 | Hen | Apr 2023 | A1 |
| 20230123477 | Luttwak et al. | Apr 2023 | A1 |
| 20230125134 | Raleigh et al. | Apr 2023 | A1 |
| 20230134674 | Quinn et al. | May 2023 | A1 |
| 20230135240 | Cody et al. | May 2023 | A1 |
| 20230136839 | Sundararajan et al. | May 2023 | A1 |
| 20230161614 | Herzberg et al. | May 2023 | A1 |
| 20230164148 | Narayan | May 2023 | A1 |
| 20230164164 | Herzberg et al. | May 2023 | A1 |
| 20230164182 | Kothari et al. | May 2023 | A1 |
| 20230169165 | Williams et al. | Jun 2023 | A1 |
| 20230171271 | Williams et al. | Jun 2023 | A1 |
| 20230192418 | Horowitz et al. | Jun 2023 | A1 |
| 20230208870 | Yellapragada et al. | Jun 2023 | A1 |
| 20230224319 | Isoyama et al. | Jul 2023 | A1 |
| 20230231867 | Rampura Venkatachar | Jul 2023 | A1 |
| 20230237068 | Sillifant et al. | Jul 2023 | A1 |
| 20230254330 | Singh | Aug 2023 | A1 |
| 20230297666 | Atamli et al. | Sep 2023 | A1 |
| 20230325814 | Vijayan et al. | Oct 2023 | A1 |
| 20230336550 | Lidgi et al. | Oct 2023 | A1 |
| 20230336578 | Lidgi et al. | Oct 2023 | A1 |
| 20230376586 | Shemesh et al. | Nov 2023 | A1 |
| 20240007492 | Shen et al. | Jan 2024 | A1 |
| 20240037229 | Pabón et al. | Feb 2024 | A1 |
| 20240045838 | Reiss et al. | Feb 2024 | A1 |
| 20240073115 | Chakraborty et al. | Feb 2024 | A1 |
| 20240080329 | Reed et al. | Mar 2024 | A1 |
| 20240080332 | Ganesh et al. | Mar 2024 | A1 |
| 20240146818 | Cody et al. | May 2024 | A1 |
| 20240241752 | Crabtree et al. | Jul 2024 | A1 |
| Number | Date | Country |
|---|---|---|
| 4160983 | Apr 2023 | EP |
| 4254869 | Oct 2023 | EP |
| 2421792 | Jun 2011 | RU |
| 10202009702 | Apr 2021 | SG |
| Entry |
|---|
| International Search Report, PCT/IB23/55312. ISA/US, Commissioner for Patents, Alexandria, Virginia. Dated Aug. 30, 2023. |
| Written Opinion of the International Searching Authority, PCT/IB23/55312. ISA/US Commissioner for Patents, Alexandria, Virginia. Dated Aug. 30, 2023. |
| Microsoft Build. “Introduction to Azure managed disks”. Aug. 21, 2023, https://docs.microsoft.com/en-us/azure/virtual-machines/managed-disks-overview. |
| Ali Gholami; Security and Privacy of Sensitive Data in Cloud Computing: A Survey of Recent Developments; ARIX:2016; pp. 131-150. |
| Christos Kyrkou; Towards artificial-intelligence-based cybersecurity for robustifying automated driving systems against camera sensor attacks; IEEE 2020; pp. 476-481. |
| Guo, yu et al. Enabling Encrypted Rich Queries in Distributed Key-Value Stores. IEEE Transactions on Parallel and Distributed Systems, vol. 30, Issue: 6. https://ieeexplore.ieee.org/stamp/stamp.jsp?tp=&arnumber=8567979 (Year: 2019). |
| Henry Hanping Feng; Anomaly Detection Using Call Stack Information; IEEE: Year:2003; pp. 1-14. |
| International Search Report for PCT Application No. PCT/IB2022/060940 dated Feb. 1, 2023. The International Bureau of WIPO. |
| International Search Report for PCT/IB2023/050848, dated May 9, 2023. International Bureau of WIPO. |
| International Search Report of PCT/IB2023/058074, dated Nov. 20, 2023. Searching Authority United States Patent and Trademark Office, Alexandria, Virginia. |
| Jordan, M. et al. Enabling pervasive encryption through IBM Z stack innovations. IBM Journal of Research and Development, vol. 62 Issue: 2/3, https://ieeexplore.ieee.org/stamp/stamp.jsp?tp&arnumber=8270590 (Year: 2018). |
| Kumar, Anuj et al. A New Approach for Security in Cloud Data Storage for IOT Applications Using Hybrid Cryptography Technique. 2020 International Conference on Power Electronics & IoT Applications in Renewable Energy and its Control. https://ieeexplore. ieee.org/stamp/stamp.jsp?tp=&arnumber=9087010 (Year: 2020). |
| Leibenger, Dominik et al. EncFS goes multi-user: Adding access control to an encrypted file system. 2016 IEEE Conference on Communications and Network Security (CNS). https://ieeexoplore.ieee.org/stamp/stamp.jsp?tp=&arnumber=7860544 (Year: 2016). |
| Microsoft Docs. “Create a VM from a managed image”. Article. Jan. 5, 2022. https://docs.microsoft.com/en-us/azure/virtual-machines/windows/create-vm-generalized-managed. |
| Mishra, Bharati; Jena, Debasish et al. Securing Files in the Cloud. 2016 IEEE International Conference on Cloud Computing in Emerging Markets (CCEM). https://ieeexplore.ieee.org/stamp/stamp.jsp?tp=&arnumber=7819669 (Year: 2016). |
| No stated author; Downdetector; 2020; retrieved from the Internet https://web.archive.org/web/20201226001244/https://downdetector.com/; pp. 1-8, as printed. (Year: 2020). |
| No stated author; How to Run a Ping Test (Windows) 2020; retrieved from the Internet https://web.archive.org/web/20200811194856/https://support.shaw.ca/t5/internet-articles/how-to-run-a-ping-test-windows/ta-p/6677; pp. 1-6 as printed. (Year: 2020). |
| No stated author; IsItoownRightNow; 2020; retrieved from the Internet https://web.archive.org/web/20201202121557/https:// www.isitdownrightnow.com/; pp. 1-2 as printed. (Year: 2020). |
| Sahil Suneja; Safe Inspection of Live Virtual Machines; IEEE; Year:2017; pp. 97-111. |
| Shuvo, Arfatul Mowla et al. Storage Efficient Data Security Model for Distributed Cloud Storage. 2020 IEEE 8th R10 Humanitarian Technology Conference (R10-HTC). https://ieeexplore.ieee.org/stamp/stamp.jsp?tp=&arnumber=9356962 (Year: 2020). |
| Siqi Ma; Certified Copy? Understanding Security Risks of Wi-Fi Hotspot based Android Data Clone Services; ACM; Year: 2021; pp. 320-331. |
| Written Opinion of the International Searching Authority for PCT Application No. PCT/IB2022/060940 dated Feb. 1, 2023. The International Bureau of WIPO. |
| Written Opinion of the Searching Authority for PCT/IB2023/050848, dated May 9, 2023. International Bureau of WIPO. |
| Written Opinion of the Searching Authority of PCT/IB2023/058074, dated Nov. 20, 2023. Searching Authority United States Patent and Trademark Office, Alexandria, Virginia. |
| Zhang et al. BMC Bioinformatics 2014. “On finding bicliques in bipartite graphs: a novel algorithm and its application to the integration of diverse biological data types”. http://www.biomedcentral.com/1471-2105/15/110. |
| Chang, Bing et al. MobiCeal: Towards Secure and Practical Plausibly Deniable Encryption on Mobile Devices. 2018 48th Annual IEEE/IFIP International Conference on Dependable Systems and Networks (DSN). https://ieeexplore.ieee.org/stamp/stamp.jsp?tp= &arnumber=8416506 (Year: 2018). |
| Islam, Md Shihabul et al. Secure Real-Time Heterogeneous IoT Data Management System. 2019 First IEEE International Conference on Trust, Privacy and Security in Intelligent Systems and Applications (TPS-ISA). https://ieeexplore.ieee.org/stamp/ stamp.jsp?tp=&arnumber=9014355 (Year: 2019). |
| Safaryan, Olga A et al. Cryptographic Algorithm Implementation for Data Encryption in DBMS MS SQL Server. 2020 IEEE East-West Design & Test Symposium (EWDTS). https://ieeexplore.ieee.org/stamp/stamp.jsp?tp=&arnumber=9224775 (Year: 2020). |
| Wassermann, Sarah et al. ViCrypt to the Rescue: Real-Time, Machine-Learning-Driven Video-QoE Monitoring for Encrypted Streaming Traffic. IEEE Transactions on Network and Service Management, vol. 17, Issue: 4. https://ieeexplore.ieee.org/stamp/ stamp.jsp?tp=&arnumber=9250645 (Year: 2020). |
| Number | Date | Country | |
|---|---|---|---|
| 20230418931 A1 | Dec 2023 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 17664508 | May 2022 | US |
| Child | 18456942 | US |
