"Jeremy" <> wrote in message
news:...
> So, you just use the XP sieve ware, not something I would brag about in
> public 
>
> JJ
>
No gentlemen I don't use XP's ICF at the present time. No, what I use is a
NAT router, BlackIce, and IPsec to protect the machines on inbound and
outbound threats on the LAN.
The ICF on the XP O/S is no different than using a NAT router. One of the
main purposes of the NAT router is to stop unsolicited inbound traffic to
the machine. If an application on the machine doesn't solicited the traffic
from a remote application, the ICF just like any other host based FW, NAT
router or FW appliance will stop the unsolicited inbound traffic.
To protect things such as the services that are running on the machine,
Application Control on a personal FW solution is useless when the PFW is not
integrated with the O/S, as malware such as a Trojan, spyware, etc, etc will
beat any PFW solution to the TCP/IP before a PFW can even get started on the
TCP/IP to stop it at boot. As long as the machine is not booted, Application
Control is affective, other than that, it's kind of useless.
Time and time again, I see some poster indicate, I have stopped this unknown
request by svchost from accessing the Internet with my Application Control
on the PFW. And yet they turn around and let svchost access the Internet for
some other reason. What happen to the reason that one stopped svchost from
accessing the Internet, because it's never svchost that wants access as it's
just the messenger for the O/S and other programs that use svchost on their
behalf, such as Trojans and spyware? The list is long in this area of I
stopped something but I know not the reason why.
IPsec on the Win2k, XP, and 2K3 O/S (s) can get to the TCP/IP connection
first at boot to stop inbound or outbound and in many ways is far superior
to a third party host based FW solution.
http://www.petri.co.il/block_ping_tr...with_ipsec.htm
http://www.analogx.com/contents/articles/ipsec.htm
I also know what a FW is suppose to do. Do you? Do you see anything about
Application Control and the rest of the bloat crap that's in a these PFW
solutions, that only confuses the user if they don't know what is happening
in the link?
http://www.firewall-software.com/fir..._firewall.html
You're right, I go to where I am suppose to go to secure the machine and
that's to the O/S, if you have one that security can be implemented, because
the buck stops at the O/S and everything else is secondary to it. That
includes the NAT router, BlackIce, AV and any other third party solution in
this area. If the O/S is not secure, than nothing on the machine can be
secure.
http://www.uksecurityonline.com/index5.php
And BTW, the XP FW on the release of SP 2 will have Application Control and
will be able to get to the TCP/IP first at boot, since it is integrated with
the O/S.
Currently, IPsec and ICF on the XP O/S is a solid combination. I think the
combination should be even better with the release of SP 2 for XP.
But I also use other tools to look around for myself from time to time and
not depend solely upon a single element in the protection. That and my
common sense and not do stupid things with happy fingers goes a long way.
Duane