Intelligent event collection for rolling back an endpoint state in response to malware
An anti-malware application detects and remediates malware. The anti-malware application detects an event associated with a process and determines if the event matches an entry in an exclusions list. If the event is absent from the exclusions list, the anti-malware application monitors the operation of the process, logs the event data in an event log, and sends the event to a server to determine whether the process corresponds to malware. The anti-malware application updates the exclusions list based on the logged event if the process does not correspond to malware. The anti-malware application restores a file edited by the process to the saved copy of the original file prior to the file being edited by the process if the process corresponds to malware.
1. A method for detecting malware comprising:
detecting an event associated with a process performing an operation on a file;
determining if the event associated with the process matches an event in an exclusions list;
responsive to determining that the event associated with the process is absent from the exclusions list, monitoring the operation of the process comprising saving a plurality of event data describing a plurality of events associated with the process on a client device and sending the plurality of event data to a server;
responsive to detecting an opening of an original file by the process for editing, saving a copy of the original file prior to the original file being edited by the process;
receiving, by the client device, an indication from the server of whether the process corresponds to malware based on whether the plurality of event data includes a pattern of events indicative of malware; and
responsive to receiving an indication that the process corresponds to malware, restoring a file edited by the process to the saved copy of the original file prior to the file being edited by the process.
2. The method of claim 1 , further comprising:
detecting a second event associated with a second process performing a second operation on a second file;
determining if the second event associated with the second process matches an entry in the exclusions list;
responsive to determining that the second event associated with the second process is absent from the exclusions list:
saving second event data associated with the second process on the client device by logging the second event data in an event log, and
sending the second event data to the server;
receiving, by the client device, an indication from the server of whether the second process corresponds to malware; and
responsive to receiving an indication that the second process does not correspond to malware, updating the exclusions list based on the logged event data of the second process.
3. The method of claim 2 , wherein the exclusions list includes an entry excluding events associated with a trusted process and determining if the event matches the entry in the exclusions list comprises:
determining that an identifier of the process matches an identifier of the trusted process.
4. The method of claim 2 , wherein the exclusions list includes an entry excluding events associated with a trusted process operating on a file having a particular characteristic and determining if the event matches the entry in the exclusions list comprises:
determining that an identifier of the process matches an identifier of the trusted process and that the operated-on file has the particular file characteristic.
5. The method of claim 4 , wherein the particular file characteristic is one among a file type and a file directory.
6. The method of claim 2 , wherein updating the exclusions list is performed periodically after a first period of time, the method further comprising:
logging additional event data describing additional events in the event log occurring over a second period of time greater than the first period of time; and
purging the event data occurring over the second period of time that is greater in age than the first period of time from the event log.
7. The method of claim 2 , wherein updating the exclusions list comprises:
maintaining a count of logged events corresponding to historical operations by the process performed on files having a particular predefined characteristic; and
responsive to the count exceeding a threshold, adding an entry to the exclusions list to exclude future operations by the process on files having the particular predefined characteristic.
8. A non-transitory computer-readable storage medium storing instructions for detecting malware, the instructions when executed by a processor cause the processor to perform steps including:
detecting an event associated with a process performing an operation on a file;
determining if the event associated with the process matches an event in an exclusions list;
responsive to determining that the event associated with the process is absent from the exclusions list, monitoring the operation of the process comprising saving a plurality of event data describing a plurality of events associated with the process on a client device and sending the plurality of event data to a server;
responsive to detecting an opening of an original file by the process for editing, saving a copy of the original file prior to the original file being edited by the process;
receiving, by the client device, an indication from the server of whether the process corresponds to malware based on whether the plurality of event data includes a pattern of events indicative of malware; and
responsive to receiving an indication that the process corresponds to malware, restoring a file edited by the process to the saved copy of the original file prior to the file being edited by the process.
9. The non-transitory computer-readable storage medium of claim 8 , the instructions further including:
detecting a second event associated with a second process performing a second operation on a second file;
determining if the second event associated with the second process matches an event in the exclusions list;
responsive to determining that the second event associated with the second process is absent from the exclusions list:
saving second event data associated with the second process on the client device by logging the second event data in an event log, and
sending the second event data to the server;
receiving, by the client device, an indication from the server of whether the second process corresponds to malware; and
responsive to receiving an indication that the second process does not correspond to malware, updating the exclusions list based on the logged event data of the second process.
10. The non-transitory computer-readable storage medium of claim 9 , wherein the exclusions list includes an entry excluding events associated with a trusted process and determining if the event matches the entry in the exclusions list comprises:
determining that an identifier of the process matches an identifier of the trusted process.
11. The non-transitory computer-readable storage medium of claim 9 , wherein the exclusions list includes an entry excluding events associated with a trusted process operating on a file having a particular characteristic and determining if the event matches the entry in the exclusions list comprises:
determining that an identifier of the process matches an identifier of the trusted process and that the operated-on file has the particular file characteristic.
12. The non-transitory computer-readable storage medium of claim 11 , wherein the particular file characteristic is one among a file type and a file directory.
13. The non-transitory computer-readable storage medium of claim 9 , wherein updating the exclusions list is performed periodically after a first period of time, the instructions further comprising:
logging additional event data describing additional events in the event log occurring over a second period of time greater than the first period of time; and
purging the event data occurring over the second period of time that is greater in age than the first period of time from the event log.
14. The non-transitory computer-readable storage medium of claim 9 ,
wherein updating the exclusions list comprises:
maintaining a count of logged events corresponding to historical operations by the process performed on files having a particular predefined characteristic; and
responsive to the count exceeding a threshold, adding an entry to the exclusions list to exclude future operations by the process on files having the particular predefined characteristic.
15. A computing system comprising:
a processor; and
a non-transitory computer-readable storage medium storing instructions for detecting malware, the instructions when executed by the processor cause the processor to perform steps including:
detecting an event associated with a process performing an operation on a file;
determining if the event associated with the process matches an event in an exclusions list;
responsive to determining that the event associated with the process is absent from the exclusions list, monitoring the operation of the process comprising saving a plurality of event data describing a plurality of events associated with the process on a client device and sending the plurality of event data to a server;
responsive to detecting an opening of an original file by the process for editing, saving a copy of the original file prior to the original file being edited by the process;
receiving, by the client device, an indication from the server of whether the process corresponds to malware based on whether the plurality of event data includes a pattern of events indicative of malware; and
responsive to receiving an indication that the process corresponds to malware, restoring a file edited by the process to the saved copy of the original file prior to the file being edited by the process.
16. The computing system of claim 15 , the instructions further including:
detecting a second event associated with a second process performing a second operation on a second file;
determining if the second event associated with the second process matches an event in the exclusions list;
responsive to determining that the second event associated with the second process is absent from the exclusions list:
saving second event data associated with the second process on the client device by logging the second event data in an event log, and
sending the second event data to the server;
receiving, by the client device, an indication from the server of whether the second process corresponds to malware; and
responsive to receiving an indication that the second process does not correspond to malware, updating the exclusions list based on the logged event data of the second process.
17. The computing system of claim 16 , wherein the exclusions list includes an entry excluding events associated with a trusted process and determining if the event matches the entry in the exclusions list comprises:
determining that an identifier of the process matches an identifier of the trusted process.
18. The computing system of claim 16 , wherein the exclusions list includes an entry excluding events associated with a trusted process operating on a file having a particular characteristic and determining if the event matches the entry in the exclusions list comprises:
determining that an identifier of the process matches an identifier of the trusted process and that the operated-on file has the particular file characteristic.
19. The computing system of claim 16 ,
wherein updating the exclusions list comprises:
maintaining a count of logged events corresponding to historical operations by the process performed on files having a particular predefined characteristic; and
responsive to the count exceeding a threshold, adding an entry to the exclusions list to exclude future operations by the process on files having the particular predefined characteristic.
20. The computing system of claim 16 ,
wherein updating the exclusions list is performed periodically after a first period of time, the instructions further comprising:
logging additional event data describing additional events in the event log occurring over a second period of time greater than the first period of time; and
purging the event data occurring over the second period of time that is greater in age than the first period of time from the event log.