Ransomware detection using file replication logs
In one embodiment, a device in a network obtains log data regarding replication of files stored on an endpoint client to a file replication service. The device tracks, based on the obtained logs, encryption changes to the files that convert the files from unencrypted files to encrypted files. The device determines that the tracked encryption changes to the files are indicative of a ransomware infection on the endpoint client. The device initiates a mitigation action regarding the ransomware infection.
1. A method comprising:
obtaining, by a device in a network, log data regarding replication of files stored on an endpoint client to a file replication service;
tracking, by the device and based on the obtained logs, encryption changes to the files that convert the files from unencrypted files to encrypted files;
determining, by the device, that the tracked encryption changes to the files are indicative of a ransomware infection on the endpoint client; and
initiating, by the device, a mitigation action regarding the ransomware infection.
2. The method as in claim 1 , wherein the mitigation action comprises reverting the encrypted files to unencrypted versions of the files previously stored by the file replication service.
3. The method as in claim 1 , wherein the mitigation action comprises sending a ransomware detection alert to a user interface.
4. The method as in claim 1 , wherein obtaining the log data comprises:
obtaining the log data via an application programming interface (API) associated with the file replication service.
5. The method as in claim 1 , wherein determining that the tracked encryption changes to the files are indicative of a ransomware infection on the endpoint client comprises:
computing a number or rate of the files converted from unencrypted files to encrypted files; and
making a determination that the computed number or rate is indicative of a ransomware infection on the endpoint client.
6. The method as in claim 1 , wherein obtaining the log data comprises:
obtaining traffic log data regarding network traffic between the endpoint client and the file replication service.
7. The method as in claim 1 , wherein the file replication service is a cloud service, and wherein the device provides the replication service to the endpoint client.
8. The method as in claim 1 , wherein the log data is obtained from the file replication service.
9. An apparatus, comprising:
one or more network interfaces to communicate with a network;
a processor coupled to the network interfaces and configured to execute one or more processes; and
a memory configured to store a process executable by the processor, the process when executed configured to:
obtain log data regarding replication of files stored on an endpoint client to a file replication service;
track, based on the obtained logs, encryption changes to the files that convert the files from unencrypted files to encrypted files;
determine that the tracked encryption changes to the files are indicative of ransomware infection on the endpoint client; and
initiate a mitigation action regarding the ransomware infection.
10. The apparatus as in claim 9 , wherein the mitigation action comprises reverting the encrypted files to unencrypted versions of the files previously stored by the file replication service.
11. The apparatus as in claim 9 , wherein the mitigation action comprises sending a ransomware detection alert to a user interface.
12. The apparatus as in claim 9 , wherein the apparatus obtains the log data by:
obtaining the log data via an application programming interface (API) associated with the file replication service.
13. The apparatus as in claim 9 , wherein the apparatus determines that the tracked encryption changes to the files are indicative of a ransomware infection on the endpoint client by:
computing a number or rate of the files converted from unencrypted files to encrypted files; and
making a determination that the computed number or rate is indicative of a ransomware infection on the endpoint client.
14. The apparatus as in claim 9 , wherein the apparatus obtains the log data by:
obtaining traffic log data regarding network traffic between the endpoint client and the file replication service.
15. The apparatus as in claim 9 , wherein the file replication service is a cloud service.
16. The apparatus as in claim 9 , wherein the log data is obtained from the file replication service.
17. A tangible, non-transitory, computer-readable medium storing program instructions that cause a device in a network to execute a process comprising:
obtaining, by the device, log data regarding replication of files stored on an endpoint client to a file replication service;
tracking, by the device and based on the obtained logs, encryption changes to the files that convert the files from unencrypted files to encrypted files;
determining, by the device, that the tracked encryption changes to the files are indicative of a ransomware infection on the endpoint client; and
initiating, by the device, a mitigation action regarding the ransomware infection.
18. The computer-readable medium as in claim 17 , wherein the mitigation action comprises reverting the encrypted files to unencrypted versions of the files previously stored by the file replication service.
19. The computer-readable medium as in claim 17 , wherein determining that the tracked encryption changes to the files are indicative of a ransomware infection on the endpoint client comprises:
computing a number or rate of the files converted from unencrypted files to encrypted files; and
making a determination that the computed number or rate is indicative of a ransomware infection on the endpoint client.
20. The computer-readable medium as in claim 17 , wherein obtaining the log data comprises:
obtaining the log data via an application programming interface (API) associated with the file replication service.