Distributed catalog controller and method for data leakage prevention using distributed catalog

The AI-driven distributed catalog controller addresses the inefficiencies of conventional data leakage detection by monitoring input-output operations and generating alerts, effectively preventing data breaches and contamination in data centers by identifying at-risk data blocks and attackers, thus enhancing data security.

WO2024235435A1PCT designated stage expired Publication Date: 2024-11-21HUAWEI TECH CO LTD +1

Patent Information

Application Number
PCT/EP2023/062874
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Filing Date
2023-05-15
Publication Date
2024-11-21

AI Technical Summary

Technical Problem

Conventional data leakage detection methods in data centers often result in delayed detection, leading to increased damage due to inefficiencies and inaccuracies, failing to promptly and reliably prevent data contamination.

Method used

A distributed catalog controller utilizing artificial intelligence (AI) to monitor and track input-output operations, detect deviations from expected patterns, and generate alerts for potential data breaches, prioritizing responses based on data sensitivity and risk levels, thereby enhancing data security and reducing false threats.

Benefits of technology

The AI-powered distributed catalog controller efficiently and accurately detects data leakage, preventing potential data breaches and malware contamination, especially in BYOD environments, by identifying at-risk data blocks and attackers, and prioritizing protection measures effectively.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure EP2023062874_21112024_PF_FP_ABST
    Figure EP2023062874_21112024_PF_FP_ABST
Patent Text Reader

Abstract

A controller configured to operate in a data center system comprising one or a plurality of data nodes. The controller is further configured to receive a malware indication that malware is running on one of the one or plurality of data nodes, determine a data block that is at risk, determine an attacker of the data block at risk, determine zero or more other data blocks at risk, by determining other data blocks accessed by the attacker, and generate an alert indicating the data block at risk, the other data blocks at risk and the attacker. Moreover, the controller is a distributed catalog controller. As a result, the controller is configured to provide data protection efficiently and reliably, such as by detecting any potential sensitive data leakage using artificial intelligence (AI) catalog.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] DISTRIBUTED CATALOG CONTROLLER AND METHOD FOR DATA LEAKAGE PREVENTION USING DISTRIBUTED CATALOG

[0002] TECHNICAL FIELD

[0003] The present disclosure relates generally to the field of data security and more specifically, to a controller and a method to operate in a data center system comprising one or plurality of data nodes.

[0004] BACKGROUND

[0005] Generally, different organizations need to maintain data related to multiple subjects, customers, and potential customers. However, the corresponding data is required to be protected continuously to prevent any data loss, such as through a data leakage prevention (DLP) technique. The DLP refers to a practice that is used to detect and prevent data breaches, exfiltration as well as any unwanted destruction of the data. Therefore, different organizations use the DLP to comply with data privacy regulations and to secure corresponding data (e.g., personally identifiable information, intellectual property-related information, and the like) to prevent any data loss or data leakage. Moreover, the DLP is also used by different organizations to achieve data visibility and to provide a secure environment, such as by securing a mobile workforce, securing bring-your-own-device (BYOD) environments, securing cloud systems, and the like.

[0006] Typically, the type of data leakages is categorized as insider threats, extrusion by attackers, and unintentional (or negligent data exposure) that are responsible for the data leakage. The insider threats data leakage corresponds to an attack by compromising any privileged user account to access and transfer any personally identifiable information (PII) outside the organizational boundaries. Moreover, the extrusion by attackers corresponds to an attack that targets the sensitive data (e.g., the PII), such as by using phishing, malware, or by using code injection to gain access to the sensitive data. Furthermore, the unintentional (or negligent data exposure) data leakage corresponds to a data leak that occurs due to a lack of restrictions within the different organizations. Many attempts have been made to prevent such data leakage, such as by securing the data in motion, securing endpoints, securing data at rest, securing data in use, data identification, data leak detection, and the like. However, such attempts focus on the prevention of the data leakage, such as through firewalls, antivirus software by backing up the data and the like that continuously causes data contamination, which is not desirable. In certain scenarios, the conventional methods for detecting the data leakage may result in delayed detection, leading to an escalation in the damages caused by the data leakage. As a result, there exists a technical problem of how to detect the data leakage efficiently, accurately, and quickly to prevent the contamination of the data.

[0007] Therefore, in light of the foregoing discussion, there exists a need to overcome the aforementioned drawbacks associated with the conventional controllers.

[0008] SUMMARY

[0009] The present disclosure provides a controller and a method to operate in a data center system comprising one or plurality of data nodes. The present disclosure provides a solution to the existing problem of how to detect the data leakage efficiently, accurately, and quickly to prevent the contamination of the data. An objective of the present disclosure is to provide a solution that overcomes at least partially the problems encountered in the prior art and provides an improved controller and an improved method to operate in the data center system comprising one or plurality of data nodes to provide data leakage prevention by using artificial intelligence (Al) catalog.

[0010] One or more objectives of the present disclosure are achieved by the solutions provided in the enclosed independent claims. Advantageous implementations of the present disclosure are further defined in the dependent claims.

[0011] In one aspect, the present disclosure provides a controller configured to operate in a data center system comprising one or a plurality of data nodes. Moreover, the controller is further configured to receive a malware indication that malware is running on one of the one or plurality of data nodes, determine a data block that is at risk, determine an attacker of the data block at risk, determine zero or more other data blocks at risk, by determining other data blocks accessed by the attacker, and generate an alert indicating the data block at risk, the other data blocks at risk and the attacker. Moreover, the controller is a distributed catalog controller.

[0012] The controller is configured to provide data protection efficiently and reliably by detecting and protecting any sensitive data, such as the personally identifiable information (PII) leakage using artificial intelligence (Al) catalog. Furthermore, the controller is configured to track, monitor, and collect all input-output (I / O) operations (e.g., write and read I / O operations), such as by using a kernel driver or by using a user-space driver to detect the data leakage. Thereafter, the controller is configured to detect an unexpected pattern and further generate a list of sensitive objects, which are accessed by the attacker to indicate any potential threat that is further used to treat any potential data leakage. Moreover, the controller is configured to reduce any false threat by comparing the actual pattern with the expected pattern. In addition, the controller is configured to generate a report that includes a list of suspicious objects that includes the tags for the sensitive data, such as personally identifiable information (PII), any critical data related to an intellectual property, which can be further used to send an alert to a user. Moreover, the controller uses the Al catalog to determine all the occurrences of the suspicious files in the storage systems (e.g., using high-level view) and thereafter generate a report. The generated report includes suspicious score and corresponding risk level for each of the file (or object). The risk level depends upon the type of data, such as the sensitivity of the data, which is stored inside the file and the probability of data leakage. Thus, the controller is configured to prevent the data center system from any potential data breach, or malware contamination, and further detect the data leakage efficiently and reliably with reduced false detection to secure bring your own device (BYOD) environments.

[0013] In an implementation, the controller is further configured to receive the malware indication from a device. Moreover, the malware indication comprises an indication of a type of malware.

[0014] In a further implementation form, the controller is further configured to receive the malware indication from the device and the type of malware is ransomware.

[0015] In such an implementation, the indication of the ransomware by the controller is used to take necessary steps that are required to prevent such malware attacks and improve the overall data security of the data center system.

[0016] In a further implementation form, the device is a monitoring device arranged to monitor the one or a plurality of data nodes.

[0017] The monitoring of the one or plurality of data nodes by the device is used to detect the malware attack in the one or the plurality of data nodes, such as by determining any deviations from the expected I / O patterns and further indicates the controller about the corresponding malware, such as the ransomware.

[0018] In a further implementation, the controller is further configured to receive the expected I / O pattern by determining the expected I / O pattern based on previously received monitoring information. Moreover, the deviation comprises at least one indication of a deviating I / O operation, which is different from I / O operations in the expected pattern, which deviating I / O operation comprises an indication of the data block at risk and an indication of an entity accessing the data block at risk.

[0019] In such implementation, the determination of the deviation in the I / O pattern is used to determine the potential data breaches and data security threats that enable the data center system to detect any potential data breaches and data security threats that should be mitigated before any data loss.

[0020] In a further implementation form, the controller is further configured to determine the expected I / O pattern based on previously received monitoring of the information utilizing machine learning.

[0021] By utilizing the machine learning, the controller is configured to predict the expected I / O pattern that allows the controller to prevent the execution of the corresponding I / O operation that may include malware. As a result, the overall data security of the data center system is improved.

[0022] In a further implementation form, the controller is further configured to determine the attacker as the entity accessing the data block at risk in the monitoring information.

[0023] In such implementation, the controller is further configured to determine the attacker as the entity accessing the data block is at risk in the monitoring information to prevent the attacker from causing any damage to the data.

[0024] In a further implementation form, the controller is further configured to assign the priority tag based on the type of data in the data block at risk. Advantageously, the assignment of the priority tag allows the controller to prioritize the response and protection measures that are required to be taken in order to protect the data accordingly. As a result, the overall data security of the data center system is improved.

[0025] In another aspect, the present disclosure provides a method for use in a data center system comprising one or a plurality of data nodes. Moreover, the method comprises receiving a malware indication that malware is running on one of the one or plurality of data nodes, determining a data block that is at risk, determining an attacker of the data block at risk, determining zero or more other data blocks at risk, by determining other data blocks accessed by the attacker, and generating an alert indicating the data block at risk, the other data blocks at risk and the attacker, wherein the method is executed by a controller.

[0026] The method achieves all the advantages and technical effects of the controller of the present disclosure.

[0027] It is to be appreciated that all the aforementioned implementation forms can be combined.

[0028] It has to be noted that all devices, elements, circuitry, units, and means described in the present application could be implemented in the software or hardware elements or any kind of combination thereof. All steps which are performed by the various entities described in the present application as well as the functionalities described to be performed by the various entities are intended to mean that the respective entity is adapted to or configured to perform the respective steps and functionalities. Even if, in the following description of specific embodiments, a specific functionality or step to be performed by external entities is not reflected in the description of a specific detailed element of that entity which performs that specific step or functionality, it should be clear for a skilled person that these methods and functionalities can be implemented in respective software or hardware elements or any kind of combination thereof. It will be appreciated that features of the present disclosure are susceptible to being combined in various combinations without departing from the scope of the present disclosure as defined by the appended claims.

[0029] Additional aspects, advantages, features, and objects of the present disclosure would be made apparent from the drawings and the detailed description of the illustrative implementations construed in conjunction with the appended claims that follow. BRIEF DESCRIPTION OF THE DRAWINGS

[0030] The summary above, as well as the following detailed description of illustrative embodiments, is better understood when read in conjunction with the appended drawings. For the purpose of illustrating the present disclosure, exemplary constructions of the disclosure are shown in the drawings. However, the present disclosure is not limited to specific methods and instrumentalities disclosed herein. Moreover, those in the art will understand that the drawings are not to scale. Wherever possible, like elements have been indicated by identical numbers.

[0031] Embodiments of the present disclosure will now be described, by way of example only, with reference to the following diagrams wherein:

[0032] FIG. 1 is a block diagram that depicts a controller configured to operate in a data center system, in accordance with an embodiment of the present disclosure;

[0033] FIG. 2 is a flowchart of a method for use in a data center system, in accordance with an embodiment of the present disclosure; and

[0034] FIG. 3 is an exemplary diagram that depicts a system architecture for malware indication, in accordance with an embodiment of the present disclosure.

[0035] In the accompanying drawings, an underlined number is employed to represent an item over which the underlined number is positioned or an item to which the underlined number is adjacent. A non-underlined number relates to an item identified by a line linking the nonunderlined number to the item. When a number is non-underlined and accompanied by an associated arrow, the non-underlined number is used to identify a general item at which the arrow is pointing.

[0036] DETAILED DESCRIPTION OF EMBODIMENTS

[0037] The following detailed description illustrates embodiments of the present disclosure and ways in which they can be implemented. Although some modes of carrying out the present disclosure have been disclosed, those skilled in the art would recognize that other embodiments for carrying out or practicing the present disclosure are also possible.

[0038] The following detailed description illustrates embodiments of the present disclosure and ways in which they can be implemented. Although some modes of carrying out the present disclosure have been disclosed, those skilled in the art would recognize that other embodiments for carrying out or practicing the present disclosure are also possible.

[0039] FIG. l is a block diagram that depicts a controller configured to operate in a data center system, in accordance with an embodiment of the present disclosure. With reference to FIG. 1, there is shown a block diagram 100 that depicts a controller 104 configured to operate in a data center system 102 including one or plurality of data nodes 106, such as a first data node 106A, a second data node 106B, up to nth data node 106N.

[0040] The controller 104 is configured to operate in the data center system 102. Examples of the controller 104 may include, but are not limited to, a microcontroller, a microprocessor, a central processing unit (CPU), a complex instruction set computing (CISC) processor, an applicationspecific integrated circuit (ASIC) processor, a reduced instruction set (RISC) processor, a very long instruction word (VLIW) processor, a data processing unit, and other processors or control circuitry.

[0041] In operation, the controller 104 is configured to receive a malware indication that malware is running on one of the one or plurality of data nodes 106. In an example, the controller 104 is configured to receive the malware indication that the malware is running on the first data node 106A. In another example, the controller 104 is configured to receive the malware indication that the malware is running on the second data node 106B. Similarly, the controller 104 is configured to receive the malware indication that the malware is running on the nth data node 106N. In an implementation, the controller 104 is configured to receive the malware indication from a device 108. In another implementation, the controller 104 is configured to receive the malware indication from any external system. Moreover, the malware indication includes an indication of a type of malware. The malware indication corresponds to an alert that is received by the controller 104 that enables the controller 104 to further take appropriate actions that are required to mitigate the risk of malware attack and prevent any data breaches. In such implementation, the type of malware is a ransomware. The ransomware corresponds to a malware that prevents a user from accessing the data, such as by encrypting the data. Thus, the indication of the ransomware by the controller 104 is used to take necessary steps that are required to prevent such attacks and improve the overall data security of the data center system 102. In an implementation, the device 108 is a monitoring device that is arranged to monitor the one or plurality of data nodes 106. The monitoring of the one or plurality of data nodes 106 by the device 108 is used to detect the malware attack in the one or plurality of data nodes 106 and further indicate the controller 104 about the corresponding malware, such as the ransomware. In such an implementation, the device 108 is one of the one or plurality of data nodes 106. For example, the first data node 106A from the one or plurality of data nodes is configured to transmit the malware indication to the controller 104 of the data center system 102. Similarly, the second data node 106B from the one or plurality of data nodes 106 is configured to transmit the malware indication to the controller 104 of the data center system 102. In another implementation, the monitoring device may correspond to a data node from another data center system without affecting the scope of the present disclosure as shown and described in detail in FIG. 3. As a result, the execution of the malware can be prevented that improves the overall data security of the data center system 102. In accordance with another embodiment, the controller 104 is further configured to receive the monitoring information from the monitored node. For example, the controller 104 is configured to receive the monitoring information from the first data node 106A. Similarly, the controller 104 is configured to receive the monitoring information from the second data node 106B, without affecting the scope of the present disclosure. Advantageously, the receiving of the monitoring information from the monitored node is used to detect any potential threat, such as by determining any deviation in the monitoring information and the like in the monitored node. As a result, the overall data security of the data center system 102 is improved.

[0042] In accordance with an embodiment, the controller 104 is configured to receive the malware indication by receiving monitoring information for a monitored node of the one or plurality of data nodes 106. Firstly, the device 108 is configured to monitor the one or plurality of data nodes 106 of the data center system 102. Thereafter, the device 108 is configured to transmit the monitoring information of the monitored node to the controller 104. For example, the device 108 (or the first data node 106A) is configured to transmit the malware indication by monitoring the second data node 106B from the one or plurality of data nodes 106 to the controller 104. Moreover, the monitoring information includes indicators of input / output (I / O) operations for the monitored node, receiving an expected VO pattern for the monitored node, and determining a deviation in the monitoring information compared to the expected I / O pattern. As a result, the indicators of the I / O operations, the expected I / O pattern, and the deviation in the monitoring information are used to mitigate the potential threats that can be prevented to improve the overall data security of the data center system 102. In accordance with an embodiment, the monitoring information includes metadata for the I / O operations and not content data of the I / O operations. In an example, the metadata for the I / O operations is updated from time to time based on the indicators of the I / O operations for the monitored node. Moreover, the metadata for the I / O operations is used to detect the malware, such as by determining any deviation in the I / O patterns. As a result, the potential malware is detected efficiently and accurately before execution to improve the overall data security of the data center system 102.

[0043] In accordance with an embodiment, the controller 104 is further configured to have a global scope of the data center system, by being configured to receive monitoring information from the one or plurality of data nodes 106. Advantageously the global scope of the data center system 102 allows the controller 104 to compare an actual I / O pattern and an expected I / O pattern efficiently and accurately. Hence, the false malware indications are detected efficiently and accurately. In an implementation, the controller 104 is further configured to receive the expected I / O pattern by determining the expected I / O pattern based on previously received monitoring information. The deviation includes at least one indication of a deviating I / O operation, which is different from I / O operations in the expected pattern, which deviating I / O operation includes an indication of the data block at risk and an indication of an entity accessing the data block at risk. The I / O operations in the expected pattern refer to an anticipated behaviour of the I / O operations that are anticipated based on the monitoring information by the controller 104 of the data center system 102. As a result, the controller 104 is configured to identify the potential data breaches and data security threats that enable the data center system 102 to further take appropriate actions that are required to prevent or mitigate such data breaches and data security threats. In another implementation, the controller 104 is further configured to determine the expected I / O pattern based on previously received monitoring of the information utilizing machine learning. In other words, controller 104 is configured to receive the monitoring information, such as from the device 108, the monitoring device, or the monitored node. Thereafter, the controller 104 is configured to determine the expected I / O pattern based on the corresponding monitoring information, such as by utilizing machine learning. For example, a machine learning model can be used to train the controller 104 that is configured to determine the expected I / O pattern. Therefore, by utilizing the machine learning, the controller 104 is configured to predict the expected I / O pattern that allows the controller 104 to prevent the execution of the corresponding I / O operation that may include malware. As a result, the overall data security of the data center system 102 is improved. In yet another implementation, the controller 104 is further configured to determine the deviation based on the monitoring information based on one or more of resource monitoring of the data nodes in the data center system 102, resource consumption changes over time, changes of data blocks on volumes compressed or not compressed, detected randomization patterns, volumes changes, size changes, change rate for a data block, the number of reads in a window time frame, block segments dispersion rate changes, and / or monitoring information history. In an example, the controller 104 is configured to determine the deviation based on the monitoring information based on the resource monitoring of the data nodes in the data center system 102. In another example, the controller 104 is configured to determine the deviation based on the monitoring information based on the resource consumption changes over time. In yet another example, the controller 104 is configured to determine the deviation based on the monitoring information based on the changes of data blocks on volumes compressed or not compressed. In another example, the controller 104 is configured to determine the deviation based on the detected randomization patterns or volume changes or size changes or change rate for a data block without affecting the scope of the present disclosure. Similarly, in another example, the controller 104 is configured to determine the deviation based on the number of reads in a window time frame. In yet another example, the controller 104 is configured to determine the deviation based on the block segment's dispersion rate changes, and / or monitoring information history.

[0044] In addition, the controller 104 is configured to determine the deviation based on the resource monitoring of the data nodes in the data center system 102 and the resource consumption changes over time. Similarly, in another example, the controller 104 is configured to determine the deviation based on the changes of data blocks on volumes compressed or not compressed and detected randomization patterns, volume changes, size changes, and change rates for a data block without affecting the scope of the present disclosure. In yet another example, the controller 104 is configured to determine the deviation based on the number of reads in a window time frame, block segments dispersion rate changes, and / or monitoring information history. As a result, the determination of the monitoring information is used to protect the data, such as the personally identifiable information (PII) of the data center system 102.

[0045] In an implementation, an artificial intelligence (Al) catalog service is used to determine the deviation based on the monitoring information that is used to further determine the data block at risk and the attacker. In an implementation, the Al catalog service refers to a service of unstructured data management that is used to provide a single central viewpoint to the entire enterprise storage. The Al catalog service runs different types of queries and performs analytics and supplies insight into the customer storage enterprise. Moreover, the Al catalog service is used to collect an information on the unstructured data from all types of sources, such as NAS, S3, Environment (VMs), and the like in the entire enterprise storage periodically, such as through collectors. In addition, the Al catalog service is used to collect data for resource monitoring of the data center system 102 and the one or plurality of data nodes 106 of the data center system 102. Furthermore, the Al catalog service is used to detect resource consumption changes over time, data blocks segments change on volumes compressed and not compressed, detect randomization patterns, dispersal on volumes changes, size changes, incremental filesystem scans with another file’s status like size, last access, compute the change rate, compute VO temperature across files by calculating the number of reads in a window time frame and the like. Thus, the overall data security of the data center system 102 is improved.

[0046] The controller 104 is further configured to determine a data block that is at risk. In other words, the controller 104 is configured to determine the data block at risk in order to protect the corresponding data block from the malware attack. In an implementation, the controller 104 is configured to determine the data block at risk by retrieving the data block at risk from the malware indication. The malware indication includes an indication of the data block at risk. In an example, the controller 104 is configured to determine the data block at risk through the malware indication that is obtained by receiving the monitoring information about the corresponding data block at risk. In another implementation, the controller 104 is further configured to determine the data block at risk by retrieving it from the deviation operation. The determination of the data block at risk through the malware indication is used to determine the data block that is at risk, such as the data block that shows any deviation from the expected pattern. As a result, the impact of the malware attack can be mitigated. In accordance with an embodiment, the controller 104 is further configured to determine a file that the data block at risk is part of to be a file at risk. For example, the controller 104 is configured to determine the file at risk from the malware indication or through a deviation operation. As a result, the overall data security of the data center system can be improved, such as by mitigating the risk of malware attacks.

[0047] Furthermore, the controller 104 is configured to determine an attacker of the data block at risk. The attacker of the data block at risk is determined by the controller 104 in order to identify and prevent the attacker from committing any potential data breach. In an implementation, the controller 104 is further configured to determine the attacker as the entity accessing the data block at risk in the monitoring information. In other words, the controller 104 is configured to receive the monitoring information, such as through the device 108 or the monitored node from the one or the plurality of data nodes 106 in order to determine the attacker as the entity accessing the data block at risk. As a result, the attacker can be prevented from causing any further damage to the data. In another implementation, the controller 104 is further configured to determine the attacker by retrieving the attacker from the malware indication that includes an indication of the attacker. In an example, the device 108 or the monitored node is configured to transmit the monitoring information that indicates about the attacker. As a result, the controller 104 is configured to prevent the attacker from causing any harm to the data center system 102.

[0048] The controller 104 is further configured to determine zero or more other data blocks at risk by determining other data blocks accessed by the attacker. The determination of the data blocks that are accessed by the attacker is used to determine the other data blocks that are at risk to protect the data blocks from any potential attack. In accordance with an embodiment, the controller 104 is further configured to determine the zero or more other data blocks at risk by generating a list of data blocks and assign a priority tag to the data blocks of the list. Firstly, the controller 104 is configured to determine the attacker of the data block at risk. Thereafter, the controller 104 is configured to determine the data blocks that are accessed by the attacker other than the determined data block at risk. For example, a first data block and a second data block are the data blocks that are determined by the controller 104 as the data blocks that are accessed by the attacker. Furthermore, the controller 104 is configured to generate the list of the data blocks that are accessed by the attacker. Finally, the controller 104 is configured to assign the priority tag to the data blocks of the generated list. In an implementation, the controller 104 is further configured to assign the priority tag based on the type of malware. For example, the controller 104 is configured to assign the priority tag based on the data blocks that are affected by the ransomware. Similarly, the controller 104 is configured to assign the priority tag based on the type of the malware. In another implementation, the controller 104 is further configured to assign the priority tag based on the type of data in the data block at risk. For example, if the data block includes sensitive information, in that case, the controller 104 is configured to assign a higher priority tag to the corresponding data block as compared to the data block with less sensitive information. As a result, the assignment of the priority tag allows the controller 104 to prioritize the response and protection measures that are required to protect the data accordingly. In yet another implementation, the controller 104 is further configured to assign the priority tag based on the attacker. The assignment of the priority tag based on the attacker is used to notify the controller 104 about any potential threat, which allows the controller 104 to take necessary actions to mitigate the risk and protect the data center system 102 from any damage.

[0049] The controller 104 is further configured to generate an alert indicating the data block at risk the other data blocks at risk and the attacker. In an example, the controller 104 is configured to generate an alert indicating the data block at risk an alert indicating the other data blocks at risk, and an alert indicating the attacker. The alert generated by the controller 104 is used to protect the data center system 102 from the potential threat, malware, and the data security breaches. Furthermore, the controller 104 is configured to take certain necessary actions that are required to be taken to protect the controller 104 from such potential threats, malware attacks and the data breaches. Moreover, the controller 104 is a distributed catalog controller. The distributed catalog controller includes an original master distributed catalog (i.e., the Al catalog service) that is used to maintain one or more local catalogues (e.g., Al catalogues) that are created when the master distributed catalog is accessed by users. In addition, the distributed catalog controller is configured to maintain a certain level of control over the Al catalog, allowing the distributed catalog controller to create local copies of the Al catalog. In an implementation, the controller 104 can be deployed inside the Al Catalog. In another implementation, the controller 104 can be deployed outside the Al Catalog as an additional service. In such an implementation, the controller 104 is configured to communicate with the Al Catalog by using application programming interface (API). As a result, the controller 104, which is the distributed catalog controller is used to provide the data leakage prevention by using the Al catalog.

[0050] The controller 104 is configured to provide data protection efficiently and reliably, such as by detecting any potential sensitive data leakage using artificial intelligence (Al) catalog. Furthermore, the controller 104 is configured to track, monitor, and collect all input-output (IO) operations (e.g., write and read IO operations), such as by using a kernel driver or by using a user-space driver to detect the data leakage. Thereafter, the controller 104 is configured to detect an unexpected pattern and further generate a list of sensitive objects, which are accessed by the attacker in order to indicate any potential threat that is further used to treat any potential data leakage. Moreover, the controller 104 is configured to reduce any false threat by comparing the actual pattern with the expected pattern. In addition, the controller 104 is configured to generate a report that includes a list of suspicious objects that includes the tags for the sensitive data, such as a personally identifiable information (PII), any critical data related to intellectual property, which can be further used to send an alert to a user. The controller 104 uses the Al catalog to determine all the occurrences of the suspicious files in the storage systems (e.g., using high-level view) and thereafter generates a report. Moreover, the generated report includes suspicious score and corresponding risk level for each of the file (or object). The risk level depends upon the type of data, such as the sensitivity of the data, which is stored inside the file and the probability of data leakage. Thus, the controller 104 is configured to prevent the data center system 102 from any potential data breach, or malware contamination and further detect the data leakage efficiently and reliably with reduced false detection in order to secure bring your own device (BYOD) environments.

[0051] FIG. 2 is a flowchart of a method for use in a data center system, in accordance with an embodiment of the present disclosure. With reference to FIG. 2, there is shown a flowchart of method 200 for use in the data center system 102 that includes the one or plurality of data nodes 106 (of FIG. 1), such as the first data node 106 A, the second data node 106B, and the Nth data node 106N. The method 200 includes steps 202 to 210.

[0052] In operation, the method 200 includes receiving a malware indication that malware is running on one of the one or plurality of data nodes 106, such as at step 202. In an example, the method 200 includes, receiving the malware indication that the malware is running on the first data node 106A. In another example, the method 200 includes, receiving the malware indication that the malware is running on the second data node 106B. Similarly, the method 200 includes, receiving the malware indication that the malware is running on the nth data node 106N. In an implementation, the method 200 includes, receiving the malware indication through the device 108. In another implementation, the method 200 includes, receiving the malware indication through the monitored node. As a result, the malware can be prevented before its execution. Furthermore, at step 204, the method 200 includes determining a data block that is at risk. In other words, the method 200 includes, determining the data block at risk in order to protect the corresponding data block from the malware attack. Furthermore, at step 206, the method 200 includes determining an attacker of the data block at risk. The attacker of the data block at risk is determined by the controller 104 in order to prevent the attacker from committing any potential data breach. At step 208, the method 200 includes determining zero or more other data blocks at risk, by determining other data blocks accessed by the attacker. The determination of the data blocks that are accessed by the attacker is used to determine the other data blocks that are at risk to protect the data blocks from any potential attack. At step 210, the method 200 includes generating an alert indicating the data block at risk, the other data blocks at risk, and the attacker. Moreover, the method 200 is executed by the controller 104. The alert generated by the controller 104 is used to protect the data center system 102 from the potential threat, malware, and the data security breaches. Furthermore, the controller 104 is configured to take certain necessary actions that are required to be taken to protect the data center system 102 from such potential threats, malware attacks, and the data breaches. Moreover, the method 200 is executed by a distributed catalog controller. The distributed catalog controller includes an original master distributed catalog (i.e., the Al catalog service) that is used to maintain and one or more local catalogues (e.g., Al catalogues) that are created when the master distributed catalog is accessed by users. In addition, the distributed catalog controller is configured to maintain a certain level of control over the Al catalog, allowing the distributed catalog controller to create local copies of the Al catalog. As a result, the controller 104, which is the distributed catalog controller is used to provide the data leakage prevention by using the Al catalog.

[0053] The method 200 is used to provide data protection efficiently and reliably, such as by detecting any potential sensitive data leakage using artificial intelligence (Al) catalog. Furthermore, the method 200 is used to track, monitor, and collect all input-output (IO) operations (e.g., write and read IO operations), such as by using a kernel driver or by using a user-space driver to detect the data leakage. Thereafter, the method 200 is used to detect an unexpected pattern and further generate a list of sensitive objects, which are accessed by the attacker in order to indicate any potential threat that is further used to treat any potential data leakage. Moreover, the method 200 is used to reduce any false threat by comparing the actual pattern with the expected pattern. In addition, the method 200 is used to generate a report that includes a list of suspicious objects that includes the tags for the sensitive data, such as a personally identifiable information (PII), and any critical data related to intellectual property, which can be further used to send an alert to a user. Thus, the method 200 is used to prevent the data center system 102 from any potential data breach, or malware contamination and further detect the data leakage efficiently and reliably with reduced false detection in order to secure bring your own device (BYOD) environments. The steps 202 to 210 are only illustrative, and other alternatives can also be provided where one or more steps are added, one or more steps are removed, or one or more steps are provided in a different sequence without departing from the scope of the claims herein.

[0054] There is provided a computer-readable medium including computer program instructions that, when executed by one or more processors, cause the distributed catalog controller system to execute the method 200. In an example, the instructions are implemented on the computer- readable media, which include, but are not limited to, Electrically Erasable Programmable Read-Only Memory (EEPROM), Random Access Memory (RAM), Read-Only Memory (ROM), Hard Disk Drive (HDD), Flash memory, a Secure Digital (SD) card, Solid-State Drive (SSD), a computer-readable storage medium, and / or CPU cache memory. In an example, the instructions are generated by a computer program, which is implemented in view of the method 200, and for use in implementing the method 200 in the distributed catalog controller system.

[0055] FIG. 3 is an exemplary diagram that depicts a system architecture for malware indication, in accordance with an embodiment of the present disclosure. FIG. 3 is described in conjunction with elements from FIG. 1. With reference to FIG. 3 there is shown an exemplary diagram 300 that depicts the processes that exist in a first data center system 302A up to the nth data center system 302N, such as the data center system 102 (of FIG. 1).

[0056] In an implementation scenario, a system architecture includes the first data center system 302A up to the nth data center system 302N. Each of the data center systems, such as the first data center system 302A up to the nth data center system 302N includes multiple collector components. For example, the first data center system 302A includes the one or plurality of data nodes, such as a first data node (i.e., a NAS) 304, a second data node 306 (i.e., S3), and the like. Similarly, the nth data center system 302N includes the one or plurality of data nodes, such as a first data node 308, a production ESX server, 310, a production MSSQL 312, a production oracle 314, and the like. Moreover, the one or plurality of data nodes is configured to track the I / O patterns and report any deviation to an Artificial intelligence (Al) catalog service 316. In addition, the Al catalog service 316 is used to track and record the I / O operations (i.e., write and read operations), access I / O patterns and trends for each of the one or plurality of data nodes 106, such as the first data node (i.e., a NAS) 304, the second data node 306 (i.e., S3) that are included in the first data center system 302A and the first data node 308, the production ESX server, 310, the production MSSQL 312, and the production oracle 314 that are included in the nth data center system 302N.

[0057] The Al catalog service 316 is used to record I / O behavior, such as a dispersion rate for each data block, I / O patterns, and the like by collecting corresponding data, such as through an internal collector 320. However, if any deviation from the expected I / O pattern is detected by the Al catalog service 316, in that case, the Al catalog service 316 is configured to add the corresponding I / O pattern in a suspected list along with all the attackers in order to trigger an alert, such as through Al service engine 318. For example, the controller 104 is configured to receive a malware indication that a ransomware is running on one of the one or plurality of data nodes 106. Furthermore, the controller 104 is configured to determine a data block, an attacker, and other data blocks that are at risk to further generate an alert indicating the data blocks, the other data blocks at risk and the attacker. As a result, each of the data center systems, such as the first data center system 302A up to the nth data center system 302N is used to provide data protection efficiently and reliably, such as by detecting any potential sensitive data leakage using artificial intelligence (Al) catalog. Hence, the overall data security of the corresponding data center system is improved.

[0058] Modifications to embodiments of the present disclosure described in the foregoing are possible without departing from the scope of the present disclosure as defined by the accompanying claims. Expressions such as "including", "comprising", "incorporating", "have", "is" used to describe, and claim the present disclosure are intended to be construed in a non-exclusive manner, namely allowing for items, components or elements not explicitly described also to be present. Reference to the singular is also to be construed to relate to the plural. The word "exemplary" is used herein to mean "serving as an example, instance or illustration". Any embodiment described as “exemplary” is not necessarily to be construed as preferred or advantageous over other embodiments or to exclude the incorporation of features from other embodiments. The word "optionally" is used herein to mean "is provided in some embodiments and not provided in other embodiments". It is appreciated that certain features of the present disclosure, which are, for clarity, described in the context of separate embodiments, may also be provided in combination in a single embodiment. Conversely, various features of the present disclosure, which are, for brevity, described in the context of a single embodiment, may also be provided separately or in any suitable combination or as suitable in any other described embodiment of the disclosure.

Claims

CLAIMS1. A controller (104) configured to operate in a data center system (102) comprising one or a plurality of data nodes (106), wherein the controller (104) is further configured to: receive a malware indication that malware is running on one of the one or plurality of data nodes (106), determine a data block that is at risk, determine an attacker of the data block at risk, determine zero or more other data blocks at risk, by determining other data blocks accessed by the attacker, and generate an alert indicating the data block at risk, the other data blocks at risk and the attacker, wherein the controller (104) is a distributed catalog controller.

2. The controller (104) according to claim 1, wherein the controller (104) is further configured to receive the malware indication from a device (108), wherein the malware indication comprises an indication of a type of malware.

3. The controller (104) according to claim 2, wherein the controller (104) is further configured to receive the malware indication from the device (108), wherein the type of malware is ransomware.

4. The controller (104) according to claim 2, wherein the device (108) is a monitoring device (108) arranged to monitor the one or plurality of data nodes (106).

5. The controller (104) according to claim 2, wherein the device (108) is one of the one or plurality of data nodes (106).

6. The controller (104) according to any of claims 2 to 5, wherein the controller (104) is further configured to determine the attacker by retrieving the attacker from the malware indication, wherein the malware indication comprises an indication of the attacker.

7. The controller (104) according to any of claims 2 to 5, wherein the controller (104) is further configured to determine the data block at risk by retrieving the data block at risk from the malware indication, wherein the malware indication comprises an indication of the data block at risk.

8. The controller (104) according to any preceding claim, wherein the controller (104) is further configured to receive the malware indication by receiving monitoring information for a monitored node of the one or plurality of data nodes (106), wherein the monitoring information comprises indicators of input / output, I / O, operations for the monitored node, receiving an expected I / O pattern for the monitored node, anddetermining a deviation in the monitoring information compared to the expected I / O pattern.

9. The controller (104) according to claim 8, wherein the controller (104) is further configured to receive the expected I / O pattern by determining the expected I / O pattern based on previously received monitoring information, wherein the deviation comprises at least one indication of a deviating I / O operation which is different from I / O operations in the expected pattern, which deviating I / O operation comprises an indication of the data block at risk and an indication of an entity accessing the data block at risk.

10. The controller (104) according to claim 9, wherein the controller (104) is further configured to determine the expected I / O pattern based on previously received monitoring information utilizing machine learning.

11. The controller (104) according to any of claims 8 to 10, wherein the controller (104) is further configured to determine the deviation based on the monitoring information based on one or more of: resource monitoring of the data nodes (106) in the data center, resource consumption changes over time, changes of data blocks on volumes compressed or not compressed, detected randomization patterns, volumes changes, size changes, change rate for a data block, the number of reads in a window time frame, block segments dispersion rate changes, and / or monitoring information history.

12. The controller (104) according to any of claims 8 to 11, wherein the monitoring information comprises metadata for the I / O operations, and not content data of the I / O operations.

13. The controller (104) according to any of claims 8 to 12, wherein the controller (104) is further configured to receive the monitoring information from the monitored node.

14. The controller (104) according to any of claims 8 to 13, wherein the controller (104) is further configured to determine the attacker as the entity accessing the data block at risk in the monitoring information.

15. The controller (104) according to any of claims 8 to 14, wherein the controller (104) is further configured to determine the data block at risk by retrieving it from the deviation operation.

16. The controller (104) according to any preceding claim, wherein the controller (104) is further configured to determine a file that the data block at risk is part of to be a file at risk.

17. The controller (104) according to any preceding claim, wherein the controller (104) is further configured to have a global scope of the data center system (102), by being configured to receive monitoring information from the one or plurality of data nodes (106).

18. The controller (104) according to any preceding claim, wherein the controller (104) is further configured to determine the zero or more other data blocks at risk by generating a list of data blocks, and to assign a priority tag to the data blocks of the list.

19. The controller (104) according to claim 18, wherein the controller (104) is further configured to assign the priority tag based on the type of malware.

20. The controller (104) according to claim 18 or 19, wherein the controller (104) is further configured to assign the priority tag based on the type of data in the data block at risk.

21. The controller (104) according to claim 18 or 20, wherein the controller (104) is further configured to assign the priority tag based on the attacker.

22. A method (200) for use in a data center system (102) comprising one or a plurality of data nodes (106), wherein the method (200) comprises: receiving a malware indication that malware is running on one of the one or plurality of data nodes (106), determining a data block that is at risk, determining an attacker of the data block at risk, determining zero or more other data blocks at risk, by determining other data blocks accessed by the attacker, and generating an alert indicating the data block at risk, the other data blocks at risk and the attacker, wherein the method (200) is executed by a distributed catalog controller.

23. A computer program product comprising program instructions for performing the method (200) according to claim 22, when executed by one or more processors in a distributed catalog controller system.

Citation Information

Patent Citations

  • Cross machine detection techniques

    EP3531327A1

  • System and method for insider threat detection

    US20130091539A1

  • Logical network topology analyzer

    US20170295068A1

  • Artificial intelligence detection of ransomware activity patterns on computer systems

    US20220398316A1

Cited By

  • Connection destination malignancy determination system, connection destination malignancy determination program, and connection destination malignancy determination method

    US12587547B2

  • Connection destination malignancy determination system, connection destination malignancy determination program, and connection destination malignancy determination method

    US20240333729A1