Risk information output device, information output system, risk information output method, and recording medium
US-2024414180-A1 · Dec 12, 2024 · US
US2019109870A1 · US · A1
| Field | Value |
|---|---|
| Publication number | US-2019109870-A1 |
| Application number | US-201816129644-A |
| Country | US |
| Kind code | A1 |
| Filing date | Sep 12, 2018 |
| Priority date | Sep 14, 2017 |
| Publication date | Apr 11, 2019 |
| Grant date | — |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
This application relates to ransomware detection and intelligent restore. Ransomware typically involves an I/O heavy process of encrypting data files and/or deleting or renaming the original files. Thus, ransomware attacks may be detected by analyzing the I/O activity in a given file system. When a potential ransomware attack is detected, a timestamp is recorded. If the client machine is indeed taken over by the ransomware attack, an intelligent restore operation can be performed such that the file system is automatically restored to a point in time prior to the infection by the ransomware attack using the recorded timestamp.
Opening claim text (preview).
What is claimed is: 1 . A computer-implemented method for detecting file activity anomalies, the method comprising: causing a copy of primary data associated with a client computing device to be stored in one or more secondary storage devices as part of secondary data associated with the client computing device; detecting a file activity anomaly based at least on one or more file system operations performed on the client computing device satisfying one or more threshold conditions associated with the client computing device; storing timestamp information associated with the one or more file system operations; in response to detecting the file activity anomaly, restoring, based at least on the timestamp information, at least some of the secondary data stored in the one or more computing devices onto one or more primary storage devices associated with the client computing device; and outputting a notification indicating at least the file activity anomaly. 2 . The computer-implemented method of claim 1 , further comprising: monitoring file system operations performed on the client computing device over a specific time period; determining a baseline count of file system operations performed on the client computing device over the specific time period; and determining, based at least on the baseline count, at least one threshold condition of the one or more threshold conditions. 3 . The computer-implemented method of claim 2 , wherein the baseline count is an average number of file system operations performed on the client computing device for each sub-period of a plurality of sub-periods within the specific time period. 4 . The computer-implemented method of claim 2 , further comprising determining the at least one threshold condition at least by multiplying the baseline count with a predetermined percentage value, wherein the predetermined percentage value is greater than 100 percent. 5 . The computer-implemented method of claim 2 , further comprising periodically determining whether a current count of file system operations satisfies the one or more threshold conditions for each of a plurality of time periods subsequent to the specific time period and each having a same length as the specific time period. 6 . The computer-implemented method of claim 1 , wherein the one or more file system operations comprise at least one of write operations, create operations, rename operations, or delete operations. 7 . The computer-implemented method of claim 1 , wherein the timestamp information specifies a first time at which a file system operation of the one or more file system operations that is performed earliest out of all of the one or more file system operations is performed. 8 . The computer-implemented method of claim 1 , wherein the timestamp information specifies a first time that precedes a second time at which a file system operation of the one or more file system operations that is performed earliest out of all of the one or more file system operations is performed. 9 . The computer-implemented method of claim 8 , further comprising restoring a portion of the secondary data that was created at or prior to the first time specified by the timestamp information and not restoring another portion of the secondary data that was created after the first time specified by the timestamp information. 10 . The computer-implemented method of claim 1 , further comprising, prior to restoring the secondary data in response to detecting the file activity anomaly, determining an indication of an input by a user of the client computing device for confirming the detection of the file activity anomaly. 11 . A system for detecting file activity anomalies, the system comprising: a client computing device comprising computer hardware and configured to perform one or more file system operations within a file system residing on the client computing device; and one or more secondary storage devices comprising computer hardware and configured to store secondary data associated with the client computing device, wherein the secondary data is a copy of primary data stored on one or more primary storage devices associated with the client computing device, wherein the client computing device configured to: detect a file activity anomaly based at least on the one or more file system operations satisfying one or more threshold conditions associated with the client computing device; store timestamp information associated with the one or more file system operations; in response to detecting the file activity anomaly, restore, based at least on the timestamp information, at least some of the secondary data stored in the one or more computing devices onto one or more primary storage devices associated with the client computing device; and output a notification indicating at least the file activity anomaly. 12 . The system of claim 11 , wherein the client computing device is further configured to: monitor file system operations performed on the client computing device over a second time period preceding the first time period; determine a baseline count of file system operations performed on the client computing device over the second time period; and determine, based at least on the baseline count, the threshold value for disabling the one or more data protection operations. 13 . The system of claim 12 , wherein the baseline count is an average number of file system operations performed on the client computing device for each sub-period of a plurality of sub-periods within the second time period. 14 . The system of claim 12 , wherein the client computing device is further configured to determine the threshold value by multiplying the baseline count with a predetermined percentage value, wherein the predetermined percentage value is greater than 100 percent. 15 . The system of claim 12 , wherein the client computing device is further configured to periodically determine whether a current count of file system operations satisfies the one or more threshold conditions for each of a plurality of time periods subsequent to the specific time period and each having a same length as the specific time period. 16 . The system of claim 11 , wherein the one or more file system operations comprise at least one of write operations, create operations, rename operations, or delete operations. 17 . The system of claim 11 , wherein the timestamp information specifies a first time at which a file system operation of the one or more file system operations that is performed earliest out of all of the one or more file system operations is performed. 18 . The system of claim 11 , wherein the timestamp information specifies a first time that precedes a second time at which a file system operation of the one or more file system operations that is performed earliest out of all of the one or more file system operations is performed. 19 . The system of claim 18 , wherein the client computing device is further configured to restore a portion of the secondary data that was created at or prior to the first time specified by the timestamp information and not restoring another portion of the secondary data that was created after the first time specified by the timestamp information. 20 . The system of claim 11 , wherein the client computing device is further configured to, prior to restoring the secondary data in response to detecting the file activity anomaly, determining an indication of an input by a user of the client computing device
Details of monitoring file system events, e.g. by the use of hooks, filter drivers, logs · CPC title
Active attacks involving interception, injection, modification, spoofing of data unit addresses, e.g. hijacking, packet injection or TCP sequence number attacks · CPC title
wherein the data content is protected, e.g. by encrypting or encapsulating the payload · CPC title
File encryption · CPC title
Time stamp · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.