Methods and systems to identify a compromised device through active testing
Methods and devices for determining whether a mobile device has been compromised. File tree structure information for the mobile device is obtained that details at least a portion of a tree-based structure of folders and files in a portion of memory. The file tree structure information is analyzed to determine that the mobile device has been compromised, has not been compromised, or might be compromised. Based on determining that the mobile device might be compromised, the mobile device is instructed to execute a restricted action. If the restricted action occurs on the mobile device then it is determined that the mobile device has been compromised. Based on that determination, an action is taken.
1 . A computer-implemented method of determining whether security of a mobile device is compromised, the method comprising:
determining that the mobile device might be compromised;
based on the determination that the mobile device might be compromised, carrying out a testing operation that comprises instructing the mobile device to run a process with an expected run-time;
comparing an actual time the process runs with the expected run-time;
determining that the security of the mobile device is compromised, in response to determining that the actual time the process runs deviates from the expected run time by more than a threshold; and
based on the determination that the security of the mobile device is compromised, taking an action.
2 . The computer-implemented method of claim 1 , further comprising:
obtaining file tree structure information for the mobile device, wherein the file tree structure information details at least a portion of a tree-based structure of folders and files in a portion of memory; and
analyzing the file tree structure information to determine that the mobile device might be compromised.
3 . The computer-implemented method of claim 1 , further comprising, in response to the determination that the mobile device might be compromised, instructing the mobile device to execute an operation carried out from within a first user profile included in the mobile device with respect to a file or folder associated with a second user profile included in the mobile device that should not be able to be carried out from within the first user profile.
4 . The computer-implemented method of claim 3 , wherein the determining that the mobile device is compromised comprises determining that the operation occurs on the mobile device.
5 . The computer-implemented method of claim 4 , wherein the operation comprises running through a list of protected systems calls.
6 . The computer-implemented method of claim 1 , further comprising, in response to the determination that the mobile device might be compromised, instructing the mobile device to evaluate whether tasks are scheduled and maintained in an expected manner.
7 . The computer-implemented method of claim 6 , wherein the instructing the mobile device to investigate the system settings to determine whether items have been modified in a way that is required to gain root access comprises determining whether developer options have been changed.
8 . The computer-implemented method of claim 1 , further comprising, in response to the determination that the mobile device might be compromised, instructing the mobile device to investigate system settings to determine whether items have been modified in a way that is required to gain root access.
9 . The computer-implemented method of claim 1 , further comprising instructing the mobile device to automatically cause input of a command line instruction at the mobile device.
10 . The method of claim 1 , wherein the determining that the security of the mobile device is compromised comprises determining that the mobile device is infected with malware, spyware, or a virus, and wherein the action comprises locking the mobile device, wiping the mobile device, or denying access to the mobile device.
11 . The method of claim 1 , wherein the threshold is a threshold amount of time.
12 . A computing device comprising:
a processor;
a memory storing processor-executable instructions that, when executed by the processor, cause the processor to:
determine that the mobile device might be compromised;
based on the determination that the mobile device might be compromised, carry out a testing operation that comprises instructing the mobile device to run a process with an expected run-time;
comparing an actual time the process runs with the expected run-time;
determine that security of the mobile device is compromised, in response to determining that the actual time the process runs deviates from the expected run time by more than a threshold; and
based on the determination that the security of the mobile device has been compromised, take an action.
13 . The computing device of claim 12 , wherein the instructions, when executed, further cause the processor to:
obtain file tree structure information for the mobile device, wherein the file tree structure information details at least a portion of a tree-based structure of folders and files in a portion of the memory; and
analyze the file tree structure information to determine that the mobile device might be compromised.
14 . The computing device of claim 12 , wherein the instructions, when executed, further cause the processor to, in response to the determination that the mobile device might be compromised, execute an operation carried out from within a first user profile included in the mobile device with respect to a file or folder associated with a second user profile included in the mobile device that should not be able to be carried out from within the first user profile.
15 . The computing device of claim 14 , wherein the determining that the mobile device is compromised comprises determining that the operation occurs on the mobile device.
16 . The computing device of claim 15 , wherein the operation comprises running through a list of protected systems calls.
17 . The computing device of claim 12 , wherein the instructions, when executed, further cause the processor to, in response to the determination that the mobile device might be compromised, instructing the mobile device to evaluate whether tasks are scheduled and maintained in an expected manner.
18 . The computing device of claim 12 , wherein the instructions, when executed, further cause the processor to, in response to the determination that the mobile device might be compromised, instructing the mobile device to investigate system settings to determine whether items have been modified in a way that is required to gain root access.
19 . The computing device of claim 18 , wherein the instructing the mobile device to investigate the system settings to determine whether items have been modified in a way that is required to gain root access comprises determining whether developer options have been changed.
20 . A non-transitory computer-readable storage medium storing instructions that, when executed by a processor of a mobile device, cause the processor to:
determine that the mobile device might be compromised;
based on the determination that the mobile device might be compromised, carry out a testing operation that comprises instructing the mobile device to run a process with an expected run-time;
compare an actual time the process runs with the expected run-time;
determine that security of the mobile device is compromised, in response to determining that the actual time the process runs deviates from the expected run time by more than a threshold; and
based on the determination that the security of the mobile device is compromised, take an action.