Re[2]: FN-FORUM Internet Down

date posted 27th January 2003 18:58

On Sun, 26 Jan 2003, Richard Lowe wrote:

> Sunday, January 26, 2003, 10:17:34 AM, you wrote:
> L> So blame the stupid toerags carrying out the attack. Although it
> L> wouldn't have been so bad if fewer boxes had responded - the only
> L> ones that have even a glimmer of an excuse for responding are Web
> L> servers running SQL 2000 that have to be open to the outside world
>
> I'm not convinced that any SQL Server installation should be open to
> the outside world (whether patched or not). Good rule of thumb is to
> always put it behind a firewall.

Agree entirely.

> If it does need to be open (eg. for a remote client or server to
> connect to it) I think the best way to go is to only allow access to
> via a secure VPN.

Or, if the budget/skills aren't there to implement a VPN, at least limit the
IP address of that connect to legitimate clients.

On a tangent, I can't really think of a good reason to be running the
database backend on the same host as a public-facing webserver either. (I
don't regard cost as a reason in this instance, just an excuse... ;-)

> Just my 10p worth. ;)
> Cheers,
> Richard.

Best Regards,
Alex.
--
Alex Butcher Brainbench MVP for Internet Security: www.brainbench.com
Bristol, UK Need reliable and secure network systems?
PGP/GnuPG ID:0x271fd950