Method, apparatus, system, and computer readable medium for providing apparatus security

1. An apparatus comprising:

at least one processor; and

at least one memory, the at least one memory comprising instructions that when executed by the at least one processor, cause the apparatus to perform, at least, the following:

receive, at a security module, policy information associated with at least one security exception, wherein the policy information includes program dependent policy information associated with a program and based, at least in part, on one or more operational characteristics of the program, one of the operational characteristics including one of a number of external interfaces of the program, accessibility of code paths to manipulation by data passed through one or more of the external interfaces, a quality of code in the program, or a performance sensitivity of the program, and wherein the policy information comprises information indicative of a level of risk associated with the program;

determine that the at least one security exception should be monitored based, at least in part, on the program dependent policy information;

send a directive to an exception handler to provide an indication if the at least one security exception occurs;

receive the indication, from the exception handler, that the at least one security exception occurred;

determine, at the security module, an operation associated with the at least one security exception and based, at least in part, on the policy information; and

cause, by the security module, the operation to be performed, based at least in part, on a determination that the at least one security exception occurred.

2. The apparatus of claim 1 , wherein causation of the operation to be performed, based, at least in part, on determination that the at least one security exception occurred comprises sending, to the program, a directive instructing the program to perform the operation based, at least in part, on occurrence of the at least one security exception.

3. The apparatus of claim 1 , wherein the operation relates to at least one of, termination of the program, sending of an indication of the exception to the program, termination of propagation of the exception, sending information associated with the at least one security exception to a server, causing modification of, at least a portion of, the policy information.

4. The apparatus of claim 1 , wherein the policy information comprises program independent policy information.

5. The apparatus of claim 1 , wherein the at least one memory further comprises instructions to identify, by the security module, the program associated with causing occurrence of the at least one security exception, wherein determination of the operation is further based, at least in part, on the identification.

6. The apparatus of claim 1 , wherein the policy information comprises program independent policy information, wherein the determination

that the at least one security exception should be monitored is based, in part, on the program independent policy information.

7. The apparatus of claim 1 , wherein the policy information includes other program dependent policy information associated with one or more other programs, wherein the at least one memory further comprises instructions to:

determine that the at least one security exception should be monitored based, in part, on the other program dependent policy information.

8. The apparatus of claim 4 , wherein the program independent policy information further includes one or both of information relating to an operating environment of the apparatus and general information regarding security exceptions.

9. The apparatus of claim 1 , wherein the exception handler sends the indication in response to a hardware detection of the at least one security exception.

10. At least one non-transitory computer readable storage medium comprising instructions that, when executed, cause an apparatus to:

receive policy information associated with at least one security exception, wherein the policy information includes program dependent policy information associated with a program and based, at least in part, on one or more operational characteristics of the program, one of the operational characteristics including a number of external interfaces of the program, accessibility of code paths to manipulation by data passed through one or more of the external interfaces, a quality of code in the program, or a performance sensitivity of the program, and wherein the policy information comprises information indicative of a level of risk associated with the program;

determine that the at least one security exception should be monitored based, at least in part, on the program dependent policy information;

send a directive to an exception handler to provide an indication if the at least one security exception occurs;

receive the indication, from the exception handler, that the at least one security exception occurred;

determine an operation associated with the at least one security exception and based, at least in part, on the policy information; and

cause the operation to be performed, based at least in part, on a determination that the at least one security exception occurred.

11. The at least one non-transitory medium of claim 10 , wherein causation of the operation to be performed, based, at least in part, on the determination that the at least one security exception occurred comprises sending, to the program, a directive instructing the program to perform the operation based, at least in part, on occurrence of the at least one security exception.

12. The at least one non-transitory medium of claim 10 , wherein the instructions further cause the apparatus to identify the program associated with causing occurrence of the at least one security exception, wherein the determination of the operation is further based, at least in part, on the identification.

13. The at least one non-transitory medium of claim 10 , wherein the policy information comprises program independent policy information, wherein the determination

that the at least one security exception should be monitored is based, in part, on the program independent policy information.

14. The at least one non-transitory medium of claim 10 , wherein the policy information includes other program dependent policy information associated with one or more other programs, wherein the instructions further cause the apparatus to:

determine that at least one other security exception should be monitored based, at least in part, on the other program dependent policy information.

15. The at least one non-transitory medium of claim 10 , wherein the program dependent policy information further includes an identity of a source of the program.

16. The at least one non-transitory medium of claim 10 , wherein the operation relates to at least one of, termination of the program, sending of an indication of the exception to the program, termination of propagation of the exception, sending information associated with the at least one security exception to a server, causing modification of, at least a portion of, the policy information.

17. The at least one non-transitory medium of claim 10 , wherein the exception handler sends the indication in response to a hardware detection of the at least one security exception.

18. The at least one non-transitory medium of claim 17 , wherein the at least one security exception detected by hardware includes at least one of an out of bounds memory access, an attempt to execute an instruction stored in a memory region designated for non-executable information, or the program performing operations that exceed a privilege level associated with the program.

19. A method for providing apparatus security, comprising:

receiving policy information associated with at least one security exception, wherein the policy information includes program dependent policy information associated with a program and based, at least in part, on one or more operational characteristics of the program, one of the operational characteristics including a number of external interfaces of the program, accessibility of code paths to manipulation by data passed through one or more of the external interfaces, a quality of code in the program, or a performance sensitivity of the program, and wherein the policy information comprises information indicative of a level of risk associated with the program;

determining that the at least one security exception should be monitored based, at least in part, on the program dependent policy information;

sending a directive to an exception handler to provide an indication if the at least one security exception occurs;

receiving the indication, from the exception handler, that the at least one security exception occurred;

determining, by one or more hardware processors, an operation associated with the at least one security exception and based, at least in part, on the policy information; and

causing, by the one or more hardware processors, the operation to be performed, based at least in part, on a determination that the at least one security exception occurred.

20. The method of claim 19 , wherein causing the operation to be performed, based, at least in part, on the determination that the at least one security exception occurred comprises sending, to the program, a directive instructing the program to perform the operation based, at least in part, on occurrence of the at least one security exception.

21. The method of claim 19 , wherein the operation relates to at least one of, termination of the program, sending of an indication of the exception to the program, termination of propagation of the exception, sending information associated with the at least one security exception to a server, causing modification of, at least a portion of, the policy information.

22. The method of claim 19 , wherein the policy information comprises program independent policy information.

23. The method of claim 19 , further comprising identifying at least one program associated with causing occurrence of the at least one security exception, wherein determination of the operation is further based, at least in part, on the identification.

24. The method of any of claim 19 , wherein the policy information comprises program independent policy information, wherein the determination

that the at least one security exception should be monitored is based, at least in part, on the program independent policy information.

25. The method of claim 19 , wherein the policy information includes other program dependent policy information associated with one or more other programs, the method further comprising:

determining that the at least one security exception should be monitored based, in part, on the other program dependent policy information.