Outpost Leak Test Score Card

[David]

Leak Test Information

Note: This information will be updated as facts change.

PASS: Both Agnitum and independent user verification of Outpost's ability to block this Leak Test exists.

PASS (with conditions): Same as PASS, except that some user modification is required to the default setup of Outpost or their Operating System to pass the Leak Test.

UNCONFIRMED: Positive confirmation of Outpost's ability to block this Leak Test have not yet been confirmed by both Agnitum and the independent users.

FAIL: Both Agnitum and independent users verify Outpost cannot pass this Leak Test in its current form.

1. GRC LeakTest: PASS

2. Yalta: PASS

3. Yalta Enhanced: PASS

4. Outbound: PASS

5. Too Leaky: PASS

6. FireHole: PASS

7. AtelierWeb Firewall Tester: PASS (10/10) - If you allowed auto-configuration of rules during setup, you will have to remove explorer.exe from your Partially Allowed Application List to get a perfect score on this Leak Test.

8. Thermite: FAIL - Agnitum is working this issue currently.

9. Oops: PASS (with conditions) - The DNS Client service must be disabled so that each application has to make its own DNS request as opposed to using svchost.exe (XP) or services.exe (2000). The global DNS and any application rules associated with svchost.exe (XP) or services.exe (2000) must then be removed and DNS connection rules must be made for each application requiring internet access. The rules should specify the protocol (UDP), remote port (53), remote host (IP of your ISP DNS Servers), and set to Allow It in order to function. Most likely, all of the applications in your Partially Allowed Applications list, except for svchost.exe (XP) and services.exe (2000), will need this extra DNS rule added. Agnitum currently has this on their roadmap to address. So, perhaps in the future, the status can be changed from PASS (with conditions) to PASS per the scoring scheme outlined above.

10. Copycat: FAIL - Agnitum has reported that it is working on this issue. Several Bug Reports have been submitted to Agnitum through the Bug Tracking System. So, proper follow-up on this issue will be maintained.

11. GOD2: UNCONFIRMED - According to Agnitum, their internal tests show that Outpost V2.0 can pass this test. But, Agnitum has specified that component control must be set to 'MAXIMUM' before running the test. If independent user verification of Outpost's ability to block GOD2 is made available through the forum, one of Agnitum's mailing lists, or through some other means, the Outpost status regarding this Leak Test will likely change to PASS (with conditions). This is due to the fact that if confirmed, the user will have to change Outpost's default Component Control setting from Normal to Maximum in order to pass this test.

12. Wall Breaker Test #1: FAIL

12. Wall Breaker Test #2: FAIL

13. PC Audit: PASS

14. PC Audit2: PASS

Thanks to muchod, the beta testers, and Agnitum for providing the necessary information to create this scorecard.