Systems and methods for monitoring attacks to devices

1. A method comprising:

retrieving a device tree binary from a system, wherein the device tree binary is a data structure describing one or more hardware components of the system at an initial boot stage of the system;

generating a golden copy of the device tree binary of the system, wherein the golden copy is a fixed known good copy of the device tree binary at the initial boot stage of the system;

storing the golden copy of the device tree binary of the system in a trusted execution environment in the system;

initiating a timer and determining whether a running copy of the device tree binary of the system is received or generated before the timer expires;

in response to a determination that the running copy of the device tree binary has been received before the timer expires or that the device tree binary has been generated before the timer expires, identifying whether one or more parameters of the running copy of the device tree binary of the system are different from corresponding parameters of the golden copy by comparing the running copy with the golden copy; and

performing a corrective action responsive to an indication that at least one of the one or more parameters of the running copy are different from the corresponding parameters of the golden copy.

2. The method of claim 1 , wherein performing the corrective action includes at least one of:

quarantining a component of the system associated with the one or more parameters;

evaluating each of the one or more parameters of the running copy identified as different from the corresponding parameters of the golden copy; or

notifying a user of the system.

3. The method of claim 1 , further comprising generating the running copy of the device tree binary on the system.

4. The method of claim 3 , wherein generating the running copy of the device tree binary further comprises recording one or more parameters associated with one or more components of the system, wherein the one or more parameters are presented in a kernel pseudo file.

5. The method of claim 1 , further comprising receiving the running copy of the device tree binary from a non-trusted execution environment of the system.

6. The method of claim 1 , further comprising determining that the timer has been attacked based on an indication that the running copy of the device tree binary has not been generated or received before the timer expired.

7. A system for detecting an attack to an internet-of-things (IoT) enabled device, the system comprising:

one or more memory devices having instructions stored thereon that, when executed by one or more processors, cause the one or more processors to perform operations comprising:

loading an operating system in a trusted execution environment of a system, wherein at least part of the operating system is used as a root of trust;

retrieving a device tree binary of the system, wherein the device tree binary is a data structure describing one or more hardware components of the system at an initial boot stage of the system;

generating a golden copy of the device tree binary of the system, wherein the golden copy is a fixed known good copy of the device tree binary at the initial boot stage of the system;

storing the golden copy of the device tree binary of the system in the trusted execution environment;

initiating a timer and determining whether a running copy of the device tree binary of the system is received or generated before the timer expires;

in response to a determination that the running copy of the device tree binary has been received before the timer expires or that the device tree binary has been generated before the timer expires, identifying whether one or more parameters of the running copy of the device tree binary of the system are different from corresponding parameters of the golden copy by comparing the running copy with the golden copy; and

performing a corrective action responsive to an indication that at least one of the one or more parameters of the running copy are different from the corresponding parameters of the golden copy.

8. The system of claim 7 , the operations further comprising decrypting the device tree binary of the system.

9. The system of claim 7 , wherein performing the corrective action includes at least one of:

quarantining a component of the system associated with the one or more parameters;

evaluating each of the one or more parameters of the running copy identified as different from the corresponding parameters of the golden copy; or

notifying a user of the system.

10. The system of claim 7 , the operations further comprising generating the running copy of the device tree binary on the system.

11. The system of claim 10 , wherein generating the running copy of the device tree binary further comprises recording one or more parameters associated with one or more components of the system, wherein the one or more parameters are presented in a kernel pseudo file.

12. The system of claim 7 , the operations further comprising receiving the running copy of the device tree binary from a non-trusted execution environment of the IoT enabled device.

13. The system of claim 7 , the operations further comprising determining that the timer has been attacked based on an indication that the running copy of the device tree binary has not been generated or received before the timer expired.

14. A method comprising:

loading an operating system in a trusted execution environment of a system, wherein at least part of the operating system is used as a root of trust;

retrieving a device tree binary of the system, wherein the device tree binary is a data structure describing one or more hardware components of the system at an initial boot stage of the system;

generating a golden copy of the device tree binary of the system, wherein the golden copy is a fixed known good copy of the device tree binary at the initial boot stage of the system;

storing the golden copy of the device tree binary of the system in the trusted execution environment;

initiating a timer and determining whether a running copy of the device tree binary of the system is received or generated before the timer expires;

in response to a determination that the running copy of the device tree binary has been received before the timer expires or that the device tree binary has been generated before the timer expires, identifying whether one or more parameters of the running copy of the device tree binary of the system are different from corresponding parameters of the golden copy by comparing the running copy with the golden copy; and

performing a corrective action responsive to an indication that at least one of the one or more parameters of the running copy are different from the corresponding parameters of the golden copy.

15. The method of claim 14 , wherein performing the corrective action includes at least one of:

quarantining a component of the system associated with the one or more parameters;

evaluating each of the one or more parameters of the running copy identified as different from the corresponding parameters of the golden copy; or

notifying a user of the system.

16. The method of claim 14 , further comprising decrypting the device tree binary of the system, wherein the device tree binary is a data structure describing one or more hardware components of the system.

17. The method of claim 14 , further comprising generating the running copy of the device tree binary on the system.

18. The method of claim 17 , wherein generating the running copy of the device tree binary further comprises recording one or more parameters associated with one or more components of the system, wherein the one or more parameters are presented in a kernel pseudo file.

19. The method of claim 14 , further comprising:

performing, based on the determination that the running copy is not received or generated before the timer expires, a corrective action.