Firewall/AV Combination

I just spotted this thread, "What is your firewall/AVcombination", over at DSLR security forum.

http://www.dslreports.com/forum/remark,8459284~root=security,1~mode=flat

There are a lot of ZA/ZAP and NAV users there. Thought it might be interesting to see if there is a big difference here. I have a feeling there might be.

I'll start off........

Outpost Pro 2 NOD32v2

Added URL tags

 

Outpost Pro 2, then either NOD32, F-Prot, or McAfee Enterprise depending on the day.

 

As I said there, I have ZA, BI, and KAV Personal. Thinking of putting BI on manual startup instead.

Am still considering Outpost Pro 2.0.

 

SSM, Sygate Pro, Nod32, and Ad-aware is a winning combo, IMO.

Not to mention my Win2k laptop still runs quickly. I can't say the same for McAfee, Norton, F-Secure, & KAV. ZA is great, I recommend it, just don't use it (dislike the GUI). I tried Outpost 2, but it does weird things (temp files permanetly open), and has local exploits. SSM seems to be a unique program, now that Tiny Trojan Trap is abandon-ware.

 

Well this is easy. I'll just cut and paste my response in the other forum.

On Sony NVR23 Laptop:
NIS2004
RAV8 (non-resident)
Trojan Hunter 3.7

On Homebuilt Athlon1800 Desktop:
ZAPro 4.0
NOD32
KAV 4.5 (non-resident)
TDS-3

Other related programs: Port Explorer, Wormguard, Process Guard, Tracks Eraser Pro, Spybot, Steganos Safe 6.

 

.uptime.......I'm no expert so I'm not sure what you mean. I'm using Outpost Pro and never notice anything weird with the temp files. Can you explain this and especially the local exploit thing? I like Outpost Pro, but don't want to continue using it if it's a security risk to my PC

 

For this year
e Trust v7 promo
EZ firewall
TDS3
fire trust benign

 

currently kavpp+ tiny trial on my laptop and f-secure internet security beta on the desktop(w2k). kavlite+ ZAF on win 98

 

It's not an external exploit, just an internal security risk for multi-user PCs. From the open (or is it save as export?) for the configuration, any user can browse through files in the said window with system (admin) level access.

When I ran the trial, it kept permanent jet*.tmp files open in my winnt temp directory. I found it unusual, is all. Outpost also appears flawed as how it goes about reading other programs, someone recently posted a log file for a security program (process guard I think?) that showed that it was trying to gain write access in addition to read access. I am not sure if that is a threat at all, but it certainly looked like bad programming implementation.

 

On my setup too.

Now that I think about it - the jet*.temp file must be part of Outpost's logging activity. FYI the logging service is a memory-hog, and probably the #1 user complaint over at the Outpost forum, IMO. There are a couple of user-developed workarounds to tame the log size - I'm using a shutdown script, but no doubt Agnitum considers it a high priority for the next build.

I seem to recall the same thread.

Wouldn't know, but I sure am interested.

 

Hmmmm. Thanks for that information .uptime. And with optigrab agreeing........double Hmmmm.

 

Win98SE with avast! 4 Home Edition & Kerio 2.1.5. Never had any problems with either program.

 

Windows98SE, Sygate Personal Firewall 5.5, AVG Antivirus 6.0 - Backup scanner is F-prot for DOS, so far, no problems..

 

windows xp home
nod32v2
ZA+

Everythings getting along ok here.

 

XP Pro 2k Pro
NOD32 NOD32
ZA Pro 4 ZAP Pro
BOClean BOClean

Behind a Linksys Router