US12219048B1

US12219048B1 - Techniques for encrypted disk cybersecurity inspection utilizing disk cloning

Info

Publication number: US12219048B1
Application number: US18/481,091
Authority: US
Inventors: Daniel Hershko Shemesh; Yarin MIRAN; Roy Reznik; Ami Luttwak; Yinon COSTICA; Yaniv Shaked; Eyal Moscovici
Original assignee: Wiz Inc
Current assignee: Wiz Inc
Priority date: 2021-12-27
Filing date: 2023-10-04
Publication date: 2025-02-04
Anticipated expiration: 2042-05-23
Also published as: US20250088349A1

Abstract

A system and method for inspecting encrypted disks for a cybersecurity object using a generic key is disclosed. The method includes: detecting an encrypted disk in a cloud computing environment, the cloud computing environment including a security policy service; authorizing a key policy on the security policy service for a default key of an inspector account, wherein the key policy is a policy authorized to decrypt the encrypted disk; generating a second encrypted disk based on the encrypted disk; inspecting the second encrypted disk for a cybersecurity object with the default key; and releasing a resource allocated to the second encrypted disk in response to completing the inspection.

Description

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation in part of U.S. Non-Provisional patent application Ser. No. 17/664,508 filed on May 23, 2022, U.S. Non-Provisional patent application Ser. No. 18/146,074, filed Dec. 23, 2022, and U.S. Non-Provisional patent application Ser. No. 18/146,076, filed Dec. 23, 2022. The Ser. Nos. 18/146,074 and 18/146,076 claim priority from U.S. Provisional Patent Application No. 63/266,031 filed on Dec. 27, 2021, all contents of which are hereby incorporated by reference.

TECHNICAL FIELD

The present disclosure relates generally to cybersecurity, and specifically to inspection of encrypted disks in an agentless manner for cybersecurity objects.

BACKGROUND

Cybersecurity threats are ever present in cloud computing environments, and often leave traces, indicators, and the like, on a disk, storage space, memory, etc., of the workload with which they are associated. For example, a cybersecurity threat can be a misconfiguration, a vulnerability, an exposure, a weak secret, an exposed password, an out of date software application, and the like.

Scanning for cybersecurity threats in a cloud computing environment often includes scanning storage, disks, and the like, for such cybersecurity objects. One method of protecting information includes encrypting storage resources, such as disks, so that even if they are accessed by an unauthorized party, the disk is not readable. However, such encrypted disks also cannot be scanned as a scanner requires an unencrypted volume to access. Encrypted disks present a challenge as decryption keys may not be readily available, and therefore their contents cannot be scanned.

Encryption of disks can be performed at application level, on a cloud platform level, or both. A scanner therefore cannot readily access the information on the disk, or determine what is present on it.

It would therefore be advantageous to provide a solution that would overcome the challenges noted above.

SUMMARY

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 detecting a first encrypted disk on a workload in a cloud computing environment, the first encrypted disk having an address in a cloud storage system; generating a key for an inspector account; generating a second encrypted disk with a reencrypt command utilizing the generated key for the inspector account; inspecting the second encrypted disk for a cybersecurity threat; and releasing a resource allocated to the second encrypted disk in response to completing the inspection. 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: generating an instruction to clone the first encrypted disk into the second encrypted disk using a reencrypt command with the generated key, the instruction when executed causes generation of a cloned disk descriptor, the cloned disk descriptor having a data field including the address of the first encrypted disk. Method may include: generating a pointer for the cloned disk descriptor of the second encrypted disk to an encryption key, the encryption key used for encrypting the first encrypted 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: determining that the first encrypted disk utilizes an application based encryption; and fetching a custom key for the application based encryption from a key vault management system. Method may include: decrypting the custom key, where the custom key is encrypted using a key-encryption-key. Method may include: determining that the first encrypted disk is encrypted based on metadata associated with the first encrypted disk. 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: detect a first encrypted disk on a workload in a cloud computing environment, the first encrypted disk having an address in a cloud storage system generate a key for an inspector account generate a second encrypted disk with a reencrypt command utilizing the generated key for the inspector account inspect the second encrypted disk for a cybersecurity threat; and release a resource allocated to the second encrypted disk in response to completing the inspection. 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: detect a first encrypted disk on a workload in a cloud computing environment, the first encrypted disk having an address in a cloud storage system. System may in addition generate a key for an inspector account. System may moreover generate a second encrypted disk with a reencrypt command utilizing the generated key for the inspector account. System may also inspect the second encrypted disk for a cybersecurity threat. System may furthermore release a resource allocated to the second encrypted disk in response to completing the inspection. 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: generate an instruction to clone the first encrypted disk into the second encrypted disk using a reencrypt command with the generated key, the instruction when executed causes generation of a cloned disk descriptor, the cloned disk descriptor having a data field including the address of the first encrypted 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 of the second encrypted disk to an encryption key, the encryption key used for encrypting the first encrypted 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: determine that the first encrypted disk utilizes an application based encryption; and fetch a custom key for the application based encryption from a key vault management system. System where the memory contains further instructions which when executed by the processing circuitry further configure the system to: decrypt the custom key, where the custom key is encrypted using a key-encryption-key. System where the memory contains further instructions which when executed by the processing circuitry further configure the system to: determine that the first encrypted disk is encrypted based on metadata associated with the first encrypted disk. Implementations of the described techniques may include hardware, a method or process, or a computer tangible medium.

BRIEF DESCRIPTION OF THE DRAWINGS

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.

FIG. 1 is an example schematic illustration of a network diagram of a production cloud environment and an inspecting cloud environment, utilized to describe an embodiment.

FIG. 2 is an example flowchart of a method for inspecting encrypted disks of workloads in a cloud environment, implemented according to an embodiment.

FIG. 3 is an example of a flowchart of a method for disk decryption utilizing a custom key for inspecting a disk for a cybersecurity object, implemented in accordance with an embodiment.

FIG. 4 is an example flowchart of a method for disk decryption utilizing a default key for detecting cybersecurity objects, implemented in accordance with an embodiment.

FIG. 5 is an example diagram of a virtual machine and a cloned disk thereof, utilized to describe an embodiment.

FIG. 6 is an example flowchart of a method for generating a disk clone of a virtual instance for vulnerability inspection according to an embodiment.

FIG. 7 is an example schematic diagram of an inspector according to an embodiment.

DETAILED DESCRIPTION

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.

FIG. 1 is an example schematic illustration of a network diagram 100 of a production cloud environment and an inspecting cloud environment, utilized to describe an embodiment. In an embodiment, a production cloud environment 102 includes a plurality of principals, such as user account 120, and a plurality of virtual resources, such as virtual workload 110. In some embodiments, a cloud environment is implemented utilizing a cloud computing infrastructure, such as Amazon® Web Services (AWS), Microsoft® Azure, or Google® Cloud Platform (GCP). Storage may be implemented, for example using S3 in AWS.

In an embodiment, a virtual resource is a cloud entity which provides a service, access to a service, provisioning of hardware, and the like, such as a virtual machine, a software container, a serverless function, and the like. In certain embodiments, a principal is a cloud entity which is authorized to act on a resource. For example, according to an embodiment, a principal is a user account, a service account, a role, a combination thereof, and the like.

In some embodiments, the virtual workload 110 is connected a storage disk, a plurality of storage disks, and the like, such as storage disks 112-1 through 112-N, where ‘N’ is an integer having a value of ‘2’ or greater. In some embodiments, the storage disk is provisioned as a virtual disk, as a block address on a block storage, and the like. For example, a block storage is a Simple Storage Service (S3®), according to an embodiment.

In an embodiment, a user account 120 includes unique identifiers, such as email address, username, password, combinations thereof, and the like. A user account is managed by an identity and access management (IAM) service in a cloud environment, according to an embodiment. The IAM service further controls (i.e., defines authorizations, policies, rules, and the like, for) user groups, user roles, permissions, service accounts, and the like, in some embodiments.

In some embodiments an inspector account 130 is deployed in the production environment 102, and is implemented, for example as a user account, a service account, and the like. The inspector account is authorized to communicate with various components of the cloud environment 102 and further communicate with an inspecting cloud environment 104, according to some embodiments.

In certain embodiments, the inspector account 130 is configured to communicate with a key management service (KMS) 140. The KMS 140 is implemented as a virtual workload, a plurality of virtual workloads, and the like, in the production cloud environment 102, according to an embodiment. In some embodiments the KMS 140 is deployed on the cloud computing infrastructure on which the production environment 102 is deployed.

A KMS 140 is configured to store therein keys which are used to access encrypted resources in the production cloud environment 102, such as encrypted disks, encrypted files, and the like, according to an embodiment. The KMS 140 further includes a security policy engine 142, which is configured to associate a security policy with at least a portion of the keys stored in the KMS 140, according to an embodiment. In certain embodiments, a security policy indicates what user accounts are authorized to use a key managed by the KMS 140.

In an embodiment, the inspecting cloud environment 104 is configured to receive information from the production cloud environment 102 and is further configured to detect cybersecurity risks in the production cloud environment 102. In some embodiments, the inspecting cloud environment 104 includes a plurality of inspectors, such as inspector 150, which are each configured to detect a cybersecurity object. A cybersecurity object is, according to an embodiment, a secret, an application, a key, a certificate, a malware signature or object, a password, a combination thereof, and the like.

In certain embodiments, the inspector 150 is implemented as a virtual workload, such as a serverless function, deployed in the inspecting cloud environment 104. An inspector 150 is configured to receive information originating from the cloud production environment 102, in some embodiments, and is further configured to inspect the information to discover predefined data objects (i.e., cybersecurity objects) therein.

In an embodiment, the inspecting cloud environment 104 further includes a software container cluster, such as software container cluster 160. The software container cluster 160 is implemented for example utilizing a Kubernetes® (stylized as K8s) application, according to an embodiment. In certain embodiments, each cluster 160 includes a plurality of nodes.

For example, in an embodiment, an inspectable disk is generated based on the disk 112-1 in order to inspect the contents of the disk 112-1. In an embodiment, the inspectable disk is generated based on a snapshot, a clone, a copy, a combination thereof, and the like, of the disk 112-1. In certain embodiments, access to the inspectable disk is provided to the inspector 150 via the inspector account 130. For example, the inspector 150 is configured, in an embodiment, to utilize a service account (e.g., the inspector account 130) to access the inspectable disk and perform operations thereon, such as a read operation to access the contents of the inspectable disk.

In an embodiment, the software container cluster 160 is configured to provision a storage resource attached to a container, for example as a volume which is generated based on the inspectable disk. In certain embodiments, an inspector 150 is configured to access to the volume, and inspect the volume for a cybersecurity object. In an embodiment a plurality of inspectors are configured to each access the volume generated from the inspectable disk. Inspecting the inspectable disk in place of the disk 112-1 in the production environment allows the production environment to continue its operation with minimal interference, while inspecting the contents of the disk 112-1 without disrupting operation in the production environment.

FIG. 2 is an example flowchart 200 of a method for inspecting encrypted disks of workloads in a cloud environment, implemented according to an embodiment. In some embodiments, generating an inspectable disk based on a snapshot, copy, clone, combination thereof, and the like, of an encrypted disk will result in an inspectable disk which is not readable without a corresponding key.

It is beneficial for the inspecting cloud environment to be able to inspect such encrypted disks. In an embodiment, encryption of the disk is provided at the cloud level, application level, a combination thereof, and the like.

While some embodiments illustrate user of cloud managed encryption in AWS, and application level encryption in Azure, it should be readily apparent that the teachings herein can be applied to other cloud infrastructures with appropriate adjustments.

At S210, an encrypted disk is selected for inspection. In an embodiment, the encrypted disk is associated with a virtual workload, for example by provisioning a storage resource to the virtual workload. In an embodiment, a virtual workload is, for example, a virtual machine, a serverless function, a software container, and the like. In an embodiment, an inspection account (i.e., a service account) is utilized in determining that a disk is encrypted in a production cloud environment.

For example, in an embodiment a service account is authorized to access a disk, access metadata of a storage disk, access a storage provisioning system, and the like, to determine if a disk is an encrypted disk. In an embodiment, an encrypted disk includes metadata which indicates that the disk is an encrypted disk.

At S220, a check is performed to determine a level of encryption. In an embodiment, a disk is encrypted at application level, encrypted at cloud level, a combination thereof, and the like. In an embodiment, cloud level encryption (also referred to as cloud managed encryption) includes utilizing a key of a Key Management System (KMS) to encrypt a disk. In an embodiment, if the disk is encrypted at the application level execution continues at S230.

In some embodiments, if the disk is encrypted using cloud managed encryption execution continues at S240. In an embodiment, a disk may be encrypted utilizing one or more methods of cloud managed encryption and application level encryption. The methods for accessing such disks may be used consecutively, until a fully decrypted disk is accessible.

At S230, a check is performed to determine a key type. In an embodiment, a key type is a default key, a custom key, and the like. For example, a KMS in AWS supports two types of keys. The first type is an Elastic Block Store (EBS) default key, and the second type is a custom key. A policy associated with the default key cannot be changed, while for a custom key the policy can be configured, and reconfigured. In an embodiment, if the key is a custom key, execution continues at S260. In an embodiment, if the key is a default key, execution continues at S270.

At S240, a key is fetched from the key vault. For example, in an embodiment, Azure Key Vault is utilized as a KMS, implemented in Azure® cloud environments. At an application level encryption, a disk may be encrypted using Bitlocker (for Windows® operating systems), Cryptoluks (for Linux operating systems), and like, in some embodiments. An inspector account is authorized to fetch keys from a key vault, according to an embodiment. In certain embodiments, a key is a KEK (key encryption key), meaning that the key is encrypted using another asymmetric encryption, and this needs to be decrypted as well.

At S250, the disk is decrypted. In an embodiment the disk is decrypted using the key fetched from the key vault. In some embodiments, an inspectable disk is generated from the decrypted disk, and access thereto is provided to an inspecting cloud environment, where the inspectable disk is inspected for cybersecurity objects. In an embodiment, a disk is encrypted at application level utilizing based on the operating system, for example Microsoft® Windows, or Linux.

Linux disks utilize Cryptoluks, which, in an embodiment, contains two partitions, a first partition which is encrypted and a second partition which is plaintext. The plaintext partition is mounted in the inspecting cloud environment, according to an embodiment. In some embodiments, the plaintext partition includes a file named ‘osluksheader’ which appears in the ‘luks’ directory. In an embodiment, an inspector is configured to execute a decrypt command, for example:

sudo cryptsetup open/dev/<encrypted-device> <name>- - header=/<mountpoint>/luks/osluksheader

When prompted for a password, the passphrase (i.e., key) is provided after decoding the base64 through the pipe connected to the stdin. The result is a readable disk which is mountable using the device mapper, for example:

mount/dev/mapper/<name> <mount point>

In an embodiment the disk is mounted, for example on a volume which is provisioned in an inspection cluster. In certain embodiments, an inspector is configured to search the disk for data objects (e.g., cybersecurity objects) which are utilized to assess security risks and map the disk, its contents, the corresponding workload, a combination thereof, and the like, to a security graph.

In an embodiment utilizing the Microsoft Windows operating system, Windows encrypts disks using Bitlocker, a proprietary Microsoft OS encryption feature. Decrypting a Bitlocker encrypted disk includes, in an embodiment, setting the decoded base64 key from the keyvaults on the disk <secret-file.dat>. Decryption includes, according to an embodiment, executing the following command:

do dislocker/dev/<encrypted-device> -f <secret-file.bek> - - /media/<unencrypted-device>

In an embodiment, initiating execution of the command is performed by the inspector account. A decrypted disk is mounted, according to an embodiment, by initiating execution of the following instruction:

mount/media/<unencrypted-device>/dislocker-file/<mount-point>

In an embodiment, the instruction is executed by a control plane of a software container cluster in an inspection environment. A mounted disk, for example on a volume which is provisioned in an inspection software container cluster, is inspected for cybersecurity objects. In some embodiments, the disk, its contents, any detected cybersecurity object, and a corresponding workload, are represented on a security graph.

At S260, the disk is decrypted using the custom key. In some embodiments, decryption utilizing a custom key is described in more detail with respect to FIG. 3 .

At S270, the disk is decrypted using the default key. Decryption utilizing a default key is described in more detail with respect to FIG. 4 .

FIG. 3 is an example of a flowchart 300 of a method for disk decryption utilizing a custom key for inspecting a disk for a cybersecurity object, implemented in accordance with an embodiment.

At S310, a key policy is attached to a custom key. The custom key is used for decrypting an encrypted disk in a cloud computing environment. In an embodiment, AWS KMS is used in an AWS cloud environment. A kms:PutKeyPolicy instruction is set to provide cross-account permissions, allowing an inspector account access to the required decryption keys, according to an embodiment.

In certain embodiments, the KMS is configured to provide certain instructions (such as DecribeKey, CreateGrant, GenerateDataKey, ReEncrypt, Decrypt, etc.) only to keys in the KMS which have a tag corresponding to permissions granted to the inspector account.

At S320, the encrypted disk is decrypted. In an embodiment, the decrypted disk is utilized in generating an inspectable disk. In some embodiments, the encrypted disk is decrypted by executing an instruction initiated by an inspector account utilizing the decryption key accessed from the KMS, access to which was previously provided to the inspector account.

At S330, an inspectable disk is generated based on the decrypted disk. In certain embodiments, generating an inspectable disk includes generating a clone, a copy, a snapshot, and the like, based on the decrypted disk. In an embodiment the instruction for generating the inspectable disk is initiated by the inspector account.

At S340, access to the inspectable disk is provided to an inspector. In an embodiment, providing access to an inspector includes providing access to the inspectable disk to a service account (e.g., inspector account) which is configured to be assumed by an inspector workload.

In an embodiment, providing access includes sending a copy, a pointer of a clone, a snapshot, and the like, from the inspector account to the inspecting environment over a secure communication channel, such as a secure shell (SSH) communication.

At S350, a volume is generated from the inspectable disk. In an embodiment, a software container cluster is configured to provision a storage, into which a volume is generated based on the inspectable disk.

At S360, an instruction is generated to inspect the volume. In an embodiment, the volume is inspected for cybersecurity objects. In some embodiments, inspection includes searching the volume for files, text, regular expressions (regex), secrets, keys, application identifiers, malware signatures, virtual workloads, misconfigurations, combinations thereof, and the like.

FIG. 4 is an example flowchart 400 of a method for disk decryption utilizing a default key for detecting cybersecurity objects, implemented in accordance with an embodiment. In certain cloud infrastructures, such as AWS, default keys do not support changing of an attached security policy.

At S410, a key is generated for an inspector account. In an embodiment, the key is generated to allow cross account access, with permissions for the inspector account. For example, an encrypted disk is selected, and a key is generated for the inspector account, to allow the inspector account to access the encrypted disk, according to an embodiment. In some embodiments, the inspector account is a service account which is configured to be assumed by an inspector workload.

At S420, a snapshot is generated of the encrypted disk. In an embodiment, generating the snapshot is performed based on executing an instruction initiated by an inspector account. In certain embodiments, the snapshot is a block-based copy of the encrypted disk at a particular point in time.

At S430, the snapshot is copied with a reencrypt command. Copying a snapshot includes, in an embodiment, executing a CopySnapshot instruction with a ReEncrypt instruction, where reencryption is performed with the generated key. In an embodiment, the instructions are provided by the inspector account, which has kms:CreateGrant and kms:ReEncryptFrom permissions from the KMS.

At S440, access is provided to the copied snapshot. In an embodiment, access is provided to an inspecting cloud environment, such as the inspecting cloud environment 104 of FIG. 1 above, and specifically to an inspector, for example by providing authorization to an inspector account to access the copied snapshot. In an embodiment, the copied snapshot is decrypted using the generated key for the inspector account. The key is provided to the inspector account. according to some embodiments.

At S450, a volume is generated from the copied snapshot. In an embodiment, a software container cluster is configured to provision a storage space, into which a volume is generated based on the copied snapshot of the decrypted disk.

At S460, the generated volume is inspected for a cybersecurity object. In an embodiment, inspection includes searching the volume for a file, a text, a regular expression (regex), a secret, a key, a certificate, a virtual workload, a combination thereof, and the like.

FIG. 5 is an example diagram 500 of a virtual machine 510 and a cloned disk thereof, utilized to describe an embodiment. While an Azure® cloud computing infrastructure is discussed here, it should be understood that the teachings herein apply equally to other cloud computing infrastructures which offer equal functionality. The VM 510 includes a plurality of disks allocated to the VM 510. The VM 510 may be deployed only with an OS disk, with an OS disk and a plurality of data disks, and so on.

In this example embodiment, the plurality of disks includes an operating system (OS) disk 502, an optional temporary disk 504, and at least a data disk 506. The OS disk 502 includes a preinstalled OS, such as Microsoft® Windows, or Linux®. The preinstalled OS is in a boot volume of the OS disk 502. The optional temporary disk 504 may be used for storing temporary data, such as page files, swap files, and the like. The data disk 506 may be used for storing an application, application code, libraries, binaries, application data, and the like. In an embodiment, a plurality of data disks 506 may be allocated to the VM 510. In some configurations, a disk of the plurality of disks may be encrypted. For example, the OS disk 502, and the data disk 506 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 510 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 510 which results in allocation of a disk. The hardware resources are provisioned from cloud storage pages 520 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 520 are Azure page blobs. A page blob is a collection of pages, each page having a predetermined size. For example, the predetermined size may be 512-bytes per page.

A disk clone 512 (also referred to as cloned disk 512) includes a disk descriptor which includes a reference to an address of a disk of the VM 510. In certain cloud computing infrastructures, when a disk is cloned, a pointer, such as pointer 516, 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 510 which points to the data disk 506, and generating the pointer 516 for the cloned VM 510 to point to the data disk 206. In certain embodiments where a disk is encrypted, a pointer may be generated for the cloned disk 512 to the encryption key.

In an embodiment, the cloning process generates the disk clone 512 as a background process. This is possible through the utilization of diffs. A diff is an additional content that includes the difference between a particular content at one point in time (e.g., when the original disk was cloned) and at a second, later, point in time. Thus, the VM 510 may access the data disk 506 and any diffs generated, or committed, after the disk clone 512 is generated, whereas the disk clone 512 may access only the content of the original data disk 506, and cannot access any diffs generated since.

The cloned disk 512 may then be inspected by an inspector, such as the inspector 150 of the inspection environment 104 of FIG. 1 above. In some embodiments, a cloud computing infrastructure may be divided into regions, corresponding to geographic regions. In such embodiments, cloning a disk may be possible only if the disk clone is in the same region as the original disk from which the clone is generated. In an embodiment an inspection controller is configured to determine if inspecting a virtual instance requires generating a disk clone or a snapshot. In an embodiment, the determination is performed based on the geographic location of the VM 510, an intended geographic location into which a disk of the VM 510 is cloned, a geographic location of the inspection environment, a number of disks allocated to the virtual instance, or any combination thereof.

By inspecting a cloned disk 512 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 512 is complete, the cloned disk 512 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 512 may be deleted to accomplish spinning down.

At S610, 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 an “original disk”). In some embodiments, the disk is represented as a node in the security graph, the node being connected to an 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 S620, 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 the 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, a cloning process may be initiated, otherwise a snapshot is generated, and inspection is performed on the generated snapshot.

At S630, 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 FIG. 1 , is provided with access to the cloned disk. For example, the cloning process may include generating an instruction which, when executed, configures the cloned disk to allow an inspector workload access thereto. The inspector may inspect the cloned disk for security objects, such as files, folders, and the like. A security object may be, for example, a password stored in plaintext, a password stored in cleartext, a certificate, and the like.

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

FIG. 7 is an example schematic diagram of an inspector 150 according to an embodiment. The inspector 150 includes a processing circuitry 710 coupled to a memory 720, a storage 730, and a network interface 740. In an embodiment, the components of the inspector 150 may be communicatively connected via a bus 750.

The processing circuitry 710 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 720 may be volatile (e.g., random access memory, etc.), non-volatile (e.g., read only memory, flash memory, etc.), or a combination thereof. In an embodiment, the memory 720 is an on-chip memory, an off-chip memory, a combination thereof, and the like. In certain embodiments, the memory 720 is a scratch-pad memory for the processing circuitry 710.

In one configuration, software for implementing one or more embodiments disclosed herein may be stored in the storage 730, in the memory 720, in a combination thereof, and the like. 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 710, cause the processing circuitry 710 to perform the various processes described herein.

The storage 730 is a magnetic storage, an optical storage, a solid-state storage, a combination thereof, and the like, and is realized, according to an embodiment, as a flash memory, as a hard-disk drive, or other memory technology, or any other medium which can be used to store the desired information.

The network interface 740 is configured to provide the inspector 150 with communication with, for example, the KMS 140, the container cluster 160, the security database 170, and the like.

It should be understood that the embodiments described herein are not limited to the specific architecture illustrated in FIG. 7 , and other architectures may be equally used without departing from the scope of the disclosed embodiments.

Furthermore, in certain embodiments other systems described herein may be implemented with the architecture illustrated in FIG. 7 . In other embodiments, other architectures may be equally used without departing from the scope of the disclosed embodiments.

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.

Claims

What is claimed is:

1. A method for inspecting encrypted disks using a default key for detecting a cybersecurity object, comprising:

detecting a first encrypted disk on a workload in a cloud computing environment, the first encrypted disk having an address in a cloud storage system;

generating a key for an inspector account that is distinct from any information of any account of any of one or more users that have access to the first encrypted disk;

generating a second encrypted disk with a reencrypt command utilizing the generated key for the inspector account such that the second encrypted disk is a clone of the first encrypted disk, the second encrypted disk including a cloned disk descriptor having a data field including an address of the first encrypted disk, and wherein the second encrypted disk becomes available for inspection substantially immediately upon creation and is not accessible at any time by any of the one or more users that have access to the first encrypted disk;

inspecting the second encrypted disk for a cybersecurity threat, wherein the first encrypted disk remains accessible to the one or more users that have access to the first encrypted disk while the inspecting is performed; and

releasing a resource allocated to the second encrypted disk in response to completing the inspection.

2. The method of claim 1, further comprising:

generating an instruction to clone the first encrypted disk into the second encrypted disk using a reencrypt command with the generated key, the instruction when executed causes generation of the cloned disk descriptor.

3. The method of claim 2, further comprising:

generating a pointer for the cloned disk descriptor of the second encrypted disk to an encryption key, the encryption key having been used for encrypting the first encrypted disk.

4. The method of claim 3, wherein the cloned disk descriptor includes a pointer to an address of a storage block in a managed storage of the cloud computing environment.

5. The method of claim 1, further comprising:

determining that the first encrypted disk utilizes an application based encryption; and

fetching a custom key for the application based encryption from a key vault management system.

6. The method of claim 5, further comprising:

decrypting the custom key, wherein the custom key is encrypted using a key-encryption-key.

7. The method of claim 1, further comprising:

determining that the first encrypted disk is encrypted based on metadata associated with the first encrypted disk.

8. A non-transitory computer-readable medium storing a set of instructions for inspecting encrypted disks using a default key for detecting a cybersecurity object, the set of instructions comprising:

one or more instructions that, when executed by one or more processors of a device, cause the device to:

detect a first encrypted disk on a workload in a cloud computing environment, the first encrypted disk having an address in a cloud storage system;

generate a key for an inspector account that is distinct from any information of any account of any of one or more users that have access to the first encrypted disk;

generate a second encrypted disk with a reencrypt command utilizing the generated key for the inspector account such that the second encrypted disk is a clone of the first encrypted disk, the second encrypted disk including a cloned disk descriptor having a data field including an address of the first encrypted disk, and wherein the second encrypted disk becomes available for inspection substantially immediately upon creation and is not accessible at any time by any of the one or more users that have access to the first encrypted disk;

inspect the second encrypted disk for a cybersecurity threat, wherein the first encrypted disk remains accessible to the one or more users that have access to the first encrypted disk while the inspecting is performed; and

release a resource allocated to the second encrypted disk in response to completing the inspection.

9. A system for inspecting encrypted disks using a default key for detecting a cybersecurity object comprising:

a processing circuitry; and

a memory, the memory containing instructions that, when executed by the processing circuitry, configure the system to:

10. The system of claim 9, wherein the memory contains further instructions which when executed by the processing circuitry further configure the system to:

generate an instruction to clone the first encrypted disk into the second encrypted disk using a reencrypt command with the generated key, the instruction when executed causes generation of the cloned disk descriptor.

11. The system of claim 10, wherein 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 of the second encrypted disk to an encryption key, the encryption key having been used for encrypting the first encrypted disk.

12. The system of claim 11, wherein the cloned disk descriptor includes a pointer to an address of a storage block in a managed storage of the cloud computing environment.

13. The system of claim 9, wherein the memory contains further instructions which when executed by the processing circuitry further configure the system to:

determine that the first encrypted disk utilizes an application based encryption; and

fetch a custom key for the application based encryption from a key vault management system.

14. The system of claim 13, wherein the memory contains further instructions which when executed by the processing circuitry further configure the system to:

decrypt the custom key, wherein the custom key is encrypted using a key-encryption-key.

15. The system of claim 9, wherein the memory contains further instructions which when executed by the processing circuitry further configure the system to:

determine that the first encrypted disk is encrypted based on metadata associated with the first encrypted disk.

16. The method of claim 1, further comprising:

providing the inspector account with a create-grant permission; and

providing the inspector account with a reencrypt-from permission.

17. The method of claim 16, wherein the second encrypted disk is generated based on the create-grant permission and the reencrypt-from permission.

18. The system of claim 9, wherein the memory contains further instructions which when executed by the processing circuitry further configure the system to:

provide the inspector account with a create-grant permission; and

provide the inspector account with a reencrypt-from permission.

19. The system of claim 18, wherein the second encrypted disk is generated based on the create-grant permission and the reencrypt-from permission.