Port Scanning, but Monitoring is Off for Target Device
My work laptop is connected to my home network that is protected by Firewalla. Security reached out to inform me a few months ago that ESET was detecting a Win32/Botnet.generic attack, which they stated appeared to be a device on my home network doing port scans against my laptop. I triaged this at that time and learned that Firewalla does do port scans and I turned Monitoring off for my work laptop in Firewalla. Which successfully addressed the issue.
As of today, they are reporting that the issue is occurring again. I reviewed Firewalla and logs and confirmed that it's coming from my Firewalla device to my company laptop, but Monitoring for that laptop is still turned off. I have not found any other area that could explain why this is happening again. Does anyone have any insight?
-
When you say + button, where exactly is that? I am on Firewalla Blue and if I pull up the device in question it shows Monitoring as disabled. So, I do believe that there should be no port scanning for the device.
From the Security team's ESET logs it appears it's showing it as a warning, but is being blocked as well as the action.
-
Thanks! I guess I should have slowed down a bit and dug into all the options more. When I went there first it didn't show me the additional options right away, so I thought it was a system wide on/off type of thing. I do see it now. I think it might be cool to do an inverse type of selection, like Apply to All except for devices you define. For example, in my case I have around 60 devices and I only wanted to exclude 2 devices from having port scans done. I did not see an easy way to just exclude those two and have it run for all others on my network by default.
-
Okay, will let the team know this requirement.
May I know if ESET will block firewalla after detecting the scan? or it just warn you? We have several cases from the consumer side, where the antivirus software will block the router (which is firewalla) and kill internet when detect scanningÂ
Please sign in to leave a comment.
Comments
8 comments