
Once the issues have been resolved, the SNMP port can be turned up again from the preferences. It is up to the network administrator now to intervene and do any necessary cleanup operation on the attacker host. Within a minute from the increase in the host score, mitigation causes the port on the SNMP device to be turned downįrom this point on, attacker host 192.168.2.149 is effectively disconnected from the network and, thus, it becomes harmless. This score is high enough to ensure the attack mitigation via SNMP kicks in. Due to this suspicious activity, there is a significant increase in the score of 192.168.2.149 Indeed, there are many alerted “TCP Connection Refused” flows having 192.168.2.149 as source – apu is the DNS name of 192.168.2.149. The port scan is immediately detected by ntopng ntopng, using traffic and SNMP data is able to identify host 192.168.2.149 as a PcEngines connected to interface gigabitethernet15 of switch 192.168.2.168. For this example, an attacker host 192.168.2.149 is configured to run a port scan ( nmap -sS) towards 192.168.2.222. Uses SNMP to turn access ports down, thus effectively disconnecting the attackers from the healthy network.Īttack mitigation via SNMP is implemented as an ntopng plugin available in versions Enterprise M and above, and can be enabled from the user scripts configuration page.Finds physical switches and access ports where attackers are connected to.Uses an indication of compromise known as score to determine whether an IP is an attacker (client score) or a victim (server score).Ntopng, starting from version 4.1, capitalizes on this information to implement attack mitigation via SNMP.
#Ntopng dump flows mysql mac#

One of the greatest strengths of ntopng is its ability to correlate data originating at different layers and at multiple sources together.
