Re: Setting up IPSec on a webserver
From: x y (jamescagney90210@excite.com)
Date: 06/16/02
- Next message: twillie2002@hotmail.com: "Forget administrator password"
- Previous message: x y: "Re: controling ports"
- In reply to: tc: "Setting up IPSec on a webserver"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
From: "x y" <jamescagney90210@excite.com> Date: Sat, 15 Jun 2002 19:00:32 -0400
IPsec in windows 2000 has I believe two main functions: deciding when to
encrypt network traffic and deciding when to filter or block network
traffic. Using packet filters to block certain ports on a web server can be
a good idea to secure it, though I wouldn't recommend using win2000 ipsec
port filtering as there is no logging, which is essential IMHO. You could
consider using sygate firewall which is free for non-commercial use and
around $35 for business use. even though it may feel funny putting free
software that is most commonly used for workstations, the vendor claims it
is also suitable for servers.
enabling encryption of traffic on a web server between it and other windows
2000 servers on your internal network [such as a domain controller for
authentication, sql server, etc] might not be a bad idea depending on your
needs, if you are concerned about a hacker hacking one of the systems on
your internal network and installing a sniffer to capture and read the
traffic.
"tc" <tcruise@ev1.net> wrote in message
news:e77501c212f5$c962d460$39ef2ecf@TKMSFTNGXA08...
> What do I gain in terms of security from setting up IPSec?
>
> How do I setup and configure IPSec for my webserver?
- Next message: twillie2002@hotmail.com: "Forget administrator password"
- Previous message: x y: "Re: controling ports"
- In reply to: tc: "Setting up IPSec on a webserver"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
|
