Secure system for allowing the execution of authorized computer program code

1. A method comprising:

maintaining, by a kernel mode driver of a computer system, a whitelist containing cryptographic hash values of code modules that are approved for loading into memory of the computer system and execution on the computer system (“approved code modules”), wherein at least a subset of the cryptographic hash values has been included within the whitelist based upon results of application of one or more behavior analysis techniques to a corresponding subset of code modules;

monitoring, by the kernel mode driver, a set of events occurring within one or more of a file system accessible by the computer system and an operating system that manages resources of the computer system;

responsive to observation, by the kernel mode driver, of an event of the set of events relating to a code module, causing, by the kernel mode driver, a cryptographic hash value of the code module to be authenticated with reference to the whitelist; and

allowing the code module to be loaded and executed within the computer system if the cryptographic hash value matches one of the cryptographic hash values of approved code modules within the whitelist.

2. The method of claim 1 , wherein a behavior analysis technique of the one or more behavior analysis techniques comprises sandboxing.

3. The method of claim 2 , wherein the code module comprises an executable code module.

4. The method of claim 2 , wherein the code module comprises a dynamically-linked library file.

5. The method of claim 2 , wherein the code module comprises a Java applet.

6. The method of claim 2 , wherein the code module comprises JavaScript.

7. The method of claim 1 , wherein the whitelist comprises a multi-level whitelist including (i) a global whitelist database remote from the computer system and maintained by a trusted service provider and (ii) a local whitelist database containing at least a subset of the set of content of the global whitelist database.

8. The method of claim 1 , wherein the cryptographic hash value is computed using Message Digest #5 (MD-5).

9. The method of claim 1 , wherein the cryptographic hash value is computed using a Secure Hash Algorithm (SHA).

10. The method of claim 1 , wherein said monitoring a set of events occurring within one or more of a file system accessible by the computer system and an operating system that manages resources of the computer system comprises monitoring operating system process creation or module load activity.

11. The method of claim 10 , wherein said monitoring operating system process creation or module load activity comprises an operating system module load activity monitor intercepting module load activity by running processes within the computer system by hooking to an application programming interface (API) call of the operating system and temporarily turning control over to the kernel mode driver.

12. A non-transitory program storage device readable by a computer system, tangibly embodying a program of instructions executable by one or more computer processors of the computer system to perform a method for authenticating code modules, the method comprising:

maintaining, by a kernel mode driver of the computer system, a whitelist containing cryptographic hash values of code modules that are approved for loading into memory of the computer system and execution on the computer system (“approved code modules”), wherein at least a subset of the cryptographic hash values has been included within the whitelist based upon results of application of one or more behavior analysis techniques to a corresponding subset of code modules;

monitoring, by the kernel mode driver, a set of events occurring within one or more of a file system accessible by the computer system and an operating system that manages resources of the computer system;

responsive to observation, by the kernel mode driver, of an event of the set of events relating to a code module, causing, by the kernel mode driver, a cryptographic hash value of the code module to be authenticated with reference to the whitelist; and

allowing the code module to be loaded and executed within the computer system if the cryptographic hash value matches one of the cryptographic hash values of approved code modules within the whitelist.

13. The non-transitory program storage device of claim 12 , wherein a behavior analysis technique of the one or more behavior analysis techniques comprises sandboxing.

14. The non-transitory program storage device of claim 13 , wherein the code module comprises an executable code module, a dynamically-linked library file, a Java applet or JavaScript.

15. The non-transitory program storage device of claim 12 , wherein the whitelist comprises a multi-level whitelist including (i) a global whitelist database remote from the computer system and maintained by a trusted service provider and (ii) a local whitelist database containing at least a subset of the set of content of the global whitelist database.

16. The non-transitory program storage device of claim 12 , wherein the cryptographic hash value is computed using Message Digest #5 (MD-5).

17. The non-transitory program storage device of claim 12 , wherein the cryptographic hash value is computed using a Secure Hash Algorithm (SHA).

18. The non-transitory program storage device of claim 12 , wherein said monitoring a set of events occurring within one or more of a file system accessible by the computer system and an operating system that manages resources of the computer system comprises monitoring operating system process creation or module load activity.

19. The non-transitory program storage device of claim 18 , wherein said monitoring operating system process creation or module load activity comprises an operating system module load activity monitor intercepting module load activity by running processes within the computer system by hooking to an application programming interface (API) call of the operating system and temporarily turning control over to the kernel mode driver.