I was running NOD32 v3.x on one of my systems along with ZAP 8.0.059.000 and there was an incompatibility problem related to using a password and having access to secure web sites requiring cookies. This happened when the custom privacy settings were enabled in ZAP. I never knew the exact cause of the conflict but it seemed to be related to the proxy based design of NOD32 v3 engine interfering with the normal working of the privacy settings in ZAP. This conflict existed on every machine that used ZAP v7.x or v8.x along with versions of NOD v3.x. Because of this nagging conflict when the privacy settings were enabled in ZAP v7.x and ZAP v8.x I have been using NOD32 v2.7x on most of my systems. I only used NOD32 v3 on one system for testing the latest versions of NOD32. That system was just upgraded to NOD32 v4 with what appear to be surprisingly positive results. I still have more testing to do before I will be certain of the results but so far it seems like the previous compatibility problem that existed with NOD32 v3 no longer exists in NOD32 v4. I don't know whether or not there was a deliberate attempt by ESET developers to correct this particular compatibility problem with ZAP...but if these positive results continue I would like to express my appreciation to ESET and their NOD32 v4 developers for making these improvements. I might finally be able to upgrade all those other machines that have been running v2.7 with the latest v4!