OS monitor
An in-vehicle communication network comprising a bus and at least one node connected to the bus; an in-vehicle network operating system (OS) that manages OS processes, to enable a processor to run the processes and execute their respective process codes; and a module hosted in the OS that is configured to monitor the OS and vet a process that the OS enables for running by a processor to determine if the process is potentially damaging.
1. An in-vehicle communication network comprising: a bus and at least one node connected to the bus; an in-vehicle network operating system (OS) that manages OS processes, to enable a processor to run the processes and execute their respective process codes; and a module hosted in the OS that is configured to monitor the OS and vet a process that the OS enables for running by a processor to determine if the process is potentially damaging.
2. The in-vehicle communication network according to claim 1 wherein the module is configured to prevent the process from having access to the network bus if the process is determined to be potentially damaging.
3. The in-vehicle communication network according to claim 1 wherein the module has a hook in at least one position of the OS that provides information to the module responsive to operation of the OS that the module processes to monitor the OS, the at least one position comprising at least one or any combination of more than one of: a fork ( ), exec ( ), spawn ( ), or open ( ).
4. The in-vehicle communication network according to claim 3 wherein processing the information comprises determining if all running threads of the process code being run are running from the code section of the process code.
5. The in-vehicle communication network according to claim 1 wherein vetting the process comprises determining if a copy of a process code of the process being run by the processor is a copy of process code of a known process.
6. The in-vehicle communication network according to claim 5 wherein determining if the copy is a copy of a known process comprises determining validity of a digital signature associated with the process.
7. The in-vehicle communication network according to claim 5 wherein vetting the process comprises determining if the copy of the process code being run by the processor is substantially the same as the copy of the process code in a secondary memory comprised in the in-vehicle network in which process codes for the processes are stored.
8. The in-vehicle communication network according to claim 7 wherein vetting the process comprises determining if all dynamic libraries associated with the copy of the process code being run are known and allowed.
9. The in-vehicle communication network according to claim 1 wherein the OS is an OS chosen from the group consisting of: QNX, Linux, or an Android OS.