Re: SQL cluster firewall question
- From: Erland Sommarskog <esquel@xxxxxxxxxxxxx>
- Date: Fri, 19 Jan 2007 14:25:22 -0800
Enghps1 (jamesserjeant@xxxxxxxxxxxxxxxx) writes:
We have been running a standalone SQL2005 box which uses a dedicated
webserver for the last 12 months and both sit on our perimeter (DMZ)
zone. The SQL box is now due to be replaced by a failover SQL cluster.
Failover clusters requires domain access and therefore it will have to
sit on the TRUSTED zone but now we face a real security issue with how
the webserver (in the DMZ) can safely talk to the cluster (in the TRUST)
without compromising security. I can maybe live with opening 1433 for
SQL as it will still require authentication,
But make sure that the web server *never* builds SQL strings by
interpolating parameters from user input (including cookies!), but
always used parameterised queries or calls stored procedures through
RPC. Also, as extra safety precuation, make sure that the web
server connects to SQL Server through a low-privileged account,
preferrably only with EXEC access to stored procedures.
but .NET on the DMZ webserver will still require port 80 to be open to
the cluster.
One cannot accuse me for knowing to much about web servers, but why
would .Net have to access port 80 on the cluster? DO you use HTTP
Endpoints on SQL Server?
Then again, port 80 is only dangerous if there is something powerful
listening there, isn't it?
--
Erland Sommarskog, SQL Server MVP, esquel@xxxxxxxxxxxxx
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
.
- References:
- SQL cluster firewall question
- From: Enghps1
- SQL cluster firewall question
- Prev by Date: Re: SQL password
- Next by Date: Re: ASP - Stored Procedure best practice?
- Previous by thread: SQL cluster firewall question
- Next by thread: SQL password
- Index(es):
Relevant Pages
|
|
