Well visiting a site with my browser via http: 80 I was alerted that a NMap Null Scan was thwarded via port 1449. Why wasn’t I also alerted by ZA firewall. What firewall protects from these scans. Why an av solution alerts and a fw is silent.
That was actually what it was, but I want to know how much I am at risk, because it was the first time I experienced that when visiting the website I was alerted to a scan.
The problem with the Windows boot you can’t select the order applications are loaded so it is possible ZA (you didn’t say if it’s the free or pro, I assume free) isn’t getting loaded or something is delaying or slowing it and Network Shield gets in there first.
As to if you are at risk, I wouldn’t have thought so as Network Shield is effectively doubling up protection on the common attack ports and ZA should be stealthing and or covering the rest. What concerns me is if Network Shield gets in first and blocks an attack, effectively signalling your presence, which could attract further attention.
I suggest a full shields-up check at grc.com and see if you are stealthed, you probably will be, because any activity on the ports avast monitors is unlikely to find malicious content and ZA would effectively be the next in line.
Well Network Shield effectively blocks the download and if it blocks the download it is loading before the firewall, in which case the firewall won’t know about the attempt.
ZA free and pro I would have thought would fall into that category of a good firewall intercepting before Network Shield, but as I said there is no control on application loading on boot (by default). I don’t know if I would want to use something like Startup Delayer to delay the start of avast to try to let ZA load first. To me it seems to be a loading problem rather than a good/bad firewall issue.
The ZA is 6.5.737.000. The truth of the matter is that there was a conflict between that ZA version and the Torpark browser I was using at that moment. Why I cannot imagine but after using Torpark for a while the ZA client closes down and must be restored through reboot, very irritating behaviour of ZA. After that experience I have given up on that Torpark version (checked the checksum on downloading, but there are more experiencing strange ZA client behavior using Torpark and ZA at the same time. (Some had to install ZA anew after downloading Torpark). Then I had the Nmap null alert from the av. Why ZA conflicts with the Torpark (firefox with tor-router browser)?