QUOTE (CogitoErgoSum @ May 21 2008, 11:21 PM)

Hello jjmonge,
Although, I have not personally used the DefenseWall(DW) and SandBoxie(SB) combination, it appears that this set-up offers solid and strong protection without conflicts according to those who use it. Since you are already using DW which employs a policy restriction sandbox and SB which employs a virtual sandbox, I highly recommend that you seriously consider uninstalling SpyWall(SW) as it also employs a sandbox to minimize or eliminate potential conflicts. In short, running three sandboxes simultaneously is like waiting for a train wreck to happen which may result in less overall protection due to possible interference between security programs. Other than SW, you have a good set-up with both DW and SB. Lastly, if you are using a router with a NAT and SPI firewall you should be okay without a software firewall. On the other hand, if you are not using a hardware firewall, I highly recommend that you use the Windows firewall at the very least for basic inbound protection. Hope this helps.
Peace & Gratitude,
CogitoErgoSum
Sorry guys, but I have a clear opinion on using both a policy sandbox and an application based virtaulisation sandbox: useless, does not add any dimension to your protection:
In general:
Level 1 = Firewall
Level 2 = Policy based Threat gate mitigation like DefensWall (the best) or GeSWall
Reason why this is such a brilliant solution is that DefenseWall remembers the status of a downloaded file or program. You do not need to throw it away as in a virtual sandbox, because it remains chained to the strengthened limited user environment of DefenseWall. This is exactly the reason why virtual sandbox adds nothing, it only makes it more difficult to use Besides in 9 out 10 test DefenseWall proves to be stronger that SBIE, SfaSpace, GeSWall, Returnil etc, so that is a second reason not to bother.
Level 3 = an antivirus
In 99.99 of the situations this is easy and sufficient
My setup
Level 1: Default windows XP firewall
Level 2: DefenseWall
Level 3: ThreatFire (behavior blocker with AV check) with an extra rule for outbound protection
Looking at the scope of protection you notice that DW and TF will overlap. Point is that TF will take as many CPU cycles as an Antivurus. With the same system impact I now get an intelligent behavior blocker for free (on top of the AV check). Bonus of the bahavior blocker: when I allow a program to install (DW = run as trusted) I would like a second safety net, TF provides this (AV + Behavior blocker).