Network traffic correlation engine
A network traffic correlation engine monitors inbound and/or outbound connection information received from on each host computer system on a network. Each host device on the network store data logs corresponding to information corresponding to communications sent by the device and received by the device. The network traffic correlation engine correlates connections between different hosts throughout the network. If the network traffic correlation engine identified unmatched outbound and inbound connections, the network traffic correlation engine generates an alert to initiate further investigation and may also provide a mapping of the communications showing a possible start device for the connection and/or a type of access that the connections may now be providing.
1. A system comprising:
a plurality of hosts on an enterprise network, each host of the plurality of hosts sending communications via the enterprise network; and
a computing device, comprising:
a processor; and
non-transitory memory storing instructions that, when executed by the processor, cause the computing device to:
monitor, by a network traffic correlation engine, network communications aggregated from the plurality of hosts on the enterprise network, wherein the network communications comprises inbound and outbound connection information received from each host on the enterprise network;
identify, by the network traffic correlation engine, whether a correlation exists between a first communication sent from a first host device via the enterprise network to a second host device and a second communication received via the enterprise network by the second host device;
determine, based on whether a correlation exists between the first communication and the second communication, whether an anomalous communication condition exists; and
trigger, based on the correlation, an alert identifying that the anomalous communication condition is present between the first host device and the second host device.
2. The system of claim 1 , wherein the instructions, when executed, cause the computing device to:
aggregate information from a plurality of network communication services and data logs, wherein the information corresponds to a plurality of network communication connections to and from the first host device and the second host device.
3. The system of claim 1 , wherein the instructions, when executed cause the computing device to:
match messages received by the first host device to messages sent by the second host device based on aggregated communication information to detect an anomalous communication on the enterprise network.
4. The system of claim 1 , wherein triggering the alert comprises providing an indication of the alert on a user interface device at a central location on the enterprise network.
5. The system of claim 1 , wherein the anomalous communication condition comprises an indication that logging of sent messages was disabled.
6. The system of claim 1 , wherein monitoring of network communications information aggregated from a plurality of hosts on the enterprise network comprises aggregating information received from a plurality of host intrusion detection systems each associated with a different host device.
7. A method comprising:
monitoring, by a network traffic correlation engine, network communications based on aggregated information from each host of a plurality of hosts on an enterprise network, wherein the network communications comprises inbound and outbound connection information;
identifying, by the network traffic correlation engine, whether a correlation exists between a first outbound communication sent from a first host device and a second inbound communication received by a second host device; and
triggering, based on the correlation, an alert identifying that an anomalous communication condition is present between the first host device and the second host device, wherein the anomalous communication condition comprises an indication of host to host communication.
8. The method of claim 7 , comprising:
aggregating information from a plurality of network communication services and data logs, wherein the information corresponds to a plurality of network communication connections to and from the first host device and the second host device.
9. The method of claim 7 , comprising,
matching messages received by the first host device to messages sent by the second host device based on aggregated communication information to detect the anomalous communication condition on the enterprise network.
10. The method of claim 7 , wherein triggering the alert comprises providing an indication of the alert on a user interface device at a central location on the enterprise network.
11. The method of claim 7 , wherein the anomalous communication condition comprises an indication that logging of sent messages was disabled.
12. The method of claim 7 , wherein the monitoring of network communications information aggregated from a plurality of hosts on the enterprise network comprises aggregating information received from a plurality of host intrusion detection systems each associated with a different host device.
13. The method of claim 7 , further comprising determining, based on whether a correlation exists between a first communication and a second communication, whether an anomalous communication condition exists.
14. One or more non-transitory computer-readable media storing instructions that, when executed by a host computing device comprising a processor, memory, and a communication interface, cause the host computing device to:
aggregate, by a network traffic correlation engine, network communications information from a plurality of hosts on an enterprise network, wherein the network communications information comprises inbound and outbound connection information associated with each host on the enterprise network;
identify, by the network traffic correlation engine, whether a correlation exists between a first outbound communication sent from a first host device and a second inbound communication received by a second host device; and
trigger, based on the correlation, an alert identifying that an anomalous communication condition is present between the first host device and the second host device, wherein the anomalous communication condition comprises an indication of host to host communication.
15. The one or more non-transitory computer-readable media of claim 14 , wherein the instructions, when executed by the processor, cause the host computing device to:
aggregate information from a plurality of network communication services and data logs, wherein the information corresponds to a plurality of network communication connections to and from the first host device and the second host device.
16. The one or more non-transitory computer-readable media of claim 15 , wherein the instructions, when executed by the processor, cause the host computing device to:
match messages received by the first host device to messages sent by the second host device based on the aggregated information to detect an anomalous communication on the enterprise network.
17. The one or more non-transitory computer-readable media of claim 14 , wherein triggering the alert comprises providing an indication of the alert on a user interface device at a central location on the enterprise network.
18. The one or more non-transitory computer-readable media of claim 14 , wherein an anomalous communication condition comprises an indication that logging of sent messages was disabled.
19. The one or more non-transitory computer-readable media of claim 14 , wherein monitoring of network communications information aggregated from a plurality of hosts on the enterprise network comprises aggregating information received from a plurality of host intrusion detection systems each associated with a different host device.
20. The one or more non-transitory computer-readable media of claim 15 , wherein the instructions further cause the host computing device to determine, based on whether a correlation exists between a first communication and a second communication, whether an anomalous communication condition exists.