Automatic malware remediation and file recovery management
By automatically detecting and repairing malware infections of client devices in cloud services, and resuming the initial version with synchronous history, the automated management problem of malware attacks in cloud storage services is solved, and rapid and effective digital content recovery is achieved.
Patent Information
- Application Number
- CN202080030340.2
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Priority Date
- 2019-04-23
- Filing Date
- 2020-03-28
- Publication Date
- 2024-11-08
- Estimated Expiration
- 2040-03-28
AI Technical Summary
When existing cloud storage services face malware attacks, it is difficult for users to automatically repair and restore, and the conventional repair methods are cumbersome, time-consuming and difficult to complete, resulting in fragile digital content and lack of effective management tools in the face of malware attacks.
By receiving synchronous data from client devices at remote cloud services, automatically detecting malware infections, calling anti-virus services for repair, and recovering the initial version based on the synchronization history, automatically replacing infected files to achieve automatic repair and recovery of devices and files .
Simplifies the malware repair process, reduces user intervention, improves the security of digital content, reduces the impact of malware, provides automated management tools for device infections, and ensures rapid recovery of files.
Smart Images

Figure CN114424194B_ABST
Abstract
Description
Background Art
[0001] A cloud storage account allows users to store their electronic content items or files in an online storage account that can be accessed from any computing device using an Internet connection. Some of the better known examples of cloud storage service providers include Microsoft Google and Through these types of services, users can upload content items such as pictures, songs, documents, and other electronic content from a computing device to an online storage account. These items can then be accessed from a different computing device. In some cases, such as Microsoft's The service provides a means to store, synchronize and share a wide variety of file types with others and across multiple computing devices, as well as the ability to synchronize system settings, visual customizations, themes, application settings and browser tabs, history and saved passwords across different devices.
[0002] As more and more computers have become interconnected through various networks, attacks delivered through networks have also increased, and computer security has become a top priority. Such malware attacks can appear in the form of computer viruses, computer worms, ransomware, system component replacement, spyware, adware, denial of service attacks, and other invasive attacks that exploit one or more computer system vulnerabilities to achieve illegal purposes. In particular, ransomware is malware that increasingly targets cloud storage.
[0003] Unfortunately, even with cloud storage backup, users continue to find that their digital content items are still vulnerable to malware attacks. For users, resolving these attacks can be time consuming and challenging. Conventional repair methods require users to perform a series of multiple manual steps, which in many cases may be difficult for users to complete. Therefore, there are still important areas that require new and improved concepts to ensure the safety of digital content, reduce the impact of malware, and provide users with tools for improved management of device infections. Summary of the invention
[0004] The automatic repair and recovery system according to the first aspect of the present disclosure includes a processor and a computer-readable medium containing instructions, the instructions, when executed by the processor, cause the processor to receive synchronization data for a first file from a first client device over a communication network at a remote cloud service during a synchronization session, the synchronization data indicating that the first client device is associated with a possibility of being infected by malware. The instructions also cause the processor to: determine at the remote cloud service in response to receiving the synchronization data that the first client device has been infected by malware; and in response to the determination that the first device has been infected, automatically call an anti-virus service for repairing the first client device, the first device being registered with the anti-virus service. In addition, the instructions also cause the processor to: confirm at the remote cloud service that the repair of the first client device has been successfully completed, and determine the initial infection time when the infected version of the first file was initially submitted for synchronization with the remote cloud service based on an inspection of the synchronization history of the first file. The instructions also cause the processor to automatically restore the first file on the client device by identifying (at the remote cloud service) a first version of the first file that was synchronized before the initial infection time and replacing the infected version with the first version.
[0005] A method according to a second aspect of the present disclosure includes receiving synchronization data for a first file from a first client device over a communication network at a remote cloud service during a synchronization session, the synchronization data indicating that the first client device is associated with a likelihood of being infected by malware. The method also includes: determining at the remote cloud service in response to receiving the synchronization data that the first client device has been infected by malware; and then automatically invoking an anti-virus service for repairing the first client device in response to the determination that the first device has been infected, the first device being registered with the anti-virus service. The method also includes confirming at the remote cloud service that the repair of the first client device has been successfully completed. In addition, the method includes determining an initial infection time when an infected version of the first file was initially submitted for synchronization with the remote cloud service based on an inspection of the synchronization history of the first file. Finally, the method can include automatically restoring the first file on the client device by identifying (at the remote cloud service) a first version of the first file that was synchronized before the initial infection time and replacing the infected version with the first version.
[0006] A computer-readable medium according to a third aspect of the present disclosure includes instructions stored therein, which, when executed by a processor, cause the processor to perform operations, the operations including receiving synchronization data for a first file from a first client device over a communication network at a remote cloud service during a synchronization session, the synchronization data indicating that the first client device is associated with a likelihood of being infected by malware. In addition, the instructions also cause the processor to: determine at the remote cloud service in response to receiving the synchronization data that the first client device has been infected by malware; and then automatically invoke an anti-virus service for repairing the first client device in response to the determination that the first device has been infected, the first device being registered with the anti-virus service. In addition, the instructions also cause the processor to confirm at the remote cloud service that the repair of the first client device has been successfully completed. The instructions also cause the processor to: determine an initial infection time when an infected version of the first file was initially submitted for synchronization with the remote cloud service based on an inspection of the synchronization history of the first file; and automatically restore the first file on the client device by identifying (at the remote cloud service) a first version of the first file that was synchronized before the initial infection time and replacing the infected version with the first version.
[0007] This Summary is provided to introduce a collection of concepts in a simplified form that are further described in the Detailed Description below. This Summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter. Furthermore, the claimed subject matter is not limited to implementations that overcome any or all of the deficiencies noted in any part of this disclosure. BRIEF DESCRIPTION OF THE DRAWINGS
[0008] The accompanying drawings illustrate one or more embodiments according to the present teachings by way of example only and not by way of limitation. In the accompanying drawings, like reference numerals are used to indicate the same or similar elements. In addition, it should be understood that the accompanying drawings are not necessarily drawn to scale.
[0009] Figure 1A and Figure 1B is a conceptual illustration of an implementation of automatic repair and recovery;
[0010] Figure 2 is a diagram illustrating an implementation of a repair and recovery management architecture;
[0011] Figure 3A and Figure 3B is a conceptual illustration of an implementation of a malware attack and corresponding malware detection;
[0012] Figure 4A and Figure 4B is a conceptual illustration of an embodiment of confirming a device is infected and determining the time of infection;
[0013] Figure 5 is a representation of the automatic repair process;
[0014] Fig. 6A and Figure 6B It is a representation of the automatic file recovery process;
[0015] Fig. 7A is a representation of a device display of an implementation of a notification of the occurrence of repair and recovery of a user device;
[0016] Figure 7B is an example of a user interface for adjusting user preferences for automatic repair and recovery of a user device;
[0017] Fig. 8A and Figure 8B is a flow chart illustrating an embodiment of a process for automatic repair and recovery;
[0018] Fig. 9 is a flow chart presenting an implementation of an automated repair and recovery process;
[0019] Fig.10 is a block diagram of an exemplary computing device that may be used to provide implementations of the mechanisms described herein; and
[0020] Fig.11 is a block diagram illustrating components of an exemplary machine configured to read instructions from a machine-readable medium. DETAILED DESCRIPTION
[0021] In the detailed description below, many specific details are set forth by way of example in order to provide a thorough understanding of the relevant teachings. However, it should be apparent that the present teachings can be practiced without such details. In other cases, well-known methods, processes, components and / or circuit systems are described at a relatively high level without giving details in order to avoid obscuring various aspects of the present teachings.
[0022] The following description discloses systems and methods for repairing electronic content items and computing devices after they have been infected by malware.(One or more) user accounts affected by the attack are associated with an online or cloud-based storage system that hosts and synchronizes files for the user account. A content management system is configured to receive information about the electronic content items and verify whether one or more of the items have been potentially targeted or damaged by malware. If the user account has opted in or otherwise enabled an automatic repair service, the system can remotely determine whether the client device contains an anti-virus program and then automatically run the anti-virus program to remove the malware. The repair of the device becomes a fully automated process initiated by a remote service and can provide both restoration of the affected device and recovery of infected files. Such proactive repair measures can reduce potential data loss situations, free users from the burden of device repair and file damage, and help minimize the possibility of incomplete or erroneous attempts in malware removal.
[0023] For reference purposes, content management system (CMS) refers to a cloud-based system, through which users can store content items, and perform various content management tasks, such as retrieving, modifying, browsing and / or sharing the content items, and enabling users to access the content from multiple client devices. Generally speaking, users can interact with CMS by one or more client devices connected to a network. CMS can support connections from various different client devices, such as desktop computers, mobile computers, mobile communication devices (such as mobile phones, smart phones, tablet computers, etc.), smart TVs, gaming devices, set-top boxes, and / or any other network-enabled computing devices. CMS can be configured to accept connections from multiple client devices simultaneously and interact with these client devices. Typically, users use CMS by interacting with client-side applications, which are installed on the device of the client or work via third-party applications (such as web browser applications) and are configured to communicate with the CMS.
[0024] In addition, as a general concept, the term "electronic content item" or "content item" includes any digital data that can be presented (e.g., visually or audibly presented), including but not limited to: electronic documents, media streams, web pages, hypertext documents, images, digital videos or video recordings, digital audio or audio recordings, animations, digital messages, markup language documents (such as hypertext markup language (HTML) or extensible markup language (XML) documents), forms with blank components for accepting input data, or data describing GUI applications, and other digital data. In addition, the "item" used in this article can include any folder, file, directory, or data object on an electronic device. As an example, an item can refer to a directory "folder" that can include documents, photos, music files, and video files.
[0025] Additionally, the terms "software application," "software," or "application" may refer to a computer program that performs useful work that is generally unrelated to the computer itself. Some non-limiting examples of software applications include word processing software, spreadsheets, accounting systems, and telecommunications programs, as well as gaming software, utility programs and productivity tools, mobile applications, presentation graphics, and other productivity software. Therefore, specific references to software applications by name throughout this specification should not be construed as limiting the use of the proposed systems and methods.
[0026] In addition, synchronization can refer to uploading content items from client devices to CMS or alternatively downloading content items from content management system to client devices through communication network, which will obtain synchronized content library on both client devices and content management system. It should be understood that for simplicity, the example described in this article will introduce the situation where uploading occurs. However, all references to "upload" and the examples of synchronization based on uploading introduced in the description below should be understood to also cover the situation that synchronization events involve downloading electronic content. For example, client devices can be configured to synchronize content items stored on client devices with associated accounts on CMS by uploading content items stored on client devices to linked content management system. The client devices can also be configured to synchronize content items by downloading content items stored on linked content management system to the client devices.
[0027] The following embodiments describe methods for monitoring and repairing client devices, corresponding operating systems and core components, and digital content associated with the devices for malware. As a general concept, malware refers to software that has been specifically designed to damage or interfere with a system (e.g., malicious software or "malicious software"), and malware damages the integrity of the computer's operating system. On a daily basis, operating systems are designed to provide infrastructure for hosting processes and providing system services for these processes. These operating systems generally provide basic security protection, including enhancements to access control and ownership rights involving system resources. Some typical protective security services appear in the form of host firewalls, vulnerability assessments, patch detection, behavior blocking, host or network intrusion detection, and anti-virus technology. These services run as local applications in the operating system. However, despite these measures, the device operating system is sometimes unable to accurately determine whether it has been attacked, or prolongs the time required to diagnose such an attack. As an example, once some form of malicious code or other malware attacks a computer system and obtains the necessary level of control (e.g., administrator-level access), all further attempts made by the operating system to determine whether it has been attacked will no longer be trustworthy, because the mechanism for such attempts may have been destroyed.
[0028] Protecting a computer system and its operating system from such damage involves further installing security applications, such as anti-virus software, personal firewalls, and intrusion detection systems. Even in a system comprising multiple computer systems, such as in a computer network or a cluster of computer systems deployed in an array, each individual computer system will run its own set of security applications. Generally speaking, this is because each computer system in a network or array is typically a physically separate entity with its own network attachment, its own (one or more) central processing unit, and its own operating system instance. These types of security applications can be installed on each computer system with the purpose of preventing the device and its operating system from being damaged. However, such security applications may also fail to protect the computer system, partly because - like other applications running on the computer system - it is also vulnerable to attack.
[0029] Specifically, ransomware is becoming more sophisticated and more destructive for end users. Ransomware is a malware that infects a device and denies a user access to computer files or data on the device. It usually requires a "ransom" to be paid in return for allowing the user to access their computer files or data. For example, ransomware can be used to encrypt computer files or data. After receiving the ransom payment, a key for decrypting the file or data is sent. Ransomware may be installed on a computer via a Trojan horse, which is a malware file disguised as a legitimate file, data or program. Ransomware can also be embedded in email attachments and pictures. One type of ransomware ("Locker") encrypts the entire hard drive of a computer, essentially locking the entire system against the user, while another type ("Crypto") will only encrypt specific, seemingly important files on the computer, such as word documents, PDFs, and image files. Such ransomware is always evolving, causing increased damage to client files and increased pressure on end users. It should be understood that although the disclosure below may refer to a specific type of malware (e.g., ransomware) for purposes of the following examples, the benefits of the present disclosure are not limited thereto and the present disclosure can be implemented for diagnosis and treatment of a wide range of malware types.
[0030] It should also be understood that the following disclosure is applicable to all types of anti-virus applications, anti-spyware applications, and other anti-malware applications that are installed locally on a client device and are intended to protect the device by identifying harmful applications or other executable code and / or removing or at least counteracting the harmful code. As will be discussed in more detail below, in order to reduce the impact of malware on client devices, in different embodiments, the CMS can provide or perform the service for user accounts that have opted in to the automatic repair and recovery service (RRS). The RRS can be configured to automatically detect whether malware has attacked a file. In response, the RRS can remotely execute a local instance of the anti-virus software and collaborate with the client device to return the affected files to a pre-attack or pre-infection state. The RRS can be configured to operate as an extension of an existing CMS or as an agent extension component running on a client device.
[0031] In some embodiments, RRS monitors changes to user files by scanning synchronized files. When changes to files are detected, the system can determine whether the files have been maliciously changed (e.g., deleted, encrypted, or otherwise destroyed). Such determination can occur based on many factors, including but not limited to criteria such as (a) entropy changes, (b) heuristics, (c) sudden changes in user behavior (e.g., behavioral analysis), and (d) changes in honeypot technology files or directories on files stored on a storage device of a cloud provider or stored on a storage device of a client device. In some embodiments, the system can use data analysis to help distinguish between legitimate changes and malicious changes. Various machine learning techniques, such as support vector machines, Bayesian networks, learning regression, neural networks, big data analysis, evolutionary algorithms, and other similar techniques can also be applied. Various file characteristics can be collected, such as the number and frequency of file changes, the location of file changes, the mode of change (file extension, file title, entropy change, file type), user information (e.g., organization or location), and other characteristics to assist the detection process.
[0032] In order to better introduce the system and method to readers, Figure 1A and Figure 1B A method for implementing a malware repair and recovery management system ("system" also referred to as Figure 2 1 and 1 . A high-level example of a representative computing environment ("environment") 150 is shown schematically in FIG. 1 . In various embodiments, environment 150 can include one or more computing device end users, or simply "users." One or more users can interact with or manipulate data presented via a user device. Figure 1A and Figure 1B A general description is given of the various features and activities illustrated in the drawings, wherein additional details and examples are given in connection with subsequent figures.
[0033] As an example, a first user account ("first user") 110 is accessing or otherwise sharing data using a sync client application ("sync client") 100 on a first device 120. The first device 120 may be a personal computer such as a desktop or laptop computer, a mobile device, or any other computer system with a file system. The first device 120 executes an operating system such as Microsoft Mac or other operating systems, and includes memory, storage, network interfaces, and Figure 1AFor the sake of clarity, other computer hardware is not shown. The first device 120 creates, modifies, and / or deletes files on its storage system via its operating system, wherein modifications are described herein. In addition, the first device 120 includes one or more synchronization folders. Figure 1A In the figure, only one device is shown, but any number of devices can share synchronized folders via the synchronization service. For example, the first device 120 can be connected to a server or an online or cloud-based storage and computing service ("cloud storage service") 190, such as a CMS. As the first user 110 adds or modifies electronic content via the first device 120, various content or files can be updated or saved in the cloud storage device through the network connection.
[0034] Thus, the first device 120 allows the first user 110 to create, modify, and delete files on the client's local file system, and the CMS - via the sync client 100 - allows those actions to be synchronized with versions of the same files on the host system and / or one or more other client computers. In some embodiments, a user can create folders and designate them for synchronization. The content of the files is managed in part by the sync client 100 to maintain a desired synchronization frequency or level. Generally speaking, a user can create a shared synchronized folder through a local control for the sync client 100 or via a web server, which can present a user interface to the end user to identify the files to be synchronized or adjust user settings, etc.
[0035] In general, an "interface" can be understood to refer to a mechanism for delivering content to an application user via a client application. For example, an interface may include pop-up windows, controls, actuatable interfaces, interactive buttons, or other objects that may be presented to a user via a local application user interface (UI), as well as mechanisms local to a particular application for presenting content associated with those local controls. In addition, an "actuation" or "actuation event" refers to an event (or a specific sequence of events) associated with a particular input or use of an application via an interface that can trigger a change in the display of the application. A selectable or actuatable option or button is configured to receive user input and trigger such an actuation event.
[0036] Additionally, "local controls" refers to mechanisms for delivering content to application users via a client application. For example, local controls may include actuatable or selectable options or "buttons" that may be presented to a user via a local application UI, touch screen access points, menu items, or other objects that may be shown to a user via a local application UI, sections of a larger interface, and mechanisms local to a particular application for presenting associated content with those local controls. The term "asset" refers to content that may be presented in association with a local control in an original application. Thus, as non-limiting examples, an asset may include text within an actuatable pop-up window, audio associated with an interactive click of a button or other local application object, video associated with a teaching user interface, or other such presentation of information.
[0037] exist Figure 1A In an example of , the sync client 100 can provide a UI that is configured to allow the first user 110 to select or authorize folders or content to be shared with the cloud storage service 190. The first device 120 can then upload or synchronize one or more electronic content items available in a storage component associated with the first device 120. For simplicity purposes, the electronic content collection includes a first electronic content item ("first item") 102, although in most cases there will be multiple electronic content items queued for synchronization. The first item 102 can be associated with a synchronization folder made available by the sync client 100 on the first device 120. In some embodiments, the operating system can send a message to indicate that a change has occurred to the synchronized folder, as well as the location (path) of the folder or the file within the folder to which the change has occurred. Because the folder is synchronized, the data associated with each item is transmitted to the cloud storage service 190.
[0038] As will be discussed in greater detail below, because the first user account was synchronized or otherwise shared data with the cloud storage service 190 at the first time 104 (approximately 3:00 PM) during the synchronization account session 112, there may be various indications of "signs" or potential for one or more items or files to be affected or impacted by malware. In some implementations, the cloud storage service 190 may be configured to detect such indications during or shortly after synchronization occurs. For example, the cloud storage service 190 may receive synchronization data for one or more files from the first device that indicates that the first device is associated with a potential for infection by malware.
[0039] exist Figure 1A, such a detection has occurred, which is represented by the alert trigger 114. In other words, in the first stage 130, the system has determined that one or more files from the most recent sync account session 112 likely reflect damage indicative of a device infection caused by malware. In various embodiments, the system can proceed with verification of the infection in a second stage 132, in which a more thorough examination of the user account and associated files can occur. In one example, the system can determine that the malware 192 has attacked the first device 120 (i.e., there is confirmation or verification of the infection) based on damage to one or more of the files synchronized via the sync client installed on the first device 120 (here, the first item 102).
[0040] In such a case, the system can attempt to determine approximately when the infection initially occurred and the scope of the infection, as represented by the third stage 134. This determination can be based on a wide range of factors. In this case, the system determined that the device infection 196 began with a file being synchronized at or after 2:00 PM (see second time 194), which coincides with a synchronization session that occurred approximately one hour prior to the most recent (current) synchronization session. In various embodiments, based on some or all of this information, the system can initiate an automatic repair.
[0041] Reference now Figure 1B, the cloud storage service 190 can transmit or transfer instructions or requests 162 to the anti-virus service 160 at the fourth stage 136 to start or execute the device repair process. It is understood that the anti-virus service 160 is installed on the first user account 110 or otherwise registered with the first user account 110 at the time of repair. Therefore, in different embodiments, the system can include some provisions for remotely and automatically activating or executing software or services associated with the local first device 120. In some embodiments, it is understood that this process will only occur in those cases where consent or authorization from the first user account 110 is obtained (just before each run event, or a general consent applicable to all or most future infection determinations obtained at an earlier time). Once the anti-virus service 160 receives the request 162, the fifth stage 138 occurs, in which the first device 120 is repaired and malware is removed via the anti-virus service 160. This repair session 170 can include, for example, removing malware (such as ransomware) from the affected device and / or potentially re-imaging the affected device. In some embodiments, the system can automatically extend its repair session 170 to multiple devices associated with the first user account 110, if other devices are found to also store (one or more) damaged files, not just the first device 110 that was first identified as infected, thereby ensuring that the user account as a whole is safe. In some embodiments, this can occur simultaneously (i.e., multiple infected devices for the user account can undergo automatic repair at approximately the same time), can occur sequentially (i.e., each infected device for the user account can undergo automatic repair one after another), or the end user can select when it is acceptable for execution of automatic repair for each device.
[0042] Once the first device 110 is repaired, in some embodiments, the system can proceed with initiating automatic recovery of the affected files. For example, in the fifth stage 140, the first item 102 is reversed back to a point in time when the first item 102 existed before the infection occurred (e.g., at Figure 1A 134 in the third stage 134 of the present invention) (see rollback loop 180). In other words, for the purposes of this example, the system is able to return or restore the affected files from the compromised state or condition reflected at 3:00 PM to the pre-infection state existing at 2:00 PM (see restore point 184). This restoration can occur with respect to files stored in the cloud storage service and / or files stored in the first device.
[0043] It can be appreciated that in many cases, ordinary users are unaware of the incidents that have caused malware attacks on their devices or files. Therefore, users may make behaviors that exacerbate the problem or otherwise compromise the security of their own accounts. Similarly, in the case where the user becomes aware of the problem, he or she may try to initiate recovery and repair, but it is difficult to cope with the many carefully arranged manual steps required to successfully and completely complete the removal of malware. Many times, users may initiate or complete some of the tasks to the extent required to continue normal work, but still do not realize that malware continues to exist on their devices. In another example, users may believe that they have thoroughly purified the device, but in fact fail to perform a certain action necessary to complete the repair, and then find that the device is still unsafe. As a general concept, an automatic repair session will refer to the implementation of a repair that is triggered or initiated remotely on one or more user devices. Although in some embodiments, a user may be notified or messaged regarding the diagnosis and suggested actions prior to a repair and / or the user may be required to provide user input to the system before the repair begins, the overall process described herein is configured to occur in a substantially automatic manner, wherein the user can continue to work at their device and, if desired, monitor the progress of the repair and recovery, or simply walk away from the device while the repair and recovery session occurs.
[0044] In other words, upon determining that a device has been infected, the system can automatically take steps to protect the user account by quickly initiating repair of the affected device(s) and recovery of infected files. To further provide context for the use and application of the system described herein, Figure 2 A non-limiting example of an automatic repair and recovery system ("system") 200 operating in conjunction with or in association with a cloud service 204 and a sync client 220 is presented. In various embodiments, one or more files of a sync upload set (or download set) can include characteristics, attributes, or parameters that can be used by the system to determine whether the file reflects an infection of the client device. As a general concept, "sync content set" will be used to refer to content items queued for synchronization in a pending sync session. The session can be initiated automatically at predetermined intervals or following a specific trigger event, or can be initiated manually by a user, and can contain one file, one folder, or multiple folders or directories. Additionally, a "queue" refers to a sequence of previous versions of a particular file that are generated following multiple sync events with a cloud service.
[0045] exist Figure 2In the embodiment of the present invention, the synchronization client 220 is configured to monitor the synchronization process and transmit the synchronization content to the synchronization server system installed on the client device 202 or associated therewith. The synchronization client 220 generally includes or accesses a synchronization item identification module, which is particularly configured to identify one or more new synchronization items to be synchronized from the synchronization client 220 to the synchronization file storage device 270 associated with the cloud service 204. For example, in response to the creation or modification of a digital content item, a corresponding new synchronization item 206 can be generated and provided to the pending synchronization item module for transmission to the cloud service. In some embodiments, the new synchronization item can be added to a pending synchronization item queue. The pending synchronization item queue can be configured to determine the order for synchronizing the pending synchronization items; for example, the pending synchronization item queue can be configured to select the next synchronization item from the pending synchronization items.
[0046] In some embodiments, the sync client 220 includes a data transfer module configured to retrieve sync items from the pending item queue, obtain data for corresponding portions of the content item (e.g., file) 208 from the client content storage 230, and transmit the data in an upstream content item data message 206 via the network(s) 290 to the cloud service or server system 204. In various embodiments, malware 240 may attack the client device 202, and in some embodiments, such as in Figure 2 As shown in , malware 240 can cause damage to files 208 stored in client content storage 230. When these files 208 are next synchronized with synchronization file storage 270 via synchronization client 220, these files 208 can be examined by diagnostic module 280, which can determine whether the signs or indications of damage are actual reflections of device infection.
[0047] In general, the cloud service 202 is configured to receive content data (files) for storage in the sync content storage 454. The server content storage may implement version control to save previous versions of user content items that have been modified or deleted. In some embodiments, the cloud service 204 is configured to maintain a sync history, which will be discussed further below. The sync history stores information about sync activities for users of the sync service.
[0048] In addition, in some embodiments, the sync content storage 270 can communicate and / or share information with a diagnostic module 280 that can examine the sync data for the synchronized files. In the event that the sync data indicates that the client device 202 is associated with the possibility of infection by malware, the diagnostic module 280 can further determine or confirm that the client device 202 has been infected by malware. In response, the repair controller 250 can automatically call an anti-virus service (see anti-virus component 210) installed on the now infected client device 202, registered with the device, or otherwise associated with the device for repair. In different embodiments, this call can occur as a message or instruction that is transmitted from the repair controller 250 and optionally via the sync content storage 270 to the sync client 220. The sync client 220 can then request the anti-virus component 210 to initiate a repair session for the client device 202 to remove the infection and repair the device.
[0049] At the end of the repair session, in some embodiments, the cloud service 204 can confirm or otherwise be configured to determine that the repair of the first client device has been successfully completed. In response, the recovery controller 260 can initiate automatic recovery of the damaged file(s) for: (a) the copy of the file(s) stored on the client content storage 230 at the client device 202 and or alternatively (b) the copy stored on the sync content storage 270 in the cloud service 204. In some embodiments, the diagnostic module 280 can facilitate the recovery process by identifying the most recent version of the (now damaged) file as a result of a sync session that occurred before the malware attack. In some embodiments, this identification can follow a determination of the initial infection time when the infected version of the first file was initially submitted for synchronization with the remote cloud service based on an examination of the synchronization history of the first file. Once an appropriate rollback point has been established, the infected version of the file can be replaced or updated with the undamaged version of the file represented by the rollback version 232.
[0050] In various embodiments, the cloud service 204 can also include or have access to a user account information module 212 that can enable or facilitate verification of any required user authorization 214 or consent for the automatic repair and / or automatic recovery process. Additionally, a message generator 216 can collaborate with the user account information module 212 to identify various notification channels indicated by a user account, such as email, direct message via a social media channel, instant messaging message, and / or mobile device text message. The message generator 216 can issue a user notification 476 and is configured to warn the user about the malware attack, obtain authorization from the user when necessary, and / or provide updates about the automatic process.
[0051] Now refer to Figure 3A - The sequence illustrated in FIG7 presents another example of a scenario for implementing a malware remediation management system ("the system"). Figure 3A Initially, a first synchronization session ("first session") 310 is initiated via a second device 320 at a first time 312 ("3:00 PM") on a first day 314 ("Monday the 22"). During this first session 310, files 304 in a synchronization folder 324 are successfully synchronized, and at the end of the first session 310, the system 300 does not detect any indication of malware (as represented by a healthy device icon 322). After the time period 302, at a second time 332 ("9:00 AM") on the following second day 334 ("Wednesday the 24"), a second synchronization session ("second session") 330 is initiated. It can be observed that at some point during the time period 302, one or more files of the second device 320 and / or a user account logged into the second device 320 become infected by malware 326. In this scenario, for the purpose of providing an example, the files are shown as being "locked" after a ransomware attack 328. It should be appreciated that in some implementations, additional or multiple synchronization sessions may have occurred during time period 302 that are not depicted herein.
[0052] In various embodiments, malware remediation management system (“system”) 300 can be configured to maintain up-to-date knowledge of changes made to files as files are synchronized with cloud-based storage and computing services (“cloud storage services”) 350, such as in Figure 3B In some embodiments, the system 300 can be configured to Figure 3A The synchronization process and the corresponding data are evaluated and / or checked during the substantially parallel course of the events shown in . Figure 3B, during a first session 310, system 300 can detect or otherwise obtain a first set of information 340 indicating that the file currently reflects a possibly normal or undamaged state 342. However, during or after a second session 330, cloud storage service 350 can obtain a second set of information 360 and determine that a possible infection of the client device has occurred 362. For example, system 300 can detect that one or more of the files being synchronized are associated with various indicators or possible malware signs.
[0053] Next reference Figure 4A In various implementations, at or about this time (during or soon after the second session 330), the system 300 can initiate an assessment, inspection, and / or evaluation 416 of the potentially compromised files and other files and data 412 associated with the user account 414 stored on the cloud storage service 350. If during this evaluation 416, the system 300 again detects anomalies or other inconsistencies or information indicative of malware, the system 300 is configured to confirm the presence of an infection 418 on the client device.
[0054] In some embodiments, during and / or after the evaluation 416, the system 300 can optionally further continue to perform a more in-depth or comprehensive analysis or diagnosis based on its own stored user synchronization history. For example, Figure 4B A possible approach is described that the system 300 can apply to determine when and on which file(s) a client device was initially infected. For the purpose of illustration to the reader, along the Figure 4B The lower part of shows multiple previously synchronized versions of a single (affected) file. Each file version corresponds to a different synchronization session that occurred at a different time. Figure 4B In the example, the system 300 initiates a check of files for the user's account 414, and the check is performed "backwards" in time, that is, from the second time 332 on the second day 334 (the known "post-infection" period) to the first time 312 on the first day 314 (the known "pre-infection" period).
[0055] During this process, system 300 can evaluate, for example, first file version 412 synchronized during first period 410, second file version 422 synchronized during second period 420, third file version 432 synchronized during third period 430, fourth file version 442 synchronized during fourth period 440, fifth file version 452 synchronized during fifth period 450, sixth file version 462 synchronized during sixth period 460, and seventh file version 472 synchronized during seventh period 470. As shown in Figure 4B , in some embodiments, the system 300 can determine that the file has been corrupted 404 within a number of synchronization sessions (at least back to the fourth time period 440). In some embodiments, the system 300 can be able to roughly indicate the infection time. In one embodiment, the system 300 can establish an infection boundary 406 (e.g., a fifth file version 452) at the fifth time period 450 to ensure clear demarcation or isolation of the corrupted file. In some embodiments, the system 300 can also roughly determine the infection day 456 and infection time 454 of the client device corresponding to the infection boundary 406. Prior to this time, for example, in the sixth time period 460 and earlier, the file (e.g., the sixth file version 462) was considered "clean" or normal.
[0056] In various embodiments, in response to determining that an infection has affected file(s) associated with a user account and a device, the system may automatically initiate an automatic repair process. In some embodiments, the repair may be directed primarily or entirely to the devices that share the synchronized files, while in other embodiments, several or all devices associated with the user account may be subject to automatic repair. Figure 5 , a depiction of the resulting automatic repair process 500 is illustrated. It can be seen that in some optional embodiments, the user 520 may first receive an automatic request 512 from the system, which will notify the user 520 that an infection has occurred and require the user 520 to provide authorization, approval, or confirmation of the upcoming automatic repair process 500. In this example, the user 520 provides the requested input 524 via the second device 320. In response (in embodiments where such input is required), the cloud storage service 500 transmits a request or otherwise communicates instructions 510 to the antivirus provider 550 at the initial repair time 502 (10:00 AM). In the event that such input is not necessary, for example, when authorization has been indicated or recorded at a time prior to the event, the automatic repair process 500 can proceed directly to remote execution to the antivirus provider 550.
[0057] For the purposes of this example, the anti-virus provider 550 is a locally installed or accessed application that the user 520 has previously registered with, which is configured to repair the damage caused by the malware attack 530 of the second device 320. During the repair duration 560, the second device 320 can undergo a wide range of various repair processes 590, including but not limited to: installation of any processing software, running scripts, removing traces of malicious code (while leaving legitimate or undamaged files intact), isolating devices, facilitating remote access, performing forensic analysis, and / or re-imaging the device. Once the client-based malware repair service is triggered, the (one or more) affected devices can undergo a fully automatic point-in-time recovery without any further user input. Although the user 520 is shown as being adjacent to the second device 320 in this example, in other examples, the user can be located elsewhere (e.g., not presented with the device) during the duration of the automatic repair process 500. In some other cases, the user 520 can even continue to work on the second device 320 using the unaffected resources of the second device, while the automatic recovery of the device continues to occur, although there may be some intervals that cause the process to request the user to "step back" to allow the machine repair work to continue without interference, and the entire process can be completed without any intervention from the user. The resulting repaired state is represented by a safe symbol 580. In this example, the automatic repair process 500 that has occurred within the repair duration 560 is completed at a second time 504 (2:00 PM) of the same day. In other embodiments, the process can occur within any time period ranging from a few seconds or minutes to several days. For example, if the infection is detected early, the process may be shorter, while if the user interrupts the process or the malware attack is more severe, it may take more time. Once the repair is completed, the system can receive or otherwise obtain a signal 540 that the device is safe. In some embodiments, an automatic file recovery process can then be initiated, wherein the damaged file version will be replaced or restored with an earlier unaffected file version.
[0058] Next, refer to Fig. 6A and Figure 6B , which illustrates one embodiment of an automatic data recovery process 600. In various embodiments, the cloud storage service 350 includes or has access to previously synchronized versions 650 of the file, if any. For example, for substantially every data item or file that has been synchronized with the user's account, the cloud storage service 350 may include multiple versions corresponding to the file content during past synchronization sessions that synchronized that particular file. Fig. 6A, the cloud storage service 350 can reference a log or directory identifying versions 650 available or associated with a data item 602, where the versions include a first (initial) version 610, a second version 612, a third version 614, a fourth version 616, a fifth version 618, a sixth version 620, a seventh version 622, an eighth version 624, a ninth version 626, a tenth version 628, an eleventh version 630, and a twelfth (most recent or latest) version 632. In this case, the system has determined that there is file corruption (see infection boundary 406), starting at the eighth version 624 and onward to the twelfth version 632, while versions of the file prior to the eighth version 624 (i.e., the first through seventh versions) are uninfected (see uncompromised state 342). Recovery of a file—e.g., reverting a file to a previous version of the same file—can involve identifying a previous or most recent “safe” or uncorrupted version of the file that can be used for recovery. In one embodiment, the system can also support or provide additional security by initiating a rollback of the account state to a time before the date the first file was affected by the ransomware. In other words, while in some embodiments the system can be configured to restore to a file version that existed just before the infection to maximize data recovery, in some other embodiments the system can initiate a rollback process that includes a "cache" period. This buffer period can extend from the infection time back to an earlier time and include a synchronization session that synchronizes one or more safe versions of the file to fully ensure that all traces of damage to the file are rolled back.
[0059] exist Figure 6B One possible outcome of this type of automatic data recovery process 600 is illustrated in FIG. In the event that a corruption has occurred after a synchronization period in which the eighth version 624 is synchronized, the rollback 610 can, in some embodiments, retrieve or restore to the seventh version 622 to implement recovery. In other embodiments, such as in Figure 6B, a more "conservative" application of the recovery process 600 is shown, wherein the seventh version 622 is considered to have occurred during the buffer period between the infected state and the pre-infection state. In some embodiments, the selection of the recovery boundary (e.g., how wide or how large the buffer period should be extended) can also be adjusted or selected by the end user. In this case, the rollback 610 alternatively involves putting the sixth version 620 in the "front" of the version queue to make it as the most recent version of the file that will be considered safe and accessible to the user. The sixth version 620 is the front end or most current version of the recovery version set 660. A set of damaged (or potentially damaged) versions 670 of the file can be removed, isolated, isolated, destroyed or otherwise distinguished from the recovery version set 660, for example, according to user preferences. In some embodiments, these damaged versions 670 can be kept indefinitely in case the user wishes to try to further recover data that is only available in one of the damaged versions of (one or more) files later.
[0060] During or after the automatic repair and / or automatic data recovery process, in various embodiments, the user may be notified of one or more stages in the process. These notifications can be automatic and may be transmitted based on system settings and / or user preferences. Fig. 7AAn example is shown in FIG. 7 , in which a user interface 700 is depicted that displays an email message for a user account. Although email messages are described for the purposes of this example, it should be understood that in other embodiments, any other form of communication associated with the user's account may be used to provide such information, including but not limited to: text messages, chat messages, pop-up windows, automated phone calls, symbolic indications (shown briefly or on multiple occasions on the display while the process is occurring) or other local controls can be used. In this case, an email message ("message") 710 from the system is delivered to an email account linked to a user account associated with an infected client device. Subject line 722 prompts the user that this is a "file recovery notification." Message 710 includes a subject summary 730 "Ransomware has been detected on one of your devices." In some embodiments, message 710 can also include a paragraph with (for example) a diagnostic summary 732, which can notify the user of the detected (one or more) problems ("Hello Bruno, your account began to show signs of suspicious activity on December 22, 2018. We have determined that 231 files appear to have been compromised by a ransomware attack"). In one embodiment, this can be followed by an action summary 734, which can describe the steps deemed necessary to resolve the problem(s) ("We automatically initiated a repair to remove the malware and restore your files to their pre-infection state"). In addition, the message 710 can include a status summary 736, whereby the user is informed of the current state of their device(s) and data ("The detected malware has been cleared for your account. The compromised files on your local device have been rolled back to their pre-infection state"). In some embodiments, the message 710 can also provide the user with one or more selectable options or links, or otherwise provide guidance or suggestions on how the user can obtain additional or more detailed information. For example, the message 710 includes a first selectable option 760 for viewing additional details ("View detailed progress report") and a second selectable option 770 for accessing or viewing the changed files ("Inspect the restored files"). Such options can also provide other menu interfaces or allow the user to navigate to other menu interfaces from which the user can make modifications to their automatic repair and recovery settings and cancel the file rollback if desired. For example, a user may wish to opt out of one or more steps of the automated process, opt in to other services to increase automation, and / or request that notifications be provided via a different mechanism.
[0061] refer to Figure 7BAn example of a user interface 708 for adjusting user preferences and providing authorization for automatic repair and recovery processes is shown. In this case, the user interface 708 presents options for both repair in the upper section 758 and recovery in the lower section 768. In the upper section, the user is provided with a first selectable option 792 for authorizing or enabling automatic repair. Additional settings include a first selectable sub-option 714 ("Perform as soon as malware infection is confirmed?"), a second selectable sub-option 716 ("Do not run the following processes until I confirm: device reimage, device restart, software update"), a third selectable sub-option 718 ("Repair only at the following times: morning / afternoon / evening / night"), and a fourth selectable sub-option 724 ("Initiate process only when I am not logged into the device"). In the lower section, the user is provided with a second selectable option 726 for authorizing or enabling automatic recovery. Additional settings include a fifth selectable sub-option 728 ("Restore using the most recent synced version not affected by [malware]?"), a sixth selectable sub-option 744 ("Use X Hours buffer period ago to restore? "), seventh selectable sub-option 746 ("Restore only at the cloud server?") and eighth selectable sub-option 748 ("Restore only on the client device?"). It should be understood that these options and the arrangement of these options shown together are merely introduced for the purpose of illustration, and many other possible user preference settings or tasks are possible, including but not limited to providing or adjusting earlier versions relative to FIG. 1- Fig. 7A Those settings or tasks that characterize the described implementations.
[0062] It should be understood that the disclosed processes and systems can be applicable to both enterprise environments, which typically include network administrators and other information technology workers, and consumer-level entities, which are frequently targeted by malware to attack their personal computing devices. These automated processes allow individuals to feel confident that malware attacks are properly addressed, even without network management software.
[0063] For clarity, FIG8 illustrates an embodiment of a process 800 for providing automatic repair and recovery services (e.g., via a remote cloud service) for a local client device. In this example, a first stage 810 includes establishing a synchronization session with a client device for one or more files. In a second stage 820, a system associated with the remote cloud service can detect possible infection based on the most recent or some recent synchronized versions of the file. If the system is able to confirm that the client device has been infected by malware ("yes") in a third stage 822, the process 800 can continue. If there is no infection, the process can end, or return to initiate at the beginning of another synchronization session or file synchronization.
[0064] In the fourth stage 824, the system can confirm whether the user account associated with the synchronization session has authorized the automatic repair process. If authorization is not available ("No"), then a request can be transmitted in the fifth stage 826 to obtain user authorization. In some embodiments, the request can also include information about the infection for the user to review. If authorization is not received at the sixth stage 828 ("No"), then the process can end, or return to initiate at the beginning of another synchronization session or file synchronization. However, if the user provides his authorization at the sixth stage 828 ("Yes"), or if authorization is already available after the fourth stage 824, then the process 800 can continue in the seventh stage 830, in which the cloud service remotely executes the anti-virus service at the local client device. In some embodiments, for example, if the anti-virus service is unable to complete the repair for some reason, then the user can follow up by completing a manual repair.
[0065] Once the device repair is complete (eighth stage 840), the system can then confirm in the ninth stage 850 whether the user account associated with the synchronization session has authorized the automatic data recovery process. If authorization is not available ("No"), then a request can be transmitted in the tenth stage 852 to obtain user authorization. In some embodiments, the request can also include information about the repair and upcoming planned recovery for the user to review. If authorization is not received at the eleventh stage 854 ("No"), then the process can end, or return to initiate at the beginning of another synchronization session or file synchronization. However, if the user provides his authorization at the eleventh stage 854 ("Yes"), or if authorization is already available after the ninth stage 850, then the process 800 can continue in the twelfth stage 860, in which the cloud service can estimate and / or confirm when the infection occurred and / or which version of the affected file(s) was first damaged. Based on this determination, the system can automatically roll back the compromised file version(s) to an earlier version where infection has not occurred or damage has not occurred in the thirteenth stage 870. Data recovery can involve either or both of the cloud storage files and the client device files. Once completed in the fourteenth stage 880, the service can generate a notification in the fifteenth stage 890 and communicate it to the user account.
[0066] Fig. 9 is a flow chart illustrating an embodiment of a method 900 for automatically repairing a user device and restoring data for the user device. Fig. 9In an example of , a first step 910 includes receiving synchronization data for a first file from a first client device at a remote cloud service over a communication network during a synchronization session, the synchronization data indicating that the first client device is associated with a likelihood of being infected by malware. In a second step 920, the method 900 includes determining at the remote cloud service in response to receiving the synchronization data that the first client device has been infected by malware. A third step 930 includes automatically invoking an antivirus service for repairing the first client device in response to the determination that the first device has been infected, the first device being registered with the antivirus service. A fourth step 940 involves confirming at the remote cloud service that the repair of the first client device has been successfully completed, and a fifth step 950 includes determining an initial infection time when an infected version of the first file was initially submitted for synchronization with the remote cloud service based on an examination of the synchronization history of the first file. A sixth step 960 includes restoring the first file on the client device by identifying a first version of the first file that was synchronized before the initial infection time and replacing the infected version with the first version. The identification can occur at the remote cloud service by referencing a history for the particular file stored in cloud storage.
[0067] In other embodiments, additional steps may be included. For example, in some embodiments, the malware can be one of: ransomware, spyware, adware, a virus, or a worm. In another example, an anti-virus service may be installed locally on the first client device. In some embodiments, the first version corresponds to a most recent version of the first file synchronized before the initial infection time, while in other embodiments, the first version corresponds to a version of the first file synchronized during a synchronization session that occurred at least a predetermined buffer period earlier than the initial infection time.
[0068] In other examples, the method further includes automatically restoring the copy of the first file within the remote cloud storage device by reverting the infected version stored in the remote cloud storage device to the first version. In addition, the method can include receiving authorization to enable automatic repair from a user account associated with the first client device at the remote cloud service, and / or receiving authorization to enable automatic recovery of files on the client device from a user account associated with the first client device at the remote cloud service. In some cases, the authorization is obtained before receiving synchronization data for the first file, while in other cases, the authorization is obtained in response to a request from the remote cloud service after determining that the first client device has been infected by malware. In one embodiment, the method further includes: receiving synchronization data for multiple files from the first client device during the synchronization session; characterizing a subset of the multiple files as having been damaged by malware; and automatically restoring only the subset of the multiple files.
[0069] As noted above, a mechanism is provided for users, by means of which device repair and electronic content recovery can be better managed, the ability to provide the mechanism can significantly improve workflow efficiency and protect user data. By detecting situations that may lead to potential data damage, the automatic system can allow users to feel at ease in their daily computing use. By using this system, users can continue to reliably access and maintain the latest safe version of their electronic content from different devices, regardless of malware attacks on their devices. In addition, by providing users with notifications to follow these automatic processes, users are given the opportunity to maintain the latest understanding of the status of their electronic content, especially in situations where users may not otherwise be aware of attacks and / or file recovery. This type of solution can help users have more confidence in the security and access of their electronic content, and / or reduce the possibility of them experiencing data loss. Since recovery is limited to those files that have been affected by malware, the overall process described is significantly less invasive than the standard repair process, and the possibility of rolling back the intentional changes made by the user is greatly reduced. These processes can also be configured to occur asynchronously at the time and opportunity that has the least interference to the user according to the user's own preferences.
[0070] To illustrate the present disclosure and its benefits, the text introduces the following diagrams with respect to FIG. Fig. 9 Detailed examples of the systems, devices, and techniques described herein. Such example use should not be construed as limiting the logical process implementation of the present disclosure, nor should it be considered that changes in user interface methods compared to those described herein are outside the scope of the present disclosure. In some embodiments, in FIG. Fig. 9The various features described in the are implemented in respective modules, which may also be referred to as and / or include logical units, components, units and / or mechanisms. A module may constitute a software module (eg, code embodied on a machine-readable medium) or a hardware module.
[0071] In some examples, the hardware module can be implemented mechanically, electronically, or any suitable combination thereof. For example, the hardware module may include a dedicated circuit system or logic unit configured to perform a specific operation. For example, the hardware module may include a dedicated processor, such as a field programmable gate array (FPGA) or an application-specific integrated circuit (ASIC). The hardware module may also include a programmable logic unit or circuit system temporarily configured by software to perform certain operations, and may include a portion of machine-readable medium data and / or instructions for such a configuration. For example, the hardware module may include software contained in a programmable processor configured to execute a set of software instructions. It will be appreciated that the decision to implement the hardware module mechanically, in a dedicated and permanently configured circuit system, or in a temporarily configured circuit system (e.g., configured by software) may be driven by cost, time, support, and engineering design considerations.
[0072] Accordingly, the phrase "hardware module" should be understood to encompass a tangible entity that can perform a specific operation and can be configured or arranged in a physical manner, such an entity is physically constructed, permanently configured (e.g., hardwired) or temporarily configured (e.g., programmed), so as to operate in a specific manner or perform a specific operation described in this article. As used herein, "hardware implementation module" refers to a hardware module. Considering an example in which a hardware module is temporarily configured (e.g., programmed), it is not necessary to configure or instantiate each hardware module in the hardware module at any one time. For example, in the case where a hardware module includes a programmable processor that is configured by software to become a special-purpose processor, the programmable processor can be configured as different special-purpose processors (e.g., including different hardware modules) at different times. Software can configure a specific one or more processors accordingly, so that (for example) it constitutes a specific hardware module at one time and a different hardware module at different times. A hardware module implemented using a processor can be referred to as "processor-implemented" or "computer-implemented."
[0073] A hardware module can provide information to other hardware modules and receive information from other hardware modules. Accordingly, the described hardware modules can be viewed as being communicatively coupled. In the case where multiple hardware modules exist simultaneously, communication can be achieved by signal transmission (e.g., by appropriate circuits and buses) between two or more hardware modules in the hardware module. In an embodiment where multiple hardware modules are configured or instantiated at different times, for example, communication between such hardware modules can be achieved by storing and retrieving information in a memory device to which the multiple hardware modules have access. For example, a hardware module can perform an operation and store the output in a memory device, and another hardware module can then access the memory device and retrieve and process the stored output.
[0074] In some examples, at least some of the operations of the method can be performed by one or more processors or processor implementation modules. In addition, the one or more processors can also be used to support the execution of related operations in a "cloud computing" environment or as "software as a service" (SaaS) by operation. For example, at least some of the operations can be performed by multiple computers (as an example of a machine including a processor) and / or performed in the multiple computers, wherein these operations can be accessed via a network (e.g., the Internet) and / or via one or more software interfaces (e.g., application interface (API)). The execution of specific operations in the operations can be distributed in the processors, so that it does not only reside in a single machine, but is deployed across several machines. The processor or processor implementation module can be located in a single geographical location (e.g., in a home or office environment or in a server farm), or can be distributed across multiple geographical locations.
[0075] Fig.10 is a block diagram 1000 illustrating an exemplary software architecture 1002, portions of which may be used in conjunction with the various hardware architectures described herein to implement any of the features described above. Fig.10 is a non-limiting example of a software architecture, and it will be appreciated that many other architectures may be implemented to facilitate the functionality described herein. The software architecture 1002 may be run on hardware such as Figure 1A1002, which includes, among other things, a document storage device 1070, a processor, a memory, and input / output (I / O) components. A representative hardware layer 1004 is illustrated, which can represent, for example, the device 120 of FIG. 1. The representative hardware layer 1004 includes a processing unit 1006 and associated executable instructions 1008. The executable instructions 1008 represent executable instructions of the software architecture 1002, including implementations of the methods, modules, etc. described herein. The hardware layer 1004 also includes a memory / storage device 1010, which also includes executable instructions 1008 and accompanying data. The hardware layer 1004 may also include other hardware modules 1012. The instructions 1008 stored by the processing unit 1008 may be part of the instructions 1008 stored by the memory / storage device 1010.
[0076] Exemplary software architecture 1002 can be conceptualized into layers, each providing various functions. For example, software architecture 1002 may include layers and components such as operating system (OS) 1014, library 1016, framework 1018, application 1020, and presentation layer 1044. Operationally, application 1020 and / or other components within the layer may invoke API calls 1024 to other layers and receive corresponding results 1026. The illustrated layers are representative in nature, and other software architectures may include additional or different layers. For example, some mobile or dedicated operating systems may not provide framework / middleware 1018.
[0077] OS 1014 can manage hardware resources and provide public services. OS 1014 can include (for example) kernel 1028, service 1030 and driver 1032. Kernel 1028 can play the role of abstraction layer between hardware layer 1004 and other software layers. For example, kernel 1028 can be responsible for memory management, processor management (for example, scheduling), component management, networking, security settings, etc. Service 1030 can provide other public services for other software layers. Driver 1032 can be responsible for controlling lower hardware layer 1004 or docking with it. For example, driver 1032 can include display driver, camera driver, memory / storage device driver, peripheral device driver (for example, via universal serial bus (USB)), network and / or wireless communication driver, audio driver, etc., depending on hardware and / or software configuration.
[0078] The library 1016 may provide a common infrastructure that can be used by the application 1020 and / or other components and / or layers. The library 1016 generally provides functions used by other software modules to perform tasks, rather than directly interacting with the OS 1014. The library 1016 may include a system library 1034 (e.g., a C standard library), which may provide functions such as memory allocation, string manipulation, and file operations. In addition, the library 1016 may include an API library 1036, such as a media library (e.g., supporting the presentation and manipulation of image, sound, and / or video data formats), a graphics library (e.g., an OpenGL library for rendering 2D and 3D graphics on a display), a database library (e.g., SQLite or other related database functions), and a web library (e.g., WebKit, which may provide web browsing functions). The library 1016 may also include a wide range of various other libraries 1038 to provide many functions for the application 1020 and other software modules.
[0079] Framework 1018 (sometimes also referred to as middleware) provides a higher level common infrastructure that can be used by applications 1020 and / or other software modules. For example, framework 1018 can provide various graphical user interface (GUI) functions, advanced resource management, or advanced positioning services. Framework 1018 can provide a wide range of other APIs for applications 1020 and / or other software modules.
[0080] Applications 1020 include built-in applications 1040 and / or third-party applications 1042. Examples of built-in applications 1040 may include, but are not limited to, contact applications, browser applications, location applications, media applications, messaging applications, and / or game applications. Third-party applications 1042 may include any application developed by an entity other than the vendor of a particular platform. Applications 1020 may use functions available via OS 1014, library 1016, framework 1018, and presentation layer 1044 to create a user interface that interacts with a user.
[0081] Some software architectures use virtual machines, as exemplified by virtual machine 1048. Virtual machine 1048 provides an execution environment within which applications / modules can run, just as they would on a hardware machine (e.g., Fig.10 The virtual machine 1048 may be hosted by a host OS (e.g., OS 1014) or a hypervisor and may have a hypervisor 1046 that manages the operation of the virtual machine 1048 and interoperation with the host operating system. A software architecture that may be different from the software architecture 1002 outside the virtual machine runs within the virtual machine 1048 such as an OS 1050, a library 1052, a framework 1054, an application 1056, and / or a presentation layer 1058.
[0082] Fig.11 1 is a block diagram illustrating components of an exemplary machine 1100 configured to read instructions from a machine-readable medium (e.g., a machine-readable storage medium) and perform any of the features described herein. The exemplary machine 1100 has the form of a computer system within which instructions 1116 (e.g., in the form of software components) for causing the machine 1100 to perform any of the features described herein can be run. As such, the modules or components described herein can be implemented using the instructions 1116. The instructions 1116 can cause an unprogrammed and / or unconfigured machine 1100 to work as a specific machine configured to perform the described features. The machine 1100 can be configured to operate as a standalone device, or can be coupled to (e.g., networked to) other machines. In a networked deployment, the machine 1100 can operate as a server machine or a client machine in a server-client network environment, or as a node in a peer-to-peer or distributed network environment. The machine 1100 may be embodied as, for example, a server computer, a client computer, a personal computer (PC), a tablet computer, a laptop computer, a netbook, a set-top box (STB), a gaming and / or entertainment system, a smart phone, a mobile device, a wearable device (e.g., a smart watch), and an Internet of Things (IoT) device. In addition, while only a single machine 1100 is shown, the term "machine" includes a collection of machines that individually or jointly execute instructions 1116.
[0083] The machine 1100 may include a processor 1110, a memory 1130, and I / O components 1150, which may be communicatively coupled via, for example, a bus 1102. The bus 1102 may include multiple buses that couple various elements of the machine 1100 via various bus technologies and protocols. In an example, the processor 1110 (e.g., including a central processing unit (CPU), a graphics processing unit (GPU), a digital signal processor (DSP), an ASIC, or a suitable combination thereof) may include one or more processors 1112a to 1112n that may execute instructions 1116 and process data. In some examples, one or more processors 1110 may execute instructions provided or identified by one or more other processors 1110. The term "processor" includes a multi-core processor having several cores that may execute instructions simultaneously. Although Fig.11 Multiple processors are shown, but machine 1100 may include a single processor with a single core, a single processor with multiple cores (e.g., a multi-core processor), multiple processors with a single core, multiple processors with multiple cores, or any combination thereof. In some examples, machine 1100 may include multiple processors distributed across multiple machines.
[0084] The memory / storage device 1130 may include a main memory 1132, a static memory 1134 or other memory, and a storage unit 1136, all of which may be accessed by the processor 1110 (e.g., via the bus 1102). The storage unit 1136 and the memory 1132, 1134 store instructions 1116 embodying any one or more of the functions described herein. The memory / storage device 1130 may also store temporary data, intermediate data, and / or long-term data for the processor 1110. The instructions 1116 may also reside, in whole or in part, within the memory 1132, 1134, within the storage unit 1136, within at least one of the processors 1110 (e.g., within a command buffer or cache memory), within at least one of the I / O components 1150, or within any suitable combination thereof during execution thereof. Accordingly, memories 1132, 1134, storage unit 1136, memory within processor 1110, and memory within I / O component 1150 are all examples of machine-readable media.
[0085] As used herein, "machine-readable medium" refers to a device that can temporarily or permanently store instructions and data that cause the machine 1100 to operate in a specific manner. As used herein, the term "machine-readable medium" does not include transient electrical or electromagnetic signals themselves (e.g., on a carrier wave propagating through a medium); the term "machine-readable medium" can therefore be considered to be tangible and non-transient. Non-limiting examples of non-transient tangible machine-readable media can include, but are not limited to, non-volatile memory (such as flash memory or read-only memory (ROM)), volatile memory (such as static random access memory (RAM) or dynamic RAM), buffer memory, cache memory, optical storage media, magnetic storage media and devices, network-accessible or cloud storage devices, other types of storage devices, and / or any suitable combination thereof. The term "machine-readable medium" applies to a single medium or a combination of multiple media used to store instructions (e.g., instructions 1116) for execution by the machine 1100, so that the instructions, when executed by one or more processors 1110 of the machine 1100, cause the machine 1100 to perform one or more of the features described herein. Thus, a “machine-readable medium” may refer to a single storage device as well as a “cloud-based” storage system or storage network that includes multiple storage devices or devices.
[0086] I / O components 1150 may include a wide variety of hardware components suitable for receiving input, providing output, generating output, transmitting information, exchanging information, capturing measurements, etc. The specific I / O components 1150 included in a particular machine will depend on the type and / or function of the machine. For example, a mobile device (e.g., a mobile phone) may include a touch input device, while a headless server or IoT device may not include such a touch input device. Fig.11 The specific examples of I / O components shown in are not limiting in any way, and other types of components may be included in the machine 1100. The grouping of the I / O components 1150 is only to simplify the discussion, and the grouping is not limiting in any way. In various examples, the I / O components 1150 may include a user output component 1152 and a user input component 1154. The user output component 1152 may include, for example, a display component (e.g., a liquid crystal display (LCD) or a projector) for displaying information, an acoustic component (e.g., a speaker), a tactile component (e.g., a vibration motor or a force feedback device), and / or other signal generators. The user input component 1154 may include, for example, an alphanumeric input component (e.g., a keyboard or a touch screen), a pointing component (e.g., a mouse device, a touch pad, or other pointing tool), and / or a tactile input component (e.g., a physical button or a touch screen that provides the location and / or force of a touch or touch gesture) configured to receive various user inputs (such as commands and / or selections).
[0087] In some examples, I / O component 1150 may include biometric component 1156 and / or location component 1162, along with a wide range of other environmental sensor components. Biometric component 1156 may include, for example, components for detecting body expressions (e.g., facial expressions, vocal expressions, gestures or body postures, or eye tracking), measuring biosignals (e.g., heart rate or brain waves), and identifying people (e.g., through voice, retinal and / or facial recognition). Location component 1162 may include, for example, a location sensor (e.g., a global positioning system (GPS) receiver), an altitude sensor (e.g., a barometric pressure sensor, from which altitude can be derived), and / or an orientation sensor (e.g., a magnetometer).
[0088] The I / O components 1150 may include a communication component 1164 that implements a wide variety of technologies that can be used to couple the machine 1100 to the network 1170 and / or the device 1180 via corresponding communication couplings 1172 and 1182. The communication component 1164 may include one or more network interface components or other appropriate devices for interfacing with the network 1170. The communication component 1164 may include, for example, components suitable for providing the following communications: wired communication, wireless communication, cellular communication, near field communication (NFC), Bluetooth communication, Wi-Fi, and / or communication via other modalities. The device 1180 may include other machines or various peripheral devices (e.g., coupled via USB).
[0089] In some examples, the communication component 1164 can detect an identifier or include a component suitable for detecting an identifier. For example, the communication component 1164 can include a radio frequency identification (RFID) tag reader, an NFC detector, an optical sensor (e.g., a one-dimensional or multi-dimensional barcode or other optical code), and / or an acoustic detector (e.g., a microphone to identify an audio signal with a tag). In some examples, location information can be determined based on information from the communication component 1162, such as, but not limited to, a geographic location obtained through an Internet Protocol (IP) address, a location obtained through Wi-Fi, NFC, Bluetooth or other wireless sites and / or signal triangulation.
[0090] Although various embodiments have been described, these descriptions are intended to illustrate rather than to constitute limitations, and it should be understood that within the scope of the embodiments, many other embodiments are also possible. Although many possible combinations of features are shown in the drawings and discussed in this detailed description, many other combinations of disclosed features are also possible. Unless specifically limited, any feature of any embodiment can be used in combination with or replaced by any other feature or element in any other embodiment. Therefore, it should be understood that any feature of the features shown and / or discussed in this disclosure can be implemented together in any appropriate combination. Accordingly, unless the attached claims and their equivalents are considered, the embodiments are not subject to any restrictions. Moreover, various modifications and changes can be made within the scope of the attached claims.
[0091] Although the above describes what is considered to be the best mode and / or other examples, it should be understood that various modifications may be made therein, and the subject matter disclosed herein may be implemented in various forms and examples, and the teachings may be used in many applications, only some of which are described herein. The following claims are intended to assert the rights to any and all applications, modifications, and variations that fall within the substantive scope of the present teachings.
[0092] Unless otherwise indicated, all measurements, values, ratios, positions, sizes, dimensions and other specifications set forth in this specification (including the claims that follow) are approximate rather than exact and are intended to have a reasonable range compatible with the functions to which they are related and the common practices in the art to which they belong.
[0093] The scope of protection is limited only by the claims now attached. The scope is intended and should be interpreted to have a breadth consistent with the ordinary meaning of the language used in the claims (when considering this specification and subsequent examination history interpretation), and to encompass all structural and functional equivalents. Notwithstanding the foregoing, no claim is intended to cover subject matter that does not satisfy the requirements of Sections 101, 102, or 103 of the Patent Act, nor should it be interpreted in such a manner. Any unintended coverage of such subject matter is hereby disclaimed.
[0094] Except as stated immediately above, nothing that has been stated or illustrated is intended or should be construed as causing any component, step, feature, object, benefit, advantage, or equivalent to be dedicated to the public, whether or not it is recited in the claims.
[0095] It should be understood that the terms and expressions used in this article have the general meaning given to such terms and expressions relative to the corresponding fields of their research and study, except that the specific meanings are otherwise set forth herein. Relational terms, such as first and second, etc., can be used solely to distinguish one entity or action from another entity or action, without necessarily requiring or implying any actual such relationship or order between such entities or actions. The terms "include", "comprises" or any other variation thereof are intended to cover non-exclusive inclusion, so that the process, method, product or equipment including the listed elements not only includes these elements, but also may include other elements that are not explicitly listed or non-inherent in such processes, methods, products or equipment. Elements modified with singular articles in the absence of other constraints do not exclude the presence of additional equivalent elements in the process, method, product or equipment including the elements.
[0096] The purpose of providing a summary of the specification is to allow the reader to quickly understand the essence of the technical disclosure. The summary is submitted with the understanding that it should not be used to interpret or limit the scope and meaning of the claims. In addition, in the previous detailed description section, it can be seen that various features are grouped together in each example to make the disclosure smooth. This method of disclosure should not be interpreted as reflecting the following intention: the claims require more features than those explicitly cited in each claim. On the contrary, as reflected in the following claims, the features on which the subject matter of the present invention relies may be less than all the features of a single disclosed example. Therefore, the following claims are hereby incorporated into the detailed description section, wherein each claim itself represents an independently claimed subject matter.
Claims
1. An automatic repair and recovery system, comprising: processor; as well as A computer readable medium comprising instructions which, when executed by the processor, cause the processor to: receiving, at a remote cloud service over a communications network, synchronization data for a first file from a first client device during a synchronization session, the synchronization data indicating that the first client device is associated with a likelihood of being infected by malware; determining, at the remote cloud service in response to receiving the synchronization data, that the first client device has been infected by malware; accessing first user account information associated with the first client device to identify a remediation action that has been approved for automatic invocation on the first client device in response to determining that the first client device has been infected by malware; automatically calling, on the first client device, the repair action that has been approved to be automatically called for repairing the first client device; confirming, at the remote cloud service, that the repair of the first client device has been successfully completed; determining an initial infection time when an infected version of the first file was initially submitted for synchronization with the remote cloud service based on an examination of a synchronization history of the first file; and The first file on the client device is automatically restored by identifying, at the remote cloud service, a first version of the first file that was synchronized prior to the initial infection time and replacing the infected version with the first version.
2. The system according to claim 1, wherein: The malware is one of the following: ransomware, spyware, adware, virus, or worm.
3. The system according to claim 1, wherein: An anti-virus service is installed locally on the first client device.
4. The system according to claim 1, wherein: The instructions also cause the processor to automatically restore the copy of the first file within the remote cloud storage device by reverting the infected version stored in the remote cloud storage device to the first version.
5. The system according to claim 1, wherein: A plurality of files on the first client device are damaged by malware, and wherein the instructions further cause the processor to automatically recover a copy of each of the plurality of files within a remote cloud storage device by reverting an infected version of each damaged file to a version of the file that was synchronized prior to the initial infection time.
6. The system according to claim 1, wherein: The first version corresponds to a version of the first file that was synchronized during a synchronization session that occurred at least a predetermined buffer period prior to the initial infection time.
7. The system according to claim 1, wherein: The instructions also cause the processor to receive, at the remote cloud service, authorization from a user account associated with the first client device to enable automatic recovery of files on the client device.
8. The system according to claim 7, wherein: The authorization is obtained before receiving the synchronization data for the first file.
9. The system according to claim 7, wherein: The authorization is obtained in response to a request from the remote cloud service after determining that the first client device has been infected with malware.
10. An automatic repair and recovery method, comprising: receiving, at a remote cloud service over a communications network, synchronization data for a first file from a first client device during a synchronization session, the synchronization data indicating that the first client device is associated with a likelihood of being infected by malware; determining, at the remote cloud service in response to receiving the synchronization data, that the first client device has been infected by malware; accessing first user account information associated with the first client device to identify a remediation action that has been approved for automatic invocation on the first client device in response to determining that the first client device has been infected by malware; automatically calling, on the first client device, the repair action that has been approved to be automatically called for repairing the first client device; confirming, at the remote cloud service, that the repair of the first client device has been successfully completed; determining an initial infection time when an infected version of the first file was initially submitted for synchronization with the remote cloud service based on an examination of a synchronization history of the first file; and The first file on the client device is automatically restored by identifying, at the remote cloud service, a first version of the first file that was synchronized prior to the initial infection time and replacing the infected version with the first version.
11. The method according to claim 10, wherein: A plurality of files on the first client device are compromised by malware, and wherein the first version corresponds to a version of the first file that was synchronized during a synchronization session that occurred before an earliest initial infection time among the plurality of files.
12. The method of claim 10, further comprising automatically restoring the copy of the first file within a remote cloud storage device by reverting the infected version stored in the remote cloud storage device to the first version.
13. The method according to claim 10, wherein: The first version corresponds to a most recent version of the first file that was synchronized before the initial infection time.
14. The method according to claim 10, wherein: The first version corresponds to a version of the first file that was synchronized during a synchronization session that occurred at least a predetermined buffer period prior to the initial infection time.
