Behavioral threat detection engine
Examples of the present disclosure describe systems and methods for a behavioral threat detection engine. In examples, the behavioral threat detection engine manages execution of one or more virtual machines, wherein each virtual machine processes a rule in relation to a context. The behavioral threat detection engine uses any of a variety of techniques to identify when events occur. Accordingly, the behavioral threat detection engine provides event indications, in the form of event packets, to one or more virtual machines, such that corresponding rules are able to process the events accordingly. Eventually, a rule may make a determination as to the presence or absence of a behavior. As a result, execution of the associated virtual machine may be halted, thereby indicating to the behavioral threat detection engine that a determination has been made. Thus a behavioral threat detection engine employs a behavior-based approach to detecting malicious or potentially malicious behaviors.
1. A system comprising:
a processor; and
a non-transitory computer readable medium comprising instructions for:
evaluating a first rule in a rule data store to determine a first event associated with the first rule;
monitoring for an event indication associated with the first event;
when an event indication is detected, identifying the first rule associated with the received event indication;
generating an event packet based on the received event indication, the event packet comprising an identifier for the first event and a parameter relating to the first event;
providing the generated event packet to a rule virtual machine executing the first rule; and
performing an action based on an evaluation of the event by the rule virtual machine.
2. The system of claim 1 , wherein the instructions are further for initializing the rule virtual machine based on a second event associated with a second rule.
3. The system of claim 2 , wherein the second rule is a matching rule associated with multiple events.
4. The system of claim 1 , wherein the first event is a file event, a process event, or an event associated with a registry.
5. The system of claim 1 , wherein the identifier for the first event is an identifier for an event type of the first event.
6. The system of claim 1 , wherein the action comprises one or more of: providing an indication associated with the event, automatically mitigating a behavior associated with the event, or logging the event.
7. The system of claim 1 , wherein monitoring comprises generating a hook on an application programming interface (API).
8. A method, comprising:
evaluating a first rule in a rule data store to determine a first event associated with the first rule;
monitoring for an event indication associated with the first event;
when an event indication is detected, identifying the first rule associated with the received event indication;
generating an event packet based on the received event indication, the event packet comprising an identifier for the first event and a parameter relating to the first event;
providing the generated event packet to a rule virtual machine executing the first rule; and
performing an action based on an evaluation of the event by the rule virtual machine.
9. The method of claim 8 , further comprising initializing the rule virtual machine based on a second event associated with a second rule.
10. The method of claim 9 , wherein the second rule is a matching rule associated with multiple events.
11. The method of claim 8 , wherein the first event is a file event, a process event, or an event associated with a registry.
12. The system of claim 8 , wherein the identifier for the first event is an identifier for an event type of the first event.
13. The method of claim 8 , wherein the action comprises one or more of: providing an indication associated with the event, automatically mitigating a behavior associated with the event, or logging the event.
14. The method of claim 8 , wherein monitoring comprises generating a hook on an application programming interface (API).
15. A non-transitory computer readable medium, comprising instructions for:
evaluating a first rule in a rule data store to determine a first event associated with the first rule;
monitoring for an event indication associated with the first event;
when an event indication is detected, identifying the first rule associated with the received event indication;
generating an event packet based on the received event indication, the event packet comprising an identifier for the first event and a parameter relating to the first event;
providing the generated event packet to a rule virtual machine executing the first rule; and
performing an action based on an evaluation of the event by the rule virtual machine.
16. The non-transitory computer readable medium of claim 15 , wherein the instructions are further for initializing the rule virtual machine based on a second event associated with a second rule.
17. The non-transitory computer readable medium of claim 16 , wherein the second rule is a matching rule associated with multiple events.
18. The non-transitory computer readable medium of claim 15 , wherein the first event is a file event, a process event, or an event associated with a registry.
19. The non-transitory computer readable medium of claim 15 , wherein the identifier for the first event is an identifier for an event type of the first event.
20. The non-transitory computer readable medium of claim 15 , wherein the action comprises one or more of: providing an indication associated with the event, automatically mitigating a behavior associated with the event, or logging the event.
21. The non-transitory computer readable medium of claim 15 , wherein monitoring comprises generating a hook on an application programming interface (API).