System and method for using rules to protect against malware

1. A method for preventing a malicious or unwanted software function from acting upon an object within a computer system, the method being executed by one or more processors configured to perform a plurality of operations comprising:

determining a rule from a plurality of pre-existing rules that applies to an object within a computer system,

wherein each of the plurality of pre-existing rules is associated with a plurality of characteristics including: a platform indicator that specifies a type of platform on which an object to which the rule applies operates, an object type indicator that specifies a type of object to which the rule applies, an object indicator that specifies a specific object to which the rule applies, and a function type indicator that specifies a function type that triggers an action with regard to the object, and

wherein determining a rule that applies to the object includes determining a rule from the plurality of pre-existing rules that includes: a platform indicator that matches a platform on which the object operates, an object type indicator that matches an object type of the object, and an object indicator that matches the object;

associating object attributes with the object according to the rule, wherein the object attributes include a function type of the function type indicator and a classification that indicates a specific action to be performed with regard to the object;

detecting a software function attempting to act upon the object;

determining whether the detected software function matches the function type of the object attributes; and

performing the specific action when the detected software function matches the function type of the object attributes, wherein the specific of action relates to whether the detected software function will be allowed to act upon the object, and wherein the specific action performed is determined using the classification of the object attributes.

2. The method of claim 1 , wherein the specific action includes:

preventing the software function from acting upon the object when the classification indicates that the software function is to be prevented from acting upon the object;

allowing the software function to act upon the object when the classification indicates that the software function is allowed to act upon the object; and

seeking manual approval before allowing the software function to act upon the object when the classification indicates that manual approval is required before the software function is allowed to act upon the object.

3. The method of claim 2 , wherein the manual approval includes alerting at least one user that the software function requires review prior to acting upon the object.

4. The method of claim 1 , wherein the function type of the detected software function comprises one of:

an update function that attempts to update the object; or

a delete function that attempts to delete the object.

5. The method of claim 1 , wherein the object type of the object is one of a file object or a registry object.

6. The method of claim 1 , wherein the object indicator includes a path attribute identifying the object.

7. The method of claim 1 , wherein the rule includes a list of one or more specific processes, wherein the object attributes include identifiers for each of the one or more specific processes, and wherein performance of the specific action is dependent on whether the detected software function is a process listed on the list.

8. The method of claim 7 , wherein the detected software function has a function type matching the function type of the object attributes and the classification indicates that the detected software function should be prevented from acting upon the object, and wherein the specific action includes allowing the detected software function to act on the object when the detected software function is a process that is one of the one or more specific processes.

9. The method of claim 1 , wherein the rule includes an exception list specifying one or more exceptions, wherein each exception is one of the plurality of preexisting rules, wherein the detected software function has a function type matching the one or more attributes and wherein the specific action is altered by the one or more exceptions.

10. The method of claim 1 , further comprising creating a log entry when the specific action prevents the software function from operating on the object, wherein the log entry includes one or more of:

information regarding an identity of the detected software function;

an identity of the object; and

an identity of the rule.

11. A system for preventing a malicious or unwanted software function from acting upon an object within a computer system, the system comprising:

at least one memory device upon which the plurality of pre-existing rules are stored, wherein each of the plurality of pre-existing rules is associated with a plurality of characteristics including: a platform indicator that specifies a type of platform on which an object to which the rule applies operates; an object type indicator that specifies a type of object to which the rule applies, an object indicator that specifies a specific object to which the rule applies, and a function type indicator that specifies a function type that triggers an action with regard to the object; and

at least one computing device configured to:

determine a rule from the pre-existing plurality of rules that applies to the object within the computer system, wherein determination of the rule that applies to the object includes a determination of a rule from the plurality of pre-existing rules that includes: a platform indicator that matches a platform on which the object operates, an object type indicator that matches an object type of the object, and an object indicator that matches the object,

associate object attributes with the object according to the rule, wherein the object attributes include a function type of the function type indicator and a classification that indicates a specific action to be performed with regard to the object,

detect a software function attempting to act upon the object,

determine whether the detected software function matches the function type of the object attributes, and

perform the specific action when the detected software function matches the function type of the object attributes, wherein the specific of action relates to whether the detected software function will be allowed to act upon the object, and wherein the specific action performed is determined using the classification of the object attributes.

12. The system of claim 11 , wherein the specific action includes:

prevention of the software function from acting upon the object when the classification indicates that the software function is to be prevented from acting upon the object;

allowance of the software function to act upon the object when the classification indicates that the software function is allowed to act upon the object; and

acquisition of manual approval before allowing the software function to act upon the object when the classification indicates that manual approval is required before the software function is allowed to act upon the object.

13. The system of claim 11 , wherein the rule includes a list of one or more specific processes, wherein the object attributes include identifiers for each of the one or more specific processes, and wherein performance of the specific action is dependent on whether the detected software function is a process listed on the list.

14. The system of claim 13 , wherein the detected software function has a function type matching the function type of the object attributes and the classification indicates that the detected software function should be prevented from acting upon the object, and wherein the specific action includes allowance of the detected software function to act on the object when the detected software function is a process that is one of the one or more specific processes.

15. The system of claim 11 , wherein the at least one computing device is further configured to create a log entry when the specific action prevents the software function from operating on the object, wherein the log entry includes one or more of:

information regarding an identity of the detected software function;

an identity of the object; and

an identity of the rule.

16. A system for preventing a malicious or unwanted software action from being performed upon an object within a computer system, the system comprising:

at least one memory device upon which a plurality of pre-existing rules are stored, wherein each of the plurality of pre-existing rules is associated with a plurality of characteristics including a platform indicator that specifies a platform on which an object to which the rule applies operates, an object type indicator that specifies a type of object to which the rule applies, an object indicator that specifies a specific object to which the rule applies, and a function type indicator that specifies a function type that will be prevented from acting on the object; and at least one computing device configured to:

determine a rule from the plurality of pre-existing rules that applies to the object within the computer system, wherein determination of the rule that applies to the object includes a determination of a rule from the plurality of pre-existing rules that includes: a platform indicator that matches a platform on which the object operates, an object type indicator that matches an object type of the object, and an object indicator that matches the object

associate object attributes with the object according to the rule, wherein the plurality of characteristics of the rule further include a list of one or more specific processes of the specified function type that will not be prevented from acting on the object, wherein the object attributes include a function type of the function type indicator, a classification that indicates that the functions of the function type indicator should be prevented from acting upon the object, and a list of the one or more specific processes,

detect a software action attempting to act upon the object,

determine whether the detected software function matches the function type of the object attributes,

determine, when the detected software function matches the function type of the object attributes, whether the detected software function is one of the one or more specific processes,

prevent the detected software function from acting on the object when the detected software function matches the function type of the object attributes and is not one of the one or more specific processes, and

allow the detected software function to act on the object when the detected software function matches the function type of the object attributes and is one of the one or more specific processes.

17. The system of claim 16 , wherein the one or more characteristics of the rule further includes an exception list that specifies one or more exceptions, wherein each exception is one of the plurality of preexisting rules, and wherein the detected software function is allowed to act upon the object when the detected function has a function type matching the one or more attributes and at least one of the one or more exceptions applies to the detected software function.

18. The method of claim 1 , wherein associating object attributes with the object according to the rule further comprises associating one or more flags with the object.

19. The system of claim 11 , wherein the at least one computing device configured to associate object attributes with the object according to the rule is further configured to associate one or more flags with the object.