Securing SQL
From: Bad Beagle (maxwelli_at_nospam.postalias)
Date: 11/23/05
- Next message: Stryder Honeymonkey: "Certificate-based DHCP authentication"
- Previous message: Gopi: "w32 spam list"
- Next in thread: Steven L Umbach: "Re: Securing SQL"
- Reply: Steven L Umbach: "Re: Securing SQL"
- Reply: karl levinson, mvp: "Re: Securing SQL"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Wed, 23 Nov 2005 08:17:22 -0700
I would like to know what the suggestions are for designing a secure
solution for Windows servers and SQL. I have a Windows 2000 server that is
my web server - this server is in the dmz. This server has pages that
access a SQL server. The SQL server hosts a database that is used both
internally and externally and needs to be updated by someone internal. My
question is where this SQL server should be placed - on the lan and do file
replication or in the dmz and open up the firewall for sql traffic. Any
thoughts, suggestions, recommendations. Thank you.
- Next message: Stryder Honeymonkey: "Certificate-based DHCP authentication"
- Previous message: Gopi: "w32 spam list"
- Next in thread: Steven L Umbach: "Re: Securing SQL"
- Reply: Steven L Umbach: "Re: Securing SQL"
- Reply: karl levinson, mvp: "Re: Securing SQL"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
